Open nickrobinson251 opened 2 years ago
compared to v33:
DGENP, DGENQ, DGENF
Union{Float64,Missing}
columnsNREG
Union{Float64,Missing}
columnName
+ 12 Rate
columns rather than 3 + new mid-row column Met
I, J, CKT, R, X, B, ---- RATE_A, RATE_B, RATE_C, GI, BI, GJ, BJ, ST, ----- LEN, O1, F1, O2, F2, O3, F3, O4, F4
I, J, CKT, R, X, B, NAME, RATE_1, ..., RATE_12, GI, BI, GJ, BJ, STAT, MET, LEN, O1, F1, O2, F2, O3, F3, O4, F4
Branches34
typeZCOD
NOD1/2/3
NDR
/NDI
(also different column names? ANMXR,ANMNR
were ALFMX, ALFMN
, and ANMXI,ANMNI
were GAMMX, GAMMN
)Union{Int,Missing}
column NREG1
/NREG2
VSCDCLine34
type?F
columns have double / been split into Re
/Im
?
NREG
Union{Float64,Missing}
columnI don't know what any of these new columns mean, since i've no documentation just some example files...
NREG
maybe (at a complete guess) could be "non-regulating" (i.e. fixed output generators), in which case we'd expect this to be binary 0
/1
(so we can use Bool
). Might be worth checking if there's any other values in the NREG
columns of the v34 files i have.MET
(Branches` maybe means "metered"NDR
/NDI
i've no idea (the suffizx R
is for "Rectifier", and I
is for "Inverter")DGENP, DGENQ, DGENF
(Loads), ZCOD
(Transformers): generally COD
means "code" which means enum i.e. 0, 1, 2, ..., N different modes, so we could check out is there integer (rather than just binary)... but i've no idea what the codes would mean. And per-bus NOD
(Transformers) ... no idea (are they ever non-zero in the data we have?)comment rows, like @! I,'ID',STAT,AREA,ZONE, ...
, can be ignored by Parsers.Options(comment="@!")
https://github.com/JuliaData/Parsers.jl/blob/e75d67e78b8e702f2d7e8ab1cc94e50cbe134b5c/src/Parsers.jl#L54
Since we support v33, i'm hopeful a lot can be reused to add support for v34... and I do have an example v34 file now, but not the v34 manual/specification
Fortunately, the v34 file i have seems to contain comments at the start of each section
@!
Here's how the v34 file looks (with data itself removed):