Phast Release Notes
Phast Release Notes
PHASTTM
SAFETITM
Manage hazards for safe and efficient operations
VERSION: 8.71
DATE: October 2022
Reference to part of this report which may lead to misinterpretation is not permissible.
0 October 2022 Release version 8.71 David Alvarez Boedo James Pickles James Pickles
This publication or parts thereof may not be reproduced or transmitted in any form or by any means, including copying
or recording, without the prior written consent of DNV AS.
RELEASE NOTES
Table of contents
1 BUG FIXES ....................................................................................................................................................... 2
Bug # Description
380549 3D geometry not available in Phast “CFD jet fire (flare).psux" and “CFD jet fire (riser).psux"
examples files.
Effects levels that have been copied and pasted without the properties being changed could
cause errors when loading studies into the Study Manager. Additional guards have been
introduced to Study Manager to support the case where duplicate effect levels are used.
381485 Very weak explosions can trigger RISKRES 7 errors and nullify all the risk results
unnecessarily.
383522 Background image option not available for CFD based graphs.
384666 CFD-based graphs not available in “CFD pool fire (onshore plant).psux” example file.
385390 Label of tab incorrect for "Jet Fire" consequence data export (CDE) report.
386282 Different contours between 2D and 3D pool fire modelling following CFD calculations.
For some materials (particularly for high boiling point materials e.g., heavier hydrocarbons
C5++) an incorrect pool temperature is set for the CFD pool fire simulations, leading to the CFD
pool fire being calculated using a minimal burning rate and the radiation levels being under
predicted.
389461 Wind direction units, incorrect on some jet fire graphs leading to very large wind directions
appearing.
389709 Export graphs fails with "Include Content Panel" ticked and file name includes any of the
following characters ‘&<>"
389968 Following a parallel run, some data was incorrectly being merged back to the combined results
causing its size to increase exponentially. This could lead to performance issues and problems
loading the file - often causing an "Out of Memory" error for the GIS map process (PhastGis32)
and slowness in the main application.
392252 The material to track dropdown is blank if a mixture is selected for the material and a
component within the mixture is added to the Materials tab.
392261 Changing material to track at the equipment level displays wrong stream at the scenario level.
Description In the Run Row Grid, the Plant Boundary field is never shown as mandatory even if “Use free
field modelling” is set to Free field (plant boundary) in the Flammable parameters. If a given
Run Row has only toxic Scenarios selected or if all flammable Scenarios are modelled with
100% probability of immediate ignition, then the risk calculations will run successfully for the
Run Row even if no plant boundary is selected in the Run Row Grid, since the calculations will
not involve the modelling of free field delayed ignition outcomes. However, if the Run Row has
flammable Scenarios that are modelled with an immediate ignition probability less than 100%,
the risk calculations will give an error about a plant boundary not being specified.
Description The discharge calculations may fail for a time-varying Scenario if the material is a mixture,
especially if the conditions are near the critical point.
The time-varying calculations are more likely to run successfully if you simplify the mixture,
e.g., to two components that have similar properties. If the calculations still fail with the
simplified mixture, you should perform the time-varying calculations using a single pure
component.
Non-time-varying calculations with the Leak or Short pipe scenarios may run successfully for
the mixture, especially if you have a licence for the multi-component modelling and select the
multi-component option for the Equipment item. With the initial release rate from these
calculations and with time-varying results for a simplified mixture or single component, you
could make an estimate of the time-varying behaviour and define this in a User-defined source
Scenario.
47089 The Normal boiling point can be edited for a mixture that is using the Phast64 property method
template, and this will give inconsistencies in the modelling
Description If you set the template for a mixture to Phast64 and click on Calculate, the Normal boiling
point will be one of the fields in the list of properties that is enabled and editable. However, if
you change the value, you will find that inconsistencies occur for Equipment items that have the
mixture selected, both in the calculations of phase and limits in the Materials tab, and in the
consequence calculations for Scenarios.
If you have edited the normal boiling point for any mixture, you should reset it to the calculated
value by editing the mixture and clicking on Calculate.
Description If you upgrade a v6.54 or v6.7 file that includes a standalone Pool Vaporization Model, the
Model will be upgraded as a Spill Scenario under an AST Equipment item, but it will be
removed from the Model Selection which means that it will not be included when you run the
calculations, no matter which Run Row is selected.
The upgrade is handled in this way because the standalone Pool Vaporization Model cannot be
used in the risk calculations, but the Spill Scenario can. The Spill Scenario will be incomplete
on upgrade because there is no event frequency specified, and it is removed from the Model
Selection so that it does not cause problems with the risk calculations.
You should decide whether you want to include the Scenario in the risk calculations. If you
decide not to include it but you do want to be able to run the consequence calculations for it,
you should create a separate Model Selection and Run Row for it, and only run the
consequences calculations for that Run Row.
49587 Consequence results are cleared for a long pipeline item when you change the failure
frequency data
Description If you run the consequence calculations for a long pipeline and then change any of the settings
for the failure frequency in the Risk tab for the item, the results of the consequence calculations
will be cleared even though the values for frequency are not relevant to the consequence
calculations.
50765 The translucency used to display risk contours is the value set in the Risk Contour Styles, not
the values set for the individual risk levels in the Risk Preferences
Description The Contours tab of the Risk Preferences dialog shows the colours that will be used for the risk
contours for each level of risk and allows you to edit the colour. The inputs for setting the colour
includes an A field that is set by default to 100%, which corresponds with zero translucency. If
you reduce the value for A, the Risk Preferences dialog will display a colour that has the
appropriate level of translucency applied, but the Risk Contour Plots will not use this level and
will instead use the level that is set for Translucency in the Risk Contour Style dialog. To open
the Risk Contour Style dialog, select Risk (Initial) from the Styles gallery in the Settings tab of
the Ribbon Bar.
The settings in the Risk Contour Style dialog are applied to all contours, and the default value
for Translucency is set to zero. If you change the settings in the dialog, you must generate a
new Risk Contour Plot to see the effect of the changes.
Description The dispersion calculations for vertical releases can be problematic, particularly when
determining downwind concentrations. The algorithms are based on tangents to the centreline,
and therefore vertical or near vertical clouds can run into difficulties that require special
handling. In some cases, it has become apparent that this can lead to concentration predictions
that are generally over-conservative. In most cases these problems can be solved by reducing
the release angle, so it is just off vertical, e.g., to 85 degrees from the horizontal.
90431 Issue about Material to Track is not used for risk calculations when using "Concentration and
Risk based" termination Criteria
Description When calculating risk, Safeti ignores the selection for material to track. It uses the whole
mixture concentration and assumes the concentration of interest in the model to be that of the
mixture. This is a problem for the users especially when they are using the dispersion
termination criteria of "Concentration and Risk based" to get the frequency contours of
exceeding a particular toxic concentration, and the toxic concentration comes from a dominant
toxic component which they have selected in the Material to Track.
Description The outdoor and indoor vulnerabilities on the parameter set, enabled via the workspace dialog,
do not display fireball, jet fire and pool fire radiation intensities.
92124 Parameter vulnerabilities not updating when number of radiation levels is updated
Description The outdoor and indoor vulnerabilities on the parameter set, enabled via the workspace dialog,
are not updated to reflect the number of radiation levels specified on either the jet fire, pool fire
or fireball and BLEVE blast parameters.
Description Distance downwind to defined concentrations may show a blank field when a concentration of
interest is not reached.
However, "n/a" is presented in case of other consequence types (i.e., jet fires, pool fires,
fireballs, etc.).
"Not reached(*)" will be included instead to be consistent and ensure users understand the
context (i.e., it depends on the height of interest).
Description If you have multiple Microstation 8 CAD connections, the GIS will display the first one listed on
the Map tab only. It is not possible to display multiple Microstation 8 CAD connections on the
GIS simultaneously.
If you delete any Microstation 8 CAD connections from your study, you must close any GIS
views and re-open them before you are able to add further Microstation 8 CAD connections.
Please note that it is possible to display multiple connections of other CAD formats, including
Microstation 7, on the GIS.
240385 Option in the dialog of whether to include pool fires for flammable pool sources
Description Logic within the modelling can cause pool sources to give pool fire results. However, some
users will not want this; instead, they might want to model dispersion from the pool source
resulting in flash fire effects only.
Pool sources of flammable material will not produce pool fires unless the following warning is
seen “UDM3 1128: Mass conservation check failed. Released mass exceeds observer and
pool mass by <fraction>. Switching to equivalent pool approach.”
In those circumstances the pool fore effects can be prevented by switching the Method to
handle mass conservation failure to None. Note this can lead to underestimates in the
amount of mass and concentrations in the dispersing cloud.
It is proposed that, in a future release, users will have the option of whether to include pool fire
effects with any pool sources.
241724 Problem displaying images when inserting a georeferenced image after an interactively placed
image
Description Inserting a georeferenced raster image followed by a non-georeferenced image does not cause
any problems. However, inserting a non-georeferenced raster image followed by a
georeferenced image causes the GIS display to go blank and it is impossible to view them.
249990 Consequence data grid uses the averaging time in the parameters rather than the averaging
time defined in the scenario
Description The consequence data grid for toxic/flammable scenarios will always use the averaging times
in the Toxic/flammable parameters irrespective of the setting chosen for the averaging time
within the scenario.
The summary report displays the consequence distances for the averaging time specified in a
scenario.
Description The merging in of weathers is currently set by design. After importing from excel please ensure
to delete the default weathers from the new workspace if not required.
254979 Running a pool fire scenario using CFD calculations causes a crash when the study file is
located in a OneDrive folder
Description A crash will occur when running a pool fire scenario using CFD calculations if the study file is
located in a OneDrive folder. Please save and run the study file from the local drive.
Description A crash may occur when editing the weather folder in Phast 3D. When the weather folder
dialog is open, a random sequence of the actions below could cause the program to crash.
• Clear All
• Select All
• Select\Deselect individual weather directions
• Navigate to Angular offset or Number of directions
• Ensure that the study is saved before making changes in the weather folder dialog to
avoid losing data.
298348 Upper limit for volume inventory may sometimes be too large
Description This applies to time varying leaks and short pipe scenarios. Following message “Specified input
mass (X) kg too large for vessel volume [TVD2 10]” may appear in some cases where the
volume inventory is too large.
Workaround:
2. Reducing inventory
312490 Long pipeline: Discontinuity following irrelevant valve closure at upstream end
Description A valve closes at the upstream end causing a discontinuity when there is no pumped inflow.
The closure of the valve at the upstream end should not impact the flow in any way.
Description Workaround 1: Unzip the .psc file and extract/save the .psu file on your local hard disk.
The .psu file can be upgraded and opened in 8.7.
314616 During and after CFD calculations temperature at a point is not updated in the legend when the
user SHIFT+clicks in the 3D viewer
Description SHIFT+click in the 3D viewer during and after CFD calculations have been completed does not
update the temperature at a point in the legend.
Please generate a new instance of the 3D results viewer via the 3D dropdown of the ribbon bar
or the right-click menu of your pool fire scenario to ensure this works correctly.
Description No contours will be shown on the Standalone Pool Fire Radiation/Temperature on a Plane
(CFD) 2D graphs when requesting to plot a user-defined contour plane.
322883 Flammable cases may produce blank fire radiation graphs where the related fire scenario does
not exist
116518
323154 Flame shapes do not show immediately on standalone 2D graphs if only a contour plot is
requested
370523
Description The flame shape will not be shown immediately on radiation contour graphs for standalone
equipment when requesting only radiation/temperature contours. A workaround is either to
uncheck/check the Show Flame Shape checkbox available in Graph Tools > Consequence
tab or to request extra types of results required in the Calculations tab before running
calculations (e.g., radiation/temperature at a point calculation)
Description There should be no inventory in the tail pipe at the onset of relief action.
Workaround:
Description For the dynamic fireball model, radiation effects are reported at the time giving maximum
radiation impact at the location/plane of interest. It appears the numeric method employed in
determining the time at which maximum radiation impact is experienced at some elevated
heights of interest is struggling to find a unique solution (hence the error).
A potential workaround is to select any of the static fireball models (e.g. Roberts/TNO hybrid).
Note that with the static fireball models, radiation transect results at a fixed effect height is
largely insensitive to release height as well.
To model the impact of observer elevation relative to different release height (or, to be more
precise, fixed fireball trajectory), users could set up the linked scenario cases in question as
standalone fireball scenarios, model radiation versus distance results at relevant heights of
interest and extract the desired distances to radiation intensities from the radiation transect
results.
333869 GIS radiation contours not displayed for Standalone fire scenarios
Description As per title. Note that there are radiation contours results for Standalone fire scenarios when
requesting graphs.
Description Following message “Negative argument to square root function [Note: The MDE message
contains 1 parameter values (X) but there are 0 place holders in the reference message
description.]. [MATH 1]” may appear in some cases where the sonic velocity (non-default
velocity capping method) has been applied by the user.
The failing cases are due to the property system failing to calculate the sonic velocity.
The errors can be avoided by selecting the default “Fixed velocity” capping method instead.
Description The path to the KFX geometry is a temporary location, which gets deleted after X days,
meaning that if the .json file is imported into KFX after this period, the KFX geometry will not
load.
Workaround: create a copy of the combined.kfx geometry from Phast temp directory and place
it in the same location as the JSON file.
Note: Phast temp directory can be found by opening .json file in notepad (or similar) and find
“GeometryFile” path (e.g., "GeometryFile":
"C:\\Users\\[username]\AppData\\Local\\DNV\\Temp\\Safeti_Phast_8_7_0\\d0bd4bfc-97f7-
4572-ad62-5a54ffa56053\\Combined.kfx".
335831 BLEVE blast results in “Consequence Data” does not show distance correspond to beyond 3
overpressure levels
Description As per title. Functionally to support more than 3 overpressure levels within “Consequence Data”
results for BLEVE blast scenario will be added in future versions.
336752 3D Dispersion (Classic) results currently do not use the material to track
Description As per title. Note that the dispersion graphs use the material to track
336811 Default "3D calculation parameters" may not be applicable to all scenarios
Workaround:
2. Generate 2D dispersion graphs to see the extend/boundaries of the cloud and check:
• Sideview graph for “x” - maximum downwind direction and “z” - maximum
elevation
4. Rerun
Description We continue to explore the cause of this issue, which seems to affect Chinese versions of
Windows only. In the interim, we have seen some customers have success with performing a
Windows update, a manual update to .Net 3.5 and restarting Phast/Safeti until the GIS loads
successfully.
Description In rare occasions, the CFD calculations can become suspended when attempting to cancel /
stop them. This causes Phast to appear to be continuously attempting to stop calculations
without them ever being stopped, rendering the program unusable. If this happens, a force
closure of Phast via the Task Manager is required.
Description Phast could fail to find radiation existing ellipses for standalone fire models in some cases and
has been observed in a case of elevated pool fire so far. This problem relates to the searching
method used by Phast to locate defining points of the ellipse, i.e., the downwind, upwind and
crosswind locations, and may occur for ellipses near to the flame. The searching method could
fail to locate any one of the defining locations because of searching step size or complex
scenarios, such as ellipses below elevated pool fires.
Workaround:
Use footprint contours. Please note that contour plots are generated using point observer, the
footprint results will be slightly more conservative compared to radiation vs distance and
radiation ellipses, which are calculated using optimized planar observer.
366356 Missing green tick after a CFD run has finished successfully
Description As designed. Running of CFD allows the user to select the weather(s) they are interested in
running the CFD calculations for. If a selection is made then upon completion of the
calculations the standard classic selection is applied and then the results status for the scenario
is determined. This can mean that no 'green tick', to indicate successfully run calculations
appears next to the scenario. This is as designed as there are missing results for the other
weathers.
Description For standalone models of jet fire, pool fire or fireball, radiation predicted along a transect starts
from the release point into a specified direction. No radiation is calculated on the transect
beyond the release point in the opposite direction. In Phast/Safeti 8.7, wind can be set in any
direction for standalone fire models, starting a transect from the release point can miss critical
results on the transect in certain wind directions and this is an area for improvement.
372734 Blank input supertab after running risk results. It may happen occasionally.
Workaround 2:
2. Close Safeti
3. Reopen Safeti
377331
Description When generating graphs following a calculation involving a toxic material (regular results
graphs or toxic footprints on the GIS plot) there is potential to be presented with a set of error
messages when attempting to create the plots:
Workaround
This behaviour has been observed when the probit calculation method "Prefer Probit" has been
selected in the toxic parameters. Changing this selection to "Use Probit" creates the graphs as
intended so it is recommended to change to this setting in the event of this error.
376510
Description Geometry may be missing from 3D temperature or radiation results after running classic (non-
CFD) calculations and generating results in the 3D viewer.
379616 Flame shape disappears after generating 3D temperature/radiation results when clicking on
“Zoom In” or “Zoom Out” buttons through the Ribbon > 3D tab
Description Workaround: uncheck and check "Flame shape" from 3D results selector
Description A crash during parallel calculations will cause the user’s psux to be absent of any results from
the calculations. The user may at this point assume that running calculations in the parallel
was a wasted effort. However, it may be possible to retrieve results by locating a Result.psux
file in the temporary folder used for parallel calculations.
C:\Users\[UserID]\AppData\Local\DNV\Temp\Safeti_Phast_8_7_1\[Unique tag]\Parallel\[Unique
tag]
This file could be beneficial particularly for large studies. If there is a crash during parallel
calculations and you wish to retrieve results, please copy the Result.psux file to a safe
location, because this file will eventually be deleted automatically from the temporary folder.
Digital Solutions
DNV is a world-leading provider of digital solutions and software applications with focus on the energy, maritime and
healthcare markets. Our solutions are used worldwide to manage risk and performance for wind turbines, electric grids,
pipelines, processing plants, offshore structures, ships, and more. Supported by our domain knowledge and Veracity
assurance platform, we enable companies to digitize and manage business critical activities in a sustainable,
cost-efficient, safe and secure way.