==== AFT Impulse 4.0 (Version Date 2013.07.

03) Release Notes ===== This file contains last minute information not included in the version 4.0 manua l. Topics. 1. Information about tokens. 2. Errors in and updates to the AFT Impulse 4.0 manual 3. Example and verification files included 4. Notes for network installations 5. Setting up User Log tracking 6. Graphic Server conflicts 7. Changes and bug fixes

============================================================== 1. Information about tokens ============================================================== Information on issues related to protection tokens is given in two places. The T OKEN.HLP file located on setup CD has basic information about managing tokens. T he Impulse.HLP file has additional information about setting up pointers to toke ns located on LAN's or WAN's. Look for the CONTROL.AFT topic. ============================================================== 2. Errors in and updates to the manual ============================================================== None. ============================================================== 3. Example and verification files included ============================================================== In addition, a directory called VERIFICATION is created. Here there are numerous files that give information on calculation verification. ============================================================== 4. Notes for network installations ============================================================== See the Impulse.HLP "Information on Software Installation" topic for important i nformation about network installation. There are two parts which need to be installed for AFT Impulse to function: 1) t he application, and 2) the copy protection. Note that these installation steps n eed to be performed as an administrator and with elevated permissions as require d by the operating system. The full application can be installed on each user's computer or on a networked server. In either case the copy protection needs to be installed on the server. Below are the steps to take in these two situations.

*** Application AND copy protection BOTH on the SERVER*** 1) Install the full application on the server using the "Network Installation" o ption. 2) If the installation was downloaded from AFT's website then also download the Client Setup and save it in a folder called Network Client Setup that is located below the application folder from step 1. You may need to create this folder. 3) Install the copy protection by running the AFTCopyProtectionSetup. If a USB k ey or Crypkey has already installed for another application it usually does not need to be reinstalled but may need to be updated to run the new application. 4) On each client, run the Network Client Setup which should be located in the N etwork Client Setup folder (see step 2 above) on the server. This will create th e shortcuts on the client to the application on the server as well as install/re gister DLLs, OCXs and example model files. 5) If Crypkey is used for the copy protection, then each client must run the AFT CopyProtection setup to install the client portion of the Crypkey files. *** Application on the CLIENT with the copy protection on the SERVER*** 1) Install the copy protection on the server by running the AFTCopyProtectionSet up. If a USB key or Crypkey has already installed for another application it usu ally does not need to be reinstalled but may need to be updated to run the new a pplication. 2) Install the full application on EACH client using the "Client Installation" o ption. 3) If a Network USB key (red) is used then the Nethasp.ini file may need to be m odified with the IP address of the server. See the HASPKeyGuide.pdf located in t he AFT Products folder on the server for more information. 4) If Crypkey is used for the copy protection, then each client must run the AFT CopyProtection setup to install the client portion of the Crypkey files. ============================================================== 5. Setting up User Log tracking ============================================================== Summary of User Logs Each time a user starts AFT Impulse, information about the user s computer log-on name, computer name and time AFT Impulse was started is automatically logged in a file called ImpulseUser.log. This file is located in a folder called Logs. The log can be viewed using the AFT User Log Viewer that is installed in the App lication folder. This will show all people currently using AFT Impulse. Chempak data token usage is logged in to a separate file that can be viewed using the Us er Log Viewer. Note: This log file is only created when software tokens are used. No log file i s created if a hardware key is used. Using the AFT User Log Viewer When AFT User Log Viewer is started, it will automatically determine where the a pplication token is located and try to open the user log file. The User Log View er can be run independently and does not need to have AFT Impulse running to wor k. A table at the bottom will show the current people using AFT Impulse. It will show the log-on name of the user, the computer they are using and the time they started AFT Impulse. If there is contact information available (see Requiring C ontact Information below) it is also shown. Choosing Refresh from the File menu

can refresh the list. Other information about the log file and token is also shown above the user tabl e. This includes the location of the log file, the date and time the log was cre ated and last modified, the location of the token, the token serial number and t he maximum number of current users. You can switch to view the user log for the Chempak data by choosing Chempak Log from the File menu. This will show the people who are accessing the data files from any application. For example, if one person is using the Chempak data in AF T Arrow, another in AFT Impulse and a third in Chempak Viewer; all three users w ill be listed in the table of users. You can switch back to the application user log by choosing Application Log from the File menu. Control.aft and Remote Tokens The AFT User Log Viewer relies on the Control.aft file located in the applicatio n folder to determine which application log file is to be viewed and where the a pplication and Chempak tokens are located. If this file is not found an error oc curs because the User Log Viewer cannot get the required information to run. The default location for the application token is the application folder. Howeve r, the tokens can be deployed at a different location for various reasons. The C ontrol.aft file describes where the token is found. The User Log Viewer will use this information to determine where the log file is located. The log file is al ways placed in a folder called Logs, which is a sub-folder of the location set i n the Control.aft file. The Control.aft file also describes where the Chempak data files and the Chempak data token are located. If no license or token is found for the data, an error occurs and no information will be given. Requiring Contact Information It can be helpful to have more information about the person using AFT Impulse (o r Chempak data) than is standard. In this case contact information can be requir ed. To enable this feature, open the log file (located in the Logs folder) and f ind the heading [FILE CONTROL] and set Require Contact Info = TRUE If contact information is required but not available, the user that launches AFT Impulse will be asked to provide his/her name, location and telephone number. T his information is saved in the user s Impulse4.ini file, located in the Window fo lder. This information can be changed by the local user by editing the Impulse4. ini file with a standard text editor such as Notepad. Disabling the User Log Feature The feature of logging users can be disabled by editing the log file (located in the Logs folder). Find the heading [FILE CONTROL] and set Enable Log = FALSE Multiple Entries and Other Problems Occasionally a user may be entered in the log file even though he has closed the

application. This can occur for a number of reasons, including not exiting the application normally. If this happens, the next time the user launches the appli cation he will be asked if he wants to overwrite the entry in the file with this new log-on information. Typically the answer is "Yes, overwrite the information ". If the user is actually running two incidences of the application then answer "No" to this question and both incidences will be logged.

============================================================== 6. Graphic Server conflicts ============================================================== AFT Impulse uses a third party tool for graphing called the Graphics Server. The re are four files that are used to load and run the Graphics Server: GRAPHS32CX GSW32.EXE GSWDLL32.DLL GSWAG32.DLL Because of how the Graphics Server is written, multiple copies of GSW32.EXE or G SWDLL32.DLL in your Path will cause problems when your try to load AFT Impulse 4 .0. In practice, the most common problem is a network installation where all AFT Imp ulse files have been installed into the network folder along with AFT Impulse. T hus, GSW32.EXE and GSWDLL32.DLL will exist in the AFT Impulse network folder. A client PC which happens to have copies of either or both of these files on the l ocal hard drive (usually in the WINDOWS\SYSTEM folder on Windows 9x and WINNT\SY STEM32 on Windows NT/2000) will fail to load properly. The most likely reason co pies exist on the local hard drive is another application installed locally uses them. A complete list of your options is given below, along with an explanation of the impact of each option. The recommended option is number 5. In the following exp lanations, the term conflicting files means the GSW32.EXE and GSWDLL32.DLL files . Your WINDOWS\SYSTEM folder is just called your SYSTEM folder. 1. Delete the conflicting files on your hard drive. This will solve the problem for AFT Impulse 4.0, but may cause other software you use to stop working. This is not a permanent solution in that if you install other software in the future that installs copies of the conflicting files into your SYSTEM folder, the curre nt problem with AFT Impulse will occur again. 2. Change the names of the conflicting files on your hard drive. This will solve the problem for AFT Impulse 4.0, but may cause other software you use to stop w orking. However, when you try to run the other software and it fails to load bec ause of these missing files, you can change the names back to the original names . This will then cause AFT Impulse 4.0 to stop working until you rename them onc e again, but will allow you to run your other software that needs these files. T his will also require you to remember which files you renamed. This is not a per manent solution in that if you install other software in the future that install s copies of the conflicting files into your SYSTEM folder, the current problem w ith AFT Impulse will occur again. 3. Move the conflicting files on your hard drive into the application folder tha t uses them. This will solve the problem for AFT Impulse 4.0 and still allow the other software you use to run properly. However, you will need to know which so ftware uses the conflicting files so you can copy the files into their folder. I f you remember what you do, you can move the files out of the SYSTEM folder (or

wherever conflicting files exist) and into a temporary folder. When a software a pplication that used to work fails because these files are missing, you can copy the files into its folder at that time. This is not a permanent solution in tha t if you install other software in the future that installs copies of the confli cting files into your SYSTEM folder, the current problem with AFT Impulse will o ccur again. 4. Allow AFT Impulse 4.0 to automatically rename the files for you. This is not a perfect solution, but it does have advantages. This option enables a feature w hereby AFT Impulse searches for the conflicting files in both your SYSTEM folder and WINDOWS folder before the full AFT Impulse application is launched. If it f inds them, it automatically renames them and thus only the copies in the AFT Imp ulse network folder are found. When you exit AFT Impulse, the files will be rena med back to their original names. The advantages are, 1) you can continue to run your other software that uses these files and AFT Impulse with no conflicts (as long as they are not run at the same time) and, 2) even if you install other so ftware in the future, this option will continue to work for you. The disadvantag es are, 1) you are permitting AFT Impulse to change files on your local hard dri ve every time it is run, which understandably makes some users uncomfortable and , 2) you cannot run AFT Impulse 4.0 at the same time as the other software which needs these files. 5. Reinstall AFT Impulse with the option to run auxiliary files on the client (r ecommended). This option is the best long-term option. To do this, first uninsta ll AFT Impulse from the network and reinstall it with the option to use auxiliar y files on the client. See Information on Software Installation for more help.

============================================================== 7. Changes and bug fixes ============================================================== *** Changes for Version Date 2007.10.12 *** None: Initial Release *** Changes for Version Date 2007.10.19 *** >> Changes to computation logic that could impact results << 1. None. >> Changes to data management that could impact results << 1. None. >> Changes that do not impact results << 1. With international Windows settings sometimes the font size in the Visual R eport window is unrealistically large (greater than 100 for example). Now any fon t size greater than 50 is set to 12. 2. The new Vacuum Breaker Valve three-stage option was not enabled for user se lection. Now it is enabled. 3. Increased size of information text on Output, Graph Results and Visual Repo rt window. 4. Fixed problem with models that have a large number of closed pipes and junc tions taking an extremely long time to load a scenario.

*** Changes for Version Date 2007.10.22 *** >> Changes to computation logic that could impact results << 1. None. >> Changes to data management that could impact results << 1. There was a problem with the Pump Specifications window that caused the dat a from an existing pump junction to be lost when the window was opened. The pump was saved OK once it was defined but could not be edited without entering the data again . This was fixed. >> Changes that do not impact results << 1. The surge tank junction accepted connecting pipes at a different elevation than the junction. This feature was not intended to model uncovered pipes when tanks drain, but it was possible that it might be interpreted that way. So the feature w as removed. 2. The Graph Results feature to not show the legend was not working properly. This was fixed.

*** Changes for Version Date 2007.11.27 *** >> Changes to computation logic that could impact results << 1. A fixed flow pump that was off during steady-state and had a startup flowra te transient would never start. This was fixed. The controlled pump flow (and controlled pressure) worked fine. This change only affected fixed flow pump s with transients. 2. Fixed problem with submerged pumps that have special conditions being open with flow through that also use an internal check valve that is closed during the ini tial steady state part. The check valve was ignored and the pressure values were being propagated through the pump which caused an artificial transient. >> Changes to data management that could impact results << 1. None. >> Changes that do 1. Fixed erratic 2. Fixed problem ata. 3. Fixed problem e deselected on not impact results << toolbar and menu behavior on Workspace. where the Pipe Fittings & Losses were not printing in Model D that caused long delays when multiple pipes and junctions wer the Workspace.

*** Changes for Version Date 2007.12.31 *** >> Changes to computation logic that could impact results << 1. Changed transient tee resistance calculations by adding a lower flow ratio cutoff to avoid extremely low flow ratios which can cause unstable and inaccurate results. 2. Fixed steady-state tee calculation problem when there was a negative K fact or and negative flow. Impulse could converge on a result which was poor. >> Changes to data management that could impact results << 1. The time setting was not being cleared when a pump transient model was rese t to None. This caused incorrect units to be passes when the trip time was being conve rted. Opening the Pump Specifications window again and clicking OK would reset th is. 2. There was a serious problem with Transient Control that could affect intern ational users that was fixed. The problems relates to the international use of the "," symbol as a decimal separator. A new parameter in Transient Control is the Psi weighting factor which was supposed to be between 0 and 1, but a value of 0 .5 (or 0,5 internationally) was being interpreted as "5". This was fixed and a lso checks were included to keep the value always within 0 and 1. >> Changes that do not impact results << 1. The Checklist has a button to open the relevant window and the tooltips wer e not correct. These were fixed. 2. In Transient Control added persistent drop down symbols to the Pipe Station Output grid. 3. Assigned Flow junction was not properly saving the option for transient flo w type (absolute vs. relative). This was fixed. 4. Fixed Workspace Undo problem when trying to undo the stretching of a single pipe.

*** Changes for Version Date 2008.01.15 *** >> Changes to computation logic that could impact results << 1. When using a relief valve which has two pipes and exits directly to an exte rnal pressure, and when the constant Cv or K model was used, the values for the adjacent pipes were not updated by the solver and hence were never correct once the valve opened. This would affect all results that occurred after that point. This was fixed. >> Changes to data management that could impact results << 1. Fixed problem when an fixed loss value was entered directly in the Pipe Spe cifications Window when the regional settings used a comma as a decimal separator. The

Fittings and Losses window was not affected. >> Changes that do not impact results << 1. When one moves a junction which has connected pipes, and the pipes are not moved at the same time as the junction, then when one undoes the move and then re does it, the redo would not work properly. This was fixed. 2. Fixed problem when a junction was morphed when there were no changes in any child scenarios.

*** Changes for Version Date 2008.01.17 *** >> Changes to computation logic that could impact results << 1. Fixed a problem which was amplified by a change made in the 2007.12.31 vers ion related to detailed tees. The problem exhibited itself when pipes connected to a particular tee had reference flow directions opposite of the physical flow direction. The tee calculation routine should have taken absolute values wh en getting flow split ratios but it did not. This has now been fixed. 2. Fixed a problem created in the 2007.12.31 version which caused flow imbalan ces in models with fixed or known flows in branching areas. The flows were overwri tten with initial guesses and never changed. >> Changes to data management that could impact results << 1. None. >> Changes that do not impact results << 1. Changed how the Solution Balance Summary reports steady-state mass balance. Before it tried to always sum junctions to zero and show imbalances in the In/Out field. Now the In/Out field will only display for branch junctions with a flow sou rce. And the total flow for junctions like reservoirs will show an imbalance bec ause reservoirs are imbalanced by their nature.

*** Changes for Version Date 2008.03.21 *** >> Changes to computation logic that could impact results << 1. When modeling a single pump with interpolated pump data and specifying it a s one of a series of pumps on the Options tab, Impulse would give an artificial tran sient warning and stop. In some cases the artificial transient was real, and in o ther cases it was a false warning. Cases where it was real was when there was no transient on that pump, or there was a transient using the without inertia

model, the pump trip with no backflow model, or the pump startup with no backflow model. All of the four quadrant models had warnings which were false. For the case s with real correct warnings Impulse was not accounting for the series pump settin g and only modeled a single pump. The resulting artificial transient stopped the solver. Hence the user never saw any incorrect results. This was fixed. 2. Fixed problem with Detailed Tees/Wyes that would cause the transient solver to not complete the run. This was introduced in the 2008.01.17 version. 3. Fixed a problem where the losses for a detailed tee/wye that had flow comin g in the branch and going out both straight-through pipes (or the opposite flow dire ctions) were being set to zero. This was introduced in the 2008.01.17 version. 4. Momentum term for point force nodes was not being calculated correctly beca use the value for fluid density was not being set. >> Changes to data management that could impact results << 1. For Assigned Flow and Assigned Pressure junctions the setting for Infinite Pipe transient special condition was not being applied unless transient data exi sted. This was fixed. 2. When reading in models from Impulse 2 it was possible for the pointers to t he output data to become corrupted. Once this happened, Impulse could not prop erly read output even if the model was rerun in Impulse 4. This was fixed. 3. Fixed problem with importing AFT Fathom files with Elbows, Heat Exchangers, Orifices Screens and Venturi. They were being converted to lossless Branches. They a re now changed to General Components with the original loss value. 4. Fixed problem combining pipes that have additional losses. The loss types w ere not being combined properly. 5. Fixed a problem with force sets having the same ID. This occurred when the Transient Control was opened with existing force sets and a new one was add ed. >> Changes that do not impact results << 1. Fixed snap to grid problem when pipes or junctions were near an edge. 2. Fixed Workspace drawing anomaly when pressing the escape key while drawing a new pipe. 3. When in the Branch Specifications window, the F5 jump to next specification s window option did jump but did not close the Branch Specifications window w hich made it appear like it was not jumping. This was fixed. 4. Was not displaying pulp and paper stock properties when using constant prop erties in System Properties. Fixed this. 5. Added millibars (mbar) as unit of pressure 6. Fixed problem during transient run where a pump speed goes to zero and an e

rror occurs. In some cases Impulse was dividing through by the zero speed to obt ain 7. o a torque causing a divide by zero error. This was fixed. Fixed problem printing the Model Data. An error would occur if there were n

Fittings & Losses in the model. 8. Fixed problem reading in pumps from Impulse 2.0 files. 9. Allowed empty database files to be the target file in Database Manager. 10. Fixed problem displaying "Pipes and Junctions Only" in Model Data. 11. Fixed problem with the wavespeed being shown as defined when it had no valu e set. 12. Fixed problem printing the Visual Report legend units in Transient mode. 13. Made modifications to the estimated run time calculations.

*** Changes for Version Date 2008.04.18 *** >> Changes to computation logic that could impact results << 1. During the transient a flow control valve which was closed by the user does not calculate correctly and gives erroneous results. This was fixed. 2. Fixed a problem where a valve would not open if connected to a partially fu ll pipe. >> Changes to data management that could impact results << 1. Fixed problem in Global Junction Editing where if only the database name wa s selected, the data was not applied, only the name which caused inconsistent data. >> Changes that do not impact results << 1. Fixed printing problem for Graph Results which could cutoff part of a graph in certain cases. 2. Allowed empty database files to be the target file in Database Manager. 3. Fixed problem where the model data setting for pipes would not be set as th e user default unless the Model Data Control window was first closed and reopened. 4. Fixed a problem in the Fittings & Losses database the use of a comma in the type or subtype name would cause the data to become corrupted. 5. Added more information explaining what happened when a valid license was no t found.

*** Changes for Version Date 2008.05.01 *** >> Changes to computation logic that could impact results << 1. None. >> Changes to data management that could impact results << 1. A check valve with transient data would have the data truncated when a scen ario was created or when an Impulse 3.0 model was read in. This was fixed. >> Changes that do not impact results << 1. Fixed for data field anomaly in pump specifications window when that occurr

ed sometimes when the "No Transient - Four Quadrant method is chosen.

*** Changes for Version Date 2008.08.08 *** >> Changes to computation logic that could impact results << 1. When using a General Component junction with a resistance curve, and using cavitation modeling, if the flows through the junction went to very small v alues it could lead to some unusual results. The results were not wrong, just not of good quality as compared to using something like a constant K factor. This was a result of how the polynomial behaved at very low flow rates. A change was made to handle this better when flow rates are zero or have very small values. 2. An exit valve in a closed line would cause and artificial transient because the steady state pressure was overwritten. This was fixed. >> Changes to data management that could impact results << 1. If a junction with pipe elevations/depths (like a reservoir) is moved and t hen the move is undone, the elevation/depth values were erased. This is fixed. 2. Curve fit configurations that use temperature would allow users to change t he temperature units without redoing the curve fit. >> Changes that do not impact results << 1. A Workspace display fix in the previous release to show a "T" symbol for pu mps with transients did not work properly. This is fixed again. 2. When using the batch run on multiple model files and including Model Data i n the output report content, and sending output directly to PDF files, the PDF fi le Was not created because of a file name issue. This was fixed. 3. When double-clicking a pipe or junction label on the Workspace, the user is offered the option of relocating the label or opening the specifications window. An d the user has the option to remember the selection for the future. This final op tion was shown inadvertently and did not do anything. The option is now hidden. 4. when importing a model from AFT Fathom, in order to get the wavespeed defin ed the user had to open and close each pipe window. This was a result of the pipe modulus of elasticity not being defined. Now if the Fathom model has pipe material data supplied by AFT then AFT Impulse can automatically get the modulus of elast icity and the wavespeed after the System Properties are specified. 5. Previously Impulse always saved the input file when a model was run in orde r to preserve all the output. This was inconsistent in that the user never expli citly saved the model file and it could cause confusion. Now the model is not sav

ed. If the user does not save the model with the output, they are prompted (as before) to save it when they exit the model. But now if they choose not to save it, they do not preserve their output. 6. In the Output window junction table the inlet and outlet static and stagnat ion pressures displayed confused some users in certain cases. Specifically, whe n junctions had multiple pipes connected the definition of inlet and outlet, as well as the difference between static and stagnation pressure was ambiguous. No calculation logic was changed, but the display logic was changed to make th e displayed values less confusing. This was done for Spray Discharge, Assigned Pressure and Relief Valve junctions. 7. If only one data point was used for a pump curve the resulting curve fit wa s not done and the graph looked like random noise. This was changed to be a flat line. 8. When user selects "No" when prompted to update the curve fits in the Curve Fit Configuration window after changes are made, control is returned to the configuration window instead of closing the window.

*** Changes for Version Date 2008.12.04 *** >> Changes to computation logic that could impact results << 1. None. >> Changes to data management that could impact results << 1. Fixed problem with the Surge Tank where the transient data was not being sa ved. 2. Fixed minor problem with pipes with intermediate elevations. If the user us es a "reverse pipe direction" on a pipe with intermediate elevations, and then immediately runs the model without re-opening the pipe window or saving the model and re-opening from disk, then the maximum and minimum pressure output coul d be incorrect. 3. Fixed a problem when you have a pump in your model with variable speed cont rol to control on suction or discharge pressure (or head) and the control point is conditional in that the pump only controls when the control point is exceed ed. The results are correct when you run the model, but if you save the model and r e-open it the speed is displayed as 100% and the pressure and head rise are displa yed as if the pump was running at 100%. This was fixed. 4. When importing models from Fathom that had non-cylindrical pipes, Impulse c ould get confused on the geometry which would give errors when trying to section the

pipes. This was fixed. 5. For submerged pumps with fixed flow the steady-state pump head was reported as zero. This was fixed. Also, the junction inlet pressure was reported the sa me as the outlet pressure and reports a true inlet pressure. 6. When exporting a CAESAR II force file with multiple forces, the data for th e first force was written for all forces. This was fixed. 7. Made an improvement in force imbalance calculations in high momentum system s to better handle momentum changes which occur at an area change. This does not affect the analysis but only the post-processing of force sets. 8. Fixed problem reading in older models with a user specified additional loss valve. Unit conversion error would most likely occur when the decimal delimiter wa s a comma. >> Changes that do not impact results << 1. Fixed bug in Valve and Control Valve Specifications windows where the Open Percentage table looked for a maximum open percentage of 100% and treated decimal values like 100.0% as not equal to 100% and gave a warning. This no longer happens. 2. Fixed bug in Valve and Control Valve Specifications windows where pasting d ata into the Open Percentage table for Open Percent and Cv only without area led to the Cv data showing up in both the Cv column and area column. This no longer happe ns. 3. When trying to create a CAESAR II force file, and error would sometimes occ ur which would cause Impulse to crash. The error involved setting colors in the tabl e. 4. When using Force Sets in Transient Control and switching between Differenti al and Point forces it was possible for Impulse to get confused about the pipe indices and crash. This was fixed. 5. Added a check for pump junctions imported from AFT Fathom models which have fixed head or pressure rise which is supported in AFT Fathom but not in AFT Impul se. Now the fixed head/pressure flag is changed when the junction is read in an d set to undefined. 6. When force data is exported to a CAESAR II file format the engineering unit s of force were written in the AFT Impulse format. However, CAESAR II only accepts "Ne wtons" and "LB" or "POUND". Time is only accepted in "seconds". The export routine was changed to warn the user if necessary and to automatically write the units in a CAESAR II format. 7. If part or all of the Workspace where a hidden annotation is located the an notation would be selected. If the selected objects were deleted the annotation woul

d also be deleted. Now hidden annotations cannot be selected and are not deleted. 8. Fixed problem with the pop-up inspection window on the Workspace where it w ould lock up or crash depending on what mouse action was done while it was open.

*** Changes for Version Date 2009.02.20 *** >> Changes to computation logic that could impact results << 1. Due to conversion back and forth between single and double precision number s used for transient calculations, it was possible for models opened from dis k to have different results than those built directly and then run. This happ ened for models with significant cavitation after many thousands of time steps a nd an accumulation of small differences. Due to the uncertainty of cavitation res ults in general, neither result was more correct than the other. However, it caused concern for some customers. We have tried to identify all cases of this and have im plemented a workaround in code to enforce consistency of results. Results now may not agree 100% with those previously obtained either from direct runs or opened from disk. None of the results previously or now are more correct than the others. But now results should be 100% consistent. >> Changes to data management that could impact results << 1. When using Global Junction Edit to changing from a controlled to a fixed fl ow pump the control setting was not cleared which left the pump in the controlled state. This was fixed. 2. There was a data corruption problem when older models were opened when the transient data in child scenarios was set to 0. This has been fixed. 3. Fixed problem when the Output Control was changed in a scenario that did no t have output data. This caused any results in the child scenarios to be cleared. 4. Fixed problem changing pumps from controlled value to a specific speed usin g Global Junction Edit. >> Changes that do not impact results << 1. When using variable fluid properties and Chempak, some of the Chempak fluid names have commas. When using such a fluid for a specific pipe, the pipe data wou ld become corrupted. This was fixed. 2. If you add force sets into your model and then change your model from trans ient to steady-state it confused Impulse when trying to open the model because the pipe sectioning no longer existed. The model would not open. This was fixed.

3. Fixed an issue on the Workspace when undoing a move with a pipe which has v ertices 4. Fixed a small bug on the Pipe Specifications window when the user chooses t o specify a pipe display thickness (pixel thickness on the Workspace) a default value was not automatically entered.

*** Changes for Version Date 2009.04.03 *** >> Changes to computation logic that could impact results << 1. When cavitation happens at a junction Impulse attempts to apportion the cav ity volume equally around the junction - if all sides are cavitating. This impr oves modeling quality. For a certain cases Impulse was apportioning the volume pre-maturely before all sides cavitated. This caused confusion with cavitat ion logic and affected subsequent results. This was fixed. 2. When pumps with a pump curve and no transient at all are set to a special c ondition "off with no flow" they go through a transient solution based on the no flo w condition. Previously this was handled through the logic of using an integr al check valve which was closed. However, this was found to result in somewhat different results than if the true zero flow solution was used. This was ch anged. Note that this is a rare application in that most users would not use an "o ff with no flow" condition for a pump with a pump curve. >> Changes to data management that could impact results << 1. Fixed problem with where the warning when a partially full pipe drained wou ld be lost when the scenario was reopened. >> Changes that do not impact results << 1. Fixed problem importing pipe materials. 2. Fixed problem importing inlet/outlet elevations from a Fathom model file.

*** Changes for Version Date 2009.04.28 *** >> Changes to computation logic that could impact results << 1. When a control valve is in a flow path that is closed off it cannot maintai n its setpoint because there is no flow. The logic to handle this in some cases c ould cause premature determination of other control valve states and hence incor rect results for steady-state. 2. Changed how inline relief valves respond to Special Conditions set to Ignor e. Previously the relief valve was just set to open. It was decided it was bes t for the valve to remain permanently closed in such cases. This was changed.

>> Changes to data management that could impact results << 1. Fixed a problem introduced in the 2009.04.03 release where the Cv Variable loss model for Relief Valves would be changed to K Factor. Users of the 2009.04. 03 release that have Relief Valves with Cv Variable losses need to open the Specifications window for each and reset the loss type. >> Changes that do not impact results << 1. None.

*** Changes for Version Date 2009.07.17 *** >> Changes to computation logic that could impact results << 1. Fixed a weakness in the application of K factors at Branch, Tee and Surge T ank junctions. In all previous versions Impulse used the hydraulic resistance multiplied by the flow rate squared to obtain a pressure loss. This is corr ect but the question is which flow rate to use. Previously the flowrate used wa s that at the junction. Further consideration led to the conclusion it should be t he flow rate one pipe section away from the junction to be more consistent wit h the method of characteristics. We believe the previous method caused unstable results especially when using detailed tees. This change should ma ke the use of detailed tees more stable and more useful. 2. When using a Variable Cv relief valve model with an "internal relief valve" which relieves into discharge piping, Impulse would get confused sometimes when t he valve cavitated. The result was that the valve could stay open when it should hav e closed which could further lead to unrealistic response and predicted results. The logic under such conditions was improved to make sure the valve closed in such ca ses. 3. For vacuum breaker valves modeled as initially subatmospheric with an initi al gas mass, the check for artificial transient can give a false warning. Further, the check does not leave the valve in its initial state as intended and could s lightly affect results of the simulation. In such cases the artificial transient ch eck is now skipped for this valve. 4. The user entered K factors for Branch and Surge Tank junctions were in some cases not being applied properly during the transient. If a connecting pipe with a K factor was off (zero flow) during the steady-state then the K factor would not be applied properly during the transient. Also, if the flow was negative durin g steadystate and a K factor was entered only for one direction (only Flow In or on

ly Flow Out in the junction window) then the incorrect K factor could also get used. This was fixed. >> Changes to data management that could impact results << 1. When using variable fluid properties and global pipe editing, the bulk modu lus did not get changed. This was fixed. 2. When viewing or exporting imbalanced force data, the unit conversion for "k gf" (kilogram force) was incorrect. The conversion should have been either mult iplied by g in m/s^2 (9.81) when it should have been divided or multiplied when it should have been divided - depending on whether units were being converted to or f rom kgf. So results were off by 9.81 squared. This was fixed. 3. Added logic to handle spurious bulk modulus values should they be negative. Now instead of showing the negative value it shows nothing at all. 4. Pipes with intermediate elevations can have the maximum or minimum steady-s tate pressure occur at an intermediate point. In the Output window General secti on the overall maximum and minimum steady-state pressures are reported. If the maximum or minimum was located at an intermediate elevation Impulse would not report this. Only the overall maximum and minimum that occurred at pipe endpoints. This was fixed. Overall maximum and minimum transient pressures were always correct and not affected by this change. When using variable fluid properties and pumps with fixed flow transients (which would usually be for positive displacement pumps) and if the density changes across the pump, and if the fixed flow rate is volumetric, then an artificial transient could occur. This was a result of using suction densit steady-state flow rate but the average density for transient flow rate. >> Changes that do not impact results << 1. Fixed some problems running batch jobs when an error occurs in one of the m odels or scenarios. The batch run could get hung up. 2. Fixed display issues in Model Data for pumps where obsolete data was displa yed from older versions. Also, fixed a problem where user was told a second transien t existed when it did not. 3. Removed a spurious warning that could occur for vacuum breaker valves. If a transient error occurred then the user could be told there was cavitation a t a 4. vacuum breaker valve even though there was not. This was fixed. Modified the Isentropic Exponent calculation for ASME Steam calculations to use gamma=w^2/p*v instead of Cp/Cv. Cp/Cv is only an approximation, and the equation, which is derived from the the ASME formulation for sonic velocity, provides accurate calculations ove r the full range of steam table values. Isentropic Exponent is not currently used in

5.

y for

Fathom calcs, but the ASME routines were modified to keep them in snyc with other applications. 5. Fixed an issue where carriage returns were not handled properly when adding notes to existing notes using Global Edit.

*** Changes for Version Date 2009.10.07 *** >> Changes to computation logic that could impact results << 1. In pipe sequences which have no flow and junctions with elevation differenc es at the junction the pressure was not being calculated properly in some cases f or the steady-state case. This could cause an artificial transient. This was fixed . >> Changes to data management that could impact results << 1. If a surge tank was modeled with a short connector pipe and vapor formed at the then when it collapsed Impulse would hang. The logic was modified slightly to handle this case better. 2. The steady-state relief valve variable Cv model was changed. Previously the dP and Cv data was converted to dP vs flowrate data and dP was interpolated on thi s basis. However, the resulting dP value is different than if obtained by interpolat ing based on dP and Cv because the curve relating dP, Q and Cv is non-linear. N either is necessarily more correct than the other and all inconsistencies between the two could be resolved by using more data points in the Cv vs dP input. It was decided that since the data is entered in dP and Cv that should be the basi s of interpolation and so the solver was changed. Results should not change dram atically but it is likely there will be some differences if the relief valve opens d uring steady-state. 3. If using variable pipe resistance and Power Law or Bingham Plastic non-newt onian viscosity models, Impulse was using constant resistance based on the steady -state velocity. This was fixed. 4. When using Global Edit and changing curve-fit data, the data was changed ev en if the edit was canceled. >> Changes that do not impact results << 1. Removed spurious warning about variable density when generating force files for CAESAR II 2. Added a clarifying note to the Pipe Specifications window Fluid Properties tab which displays when variable fluid properties is used. The note explains th e

possible need for a Volume Balance junction and provides a link to the Help system. 3. Fixed problem with X-Y tables with more than 15000 data points. The tables are restricted to 32000.

*** Changes for Version Date 2010.02.01 *** >> Changes to computation logic that could impact results << 1. There was a problem with Impulse when using regional Control Panel Regional Settings where the decimal point is a "comma" and using an elbow with R/D of 1.5 as a pipe fitting loss. The 1.5 is interpreted as "15" which causes a problem with Im pulse K factor calculations at such elbows. We have fixed this. 2. Fixed a problem reading a Bend type Fitting & Loss with a r/D = 1.5 when th e decimal separator is a comma. This caused the actual loss for this type to be too l arge. >> Changes to data management that could impact results << 1. On pipe and junction specifications windows the user can push the F5 functi on key to jump to the next pipe or junction. If the user happens to have entered a value into a grid on these windows and then pushed the F5 key in some cases the n ew value was not kept. This was fixed. >> Changes that do not impact results << 1. Fixed a problem when annotations are selected on the Workspace and then del eted using the Annotation Manager Impulse would crash.

*** Changes for Version Date 2010.05.03 *** >> Changes to computation logic that could impact results << 1. There was a bug found in a very specific configuration. When a model has a loop with only one outlet that loop can only be pressurized through its outlet p ath. While Impulse has logic to handle this configuration a hole was found that depended on some arbitrary issues such as the order in how the pipes and junctions w ere built in the model. The end result was a correct Steady-state result for ev erything except the pressures in this piping. All piping could be off by a set amoun t. This was fixed. 2. Fixed problem where the pressures were not updated in a pipe that is attach ed to a closed spray. 3. Put in a check for defined reference pressures when a valve or pump changes state and the model is rerun. This check is the same as the check when the model

run is started. 4. Changed the logic to allow pressures to cross a failed-open control valve w hen it is in a pipe flow path that is closed by another junction. 5. Changed the logic to fail FCVs when the flow path that is closed by another junction. 6. The laminar friction factor for Bingham Plastic calculations was not being converted to Darcy friction factor correctly. >> Changes to data management that could impact results << 1. Fixed a problem importing Relief Valves from Fathom with Cv cs dP loss data . 2. Added a check to verify that the fluid being used in the model matched the data in the connected database. If it is different the user is prompted to update o r keep the fluid in the model. >> Changes that do not impact results << 1. Certain windows that created small graphs such as the Edit Fluid Database w indow had a print feature that did not work reliably. This was fixed. 2. Added warning about pump efficiency being greater than 100% due to user's p ump power data issues. 3. Fixed a graphing issue for profile plots with an extremely high number of c omputing stations (>32000). Previously the graph would not plot and an error would o ccur. 4. Fixed a Workspace and Visual Report minor printing problem. If the user dir ectly changed the pipe line pixel thickness on the Pipe Specifications window, it displayed properly on the Workspace and Visual Report but did not print pro perly. This was fixed. 5. Added check for pumps that when a transient speed input is selected by the user that speed data was in fact entered. 6. Added an error message when the .out file cannot be opened because the mode l is run from a folder where the user does not have write permissions.

*** Changes for Version Date 2010.12.20 *** >> Changes to computation logic that could impact results << 1. When using the partially full pipe feature, and if the pipe is completely d rained during the simulation, there was an array indexing problem for that pipe th at could cause some calculation errors. It is not believed that the errors would be significant or even noticeable, but it is difficult to say with certainty. 2. Fixed problem updating the fluid bulk modulus when the database fluid was c hanged and then the scenario was updated. This resulted in incorrect wave speeds.

3. Fixed a problem related to #3 for when variable fluid propertied were used. The bulk modulus associated with the pipes were not being updated correctly. >> Changes to data management that could impact results << 1. When graphing results for EGL/HGL/Profile plots, if the cross-plot feature was used and more than one pipe sequence was plotted, and a max/min plot wa s created, some of the curves could be misidentified. The max and min labels were reversed in some cases. 2. The Total Time Steps in Transient Control is calculated in the Transient Co ntrol window based on the Start Time and Stop Time. If the stop Time is changed a nd a child scenario is loaded then Total Time Steps may not be updated. This mea ns that even if the Stop Time is correct in the child scenario, the Total Time Step s may not be. If Transient Control is re-opened in the child the Total Time Steps is updated. But if not, the simulation may not run the right number of steps b ased on the Stop Time. This was fixed. 3. Fixed a problem using Copy-Paste where the pipes and junctions were not cor rectly connected. This could lead to problems when copying from one file and pasti ng into another. The connections would be corrected before the model was run. >> Changes that do not impact results << 1. When graphing results in one case it was possible for a pipe sequence to be mis-identified as non-sequential and the graph would not display. This coul d occur when pipes had steady-state flows which were opposite of the user's referen ce positive flow direction. This was fixed. 2. If the user chose a pump transient model "No Transient - Four Quadrant" and added user four quadrant data, the data was not being saved for the junction. Thi s was fixed. 3. If running models in batch run with the feature to run separate models, aft er each model we need to save the input file so that the output will be saved. This was added. 4. When using Chempak or ASME Steam/Water data and using variable fluid proper ties, global editing of pipe data and copying data from pipe to pipe did not copy the pressure - only the temperature and other fluid properties. This was fi xed. 5. The code to catch poor pump curve fits for 3rd and 4th order curves was the re but not called properly. So users did not get a warning they should have gotten. Th is was fixed. 6. Fixed problem where four quadrant pumps modeled as constant efficiency had an

error during the transient. 7. An error occurred when running the transient solver when using a Bingham Pl astic viscosity model and closed pipes during the steady-state. This was fixed. 8. Added flyout menu to File menu to support TRIFLEX force file generation. 9. When working with pre-existing pump junctions with multiple impeller config urations, if the engineering units used in the original impeller specification have s ince been removed from being active units (in the Unit Preferences window) then futur e editing of the pump configuration will result in a loss of the engineering units an d loss of original data. This was fixed. 10. When performing curve fits on pump data users can set a maximum x-axis valu e for flow. However, on subsequent curve fits for this pump the value is ignored. This was fixed. 11. When using the Copy Data from Junction on pump junctions which use start-up transients with motor/torque data, the motor/torque data did not copy. This was fixed. 12. Fixed problem where the Toolbox icons were displaying too large on some lap tops when running Windows 7.

*** Changes for Version Date 2011.01.12 *** >> Changes to computation logic that could impact results << 1. Fixed a problem with Relief valves modeled as inline exit valves during ste adystate that could cause convergence problems. 2. Fixed a problem calculating pressures in a zero-flow loop (isolated loop) t hat has the reference flow directions in pipes in opposite directions while also ha ving a hydrostatic pressure difference (elevation change) across a junction in tha t loop. >> Changes to data management that could impact results << 1. Fixed a problem where Save As would not copy the .out files to the new file name so the scenarios would have to be rerun. >> Changes that do not impact results << 1. Disabled vacuum breaker valve different inlet cracking pressure from extern al gas pressure because this feature is not reliable. 2. A change made in the 2010.05.03 release caused an unexpected problem with g raphs. In the Graph Results, Pipe Transient Data, if using design alert cross-plot s the legend did not display. This was fixed. 3. Clarified error message if the user somehow had a solution tolerance of zer o.

*** Changes for Version Date 2011.02.03 *** >> Changes to computation logic that could impact results << 1. The chance to impact results is very small - maybe impossible - because it appears this issue will always cause an error to occur. When using variable speed p umps with pressure control and the control is only for high or low level, the transie nt solver got an imaginary root of an equation when solving for pump speed. This resu lted in an artificial transient and no transient was run. This was fixed. 2. The FCV K factor and Cv calculation included the elevation change across th e valve. This was fixed. >> Changes to data management that could impact results << 1. Fixed a problem where flow imbalance warnings were generated when a model/s cenario was reopened When the relaxation and the relative flow tolerance were autom atically lowered. This was cause by checking the solution against the user-specified values and not the lowered values which were used during the run. 2. Fixed problem when a scenario that had controlled suction or discharge pump s was reloaded when these pumps were not actively controlling. The pumps were set to their control pressure and the results were incorrect. The pump controlling state is now archived in the model results and not recalculated. 3. The pressure drop across a FCV had the hydrostatic pressure across the valv e calculated incorrectly. This also affected the inlet conditions of the down stream pipe as well as the valve failure calculations. This was fixed. 4. The valve failure check for a PSV incorrectly included the hydrostatic pres sure across the valve twice. This was fixed. >> Changes that do not impact results << 1. The Renumber Wizard allowed you to change the pipe or junction numbers but it did not erase old output. So it could display output for pipes or junction numb ers that no longer exists. This would be resolved the next time the scenario was loa ded or the model was opened. At the moment of renumbering it could cause confusion . 2. If a valve was copied from another valve using the SameAs feature and it wa s the same handbook valve type, the K factor would be erased. This caused the jun ction to become undefined and the handbook valve type would have to be reselected .

*** Changes for Version Date 2011.04.21 *** >> Changes to computation logic that could impact results << 1. None. >> Changes to data management that could impact results << 1. When a scenario other than the current scenario and then the Scenario Manag er is closed without loading the current scenario the number of pipe and junction objects from the parent was being reset to what ever the parent of the save d scenario was. This caused the data flow from the parent of the current scen ario was corrupted and some objects which were deleted in the current scenario b ut exist in its parent were being shown. This was fixed. >> Changes that do not impact results << 1. When running Bingham Plastic non-newtonian models the Output window could s how extraneous input data for Brecht & Heller Pulp and Paper stock. The data ha d no affect on the model. 2. Changed help file format to .chm for Windows 7 compatibility.

*** Changes for Version Date 2011.05.12 *** >> Changes to computation logic that could impact results << 1. Fixed a problem with dP vs. Reynolds number resistance curves where the Rey nolds number was not being calculated correctly which resulted in incorrect dP re sults. 2. Fixed a problem with Assigned Pressure junctions using static pressures whe re it would cause the model to not converge. This problem was introduced in the 2011.02.03 version. >> Changes to data management that could impact results << 1. When a scenario was promoted it would acquire the Analysis Type of the new parent. This would cause problems graphing if the new parent was run as a steady st ate scenario. This was fixed so that the original Analysis Type was retained. >> Changes that do not impact results << 1. None.

*** Changes for Version Date 2012.01.12 *** >> Changes to computation logic that could impact results << 1. For cases when a relief valve is open during steady-state, the relief valve Variable Cv model was not working properly in some cases and would just use a lossle ss valve. This was fixed.

>> Changes to data management that could impact results << 1. The open percentage data for a valve would be lost in child scenarios. Some times if the Base scenario was opened first and then the child the data would be retained. This has been fixed. 2. Updated the impulse4.dat file with minor corrections to PVC, Ductile Iron a nd Copper Pipe. See notes in the file for specific details. 3. Fixed problem importing heat exchangers from Fathom with special conditions set. The heat exchangers are changed to branches which do not have special condition s so they were not able to be changed once in Impulse. 4. Fixed problem when global editing pumps that are from a database. The curre nt configuration was being reset to the first one. It is now the configuration that is selected in the global edit list. >> Changes that do not impact results << 1. Modified warning window that came up when partially full pipe feature was a pplied by user incorrectly. There was an option to cancel the run but if cancel wa s chosen the model still ran. This was fixed. 2. If ESC was pressed when a pipe was drawn between two junctions while in mul ti-pipe drawing mode, the pipe would be deleted. This was fixed so only the multi-p ipe mode was exited. 3. If the output was printed or a PDF was created with a model that has thousa nds of time steps Impulse would lock up or produce an error because the Transient Pipe Data (all pipes) option was defaulted to be selected. If the Print Format C ontrol window was opened and closed before printing then this option would be clea red and the printing would proceed without error. This is fixed so that it is not s elected by default. 4. fixed Global Edit problem not updating the liquid temperature setting for V acuum Breaker valves. 5. Moved metric ton units (m-ton) from the English to SI system of units. 6. Added event messages to record when the intermediate orifice trips in the 3 -stage valve junction. *** Changes for Version Date 2012.03.09 *** >> Changes to computation logic that could impact results << 1. Made a slight improvement to the infinite pipe junction calculation that us es a second order curve fit for pipes with two sections. This will only impact p ipes with two sections connected to an infinite pipe boundary. Results should be

a bit more accurate. 2. Fixed the Surge Tank junction dipping tube model (on the optional tab) when the liquid level starts initially above the dipping tube level as opposed to be low. Previously an error occurred right away. Now it calculates properly. This d id not impact results since the model would not run to produce results. >> Changes to data management that could impact results << 1. In Transient Control there is a numerical factor Psi used for cavitation mo deling. This factor should always be 0.5 in the current cavitation model in Impulse . However, the interface allowed users to change it at their option. This was changed and now the value is always set to 0.5 and the user can no longer change it . >> Changes that do not impact results << 1. Fixed a problem with the Toolbox Zoom-in feature where Impulse would crash if the zoom in was too small. 2. Changed/clarified descriptions for CH, CQ, and CE pump correction factors. 3. Changed/clarified that Output window General results for overall maximum an d minimum pressure are for steady-state. 4. Fixed an issue initializing the transient data for the 3-stage vacuum break er valve when the volumetric flow rate trigger was specified.

*** Changes for Version Date 2012.03.22 *** >> Changes to computation logic that could impact results << 1. None. >> Changes to data management that could impact results << 1. None. >> Changes that do not impact results << 1. An improvement made to the 2012.03.09 release created an issue for some international users when entering data in the Transient Control window. Thi s was related to international numbering convention support for the Psi paramette r. This was fixed. 2. Fixed minor issue with global editing of liquid accumulators. If the user e ntered only an initial volume then this could not be applied for global editing. T his was fixed.

*** Changes for Version Date 2012.10.09 *** >> Changes to computation logic that could impact results <<

1. Fixed a problem with Inline Relief Valves that use K-variable and Polynomia l loss types. The resistance across the valve was also added to the piping which c aused the flows and pressures to be off 2. Fixed a problem with Inline Relief Valve where the resistance was not being converted to Cv or K correctly. The fluid density relative to standard water was not being applied correctly which would impact results depending on the actual fluid density and how far from water density it is. 3. Fixed a problem with the user-set k factors on Sprays where it was always u sing the K-factor for the flow into pipe. It now correctly uses the K-factor for the flow in and out of the pipe depending on the flow direction. >> Changes to data management that could impact results << 1. Fixed several output display issues with Inline Relief Valves. For example, the K factor was being reported as 0, static pressures at the valve were reported as the inlet but should be n/a 2. Fixed a problem with with Inline Relief Valves where some values in the Val ve Summary were set to zero when the model was reopened. Rerunning the model r eported the values again. >> Changes that do not impact results << 1. Made minor change in the Transient Control window. This was related to hand ling international numbering convention support for the Psi parameter. 2. Fixed problem reporting the number of pumps in series in the Model Data.

*** Changes for Version Date 2012.12.17 *** >> Changes to computation logic that could impact results << 1. When using a pumps with viscosity corrections, there was an error in calcul ating the pump flow during the transient. For pumps that were under operation dur ing the steady-state this caused an artificial transient. So by default the run sto pped and impact on results would occur. However, for models with pumps off during th e steadystate which started up during the transient, incorrect flow and head calcul ations could result. 2. There was an error in how the momentum change in force calculations for for ce pairs were being made. The impact should only be significant in cases where there is a very large velocity between the From/To nodes. This issue has been fixed. >> Changes to data management that could impact results << 1. Fixed a problem when using variable fluids. If there are pipes that used a

fluid initially defined in System Properties and then the System Property data wa s changed without changing the name of the fluid, the changes would not be retained. >> Changes that do not impact results << 1. Fixed problem where selecting Same As Parent/Pipe (or Junction) Display Opt ions in the Visual Report Options was not updating the display which caused the set tings to be erased when Show was clicked. 2. Added the ability to read in and convert Fathom 8 model files. 3. Fixed a problem with writing CAESER II force files when the total number of data points for all sets was greater than 32,000.

*** Changes for Version Date 2013.05.03 *** >> Changes to computation logic that could impact results << 1. Fixed several problems with Inline Exit Relief Valves when the downstream p ipe section was closed. The pressure drop calculations were not being correctly . 2. Fixed a problem with Cv vs dP for Relief Valves if there were more than one valve in the model. Since this is an iterative process the position of the other valves would influence the one being calculated. 3. Fixed several problems with the relief valve display in the Valve Summary w here parameters were zero or did not have a value. 4. Fixed a problem getting the pressure drop for a Cv vs dP Relief Valve becau se Impulse handles this differently than Fathom. >> Changes to data management that could impact results << 1. None. >> Changes that do not impact results << 1. Fixed a problem where the pipe elevations in Visual Report using Input mode were not refreshed until the model ran. 2. An error was occurring if a user tried to enter data into the "second trans ient" data grid for Dual Event transients when XTS is active.

*** Changes for Version Date 2013.07.03 *** >> Changes to computation logic that could impact results << 1. None. >> Changes to data management that could impact results << 1. None. >> Changes that do not impact results << 1. Fixed a problem with Force Sets when one of the pipes defined in the set wa

s deleted from a parent or child scenario.