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
For repeat calculations, if there are several calculations that should be repeated then looping or even using map will take longer if done individually for each calculation than if the calculations can be grouped
EG: There might be 3 calculations that are done for all layouts and inverter blocks.
tracking
plane of array irradiance
power
Looping 3 times will take longer than just looping once.
dag magic
Since repeat calculations are independent, then having a super calculator and an easy way to repeat them (ie a special map calculator) could be coordinated with the DAG, so that in the future, carousel knows or can distributed them to multiple machines or processes.
just like data
This idea is somewhat similar to the idea of nesting data.
Also in order to pass the arguments to a group of calculators, it might be easier to use a nested source of data used for each of the sub-calculations
The text was updated successfully, but these errors were encountered:
Thanks @anomam for this GREAT 🎉 idea 💡
Similar to:
why
For repeat calculations, if there are several calculations that should be repeated then looping or even using
map
will take longer if done individually for each calculation than if the calculations can be groupedEG: There might be 3 calculations that are done for all layouts and inverter blocks.
Looping 3 times will take longer than just looping once.
dag magic
Since repeat calculations are independent, then having a super calculator and an easy way to repeat them (ie a special
map
calculator) could be coordinated with the DAG, so that in the future, carousel knows or can distributed them to multiple machines or processes.just like data
The text was updated successfully, but these errors were encountered: