Format for logging solver statistics
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Read the issue discussion and inspect Luke's ida-stats-helper branch, which already logs IDA statistics in JSON. Decide whether statistics belong in a separate file and choose a format before planning a schema and phasor dynamics app options; done means agreeing on that format and interface for comparing time integration methods.
Written by the indexing model from the issue text.
Description
Summary
I'd like to use this issue to decide a format for writing solver statistics to a file for the phasor dynamics app and possibly other uses. My first though was to include solver statistics in the monitoring CSV file, but there are situations where we may want to record statistics at a different frequency than the solution, e.g., statistics at every time steps and solution at every cycle. That makes me think statistics should be logged in a separate file. I think the main question I have is: Should we use CSV, JSON, or some other format? Once we settle on that, I can plan out a schema and new phasor dynamics app options.
Rationale
It will helpful to have a unified interface so we can analyze and compare various time integration methods.
Description
No response
Additional information
Luke already made https://github.com/ORNL/GridKit/tree/lukel/ida-stats-helper to implement statistics logging for IDA in JSON format.
- Dominant language
- C++
- Stars
- 27
- Forks
- 11
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 15
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ORNL/GridKit
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ORNL/GridKit#587 · 1 reaction ·
Maintainers usually reply within 1 day
-
Companion OPF models for PD initialization constraintsPossibly taken @lukelowry claimed this 3 days ago. OpenIVP question
ORNL/GridKit#656 · 1 assignee ·
Maintainers usually reply within 1 day
-
Extract CommonMath functionsPossibly taken @amandeep25100-a11y claimed this 6 days ago. Opencleanup
Difficulty 4/5 3-5 days Newbie friendliness 54/100
ORNL/GridKit#642 · 1 comment ·
Maintainers usually reply within 1 day
-
Add support for hierarchical modeling to the JSON format case file specificationsPossibly taken @abirchfield claimed this 33 days ago. Opendocumentation enhancement new case question
ORNL/GridKit#619 · 8 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Separate Rosenbrock integrator interface to GridKit from the integrator implementation.May be free again @alexander-novo claimed this 33 days ago, and no pull request is open. Openenhancement new solver
ORNL/GridKit#618 · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
useless statementOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
grizzlypeak3d/DJV#962 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day