{
"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
}
]
}
Summary
Ability to make a monitor in the
*.solver.jsonand collect component monitor data based on some regular expressionRationale
Having the monitors defined in the
*.case.jsonis 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
Additional information
@PhilipFackler I liked your vision for this