editorial

README.md

@@ -151,7 +151,9 @@ Data processing for this dataset consists exclusively of post-simulation wrangli
 
 The Python API for the RMS simulation models in MATLAB Simulink writes five signal files directly to disk in CSV format at the end of each simulation run: voltage magnitude in d-q axis (Vd and Vq in kV), current (id and iq in kA), powers (P in MW, Q in kvar), and voltage angle (in radians). These files are sampled at 1 ms resolution, yielding approximately 6,501 rows per file for a 6.5-second simulation. No conversion step is required, as MATLAB writes these directly in the target format. The decision to write CSVs directly from Simulink was made to minimize pipeline wrangling and reduce the risk of conversion errors. The Python API for PSCAD writes recorded signals in COMTRADE format first, and a dedicated Python conversion script converts these files to the same 5-CSV structure as the MATLAB outputs. For each simulation run in both MATLAB and PSCAD, Python scripts assemble one scenario descriptor files, recording the initial conditions and the disturbance information. This files are generated directly from the Python scenario-sampling scripts and written alongside the simulation outputs, ensuring that every scenario folder is self-describing. Note that users working with paired EMT/RMS data must account for this resolution difference explicitly, which is the primary intended use case of this dataset.
 
-No labels were created prior to simulation or by external human annotators. Annotation is fully automated and embedded within the simulation models. The dataset contains 3,000 scenarios, each identified by a four-digit, zero-padded index. There are 1600 scenarios simulated for the GFM control mode, named xxxx_M where xxxx is in [0001, 1600], and 1400 scenarios simulated for the GFL control mode, named xxxx_L where xxxx is in [0001, 1400]. Each control mode scenario contributes one metadata file and 2 signal CSV files (one from the EMT simulation and one from the RMS phasor-domain simulation). The signal file follow the naming convention xxxx__[M|L]_[EMT|RMS].csv, where where the EMT or RMS denotes the simulation domain. The metadata file follows the naming convention xxxx__[M|L]_meta_data.csv. The metadata and signal files contain the following information:
+No labels were created prior to simulation or by external human annotators. Annotation is fully automated and embedded within the simulation models. The dataset contains 3,000 scenarios, each identified by a four-digit, zero-padded index. There are 1600 scenarios simulated for the GFM control mode, named xxxx_M where xxxx is in [0001, 1600], and 1400 scenarios simulated for the GFL control mode, named xxxx_L where xxxx is in [0001, 1400]. Each control mode scenario contributes one metadata file and 2 signal CSV files (one from the EMT simulation and one from the RMS phasor-domain simulation). The signal file follow the naming convention xxxx_[M|L]_[EMT|RMS].csv, where where the EMT or RMS denotes the simulation domain. 
+
+The metadata file follows the naming convention xxxx_[M|L]_meta_data.csv. The metadata and signal files contain the following information:
 
 - xxxx_[M|L]_meta_data.csv: located in ./metadata, these files provide information needed to reconstruct or verify the simulation conditions for any scenario, and serve as the primary scenario-level annotation for downstream tasks. It is the authoritative annotation of each scenario's initial and disturbance conditions and records 16 rows, as follows:
   - Pref: float, active power reference (per unit)