You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regardless of how we have developed the current workflows and how much can be done once the analysis is over I believe most of our users would still want just to get the results. Specially if they want to run 100s of them in the normal parametric studies then we can support faster but still accurate workflows.
Here are my suggestions:
For radiation analysis instead of running 3 analysis (total, direct, sun) we can run 2 (sky, sun) and add them up together. @sariths and I have discussed this before and we will miss the ambient contribution of the direct sun but it is still better than what we currently do in Ladybug legacy.
For annual analysis (regardless of which recipe to be used) we currently load all the values from all the sources for analysis points and then post process the results. This approach is totally valid for in-depth studies and provides us handful post processing features however if one just wants to calculate the annual metrics we can stop loading the values and just calculate the annual metrics from the files. I'm less keen to make this change as I assume in case of no windowGroups the differences are going to be minimal in speed, however, for 1000s of points the memory usage is going to be very different.
@sariths thoughts? This is something that we can implement right after we have a [pre]release.
The text was updated successfully, but these errors were encountered:
@mostaphaRoudsari I agree with point 1 for the most part assuming that the ambient contribution to the simulation isn't critical. This should work for outdoor radiation studies.
Which are the files in the values and just calculate the annual metrics from the files? Are these ill files?
@sariths, Yes. The ill files. In case there is no window groups or dynamic blinds it will be a single file for total and a single file for direct results.
Regardless of how we have developed the current workflows and how much can be done once the analysis is over I believe most of our users would still want just to get the results. Specially if they want to run 100s of them in the normal parametric studies then we can support faster but still accurate workflows.
Here are my suggestions:
For radiation analysis instead of running 3 analysis (total, direct, sun) we can run 2 (sky, sun) and add them up together. @sariths and I have discussed this before and we will miss the ambient contribution of the direct sun but it is still better than what we currently do in Ladybug legacy.
For annual analysis (regardless of which recipe to be used) we currently load all the values from all the sources for analysis points and then post process the results. This approach is totally valid for in-depth studies and provides us handful post processing features however if one just wants to calculate the annual metrics we can stop loading the values and just calculate the annual metrics from the files. I'm less keen to make this change as I assume in case of no windowGroups the differences are going to be minimal in speed, however, for 1000s of points the memory usage is going to be very different.
@sariths thoughts? This is something that we can implement right after we have a [pre]release.
The text was updated successfully, but these errors were encountered: