RDCH to BAT_*
Does anyone know of clever way to convert an idv like:
RDCH
1
111,BUS_INFO
222,BUS_INFO
0
111,LOAD_INFO
Q
into something like:
BAT_BUS_DATA,111,BUS_INFO
BAT_BUS_DATA,111,BUS_INFO
BAT_LOAD_DATA_3,111,LOAD_INFO
Does anyone know of clever way to convert an idv like:
RDCH
1
111,BUS_INFO
222,BUS_INFO
0
111,LOAD_INFO
Q
into something like:
BAT_BUS_DATA,111,BUS_INFO
BAT_BUS_DATA,111,BUS_INFO
BAT_LOAD_DATA_3,111,LOAD_INFO
By far the cleverest would be if recording would work, but it doesn't. And the LOAD_INFO format is subtly different between RDCH and BATCH commands
I, ID, STATUS, AREA, ZONE, PL, QL, IP, IQ, YP, YQ, OWNER, SCALE
versus
# owner and scale are part of the INTGAR values, not at the end.
BAT_LOAD_DATA_3 I 'ID' INTGAR(1)...INTGAR(5) REALAR(1)...REALAR(6)
That would make writing a parser for this decidedly not clever looking and rather tedious.
I'm curious, how did you end up doing it?
whit loves you. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
Along these lines - it would be useful to have some kind of converter which takes specific contingencies from a CON file and creates IDEVs for more detailed analysis. I made a script which does this (not very robust) but does anyone have a "clever" solution for this (rather than recording)?
H @cajief, so your IDEV would apply the contingency as batch commands?
Yeah that's the idea. IDEV or Python, just something so that you can easily investigate contingencies of interest in isolation. Some CON files I've used have up to the max number of elements (18 I think) per contingency and it's a PITA to disable each element, especially for N-1-1.
It would be great to have. The solution would be similar to jsexauer's though. Writing a parser for a CON file would also be a pain.