Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write output table with solver stats per saveat #1677

Merged
merged 8 commits into from
Aug 6, 2024

Conversation

SouthEndMusic
Copy link
Collaborator

Fixes #1674.

Not sure how to test this?

@SouthEndMusic SouthEndMusic changed the title Write output file Write output table with solver stats per saveat Aug 1, 2024
@SouthEndMusic SouthEndMusic requested a review from Jingru923 August 5, 2024 09:49
Copy link
Member

@visr visr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this look backwards over time, e.g. that a record for t_i, is over the period t_i-1 to t_i? It would be consistent with the other tables if it is over the coming period.

I think water_balance_calls can be a bit confusing, perhaps rhs_calls or f_calls would be better. Otherwise we encode our internal function name in our data model.

Copy link
Contributor

@Jingru923 Jingru923 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes look good to me.

I don't have opinions on the naming of water_balance_calls

@SouthEndMusic SouthEndMusic merged commit a58f317 into main Aug 6, 2024
26 of 30 checks passed
@SouthEndMusic SouthEndMusic deleted the save_solver_stats branch August 6, 2024 09:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Save solver stats per saveat
3 participants