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
This has been something that I have wanted for a while since we have the conditional statement on literally every other LB visualization component except the radiation ones. I have greatly wanted the ability to make visuals that show me the radiation in just the time when it is too hot, without me trying to figure out what the "hot analysis period" is.
I can imagine an alternative way of making this happen where the SelectedSkyMtx does not get any new inputs but just the HOY input on the SelectedSkyMtx becomes a list of HOYs instead of an item. Then, we have a separate component that takes any annyalHourlyData and conditionalStatement to spit out a list of HOYs that satisfy it.
If anyone has a preference for one of these workflows, speak your mind here.
I feel this is something that I would like for the ACADIA workshop examples so I am adding this to the milestone.
-Chris
The text was updated successfully, but these errors were encountered:
@chriswmackey Just wanted let you know that I'm taking care of this in the new library similar to what you have mentioned up there which is basically filtering the days based on the list of HOYs.
@mostaphaRoudsari ,
This is great and I am very much looking forward to this!!! I am going to make you the assignee on this one and let me know if there is anything I can do to help.
-Chris
This has been something that I have wanted for a while since we have the conditional statement on literally every other LB visualization component except the radiation ones. I have greatly wanted the ability to make visuals that show me the radiation in just the time when it is too hot, without me trying to figure out what the "hot analysis period" is.
I can imagine an alternative way of making this happen where the SelectedSkyMtx does not get any new inputs but just the HOY input on the SelectedSkyMtx becomes a list of HOYs instead of an item. Then, we have a separate component that takes any annyalHourlyData and conditionalStatement to spit out a list of HOYs that satisfy it.
If anyone has a preference for one of these workflows, speak your mind here.
I feel this is something that I would like for the ACADIA workshop examples so I am adding this to the milestone.
-Chris
The text was updated successfully, but these errors were encountered: