Graphical User Interface for High Energy Multi-Particle Transport

Graphical User Interface for High Energy Multi-Particle Transport Phase I Final Report PREPARED BY: P.O. Box 1308 Richland, WA 99352-1308 PHONE: (509) 539-8621 FAX: (509) 946-2001 Email: randyschwarz@mcnpvised.com Home Page: http://www.mcnpvised.com Contract Number: NNL06AA48P July 2006

Project Summary Computer codes such as Monte Carlo N-Particle extended (MCNPX) now have the capability to transport most high-energy particle types (34 particle types now supported in MCNPX) with energies extending into the teravolt energy range. The efficient use of these types of Monte Carlo tools is very important for modeling the effects of space radiation on humans, spacecraft, and equipment. The work performed under this grant has resulted in the creation of an initial version of the Visual Editor for MCNPX. With this innovation, users of the MCNPX code have access to a powerful graphical user interface for efficient creation and interrogation of input files, which will significantly reduce the amount of time required to create and debug input files. An initial version of the MCNPX Visual Editor was created using beta source code 2.6.a downloaded from the MCNPX developer s web site. The initial version of the code satisfies all of the Phase 1 objectives and has resulted in a program that interfaces with MCNPX and has the same functionality as the MCNP Visual Editor for neutron, photon, and electron problems. Some functionality exists for the extended particles available in MCNPX, but this work is not yet complete. It is recommended that a Phase 2 grant be awarded to bring this software package into production and eventual distribution to the users. Section 7.2, Future Technical Activities, presents complete details on work suggested for Phase 2. Page ii

1.0 Table of Contents PAGE PROJECT SUMMARY... II 1.0 TABLE OF CONTENTS...III TABLE OF FIGURES...IV 2.0 IDENTIFICATION AND SIGNIFICANCE OF THE INNOVATION...1 3.0 TECHNICAL OBJECTIVES...1 4.0 WORK PLAN...2 4.1 TECHNICAL APPROACH...2 4.2 TASK DESCRIPTIONS...2 4.2.1 Compare MCNP and MCNPX...2 4.2.2 Convert Existing FORTRAN Patch to Work with MCNPX...2 4.2.3 Test/Debug the FORTRAN Patch...3 4.2.4 Modify the User Interface for MCNPX Specific Needs...3 4.2.5 Investigate the Graphical Display of MCNPX Data...3 4.2.6 Documentation...3 4.3 MEETING THE TECHNICAL OBJECTIVES...3 4.4 TASK LABOR CATEGORIES AND SCHEDULES...4 5.0 POTENTIAL APPLICATIONS...4 5.1 POTENTIAL NASA APPLICATIONS...4 5.2 POTENTIAL NON-NASA APPLICATIONS...5 6.0 CONTACTS...5 6.1 KEY CONTRACTOR PARTICIPANTS...5 6.2 KEY NASA PARTICIPANTS...5 6.3 NASA AND NON-NASA ADVISORS...6 7.0 TECHNICAL ACTIVITIES...6 7.1 RECENT TECHNICAL ACTIVITIES...6 7.1.1 Task 1: Compare MCNP and MCNPX...6 7.1.2 Task 2: Convert Existing FORTRAN Patch to Work with MCNPX...7 7.1.3 Task 3: Test/Debug the FORTRAN Patch...8 7.1.4 Task 4: Modify the User Interface for MCNPX Specific Needs...9 7.1.5 Task 5: Investigate the Graphical Display of MCNPX Data...23 7.1.6 Task 6: Documentation...27 7.1.7 Current Problems...27 7.2 FUTURE TECHNICAL ACTIVITIES...27 8.0 POTENTIAL CUSTOMER AND COMMERCIALIZATION ACTIVITIES...28 Page iii

8.1 RECENT NASA POTENTIAL CUSTOMER ACTIVITIES...28 8.2 RECENT NON-NASA POTENTIAL CUSTOMER ACTIVITIES...28 8.3 OTHER RECENT COMMERCIALIZATION ACTIVITIES...28 8.4 FUTURE POTENTIAL CUSTOMER AND COMMERCIALIZATION ACTIVITIES...28 Table of Figures Figure 7-1. Plot of an MCNP Geometry Displayed in the MCNPX Visual Editor... 8 Figure 7-2. Plot of an MCNPX Geometry Using Macrobody Surfaces Created with the Surface Wizard... 10 Figure 7-3. Plot of an MCNPX Geometry Created in the MCNPX Visual Editor... 11 Figure 7-4. Plot of a Complex Lattice Geometry Displayed in the MCNPX Visual Editor... 12 Figure 7-5. Materials in the MCNPX Visual Editor... 13 Figure 7-6. Importances in the MCNPX Visual Editor... 14 Figure 7-7. Transformations in the MCNPX Visual Editor... 15 Figure 7-8. SDEF Source Plotting in the MCNPX Visual Editor... 16 Figure 7-9. Collision Point Plotting in the MCNPX Visual Editor... 17 Figure 7-10. 3D View of a CASK Generated by the MCNPX Visual Editor... 18 Figure 7-11. Dynamic 3D View of a CASK Generated by the MCNPX Visual Editor... 19 Figure 7-12. CAD to MCNPX Conversion Performed by the MCNPX Visual Editor... 20 Figure 7-13. Cross Section Plot Generated by the MCNPX Visual Editor... 21 Figure 7-14. Tally Plot Generated by the MCNPX Visual Editor... 22 Figure 7-15. Mode Card Panel for the MCNPX Visual Editor...26 Page iv

2.0 Identification and Significance of the Innovation Computer codes such as MCNPX now have the capability to transport most high-energy particle types (34 particle types now supported in MCNPX) with energies extending into the teravolt energy range. The efficient use of these types of Monte Carlo tools is very important for modeling the effects of space radiation on humans, spacecraft, and equipment. This proposal would develop a graphical user interface for high-energy multi-particle transport. With this innovation, users of the MCNPX code would have access to a powerful graphical user interface for efficient creation and interrogation of input files, which would significantly reduce the amount of time required to create and debug input files. The MCNPX graphical user interface will be adapted from the MCNP Visual Editor, which is internationally recognized as the best code for visually creating input files for MCNP. The Visual Editor for MCNP already has many powerful features to help the user create and display MCNP geometries. These features include the ability to display multiple cross-sectional views of the geometry, optional displays of the geometry in 3D using either wire mesh or ray tracing, plotting of the source, and optional displays of particle tracks during the random walks. Because MCNPX essentially has the same geometry package as MCNP, the powerful geometry features of the Visual Editor could be extended to MCNPX in a fairly straightforward manner by adapting the interface statements that are needed in the FORTRAN for communication with the C from the Visual Editor for MCNP to a new Visual Editor for MCNPX. More work would be needed to include the many particle types and other unique features of MCNPX in this new Visual Editor. 3.0 Technical Objectives The main technical objective of this proposal is to create a graphical user interface for MCNPX adapted from the current MCNP Visual Editor code. The graphical user interface will support geometry display and creation options. Additional research will be conducted to determine how to support the many particle types available in MCNPX and what output visualization and data input aids should be added to enhance the MCNPX usability. The result will be a new Visual Editor executable that will be linked directly with the MCNPX FORTRAN code. The Visual Editor will be modified to enable the geometry features that currently work with MCNP to work directly with MCNPX. The graphical user interface will be modified as required to support the display of MCNPX geometries. Additional efforts will be made to determine what needs to be done to support the display of the different particles supported by MCNPX and also what is required to support MCNPX specific non-geometry input data. Modifications to support the different particle types available in MCNP will be performed as time permits. Page 1

Questions that will be investigated for this effort include: 1. How much do the MCNPX and MCNP FORTRAN codes differ? 2. What modifications need to be made to the graphical user interface? 3. What complications are involved in supporting the many particle types recognized by MCNPX? 4. What additional output visualization features should be added to the Visual Editor? 5. Which input data need to be supported in the Visual Editor? 4.0 Work Plan 4.1 Technical Approach Table 4-1 shows the proposed work plan. Table 4-1. Work Plan Task Objective Effort 1 Compare MCNP and MCNPX 10% 2 Convert existing FORTRAN patch to work with MCNPX 30% 3 Test/debug the FORTRAN patch 10% 4 Modify the user interface for MCNPX specific needs 20% 5 Investigate the graphical display of MCNPX data 20% 6 Documentation 10% Dr. Lee Carter of Carter Monte Carlo Analysis, Inc. (CMCAI) will mostly perform tasks 1 and 2. Randy Schwarz of (VEC) will mostly perform tasks 3 through 6 with support from CMCAI when required. 4.2 Task Descriptions 4.2.1 Compare MCNP and MCNPX Task 1 will be an initial investigation into the differences between the MCNP and MCNPX FORTRAN codes. Both codes were the same several years ago, but the codes have diverged in recent years to meet the differing needs of the users of the code. The purpose of this task is to answer technical question 1 in Section 3.0 and to develop a conversion strategy. This work will be performed mostly by CMCAI with support from VEC as needed. 4.2.2 Convert Existing FORTRAN Patch to Work with MCNPX Task 2 will result in the creation of a FORTRAN patch that will implement the conversion strategy developed in task 1. The milestone that will be accomplished is the creation of a new FORTRAN patch file that will allow the MCNP Visual Editor to link directly with the MCNPX FORTRAN code. CMCAI will do most of this work with support from VEC as needed. Page 2

4.2.3 Test/Debug the FORTRAN Patch Task 3 involves testing the FORTRAN patch and modifying the graphical user interface code if needed. Task 3 will answer technical question 2. To test the patch it is necessary to directly link the MCNPX FORTRAN code, using the patch created in task 2, with the C++ code of the graphical user interface. The testing will be performed by both CMCAI and VEC. The code will be tested to verify that all of the geometry creation and display features work when linked to the MCNPX code. This represents a fundamental building block that must be accomplished before answering the remaining technical questions. Once this link is established, the graphical user interface will have all of the MCNPX data and memory structures available for potentially displaying to the user. 4.2.4 Modify the User Interface for MCNPX Specific Needs Task 4 involves adapting the graphical user interface for MCNPX specific needs; this is an investigation that will be conducted with input from the code developers at LANL and expert users. This task will be performed by VEC with support from CMCAI to implement any necessary calls from the FORTRAN code to the graphical user interface. As a result of this investigation, a list of items will be developed, some of which could be beyond the scope of this Phase I work, but could be pursued in Phase 2 or Phase 3. Those tasks that are easily achievable will be accomplished as part of this Phase 1 grant. This task will answer technical questions 3 and 4. This work will be mostly performed by VEC with support from CMCAI. 4.2.5 Investigate the Graphical Display of MCNPX Data Task 5 will focus on specific MCNPX data that could be supported in the Visual Editor to make MCNPX users more efficient in generating the MCNPX input file. Most of this work will involve investigating specific MCNPX input data and determining what should be implemented in the Visual Editor. A list of items will be developed, most of which will be beyond Phase 1 of this work, but could be pursued in Phases 2 or 3. This work will be mostly performed by VEC with support from CMCAI. This task will answer technical question 5. 4.2.6 Documentation Task 6 will document the changes in the form of a user s manual. The existing Visual Editor Manual will be modified to include the enhancements performed as part of this grant. 4.3 Meeting the Technical Objectives The above tasks will meet the technical objectives outlined in Section 3.0 by providing a path to creating a graphical user interface for the MCNPX computer code as specified in Section 3.0. Page 3

4.4 Task Labor Categories and Schedules Tasks 1 and 2 will primarily be accomplished during the first two months of the contract. Tasks 3 and 4 will primarily be accomplished during the second two months, and the last two tasks will primarily be accomplished during the last two months of the contract. Dr. Lee Carter of CMCAI will mostly perform tasks 1 and 2. Randy Schwarz of VEC will mostly perform tasks 3 through 6 with support from CMCAI when required. It is estimated that it will take 165 hours of Dr. Carter s time and 335 hours of Mr. Schwarz s time to accomplish the above tasks. All work done by CMCAI will be performed at Dr. Lee Carter s business location in Keizer, Oregon. All work done by VEC will be performed at Randy Schwarz s business location in Richland, Washington. 5.0 Potential Applications VEC does not sell the Visual Editor; it instead releases this code to the Department of Energy code center (RSICC) to make the code available to interested users. It is believed that this provides the maximum benefit to the user community and enhances the international reputation of both VEC and CMCAI. MCNPX is available to users around the world; any enhancements to the graphical user interface enable all users of the code to be more effective in creating their geometries and performing their calculations. The improvements proposed in this document can substantially reduce the amount of time to create a computer model, benefiting users both within and outside of NASA. VEC will obtain financial reimbursement from teaching how to use this tool and from contracts with users of the tool that would like specific features added or help using the software for performing calculations. 5.1 Potential NASA Applications Any applications that require the transport of high-energy particles will benefit from this effort. These applications include: 1. Space shielding applications. 2. Evaluation of damage to electronic components in space. 3. Health physics applications for people living in space. 4. Mapping of planets. 5. Investigations of cosmic-ray radiation backgrounds and shielding for high altitude aircraft and spacecraft. 6. Charged-particle propulsion concepts for spaceflight. 7. Single-event upset in semiconductors, from cosmic rays in spacecraft or from the neutron component on the earth s surface. Page 4

5.2 Potential Non-NASA Applications Any physics applications that utilize the transport of high-energy particles will benefit from this work. These applications include: 1. Investigations for accelerator isotope production and destruction programs, including the transmutation of nuclear waste. 2. Design of accelerator spallation targets, particularly for neutron scattering facilities. 3. Research into accelerator-driven energy sources. 4. Medical physics, especially proton and neutron therapy. 5. Accelerator-based imaging technology such as neutron and proton radiography. 6. Design of shielding in accelerator facilities. 7. Activation of accelerator components and surrounding groundwater and air. 8. High-energy dosimetry and neutron detection. 9. Design of neutrino experiments. 10. Charged-particle tracking in plasmas. 6.0 Contacts 6.1 Key Contractor Participants Randy Schwarz, Principal Investigator P.O. Box 1308 Richland, WA 99352 Website: http://www.mcnpvised.com Email: randyschwarz@mcnpvised.com Phone: (509) 539-8621, Fax: (509) 946-2001 Dr. Leland (Lee) Carter, Consultant Carter M.C. Analysis, Inc. 6636 Hogan Dr. N. Keizer, OR 97303 Email: leecarter6@comcast.net Phone: (503) 304-2966 6.2 Key NASA Participants None. Page 5

6.3 NASA and Non-NASA Advisors Dr. Gregg W. McKinney MCNPX Project Leader and Radiation Transport Team Leader Nuclear Design & Risk Analysis (D-5) Los Alamos National Laboratory P.O. Box 1663, MS K575 Los Alamos, NM 87545 Email: gwm@lanl.gov, Phone: (505) 665-8367 John Hendricks Nuclear Design & Risk Analysis (D-5) Los Alamos National Laboratory P.O. Box 1663 MS K575 Los Alamos, NM 87545 Email: jxh@lanl.gov, Phone: (505) 667-6997 7.0 Technical Activities 7.1 Recent Technical Activities 7.1.1 Task 1: Compare MCNP and MCNPX This first task involved understanding how to compile the MCNPX executable using the compilers that are currently used to create the Visual Editor executable with MCNP. First the RSICC code (C00730 - version 2.5) was compiled using the steps provided with the distributed software. This software was successfully compiled both with and without the X-window graphics capability. Next the latest beta version (version 2.6.a) was downloaded from the MCNPX web site and successfully compiled. The next step was to compile version 2.6.a using the Compaq Visual Fortran/Visual C++ compiler. This was successfully performed both with and without the X- windows graphics capability. Dr. Lee Carter performed a complete review of the MCNPX FORTRAN. Here the differences between MCNPX and MCNP were investigated and the similarities were exploited to allow for the creation of a MCNPX patch file to create a version of the Visual Editor that will work with MCNPX. A number of important differences will need to be addressed later in tasks 3 through 5. Page 6

7.1.2 Task 2: Convert Existing FORTRAN Patch to Work with MCNPX Previous versions of MCNP, such as version 4C2, were written so that the source code could be updated using a patch file to make the desired update. This patch file contains the desired changes to be made in the source code, where each card in the source code has a unique identifier that the patch file can refer to for making modifications/deletions/additions involving that card. The MCNPX code configuration retains this powerful method for updating the source code. Even though the code that does the actual update has been changed in the MCNPX configuration, the line identifiers in the MCNPX code remain the same as they were for version 4C2 of MCNP except for lines that were modified to create the MCNPX code. This similarity enables us to take the patch file for MCNP 4C2, which is used to create the source code for the Visual Editor from the MCNP, and modify this patch file to create the Visual Editor for MCNPX source code. There are 18,830 lines in MCNP 4C2 patch file used to create the Visual Editor for MCNP. To adapt this patch file for use with MCNPX, it is estimated that about 10% of these lines were modified. A significant portion of the work for this task was converting the MCNP 4C2 patch file to work with MCNPX. The MCNPX patch file was then used to create the corresponding Fortran source code for the Visual Editor for MCNPX. A first draft of this conversion of the patch file was completed and the corresponding *.F Fortran source files were generated for the Visual Editor for MCNPX. This FORTRAN patch was then linked with the Visual Editor C++ code to create an initial version of the Visual Editor for MCNPX. This initial version was successfully created and a plot of a simple geometry was created. Page 7

Figure 7-1 shows a plot of the geometry created using this initial version. The ability to create a plot of the geometry within MCNPX was a major milestone in the completion of this grant and provides the basis from which the remaining Visual Editor features can be tested and implemented. Figure 7-1. Plot of an MCNP Geometry Displayed in the MCNPX Visual Editor 7.1.3 Task 3: Test/Debug the FORTRAN Patch Each of the different capabilities of the Visual Editor were tested to determine the modifications needed to get the different Visual Editor features working for MCNPX. The features that were tested included surface display and creation; cell display and creation; material display and creation; the display and creation of importances; and the display and creation of transformations. Advanced capabilities that were tested included sdef source plotting; particle track plotting; cross section plotting; tally plotting; 3D ray tracing; 3D dynamic display; and CAD to MCNP conversion. A number of modifications were required to get these capabilities working in the MCNPX version of the Visual Editor. These features were tested for simple test problems and then tested more extensively using the problems from the MCNP Visual Editor class. Most of these problems from the class worked with the exception of 3D ray tracing for an array, Page 8

radiographic ray tracing, and transparent ray tracing, which will need to be looked at further. All of the tests were for files that were originally created to work in MCNP5. 7.1.4 Task 4: Modify the User Interface for MCNPX Specific Needs The C++ code used to create the graphical user interface for MCNPX is very similar to the code used for MCNP5. This has the significant advantage that the C++ source code developed for the MCNP5 graphical user interface can be used directly with the MCNPX computer code. As improvements are made to the MCNPX version of the C++ code, the MCNP5 code will benefit. Similarly, as improvements are made to the MCNP5 C++ code, the MCNPX code will benefit. As MCNPX specific needs are identified and met, the C++ code used to generate the graphical user interface for MCNPX diverges from the MCNP5 version. This has been accommodated by adding a define directive to the Visual C++ project that can be changed to indicate if the code is being compiled for MCNP5 or MCNPX. This allows for the same C++ source code to still be used for either MCNP5 or MCNPX. Page 9

Figure 7-2 shows a plot of a geometry in the MCNPX Visual Editor that was created using macrobody surfaces. All of the macrobody surfaces were generated with the surface wizard. Cells were created from the macrobody surfaces using the cell creation panel. Materials were imported from the material library and assigned to the different cells to generate the geometry. In Figure 7-2, the input file is shown on the upper right and the surface wizard panel for creating a macrobody surface of a truncated cone is shown in the lower right. Figure 7-2. Plot of an MCNPX Geometry Using Macrobody Surfaces Created with the Surface Wizard Page 10

Figure 7-3 shows a plot of a geometry created in the MCNPX version of the Visual Editor. Importances were added to the input file using the Visual Editor s importance creation capability. In addition, materials were transferred from the material library and included in this input file. The materials were then assigned to the different cells to create this geometry. In Figure 7-3, the MCNP input file that was created is displayed in the input window on the right side of the figure. Figure 7-3. Plot of an MCNPX Geometry Created in the MCNPX Visual Editor Page 11

Figure 7-4 shows a plot of a complex reactor model created for MCNP displayed in the MCNPX Visual Editor. On the right side, the universe level has been set to 1 to hide the pin detail in the outer regions to allow the plot to be generated faster. In addition, in the right plot the universe number is displayed in each of the lattice locations. The left plot shows a detailed close-up view of the lattice pins in the outer rows. Figure 7-4. Plot of a Complex Lattice Geometry Displayed in the MCNPX Visual Editor Page 12

Figure 7-5 shows different panels demonstrating the materials capability in the MCNPX Visual Editor. In the upper right is the list of materials for the current input file. Material three, containing stainless steel, is selected. Its composition is shown near the bottom of the panel. In the bottom right is the isotope panel that will allow the user to select isotopes when creating a material. The isotopes are read from the xsdir and then displayed for the user to select as a function of isotope and particle type. In the bottom right is the material library panel that contains a number of common materials that can be selected and then added to the input file. Figure 7-5. Materials in the MCNPX Visual Editor Page 13

Figure 7-6 shows the importance panel in the MCNPX Visual Editor. The importances can be selected with the mouse in the plot window, either with a click of the mouse to select a single cell or a drag to select a range of cells. The importances can then be set to a specific value or multiplied by a scale value or set in a geometrically increasing sequence. Figure 7-6. Importances in the MCNPX Visual Editor Page 14

Figure 7-7 shows the transformation panel in the Visual Editor along with a portion of the input window showing the transformations as they appear in the input file. Transformations can be created and then used to transform surfaces and cells. Figure 7-7. Transformations in the MCNPX Visual Editor Page 15

Figure 7-8 shows the SDEF source plotting capability as implemented in the MCNPX Visual Editor. The particles in Figure 7-8 are photons. Additional research still needs to be performed to look at displaying particles supported in MCNPX that are not supported in MCNP. The points are projected onto the plot plane at a distance specified by the user. In this case the default of 100 centimeters (cm) is used so that particles within 100 cm of the plot plane are projected on the plot plane; consequently, particles are shown in the plot plane for geometric source regions that are outside the plot plane. The piping in this figure is an example of this. The color represents the energy of the source particle with red being high energy and blue being low energy. The user has the option of setting the particle color to represent the weight of the particle. The user also has the option of changing the size of the source point; in this plot the smallest source point size is used. Figure 7-8. SDEF Source Plotting in the MCNPX Visual Editor Page 16

Figure 7-9 shows collision point plotting in the MCNPX Visual Editor. The particles shown in Figure 7-9 are photons. Additional research still needs to be performed to look at displaying particles supported in MCNPX that are not supported in MCNP. This figure shows a cask with a streaming path out the top. Particles are biased toward the streaming path. The source is also biased axially. The color of the particle represents the particle weight, with blue representing the lowest weight. From the figure it can be observed that the lower weight particles originate near the top of the pins, because this is the region of highest biasing. In addition, the particles are biased toward the streaming path using importances, resulting in additional lower particle weight, as indicated by the dark blue color. Figure 7-9. Collision Point Plotting in the MCNPX Visual Editor Page 17

Figure 7-10 shows a 3D ray traced plot of a cask with a section cut out of it as generated in the MCNPX version of the Visual Editor. The left plot shows an overall view of the cask. This is the same cask for which collision points were generated in Figure 7-9. The air streaming path can clearly be observed in both the left and right plots. The right plot shows a close up view of the pins and part of the top of the cask. Figure 7-10. 3D View of a CASK Generated by the MCNPX Visual Editor Page 18

Figure 7-11 shows a 3D view of a small cask that is interactive. The user can dynamically rotate the object and change the transparency of different cells. The user can rotate the 3D image and move around the object as desired, using the rotate button or the yaw, pitch, and roll buttons. Figure 7-11. Dynamic 3D View of a CASK Generated by the MCNPX Visual Editor Page 19

Figure 7-12 shows the CAD to MCNP conversion capability in the MCNPX version of the Visual Editor. The CAD to MCNP conversion work was funded under an SBIR grant from DOE and implemented in MCNP5. Complete details on this capability can be found on the Visual Editor web site (http://www.mcnpvised.com/cad/cad.html), including the final report that was submitted to DOE. Because the C++ code for the graphical interface for MCNP5 is the same as the C++ code for MCNPX it can be directly applied to creating MCNPX geometries with only minor changes. Figure 7-12 shows a cube containing 1,000 spheres that was created in CAD and then imported into the Visual Editor and converted into an MCNP geometry. A box surrounds each set of 25 spheres to prevent the creation of MCNP cells that are too complex. In the 3D view on the right the original CAD geometry is displayed. Some of the cells have been made transparent to allow the spheres to be seen. The plot on the left shows a 2D cross section of the MCNP geometry that was created after converting the CAD geometry to an MCNP format. Figure 7-12. CAD to MCNPX Conversion Performed by the MCNPX Visual Editor Page 20

Figure 7-13 shows a cross section plot generated in the MCNPX version of the Visual Editor. The cross section plotting capability is the same as the cross section plotting capability provided by the X-windows plotter that is part of the MCNPX executable. The user must first read in the MCNPX input file that contains the cross section to plot. Once the file is read in, different material or isotopic cross sections can be plotted for user specified reactions. Figure 7-13. Cross Section Plot Generated by the MCNPX Visual Editor Page 21

Figure 7-14 shows a tally plot generated in the MCNPX version of the Visual Editor. The tally plotting capability is the same as the tally plotting capability provided by the X-windows plotter that is part of the MCNPX executable. The user must first read in a runpte or mctal file and then choose which parameters to plot. In Figure 7-14, the value of the dose rate as a function of tally segment is plotted for two different tallies. Figure 7-14. Tally Plot Generated by the MCNPX Visual Editor Page 22

7.1.5 Task 5: Investigate the Graphical Display of MCNPX Data To test the MCNPX Visual Editor for MCNPX data, the test input files that are sent out with the distribution of the beta code were read into the Visual Editor to see what problems were encountered. Table 7-1 shows a list of these 65 test problems and the results. Four different tests were made on each input file. The first test was to open the file in the Visual Editor. The Visual Editor will read the input file using the MCNPX Fortran code and then the information for the input is passed to the Visual Editor C++ code. If the Fortran has a problem reading the input or passing the information, this test will fail. Most of the test problems pass this test. The second test is to use the input window to save and then update the input file. This will show if the information passed from the Fortran to the Visual Editor is correct. If the information is wrong in the Visual Editor, when it is read in again, the code will have a fatal error or die. Table 7-1 shows there are a number of problems in this area that need to be resolved. The third test is to try to run the problem within the Visual Editor. This will show if the Visual Editor can run MCNPX from the graphical user interface (GUI). This must work or particle track plotting and 3D ray tracing will not work, because both of these features involve running the MCNPX code from the GUI. The fourth test is to run the Visual Editor from the command line. The Visual Editor can be run from the command line to test running the problem using the same script used to test the MCNPX code. This should work for most problems. As shown by the results of the test problems in Table 7-1, the MCNPX version of the Visual Editor still needs work to become fully compatible with the MCNPX specific format. It is recommended that funding be continued through Phase 2 to resolve these problems that go beyond the scope of Phase 1. Page 23

Table 7-1. Test Problems Included with the MCNPX Source Code (Input files from:..\mcnpx26a\v26a\src\test\test_sources) Has Fatal Error Test 1 Opens in Vised Test 2 Save- Update in Vised Test 3 Runs in Vised GUI Test 4 Runs in Vised Command Line Case Name Comments 1 inp01 OK DIES YES YES Dies in levset on S-U 1 2 inp02 x OK DIES NO YES Dies in levset on S-U 3 inp03 OK OK YES YES 4 inp04 OK DIES YES YES Dies in levset on S-U 5 inp05 OK DIES YES YES Dies in levset on S-U 6 inp06 OK DIES NO YES Dies in levset on S-U 7 inp07 OK DIES YES YES Dies in levset on S-U 8 inp08 DIES NA NO YES FE 2 /Dies 9 inp09 OK DIES NO YES Dies in levset on S-U 10 inp10 OK DIES NO YES Dies in levset on S-U 11 inp11 x OK DIES NO YES Memory error on S-U 12 inp12 OK DIES YES YES Format error on S-U 13 inp13 OK DIES YES YES Dies in levset on S-U 14 inp14 OK DIES NO YES Has GE 3 15 inp15 OK DIES YES YES Dies in levset on S-U 16 inp16 OK FE NO YES Trans FE on S-U 17 inp17 OK GE NO YES GE on S-U 18 inp18 OK DIES NO YES Dies in levset on S-U 19 inp19 OK OK NO YES 10 inp20 x OK DIES NO YES Dies in levset on S-U 21 inp21 OK DIES YES YES Dies in levset on S-U 22 inp22 OK DIES NO YES Dies in levset on S-U 23 inp23 x OK DIES YES YES Dies in levset on S-U 24 inp24 OK DIES YES YES Dies in levset on S-U 25 inp25 NA NA YES Continue run 26 inp26 NA NA YES Continue run 27 inp27 OK DIES NO YES Dies in levset on S-U 28 inp28 OK OK OK YES 29 inp29 x DIES NA NO YES Dies when loading 30 inp30 OK DIES YES YES Dies in levset on S-U 31 inp31 OK DIES DIES YES Dies in levset on S-U 32 inp32 OK DIES YES YES Dies in levset on S-U 33 inp33 GE GE YES YES 34 inp34 OK OK NO YES 35 inp35 OK DIES YES YES Dies in levset on S-U 36 inp36 OK DIES YES YES Dies in levset on S-U 37 inp37 OK DIES YES YES Dies in levset on S-U 38 inp38 OK DIES YES YES Dies in levset on S-U 39 inp39 OK DIES YES YES Unexpected EOF 40 inp40 OK DIES YES YES Dies in levset on S-U 41 inp41 OK OK YES YES 42 inp42 OK DIES YES YES Dies in levset on S-U Page 24

43 inp102 OK DIES NO YES Dies in levset on S-U 44 inp103 OK DIES NO YES Dies in levset on S-U 45 inp104 OK DIES NO YES Dies in levset on S-U 46 inp105 OK DIES NO YES Dies in levset on S-U 47 inp106 OK DIES NO YES Dies in levset on S-U 48 inp107 OK DIES YES YES Dies in levset on S-U 49 inp108 OK DIES YES YES Dies in levset on S-U 50 inp109 OK DIES DIES YES Dies in levset on S-U 51 inp110 OK DIES YES YES Dies in levset on S-U 52 inp117 OK DIES NO YES Dies in levset on S-U 53 inp118 OK DIES DIES YES Dies in levset on S-U 54 inp119 OK DIES DIES DIES Dies in levset on S-U 55 inp120 OK OK OK YES 56 mes01 OK DIES DIES DIES Unexpected EOF 57 mes02 OK DIES DIES YES Unexpected EOF 58 mes03 OK DIES OK YES Unexpected EOF 59 mes04 OK DIES DIES DIES Unexpected EOF 60 htp111 OK DIES DIES YES Dies in levset on S-U 61 htp112 OK DIES DIES YES Dies in levset on S-U 62 htp113 OK DIES OK YES Dies in levset on S-U 63 htp114 OK DIES OK YES Dies in levset on S-U 64 htp115 OK DIES DIES YES Dies in levset on S-U 65 htp116 OK DIES DIES YES Dies in levset on S-U 1 S-U Save-Update 2 FE fatal error 3 GE geometry error Page 25

The Visual Editor was modified to accommodate the many different particle types available in MCNPX. A new mode panel has been added to the MCNPX Visual Editor that will display the mode of an input file that is read in, or, alternatively, it can be used by the user to change or set the mode. Figure 7-15 shows this new mode panel after reading in the mes03 input file that has a mode card with almost all of the particle types specified. Figure 7-15. Mode Card Panel for the MCNPX Visual Editor Because of the many new particle types that need to be addressed, the C++ data structures used to keep track of the MCNPX cell dependent data cards had to be significantly modified to allow for the dynamic expansion of the particle dependent data depending of the mode of the input file. Page 26

7.1.6 Task 6: Documentation The MCNP Visual Editor manual was modified to present the current status and capabilities of the MCNPX Visual Editor. This manual, along with the beta code, can be sent to interested users for understanding how the current code works and how to use the MCNPX Visual Editor for their own applications. 7.1.7 Current Problems Some problems with 3D ray tracing have been discovered that need to be solved. However, other than these problems most of the functionality of the MCNP5 Visual Editor is now available in the MCNPX Visual Editor. Additional work still needs to be performed to provide support for MCNPX data as demonstrated by the test problems shown in Table 7-1. Possible areas of future improvement and research are discussed in Section 7.2. It is recommended that this research be continued through Phase 2 to resolve these problems and bring this code into production and distribution to the users. 7.2 Future Technical Activities An initial version of the MCNPX Visual Editor has now been created that meets the objective of Phase 1, but there is additional work that needs to be performed to provide support for data available in MCNPX that does not exist in MCNP5. Table 7-2 contains a list of items that should be considered to improve the MCNPX Visual Editor in Phase 2. Table 7-2. Items that Need to be Considered in Future Upgrades of the MCNPX Visual Editor (to be addressed in Phase 2) Item Number Description 1 Update the MCNPX Visual Editor to that latest beta code version (currently 2.6.b). 2 Update importance panel for multiple particles. 3 Finish updating and testing the cell data cards for multiple particles. 4 Update particle display for multiple particles. Show different particle types by color. 5 Review, update, and enhance the material library. 6 Add source creation capability. 7 Intercept bad trouble messages in MCNPX and send appropriate message to the Visual Editor so it does not die. 8 Add support for the mix and match capability. 9 Implement the MCNPX radiograph tally. 10 Implement mesh tallies. 11 Add support for the weight window mesh capability. 12 Enable the setting colors in 2D and 3D. Page 27

13 Improve the selection of cells for 3D display. 14 Enable the 3D display of universes and lattices in dynamic mode. 15 Add visual aids to the transformation panel to show the 3D transformation. 16 Add tally creation and visualization aids. 17 Allow the output file to be visualized in the Visual Editor. 8.0 Potential Customer and Commercialization Activities 8.1 Recent NASA Potential Customer Activities None. 8.2 Recent NON-NASA Potential Customer Activities None. 8.3 Other Recent Commercialization Activities VEC rented a booth at an American Nuclear Society meeting in Carlsbad, New Mexico, in April 2006. This provided an opportunity to discuss this work with both the MCNP5 and MCNPX code developers at LANL. In addition, Randy Schwarz attended both MCNPX and MCNP5 workshops that were offered as part of this meeting to better understand current methods for performing MCNP geometry visualization. A beta version of the MCNPX Visual Editor was sent to LANL to be made available for students who attended the June MCNPX training session at LANL. In addition, the work outlined in this report is also advertised on the Visual Editor website: http://www.mcnpvised.com/mcnpx/mcnpx.html After completion of Phase 1, the beta code will be made available to interested users who can verify that they are current RSICC users of the code. 8.4 Future Potential Customer and Commercialization Activities VEC will be communicating with the code developers at LANL to determine their needs and to work with them on a process for distributing the MCNPX Visual Editor to interested users. Page 28