Summary
Summary
From discussion with @pelesh @nkoukpaizan @lukelowry
Maybe we should make a new simple JSON file format for a study run. Something like:
{
"system_model": "ThreeBusBasic.json",
"dt": 0.00416666666666,
"tmax": 10,
"events": [
{"time": 1, "event_type": "fault_on", "element_id": 0},
{"time": 1.1, "event_type": "fault_off", "element_id": 0}
],
"output_file": "ThreeBus_six_cycle_fault_bus1.csv",
"reference": "ThreeBusBasic.ref.csv",
"error_tolerance": 1e-4
}
Then you send that file as a command line argument to gridkit.
Rationale
We have defined a JSON file format to configure a case study. It would be helpful to define another input file to specify simulation execution.
Description
No response
Additional information
No response
Summary
Summary
From discussion with @pelesh @nkoukpaizan @lukelowry
Maybe we should make a new simple JSON file format for a study run. Something like:
{ "system_model": "ThreeBusBasic.json", "dt": 0.00416666666666, "tmax": 10, "events": [ {"time": 1, "event_type": "fault_on", "element_id": 0}, {"time": 1.1, "event_type": "fault_off", "element_id": 0} ], "output_file": "ThreeBus_six_cycle_fault_bus1.csv", "reference": "ThreeBusBasic.ref.csv", "error_tolerance": 1e-4 }Then you send that file as a command line argument to gridkit.
Rationale
We have defined a JSON file format to configure a case study. It would be helpful to define another input file to specify simulation execution.
Description
No response
Additional information
No response