Warnings

'string' ('string':'integer') is triplex but doesn't have phases S set

• A triplex line has been used, but this triplex line does not have the phase S designated to indicate it contains single-phase components. Without this specified, you may get invalid results. See powerflow/triplex_line.cpp(76).

'string' ('string':'integer') parent 'string' ('string':'integer') does not export attach_enduse function so voltage response cannot be modeled

• Enduses must have a voltage source from a parent object that exports an attach_enduse function. The residential_enduse object references a parent object that does not conform with this requirement. Fix the parent reference and try again. See residential/residential_enduse.cpp(85).

'string' (auction:'integer') capacity_reference_property 'string' is not a double type property

• capacity_reference_property must specify a double property to work properly, and may behave unpredictably should it be pointed at non-double properties. See market/auction.cpp(347).

'string' (id:'integer') already has a link parented - this could give invalid answers in FBS!

• While connecting the different objects, a link's 'to' end already has another link as a parent. This is indicative of a loop or other 'non-radial' condition on the system. The exception to this is if an open switch is connected at that node. If it is not an open switch, Forward Backward-Sweep (FBS) will not give a proper solution in this condition. Even if it is an open switch, be aware that FBS could still give an invalid answer, depending on topological conditions. If it is an open switch, consider removing the open switch from your GLM to ensure proper answers. If it is another type of link or you do not wish to remove the open switch, consider using the Newton-Raphson (NR) solver instead. See powerflow/link.cpp(372).

'string' (id:'integer') is parented to a node, but has a link running into it!

• While connecting the different objects, a link's 'to' end already has a parent of another node. This may cause invalid answers on the system an an inaccurate powerflow. Please check the node's connection and adjust your system, if necessary. You may also consider using the Newton-Raphson solver (NR), which will not this issue. See powerflow/link.cpp(385).

'string' does not have a phase A to fault!

• A fault event was attempted on phase A of the link object. This object does not have a valid phase A to fault. See powerflow/link.cpp(5132).
• A fault event was attempted on phase A of the link object. This object does not have a valid phase A to fault. See powerflow/link.cpp(8020).

'string' does not have a phase B to fault!

• A fault event was attempted on phase B of the link object. This object does not have a valid phase B to fault. See powerflow/link.cpp(5161).
• A fault event was attempted on phase B of the link object. This object does not have a valid phase B to fault. See powerflow/link.cpp(8049).

'string' does not have a phase C to fault!

• A fault event was attempted on phase C of the link object. This object does not have a valid phase C to fault. See powerflow/link.cpp(5190).
• A fault event was attempted on phase C of the link object. This object does not have a valid phase C to fault. See powerflow/link.cpp(8078).

'string'('integer'): libraries not yet supported

• An attempt to use the library GLM directive was made. Library directives are not supported yet. See gldcore/load.c(4379).
• An attempt to parse a library GLM directive was made. Library directives are not supported yet. See gldcore/load.c(4789).

'string'('integer'): timezone 'string' is not defined

• The specified timezone is not defined in the timezone file .../etc/tzinfo.txt. Try using an known timezone, or add the desired timezone to the timezome file and try again. See gldcore/load.c(2454).

'string'('integer'): variable 'string' not found

• A macro refers to a variable that is not defined. Correct the variable reference, or define the variable before using it and try again. See gldcore/load.c(5889).

'string': controller price curve is not injective and may behave strangely

• The price curve 'changes directions' at the setpoint, which may create odd conditions in a number of circumstances. See market/controller.cpp(735).

'string': The transformer has reached its operational lifespan. Resetting transformer lifetime parameters.

• During the simulation, while using the transformer thermal aging model, the transformer reached the end of its life. It was assumed that the transformer was replaced with a new transformer of the same make, model, etc. to prevent failure of the simulation. All of the lifetime parameters are set to assume a "new" transformer. See powerflow/transformer.cpp(1211).

\'design_cooling_capacity\' not specified in parent ~ default to 5 ton or 60,000 Btu/hr

• The thermal_storage did not reference a parent object that publishes design_cooling_capacity, so 5 ton was assumed. Confirm or change the parent reference and try again. See residential/thermal_storage.cpp(214).

Afflicted object count went negative - using after fault count

• While determining the number of objects faulted by an event, a negative count was encountered. This indicates some objects magically restored themselves before the final count could be obtained. This may be a logic fault in the code, or the event generation logic. Pleas submit your code and a bug report using the trac website. See reliability/eventgen.cpp(920).

Afflicted secondary object count went negative - using after fault count

• While determining the number of objects secondarily faulted by an event, a negative count was encountered. This indicates some objects magically restored themselves before the final count could be obtained. This may be a logic fault in the code, or the event generation logic. Pleas submit your code and a bug report using the trac website. See reliability/eventgen.cpp(936).

All values in auction statistic calculations were skipped. Setting mean to zero.

• You may need to check your auction setup. At least two flags are used to skip values in the calculation of the statistics (ignore_pricecap & ignore_failedmarket). This error indicates that every value was skipped. This may be by design, but one should be aware of it. Note, standard deviation will also be set to zero after the initial statistics collection period. See market/auction.cpp(574).

Automatic controls can oscillate to the iteration limit with no time delays. To prevent this, ensure your switching limits are reasonable.

• With no time delays set (time_delay or dwell_time), the capacitor performs everything instantaneously. If the set points are too close together, the capacitor may oscillate until the convergence limit is reached. Avoid this for proper answers. See powerflow/capacitor.cpp(335).

Battery attempted to discharge too far!

• While attepting to initialize the battery, it encountered a negative or overloaded SOC condition. It has been arbitrarily set to 50%. See residential/evcharger_det.cpp(950).
• While attepting to initialize the battery, it encountered a negative or overloaded SOC condition. It has been arbitrarily set to 50%. See residential/evcharger_det.cpp(971).

Battery SOC calculation messed up and somehow went outsize 0 - 100 range!

• The initial battery SOC somehow ended up outside a 0 - 100% range. It has been forced to 50%. See residential/evcharger_det.cpp(930).

battery:'integer' 'string' - Deltamode is enabled for the module, but not this generator!

• The diesel_dg is not flagged for deltamode operations, yet deltamode simulations are enabled for the overall system. When deltamode triggers, this generator may no longer contribute to the system, until event-driven mode resumes. This could cause issues with the simulation. It is recommended all objects that support deltamode enable it. See generators/battery.cpp(272).

battery:'string' indicates it wants to run deltamode, but the module-level flag is not set!

• The diesel_dg object has the deltamode_inclusive flag set, but not the module-level enable_subsecond_models flag. The generator will not simulate any dynamics this way. See generators/battery.cpp(256).

bid_delay was less than the current minimum_timestep setting - rounded up to one whole timestep

• The time for bid_delay was less than the value set for minimum_timestep in the GLM. It was rounded to be at least one minimum_timestep in value. If this is not desired, fix your bid delay or minimum_timestep See market/generator_controller.cpp(472).

Capacitance calculation failure for 'string'

• While computing the capacitance, a zero-value denominator was encountered. Please check your underground_conductor parameter values and try again. See powerflow/underground_line.cpp(840).
• While computing the capacitance, a zero-value denominator was encountered. Please check your underground_conductor parameter values and try again. See powerflow/underground_line.cpp(966).

Capacitor 'string' has no pt_phase set, volt_var_control 'string' will pick the first phases_connected

• To properly operate capacitors from the volt_var_control object, a pt_phase property must be defined. One was missing, so the volt_var_control object assigned the first phase_connected value to pt_phase on that capacitor for proper operation. See powerflow/volt_var_control.cpp(1102).

Capacitor:'integer' - 'string' - the remote_sense object is a network_interface, node/link connections both enabled

• A capacitor has detected a network_interface object attached to the remote_sense object pointer. It will map this object to both the node and link options for remote telemetry. The capacitor operation method should specify the proper device to use, but this may have unintenteded consequences. See powerflow/capacitor.cpp(244).

Capacitor:'integer' does not have its upper voltage limit set.

• When under the VAR-VOLT control scheme, the voltage_set_high set point should be set to the upper voltage limit the capacitor will remain switched on for. See powerflow/capacitor.cpp(289).

Capacitor:'integer' does not have one or both of its current set points set.

• If the CURRENT control scheme is active, you must specify the current set points for the band of operation. Without these, the capacitor will not function and will effectively perform no action. See powerflow/capacitor.cpp(303).

Capacitor:'integer' does not have one or both of its VAr set points set.

• If VAR or VARVOLT control schemes are active, you must specify the reactive power set points for the band of operation. Without these, the capacitor will not function and will effectively perform no action. See powerflow/capacitor.cpp(296).

Capacitor:'integer' does not have one or both of its voltage set points set.

• If the VOLT control schemes is active, you must specify the voltage set points for the band of operation. Without these, the capacitor will not function and will effectively perform no action. See powerflow/capacitor.cpp(282).

Capacitor:'integer' has a secondary sensor specified, but is not in VARVOLT control. This will be ignored.

• The secondary remote sensor field is only used in the VAR-VOLT control scheme. When not under this control scheme, any inputs to this field are ignored. See powerflow/capacitor.cpp(225).

Capacitor:'integer' is set to manual bank mode, but does not know which phase to monitor.

• A capacitor is set to manual bank mode. However, pt_phase is empty and the capacitor does not know which phase to monitor to switch all conencted phases. Specify at least one phase in pt_phase to enable the bank control See powerflow/capacitor.cpp(356).

class_define_map(oclass='string',...): class 'string' does not assert UNSAFE_OVERRIDE_OMIT when parent class 'string' does

• A class is not asserting that it is unsafe to suppress synchronization behavior but its parent does assert that this is unsafe. This permits stealth omission by any classes that inherits behavior from this class and the warning is given in case this is not intended. See gldcore/class.c(722).

class_define_map(oclass='string',...): class 'string' suppresses parent class 'string' BOTTOMUP sync behavior by omitting override

• A class is suppressing the sync event implemented by its parent even though the parent is published with a flag that indicates this is unsafe. Presumably this is deliberate, but the warning is given just in case it's not intended. See gldcore/class.c(704).

class_define_map(oclass='string',...): class 'string' suppresses parent class 'string' POSTTOPDOWN sync behavior by omitting override

• A class is suppressing the postsync event implemented by its parent even though the parent is published with a flag that indicates this is unsafe. Presumably this is deliberate, but the warning is given just in case it's not intended. See gldcore/class.c(713).

class_define_map(oclass='string',...): class 'string' suppresses parent class 'string' PRETOPDOWN sync behavior by omitting override

• A class is suppressing the presync event implemented by its parent even though the parent is published with a flag that indicates this is unsafe. Presumably this is deliberate, but the warning is given just in case it's not intended. See gldcore/class.c(695).

class_find_property(CLASS *oclass='string', PROPERTYNAME name='string': property is deprecated

• You have done a search on a property that has been flagged as deprecated and will most likely not be supported soon. Correct the usage of this property to get rid of this message. See gldcore/class.c(202).

climate:'string' - Southern hemisphere solar position model may have issues

• The default solar position model was built around a northern hemisphere assumption. As such, it doesn't always produce completely accurate results for southern hemisphere locations. Calculated insolation values are approximately correct, but may show discrepancies against measured data. If this climate is associated with a solar object, use the SOLAR_TILT_MODEL SOLPOS to ensure proper results (this warning will still pop up). See climate/climate.cpp(763).

compare of strings using numeric op usually does not work

• An attempt to compare two numbers using a string comparison operation is not generally going to work as expected. Check that this is truly the desired comparison and correct it if not. If so and the warning error is not desired you may suppress warnings using #set warning=0 in the model file. See gldcore/find.c(139).

continuous_rating for link:'string' is zero - this may lead to odd warning messages about line limits with nonsense values

• The value for continuous_rating is set to zero for the particular link object. This may cause warnings related to line ratings that have nonsense values like '1.#J%'. To resolve these warnings, please put a valid number in for continuous_rating. Load order may also contribute to this problem. Ensure all configurations are first in the GLM files. See powerflow/link.cpp(539).

DC maximum power output is less than the real power output from the inverter. A higher DC power rating is recommended. Currently the VSI power output is not limited by the DC power output.

• DC maximum power output is less than the real power output from the inverter. Although currently inverter does not adjust its power output based on teh DC limitations. A higher DC power rating is recommended. See generators/inverter.cpp(3910).

debugger.conf was not found

• The debugger.conf was not found in the GLPATH environment path. This file is loaded when the debugger is enabled. Make sure that GLPATH includes the .../etc folder and try again. See gldcore/load.c(7210).

diesel_dg:'integer' 'string' - cannot set both Kd1 and Kd2 as 0 for the CVR conntrol! Have changed Kd2 to be 1

• The diesel_dg is not flagged for deltamode operations, yet deltamode simulations are enabled for the overall system. When deltamode triggers, this generator may no longer contribute to the system, until event-driven mode resumes. This could cause issues with the simulation. It is recommended all objects that support deltamode enable it. See generators/diesel_dg.cpp(1384).

diesel_dg:'integer' 'string' - Deltamode is enabled for the module, but not this generator!

• The diesel_dg is not flagged for deltamode operations, yet deltamode simulations are enabled for the overall system. When deltamode triggers, this generator may no longer contribute to the system, until event-driven mode resumes. This could cause issues with the simulation. It is recommended all objects that support deltamode enable it. See generators/controller_dg.cpp(280).

diesel_dg:'integer' 'string' - overload_limit has a value less than or equal to zero - set to 1.25

• The value for overload_limit in diesel_dg must be greater than zero. If it is not, it will be arbitrarily set to 1.25. Explicitly set this value, if this is not intended. See generators/diesel_dg.cpp(959).

diesel_dg:'integer' - 'string' has no parent object - default voltages being used

• The diesel_dg object does not have a proper parent -- default voltage values are used. See generators/diesel_dg.cpp(829).

diesel_dg:'string' - power_out_A is above 1/3 the total rating, capping

• The diesel_dg object has a power_out_A value that is above 1/3 the total rating. It will be thresholded to that level. See generators/diesel_dg.cpp(875).
• The diesel_dg object has a power_out_A value that is above 1/3 the total rating. It will be thresholded to that level. See generators/diesel_dg.cpp(1089).

diesel_dg:'string' - power_out_A is zero - arbitrarily setting to 50%%

• The diesel_dg object has a power_out_A value that is zero. This can cause the generator to never partake in the powerflow. It is being arbitrarily set to 50% of the per-phase rating. If this is undesired, please change the value. See generators/diesel_dg.cpp(1144).

diesel_dg:'string' - power_out_B is above 1/3 the total rating, capping

• The diesel_dg object has a power_out_B value that is above 1/3 the total rating. It will be thresholded to that level. See generators/diesel_dg.cpp(893).
• The diesel_dg object has a power_out_B value that is above 1/3 the total rating. It will be thresholded to that level. See generators/diesel_dg.cpp(1107).

diesel_dg:'string' - power_out_B is zero - arbitrarily setting to 50%%

• The diesel_dg object has a power_out_B value that is zero. This can cause the generator to never partake in the powerflow. It is being arbitrarily set to 50% of the per-phase rating. If this is undesired, please change the value. See generators/diesel_dg.cpp(1156).

diesel_dg:'string' - power_out_C is above 1/3 the total rating, capping

• The diesel_dg object has a power_out_C value that is above 1/3 the total rating. It will be thresholded to that level. See generators/diesel_dg.cpp(911).
• The diesel_dg object has a power_out_C value that is above 1/3 the total rating. It will be thresholded to that level. See generators/diesel_dg.cpp(1125).

diesel_dg:'string' - power_out_C is zero - arbitrarily setting to 50%%

• The diesel_dg object has a power_out_C value that is zero. This can cause the generator to never partake in the powerflow. It is being arbitrarily set to 50% of the per-phase rating. If this is undesired, please change the value. See generators/diesel_dg.cpp(1168).

diesel_dg:'string' - rotor_speed_convergence is less than zero - negating

• The value specified for deltamode convergence, rotor_speed_convergence, is a negative value. It has been made positive. See generators/diesel_dg.cpp(1183).

diesel_dg:'string' - rotor_speed_convergence is zero - it may never exit deltamode!

• A zero value has been specified as the deltamode convergence criterion for rotor speed. This is an incredibly tight tolerance and may result in the system never converging and exiting deltamode. See generators/diesel_dg.cpp(1193).

diesel_dg:'string' - voltage convergence is enabled, but no exciter is present

• While performing simple checks on the voltage convergence criterion, no exciter is turned on. This convergence check does nothing in this situation -- it requires an exciter to function See generators/diesel_dg.cpp(1249).

diesel_dg:'string' - voltage_convergence is less than zero - negating

• The value specified for deltamode convergence, voltage_convergence, is a negative value. It has been made positive. See generators/diesel_dg.cpp(1259).

diesel_dg:'string' - voltage_convergence is zero - it may never exit deltamode!

• A zero value has been specified as the deltamode convergence criterion for voltage magnitude. This is an incredibly tight tolerance and may result in the system never converging and exiting deltamode. See generators/diesel_dg.cpp(1269).

diesel_dg:'string' did not have a valid Rated_V set, assuming 15 kV

• The Rated_V property was not set or was invalid. It is being forced to 15 kV, which aligns with the base for all default parameters. This will be checked again later to see if it matches the connecting point. If this value is not desired, please set it manually. See generators/diesel_dg.cpp(974).

diesel_dg:'string' did not have a valid Rated_VA set, assuming 10 MVA

• The Rated_VA value was not set or was set to a negative number. It is being forced to 10 MVA, which is the machine base for all of the other default parameter values. See generators/diesel_dg.cpp(945).

diesel_dg:'string' did not have a valid Rated_VA set, assuming 5000 kVA

• The Rated_VA value was not set or was set to a negative number. It is being forced to 5000 kVA, which is the machine base for all of the other default parameter values. See generators/diesel_dg.cpp(862).

diesel_dg:'string' forced into DYN_SYNCHRONOUS mode

• The diesel_dg object had the deltamode_inclusive flag set, but was not of the DYN_SYNCHRONOUS type. It has been forced to this type. If this is not desired, please remove the deltamode_inclusive flag or explicitly set it to false. See generators/diesel_dg.cpp(847).

diesel_dg:'string' indicates it wants to run deltamode, but the module-level flag is not set!

• The diesel_dg object has the deltamode_inclusive flag set, but not the module-level enable_subsecond_models flag. The generator will not simulate any dynamics this way. See generators/controller_dg.cpp(255).
• The diesel_dg object has the deltamode_inclusive flag set, but not the module-level enable_subsecond_models flag. The generator will not simulate any dynamics this way. See generators/diesel_dg.cpp(1306).

Efficiency unspecified - defaulted to 'real' for this inverter type

• An inverter_efficiency value was not explicitly specified for this inverter. A default value was specified in its place. If the default value is not acceptable, please explicitly set inverter_efficiency in the GLM file. See generators/inverter.cpp(1135).

emergency_rating for link:'string' is zero - this may lead to odd warning messages about line limits with nonsense values

• The value for emergency_rating is set to zero for the particular link object. This may cause warnings related to line ratings that have nonsense values like '1.#J%'. To resolve these warnings, please put a valid number in for emergency_rating. Load order may also contribute to this problem. Ensure all configurations are first in the GLM files. See powerflow/link.cpp(549).

Empty powerflow connectivity matrix for island 'integer', your system is empty!

• Newton-Raphson has an empty admittance matrix that it is trying to solve. Either the whole system faulted, or something is not properly defined. Please try again. If the problem persists, please submit your code and a bug report via the trac website. See powerflow/solver_nr.cpp(3255).

Empty powerflow connectivity matrix, your system is empty!

• Newton-Raphson has an empty admittance matrix that it is trying to solve. Either the whole system faulted, or something is not properly defined. Please try again. If the problem persists, please submit your code and a bug report via the trac website. See powerflow/solver_nr.cpp(3264).

evcharger_det:'string' - the breaker rating may be too low for this maximum charge rate.

• The evcharger_det maximum_charge_rate and configuration calculated a maximum breaker current that may be above the current setting. This may cause the breaker to trip and affect simulation results. If this is undesired, set the breaker_amps property to a higher value. See residential/evcharger_det.cpp(196).

evcharger_det:'string' - The max charge rate is over 1.7 kW (Level 1), but the load is still 110-V connected.

• The evcharger_det maximum_charge_rate implies a level 2 or higher charge rate, but it still set up to be connected as a normal level 1 110/120 VAC device. This may cause issues with circuit breakers tripping. If this is undesired, be sure to specify the proper configuration property. See residential/evcharger_det.cpp(174).

event_gen:'string' does not have a metrics object as a parent -- metrics are not calculated.

• The event_gen object needs to be parented to a metrics object to ensure reliability metrics are being properly computed. Please ensure the parent of this event_gen object is specified, and is a metrics object if reliability metrics are desired. See reliability/eventgen.cpp(256).

event_gen:'string' has the ability to generate more than 1 simultaneous fault - metrics may not be accurate

• The event_gen object has the ability to induce simultaneous and concurrent fault conditions. This may affect the accuracy of your reliability metrics. See reliability/eventgen.cpp(658).

eventgen:'string' - minimum_timestep set - all events at least 1 minimum step long

• A minimum timestep value is set in the file. Reliability works not-so-well when the events are starting and stopping less than this value. All events are therefore going to be set to be at least 1 minimum timestep long. This may alter your results, so please plan appropriately. See reliability/eventgen.cpp(191).

eventgen:'string' indicates it wants to run deltamode, but the module-level flag is not set!

• The eventgen object has the deltamode_inclusive flag set, but not the module-level enable_subsecond_models flag. The event will not simulate any dynamics this way. See reliability/eventgen.cpp(681).

Eventgen:'string' is flagged for deltamode, but reliability deltamode is not enabled

• The deltamode flag was set for the particular eventgen object, but the enabled_subsecond_models flag for the entire reliability module is not set. Deltamode support is not enabled. If this is not desired, be sure to set the module-level variable enabled_subsecond_models to true and try again. See reliability/eventgen.cpp(221).

explicit 'string' model is experimental

• The clothes washer explicit model has some serious issues and should be considered for complete removal. It is highly suggested that this model NOT be used. See residential/clotheswasher.cpp(155).
• The refrigerator explicit model has some serious issues and should be considered for complete removal. It is highly suggested that this model NOT be used. See residential/refrigerator.cpp(151).

explicit 'string' model is experimental and has not been validated

• The dishwasher explicit model has some serious issues and should be considered for complete removal. It is highly suggested that this model NOT be used. See residential/dishwasher.cpp(178).

Failure to load solver_'string' as a library, defaulting to superLU

• While attempting to load the DLL for an external LU solver, the file did not appear to meet the libary specifications. superLU is being used instead. Please check the library file and try again. See powerflow/node.cpp(805).

Failure to map deltamode function for device:'string'

• Attempts to map up the interupdate function of a specific device failed. Please try again and ensure the object supports deltamode. The object simply may not support delta mode. If the error persists, please submit your code and a bug report via the trac website. See powerflow/link.cpp(2680).
• Attempts to map up the interupdate function of a specific device failed. Please try again and ensure the object supports deltamode. This error may simply be an indication that the object of interest does not support deltamode. If the error persists and the object does, please submit your code and a bug report via the trac website. See powerflow/node.cpp(1785).

Failure to map deltamode saturation function for device:'string'

• Attempts to map up the saturation function of a specific device (transformer) failed. Please try again. If the error persists, please submit your code and a bug report via the ticking website. See powerflow/link.cpp(2703).

Failure to map VFD current injection update for device:'string'

• Attempts to map a function for the proper VFD updates did not work. Please try again, making sure this node is connected to a VFD properly. If the error persists, please submit an issue ticket. See powerflow/node.cpp(5243).

fault_check interaction with restoration requires meshed checking mode - enabling this now

• The restoration algorithm is improved by using the meshed mode of topology checking for faults. This has been automatically enabled for the object. If this is undesired, do not use fault_check with restoration. See powerflow/fault_check.cpp(234).

fault_check:'string' was forced into meshed search mode due to multiple grids being desired

• While starting up a fault_check object, the grid_association flag was set. This flag requires the meshed topology checking routines to be active, so that capability was enabled. If this is undesired, please deactivate grid_association capability. See powerflow/fault_check.cpp(145).

file 'string' ignored in test mode

• This warning is caused by an attempt to read an input file in self-test mode. The use of self-test model precludes reading model files. Try running the system in normal more or leaving off the model file name. See gldcore/cmdarg.c(1442).

Fuse status updated, but no other changes made.

• When changed under solver methods other than NR, only the fuse status is changed. The solver handles other details in a specific step, so no other changes are performed. See powerflow/fuse.cpp(859).

Fuse:'string' fuse_resistance has been set to zero. This will result singular matrix. Setting to the global default.

• Under Newton-Raphson solution method the impedance matrix cannot be a singular matrix for the inversion process. Change the value of fuse_resistance to something small but larger that zero. See powerflow/fuse.cpp(192).

Fuse:'string' has a negative or 0 mean replacement time - defaulting to 1 hour

• A fuse has a negative or zero time specified for mean_replacement_time. The value has therefore been overridden to 1 hour. If this is unacceptable, please change the value in your GLM file. See powerflow/fuse.cpp(168).

fuse:'string' has a zero current limit - set to 9999.9 Amps

• A fuse somehow had a current limit of 0.0 Amps set. This is invalid, so a placeholder value of 9999.0 Amps is used. Please adjust this value accordingly. See powerflow/fuse.cpp(159).

Fuses only work for the attached node in the FBS solver, not any deeper.

• Under the Forward-Back sweep method, fuses can only affect their directly attached downstream node. Due to the nature of the FBS algorithm, nodes further downstream (especially constant current loads) will cause an oscillatory nature in the voltage and current injections, so they will no longer be accurate. Either ignore these values or figure out a way to work around this limitation (player objects). See powerflow/fuse.cpp(181).

generator_controller:'string' entered an unexpected state - results may be invalid!

• While determining the output state for the generator, an unexpected condition was encountered (it was turned on when it expected to be off, or vice-versa). This means all subsequent bids are suspect or incorrect. Please ensure nothing has changed cleared markets before the latency period expired. If this message persists, please submit your code and a bug report via the trac website. See market/generator_controller.cpp(1306).

Generator_rating and bid_generator_rating both have values in generator_controller:'string'

• Both the generator_rating and bid_generator_rating have non-zero values at the start of the simulation. bid_generator_rating will eventually override generator_rating, so please ensure your values are entered appropriately. See market/generator_controller.cpp(337).

global_create(char *name='string',...): property 'string' unit 'string' is not recognized

• The property definition uses a unit that is not found. Check the unit and try again. If you wish to define a new unit, try adding it to .../etc/unitfile.txt. See gldcore/globals.c(459).

gridlabd.conf was not found

• The gridlabd.conf was not found in the GLPATH environment path. This file is always loaded before a GLM file is loaded. Make sure that GLPATH includes the .../etc folder and try again. See gldcore/load.c(7191).

group_recorder::init(): no filename defined, auto-generating 'string'

• group_recorder requires a filename. If none is provided, a filename will be generated using a combination of the classname and the core-assigned ID number. See tape/group_recorder.cpp(85).

group_recorder::init(): unable to open file 'string' for writing

• If the group_recorder cannot open the specified output file, it will See tape/group_recorder.cpp(144).

house_e:'integer' 'string' - Deltamode is enabled for the module, but not this house!

• The house is not flagged for deltamode operations, yet deltamode simulations are enabled for the overall system. When deltamode triggers, this house may no longer contribute to the system, until event-driven mode resumes. This could cause issues with the simulation. It is recommended all objects that support deltamode enable it. See residential/house_e.cpp(1746).

house_e:'string' indicates it wants to run deltamode, but the module-level flag is not set!

• The house_e object has the deltamode_inclusive flag set, but not the module-level enable_subsecond_models flag. The house will not simulate any dynamics this way. See residential/house_e.cpp(1728).

impedance1 was defined, but impedance2 was not -- assuming they are equal

• One of the secondary side impedances (impedance1 or impedance2, or resistance1 and reactance1) was set to a non-zero value, indicating you wanted to use the secondary impedances, however, the other value was not also set. If you do not want to use the assumption that they are the same, please set the other impedance value. See powerflow/transformer_configuration.cpp(270).

impedance2 was defined, but impedance1 was not -- assuming they are equal

• One of the secondary side impedances (impedance1 or impedance2, or resistance1 and reactance1) was set to a non-zero value, indicating you wanted to use the secondary impedances, however, the other value was not also set. If you do not want to use the assumption that they are the same, please set the other impedance value. See powerflow/transformer_configuration.cpp(260).

Infinite reconfiguration iterations set.

• The restoration object can have the number of iterations powerflow can perform before trying another reconfiguration set. This is set via teh reconfig_iteration_limit property. If not set, or set to 0, the system will perform iterations on this reconfiguration until the overall powerflow iteration limit is reached, or the system solves and moves to a new reconfiguration. See powerflow/restoration.cpp(250).

Init() triplex_node (name:'string', id:'integer'): Phases specified did not include phase S. Adding phase S.

• Triplex nodes and meters require a single phase and a phase S component (for split-phase). This particular triplex object did not include it, so it is being added. See powerflow/triplex_node.cpp(181).

init(): Rated_kVA or {area or rated insolation or effiency} were not specified or specified as zero. Leads to maximum power output of 0.

• The relationship between power output and other physical variables is described by Rated_kVA = Rated_Insolation * efficiency * area. Since Rated_kVA was not specified and this equation leads to a value of zero, the output of the model is likely to be no power at all times. See generators/solar.cpp(601).

init(): Rated_kVA, efficiency, Rate_Insolation, and area did not calculated to the same value. Ignoring Rated_kVA.

• The relationship between power output and other physical variables is described by Rated_kVA = Rated_Insolation * efficiency * area. However, the model can be overspecified. In the case that it is, we have defaulted to old versions of GridLAB-D and ignored the Rated_kVA and re-calculated it using the other values. If you would like to use Rated_kVA, please only specify Rated_Insolation and Rated_kVA. See generators/solar.cpp(614).

init: object 'string':'integer' should have a name, but doesn't

• The object indicated has been flagged by the module which implements its class as one which must be named to work properly. Please provide the object with a name and try again. See gldcore/exec.c(603).
• The object indicated has been flagged by the module which implements its class as one which must be named to work properly. Please provide the object with a name and try again. See gldcore/exec.c(814).

INIT: overhead_line:'string' has a negative resistance in it's impedance matrix. This will result in unusual behavior. Please check the line's geometry and cable parameters.

• A negative resistance value was found for one or more the real parts of the overhead_line's impedance matrix. While this is numerically possible, it is a physical impossibility. This resulted most likely from a improperly defined conductor cable. Please check and modify the conductor objects used for this line to correct this issue. See powerflow/overhead_line.cpp(832).

INIT: triplex_line:'string' has a negative resistance in it's impedance matrix. This will result in unusual behavior. Please check the line's geometry and cable parameters.

• A negative resistance value was found for one or more the real parts of the triplex_line's impedance matrix. While this is numerically possible, it is a physical impossibility. This resulted most likely from a improperly defined conductor cable. Please check and modify the conductor objects used for this line to correct this issue. See powerflow/triplex_line.cpp(440).

INIT: underground_line:'string' has a negative resistance in it's impedance matrix. This will result in unusual behavior. Please check the line's geometry and cable parameters.

• A negative resistance value was found for one or more the real parts of the underground_line's impedance matrix. While this is numerically possible, it is a physical impossibility. This resulted most likely from a improperly defined conductor cable. Please check and modify the conductor objects used for this line to correct this issue. See powerflow/underground_line.cpp(1124).

Invalid derating factor specified, defaulting to 95%%

• A derating factor less than zero or greater than 1.0 was specified. This is not within the valid range, so a default of 0.95 was selected. See generators/solar.cpp(880).

Invalid soiling factor specified, defaulting to 95%%

• A soiling factor less than zero or greater than 1.0 was specified. This is not within the valid range, so a default of 0.95 was selected. See generators/solar.cpp(870).

inverter:'integer' 'string' - Deltamode is enabled for the module, but not this inverter!

• The inverter is not flagged for deltamode operations, yet deltamode simulations are enabled for the overall system. When deltamode triggers, this inverter may no longer contribute to the system, until event-driven mode resumes. This could cause issues with the simulation. It is recommended all objects that support deltamode enable it. See generators/inverter.cpp(1898).

Inverter:'integer' 'string' does not have a valid parent - 1547 checks have been disabled

• The IEEE 1547-2003 checks for interconnection require a valid powerflow parent. One was not detected, so this functionality has been detected. See generators/inverter.cpp(7875).

Inverter:'integer' has no parent meter object defined; using static voltages

• An inverter in the system does not have a parent attached. It is using static values for the voltage. See generators/inverter.cpp(1045).

inverter:'integer'-'string' - IEEE 1547 checks are enabled, but the model is not deltamode-enabled

• The IEEE 1547 checks have been enabled for the inverter object, but deltamode is not enabled. This will severely hinder the inverter's ability to do these checks, and really isn't the intended mode of operation. See generators/inverter.cpp(1921).

inverter:'string' - a short pf_reg_activate_lockout_time may lead to inverter controller oscillations. Recommended time: > 60s

• The pf_reg_activate_lockout_time for the inverter is negative. Negative lockout times are not allowed inside the inverter. Please correct the value and try again. See generators/inverter.cpp(1436).

inverter:'string' - battery at or below the SOC reserve - no discharging allowed

• In LOAD_FOLLOWING mode, a empty or "in the SOC reserve margin" battery was encountered and attempted to discharge. The inverter is unable to extract any further power, so the output is set to zero. See generators/inverter.cpp(3555).

inverter:'string' - battery full - no charging allowed

• In LOAD_FOLLOWING mode, a full battery status was encountered. The inverter is unable to sink any further energy, so consumption was set to zero. See generators/inverter.cpp(3546).

inverter:'string' - charge_lockout_time is zero, oscillations may occur

• The value for charge_lockout_time is zero, which means there is no delay in new dispatch operations. This may result in excessive switching and iteration limits being hit. If this is not desired, specify a charge_lockout_time larger than zero. See generators/inverter.cpp(1467).

inverter:'string' - charge_on_threshold and charge_off_threshold are equal - may not behave properly!

• For proper LOAD_FOLLOWING operation, charge_on_threshold and charge_off_threshold should specify a deadband for operation. If equal, the inverter may not operate properly and the system may never solve properly. See generators/inverter.cpp(2144).

inverter:'string' - discharge_lockout_time is zero, oscillations may occur

• The value for discharge_lockout_time is zero, which means there is no delay in new dispatch operations. This may result in excessive switching and iteration limits being hit. If this is not desired, specify a discharge_lockout_time larger than zero. See generators/inverter.cpp(1487).

inverter:'string' - discharge_off_threshold should be larger than the charge_off_threshold

• For proper LOAD_FOLLOWING operation, the deadband for the inverter should not overlap. Please specify a larger range for the discharge and charge bands of operation and try again. If the bands do overlap, unexpected behavior may occur. See generators/inverter.cpp(2172).

inverter:'string' - discharge_on_threshold and discharge_off_threshold are equal - may not behave properly!

• For proper LOAD_FOLLOWING operation, discharge_on_threshold and discharge_off_threshold should specify a deadband for operation. If equal, the inverter may not operate properly and the system may never solve properly. See generators/inverter.cpp(2162).

inverter:'string' - max_charge_rate is zero

• The max_charge_rate for the inverter is currently zero. This will result in no charging action by the inverter. If this is not desired, please specify a valid value. See generators/inverter.cpp(2107).

inverter:'string' - max_discharge_rate is zero

• The max_discharge_rate for the inverter is currently zero. This will result in no discharging action by the inverter. If this is not desired, please specify a valid value. See generators/inverter.cpp(2125).

inverter:'string' - pf_reg_activate_lockout_time is unassigned, using default value of 60s.

• The pf_reg_activate_lockout_time for the inverter is negative. Negative lockout times are not allowed inside the inverter. Please correct the value and try again. See generators/inverter.cpp(1426).

inverter:'string' - pf_reg_activate_lockout_time is zero, oscillations may occur

• The value for pf_reg_activate_lockout_time is zero, which means there is no delay in new dispatch operations. This may result in excessive switching and iteration limits being hit. If this is not desired, specify a charge_lockout_time larger than zero. See generators/inverter.cpp(1446).

inverter:'string' - pf_reg_high is undefined, setting to a default value of -0.95

• A value was not specified for pf_reg_high. This has been arbitrarily set to 0.95 leading (capacitive). If this is not acceptable, please specify the desired power factor value. See generators/inverter.cpp(2032).

inverter:'string' - pf_reg_low is undefined, setting to a default value of 0.97

• A value was not specified for pf_reg_low. This has been arbitrarily set to 0.97 lagging (inductive). If this is not acceptable, please specify the desired power factor value. See generators/inverter.cpp(2042).

inverter:'string' - pf_target_var is undefined, setting to a default value of 0.95

• A value was not specified for pf_pf_target_var. This has been arbitrarily set to 0.95 lagging (inductive). If this is not acceptable, please specify the desired power factor value. See generators/inverter.cpp(2022).

inverter:'string' - sense_object not specified for LOAD_FOLLOWING and/or power-factor regulation - attempting to use parent object

• The inverter is currently configured for LOAD_FOLLOWING mode, but did not have an appropriate sense_object specified. The inverter is therefore using the parented object as the expected sense_object. See generators/inverter.cpp(1303).

inverter:'string' indicates it wants to run deltamode, but the module-level flag is not set!

• The diesel_dg object has the deltamode_inclusive flag set, but not the module-level enable_subsecond_models flag. The generator will not simulate any dynamics this way. See generators/inverter.cpp(1865).

inverter:'string' is LOAD_FOLLOWING and/or power-factor regulating based on a meter or triplex_meter, ensure the inverter is connected inline with that object!

• The inverter operates in LOAD_FOLLOWING mode under the assumption the sense_object meter or triplex_meter is either attached to the inverter, or directly upstream in the flow. If this assumption is violated, the results may not be as expected. See generators/inverter.cpp(1347).

jsondump:'integer'-'string' -- If per-unit impedance is desired, a valid system_base must be specified - defaulting to 100 MVA

• To use the per-unit functionality of the jsdondump object, a valid system base must be specified (>0.0). Either none was specified, or an invalid one was specified. As such, the base is adjusted to an assumed base of 100 MVA. If this is not a valid base, please specify the proper value. Please try again. See powerflow/jsondump.cpp(90).

lighting load 'real' exceeds installed capacity

• The lighting load cannot exceed the installed capacity. Use a lighting load that is less than or equal to 1.0 and try again. See residential/lights.cpp(122).

lights load 'real' is negative

• The lighting load cannot be negative. Use a positive lighting load and try again. See residential/lights.cpp(128).

Line:'string' is at 'real'%% of its continuous rating on phase 1!

• Phase 1 on the line has exceeded the continuous rating associated with it. See powerflow/link.cpp(2990).

Line:'string' is at 'real'%% of its continuous rating on phase 2!

• Phase 1 on the line has exceeded the continuous rating associated with it. See powerflow/link.cpp(3026).

Line:'string' is at 'real'%% of its continuous rating on phase A!

• Phase A on the line has exceeded the continuous rating associated with it. See powerflow/link.cpp(3067).

Line:'string' is at 'real'%% of its continuous rating on phase B!

• Phase B on the line has exceeded the continuous rating associated with it. See powerflow/link.cpp(3106).

Line:'string' is at 'real'%% of its continuous rating on phase C!

• Phase C on the line has exceeded the continuous rating associated with it. See powerflow/link.cpp(3145).

Line:'string' is at 'real'%% of its emergency rating on phase 1!

• Phase 1 on the line has exceeded the emergency rating associated with it. See powerflow/link.cpp(2983).

Line:'string' is at 'real'%% of its emergency rating on phase 2!

• Phase 1 on the line has exceeded the emergency rating associated with it. See powerflow/link.cpp(3019).

Line:'string' is at 'real'%% of its emergency rating on phase A!

• Phase A on the line has exceeded the emergency rating associated with it. See powerflow/link.cpp(3060).

Line:'string' is at 'real'%% of its emergency rating on phase B!

• Phase B on the line has exceeded the emergency rating associated with it. See powerflow/link.cpp(3099).

Line:'string' is at 'real'%% of its emergency rating on phase C!

• Phase C on the line has exceeded the emergency rating associated with it. See powerflow/link.cpp(3138).

link:'integer' - 'string' -- fault current not available on very first time loop

• Due to the nature of the mesh-fault current calculation algorithm, it can not calculate a fault current on the very first iteration of the system. Please place your fault time at least one second in the future and try again. See powerflow/link.cpp(9953).

link:'string' has a negative mean_repair_time, set to 1 hour

• A link object had a mean_repair_time that is negative. This ia not a valid setting. The value has been changed to 0. Please set the variable to an appropriate variable See powerflow/link.cpp(310).

load:'string' - constant_current loads in deltamode are handled slightly different

• Due to the potential for moving reference frame of deltamode systems, constant current loads are computed using a scaled per-unit approach, rather than the fixed constant_current value. You may get results that differ from traditional GridLAB-D super-second or static powerflow results in this mode. See powerflow/load.cpp(294).

load:'string' - ZIP components on phase 'character' did not sum to 1. Setting power_fraction to 'real'

• ZIP load fractions must sum to 1. The values (power_fraction_X, impedance_fraction_X, and current_fraction_X) on the given phase did not sum to 1. To ensure that constraint (Z+I+P=1), power_fraction is being calculated and overwritten. See powerflow/load.cpp(540).

load:'string' - ZIP components on phase 1 did not sum to 1. Setting power_fraction to 'real'

• ZIP load fractions must sum to 1. The values (power_fraction_1, impedance_fraction_1, and current_fraction_1) did not sum to 1. To ensure that constraint (Z+I+P=1), power_fraction is being calculated and overwritten. See powerflow/triplex_load.cpp(242).

load:'string' - ZIP components on phase 12 did not sum to 1. Setting power_fraction to 'real'

• ZIP load fractions must sum to 1. The values (power_fraction_12, impedance_fraction_12, and current_fraction_12) did not sum to 1. To ensure that constraint (Z+I+P=1), power_fraction is being calculated and overwritten. See powerflow/triplex_load.cpp(440).

load:'string' - ZIP components on phase 2 did not sum to 1. Setting power_fraction to 'real'

• ZIP load fractions must sum to 1. The values (power_fraction_2, impedance_fraction_2, and current_fraction_2) did not sum to 1. To ensure that constraint (Z+I+P=1), power_fraction is being calculated and overwritten. See powerflow/triplex_load.cpp(342).

locale pop failed

• This is an internal error causes by a corrupt locale stack. See gldcore/local.c(57).

locale TZ is empty

• This warning indicates that the TZ environment variable has not be set. This variable is used to specify the default timezone to use while GridLAB-D is running. Supported timezones are listed in the tzinfo.txt file. See gldcore/local.c(30).

LU_init of external solver solver_'string' not found, defaulting to superLU

• While attempting to link the LU_init routine of an external LU matrix solver library, the routine failed to be found. Check the external library and try again. At this failure, powerflow will revert to the superLU solver for Newton-Raphson. See powerflow/node.cpp(833).
• While attempting to link the LU_init routine of an external LU matrix solver library, the routine failed to be found. Check the external library and try again. At this failure, powerflow will revert to the superLU solver for Newton-Raphson. See powerflow/node.cpp(850).
• While attempting to link the LU_init routine of an external LU matrix solver library, the routine failed to be found. Check the external library and try again. At this failure, powerflow will revert to the superLU solver for Newton-Raphson. See powerflow/node.cpp(867).
• While attempting to link the LU_init routine of an external LU matrix solver library, the routine failed to be found. Check the external library and try again. At this failure, powerflow will revert to the superLU solver for Newton-Raphson. See powerflow/node.cpp(884).

Manual event 'integer' of eventgen:'string' exceeded the simultaneous fault limit and was ignored

• While processing manual fault conditions, a fault attempted to exceed the maximum number of faults limit set for this eventgen object. This fault is now ignored. Increase the maximum simultaneous fault limit and try again. See reliability/eventgen.cpp(1673).

market statistic 'string' interval not a multiple of market period, rounding towards one interval

• Market statistics are only calculated when the market clears, and will be calculated assuming intervals that are multiples of the market's period. See market/auction.cpp(327).

market statistic 'string' samples faster than the market updates and will be filled with immediate data

• Market statistics are only calculated when the market clears. Statistics shorter than the market clearing rate wind up being equal to either the immediate price or to zero, due to the constant price during the specified interval. See market/auction.cpp(317).

market statistic interval for 'string' is not positive, skipping

• Negative market statistic intervals are nonsensical. See market/auction.cpp(484).

Maximum outage for 'string' was above global max - restricted to global max

• The max_outage_length value exceeds the module global event length defined in maximum_event_length. Th max_outage_length has been truncated to the module global value. If this is undesired, specify and increase the global maximum_event_length value. See reliability/eventgen.cpp(245).

metrics_collector_writer::init(): no filename defined, auto-generating 'string'

• group_recorder requires a filename. If none is provided, a filename will be generated using a combination of the classname and the core-assigned ID number. See tape/metrics_collector_writer.cpp(50).

motor:'string' -- both H and J were specified, H will be used, J is ignored

• Both H and J were specified, H will be used, J is ignored. See powerflow/motor.cpp(409).

NHTS data file not found, using defaults

• The formatted .CSV file of NHTS (or NHTS-like) data was not found. A set of default values will be used instead. See residential/evcharger_det.cpp(229).

No battery objects were found, but the VSI object exists. Now assume the VSI is attached with infinite input power.

• No battery object attached to VSI. In reality, a battery is required for VSI to output enough power. See generators/inverter.cpp(958).

No capacitor phase connection information is available for capacitor:'integer'. Defaulting to the phases property.

• The capacitor does not have any information specified about how the capacitors are actually connected. The phases property of the capacitor will be utilized instead. If this is incorrect, explicitly specify the phases in phases_connected. See powerflow/capacitor.cpp(364).

No climate data found - using static temperature

• While attempting to map a climate object for the transformer aging model, no climate object could be found. Static temperature data will be used instead. Please check your code or manually specify a climate object if this is not desired. See powerflow/transformer.cpp(1052).
• While attempting to map a climate object for the transformer aging model, no climate object could be found. Static temperature data will be used instead. Please check your code or manually specify a climate object if this is not desired. See powerflow/transformer.cpp(1071).
• While attempting to map a climate object for the transformer aging model, no climate object could be found. Static temperature data will be used instead. Please check your code or manually specify a climate object if this is not desired. See powerflow/transformer.cpp(1090).
• While attempting to map a climate object for the transformer aging model, no climate object could be found. Static temperature data will be used instead. Please check your code or manually specify a climate object if this is not desired. See powerflow/transformer.cpp(1105).
• While attempting to map a climate object for the transformer aging model, no climate object could be found. Static temperature data will be used instead. Please check your code or manually specify a climate object if this is not desired. See powerflow/transformer.cpp(1123).

No eventgen object mapped up to 'string', unscheduled faults are not allowed

• No eventgen object is specified on the fault_check field eventgen_object. Without this specified, "unscheduled" faults can not occur and will simply stop the simulation. This includes fuses blowing and "non-faulted" switch operations. See powerflow/power_metrics.cpp(386).

No fault_check object present - Newton-Raphson solver may fail!

• A fuse blew and created an open link. If the system is not meshed, the Newton-Raphson solver will likely fail. Theoretically, this should be a quick fail due to a singular matrix. However, the system occasionally gets stuck and will exhaust iteration cycles before continuing. If the fuse is blowing and the NR solver still iterates for a long time, this may be the case. See powerflow/fuse.cpp(625).
• A switch changed and created an open link. If the system is not meshed, the Newton-Raphson solver will likely fail. Theoretically, this should be a quick fail due to a singular matrix. However, the system occasionally gets stuck and will exhaust iteration cycles before continuing. If the fuse is blowing and the NR solver still iterates for a long time, this may be the case. See powerflow/switch_object.cpp(678).

No link objects were found.

• No link objects were found in your .glm file. In this way, there is no losses calculated. See tape/metrics_collector.cpp(309).

No lockout time specified for capacitor:'integer's VAR-VOLT control scheme. May switch excessively.

• Without a lockout_time set, the capacitor will only turn off for the delays instituted in time_delay. See powerflow/capacitor.cpp(342).

No value for bid_gen_rating set, assuming $0.0 Op and Maint cost

• While attempting to convert the operations and maintenance annual cost into an energy cost, the generator rating was not set. If this is not correct, please specify a value for bid_gen_rating. See market/generator_controller.cpp(610).
• While attempting to convert the operations and maintenance annual cost into an energy cost, the generator rating was not set. If this is not correct, please specify a value for bid_gen_rating. See market/generator_controller.cpp(631).

node:'integer' - 'string' - Attempted to map an NR-based function, but is not using an NR solver

• An object just attempted to map a current injection update function that only works with the Newton-Raphson solver, but that method is not being used. See powerflow/node.cpp(5215).

node:'integer' - 'string' - Tried to re-enable a node that wasn't disabled!

• While attempting to reset a node from a "disabled island" state, it was not already disabled. Therefore, no action occurred. See powerflow/node.cpp(5060).

node:'string' - Not a SWING-capable bus, so no swing status swap changed

• While attempting to swap a node from being a "swing node", it was tried on a node that was not already a SWING or SWING_PQ node, which is not a valid attempt. See powerflow/node.cpp(5017).

Node:'string' does not have the same nominal voltage as its parent - copying voltage from parent.

• A node object was parented to another node object with a different nominal_voltage set. The childed object will now take the parent nominal_voltage. If this is not intended, please add a transformer between these nodes. See powerflow/node.cpp(749).

node:'string' has a negative mean_repair_time, set to 1 hour

• A node object had a mean_repair_time that is negative. This ia not a valid setting. The value has been changed to 0. Please set the variable to an appropriate variable See powerflow/node.cpp(937).

Node:'string' is parented to a swing node and will get folded into it.

• When a node has the parent field populated, it is assumed this is for a "zero-length" line connection. If a swing node is specified, it will assume the node is linked to the swing node via a zero-length connection. If this is undesired, remove the parenting to the swing node. See powerflow/node.cpp(583).

NR: A matrix dump was requested, but no filename was specified. No dump will occur

• The powerflow module was configured such that a Newton-Raphson-based matrix dump was desired. However, no file was specified in NR_matrix_file. No output will be performed. See powerflow/node.cpp(1697).

Object 'string' (node:'integer') is flagged for deltamode, but it's parent is not. This may lead to incorrect answers!

• A childed node's parent is not flagged for deltamode. This may lead to some erroneous errors in the powerflow. Please apply the flags DELTAMODE property to the parent, or utilize the all_powerflow_delta module-level flag to fix this. See powerflow/node.cpp(1241).

Only WYE-WYE configurations are working in either Newton-Raphson or non-Manual controls

• For this portion of development, only WYE-WYE configurations are fully supported. Later implementations will include support for other regulator configurations. As it stands, WYE-WYE regulators work in SM_NR for both Manual and Automatic controls, while OPEN_DELTA_ABBC is only supported in single powerflow simulations. See powerflow/regulator.cpp(327).

outage length for object:'string' in eventgen:'string' exceeds the defined maximum outage.

• An outage length specified for the manual event generation mode is longer than the value defined in max_outage_length. If this is not desired, fix the input. If it is acceptable, the simulation will run normally. See reliability/eventgen.cpp(496).

Outage length for object:'string' is less than the minimum timestep of 'real' seconds, rounded to minimum timestep

• The selected outage length is less than the mininum timestep set. It has been forced to be at least one minimum timestep long. See reliability/eventgen.cpp(513).

Phase A of fuse:'string' just blew!

• The current through phase A of the fuse just exceeded the maximum rated value. Use a larger value, or otherwise change your system and try again. See powerflow/fuse.cpp(418).

Phase B of fuse:'string' just blew!

• The current through phase B of the fuse just exceeded the maximum rated value. Use a larger value, or otherwise change your system and try again. See powerflow/fuse.cpp(460).

Phase C of fuse:'string' just blew!

• The current through phase C of the fuse just exceeded the maximum rated value. Use a larger value, or otherwise change your system and try again. See powerflow/fuse.cpp(502).

power_convergence_value not set - defaulting to 0.01 base_power

• A value was not specified for the convergence criterion required before posting an answer up to pw_load. This value has defaulted to 1% of base_power. If a different threshold is desired, set it explicitly. See powerflow/substation.cpp(164).

property_malloc(oclass='string',...): property name 'string' is defined more than once

• A class is attempting to publish a variable more than once. This is caused by an repeated specification for a variable publication (in C++) or declaration (in GLM). See gldcore/property.c(165).

pw_load::init(): power_threshold is negative, making positive

• The power_threshold specified for pw_load is a negative value. It has been automatically made positive. See network/pw_load.cpp(651).

pw_load::init(): power_threshold is zero, convergence may not occur!

• pw_load has a zero value for power_threshold. It attempted to guess a value using the connected load inside PowerWorld, but that was 0 as well. This results in an extremely tight convergence criterion and may fail. Specify a manual value to ensure convergence. See network/pw_load.cpp(667).

pw_load::init(): power_threshold was zero, set to 0.1%% of load - 'real' MVA

• pw_load had a zero value for power_threshold. The solver pulled the current value from the connected PowerWorld load and will use 0.1% of its VA value as the convergence criterion. If this is too loose or otherwise unacceptable, specify a manual convergence value. See network/pw_load.cpp(676).

random_bernoulli(p='real'): p is not between 0 and 1

• An attempt to generate a random number used a parameter that was outside the expected range of real numbers. Correct the functional definition of the random number and try again. See gldcore/random.c(362).

random_bernoulli(p='real'): p is not within the normal bounds of +/-1e(+/-30)

• An attempt to generate a random number used a parameter that was outside the expected range of real numbers. Correct the functional definition of the random number and try again. See gldcore/random.c(356).

random_degenerate(a='real'): a is outside normal bounds of +/-1e(+/-30)

• An attempt to generate a random number used a parameter that was outside the expected range of real numbers. Correct the functional definition of the random number and try again. See gldcore/random.c(258).

random_exponential(l='real'): l is not within the normal bounds of 1e(+/-30)

• An attempt to generate a random number used a parameter that was outside the expected range of real numbers. Correct the functional definition of the random number and try again. See gldcore/random.c(479).

random_normal(m='real', s='real'): s is negative

• An attempt to generate a random number used a parameter that was outside the expected range of real numbers. Correct the functional definition of the random number and try again. See gldcore/random.c(334).

random_pareto(m='real', k='real'): k is not within the normal bounds of +/-1e(+/-30)

• An attempt to generate a random number used a parameter that was outside the expected range of real numbers. Correct the functional definition of the random number and try again. See gldcore/random.c(429).

random_pareto(m='real', k='real'): m is not within the normal bounds of +/-1e(+/-30)

• An attempt to generate a random number used a parameter that was outside the expected range of real numbers. Correct the functional definition of the random number and try again. See gldcore/random.c(423).

random_sampled(n='integer',...): sampled value is not within normal bounds of +/-1e(+/-30)

• An attempt to generate a random number used a parameter that was outside the expected range of real numbers. Correct the functional definition of the random number and try again. See gldcore/random.c(388).

random_uniform(a='real', b='real'): a is outside normal bounds of +/-1e(+/-30)

• An attempt to generate a random number used a parameter that was outside the expected range of real numbers. Correct the functional definition of the random number and try again. See gldcore/random.c(286).

random_uniform(a='real', b='real'): b is less than a

• An attempt to generate a random number used a parameter that was outside the expected range of real numbers. Correct the functional definition of the random number and try again. See gldcore/random.c(298).

random_uniform(a='real', b='real'): b is outside normal bounds of +/-1e(+/-30)

• An attempt to generate a random number used a parameter that was outside the expected range of real numbers. Correct the functional definition of the random number and try again. See gldcore/random.c(292).

range:'integer' is using an experimental model and should not be considered reliable

• The range object has a number of VERY experimental features and development is incomplete. If you are receiving this error message, reccommend no longer using this particular feature without considerable overhaul. See residential/range.cpp(469).

Regulator 'string' has phase 'character' at the maximum tap value

• The regulator has set its taps such that it is at the maximum setting. This may indicate a problem with settings, or your system. See powerflow/regulator.cpp(1007).

Regulator 'string' has phase 'character' at the minimum tap value

• The regulator has set its taps such that it is at the minimum setting. This may indicate a problem with settings, or your system. See powerflow/regulator.cpp(1034).

Regulator:'string' regulator_resistance has been set to zero. This will result singular matrix. Setting to the global default.

• Under Newton-Raphson solution method the impedance matrix cannot be a singular matrix for the inversion process. Change the value of regulator_resistance to something small but larger that zero. See powerflow/regulator.cpp(286).

Restoration object not detected!

• The fault_check object can use a restoration object in the system. If the restoration object is present, unsuccessful node support checks will call the reconfiguration. See powerflow/fault_check.cpp(1889).

restoration: Attempt to parse complex CSV array resulted in an empty array - check your inputs

• While attempting to parse a comma-separated string into a complex array, the array appears to be empty. Ensure this is the correct behavior. See powerflow/restoration.cpp(1175).

restoration: Attempt to parse double CSV array resulted in an empty array - check your inputs

• While attempting to parse a comma-separated string into a double array, the array appears to be empty. Ensure this is the correct behavior. See powerflow/restoration.cpp(966).

restoration: Attempt to parse object CSV array resulted in an empty array - check your inputs

• While attempting to parse a comma-separated string into a object array, the array appears to be empty. Ensure this is the correct behavior. See powerflow/restoration.cpp(1300).

restoration: The source vertex for the reconfiguration is not defined, defaulting to a swing bus

• To properly operate, the reconfiguration needs the sources vertex of the system defined. If left blank, the first SWING bus will be utilized instead. See powerflow/restoration.cpp(503).

Reverse real power flow detected at generator switch 'string', generator is absorbing real power now!

• The diesel generator is absorbing real power, which is not allowed. Should check kVA rating and power_out_A/power_out_B/power_out_C value settings. Large kVA rating, or small initial power output than the total loads may result in negative real power output calculated. See generators/controller_dg.cpp(481).

ron or roff was not set. Using phi to calculate. Step changes in demand rates as a function of time will be ignored.

• Ideally, in the method currently being used, ron and roff (heating and cooling rates) should be used to calculate phi. If you receive this error, the phi is being used to calculate ron and roff initially. However, phi does not update ron and roff at each time step, so you will not be able to perform disturbances of demand. If you wish this, please use ron and roff as a function of time instead. This can also be caused by using a schedule or player transform to describe the ron or roff values - essentially during the initialization, the value is not described yet. There is no current fix for this, but can be "faked" by setting phi to the correct initial value and waiting a couple of timesteps for things to settle. See residential/zipload.cpp(206).

ron or roff was not set. Using phi to calculate. Step changes in demand rates as a function of time will be ignored.

• Ideally, in the method currently being used, ron and roff (heating and cooling rates) should be used to calculate phi. If you receive this error, the phi is being used to calculate ron and roff initially. However, phi does not update ron and roff at each time step, so you will not be able to perform disturbances of demand. If you wish this, please use ron and roff as a function of time instead. This can also be caused by using a schedule or player transform to describe the ron or roff values - essentially during the initialization, the value is not described yet. There is no current fix for this, but can be "faked" by setting phi to the correct initial value and waiting a couple of timesteps for things to settle. See residential/zipload.cpp(220).

Shunt capacitance of overhead line:'string' not calculated - invalid values

• While attempting to calculate the shunt capacitance for an overhead line, an invalid parameter was encountered. To calculate shunt capacitance, ensure the condutor to earth distance for each phase is defined, as well as the diameter of that phases's cable. See powerflow/overhead_line.cpp(496).

Solar object:'string' is in player mode - be sure to specify relevant values

• The solar array object is in player mode. It will not take values from climate files or objects. Be sure to specify the Insolation, ambient_temperature, and wind_speed values as necessary. It also will not incorporate any tilt functionality, since the Insolation value is expected to already include this adjustment. See generators/solar.cpp(489).

solar:'integer' 'string' - Deltamode is enabled for the module, but not this solar array!

• The solar array is not flagged for deltamode operations, yet deltamode simulations are enabled for the overall system. When deltamode triggers, this array may no longer contribute to the system, until event-driven mode resumes. This could cause issues with the simulation. It is recommended all objects that support deltamode enable it. See generators/solar.cpp(936).

solar:'string' - Default solar position model is not recommended for southern hemisphere!

• The Liu-Jordan (default) solar position and tilt model was built around the northern hemisphere. As such, operating in the southern hemisphere does not provide completely accurate results. They are close, but tilted surfaces are not properly accounted for. It is recommended that the SOLAR_TILT_MODEL SOLPOS be used for southern hemisphere operations. See generators/solar.cpp(449).

solar:'string' indicates it wants to run deltamode, but the module-level flag is not set!

• The solar object has the deltamode_inclusive flag set, but not the module-level enable_subsecond_models flag. The generator will not simulate any dynamics this way. See generators/solar.cpp(898).

solarpanel: 'integer' climates found, using first one defined

• More than one climate object was found, so only the first one will be used by the solar array object See generators/solar.cpp(267).

solarpanel: no climate data found, using static data

• No climate object was found and player mode was not enabled, so the solar array object is utilizing default values for all relevant weather variables. See generators/solar.cpp(285).

stored_capacity and SOC are both defined, SOC being used for initial energy state

• During the initialization of the system, a value was specified for both the stored_capacity and SOC (state of charge). The thermal energy storage object gives precedence to the SOC variable, so the initial stored_capacity will be the SOC percentage of the total_capacity. See residential/thermal_storage.cpp(246).

substation attached to pw_load and not a SWING bus - forcing to SWING

• When a substation object is connected to PowerWorld via a pw_load object, the substation must be designated as a SWING bus. This designation will now be forced upon the bus. See powerflow/substation.cpp(211).

substation is not a SWING bus, so answers may be unexpected

• A substation object appears set to accept sequence voltage values, but it is not a SWING bus. This may end up causing the voltages to be converted from sequence, but then overridden by the distribution powerflow solver. See powerflow/substation.cpp(236).

substation:'string' is set up as a normal node, no sequence values will be calculated

• A substation is currently behaving just like a normal powerflow node. If it was desired that it convert a schedule or player of sequence values, please initialize those values to non-zero along with the player attachment. See powerflow/substation.cpp(252).

SWING bus:'string' is not flagged for deltamode

• Deltamode is enabled for the overall powerflow module, but not for the SWING node of the powerflow. This means the overall powerflow is not being calculated or included in any deltamode calculations. If this is not a desired run method, please enable the deltamode_inclusive flag on the SWING node. See powerflow/node.cpp(1681).

switch objects may not behave properly under FBS!

• Due to the nature of the forward-backward sweep algorithm, and open switch may induce the desired behavior on the system. If open, it should prevent current flow and set the "to" end voltage to zero. However, this may cause problems in many powerflow conditions or not properly solve. Consider using the Newton-Raphson solver in conjunction with the reliability package, or rearrange your system. See powerflow/switch_object.cpp(143).

Switch status updated, but no other changes made.

• When changed under solver methods other than NR, only the switch status is changed. The solver handles other details in a specific step, so no other changes are performed. See powerflow/switch_object.cpp(1468).

Switch:'string' switch_resistance has been set to zero. This will result singular matrix. Setting to the global default.

• Under Newton-Raphson solution method the impedance matrix cannot be a singular matrix for the inversion process. Change the value of switch_resistance to something small but larger that zero. See powerflow/switch_object.cpp(168).

The dc voltage is greater than the specified maximum for the inverter. Efficiency model may be inaccurate.

• The DC voltage at the input to the inverter is less than the maximum voltage supported by the inverter. As a result, the multipoint efficiency model may not provide a proper result. See generators/inverter.cpp(3016).
• The DC voltage at the input to the inverter is less than the maximum voltage supported by the inverter. As a result, the multipoint efficiency model may not provide a proper result. See generators/inverter.cpp(3118).
• The DC voltage at the input to the inverter is less than the maximum voltage supported by the inverter. As a result, the multipoint efficiency model may not provide a proper result. See generators/inverter.cpp(7600).

The external solver solver_'string' could not be found, defaulting to superLU

• While attempting to link an external LU matrix solver library, the file could not be found. Ensure it is in the proper GridLAB-D folder and is named correctly. If the error persists, please submit your code and a bug report via the trac website. See powerflow/node.cpp(917).

The generator has already exhausted its yearly runtime quota, it will not run this year

• The value specified for current_year_runtime is larger or equal to yearly_runtime_limit. This means the generator has exhausted all of its available runtime hours for the year and will no longer run. See market/generator_controller.cpp(528).

The PV is over rated for its parent inverter.

• The maximum output for the PV array is larger than the inverter rating. Ensure this was done intentionally. If not, please correct your values and try again. See generators/solar.cpp(788).

This connection type on transformer:'integer' ('string') does not support impedance (impedance1 or impedance2) of secondaries at this time.

• At this time impedance1 and impedance2 are only defined and used for center-tap transformers to be explicitly defined. These values will be ignored for now. See powerflow/transformer_configuration.cpp(221).

This connection type on transformer:'integer' ('string') does not support shunt_impedance at this time.

• At this time shunt_impedance is only defined and supported in center-tap and WYE-WYE transformers. Theses values will be ignored for now. See powerflow/transformer_configuration.cpp(229).
• At this time no_load_loss and full_load_loss are only defined and supported in center-tap transformers. Theses values will be ignored for now. See powerflow/transformer_configuration.cpp(236).

transformer:'integer' 'string' is set to model saturation, but has no magnetization location

• While attempting to initialize a transformer for inrush saturation calculations, it was noticed that no magentization location was specified. No saturation can be modeled in this case. Please specify a winding to include the magnetization on with the magnetization_location of the transformer_configuration object. See powerflow/transformer.cpp(1757).

transformer:'string' is at 'real'%% of its rated power value

• The total power passing through a transformer is above its kVA rating. See powerflow/link.cpp(2960).

transormer_configuration:'integer' ('string') reactance_resistance_ratio was not set and defaulted to 4.5. This may cause issues with larger transformers (>0.5 MVA)

• X/R ratios are highly dependent on the size of the transformer. As the transformer rating goes up so does the X/R ratio. For small residential transformers (<500 kVA), the values range from about 2-5 as good estimates. For a good X/R reference, recommend GE's GET-3550F document, Appendix Part II. See powerflow/transformer_configuration.cpp(248).

triplex_load:'string' - constant_current loads in deltamode are handled slightly different

• Due to the potential for moving reference frame of deltamode systems, constant current loads are computed using a scaled per-unit approach, rather than the fixed constant_current value. You may get results that differ from traditional GridLAB-D super-second or static powerflow results in this mode. See powerflow/triplex_load.cpp(155).

Unable to compute capacitance for 'string'

• One phase of an underground line has either a conductor diameter, a concentric-neutral location diameter, or a neutral strand count of zero. This will lead to indeterminant values in the analysis. Please fix these values, or run the simulation with line capacitance disabled. See powerflow/underground_line.cpp(823).
• One phase of an underground line has either a conductor diameter, a concentric-neutral location diameter, or a neutral strand count of zero. This will lead to indeterminant values in the analysis. Please fix these values, or run the simulation with line capacitance disabled. See powerflow/underground_line.cpp(950).

Unable to find secondary interruption flag, no secondary interruptions recorded in metrics:'string'

• While attempting to link to the 'secondary customer interrupted' flag, it was not found. THe object may not support "secondary interruption counts" and this message is valid. If a secondary count was desired, ensure the object supports being polled by reliability as a customer (customer_interrupted_secondary exists as a published property) and try again. If the error persists, please submit your code and a bug report via the trac website. See reliability/metrics.cpp(464).

Unable to map add_event function in eventgen:'string'

• While attempting to map the "add_event" function from an eventgen object, the function failed to be found. Ensure the target object in fault_check is an eventgen object and this function exists. If the error persists, please submit your code and a bug report via the trac website. See powerflow/fuse.cpp(341).
• While attempting to map the "add_event" function from an eventgen object, the function failed to be found. Ensure the target object in fault_check is an eventgen object and this function exists. If the error persists, please submit your code and a bug report via the trac website. See powerflow/switch_object.cpp(714).

Unable to map mean_repair_time from object:'string'

• While attempting to access the mean_repair_time of the safety device, GridLAB-D encountered an error. Ensure the object has this value. If it does not, it will be ignored. If it does exist and this warning appeared, please try again. If the warning persists, please submit your code and a bug report via the trac website. See powerflow/link.cpp(7254).
• While attempting to access the mean_repair_time of the safety device, GridLAB-D encountered an error. Ensure the object has this value. If it does not, it will be ignored. If it does exist and this warning appeared, please try again. If the warning persists, please submit your code and a bug report via the trac website. See powerflow/link.cpp(10059).

Underground_line:'integer' 'string' - phase N conductor should just be a normal conductor!

• A conductor on phase N has properties that imply it is either a concentric neutral or a tape-shield cable. This is redundant for a neutral connection and may not be necessary. See powerflow/underground_line.cpp(1308).

Underground_line:'integer' - 'string' is a tape-shielded cable and may need an explicit phase N conductor

• The underground cable is set up as a tape-shielded cable. For neutral currents, it may require an explicit neutral to be connected, unless it represents a delta-connected system. See powerflow/underground_line.cpp(709).

Unsupported phase on a possibly meshed node

• An unsupported connection was found on the system. Since reliability is enabled, the solver will simply ignore the unsupported components for now. See powerflow/fault_check.cpp(357).

Unsupported phase on node 'string'

• An unsupported connection was found on the indicated bus in the system. Since reliability is enabled, the solver will simply ignore the unsupported components for now. See powerflow/fault_check.cpp(287).

Vehicle location not set, using defaults

• The value for vehicle_index was not set, so a read of the NHTS file was not even attempted. A set of default values will be used instead. See residential/evcharger_det.cpp(215).

VFD:'integer' - 'string' - FROM node nominal_voltage is not equal to or greater than TO node nominal_voltage - implies DC-DC converter!e

• The from node nominal_voltage is less than the to node nominal_voltage. This implies an internal DC-DC converter, which is not explicityly modeled. Efficiency values will not be accurate! See powerflow/vfd.cpp(201).

VFD:'integer' - 'string' - nominal_output_frequency is not set or is negative - defaulting to system nominal

• The nominal_output_frequency variable was not set properly - defaulting to nominal_frequency of the system. See powerflow/vfd.cpp(211).

VFD:'integer' - 'string' - rated_output_voltage does not match the TO node nominal voltage

• The rated_output_voltage does not match the nominal_voltage of the TO node. This may cause some issues with simulations results. See powerflow/vfd.cpp(189).

VFD:'integer' - 'string' - rated_output_voltage was not set, defaulting to TO node nominal

• The rated_output_voltage was not set for the VFD. It has been defaulted to the nominal_voltage value of the TO node. See powerflow/vfd.cpp(174).

VFD:'integer' - 'string' - the desired_motor_speed results in a frequency of less than 3.0 Hz

• The desired_motor_speed results in a value that is less than the starting frequency of a typical VFD. This is high discouraged, since it may not function properly in this range. See powerflow/vfd.cpp(367).

VFD:'integer' - 'string' - VFD currently at 'real'%% of rated speed -- VFDs perform best when running at >= 75 percent output

• Recommended to run a VFD at 75%. Lower values are not recommended and can result in odd behavior See powerflow/vfd.cpp(376).

volt_var_control 'string': A link to monitor power-factor was not specified, using first regulator.

• The volt_var_control object requires a link-based object to measure power factor. Since one was not specified, the control scheme will just monitor the power values of the first feeder regulator. See powerflow/volt_var_control.cpp(809).

volt_var_control 'string': capacitor_delay should be greater than or equal to 1 to prevent convergence issues.

• The capacitor_delay should be greater than or equal to 1.0 to avoid having a system oscillate switch positions until the convergence limit is reached. See powerflow/volt_var_control.cpp(211).

volt_var_control 'string': Desired, minimum, and maximum voltages don't match

• The lists for desired_voltages, minimum_voltages, and maximum_voltages should all have the same number of elements. If they don't, if at each field has at least one specification, the first for each will be used on all regulators. If they don't all have at least one specification, the whole set will be set to default values. See powerflow/volt_var_control.cpp(549).

volt_var_control 'string': Low loading deadband for regulator 'integer' is expected to be larger than the high loading deadband

• The high_load_deadband is larger than the low_load_deadband setting. The algorithm proposed in the referenced paper suggests low_load_deadband should be larger (less constrained) than the high load. This may need to be fixed to be consistent with expected results. See powerflow/volt_var_control.cpp(771).

volt_var_control 'string': No capacitors specified.

• The capacitor_list in the volt_var_control is empty. This means no capacitors are controlled by the volt_var_control object, which more or less means you have voltage setpoint regulators and no need for a central control. See powerflow/volt_var_control.cpp(1126).

volt_var_control 'string': No measurement point specified for reg 'integer' - defaulting to load side of regulator

• If no measuremnt points are specified for a regualtor in the volt_var_control object, it will default to the load side of the regulator. Please specify measurement points for better control. See powerflow/volt_var_control.cpp(1418).

volt_var_control 'string': Power factor monitored phases not set - defaulting to substation_link phases

• The pf_phases variable was not set, so the volt_var_control object defaulted to the phases of the substation_link object. If this is not desired, please specify the phases on pf_phases. See powerflow/volt_var_control.cpp(1503).

volt_var_control 'string': regulator_delay should be greater than or equal to 1 to prevent convergence issues.

• The regulator_delay should be greater than or equal to 1.0 to avoid having a system oscillate switch positions until the convergence limit is reached. See powerflow/volt_var_control.cpp(228).

volt_var_control 'string': The set point for phase A will exceed the maximum allowed voltage!

• The set point necessary to maintain the end point voltage exceeds the maximum voltage limit specified by the system. Either increase this maximum_voltage limit, or configure your system differently. See powerflow/volt_var_control.cpp(1713).

volt_var_control 'string': The set point for phase A will exceed the minimum allowed voltage!

• The set point necessary to maintain the end point voltage exceeds the minimum voltage limit specified by the system. Either decrease this minimum_voltage limit, or configure your system differently. See powerflow/volt_var_control.cpp(1737).

volt_var_control 'string': VDrop, low V BW, and high V BW don't match

• The lists for maximum voltage drop, voltage drop low loading, and voltage drop high loading should all have the same number of elements. If they don't, if at each field has at least one specification, the first for each will be used on all regulators. If they don't all have at least one specification, the whole set will be set to default values. See powerflow/volt_var_control.cpp(657).

waterheater:'integer' is boiling

• The temperature model for the waterheater has broken, or the environment around the waterheater has burst into flames. Please post this with your model and dump files attached to the bug report. See residential/waterheater.cpp(679).

windturb_dg (id:'integer', name:'string'): Rated generator voltage (LL: 'real') and nominal voltage (LL: 'real') of meter parent are different by greater than 10 percent. Odd behavior may occur.

• Currently, the model allows you to attach the turbine to a voltage that is quite different than the rated terminal voltage of the generator. However, this may cause odd behavior, as the solved powerflow voltage is used to calculate the generator induced voltages and conversion from mechanical power. It is recommended that the nominal voltages of the parent meter be within ~10% of the rated voltage. See generators/windturb_dg.cpp(541).
• Currently, the model allows you to attach the turbine to a voltage that is quite different than the rated terminal voltage of the generator. However, this may cause odd behavior, as the solved powerflow voltage is used to calculate the generator induced voltages and conversion from mechanical power. It is recommended that the nominal voltages of the parent meter be within ~10% of the rated voltage. See generators/windturb_dg.cpp(591).

windturb_dg (id:'integer',name:'string'): internal iteration limit reached, breaking out of loop. Injected current may not be solved sufficiently.

• This may need some work. The generator models are solved iteratively by using the system voltage as the boundary condition. The current model iterates on solving the current injection, but then breaks out if not solved within 100 iterations. May indicate some issues with the model (i.e., voltage is incorrectly set on the connection node) or it may indicate poor programming. Please report if you see this message. See generators/windturb_dg.cpp(931).
• This may need some work. The generator models are solved iteratively by using the system voltage as the boundary condition. The current model iterates on solving the current injection, but then breaks out if not solved within 100 iterations. May indicate some issues with the model (i.e., voltage is incorrectly set on the connection node) or it may indicate poor programming. Please report if you see this message. See generators/windturb_dg.cpp(1049).

zipload_init: The demand response zipload is an experimental model at this time.

• The warning is pretty obvious. However, over time, we will be developing this model further. If you have any questions about it, please see the Matlab files found in ../design/dr_model/ or read the paper titled "On the Equilibrium Dynamics of Demand Response" submitted to HICSS 2011 or post your questions on the WIKI forum. See residential/zipload.cpp(142).

zipload_init: Using a value for thermostatic_control_range (L) greater than 50 may cause some instabilities.

• This warning is shown only as a reminder. Large values of L (thermostatic_control_range) can cause instabilities for some combinations of ron and roff. If you receive inderminant numbers as part of the solution, try reducing L. See residential/zipload.cpp(173).

Errors

'string' (auction:'integer') capacity_reference_object of type 'string' does not contain specified reference property 'string'

• capacity_reference_object must contain a property named by capacity_reference_property. Review the published properties of the object specified in capacity_reference_object. See market/auction.cpp(339).

'string' (auction:'integer') capacity_reference_object specified without a reference property

• capacity_reference_object can only be used when capacity_reference_property is specified. See market/auction.cpp(357).

'string' (auction:'integer') is using a one-sided market with a negative fixed quantity

• capacity_reference_object can only be used when capacity_reference_property is specified. See market/auction.cpp(367).

'string' is an invalid nsync command

• The nsync debugger command was given an option that isn't valid. Check the syntax and try again. See gldcore/debug.c(690).

'string' is an invalid option to details command

• The details debugger command was given an option that isn't valid. Check the syntax and try again. See gldcore/debug.c(609).

'string' is an invalid option to inactive command

• The inactive debugger command was given an option that isn't valid. Check the syntax and try again. See gldcore/debug.c(636).

'string' is an invalid option to unnamed command

• The unnamed debugger command was given an option that isn't valid. Check the syntax and try again. See gldcore/debug.c(663).

'string' is not a recognized breakpoint subcommand

• The break subcommand isn't recognized. Check the command syntax and try again. See gldcore/debug.c(969).

'string' is not recognized

• The watch subcommand isn't recognized. Check the command syntax and try again. See gldcore/debug.c(1080).

'string': 'string' (GLPATH='string')

• The unit subsystem was not able to locate the unit file in the working directoy or in the directories specified in GLPATH. See gldcore/unit.c(510).

'string': object 'string' stopped its clock (debug)!

• This indicates that one of the objects in the simulator has encountered a state where it cannot calculate the time to the next state. This usually is caused by a bug in the module that implements that object's class. See gldcore/debug.c(1445).

'string': object 'string' stopped its clock (exec)!

• This indicates that one of the objects in the simulator has encountered a state where it cannot calculate the time to the next state. This usually is caused by a bug in the module that implements that object's class. See gldcore/exec.c(521).

'string': object 'string' stopped its clock! (test)

• This indicates that one of the objects in the simulator has encountered a state where it cannot calculate the time to the next state. This usually is caused by a bug in the module that implements that object's class. See gldcore/exec.c(2544).

'string': set_rank internal error, rank > object count

• As a sanity check, the rank of an object should not exceed the number of objects in the model. If the model is deliberately playing with the ranks, please either reduce the manual rank adjustment, or add a number of "harmless" objects to inflate the number of objects in the model. See gldcore/object.c(1224).
• As a sanity check, the rank of an object should not exceed the number of objects in the model. If the model is deliberately playing with the ranks, please either reduce the manual rank adjustment, or add a number of "harmless" objects to inflate the number of objects in the model. See gldcore/object.c(1270).

'string': target 'string' is not valid

• Check to make sure the target you are specifying is a published variable for the object that you are pointing to. Refer to the documentation of the command flag --modhelp, or check the wiki page to determine which variables can be published within the object you are pointing to with the assert function. See assert/assert.cpp(91).
• Check to make sure the target you are specifying is a published variable for the object that you are pointing to. Refer to the documentation of the command flag --modhelp, or check the wiki page to determine which variables can be published within the object you are pointing to with the assert function. See mysql/group_recorder.cpp(330).
• Check to make sure the target you are specifying is a published variable for the object that you are pointing to. Refer to the documentation of the command flag --modhelp, or check the wiki page to determine which variables can be published within the object you are pointing to with the assert function. See mysql/group_recorder.cpp(555).

'string': transformer configuration installed insulation life must be greater than zero

• During the simulation, installed_insulation_life was found to be zero or negative. Either this was specified incorrectly in the model - check to see that installed_insulation_life was set as a positive value in your configuration file - or a major error occurred in the model. If the latter, please post on the GridLAB-D forums. See powerflow/transformer.cpp(1182).

'string': transformer granularity is too small for the minimum timestep specified

• During the simulation, the time step that occured was greater than what the aging_granularity was set to. The usual cause is becasue the aging_granularity wasn't set or set to zero. If setting the aging_granularity parameter to something greater than 0 doesn't get rid of this error please post on the GridLAB-D forums. See powerflow/transformer.cpp(1264).

'string'::'string'.create(OBJECT **obj={name='string', id='integer'},...): 'string'

• The create operation of the specified object failed. The message given provide additional details and can be looked up under the Exceptions section. See residential/thermal_storage.cpp(523).

'string'::'string'.init(OBJECT **obj={name='string', id='integer'},TIMESTAMP t1='string'): 'string'

• The synchronization operation of the specified object failed. The message given provide additional details and can be looked up under the Exceptions section. See residential/thermal_storage.cpp(575).

'string'::'string'.init(OBJECT *obj={name='string', id='integer'}): 'string'

• The initialization operation of the specified object failed. The message given provide additional details and can be looked up under the Exceptions section. See residential/thermal_storage.cpp(543).

'include' variable is not set and neither is GRIDLABD environment, compiler cannot proceed without a way to find gridlabd.h

• The runtime class compiler needs to find the file gridlabd.h and uses either the include global variable or the gridlabd environment variable to find it. Check the definition of the gridlabd environment variable or use the #define include=path to specify the path to the gridlabd.h. See gldcore/load.c(642).

access to global process map 'string' is denied

• Access to the process map is denied. Consult with the system administrator to obtain access to the process map. See gldcore/module.c(2038).

aggregate group 'string' does not use a known aggregator

• An aggregation expression uses an aggregator that is not defined. Check that all your aggregators used allowed functions (e.g., min, max, avg, std, sum, count, etc.). See gldcore/aggregate.c(129).

aggregate group 'string' has invalid units ('string')

• An aggregation expression include a unit specification in the value expression, but the unit is not found. Check your aggregations and make sure all the units are defined. See gldcore/aggregate.c(103).

aggregate group 'string' is not valid

• An aggregation expression does not have the required syntax, e.g., aggregation(value[.part]). Check the aggregation's syntax and make sure it conforms to the required syntax. See gldcore/aggregate.c(65).

aggregate group expression 'string' does not result in a set with a fixed class

• A group expression generated a group whose members vary over time. This is not allowed. Check that all your groups are defined such that the group membership is constant. See gldcore/aggregate.c(158).

aggregate group expression 'string' does not result is a usable object list

• A group expression failed to generate a useful group. Check that all your groups are correctly defined. See gldcore/aggregate.c(173).

aggregate group expression 'string' failed

• A group expression failed to generate a useful group. Check that all your groups are correctly defined. See gldcore/aggregate.c(143).

aggregate group expression 'string' results is an empty object list

• A group expression generated an empty group. Check that all your groups are correctly defined. See gldcore/aggregate.c(186).

aggregate group property 'string' cannot be aggregated

• The aggregate referred to a type of property that cannot be aggregated. Check that your aggregate part refers to a numeric value. See gldcore/aggregate.c(260).

aggregate group property 'string' cannot have part 'string'

• An aggregate part refers to a property that is a real number and does not have any parts. Check that all your aggregate parts refer a property with parts, e.g., a complex value. See gldcore/aggregate.c(217).
• The aggregate part requested is not recognized for the property given. Check that your aggregate part is defined for a complex value. See gldcore/aggregate.c(245).

aggregate group property 'string' cannot use units 'string'

• The aggregate attempted to convert a property to a unit that is not compatible with the property's original unit. Check that your aggregate uses a unit that is fundamentally compatible. See gldcore/aggregate.c(287).

aggregate group property 'string' is not found in the objects satisfying search criteria 'string'

• A group expression failed to generate a group that contains objects that meet the required criteria. Check that all your groups are correctly defined. See gldcore/aggregate.c(201).

aggregate group property 'string' is unitless and cannot be converted

• The aggregate attempted to convert the units of a property that is unitless. Check that your aggregate part does not include a unit specification. See gldcore/aggregate.c(274).

Although controller given group id, no dgs with given group id found.

• While trying to put together a list of all dg objects with the specified controller groupid, no such dg objects were found. See generators/controller_dg.cpp(107).

An error occured writing the CLSID to the registry.

• An error occurred while writing the CLSID value to the registry. Please submit your code and a bug report via the trac website. See network/pw_model.cpp(202).

An object named 'string' already exists!

• GridLab-D prohibits two objects from using the same name, to prevent ambiguous object look-ups. See gldcore/object.c(2406).

auction init_stdev is negative!

• By mathematical definition, real standard deviations cannot be negative. See market/auction.cpp(419).

bidding into future markets is not yet supported

• Tracking bids input markets other than the immediately open one will be supported in the future. See market/auction.cpp(1531).

Capacitor:'integer' does not have any capacitance values defined!

• The capacitor does not have any actual capacitance values defined. This results in the capacitor doing nothing at all and results in no change to the system. Specify a value with capacitor_A, capacitor_B, or capacitor_C. See powerflow/capacitor.cpp(257).

check_COM_output: 'string'

• A generic COM error was encountered while interfacing with PowerWorld. Please check MSDN and other resources for what this may mean. See network/pw_model.cpp(151).

check_COM_output: bad index in SafeArrayGetElement

• A bad index value was encountered while parsing the COM output to PowerWorld. Please ensure all values are correct and try again. See network/pw_model.cpp(123).

check_COM_output: COM call did not return an array of variants

• An error was encountered in pw_load while trying to return a required array. Please try again. If the error persists, please submit your code and a bug report via the trac website See network/pw_model.cpp(110).

check_COM_output: invalid arguement in SafeArrayGetElement

• An invalid argument was encountered while parsing the COM output to PowerWorld. Please ensure all values are correct and try again. See network/pw_model.cpp(131).

check_COM_output: ran out of memory during SafeArrayGetElement

• Memory ran out while parsing the COM output to PowerWorld. Please ensure all values are correct and try again. If the error persists, please submit a bug report via the trac website. See network/pw_model.cpp(139).

check_COM_output_load: 'string'

• A generic COM error was encountered while interfacing with PowerWorld. Please check MSDN and other resources for what this may mean. See network/pw_load.cpp(73).

check_COM_output_load: bad index in SafeArrayGetElement

• A bad index value was encountered while parsing the COM output to PowerWorld. Please ensure all values are correct and try again. See network/pw_load.cpp(45).

check_COM_output_load: COM call did not return an array of variants

• An error was encountered in pw_load while trying to return a required array. Please try again. If the error persists, please submit your code and a bug report via the trac website See network/pw_load.cpp(32).

check_COM_output_load: invalid arguement in SafeArrayGetElement

• An invalid argument was encountered while parsing the COM output to PowerWorld. Please ensure all values are correct and try again. See network/pw_load.cpp(53).

check_COM_output_load: ran out of memory during SafeArrayGetElement

• Memory ran out while parsing the COM output to PowerWorld. Please ensure all values are correct and try again. If the error persists, please submit a bug report via the trac website. See network/pw_load.cpp(61).

class 'string' not found

• A search rule specified a class that doesn't exist. Check the class name to make sure it exists and try again. See gldcore/find.c(1037).
• A search rule specified a class that doesn't exist. Check the class name to make sure it exists and try again. See gldcore/find.c(1055).

class_define_function(CLASS *class={name='string',...}, FUNCTIONNAME functionname='string', ...) the function name has already been defined

• The function in question has already been defined for the class. Only one function of any given name is permitted in each class. Remove or correct the duplicate function declaration and try again. See gldcore/class.c(1026).

class_define_map(oclass='string',...): expected keyword missing after 'string'

• The structure of class is being published with some special properties that only work in the context of a published variable. This is caused by a problem with the module that publishes the class. See gldcore/class.c(737).

class_define_map(oclass='string',...): parent property class name 'string' attempting to inherit from self!

• A class is attempting to directly inherit properties from itself. This is caused by a problem with the module that publishes the class. See gldcore/class.c(684).

class_define_map(oclass='string',...): parent property class name 'string' is not defined

• A class is trying to inherit properties from another class that has not been defined. This is usually caused by a problem in the module(s) that publishes the classes. Either the child class is in not specifying the parent class correctly, or the parent class is not created before the child class. If the child class depends on a class implemented in another module, the module publishing the child class must load the module publishing the parent class before attempting to use it. See gldcore/class.c(671).

class_define_map(oclass='string',...): property 'string' unit 'string' is not recognized: 'string'

• A class is attempting to publish a variable using a unit that is not defined. This is caused by an incorrect unit specification in a variable publication (in C++) or declaration (in GLM). Units are defined in the unit file located in the GridLAB-D etc folder. This error immediately follows a throw event with the same message. See gldcore/class.c(835).

class_define_map(oclass='string',...): property keyword 'string' could not be defined as value 'integer'

• An attempt to define an enumeration property is using a value that cannot be used, either because it is already being used, or because it is outside of range of allowed values for that property. That is caused by a problem in the module that publishes the class. See gldcore/class.c(751).
• An attempt to define an set property is using a value that cannot be used, either because it is already being used, or because it is outside of range of allowed values for that property. That is caused by a problem in the module that publishes the class. See gldcore/class.c(767).

class_define_map(oclass='string',...): property name 'string' conflicts with built-in property

• A class is attempting to publish a variable with a name normally reserved for object headers. This is not allowed. If the class is implemented in a module, this is problem with the module. If the class is declared in a GLM file, you must correct the problem to avoid unpredictable simulation behavior. See gldcore/class.c(912).

class_define_map(oclass='string',...): property name 'string' is too big

• A class is publishing a property using a name that is too big for the system. Property names are limited in length. This must be corrected in the code the declares the property or publishes the class. See gldcore/class.c(902).

class_define_map(oclass='string',...): property size must be greater than 0

• A class is attempting to define a repeated variable (such as an array) that contains less than 1 item. This is caused by a problem in the module that published the class. See gldcore/class.c(804).

class_define_map(oclass='string',...): PT_INHERIT unexpected; class already inherits properties from class 'string'

• This error is caused by an attempt to incorrectly specify a class that inherits variables from more than one other class. This is almost always caused by a bug in the module's constructor for that class. See gldcore/class.c(655).

class_define_map(oclass='string',...): substructure of property 'string' substructure could not be published

• A class is publishing a property that has a substructure, which couldn't be published. This must be corrected in the code the declares the property or publishes the class. See gldcore/class.c(886).

class_define_map(oclass='string',...): unrecognized extended property (PROPERTYTYPE='string')

• A property extension given in a published class specification uses a property type (PT_*) is that not valid. This is caused by a problem in the module that publishes the class. See gldcore/class.c(872).

class_define_map(oclass='string',...): unrecognized property access code (value='integer' is not valid)

• A class is attempting specify a type variable access that is unknown. This is caused by a problem in the module that publishes the class. See gldcore/class.c(789).

class_find_property(oclass='string', name='string') causes an infinite class inheritance loop

• A class has somehow specified itself as a parent class, either directly or indirectly. This means there is a problem with the module that publishes the class. See gldcore/class.c(215).

class_find_property_rec(CLASS *oclass='string', PROPERTYNAME name='string', CLASS *pclass='string') causes an infinite class inheritance loop

• A class has somehow specified itself as a parent class, either directly or indirectly. This means there is a problem with the module that publishes the class. See gldcore/class.c(162).

climate:'string' - Latitude is outside +/-90!

• The value read from the weather data indicates a latitude of greater than 90 or less than -90 degrees. This is not a valid value. Please specify the latitude in this range, with positive values representing the northern hemisphere and negative values representing the southern hemisphere. See climate/climate.cpp(818).

climate:'string' - Longitude is outside +/-180!

• The value read from the weather data indicates a longitude of greater than 180 or less than -180 degrees. This is not a valid value. Please specify the longitude in this range, with positive values representing the eastern hemisphere and negative values representing the western hemisphere. See climate/climate.cpp(830).

climate::init(): no csv_reader specified for tmyfile 'string'

• The weather file provided is for the csv_reader object but not csv_reader object was specified in the reader property. Please specify the name of the csv_reader object in the climate object in the glm. See climate/climate.cpp(720).

CloseCase() failed

• PowerWorld encountered an error while trying to close the open case. Please check to ensure your model is correct. See network/pw_model.cpp(423).

code_block malloc failed (inline_block_size='integer')

• The memory allocation for the inline code block failed. Try freeing up memory or reducing the size of the inline blocks (inline_block_size global variable). See gldcore/load.c(235).

command line option 'string' is not recognized

• The command line option given is not valid where it was found. Check the command line for correct syntax and order of options. See gldcore/cmdarg.c(1467).

commit_all() failure: 'string'

• The commit'ing procedure failed. This is usually preceded by a more detailed message that explains why it failed. Follow the guidance for that message and try again. See gldcore/exec.c(1172).

compare op 'integer' not supported on doubles

• This error is caused when an object find procedure uses a comparison operator that isn't allowed on a that type of property. Make sure the property type and the comparison operator are compatible and try again. If your GLM file isn't the cause of the problem, try reducing the complexity of the GLM file you are using to isolate which module is causing the error and file a report with the GLM file attached. See gldcore/find.c(110).

compare op 'integer' not supported on integers

• This error is caused when an object find procedure uses a comparison operator that isn't allowed on a that type of property. Make sure the property type and the comparison operator are compatible and try again. If your GLM file isn't the cause of the problem, try reducing the complexity of the GLM file you are using to isolate which module is causing the error and file a report with the GLM file attached. See gldcore/find.c(37).
• This error is caused when an object find procedure uses a comparison operator that isn't allowed on a that type of property. Make sure the property type and the comparison operator are compatible and try again. If your GLM file isn't the cause of the problem, try reducing the complexity of the GLM file you are using to isolate which module is causing the error and file a report with the GLM file attached. See gldcore/find.c(64).
• This error is caused when an object find procedure uses a comparison operator that isn't allowed on a that type of property. Make sure the property type and the comparison operator are compatible and try again. If your GLM file isn't the cause of the problem, try reducing the complexity of the GLM file you are using to isolate which module is causing the error and file a report with the GLM file attached. See gldcore/find.c(87).

compare op 'integer' not supported on strings

• This error is caused when an object find procedure uses a comparison operator that isn't allowed on a that type of property. Make sure the property type and the comparison operator are compatible and try again. If your GLM file isn't the cause of the problem, try reducing the complexity of the GLM file you are using to isolate which module is causing the error and file a report with the GLM file attached. See gldcore/find.c(147).

comparison operators not supported for property type 'string'

• This error is caused when an object find procedure uses a comparison operator that isn't allowed on a that type of property. Make sure the property type and the comparison operator are compatible and try again. If your GLM file isn't the cause of the problem, try reducing the complexity of the GLM file you are using to isolate which module is causing the error and file a report with the GLM file attached. See gldcore/find.c(238).

compound unit 'string' could not be correctly identified

• The given unit had a recognized scalar prefix, but the underlying base unit was not identified. This will cascade a null pointer to the calling method. See gldcore/unit.c(154).

connection::preupdate: deltamode_timestep must be a positive, non-zero number!

• The value for global_deltamode_timestep, must be a positive, non-zero number. Please use such a number and try again. See connection/init.cpp(131).

convergence iteration limit reached at 'string' (exec)

• This indicates that the core's solver was unable to determine a steady state for all objects for any time horizon. Identify the object that is causing the convergence problem and contact the developer of the module that implements that object's class. See gldcore/exec.c(2325).

convergence iteration limit reached for object 'string' (debug)

• This indicates that the core's solver was unable to determine a steady state for all objects for any time horizon. Identify the object that is causing the convergence problem and contact the developer of the module that implements that object's class. See gldcore/debug.c(1463).

convergence iteration limit reached for object 'string':'integer'

• This indicates that the core's solver was unable to determine a steady state for all objects for any time horizon. Identify the object that is causing the convergence problem and contact the developer of the module that implements that object's class. See gldcore/exec.c(536).

convergence iteration limit reached for object 'string':'integer' (test)

• This indicates that one of the objects in the simulator has encountered a state where it cannot calculate the time to the next state. This usually is caused by a bug in the module that implements that object's class. See gldcore/exec.c(2559).

convert_from_complex(): unable to convert unit 'string' to 'string' for property 'string' (tape experiment error)

• This is an error with the conversion of units from the complex property's units to the requested units. Please double check the units of the property and compare them to the units defined in the offending tape object. See gldcore/convert.cpp(155).

convert_to_complex('string','string'): complex number format is not valid

• A complex number was given that doesn't meet the formatting requirements, e.g., <+/->. Check the format of your complex numbers and try again. See gldcore/convert.cpp(216).

convert_to_double(const char *buffer='string', void *data=0x%*p, PROPERTY *prop={name='string',...}): unit conversion failed

• This error is caused by an attempt to convert a value from a unit that is incompatible with the unit of the target property. Check your units and try again. See gldcore/convert.cpp(120).
• This error is caused by an attempt to convert a value from a unit that is incompatible with the unit of the target property. Check your units and try again. See gldcore/convert.cpp(239).

could not find 'from' unit 'string' for unit_convert

• The specified unit name was not found by the unit system. Verify that it is a valid unit name. See gldcore/unit.c(635).

could not find 'to' unit 'string' for unit_convert

• The specified unit name was not found by the unit system. Verify that it is a valid unit name. See gldcore/unit.c(629).

could not run unit_convert_complex due to null arguement

• An error occured earlier in processing that caused a null pointer to be used as an arguement. Review other error messages for details, but either a property was not found, or a unit definition was not found. See gldcore/unit.c(674).

could not run unit_convert_ex due to null arguement

• An error occured earlier in processing that caused a null pointer to be used as an arguement. Review other error messages for details, but either a property was not found, or a unit definition was not found. See gldcore/unit.c(650).

csv_reader could not open \'string'\' for input!

• The specified input file could not be opened for reading. Verify that no other applications are using that file, double-check the input model, and re-run GridLAB-D. See climate/csv_reader.cpp(91).

csv_reader has no input file name!

• No input file was specified for the csv_reader object. Double-check the input model and re-run GridLAB-D. See climate/csv_reader.cpp(80).

csv_reader::read_header ~ unable to find column property \'string'\'

• The specified property in the header was not found published by the weather class. Please check the column header input and re-run GridLAB-D. See climate/csv_reader.cpp(289).

csv_reader::read_line ~ unable to read time string \'string'\' with default format

• The input timestamp could not be parsed. Verify that all time strings are formatted as 'MM:dd:hh:mm:ss', 'MM:dd:hh:mm', 'MM:dd:hh', 'MM:dd', or 'MM'. See climate/csv_reader.cpp(336).

csv_reader::read_line ~ unable to read time string \'string'\' with format \'string'\'

• The input timestamp could not be parsed using the specified time format. Please review the specified file's time format and input time strings. See climate/csv_reader.cpp(346).

csv_reader::read_line ~ unable to set value \'string'\' to double property \'string'\'

• The specified property value could not be parsed as a number. Please check the CSV file for non-numeric characters in the data fields on that line. See climate/csv_reader.cpp(378).

csv_reader::read_prop ~ error reading property & value

• The line was not read properly by the parser. Property lines must be of the format "prop=val". Please review the CSV file and re-run GridLAB-D. See climate/csv_reader.cpp(180).

csv_reader::read_prop ~ missing \'=\' seperator

• Property lines must have the property name and property value seperated by an equals sign. Please correct the CSV file and re-run GridLAB-D. See climate/csv_reader.cpp(171).

csv_reader::read_prop ~ unable to convert property \'string'\' due to type restrictions

• This is a programming problem. The property parser within the csv_reader is only able to properly handle char32 and double properties. Please contact matthew.hauer@pnl.gov for technical support. See climate/csv_reader.cpp(220).

csv_reader::read_prop ~ unable to set property \'string'\' to \'string'\'

• The double parser was not able to convert the property value into a number. Please review the input line for non-numeric characters and re-run GridLAB-D. See climate/csv_reader.cpp(208).

csv_reader::read_prop ~ unrecognized csv_reader property \'string'\'

• The property specified within the CSV file is not published by csv_reader. Please review the list of published variables, correct the CSV file, and re-run GridLAB-D. See climate/csv_reader.cpp(190).

delegated types not supported using class_define_type (use class_define_map instead)

• Property delegation is not supported yet so this should never happen. This is most likely caused by a lack of memory or an unstable system. See gldcore/class.c(1258).

delta mode initialization failed

• The initialization of the deltamode subsystem failed. The failure message is preceded by one or more errors that will provide more information. See gldcore/exec.c(1885).

delta_preupdate(): module 'string' failed

• A module failed to complete an preupdate correctly while operating in deltamode. Generally, this is an internal error and should be reported to the GridLAB-D developers. See gldcore/deltamode.c(535).

delta_update() failed, deltamode operation cannot continue

• An error was encountered while trying to perform a deltamode update. Look for other relevant deltamode messages for indications as to why this may have occurred. If the error persists, please submit your code and a bug report via the trac website. See gldcore/exec.c(2349).

delta_update(): clockupdate failed

• * A module failed to complete an clockupdate correctly while operating in deltamode. * Generally, this is an internal error and should be reported to the GridLAB-D developers. See gldcore/deltamode.c(451).

delta_update(): delta_interupdate() wanted to exit deltamode. However, delta_clockupdate() wanted to continue in deltamode. This shouldn't happen. Please check your object's delta_clockupdate function to determine what went wrong.

• While performing the interupdate portion of the deltamode updates, all objects determined that it was ok to exit deltamode. When this is the case, objects delta_clockupdate can only return DELTA_ITER indicating that there needs to be a reiteration of the current deltamode timestep or EVENT indicating that the simulation can exit deltamode. Please check your object's delat_clockupdate function to make sure it adhere's to this behavior. See gldcore/deltamode.c(420).

delta_update(): delta_interupdate() wanted to move to the next deltamode timestep. However, delta_clockupdate() wanted to exit deltamode. This shouldn't happen. Please check your object's delta_clockupdate function to determine what went wrong.

• While performing the interupdate portion of the deltamode updates, all objects determined that it was ok move to the next deltamode timestep. When this is the case, objects delta_clockupdate can only return DELTA_ITER indicating that there needs to be a reiteration of the current deltamode timestep or DELTA indicating that the simulation can move to the next deltamode timestep. Please check your object's delta_clockupdate function to make sure it adhere's to this behavior. See gldcore/deltamode.c(436).

delta_update(): interupdate failed

• A module failed to complete an interupdate correctly while operating in deltamode. Generally, this is an internal error and should be reported to the GridLAB-D developers. See gldcore/deltamode.c(358).

delta_update(): interupdate federation iteration limit reached

• While performing the clockupdate portion of the deltamode updates, too many federate reiterations were requested, so the simulation failed to progress forward. You can increase the iteration count with the global variable deltamode_iteration_limit. See gldcore/deltamode.c(463).

delta_update(): interupdate iteration limit reached

• While performing the interupdate portion of the deltamode updates, too many reiterations were requested, so the simulation failed to progress forward. You can increase the iteration count with the global variable deltamode_iteration_limit. See gldcore/deltamode.c(401).

delta_update(): postupdate failed

• A module failed to complete an postupdate correctly while operating in deltamode. Generally, this is an internal error and should be reported to the GridLAB-D developers. See gldcore/deltamode.c(505).

delta_update(): preupdate failed

• A module failed to complete a preupdate operation correctly while operating in deltamode. Generally, this is an internal error and should be reported to the GridLAB-D developers. See gldcore/deltamode.c(260).

delta_update(): update failed for object \'string'\'

• An object failed to update correctly while operating in deltamode. Generally, this is an internal error and should be reported to the GridLAB-D developers. See gldcore/deltamode.c(337).

deltamode player: player \

• Starting a player with a deltamode timestep causes segmentation faults. A fix was developed, but still has issues with certain platforms and must be investigated further. For now, start all player files with non-deltamode timesteps. This issues is documented at #1001 on the GridLAB-D Git site, and it expected to be resolved in release 4.1. See tape/tape.c(574).

details command syntax error

• The details debugger command support only one option, but somehow more than one option was read. Check the syntax and try again. See gldcore/debug.c(618).

diesel_dg: failed to allocate to allocate the delayed torque array for Governor!

• The diesel_dg object failed to allocate the memory needed for the delayed torque array inside the governor control. Please try again. If the error persists, please submit your code and a bug report via the trac website. See generators/diesel_dg.cpp(2101).

diesel_dg: failed to allocate to allocate the delayed x5a array for Governor!

• The diesel_dg object failed to allocate the memory needed for the delayed x5a array inside the governor control. Please try again. If the error persists, please submit your code and a bug report via the trac website. See generators/diesel_dg.cpp(2145).

dump to 'string' failed

• An attempt to create a dump file failed. This message should be preceded by a more detailed message explaining why if failed. Follow the guidance for that message and try again. See gldcore/environment.c(56).

Error from GetParametersSingleElement(): 'string'

• The call to GetParametersSingleElement failed. Please review the error message and respond accordingly. Addition COM-related error handling may be found on the MSDN website. See network/pw_load.cpp(198).
• The call to GetParametersSingleElement failed. Please review the error message and respond accordingly. Addition COM-related error handling may be found on the MSDN website. See network/pw_load.cpp(298).
• The call to GetParametersSingleElement failed. Please review the error message and respond accordingly. Addition COM-related error handling may be found on the MSDN website. See network/pw_load.cpp(421).
• The call to GetParametersSingleElement failed. Please review the error message and respond accordingly. Addition COM-related error handling may be found on the MSDN website. See network/pw_recorder.cpp(482).

Error from SetParametersSingleElement(): 'string'

• The call to SetParametersSingleElement failed. Please review the error message and respond accordingly. Addition COM-related error handling may be found on the MSDN website. See network/pw_load.cpp(538).

exec_add_breakpoint() - memory allocation failed

• The add breakpoint debugger command failed because the system ran out of memory. Follow the usual procedure for freeing up memory before trying again. See gldcore/debug.c(378).

exec_add_watchpoint() - memory allocation failed

• The add breakpoint debugger command failed because the system ran out of memory. Follow the usual procedure for freeing up memory before trying again. See gldcore/debug.c(420).

expression(): invalid find op!

• A search rule used a term that isn't valid. Check the search rule syntax and try again. See gldcore/find.c(1025).

Failed to allocate battery array.

• While trying to allocate the array of pointers to the controlled batteries, the pointer array came back null. See generators/central_dg_control.cpp(154).
• While trying to allocate the array of pointers to the controlled inverters with battery children, the pointer array came back null. See generators/central_dg_control.cpp(172).

Failed to allocate inverter array.

• While trying to allocate the array of pointers to the controlled inverters, the pointer array came back null. See generators/central_dg_control.cpp(145).

Failed to allocate solar array.

• While trying to allocate the array of pointers to the controlled solars, the pointer array came back null. See generators/central_dg_control.cpp(163).
• While trying to allocate the array of pointers to the controlled inverters with solar children, the pointer array came back null. See generators/central_dg_control.cpp(181).

Failed to perform postupdate for group_recorder object

• While trying to perform the final write for a group recorder deltamode call, an error occurred. Please look at the output console for more details. See tape/tape.c(782).

Failed to swap SWING status of node:'string' on inverter:'string'

• While attempting to handle special reliability actions on a "special" device (switch, recloser, etc.), the function required failed to execute properly. If the problem persists, please submit a bug report and your code to the trac website. See generators/inverter.cpp(5125).

fault_check:'integer' 'string' -- Special debug mode utilized, simulation terminating

• The special "SINGLE_DEBUG" mode has been activated in fault_check. This performs a topology check ignoring some of the phase checking built into powerflow. This is meant only for debugging topological issues, so the simulation is terminated prematurely, regardless of if any issues were found or not. See powerflow/fault_check.cpp(373).

federation convergence iteration limit reached at 'string' (exec)

• This indicates that the federation that this gridlab-d model a part of was unable to determine a steady state any time horizon. See gldcore/exec.c(2311).

finalize_all() failure: 'string'

• The finalizing procedure failed. This is usually preceded by a more detailed message that explains why it failed. Follow the guidance for that message and try again. See gldcore/exec.c(1239).

find expression on 'string' not supported

• A search criteria attempted to search on the flags of an object, which is supported yet. Remove the "flags" criteria and try again. See gldcore/find.c(1249).

find expression refers to unknown or unsupported property 'string'

• A search criteria used an expression that isn't recognized. Fix the search rule and try again. See gldcore/find.c(1256).

findtype 'string' not supported

• This error is caused when an object find procedure uses a comparison operator that isn't allowed on a that header item. Make sure the header item and the comparison operator are compatible and try again. If your GLM file isn't the cause of the problem, try reducing the complexity of the GLM file you are using to isolate which module is causing the error and file a report with the GLM file attached. See gldcore/find.c(265).

Generator deltamode update - failed to link to powerflow frequency

• While performing a deltamode update, mapping the current powerflow frequency value failed. Please try again. If the error persists, please submit a bug report via the trac website. See generators/init.cpp(361).

Generator object:'string' - deltamode function returned an error!

• While performing a deltamode update, one object returned an error code. Check to see if the object itself provided more details and try again. If the error persists, please submit your code and a bug report via the trac website. See generators/init.cpp(290).

Generator object:'string' - failed post-deltamode update

• While calling the individual object post-deltamode calculations, an error occurred. Please try again. If the error persists, please submit your code and a bug report via the trac website. See generators/init.cpp(390).

generators::deltamode_timestep must be a positive, non-zero number!

• The value for deltamode_timestep, as specified as the module level in generators, must be a positive, non-zero number. Please use such a number and try again. See generators/init.cpp(194).

get_market_for_time() was called with a null object pointer

• The call was made without specifying the object that called it. Double-check the code where this method was called and verify that a non-null object pointer is passed in. See market/auction.cpp(34).

global variable definition 'string' not formatted correctedly

• A request to set a global variable was not formatted properly. Use the proper format, i.e. name=value, and try again. See gldcore/globals.c(597).

global_block malloc failed (inline_block_size='integer')

• The memory allocation for the inline global code block failed. Try freeing up memory or reducing the size of the inline blocks (inline_block_size global variable). See gldcore/load.c(248).

global_init(): global variable 'string' registration failed

• The global variable initialization process was unable to register the indicated global variable. This error usually follows a more detailed explanation of the error. Follow the troubleshooting for that message and try again. See gldcore/globals.c(298).

global_setvar(): unable to set 'string' to 'string'

• The input value was not convertable into the desired type for the input variable. Check the input range, review the input file, and adjust the input value appropriately. See gldcore/globals.c(582).

global_setvar(char *name='string',...): value is too long to store

• An attempt to set a global variable failed because the value of the variable was too long. See gldcore/globals.c(540).

group_recorder::commit(): the object has error'ed and is halting the simulation

• In strict mode, any group_recorder logic errors or input errors will halt the simulation. See tape/group_recorder.cpp(271).
• In strict mode, any group_recorder logic errors or input errors will halt the simulation. See tape/group_recorder.cpp(350).

group_recorder::flush_line(): output file is not open

• group_recorder claimed to be open and attempted to flush to a file when a file had not successfully opened. See tape/group_recorder.cpp(637).

group_recorder::flush_line(): unable to flush output file

• An IO error has occured. See tape/group_recorder.cpp(646).

group_recorder::init(): an error occured when writing the file header

• Unexpected IO error. See mysql/group_recorder.cpp(208).
• Unexpected IO error. See tape/group_recorder.cpp(183).

group_recorder::init(): invalid write_interval of 'integer', must be -1 or greater

• The group_recorder interval must be -1, 0, or a positive number of seconds. See mysql/group_recorder.cpp(142).
• The group_recorder interval must be -1, 0, or a positive number of seconds. See tape/group_recorder.cpp(96).

group_recorder::init(): no group defined

• group_recorder must define a group in "group_def". See mysql/group_recorder.cpp(128).
• group_recorder must define a group in "group_def". See tape/group_recorder.cpp(65).

group_recorder::init(): the defined group returned an empty set

• Placeholder. See mysql/group_recorder.cpp(167).
• Placeholder. See tape/group_recorder.cpp(125).

group_recorder::init(): unable to construct a set with group definition

• An error occured while attempting to build and populate the find list with the specified group definition. See mysql/group_recorder.cpp(155).
• An error occured while attempting to build and populate the find list with the specified group definition. See tape/group_recorder.cpp(112).

group_recorder::init(): unable to find property 'string' in an object of type 'string'

• An error occured while reading the specified property in one of the objects. See mysql/group_recorder.cpp(185).
• An error occured while reading the specified property in one of the objects. See tape/group_recorder.cpp(159).

group_recorder::read_line(): malloc failure

• Memory allocation failure. See tape/group_recorder.cpp(448).

group_recorder::read_line(): potential buffer overflow from a too-short automatically sized output value buffer

• A potential buffer overflow was caught, most likely due to incorrect property representation assumptions for buffer allocation. See tape/group_recorder.cpp(515).

group_recorder::read_line(): unable to get complex property 'string' from object 'string'

• Could not read a complex property as a complex value. See tape/group_recorder.cpp(473).
• Could not read a complex property as a complex value. See tape/violation_recorder.cpp(1092).
• Could not read a complex property as a complex value. See tape/violation_recorder.cpp(1112).

group_recorder::read_line(): unable to get value for 'string' in object 'string'

• An error occured while reading the specified property in one of the objects. See tape/group_recorder.cpp(506).

group_recorder::sync

• Placeholder. See tape/group_recorder.cpp(217).

group_recorder::sync(): error when writing the values to the file

• Placeholder. See tape/group_recorder.cpp(251).

group_recorder::write_footer(): output file is not open

• group_recorder claimed to be open and attempted to write to a file when a file had not successfully opened. See tape/group_recorder.cpp(666).

group_recorder::write_header(): the output file was not opened

• group_recorder claimed to be open and attempted to write to a file when a file had not successfully opened. See tape/group_recorder.cpp(379).

group_recorder::write_line(): error when converting the sync time

• Unprintable timestamp. See tape/group_recorder.cpp(572).
• Unprintable timestamp. See tape/group_recorder.cpp(584).

group_recorder::write_line(): error when writing the sync time as a string

• Error printing the timestamp. See tape/group_recorder.cpp(595).

group_recorder::write_line(): error when writing to the output file

• File I/O error. See tape/group_recorder.cpp(615).

group_recorder::write_line(): no output file open and state is 'open'

• group_recorder claimed to be open and attempted to write to a file when a file had not successfully opened. See tape/group_recorder.cpp(545).

group_recorder::write_line(): output buffer not initialized (read_line() not called)

• read_line was not called before write_line, indicating an internal logic error. See tape/group_recorder.cpp(556).

House thermal mass or UA invalid. Eigen values not set.

• The house envelope_UA, mass_heat_coeff, or floor_area have not been set to legitimate values. Please review these properties and set them to values greater than 1e-6. See residential/house_a.cpp(835).

house: thermostat setpoints deadbands overlap (TcoolOff='real' < TheatOff='real')

• The house models the thermostat with explicit heating and cooling on and off points, dependent on the device setpoints and the thermostat's activation deadband. If the heating and cooling points are too close to each other, the device will not emulate a real thermostat. To remedy this error, either make the thermostat deadband smaller, or set the heating and cooling setpoints further apart. See residential/house_a.cpp(520).

house:'integer' 'string'; using static voltages

• The House model relies on a triplex_meter as a parent to calculate voltages based on events within the powerflow module. Create a triplex_meter object and set it as the parent of the house object. See residential/house_a.cpp(347).

house:'integer' - 'string' - Failed to map powerflow variable

• While attempting to map the house variables to the required powerflow variables, an error occurred. Please try again. If the error persists, please submit your code and a bug report via the trac website. See residential/house_e.cpp(1298).

ignored signal 'integer'

• A signal was received that is not handled. This is not serious, but may indicate that a behavior was expected by another application that GridLAB-D does not support. If this is unexpected, make sure that the signal is not being raised accidentally by another application. See gldcore/debug.c(325).

inactive command syntax error

• The inactive debugger command support only one option, but somehow more than one option was read. Check the syntax and try again. See gldcore/debug.c(645).

init failure: 'string'

• The initialization procedure failed. This is usually preceded by a more detailed message that explains why it failed. Follow the guidance for that message and try again. See gldcore/exec.c(612).

init(): Rated Insolation was not specified (or zero). Power outputs cannot be calculated without a rated insolation value.

• The relationship between power output and other physical variables is described by Rated_kVA = Rated_Insolation * efficiency * area. Rated_kVA and Rated_Insolation are required values for the solar model. Please specify both of these parameters or efficiency and area. See generators/solar.cpp(628).

init_all(): object 'string' initialization failed

• The initialization of the named object has failed. Make sure that the object's requirements for initialization are satisfied and try again. See gldcore/exec.c(591).

init_block malloc failed (inline_block_size='integer')

• The memory allocation for the inline init block failed. Try freeing up memory or reducing the size of the inline blocks (inline_block_size global variable). See gldcore/load.c(261).

instance_cnx_mmap: no instance provided

• There was an internal error that was not caught prior to attempting to construct the message-passing layer without an instance for context. See gldcore/instance_cnx.c(14).

invalid breakpoint number

• The break disable command specified a breakpoint number that doesn't exist. Check the list of breakpoints and try again. See gldcore/debug.c(933).

invalid debug command, try 'help'

• The debug command given is not recognized. Use the help to check the command syntax and try again. See gldcore/debug.c(1261).

invalid debug state

• The debugger has entered a state the indicates the system has become unstable. Please submit a problem report to the core development and include both the input and output files, including the XML dump file. See gldcore/debug.c(1402).

invalid findtype means search is specified incorrectly or FT_END is probably missing

• The search rule is invalid because it contains a term that isn't recognized or the search rule is not correctly terminated by the FT_END term. Check the syntax of the search rule and try again. If the search rule comes from a module, report the problem. See gldcore/find.c(464).

invalid object or value

• The set debug command was unable to set the specified property either because the object could not be found, or the value given could not be converted to the type required for the property. Check the command syntax and try again. See gldcore/debug.c(1181).

invalid property for object 'string'

• This error should not occur and in harmless. If it does occur, please report the problem to the core development team. See gldcore/debug.c(1174).

invalid time

• The break time specifies a timestamp that isn't valid. Check the command syntax and try again. See gldcore/debug.c(909).

invalid watchpoint number

• The watch command refers to a watchpoint that doesn't exist. Check the list of watchpoints and try again. See gldcore/debug.c(1020).

Inverter 1547 Checks - invalid state!

• While performing the IEEE 1547-2003 frequency and voltage checks, an unknown state occurred. Please try again. If the error persists, please submit you GLM and a bug report via the ticketing system. See generators/inverter.cpp(8054).

Inverter failed pre_deltaupdate call

• While attempting to call the pre_deltaupdate portion of the inverter code, an error was encountered. Please submit your code and a bug report via the ticketing system. See generators/inverter.cpp(5092).

Inverter:'integer' 'string' failed to map the nominal_voltage property

• While attempting to map the nominal_voltage property, an error occurred. Please try again. If the error persists, please submit your GLM and a bug report to the ticketing system. See generators/inverter.cpp(835).
• While attempting to map the nominal_voltage property, an error occurred. Please try again. If the error persists, please submit your GLM and a bug report to the ticketing system. See generators/inverter.cpp(7815).

inverter:'string' - charge_lockout_time is negative!

• The charge_lockout_time for the inverter is negative. Negative lockout times are not allowed inside the inverter. Please correct the value and try again. See generators/inverter.cpp(1458).

inverter:'string' - discharge_lockout_time is negative!

• The discharge_lockout_time for the inverter is negative. Negative lockout times are not allowed inside the inverter. Please correct the value and try again. See generators/inverter.cpp(1478).

inverter:'string' - inverter failed to map power calculation function of transformer!

• While attempting to link up the power_calculation function for the transformer specified in sense_object, something went wrong. Please try again. If the error persists, please post your code and a bug report via the trac website. See generators/inverter.cpp(1378).

inverter:'string' - LOAD_FOLLOWING and power-factor regulation will not work without a specified sense_object!

• The inverter is currently configured for LOAD_FOLLOWING mode, but does not have an appropriate sense_object specified. Please specify a proper object and try again. See generators/inverter.cpp(1312).

inverter:'string' - sense_object is a link, but not a transformer!

• When in LOAD_FOLLOWING and the sense_object is a powerflow link, that powerflow object must be a transformer. Please change your model and try again. See generators/inverter.cpp(1400).

inverter:'string' - sense_object is a node, but not a meter or triplex_meter!

• When in LOAD_FOLLOWING and the sense_object is a powerflow node, that powerflow object must be a meter or a triplex_meter. Please change your model and try again. See generators/inverter.cpp(1356).

inverter:'string' - sense_object is not a proper powerflow object!

• When in LOAD_FOLLOWING mode, the inverter requires an appropriate connection to a powerflow object to sense the current load. This can be either a meter, triplex_meter, or transformer at the current time. See generators/inverter.cpp(1411).

inverter:'string' -- Failed to find node swing swapper function

• While attempting to map the function to change the swing status of the parent bus, the function could not be found. Ensure the inverter is actually attached to something. If the error persists, please submit your code and a bug report via the ticketing/issues system. See generators/inverter.cpp(5110).

Latitude beyond the currently supported range 24 - 48 N, Simulations will continue assuming latitude 'real'N

• GridLAB-D currently only supports latitudes within a temperate band in the northern hemisphere for the building models. Latitudes outside 24N to 48N may not correctly calculate solar input. See residential/house_a.cpp(429).

lights parent must publish \'floor_area\' to work properly if no installed_power is given ~ default 2500 sf

• The lights did not reference a parent object that publishes a floor are, so 2500 sf was assumed. Change the parent reference and try again. See residential/lights.cpp(174).

market latency queue is overwriting as-yet unused data, so is not long enough or is not consuming data

• This is indicative of problems with how the internal circular queue is being handled. Please report this error on the GridLAB-D TRAC site. See market/auction.cpp(632).

maximum number of allowed schedule blocks exceeded

• Up to 4 schedule blocks are allowed. Define your schedule so it only uses four blocks and try again. See gldcore/schedule.c(724).

metrics_collector allows only these parents: triplex meter, house, waterheater, inverter, substation, meter, capacitor, regulator

• Check the parent object of the metrics_collector. See tape/metrics_collector.cpp(213).

metrics_collector must have a parent (triplex meter, house, waterheater, inverter, substation, or meter)

• Check the parent object of the metrics_collector. See tape/metrics_collector.cpp(127).

metrics_collector must have a triplex meter, house, waterheater, inverter, swing-bus, capacitor or regulator as its parent

• Check the parent object of the metrics_collector. The metrics_collector is only able to be childed via a triplex meter or a house or a waterheater or an inverter or a swing-bus when connecting into powerflow systems. See tape/metrics_collector.cpp(776).

metrics_collector must have a triplex meter, meter, house, waterheater, inverter or swing-bus as its parent

• Check the parent object of the metrics_collector. The metrics_collector is only able to be childed via a triplex meter or a house or an inverter when connecting into powerflow systems. See tape/metrics_collector.cpp(598).

metrics_collector::init(): invalid interval of 'integer', must be greater than 0

• The metrics_collector interval must be a positive number of seconds. See tape/metrics_collector.cpp(331).

metrics_collector_writer::init(): error when converting the starting time

• Unprintable timestamp. See tape/metrics_collector_writer.cpp(118).

metrics_collector_writer::init(): error when writing the starting time as a string

• Error printing the timestamp. See tape/metrics_collector_writer.cpp(125).

metrics_collector_writer::init(): invalid interval of 'integer', must be greater than 0

• The metrics_collector interval must be a positive number of seconds. See tape/metrics_collector_writer.cpp(74).

missing file name for script command

• The script command requires a filename, but non was provided in the command. Identify the file and try again. See gldcore/debug.c(711).

model initialization failed

• The initialization procedure failed. This is usually preceded by a more detailed message that explains why it failed. Follow the guidance for that message and try again. See gldcore/exec.c(1762).

model_commit_failed

• The commit procedure failed. This is usually preceded by a more detailed message that explains why it failed. Follow the guidance for that message and try again. See gldcore/exec.c(2290).

module 'string' cannot register class 'string', it is already registered by module 'string'

• This error is caused by an attempt to define a new class which is already defined in the module or namespace given. This is generally caused by bug in a module or an incorrectly defined class. See gldcore/class.c(444).

module 'string' does not exist

• The break module refers to a module that does not exist. Identify the correct name of the module and try again. See gldcore/debug.c(848).

module 'string' load failed - invalid DLL format

• GridLAB-D and MinGW are not compatible. Most likely the 32-bit version of MinGW is installed on a 64-bit machine running the 64-bit version of GridLAB-D. Try installing MinGW64 instead. See gldcore/module.c(408).

module 'string' not found

• A search rule specified a module that hasn't been loaded. Check the module name to make sure it's been loaded and try again. See gldcore/find.c(1083).

module 'string' return invalid/infinite dt for delta mode inquiry

• A module returned an invalid time-difference for deltamode operation. Generally, this is an internal error and should be reported to the GridLAB-D developers. See gldcore/deltamode.c(222).

module_load(file='string'::'string'): subload failed

• A module is unable to load a submodule require for operation. Check that the indicated submodule is installed and try again. See gldcore/module.c(311).

mti_init memory allocation failed

• Memory allocation failed initialize a multithreaded iterator. Free up memory and try again. See gldcore/threadpool.c(221).

Newton-Raphson failed to converge the dynamic powerflow, sticking at same iteration.

• Newton-Raphson failed to converge the dynamic powerflow in the number of iterations specified in NR_iteration_limit. It will try again (if the global iteration limit has not been reached). See powerflow/init.cpp(374).

Newton-Raphson method is unable to converge the dynamic powerflow to a solution at this operation point

• Newton-Raphson has failed to complete even a single iteration on the dynamic powerflow. This is an indication that the method will not solve the system and may have a singularity or other ill-favored condition in the system matrices. See powerflow/init.cpp(363).

No batteries with inverter parents with given group id found.

• While trying to put together a list of all battery objects with parent inverter objects with the specified controller groupid, no such battery objects were found. See generators/central_dg_control.cpp(126).

No inverters with given group id found.

• While trying to put together a list of all inverter objects with the specified controller groupid, no such inverter objects were found. See generators/central_dg_control.cpp(116).

No line or bus objects were found.

• No line or bus objects were found in your .glm file. if you specified a group id double check to make sure you have line objects with the specified group id. See powerflow/jsondump.cpp(203).

no solars with inverter parents with given group id found.

• While trying to put together a list of all solar objects with parent inverter objects with the specified controller groupid, no such solar objects were found. See generators/central_dg_control.cpp(135).

Node frequency update: unknown state encountered

• While running the frequency/angle estimation routine for a node object, it somehow entered an unknown state. Please try again. If the error persists, please submit your GLM and a bug report via the ticketing system. See powerflow/node.cpp(4589).

Node'integer' 'string' GFA checks failed- invalid state!

• While performing the GFA update on the node, it entered an unknown state. Please try again. If the error persists, please submit your code and a bug report via the ticketing system. See powerflow/node.cpp(4789).

node:'integer' ('string') has more phases leaving than entering

• A node has more phases present than it has sources coming in. This scenario implies an unconnected phases between the from and to nodes of a connected line. Please adjust the phases appropriately. Also be sure no open switches are the sole connection for a phase, else this will fail as well. In a few NR circumstances, this can also be seen if the "from" and "to" nodes are in reverse order - the "from" node of a link object should be nearest the SWING node, or the node with the most phases - this error check will be updated in future versions. See powerflow/node.cpp(1459).

node:'integer' - 'string' - Already has an extra current injection function mapped

• An object attempted to map a current injection update function, but that node already has such a function mapped. Only one is allowed per node. Note this includes any attachments to child nodes, since those end up on the parent object. See powerflow/node.cpp(5168).

node:'integer' - 'string' - Failed to map current_injection_update from calling object:'integer' - 'string'

• The attached node was unable to find the exposed function "current_injection_update" on the calling object. Be sure it supports this functionality and try again. See powerflow/node.cpp(5153).

node:'integer' - 'string' - Parent node:'integer' - 'string' - Already has an extra current injection function mapped

• An object attempted to map a current injection update function to its parent, but that node already has such a function mapped. Only one is allowed per node. Note this includes any attachments to child nodes, since those end up on the parent object. See powerflow/node.cpp(5203).

Nominal voltages of tranmission node ('real' V) and substation ('real') do not match!

• The nominal voltage of the transmission node in PowerWorld does not match that of the value inside GridLAB-D's substation's nominal_voltage. This could cause information mismatch and is therefore not allowed. Please set the substation to the same nominal voltage as the transmission node. Use transformers to step the voltage down to an appropriate distribution or sub-transmission level. See powerflow/substation.cpp(197).

NR: 'string' tried to parent to a node that has too many children already

• While trying to link a child to its parent, a memory overrun was encountered. Please try again. If the error persists, please submit you code and a bug report via the trac website. See powerflow/node.cpp(1563).

NR: memory allocation failure for branch table

• This is a bug. GridLAB-D failed to allocate memory for the link table for Newton-Raphson. Please submit this bug and your code. See powerflow/node.cpp(1613).

NR: memory allocation failure for bus table

• This is a bug. GridLAB-D failed to allocate memory for the bus table for Newton-Raphson. Please submit this bug and your code. See powerflow/node.cpp(1593).

nsync command syntax error

• The nsync debugger command support only one option, but somehow more than one option was read. Check the syntax and try again. See gldcore/debug.c(699).

object 'string' does not exist

• The break error refers to an object that does not exist. Find the correct object name and try again. See gldcore/debug.c(827).

object 'string' does not have a property named 'string'

• The watch command refers to an object property that isn't defined. Check the list of properties for that class of object and try again. See gldcore/debug.c(1061).

object 'string' finalize failed

• The finalize function of the named object has failed. Make sure that the object's requirements for finalizing are satisfied and try again. (likely internal state aberations) See gldcore/exec.c(1227).

object 'string' finalize memory allocation failed

• Insufficient memory remains to perform the finalize operation. Free up memory and try again. See gldcore/exec.c(1205).

object 'string' precommit failed

• The precommit function of the named object has failed. Make sure that the object's requirements for precommit'ing are satisfied and try again. (likely internal state aberations) See gldcore/exec.c(959).

object 'string' precommit memory allocation failed

• Insufficient memory remains to perform the precommit operation. Free up memory and try again. See gldcore/exec.c(935).

object 'string' undefined

• The print command refers to an object that doesn't exist. Check the list of objects and try again. See gldcore/debug.c(1124).

object 'string':'integer' called set_header_value() for invalid field 'string'

• The valid header fields are "name", "parent", "rank", "clock", "valid_to", "latitude", "longitude", "in_svc", "out_svc", "heartbeat", and "flags". See gldcore/object.c(975).

object 'string':'integer' latitude 'string' is invalid

• Latitudes are expected to be in the format of X{N,S, }Y'Z". The seconds may be excluded. If the seconds are excluded, minutes may be excluded. If minutes are excluded, the north/south indicator may be excluded. There must be only one space between the degree value and the minute value. Negative degrees are valid. See gldcore/object.c(883).

object 'string':d longitude 'string' is invalid

• Latitudes are expected to be in the format of X{E,W, }Y'Z". The seconds may be excluded. If the seconds are excluded, minutes may be excluded. If minutes are excluded, the north/south indicator may be excluded. There must be only one space between the degree value and the minute value. Negative degrees are valid. See gldcore/object.c(899).

object 'string':d name already set to 'string'

• Object definitions within model files may only have name specifiers once. They may not be named multiple times within the object file. See gldcore/object.c(820).

object dump failed

• The print was unable to complete the dump of the specified object because of an internal error. Follow the guidance for the message that precedes this message and try again. See gldcore/debug.c(1105).

object id 'integer' not found

• A search rule specified an object id that doesn't exist. Check the object list to make it exists and try again. See gldcore/find.c(1101).

occupantload must have a parent house

• The occupantload object, being an enduse for the house model, must have a parent house that it is connected to. Create a house object and set it as the parent of the offending occupantload object. See residential/occupantload.cpp(83).

occupantload parent must publish attach_enduse()

• The occupantload object attempt to attach itself to its parent, which must implement the attach_enduse function. See residential/occupantload.cpp(97).

OpenCase() failed

• PowerWorld failed to open the case specified. Please ensure the case exists, is a valid PowerWorld file, and that it is located in the proper folder and try again. See network/pw_model.cpp(230).

parent 'string' not found

• A search rule specified a parent that isn't defined. Check the parent name and try again. See gldcore/find.c(1129).

Powerflow object:'integer' - 'string' - deltamode function returned an error!

• While performing a deltamode update, one object returned an error code. Check to see if the object itself provided more details and try again. If the error persists, please submit your code and a bug report via the trac website. See powerflow/init.cpp(439).

Powerflow object:'string' - failed post-deltamode update

• While calling the individual object post-deltamode calculations, an error occurred. Please try again. If the error persists, please submit your code and a bug report via the issues system. See powerflow/init.cpp(556).

powerflow::deltamode_timestep must be a positive, non-zero number!

• The value for deltamode_timestep, as specified as the module level in powerflow, must be a positive, non-zero number. Please use such a number and try again. See powerflow/init.cpp(228).

powerworld_bus_num must be a non-negative integer

• PowerWorld uses positive integers for bus numbers. The pw_load object must connect to a valid bus, requiring a valid bus number. See network/pw_load.cpp(601).

powerworld_load_id must be set

• PowerWorld uses a short string for load IDs. The pw_load object must connect to a valid load, requiring a load ID be defined. See network/pw_load.cpp(608).

precommit_all() failure: 'string'

• The precommit'ing procedure failed. This is usually preceded by a more detailed message that explains why it failed. Follow the guidance for that message and try again. See gldcore/exec.c(972).

property 'string' of 'string' is cannot be set like an int16

• The specified property was not an int16. See gldcore/object.c(1037).

property type 'string' not recognized in enduse_publish

• The enduse_publish structure is not defined correctly. This is an internal error and cannot be corrected by users. Contact technical support and report this problem. See gldcore/enduse.c(526).

property_malloc(oclass='string',...): memory allocation failed

• This means that the system has run out of memory while trying to define a class. Trying freeing up some memory by unloading applications or configuring your system so it has more memory. See gldcore/property.c(117).

property_malloc(oclass='string',...): property 'string' cannot have unit 'string' because it is not a double or complex value

• Only double and complex properties can have units. Either change the type of the property or remove the unit specification from the property's declaration. See gldcore/property.c(141).

PT_KEYWORD not allowed unless it follows another property specification

• The enduse_publish structure is not defined correctly. This is an internal error and cannot be corrected by users. Contact technical support and report this problem. See gldcore/enduse.c(483).

PT_KEYWORD not supported after property 'string' 'string' in enduse_publish

• The enduse_publish structure is not defined correctly. This is an internal error and cannot be corrected by users. Contact technical support and report this problem. See gldcore/enduse.c(515).

pw_load::init(): object \'string'\' does not specify a parent model object

• pw_load objects require that a parent object is specified, refering to a pw_model object. See network/pw_load.cpp(576).

pw_load::init(): object \'string'\' specifies a parent object \'string'\' that is not a pw_model object

• pw_load objects require that the specified parent object refers to a pw_model object. Other types are not supported. See network/pw_load.cpp(584).

pw_load::init(): unable to get PowerWorld bus voltage from Bus #'integer', Load ID 'string', for the pw_load \'string'\'

• An error occured while calling a function that retrieves data from PowerWorld. The Bus/Load pair may be incorrect, there may have been a COM error with SimAuto, or other unexpected results may have occured. See network/pw_load.cpp(630).
• An error occured while calling a function that retrieves data from PowerWorld. The Bus/Load pair may be incorrect, there may have been a COM error with SimAuto, or other unexpected results may have occured. See network/pw_load.cpp(639).

pw_load::init(): unable to get PowerWorld nominal voltage from Bus #'integer', for the pw_load \'string'\'

• An error occured while calling a function that retrieves data from PowerWorld. The Bus/Load pair may be incorrect, there may have been a COM error with SimAuto, or other unexpected results may have occured. See network/pw_load.cpp(620).

pw_load::presync(): cModel is null (is deferred initialization enabled?)

• The pw_load object must be parented to a pw_model object and must be ran in deferred initilization mode. Please make sure both of these conditions are true and try again. See network/pw_load.cpp(694).

pw_load::presync(): get_powerworld_busangle failed

• pw_load failed to retrieve the bus angles for the connection point. Please ensure all connection values are correct and try again. See network/pw_load.cpp(705).

pw_load::presync(): get_powerworld_voltage failed

• pw_load failed to retrieve the bus voltages for the connection point. Please ensure all connection values are correct and try again. See network/pw_load.cpp(713).

pw_load::presync(): GPSE failed

• pw_recorder encountered an error when attempting to retrieve a parameter from PowerWorld. Please try again. If the error persists, please submit your code an an error report via the trac website. See network/pw_recorder.cpp(215).

pw_model::init(): no PowerWorld model file specified

• The pw_model requires either a valid PWB model file path, or for an alternate mode to be triggered. Please check the model_name definition, and the path to the desired model file. See network/pw_model.cpp(343).

pw_recorder::build_keys(): 'string' did not parse any key strings

• pw_recorder was unable to parse the key strings specified. Please ensure they are correct and try again. See network/pw_recorder.cpp(307).

pw_recorder::build_keys(): 'string' did not parse any key values

• pw_recorder was unable to parse the key values specified. Please ensure they are correct and try again. See network/pw_recorder.cpp(314).

pw_recorder::build_keys(): 'string' has 'integer' key properties and 'integer' key values listed

• pw_recorder was unable to parse the key properties specified. Please ensure they are correct and try again. See network/pw_recorder.cpp(321).

pw_recorder::init(): error when building keys for 'string'

• An error occurred while building the keys for the pw_recorder. Ensure your property values, key strings, and key values are correct and try again. See network/pw_recorder.cpp(129).

pw_recorder::init(): error when calling GetParameterSingleElement wrapper function for 'string'

• An error occurred while trying to extract a value from PowerWorld. Please check that your key string, key values, and property values are correct and try again. See network/pw_recorder.cpp(144).

pw_recorder::init(): invalid interval in 'string'

• An invalid interval was specified in the pw_recorder. Please specify a value in seconds, 0 (all iterations), or -1 (on change). See network/pw_recorder.cpp(154).

pw_recorder::init(): key_strings not defined for 'string'

• The key strings required for the pw_recorder are not specified. Please specify these values and try again. See network/pw_recorder.cpp(101).

pw_recorder::init(): key_values not defined for 'string'

• The key value field required for the pw_recorder is not specified. Please specify these values and try again. See network/pw_recorder.cpp(110).

pw_recorder::init(): model of 'string' is not a pw_model

• The object specified in the model field of the pw_recorder is not a pw_model object. See network/pw_recorder.cpp(83).

pw_recorder::init(): object \'string'\' does not specify a model object

• A model object was not explicitly specified or connected as a parent to the pw_recorder object. Please make this connection and try again. See network/pw_recorder.cpp(62).

pw_recorder::init(): parent of 'string' is not a pw_model

• The pw_recorder object does not have the model field specified and is not parented to a pw_model object. Please specify a pw_model object in the model field or parent the pw_recorder to one and try again. See network/pw_recorder.cpp(71).

pw_recorder::init(): properties not defined for 'string'

• The recording properties list is not defined for the pw_recorder object. Please specify these properties and try again. See network/pw_recorder.cpp(119).

pw_recorder::init(): unable to open outfile 'string' for writing

• pw_recorder was unable to open the output file. Please ensure it isn't open in another program and try again. See network/pw_recorder.cpp(184).

pw_recorder::init(): unable to write header for 'string'

• pw_recorder was unable to write the header in the output file. Please ensure the file isn't open in another program and try again. See network/pw_recorder.cpp(192).

rank 'string' is invalid

• A search rule specified an object rank that is negative. Make sure the rank is zero or positive and try again. See gldcore/find.c(1147).

ranks setup failed

• The rank setup procedure failed. This is usually preceded by a more detailed message that explains why it failed. Follow the guidance for that message and try again. See gldcore/exec.c(1774).

received SIGABRT; exiting now

• A signal from the operating system was caught, which aborts the current simulation. This is not normal, but may be intentional. If it is not intentional, make sure that the signal is not being raised accidentally by another application. See gldcore/debug.c(295).

received SIGTERM; exiting now

• A signal from the operating system was caught, which halts the current simulation. This is not normal, but may be intentional. If it is not intentional, make sure that the signal is not being raised accidentally by another application. See gldcore/debug.c(284).

Reliability object:'integer' - 'string' - deltamode function returned an error!

• While performing a deltamode update, one object returned an error code. Check to see if the object itself provided more details and try again. If the error persists, please submit your code and a bug report via the trac website. See reliability/init.cpp(163).

Residential object:'integer' - 'string' - deltamode function returned an error!

• While performing a deltamode update, one object returned an error code. Check to see if the object itself provided more details and try again. If the error persists, please submit your code and a bug report via the trac website. See residential/init.cpp(285).

Residential object:'string' - failed post-deltamode update

• While calling the individual object post-deltamode calculations, an error occurred. Please try again. If the error persists, please submit your code and a bug report via the trac website. See residential/init.cpp(353).

residential::deltamode_timestep must be a positive, non-zero number!

• The value for deltamode_timestep, as specified as the module level in residential, must be a positive, non-zero number. Please use such a number and try again. See residential/init.cpp(208).

restoration: Attempting to parse a character token failed

• While attempting to parse a string of numbers, an unexpected state was encountered. Please check your inputs and try again. See powerflow/restoration.cpp(935).
• While attempting to parse a string of numbers, an unexpected state was encountered. Please check your inputs and try again. See powerflow/restoration.cpp(1062).
• While attempting to parse a string of numbers, an unexpected state was encountered. Please check your inputs and try again. See powerflow/restoration.cpp(1269).

restoration: Attempting to parse a complex character token failed

• While attempting to parse a string of numbers, an unexpected state was encountered. Please check your inputs and try again. See powerflow/restoration.cpp(1087).

restoration: Failed to allocate space for complex array!

• While attempting to allocate space for a complex array for parsing a comma-separated list into, an error occurred. Please try again. If the error persists, please submit your code and a bug report via the ticketing system. See powerflow/restoration.cpp(1028).

restoration: Failed to allocate space for double array!

• While attempting to allocate space for a double array for parsing a comma-separated list into, an error occurred. Please try again. If the error persists, please submit your code and a bug report via the ticketing system. See powerflow/restoration.cpp(901).

restoration: Failed to allocate space for object array!

• While attempting to allocate space for a object array for parsing a comma-separated list into, an error occurred. Please try again. If the error persists, please submit your code and a bug report via the ticketing system. See powerflow/restoration.cpp(1235).

RunScriptCommand(EnterMode(RUN);) failed

• PowerWorld failed to enter the RUN mode. Please ensure there are no model errors and that PowerWorld is functioning correctly and try again. See network/pw_model.cpp(243).

RunScriptCommand(SolvePowerFlow;) failed

• SimAuto reported a problem when asked to simulate the model. Review the error message on the console. See network/pw_model.cpp(256).
• PowerWorld failed to solve the powerflow correctly. Please ensure the model is correct and the system condition is valid and try again. See network/pw_model.cpp(373).

saveall: extension '.'string' not a known format

• Only the format extensions ".txt", ".gld", and ".xml" are recognized by GridLAB-D. Please end the specified output field accordingly, or omit the extension entirely to force use of the default format. See gldcore/save.c(75).

schedule 'string' has 'integer' gaps which may cause erroneous results

• The definition given the schedule has missing data that will cause time synchronization problems. Make sure that all the time covered by the schedule has values given. See gldcore/schedule.c(248).

schedule 'string': block 'string' definition is too long

• The definition given the schedule is too long to be used. Use a definition that is less than 1024 characters and try again. See gldcore/schedule.c(831).

schedule 'string': unexpected text before block start

• The schedule syntax is not valid. Remove the unexpected or invalid text before the block and try again. See gldcore/schedule.c(797).

schedule name is too long

• The name given the schedule is too long to be used. Use a name that is less than 64 characters and try again. See gldcore/schedule.c(756).

schedule_compile(SCHEDULE *sch='{name='string', ...}') ignored an invalid definition 'string'

• The schedule definition is not valid and has been ignored. Check the syntax of your schedule and try again. See gldcore/schedule.c(344).

schedule_compile(SCHEDULE *sch='{name='string', ...}') maximum number of blocks reached

• The schedule definition has too many blocks to compile. Consolidate your schedule and try again. See gldcore/schedule.c(271).

schedule_compile(SCHEDULE *sch={name='string', ...}) 'string' in block 'string' has a conflict with value 'real' on 'string' 'integer'/'integer' 'integer':'integer'

• The schedule definition is not valid and has been ignored. Check the syntax of your schedule and try again. See gldcore/schedule.c(429).

schedule_compile(SCHEDULE *sch={name='string', ...}) 'string' pattern syntax error in item 'string'

• The schedule definition is not valid and has been ignored. Check the syntax of your schedule and try again. See gldcore/schedule.c(374).

schedule_create(char *name='string', char *definition='string') definition does not match previous definition of schedule 'string')

• There is more than 1 schedule with a given name, but they have different definitions. Under certain circumstances, this can lead to unpredictable simulation results and should be remedied by using a distinct name for each distinct schedule. See gldcore/schedule.c(953).

schedule_create(char *name='string', char *definition='string') definition too long)

• The definition given the schedule is too long to be used. Use a definition that is less than 1024 characters and try again. See gldcore/schedule.c(996).

schedule_create(char *name='string', char *definition='string') memory allocation failed)

• The schedule module could not allocate enough memory to create a schedule item. Try freeing system memory and try again. See gldcore/schedule.c(972).

schedule_create(char *name='string', char *definition='string') name too long)

• The name given the schedule is too long to be used. Use a name that is less than 64 characters and try again. See gldcore/schedule.c(981).

schedule_recompile(SCHEDULE *sch='{name='string', ...}') ignored an invalid definition 'string'

• The schedule definition is not valid and has been ignored. Check the syntax of your schedule and try again. See gldcore/schedule.c(536).

schedule_recompile(SCHEDULE *sch={name='string', ...}) 'string' in block 'string' has a conflict with value 'real' on 'string' 'integer'/'integer' 'integer':'integer'

• The schedule definition is not valid and has been ignored. Check the syntax of your schedule and try again. See gldcore/schedule.c(611).

schedule_recompile(SCHEDULE *sch={name='string', ...}) 'string' pattern syntax error in item 'string'

• The schedule definition is not valid and has been ignored. Check the syntax of your schedule and try again. See gldcore/schedule.c(558).

set syntax error ('integer' items)

• The set syntax doesn't have the correct number of arguments. Check the command syntax and try again. See gldcore/debug.c(1190).

shared memory limit exceeded (need 'real'kB)

• The process map is too big for the limits on shared memory. Consult your system's manuals to learn how to increase the size of shared memory. See gldcore/module.c(2057).

solver_NR: An attempt to allocate a variable array for the NR solver failed!

• While attempting to allocate an array for the NR solver, a memory allocation issue was encountered. Please try again. If the error persists, please submit an issue via the ticketing system. See powerflow/solver_nr.cpp(5873).

solver_NR: Attempted to allocate over an existing NR solver variable array!

• While attempting to allocate over a NR solver/island variable, the variable to allocate to was not empty. The base size is unknown, so this will fail (it may leave stranded memory locations). Please try again, and adjust any code added. If the error persists, post an issue under the ticketing system. See powerflow/solver_nr.cpp(5857).

solver_nr: Mesh fault impedance extract failed - invalid node

• While attempting to extract the mesh fault impedance value, a node with either invalid phasing or no phases (already removed) was somehow flagged. Please check your file and try again. If the error persists, please submit your code and a bug report via the ticketing system. See powerflow/solver_nr.cpp(3725).

solver_nr: Mesh impedance attempted from unsupported LU solver

• The mesh fault current impedance "pull" was selected, but for the external LU solver. This is unsupported at this time. To use the mesh fault current capabilities, please use the superLU solver. See powerflow/solver_nr.cpp(3952).

solver_nr: Node reference for mesh fault calculation was invalid -- it may be a child

• While attempting to compute the equivalent impedance at a mesh faulted node, an invalid node reference was found. This is likely an internal error to the code -- submit your code and a bug report via the tracking website. See powerflow/solver_nr.cpp(3701).

solver_nr: superLU failed mesh fault matrix inversion with code 'integer'

• superLU failed to invert the equivalent impedance matrix for the mesh fault calculation method. Please try again and make sure your system is valid. If the error persists, please submit your code and a bug report via the ticketing system. See powerflow/solver_nr.cpp(3804).

Specified target 'string' for 'string' is not valid.

• Check to make sure the target you are specifying is a published variable for the object that you are pointing to. Refer to the documentation of the command flag --modhelp, or check the wiki page to determine which variables can be published within the object you are pointing to with the assert function. See assert/complex_assert.cpp(115).
• Check to make sure the target you are specifying is a published variable for the object that you are pointing to. Refer to the documentation of the command flag --modhelp, or check the wiki page to determine which variables can be published within the object you are pointing to with the assert function. See assert/complex_assert.cpp(273).
• Check to make sure the target you are specifying is a published variable for the object that you are pointing to. Refer to the documentation of the command flag --modhelp, or check the wiki page to determine which variables can be published within the object you are pointing to with the assert function. See assert/double_assert.cpp(112).
• Check to make sure the target you are specifying is a published variable for the object that you are pointing to. Refer to the documentation of the command flag --modhelp, or check the wiki page to determine which variables can be published within the object you are pointing to with the assert function. See assert/double_assert.cpp(233).
• Check to make sure the target you are specifying is a published variable for the object that you are pointing to. Refer to the documentation of the command flag --modhelp, or check the wiki page to determine which variables can be published within the object you are pointing to with the assert function. See assert/enum_assert.cpp(74).
• Check to make sure the target you are specifying is a published variable for the object that you are pointing to. Refer to the documentation of the command flag --modhelp, or check the wiki page to determine which variables can be published within the object you are pointing to with the assert function. See assert/enum_assert.cpp(145).
• Check to make sure the target you are specifying is a published variable for the object that you are pointing to. Refer to the documentation of the command flag --modhelp, or check the wiki page to determine which variables can be published within the object you are pointing to with the assert function. See assert/int_assert.cpp(112).

strdatetime: timestamp larger than provided buffer

• The buffer provided to strdatetime was insufficiently large, or was otherwise packed with data beforehand. The relevant code should use a larger buffer, or the output data set should be smaller. See gldcore/timestamp.c(593).

strict naming prevents implicit creation of 'string'

• The global_strictnames variable prevents the system from implicitly creating a new variable just by setting a value. Try using the name of a named variable or remove the strict naming setting by setting global_strictnames=0. See gldcore/globals.c(556).

substation needs to have all three phases!

• To meet the requirements for sequence voltage conversions, the substation node must have all three phases at the connection point. If only a single phase or subset of full three phase is needed, those must be set in the distribution network, typically after a delta-ground wye transformer. See powerflow/substation.cpp(267).

tape object:'integer' - unable to allocate space for deltamode

• While attempting to allocate space for a tape module deltamode-capable object, an error occurred. Please try again. If the error persists, please submit your code and a bug report via the ticketing system. See tape/tape.c(401).

The high window temperature cutoff must be greater than the low window temperature cutoff.

• The window_high_temperature_cutoff must be a value greater than the window_low_temperature_cutoff. These two values define a temperature "deadband" in which there is a possibility that the window will "open". Please take a look at your specified values and ensure that the high is greater than the low. See residential/house_e.cpp(2353).

thread memory allocation failed

• A thread memory allocation failed. Follow the standard process for freeing up memory ang try again. See gldcore/exec.c(1818).

timestamp_year: the year has rolled over or become negative!

• This is indicative of something strange occuring within timestamp_year(). This is a "kicked up" error message that was insufficiently documented from earlier code. See gldcore/timestamp.c(118).

tried to create global variable 'string' a second time

• An attempt to create a global variable failed because the indicated variable already exists. Find out what is attempting to create the variable and fix the problem and try again. See gldcore/globals.c(366).

trying to get the private property 'string' in 'string'

• The specified property was published by its object as private. Though it may be read at the end of the simulation and by other classes in the module, other modules do not have permission to access that property. See gldcore/object.c(752).

trying to read the value of private property 'string' in 'string'

• The specified property was published by its object as private. It may not be modified by other modules. See gldcore/object.c(1142).

trying to set the value of non-public property 'string' in 'string'

• The specified property was published by its object as private. It may not be modified by other modules. See gldcore/object.c(775).
• The specified property was published by its object as private. It may not be modified by other modules. See gldcore/object.c(1008).
• The specified property was published by its object as private. It may not be modified by other modules. See gldcore/object.c(1030).
• The specified property was published by its object as private. It may not be modified by other modules. See gldcore/object.c(1058).
• The specified property was published by its object as private. It may not be modified by other modules. See gldcore/object.c(1079).
• The specified property was published by its object as private. It may not be modified by other modules. See gldcore/object.c(1100).
• The specified property was published by its object as private. It may not be modified by other modules. See gldcore/object.c(1121).

unable to add class breakpoint

• The break error could not be completed because of a problem with the internal operation needed to perform it. Follow the guidance for the message which precedes this message and try again. See gldcore/debug.c(860).

unable to add clock breakpoint

• The break clock could not be completed because of a problem with the internal operation needed to perform it. Follow the guidance for the message which precedes this message and try again. See gldcore/debug.c(804).

unable to add error breakpoint

• The break error could not be completed because of a problem with the internal operation needed to perform it. Follow the guidance for the message which precedes this message and try again. See gldcore/debug.c(791).

unable to add module breakpoint

• The break module could not be completed because of a problem with the internal operation needed to perform it. Follow the guidance for the message which precedes this message and try again. See gldcore/debug.c(839).

unable to add object breakpoint

• The break object could not be completed because of a problem with the internal operation needed to perform it. Follow the guidance for the message which precedes this message and try again. See gldcore/debug.c(818).

unable to add object watchpoint

• The watch could not be completed because of a problem with the internal operation needed to perform it. Follow the guidance for the message that precedes this message and try again. See gldcore/debug.c(1067).

unable to add pass breakpoint

• The break pass could not be completed because of a problem with the internal operation needed to perform it. Follow the guidance for the message which precedes this message and try again. See gldcore/debug.c(888).

unable to add rank breakpoint

• The break rank specifies a rank that isn't valid. Check the command syntax and try again. See gldcore/debug.c(899).

unable to add timestamp breakpoint

• The break time could not be completed because of a problem with the internal operation needed to perform it. Follow the guidance for the message which precedes this message and try again. See gldcore/debug.c(915).

unable to allocate ISimulatorAutoPtr in init()

• GridLAB-D was unable to allocate one of the necessary variables for the SimAuto interface. Please try again. If the error persists, please submit your code and a bug report via the trac website. See network/pw_model.cpp(218).

unable to allocate memory for deltamode module list

• Deltamode operation requires more memory than is available. Try freeing up memory by making more heap available or making the model smaller. See gldcore/deltamode.c(71).

unable to allocate memory for deltamode object list

• Deltamode operation requires more memory than is available. Try freeing up memory by making more heap available or making the model smaller. See gldcore/deltamode.c(115).

unable to allocate memory for deltamode rankcount

• Deltamode operation requires more memory than is available. Try freeing up memory by making more heap available or making the model smaller. See gldcore/deltamode.c(138).

unable to allocate memory for deltamode rankcount 'integer'

• Deltamode operation requires more memory than is available. Try freeing up memory by making more heap available or making the model smaller. See gldcore/deltamode.c(162).

unable to allocate memory for deltamode ranklist

• Deltamode operation requires more memory than is available. Try freeing up memory by making more heap available or making the model smaller. See gldcore/deltamode.c(126).

unable to convert from delegated property value

• Property delegation is not yet fully implemented, so you should never get this error. If you do, there is a problem with the system that is causing it to become unstable. See gldcore/class.c(388).

unable to create cache 'string' for instance 'string' (error code 'integer')

• Error code 1314 indicates that the "SeCreateGlobalPrivilege" has not been granted by the system administrator. This privilege is required for GridLAB-D to use shared memory in multirun mode. See gldcore/instance_cnx.c(30).

unable to find clsid \

• GridLAB-D was unable to find the clsid value for PowerWorld SimAuto inside the registry. Please ensure PowerWorld and SimAuto are installed and registered correctly and try again. See network/pw_model.cpp(193).

unable to implicitly create the global variable 'string'

• An attempt to create the global variable indicated failed. This is an internal error and should be reported to the software developers. See gldcore/globals.c(570).

unable to load 'string': 'string'

• In most cases, strerror(errno) will claim "No such file or directory". This claim should be ignored in favor of prior error messages. See gldcore/load.c(7032).
• In most cases, strerror(errno) will claim "No such file or directory". This claim should be ignored in favor of prior error messages. See gldcore/load.c(7126).

Unable to map battery parent object as inverter.

• While trying to map an inverter from the listof inverters with battery children as an inverter object, a null pointer was returned. See generators/central_dg_control.cpp(216).

Unable to map group_recorder postupdate function

• While trying to map up a deltamode function for group_recorders, the function was not found. Please try again. If the error persists, please submit your code and a bug report via the ticketing system. See tape/tape.c(766).

Unable to map object as battery.

• While trying to map a battery from the list as a battery object, a null pointer was returned. See generators/central_dg_control.cpp(199).

Unable to map object as inverter.

• While trying to map an inverter from the list as an inveter object, a null pointer was returned. See generators/central_dg_control.cpp(207).
• While trying to map an inverter from the listof inverters an inverter object, a null pointer was returned. See generators/central_dg_control.cpp(243).

Unable to map object as solar.

• While trying to map a solar from the list as a solar object, a null pointer was returned. See generators/central_dg_control.cpp(235).

Unable to map solar parent object as inverter.

• While trying to map an inverter from the listof inverters with solar children as an inverter object, a null pointer was returned. See generators/central_dg_control.cpp(252).

unable to open file 'string' for reading

• The file specified is not available. Make sure the filename is correct and has the required access rights and try again. See gldcore/debug.c(720).

unable to publish enumeration member 'string' of enduse 'string'

• The enduse_publish structure is not defined correctly. This is an internal error and cannot be corrected by users. Contact technical support and report this problem. See gldcore/enduse.c(495).

unable to publish set member 'string' of enduse 'string'

• The enduse_publish structure is not defined correctly. This is an internal error and cannot be corrected by users. Contact technical support and report this problem. See gldcore/enduse.c(506).

unable to register delegated type (memory allocation failed)

• Property delegation is not supported yet so this should never happen. This is most likely caused by a lack of memory or an unstable system. See gldcore/class.c(1226).

unable to set global value 'string'

• The set debug command was unable to set the specified global variable because of an internal error. Follow the guidance for the message that precedes this message and try again. See gldcore/debug.c(1156).

unable to set value of object 'string' property 'string'

• The set debug command was unable to set the value given could not be converted to the type required for the property. Check the command syntax and try again. See gldcore/debug.c(1167).

Unable to update topology for switching action

• While attempting to map the reliability function to manipulate topology, an error occurred. Please try again. If the bug persists, please submit your code and a bug report via the ticketing system. See powerflow/switch_object.cpp(1860).

Unconnected node - 'string' id:'integer'

• While parsing a GLM, the Newton-Raphson powerflow solver encountered a node that does not appear to be connected anywhere. This will cause problems with the solver. Please verify that this node is supposed to be islanded. See powerflow/node.cpp(2780).

undefined pass type for add breakpoint

• The break pass specifies a pass type that isn't valid. Only pretopdown, bottomup, and posttopdown are supported. See gldcore/debug.c(879).

Unexpected link current update call from 'string'

• While attempting to perform the current injection updates for a link, an unexpected object called the current update. Please try again. If the error persists, please submit your code and a bug report via the trac website. See powerflow/link.cpp(3649).

Unknown exception in pw_recorder::build_keys()!

• An unknown exception was encountered by the pw_recorder object. Please try again. If the error persists, please submit your code and a bug report via the trac website. See network/pw_recorder.cpp(407).
• An unknown exception was encountered by the pw_recorder object. Please try again. If the error persists, please submit your code and a bug report via the trac website. See network/pw_recorder.cpp(445).

unnamed command syntax error

• The unnamed debugger command support only one option, but somehow more than one option was read. Check the syntax and try again. See gldcore/debug.c(672).

vfd:'integer' 'string' -- failed to allocate dynamic array

• While allocating a dynamic array, an error occurred. Please try again. If the error persists, please submit See powerflow/vfd.cpp(900).

vfd:'integer' 'string' -- the stable_time value must result in at least 1 timestep of averaging!

• While attempting to allocate the averaging arrays, an invalid length was specified. Make sure your stable_time value is greater than zero! See powerflow/vfd.cpp(885).

violation_recorder::flush_line(): output file is not open

• violation_recorder claimed to be open and attempted to flush to a file when a file had not successfully opened. See tape/violation_recorder.cpp(1345).

violation_recorder::flush_line(): unable to flush output file

• An IO error has occured. See tape/violation_recorder.cpp(1354).

violation_recorder::write_footer(): output file is not open

• violation_recorder claimed to be open and attempted to write to a file when a file had not successfully opened. See tape/violation_recorder.cpp(1474).

violation_recorder::write_line(): error when converting the sync time

• Unprintable timestamp. See tape/violation_recorder.cpp(1278).

violation_recorder::write_line(): error when writing the sync time as a string

• Error printing the timestamp. See tape/violation_recorder.cpp(1286).

violation_recorder::write_line(): error when writing to the output file

• File I/O error. See tape/violation_recorder.cpp(1300).

violation_recorder::write_line(): no output file open and state is 'open'

• violation_recorder claimed to be open and attempted to write to a file when a file had not successfully opened. See tape/violation_recorder.cpp(1269).

Water heater line voltage for waterheater:'integer' is too high, exceeds twice nominal voltage.

• The waterheater is receiving twice the nominal voltage consistantly, or about 480V on what should be a 240V circuit. Please sanity check your powerflow model as it feeds to the meter and to the house. See residential/waterheater.cpp(1359).

watertank thermostat is set to 'real' and is outside the bounds of 90 to 160 degrees Fahrenheit (32.2 - 71.1 Celsius).

• All waterheaters must be set between 90 degF and 160 degF. See residential/waterheater.cpp(364).

watertank volume of 'real' outside the volume bounds of 20 to 100 gallons.

• All waterheaters must be set between 20 and 100 gallons. Most waterheaters are assumed to be 50 gallon tanks. See residential/waterheater.cpp(306).

weather property refers to a(n) \

• While attempting to map a climate property, the solar array encountered an object that is not a climate object. Please check to make sure a proper climate object is present, and/or specified. If the bug persists, please submit your code and a bug report via the trac website. See generators/solar.cpp(240).

Fatal errors

'string' environment not recognized or supported

• The environment specified isn't supported. Currently only the batch environment is normally supported, although some builds can support other environments, such as matlab. See gldcore/environment.c(121).

Breaking an infinite loop in local_datetime! (ts = %

• An internal protection against infinite loops in the time calculation module has encountered a critical problem. This is often caused by an incorrectly initialized timezone system, a missing timezone specification before a timestamp was used, or a missing timezone localization in your system. Correct the timezone problem and try again. See gldcore/timestamp.c(289).

Breaking an infinite loop in local_datetime_delta! (ts = %

• An internal protection against infinite loops in the time calculation module has encountered a critical problem. This is often caused by an incorrectly initialized timezone system, a missing timezone specification before a timestamp was used, or a missing timezone localization in your system. Correct the timezone problem and try again. See gldcore/timestamp.c(423).

default redirection of 'string' failed: 'string'

• An attempt to close a standard stream from the command line using --redirect stream has failed. The message should provide an indication of why the attempt failed. The remedy will depend on the nature of the problem. See gldcore/cmdarg.c(775).

definition is missing

• The --modtest parameter was found on the command line, but if was not followed by a module specification. The correct syntax is gridlabd --modtest module_name. See gldcore/cmdarg.c(648).
• The -D or --define command line parameters was given, but it was not followed by a variable definition. The correct syntax -D variable=value or --define variable=value See gldcore/cmdarg.c(684).

environment not specified

• The -e or --environment command line directive was not followed by a valid environment specification. The correct syntax is -e keyword or --environment keyword. See gldcore/cmdarg.c(856).

environment startup failed: 'string'

• The requested environment could not be started. This usually follows a more specific message regarding the startup problem. Follow the recommendation for the indicated problem. See gldcore/main.c(179).

incorrect module list file name

• The --testall parameter was found on the command line, but if was not followed by a valid filename containing the test description file. See gldcore/cmdarg.c(493).

info subject not specified

• The --info command line directive was not followed by a valid subject to lookup. The correct syntax is --info subject. See gldcore/cmdarg.c(1010).

insufficient buffer space to compile init code (inline_block_size='integer')

• The loader creates a buffer in which it can temporarily hold source initialization code from your GLM file. This error occurs when the buffer space has been exhausted. There are only two ways to fix this problem, 1) make the code smaller (which can be difficult to do), or 2) increase the buffer space (which requires a rebuild). See gldcore/load.c(393).
• The loader creates a buffer in which it can temporarily hold source runtime code from your GLM file. This error occurs when the buffer space has been exhausted. There are only two ways to fix this problem, 1) make the code smaller (which can be difficult to do), or 2) increase the buffer space (which requires a rebuild). See gldcore/load.c(416).
• The loader creates a buffer in which it can temporarily hold source global code from your GLM file. This error occurs when the buffer space has been exhausted. There are only two ways to fix this problem, 1) make the code smaller (which can be difficult to do), or 2) increase the buffer space (which requires a rebuild). See gldcore/load.c(439).

