You are currently reviewing an older revision of this page.
After computing one or more scenarios and saving the model, a large number of output files (with extensions .out, .rpc, or ..alm) are generated and stored in the folder where my model is saved. Why?
.OUT, .RPC, and .ALM files are results files that are generated each time a model is run and saved. These files are safe to delete because they will be regenerated up computing the model again.
If multiple output files are found along with the model files you have most likely computed a scenario where the calculation options have been set to run automated fire flow (calculation type = fire flow) with the Auxiliary Output Settings set to store results. The reason is because a separate steady state simulation is computed for each fire flow node. If you've elected to store output by way of the Auxiliary output settings a separate set of results needs to be saved each one in it's own .OUT file.
The extra results that are saved in these files are only used with the Fire Flow Results Browser tool (from the Analysis menu) to see results in model elements during an individual fire flow run. Note that the Auxiliary Output Settings are configured on the bottom right side of the Fire Flow alternative. To disable storing of extra fire flow results, select "None" for "fire flow auxiliary results type" and "<no elements>" for "auxiliary output selection set". You will still always see the summary fire flow results in the fire flow node table (such as minimum pressures, available fireflow, etc).
If the above is the case and you do need to store all the results for each fireflow run, you can use the custom results file path to have the output files stored elsewhere (instead of the location where the model is stored). This is under Tools > Options > Project. In order to use it click the check box that says, "Specify custom results file path?" and then enter the file by browsing out to it using the ellipsis button to the right of the text box, key in the file path, or paste in the file path that you might have copied from another folder.
Changing pipe diameter, with annotations Length (3D) and Diameter applied, results in error "index was outside the bounds of the array."
Compacting a database for optimal performance