Fluid_Aspect_Course_7_1 - nasa/gunns GitHub Wiki

Fluid Aspect Course 7.1: Common H&S Messages

Initialization Errors

In general, all ERROR and FATAL severity messages to H&S during simulation initialization mean that the affected network hasn’t been initialized and won’t cycle if you still mode the sim to RUN. You must fix all these errors before you can run the network.

These are the most common mistakes you’ll make that will be caught during simulation init. Most H&S messages are self-explanatory. Here is more info on those that aren’t:

From Nodes:

“Caught exception from initialization.”: The named PolyFluid object inside the node threw an exception when it was initializing. Check the H&S log for its error message immediately preceeding this node’s message.

“Node has insufficient initial pressure.”: You can’t initialize a normal node with a pressure less than FLT_EPSILON.

“Node has insufficient initial temperature.”: You can’t initialize a normal node with a temperature less than FLT_EPSILON.

From Nodes, due to attached capacitive links:

“Node has initial volume < 0.”: You can’t initialize a normal node with a volume less than zero.

“Node set illegal expansion scale factor.”: Expansion scale factor must be between (0-1).

From Fluids:

“Mass fractions don’t add up to 1.”: The Fluid State object in the drawing that defines this fluid’s initial state has mass fractions that don’t add up to 1. They must sum to exactly 1.

“Non-zero constituent fluids not all the same phase.”: You tried to mix liquid & gas phase in the Fluid State object. Either all of the gas phase’s or all of the liquid phase’s mass fractions must be zero in any Fluid State object.

From Links, due to bad shape data:

The most common errors are due to shape data values missing or out of acceptable range. See the link’s GunnsDraw help page for valid ranges & syntax. An example is:

“Link has max conductivity < 0.”: All conductors will throw this.

From Links, due to bad node connections:

“Link has all nodes uninitialized or vacuum.”: Links initially create their mInternalFluid by copying the mContents of one of the attached non-Ground nodes. This error means that the link couldn’t find any attached non-Ground nodes to copy from.

“aborted setting a port: ports cannot share the same non-boundary”: Most links do not allow two or more connections to the same non-Ground node.

Most link classes have unique rules for what nodes they can connect to. The link help pages list these rules. Here is an example of an error message:

“aborted setting a port: must assign port 1 to the boundary node.”

Run Errors

These messages can be ignored if they only happen occasionally:

“Combined flow rate magnitude < DBL_EPSILON.”: A link tried to add two fluids together at too low of a mass flow rate. Most links skip mixing fluids if the flow rate is below a threshold. Some link classes may forget to check this, giving the occasional error, which is not serious. If this message is repeated constantly, then it probably indicates a bad link design — let us know about it.

Previous Page / Next Page

⚠️ **GitHub.com Fallback** ⚠️