How do I remove the "N/A" entries in the Fire Flow Node Table for nodes not included in the Fire Flow Nodes selection set?

Product(s): WaterGEMS, WaterCAD
Version(s): CONNECT Edition, V8i
Area: Output and Reporting

Problem

How do I remove the "N/A" entries in the Fire Flow Node Table for nodes not included in the Fire Flow Nodes selection set in the Fire Flow alternative?

Solution

Starting with WaterGEMS and WaterCAD CONNECT Edition Update 3 (version 10.03.04.05), the Fire Flow Node Table will be automatically filtered to only display results for elements selected in the Fire Flow Nodes pulldown menu in the Fire Flow alternative. 

If you are using an older version or are unable to upgrade to a later version that includes this feature, you may see nodes listed in the Fire Flow Node Table that have no results and will display N/A. In such a case, you can filter the Fire Flow Node Table using one of the following methods:

Option 1

  1. Open the selection set manager
  2. Double-click the selection set used in your Fire Flow alternative.
  3. Right-click anywhere in the drawing pane, choose "Edit group" and open the Fire Flow Node Table.

Option 2:

  1. Open the Fire Flow Node Report.
  2. Right-click Fire Flow Iterations column header, choose Filter > Custom.
  3. Create a filter like this: Fire flow iterations > 0

Option 3:

  1. After the fire flow scenario has been computed open the Fire Flow Node Table.
  2. Right-click on the column heading "Fire Flow (Available)" and choose Sort > Sort Ascending.
  3. Click on the first row with a computed "Fire Flow (Available)" value, hold the Shift key, then select the last row with a computed value.
  4. Right-click on one of the highlighted row headings and select Open on Selection.

See Also

Understanding Automated Fire Flow Results

Why does the Pressure (Calculated Residual) field display N/A for a steady state or EPS run?

Results show as "N/A" when clicking a node in the Fire Flow Results Browser

WaterGEMS and WaterCAD Automated Fire Flow FAQ

  • Created by
  • When:
  • Last revision by Bentley Colleague
  • When:
  • Revisions: 5
  • Comments: 0
Recommended
Related