Multiple Monitor Sinks + Remove monitor field from case
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by locating the code that reads monitors from *.case.json and the solver configuration parser. Use the example monitors array in the issue to trace how component data is selected and written to separate files, then verify that the case-level monitor field is no longer required.
Written by the indexing model from the issue text.
Description
Summary
Ability to make a monitor in the *.solver.json and collect component monitor data based on some regular expression
Rationale
Having the monitors defined in the *.case.json is not intuitive and really difficult to use. Having a wildcard/regex in the .solver.json and beign able to colelct output into different files is what we need.
Description
{
"system_model_file": "../../../../cases/PhasorDynamics/wecc.case.json",
"dt_monitor": 0.004166666666666667,
"tmax": 10.0,
"events": [
{ "time": 1.0, "type": "fault_on", "element_id": 0 },
{ "time": 1.15, "type": "fault_off", "element_id": 0 }
],
"monitors": [
{
"file_name": "wecc.omega.csv",
"include": "Genrou_*_omega",
"reference_file": "wecc.omega.ref.csv",
"error_type": "relative",
"error_tolerance": 1e-2,
"abs_err_threshold": 1e-6
},
{
"file_name": "wecc.vmag.csv",
"include": "Bus_*_Vm",
"reference_file": "wecc.vmag.ref.csv",
"error_type": "relative",
"error_tolerance": 1e-2,
"abs_err_threshold": 1e-6
},
{
"file_name": "wecc.p.csv",
"include": "Genrou_*_p",
"reference_file": "wecc.p.ref.csv",
"error_type": "relative",
"error_tolerance": 1e-2,
"abs_err_threshold": 1e-6
},
{
"file_name": "wecc.q.csv",
"include": "Genrou_*_q",
"reference_file": "wecc.q.ref.csv",
"error_type": "relative",
"error_tolerance": 1e-2,
"abs_err_threshold": 1e-6
}
]
}
Additional information
@PhilipFackler I liked your vision for this
- 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
-
enhancement question
Difficulty 5/5 Over a week Newbie friendliness 30/100
ORNL/GridKit#624 · 2 comments · 2 reactions ·
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
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