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
Well of course that function writes them, but I think it would be much more useful to separate calculating and writing, in order to not have to pass dfPrice back to many other write_xxx functions (and then navigate getting data out of that dataframe).
Ah, I think I have done that in my branch. If anyone of you actually is working on removing dfPrice from each writing_xxx, check my branch out for an example.
My branch is Dev_newCO2. I think there are only several places that use dfPrice, right? Maybe we should start with counting how many places are with dfPrice.
Many times in various write_output functions, the value
dual.(EP[:cPowerBalance])./inputs["omega"]*scale_factor
is computed. It would be great to put this in a function
that returns some data structure (Matrix? DataFrame?) of prices. Potentially it would be even better if this calculation were cached somehow.
This could make several output functions simpler and easier to understand.
The text was updated successfully, but these errors were encountered: