Skip to content

Dynamic Data Records

This page is the reference for the record syntax of the dynamic data file: which records exist, what their fields mean, and how a model name is resolved. The models themselves (names, parameters, equations) are documented in the Model Reference, one page per family.

Every device record names a model. RAMSES adds the family prefix automatically, so both forms resolve to the same model:

RecordPrefix addedExample, equivalent forms
EXCexc_AC1A, exc_AC1A
TORtor_HYGOV, tor_HYGOV
INJECinj_GFOL, inj_GFOL
TWOPtwop_HVDC_LCC, twop_HVDC_LCC
DCTLnoneLTC

Model names are case sensitive. A name that is compiled into RAMSES but not registered in the dispatcher is rejected at load time; see User-Defined Models for how to register one through URAMSES. The Model Reference index marks which models are callable out of the box and which are not.

The SYNC_MACH, INJEC and IMPLOAD records all begin with the same four initialization fields, which set the device’s share of the bus injection computed by the power flow:

FieldDescriptionUnit
FPFraction of the bus active injection taken by this device-
FQFraction of the bus reactive injection taken by this device-
PInitial active power, used when FP is zeroMW
QInitial reactive power, used when FQ is zeroMvar

P and Q are physical powers in MW and Mvar; RAMSES divides them by the system base to obtain per unit. See Reference Frames & Initialization for how these values feed the initialization.

A synchronous machine is specified with its excitation controller (EXC) and torque controller (TOR):

SYNC_MACH Name BUS_NAME FP FQ P Q Snom Pnom H D ibratio
XT/RL Xl Xd X'd X"d Xq X'q X"q m n Ra T'do T"do T'qo T"qo
EXC EXC_TYPE parameters_passed_to_EXC
TOR TOR_TYPE parameters_passed_to_TOR ;

For the complete mathematical model, the per unit system, and the parameter list, see the Synchronous Machine Model page.

The parameters_passed_to_EXC and parameters_passed_to_TOR fields are the model’s data parameters, in the order the model declares them. That order is authoritative per model:

An injector is a component connected to a single AC bus:

INJEC INJ_TYPE NAME BUS_NAME FP FQ P Q parameters_passed_to_INJ ;

The trailing fields are the model’s data parameters in declaration order. For the catalogue of injector models and their parameters, see Injector Models.

Two injectors are worth noting here because they affect the whole simulation rather than one bus:

  • THEVEQ imposes a constant-frequency voltage source and forces the synchronous reference frame. Its single data parameter is the three-phase short-circuit power of the equivalent network, in MVA, which RAMSES converts to the Thévenin reactance at initialization. See Thévenin Equivalent.
  • VFAULT is added automatically by RAMSES to apply voltage faults; you do not write it yourself.

IMPLOAD is a record in its own right, not an INJEC model, and takes no model parameters:

IMPLOAD loadname BUS_NAME FP FQ P Q ;

A constant-impedance load holds its admittance fixed at the value implied by the initial voltage, so its power varies with the square of the bus voltage. The record has exactly six fields; the FP/FQ/P/Q group behaves as described in Common Injection Fields.

Any bus injection left unclaimed after all INJEC and IMPLOAD records are processed is converted into an impedance load automatically, named with an M_ prefix. Only residuals whose current magnitude exceeds $NETTOL are converted, so a bus that balances exactly gains no extra load.

Two-port components connect two buses, and carry an independent injection group for each end:

TWOP MODEL_NAME TWOP_NAME BUS1 BUS2 IND FP1 FQ1 P1 Q1 FP2 FQ2 P2 Q2 DATA1 DATA2 ... ;
FieldDescription
MODEL_NAMETwo-port model name, with or without the twop_ prefix
TWOP_NAMEName of this device
BUS1, BUS2Names of the two connected buses
INDConnection indicator
FP1Q1Injection group for end 1, as in Common Injection Fields
FP2Q2Injection group for end 2
DATA1 DATA2 …Model data parameters, in declaration order

For the available models and their parameters, see Two-Port Models.

Discrete controllers act on the system at discrete instants rather than through differential equations:

DCTL CTRL_TYPE CTLNAME parameters ;

DCTL takes no prefix and the names are uppercase. For the catalogue, the field lists, and the switching logic of each controller, see Discrete Controller Models.