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
As of #4621, summary variables are now evaluated lazily to improve performance. However, it has made getting a data frame of all the summary results a little clunky. E.g. instead of df = pd.DataFrame(sim.solution.summary_variables) you now need to do
or something equivalent. I propose we add an all_summary_variables attribute that returns the same as all_summary_variables in the above snippet. Or just make it so that summary_variables["Cycle number"] returns list(summary_variables.cycle_number). This would (almost) be consistent with Solution where you can do sol.t or sol["Time [s]"].data.
@pipliggins let me know if this is sensible or if I'm missing something from the new SummaryVariables class.
The text was updated successfully, but these errors were encountered:
As of #4621, summary variables are now evaluated lazily to improve performance. However, it has made getting a data frame of all the summary results a little clunky. E.g. instead of
df = pd.DataFrame(sim.solution.summary_variables)
you now need to door something equivalent. I propose we add an
all_summary_variables
attribute that returns the same asall_summary_variables
in the above snippet. Or just make it so thatsummary_variables["Cycle number"]
returnslist(summary_variables.cycle_number)
. This would (almost) be consistent withSolution
where you can dosol.t
orsol["Time [s]"].data
.@pipliggins let me know if this is sensible or if I'm missing something from the new
SummaryVariables
class.The text was updated successfully, but these errors were encountered: