Running most finite element models requires the solution of very large sets of simultaneous equations. The sets of equations solved in most pipe stress programs are on the order of 100-to-10,000 equations of relatively small active column sizes. The sets involved in most finite element calculations are easily an order of magnitude larger, resulting in a squared increase in solution time and computer resource requirements. Accordingly, the user should not start a finite element calculation on anything slower than a 300 MHz. Pentium processor with at least 128 Mb of RAM, and at least 300Mb free on the hard disk. Larger and faster machines are preferable.
The finite element program runs as a background application. The user will not see it on the task bar when running. The only way to “see” FE/Pipe running in the background is by bringing up the task manager under Windows NT/2000 or by hitting <cntrl><alt><del> under Windows95 or Windows98. When looking at the displayed processes (programs) the user might see either:
modgen fepre
premini
If any of these programs are running in the process list then the FEA program is running. All program errors should be trapped and reported. On a slower machine, (depending on the problem geometry), the solution might take upwards of 20-to-30 minutes to solve. On 500+ MHz Pentiums solutions should take only a few minutes.
During solution a file: __file__.loc is maintained in the job run directory and CPU usage should be at about 80%.
If there is no graphics in the output window when the job completes then most likely an error occurred and the user should find it described in the tabulated reports.
There are several files that might give the user some guidance during an abnormal termination, and they are:
error.log – Written if an abort occurred in the logic part of the preprocessing phase.
modgen.err – Written for every job, but may contain a description of any errors that occurred during model geometry construction.
input.add – If this file exists then it should contain a description of the model geometry. When a job does not complete successfully the user is encouraged to review this file thoroughly for potentially errant input. If errors in the input are found, the user should correct them and rerun the model. In any event, when a particular job aborts, the input <name>.nozzlepro file should be forwarded to [email protected] for review.
__file__.loc – Written during execution of the finite element portion of the run. This file contains the percentage of the current phase that is completed and the name of the current phase of the execution.
Troubleshooting the Installation:
If the software loads correctly and seems to run but does not produce the output data panes then most likely:
a) Internet Explorer 5.0 or later is not correctly loaded on the machine, or b) The user has run out of hard disk space, or
c) A geometry error has occurred.
If the NOZZLE-FRAME.HTM does not exist in the...\<jobname>\OUTPUT subdirectory then the job aborted or is still running. Jobs will abort if there are insufficient resources to solve the finite element problem.
If you get the message that your executable has been invalidated then you will need to contact the Paulin Research Group for a more recent version of the program.
If you get an error attempting to load the help, then either your version of WordPad or Word is out-of-date and needs to be updated. If you have an acrobat reader, the help documentation is also provided in a pdf file format.
If the program aborts whenever you try to run then you should make sure that you have the rights to create folders and files in the current working directory. If you are unsure of the current working directory use the “Files” button to show you what Nozzle PRO thinks is the current working directory.
If NozzlePRO will not install, then make sure that you have read AND WRITE access to the windows subdirectory.
(This access is required by the MS program installer.)
If the program always starts in DEMO mode after you have authorized it, then make sure your shortcut is pointing to the program STARTNP.EXE.
Troubleshooting the 3d model viewer
The NozzlePRO 3d models require that Microsoft DirectX 7.0A or later be installed on the machine. Microsoft describes DirectX as follows:
“What is DirectX?
Windows 2000 supports DirectX 7.0, which enhances the multimedia capabilities of your computer.
DirectX includes accelerated video card and sound card drivers that provide better playback for different types of multimedia, such as full-color graphics, video, 3-D animation, immersive music, and theater sound. DirectX enables these advanced functions without requiring you to identify the hardware components in your computer and ensures that most software runs on most hardware systems.”
Microsoft also suggests how to Troubleshoot DirectX as follows:
Troubleshooting DirectX
You can diagnose and resolve DirectX problems using the DirectX Diagnostic Tool and the Multimedia and Games Troubleshooter. The DirectX Diagnostic Tool helps you test the functionality of DirectX, to diagnose problems, and to configure your system to optimize DirectX performance. The DirectX Diagnostic Tool (Dxdiag.exe) is installed with DirectX. For information about using the DirectX Diagnostic Tool, click the Help button in the DirectX Diagnostic Tool.
The Dxdiag.exe screen is shown below:
Click on the display tab (there may be several display tabs – check them all), and then execute the DirectDraw and Direct3d tests. If dxdiag.exe cannot be located on the computer, then on the computer does not have directx
installed. DirectX can be downloaded from the Microsoft website for Windows 98 or 95 operating systems.
(Microsoft never provided DirectX 7.0 or later versions for NT.) The 3d viewer File:Options dialog box appears below:
When the program is installed it will try to use DirectX8. If DirectX8 is not installed it will shift to DirectX7 automatically and ask you to restart the program. If you don’t have DirectX7 or 8 loaded then you cannot use the 3d viewer. Several other items should be checked if there is 3d viewer abnormal behavior:
1) Make sure that you have the latest drivers for your video card.
2) Make sure that you have any patches for DirectX.
3) If you have DirectX7 – try loading DirectX8.
4) If you have DirectX8 – then try switching to DirectX7 in the dialog box above. (8 supports 7).
5) Try disabling hardware acceleration in the dialog box above.
6) If none of these help, then odds are that trying the same on another, different machine WILL work.
DirectX technologies attempt to get the most out of the video performance on the machine. Older versions of BIOSs, drivers or chip sets may produce erratic behavior. Usually moving to another machine will solve the problem. Some machines use hardware that is too new, and has not been adequately tested with DirectX. Some older machines have the same problem. This will be an ongoing nuisance as hardware and software changes continue at such a rapid pace.
Two types of 3d geometry files are created by NozzlePRO, and each is stored in the
<input_directory>\<filename>\OUTPUT subdirectory on job completion. The NOZZLE”n”.FEX file contains shaded images of the model for each load case analyzed. NOZZLE”n”.FEA files contain stress results for the different stress types for the different load cases, e.g. (NOZZLE1.FEX and NOZZLE3.FEA.) These files are registered file types with the operating system and are associated with the program VIEWFE.EXE. When the user clicks on a 3d button, or double clicks on the file directly, the 3d viewer should start and display the corresponding image. These file types are registered with the operating system during each program startup. If there is an error the user will be notified at that time. The file type registration can be checked by double clicking on “My
Computer:... Folder Options ... File Types” The user may have to hunt for the “Folder Options” button in the My Computer menu as it appears in different places depending on the operating system. When the “File Types”
button is clicked, the user should scroll down the file_types window that appears until the Finite Element Analysis and Finite Element Mesh files are found. This display on a Windows 2000 Operating system is shown below, (it is different on a machine with another operating system.)
Search for the “Edit File Type” button, (again, could be in a variety of places depending on OS), Click on “Edit”
or otherwise check the location of the application used to perform the “open” action. An example of this screen is shown below:
The application path and name should be the current version of the viewer. If not, then it should be changed.
Chapter 2 – Section 7
FE/PIPE, NozzlePRO, PVElite, and CodeCalc
Using the FE/Pipe Input Editor:
In the Options form (shown below), click on “Use FE/Pipe Editor During Run.” When this checkbox is marked the FE/Pipe data editor will be displayed prior to any plot or run. The user familiar with FE/Pipe can then make any changes needed to the input and continue on in the normal run sequence with NozzlePRO. This option is used most often under the direction of a support engineer to tweak an otherwise unwieldy model. FE/Pipe users often find generating models in NozzlePRO (especially structural models), convenient, and so use this feature to build their FE/Pipe input file. The FE/Pipe Editor can also be used to view certain geometry errors that are not trapped by NozzlePRO. The user can enter the FE editor and then “plot” the model from the editor data screen. In some cases error messages will be seen here that were not reported otherwise.
The user can also check all three of the boxes shown below on the Optional data form. The FE/Pipe editor can then be used to edit and run the model data. The FE/Pipe input file will be saved and the user can continue running the modified data. User’s should only beware that changes made in the NozzlePRO forms will not take effect when running in this mode.
The recommended procedure for running in this mode follows:
1) Check the Use FE/Pipe Editor During Run and Leave FE/Pipe Data Files boxes. (See above.) 2) Make sure all NozzlePRO input is as close as possible to the desired model.
3) Click Run FE.
4) When the FE/Pipe editor appears make the necessary changes to the model.
5) Select the option SUBMIT for Analysis to exit the FE/Pipe data editor. The run should continue through to completion if an editing error was not made.
6) The standard NozzlePRO results will appear.
7) To prepare for a second run check the box “Use Existing FE/Pipe Input File” on the Options data form.
8) Click Run FE. You will now be put back into the FE/Pipe data editor with the old input. This can now be modified for a second run.
Using a NozzlePRO ifu file in FE/Pipe:
FE/Pipe input from NozzlePRO for 3d shell elements is stored in the file NOZZLE.IFU. This file is found after a run has completed in the \<name>\OUTPUT subdirectory. This file may be read into FE/Pipe and used normally if the latest version of FE/Pipe is installed on the computer. The FE/Pipe input from NozzlePRO for axisymetric 2d and brick models is stored in the file SETUP.IFU also in the \<name>\OUTPUT subdirectory.
To use NozzlePRO with PVElite and CodeCalc several things must happen:
1) You must have a licensed and validated copy of the program. (You should receive a site key and be able to run NozzlePRO outside of PV Elite or CodeCalc as described in this manual.)
2) You must tell PVElite or CodeCalc where NozzlePRO is loaded. Enter PVElite input menu, choose component analysis module, that will launch CodeCalc, then under the CodeCalc tools menu, select configuration, then choose miscellaneous app, and there set the path to the folder where nozzlePRO is installed. This will store the path for all future runs and will only have to be done once.