intrinsic 'string' is not defined in class 'string'

• A required intrinsic function was not found. Please review and modify the class definition. See gldcore/module.c(521).

missing library name

• The -L or --libinfo command line directive was not followed by a module name. The correct syntax is -L module_name or --libinfo module_name. See gldcore/cmdarg.c(807).

missing output file

• The -o or --output command line directive was not followed by a valid filename. The correct syntax is -o file or --output file. See gldcore/cmdarg.c(841).

missing server ip address

• The --server_inaddr command line directive was not followed by a valid IP address. The correct syntax is --server_inaddr interface address. See gldcore/cmdarg.c(381).

missing server port number

• The -P or --server_portnum command line directive was not followed by a valid number. The correct syntax is -P number or --server_portnum number. See gldcore/cmdarg.c(363).

missing thread count

• The -T or --threadcount command line directive was not followed by a valid number. The correct syntax is -T number or --threadcount number. See gldcore/cmdarg.c(822).

module 'string' does not implement a test routine

• The --modtest parameter was found on the command line, but if was followed by a specification for a module that doesn't implement any test procedures. See the --libinfo command line parameter for information on which procedures the module supports. See gldcore/cmdarg.c(630).

module 'string' is not found

• The --modhelp parameter was found on the command line, but if was followed by a module specification that isn't valid. Verify that the module exists in GridLAB-D's lib folder. See gldcore/cmdarg.c(566).
• The --modtest parameter was found on the command line, but if was followed by a module specification that isn't valid. Verify that the module exists in GridLAB-D's lib folder. See gldcore/cmdarg.c(620).

module list not specified

• The --xsl command line directive was not followed by a validlist of modules. The correct syntax is --xsl module1[,module2[,...]]. See gldcore/cmdarg.c(925).

no filename for testall

• The --testall parameter was found on the command line, but if was not followed by a filename containing the test description file. See gldcore/cmdarg.c(480).

object_sync(OBJECT *obj='string', TIMESTAMP ts='string', PASSCONFIG pass='string'): int64 sync_'string'(OBJECT*,TIMESTAMP,PASSCONFIG) is not implemented in module 'string'

• The indicated sync function is not implemented by the class given. This happens when the PASSCONFIG flag indicates a particular sync (presync/sync/postsync) needs to be called, but the class does not actually implement it. This is a problem with the module that implements the class. See gldcore/object.c(1433).

ordinal 'integer' is too small (first is 'integer')

• This is an internal error caused by an attempt to index something improperly. Because the indexing system start at index 0, this means a negative index number was attempting, which is most likely a bug. This usually occurs during object initialization and might be caused by invalid object numbers, either negative or greater than about 2 billion. If your model is using a the class:id naming convention, check the object id numbers to make sure they are correct. See gldcore/index.c(76).

processor number not specified

• The --pkill command line directive was not followed by a valid processor number. The correct syntax is --pkill processor_number. See gldcore/cmdarg.c(965).

property_type[] in class.c has an incorrect number of members ('integer' vs 'integer')

• This error occurs when an improper definition of a class is used. This is not usually caused by an error in a GLM file but is most likely caused by a bug in a module or incorrectly defined class. See gldcore/class.c(433).

redirection is missing

• A --redirect directive on the command line is missing its redirection specification. The correct syntax is --redirect stream[:destination]. See gldcore/cmdarg.c(788).

redirection of 'string' to 'string' failed: 'string'

• An attempt to redirect a standard stream from the command line using --redirect stream:destination has failed. The message should provide an indication of why the attempt failed. The remedy will depend on the nature of the problem. See gldcore/cmdarg.c(763).

redirection of all failed

• An attempt to close all standard stream from the command line using --redirect all has failed. One of the streams cannot be closed. Try redirecting each stream separately until the problem stream is identified and the correct the problem with that stream. See gldcore/cmdarg.c(747).

shutdown after command line rejected

• The command line is not valid and the system did not complete its startup procedure. Correct the problem with the command line and try again. See gldcore/main.c(116).

shutdown after simulation stopped prematurely

• The simulation stopped because an unexpected condition was encountered. This can be caused by a wide variety of things, but most often it is because one of the objects in the model could not be synchronized propertly and its clock stopped. This message usually follows a more specific message that indicates what caused the simulation to stop. See gldcore/environment.c(44).

unable to create pidfile 'string'

• The system must allow creation of the process id file at the location indicated in the message. Create and/or modify access rights to the path for that file and try again. See gldcore/main.c(151).

Unable to find class 'string' in module 'string'

• The --modhelp parameter was found on the command line, but if was followed by a class specification that isn't valid. Verify that the class exists in the module you specified. See gldcore/cmdarg.c(521).

unable to grow index 'integer': 'string'

• An internal memory allocation error cause an index operation to fail. The message will usually include some explanation as to what cause the failure. Remedy the indicated memory problem to fix the indexing problem. See gldcore/index.c(99).

unable to open 'string' for writing

• The internal compiler cannot write a temporary C or C++ that it needs to build your model. The message indicates where the file is. To remedy the problem you must make sure that the system allows full access to the file. See gldcore/load.c(710).

Unable to store module name

• This error is caused by a failure to set up a module test, which requires that the name module being tested be stored in a global variable called mod_test. The root cause will be identified by determining what error in the global_setvar call occurred. See gldcore/cmdarg.c(55).

unable to write to 'string'

• The internal compiler cannot write a temporary C or C++ that it needs to build your model. The message indicates where the file is. To remedy the problem you must make sure that the system allows full access to the file. See gldcore/load.c(759).

unexpected branch result in object_tree_delete

• This should never happen and if it does, the system has become unstable and the problem should be reported. See gldcore/object.c(2323).

xml encoding not specified

• The --xmlencoding command line directive was not followed by a encoding specification. The correct syntax is --xmlencoding keyword. See gldcore/cmdarg.c(875).

Exceptions

'string'('integer'): 'character' is not recognized at 'string'

• The unit file used an invalid syntax to define a unit. Correct the syntax and try again. See gldcore/unit.c(450).

'string'('integer'): ^ not allowed after 'character' at 'string'

• The unit file used an invalid syntax to define a unit. Correct the syntax and try again. See gldcore/unit.c(441).

'string'('integer'): constant 'character' is not valid

• The specified constant name does not conform to the internally recognized constants. See gldcore/unit.c(216).

'string'('integer'): constant definition of 'string' failed; unit already defined

• The value of the specified scalar name has already been used as a unit and cannot be used as a constant. Please remove or comment out the offending line from the unit file. See gldcore/unit.c(190).

'string'('integer'): derived definition of 'string' failed; unit already defined

• The specified derived unit has already been defined within the unit file. Please review the unit definition file and remove the offending line. See gldcore/unit.c(301).

'string'('integer'): memory allocation failed

• The unit conversion system was unable to allocate memory needed to define the unit located at the specified file at the given line. Try freeing up system memory and try again. See gldcore/unit.c(249).

'string'('integer'): primary definition of 'string' failed; unit already defined with a different parameter set

• Since the specified unit was defined, the values of the universal constants OR the global precision have changed. No units should be created until after all of the constants have been specified, nor should those constants be modified between unit definitions. See gldcore/unit.c(239).

'string'('integer'): scalar definitinon of 'string' failed: 'string'

• This is actually triggered by a malloc failure, and the rest of the system is likely unstable. See gldcore/unit.c(171).

'string'('integer'): syntax error at 'string', exponent must be greater than 1

• The unit was defined akin to "m^2", but the exponent was an integer value less than 1, which is nonsensical for a physical simulation See gldcore/unit.c(412).

'string'('integer'): unable to find or derive unit 'string'

• The specified term was neither found nor derived, and likely does not exist in the unit subsystem at the point the exception is raised. Review the unit file and either move the offending unit down the file, or verify that the base unit exists. See gldcore/unit.c(351).

'string'('integer'): unable to read unit 'string'

• The unit definition contains a character that prevents it from being parsed. No unit definitions should contain the characters ^, -, *, /, or +. See gldcore/unit.c(327).

'string'('integer'): unit 'string' is not recognized

• The specified unit was not recognized as a constant, a primary unit, or a derived unit. See gldcore/unit.c(591).

--modhelp: malloc failure

• The memory allocation needed for module help to function has failed. Try freeing up system memory and try again. See gldcore/cmdarg.c(588).

_random_specs(type='integer',...); type is not valid

• An attempt to describe a random number specific a distribution type that isn't recognized. Check that the distribution is valid and try again. See gldcore/random.c(723).

_random_value(type='integer',...); type is not valid

• An attempt to generate a random number specific a distribution type that isn't recognized. Check that the distribution is valid and try again. See gldcore/random.c(682).

A non-positive value has been specified for within.

• Within is the range in which the check is being performed. Please check to see that you have specified a value for "within" and it is positive. See assert/complex_assert.cpp(82).

class_add_extended_property(oclass='string', name='string', ...): memory allocation failed

• The system has run out of memory. Try making the model smaller and trying again. See gldcore/class.c(261).

class_add_extended_property(oclass='string', name='string', ...): property type is invalid

• The function was called with a property type that is not recognized. This is a bug that should be reported. See gldcore/class.c(266).

class_add_extended_property(oclass='string', name='string', ...): unit 'string' is not found

• The function was called with unit that is defined in units file .../etc/unitfile.txt. Try using a defined unit or adding the desired unit to the units file and try again. See gldcore/class.c(271).

class_get_first_property(CLASS *oclass=NULL): oclass is NULL

• A call to class_get_first_property() was made with a NULL pointer. This is a bug and should be reported. See gldcore/class.c(74).

error when setting parent

• An error has occurred while setting the parent field of a link. Please submit a bug report and your code so this error can be diagnosed further. See powerflow/link.cpp(338).

forecast_create(): memory allocation failed

• The forecast_create function could not allocate memory for the FORECAST entity. This is probably due to a lack of system memory or a problem with the memory allocation system. Free up system memory, reducing the complexity and/or size of the model and try again. See gldcore/object.c(2592).

forecast_save(): memory allocation failed

• The forecast_create function could not allocate memory for the FORECAST entity. This is probably due to a lack of system memory or a problem with the memory allocation system. Free up system memory, reducing the complexity and/or size of the model and try again. See gldcore/object.c(2666).

global_create(char *name='string',...): property extension code not recognized (PROPERTYTYPE='integer')

• The property extension code used is not valid. This is probably a bug and should be reported. See gldcore/globals.c(470).

global_create(char *name='string',...): property keyword could not be stored

• The memory needed to store the property's keyword is not available. Try freeing up memory and try again. See gldcore/globals.c(403).
• The memory needed to store the property's keyword is not available. Try freeing up memory and try again. See gldcore/globals.c(417).

global_create(char *name='string',...): property name 'string' is too big to store

• The property name cannot be longer than the size of the internal buffer used to store it (currently this is 63 characters). Use a shorter name and try again. See gldcore/globals.c(479).

global_create(char *name='string',...): property size must be greater than 0 to allocate memory

• The size of the property must be positive. See gldcore/globals.c(450).

global_create(char *name='string',...): unable to allocate memory for global variable

• There is insufficient memory to allocate for the global variable. Try freeing up memory and try again. See gldcore/globals.c(381).

global_create(char *name='string',...): unrecognized property access code (PROPERTYACCESS='integer')

• The specific property access code is not recognized. Correct the access code and try again. See gldcore/globals.c(438).

invalid line configuration for overhead line

• The object specified as the configuration for the overhead line is not a valid configuration object. Please ensure you have a line_configuration object selected. See powerflow/overhead_line.cpp(81).

invalid line configuration for underground line

• The object specified as the configuration for the underground line is not a valid configuration object. Please ensure you have a line_configuration object selected. See powerflow/underground_line.cpp(84).

invalid or missing line spacing on overhead line

• The configuration object for the overhead line is missing the line_spacing configuration or the item specified in that location is invalid. See powerflow/overhead_line.cpp(96).

invalid or missing line spacing on underground line

• The configuration object for the underground line is missing the line_spacing configuration or the item specified in that location is invalid. See powerflow/underground_line.cpp(127).

invalid regulator configuration

• An invalid regulator configuration was provided. Ensure you have proper values in each field of the regulator_configuration object and that you haven't inadvertantly used a line or transformer configuration as the regulator configuration. See the media wiki for an example: http://sourceforge.net/apps/mediawiki/gridlab-d/index.php?title=Power_Flow_Guide See powerflow/regulator.cpp(112).

invalid regulator type

• Check the Type specification in your regulator_configuration object. It can an only be type A or B. See powerflow/regulator.cpp(266).

kml_dump(char *filename='string'): 'string'

• The system was unable to output the KML data to the specified file. Follow the recommended solution based on the error message provided and try again. See gldcore/kml.c(171).

kurtosis aggregation is not implemented

• An attempt to use the kurtosis aggregator failed because it is not implemented yet. Remove or replace the reference to the See gldcore/aggregate.c(471).

link from node is not specified

• The from node for a line or link is not connected to anything. See powerflow/link.cpp(298).

link from reference not a node

• The from connection of a link is not a node-based object. Ensure that the from object is a node, load, or meter object. If not, adjust your model accordingly. See powerflow/link.cpp(345).

link to node is not specified

• The to node for a line or link is not connected to anything. See powerflow/link.cpp(303).

negative fault impedance is invalid

• The node of interest has a negative or zero fault impedance value. Specify this value as a positive number to enable proper solver operation. See powerflow/node.cpp(1101).

negative maximum_voltage_error is invalid

• A negative maximum voltage error was specified. This can not be checked. Specify a positive maximum voltage error, or omit this value to let the powerflow solver automatically calculate it for you. See powerflow/node.cpp(1088).

no overhead line configuration specified.

• No overhead line configuration was specified. Please use object line_configuration with appropriate values to specify an overhead line configuration See powerflow/overhead_line.cpp(74).

no regulator configuration specified.

• A regulator configuration was not provided. Please use object regulator_configuration and define the necessary parameters of your regulator to continue. See the media wiki for an example: http://sourceforge.net/apps/mediawiki/gridlab-d/index.php?title=Power_Flow_Guide See powerflow/regulator.cpp(104).

no underground line configuration specified.

• No underground line configuration was specified. Please use object line_configuration with appropriate values to specify an underground line configuration See powerflow/underground_line.cpp(77).

nominal_voltage is not set

• The powerflow solver has detected that a nominal voltage was not specified or is invalid. Specify this voltage as a positive value via nominal_voltage to enable the solver to work. See powerflow/node.cpp(1109).

object 'string' commit failed

• The commit function of the named object has failed. Make sure that the object's requirements for committing are satisfied and try again. (likely internal state aberations) See gldcore/exec.c(1107).

object_close_namespace(): no current namespace to close

• An attempt to close a namespace was made while there was no open namespace. This is an internal error and should be reported. See gldcore/object.c(2516).

object_create_foreign(OBJECT *obj=): obj->oclass is not really a class

• An attempt to create an object was given a class that most likely is not a class. This is most likely a bug and should be reported. See gldcore/object.c(392).

object_create_foreign(OBJECT *obj=): object->oclass is NULL

• The system has run out of memory and is unable to create the object requested. Try freeing up system memory and try again. See gldcore/object.c(385).

object_create_foreign(OBJECT *obj=NULL): object is NULL

• An attempt to create an object was given a NULL pointer for the class. This is most likely a bug and should be reported. See gldcore/object.c(377).

object_create_single(CLASS *oclass='string'): abstract class 'string' cannot be instantiated

• An attempt to create an object using an abstract class was detected. Some classes may only be inherited but cannot be used directly in models. See gldcore/object.c(308).

object_create_single(CLASS *oclass='string'): memory allocation failed

• The system has run out of memory and is unable to create the object requested. Try freeing up system memory and try again. See gldcore/object.c(318).

object_create_single(CLASS *oclass=NULL): class is NULL

• An attempt to create an object was given a NULL pointer for the class. This is most likely a bug and should be reported. See gldcore/object.c(300).

object_dump(char *buffer=%x, int size='integer', OBJECT *obj='string':'integer') buffer overrun

• The buffer used to dump objects has overflowed. This can only be fixed by increasing the size of the buffer and recompiling. If you do not have access to source code, please report this problem so that it can be corrected in the next build. See gldcore/object.c(1687).
• The buffer used to dump objects has overflowed. This can only be fixed by increasing the size of the buffer and recompiling. If you do not have access to source code, please report this problem so that it can be corrected in the next build. See gldcore/object.c(1704).

object_open_namespace(char *space='string'): memory allocation failure

• The memory required to create the indicated namespace is not available. Try freeing up system memory and try again. See gldcore/object.c(2497).

print_class_d: tabdepth > 32, which is mightily deep!

• This means that there is very deep nesting and this is unexpected. This suggests a problem with the internal model and should be reported. See gldcore/cmdarg.c(110).

property 'string' not found in object 'string'

• The property for which the unit was requested does not exist. Depending on where this occurs it's either a bug or an error in the model. Try fixing your model and try again. If the problem persists, report it. See gldcore/object.c(257).

property_malloc(oclass='string',...): property 'string' unit 'string' is not recognized

• A class is attempting to publish a variable using a unit that is not defined. This is caused by an incorrect unit specification in a variable publication (in C++) or declaration (in GLM). Units are defined in the unit file located in the GridLAB-D etc folder. See gldcore/property.c(151).

random_exponential(l='real'): l must be greater than 0

• An attempt to generate a random number used a parameter that was outside the expected range of real numbers. Correct the functional definition of the random number and try again. See gldcore/random.c(473).

random_pareto(m='real', k='real'): k must be greater than 1

• An attempt to generate a random number used a parameter that was outside the expected range of real numbers. Correct the functional definition of the random number and try again. See gldcore/random.c(435).

random_sampled(n='integer',...): n must be a positive number

• An attempt to generate a random number used a parameter that was outside the expected range of real numbers. Correct the functional definition of the random number and try again. See gldcore/random.c(397).

random_weibull(l='real', k='real'): k must be greater than 0

• An attempt to generate a random number used a parameter that was outside the expected range of real numbers. Correct the functional definition of the random number and try again. See gldcore/random.c(504).

raw unit 'string' was not found

• The requested unit was not found by the unit subsystem. There is a good chance that this function will end up triggering a null pointer exception if not properly handled. See gldcore/unit.c(230).

Regulator connect type not supported yet

• Check the connection type specified. Only a few are available at this time. Ones available can be found on the wiki website ( http://sourceforge.net/apps/mediawiki/gridlab-d/index.php?title=Power_Flow_Guide ) See powerflow/regulator.cpp(335).
• Check the connection type specified. Only a few are available at this time. Ones available can be found on the wiki website ( http://sourceforge.net/apps/mediawiki/gridlab-d/index.php?title=Power_Flow_Guide ) See powerflow/regulator.cpp(342).
• Check the connection type specified. Only a few are available at this time. Ones available can be found on the wiki website ( http://sourceforge.net/apps/mediawiki/gridlab-d/index.php?title=Power_Flow_Guide ) See powerflow/regulator.cpp(349).

schedule_read(SCHEDULE *schedule={name='string',...}, TIMESTAMP ts=%

• The schedule could not be read because the local time could not be determined. Fix the problem causing the local time system failure and try again. See gldcore/schedule.c(1253).

skewness aggregation is not implemented

• An attempt to use the skew aggregator failed because it is not implemented yet. Remove or replace the reference to the skew aggregate and try again. See gldcore/aggregate.c(464).

Switch from node is not specified

• The from node for a line or link is not connected to anything. See generators/controller_dg.cpp(453).

unable to register class lights

• The file that implements the lights in the residential module cannot register the class. This is an internal error. Contact support for assistance. See residential/lights.cpp(59).

unable to register class pw_load

• } else { oclass->trl = TRL_PROVEN; } defaults = this; if (gl_publish_variable(oclass, PT_int32, "powerworld_bus_num", get_powerworld_bus_num_offset(),PT_DESCRIPTION, "bus_num key field of the load", PT_char1024, "powerworld_load_id", get_powerworld_load_id_offset(),PT_DESCRIPTION, "load_id key field of the load", PT_double, "power_threshold[MVA]", get_power_threshold_offset(),PT_DESCRIPTION, "power threshold for this object to trigger a model update", PT_double, "power_diff[MVA]", get_power_diff_offset(),PT_DESCRIPTION, "current power difference posted to this object", PT_complex, "load_power[MVA]", get_load_power_offset(),PT_DESCRIPTION, "constant power draw on the load", PT_complex, "load_impedance[MVA]", get_load_impedance_offset(),PT_DESCRIPTION, "constant impedance draw on the load", PT_complex, "load_current[MVA]", get_load_current_offset(),PT_DESCRIPTION, "constant current draw on the load", PT_complex, "last_load_power[MVA]", get_last_load_power_offset(),PT_DESCRIPTION, "constant power draw on the load", PT_complex, "last_load_impedance[MVA]", get_last_load_impedance_offset(),PT_DESCRIPTION, "constant impedance draw on the load", PT_complex, "last_load_current[MVA]", get_last_load_current_offset(),PT_DESCRIPTION, "constant current draw on the load", PT_complex, "load_voltage[V]", get_load_voltage_offset(),PT_DESCRIPTION, "transmission system voltage on this load", PT_double, "bus_nom_volt[V]", get_bus_nom_volt_offset(), PT_DESCRIPTION, "Nominal voltage of PowerWorld load", PT_double, "bus_volt_angle[deg]", get_bus_volt_angle_offset(),PT_DESCRIPTION,"Current voltage angle of the PowerWorld load", // PT_complex, "next_load_power", get_next_load_power_offset(), PT_double, "pw_load_mw", get_pw_load_mw_offset(),PT_DESCRIPTION,"Real power portion of total power of the PowerWorld load", PT_complex, "pw_load_mva", get_pw_load_mva_offset(),PT_DESCRIPTION,"Complex value of total power of the PowerWorld load", NULL)<1){ char msg[256]; sprintf(msg, "unable to publish properties in %s",__FILE__); throw msg; See network/pw_load.cpp(99).

unexpected motor state

• This is an error. Please submit a bug report along with at the dishwasher object & class sections from the relevant GLM file, and from the dump file. See residential/dishwasher.cpp(1412).
• This is an error. Please submit a bug report along with at the dryer object & class sections from the relevant GLM file, and from the dump file. See residential/dryer.cpp(843).
• This is an error. Please submit a bug report along with at the range object & class sections from the relevant GLM file, and from the dump file. See residential/range.cpp(878).

unitfile: 'string'

• An error occured while reading the unit file. See gldcore/unit.c(599).

unknown microwave state

• The microwave is neither on nor off. Please initialize the "state" variable to either "ON" or "OFF". See residential/microwave.cpp(263).

unknown regulator connect type

• Check the connection type specified. Only a few are available at this time. Ones available can be found on the wiki website ( http://sourceforge.net/apps/mediawiki/gridlab-d/index.php?title=Power_Flow_Guide ) See powerflow/regulator.cpp(356).

unknown transformer connect type

• An unknown transformer configuration was provided. Please ensure you are using only the defined types of transformer. Refer to the documentation of use the command flag --modhelp powerflow:transformer_configuration to see valid transformer types. See powerflow/transformer.cpp(928).