Format for logging solver statistics

Open
#624 2 comments 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
cpp
Domain
backend, data

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

enhancement question
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

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ORNL/GridKit

All issues in ORNL/GridKit

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.