 |
|
|
||||
|
||||||
|
QUESTION: How do I report a problem with MELCOR software? ANSWER: Click the "Report a Bug (Bugzilla)" tab on the top navigation bar, login to Bugzilla, and enter a bug number or a search term. You must have a Bugzilla account to report a bug/problem with MELCOR. QUESTION: Can I get a copy of the source code for MELCOR 1.86? ANSWER: We don't normally distribute source code for MELCOR 1.86. There are exceptions, however, depending on the individual case. When you fill out your request for a Non-Disclosure Agreement, indicate that you require source code and why, and your contact at the NRC will make a determination. QUESTION: What's the difference between MELCOR 1.86 and MELCOR 2.1? ANSWER: MELCOR 1.86 was originally written in FORTRAN 77. The FORTRAN language has evolved significantly since the MELCOR project began, and most platforms now support a FORTRAN 95 compiler. MELCOR 2.x is a port of the original source code to the more modern FORTRAN 95, to improve extensibility and maintainability. Most algorithms were kept intact so that the two codes are currently functionally the same. However, all future code development will be made to the MELCOR 2.x version. Aside from changes to the source code, there are significant input file changes that have to be considered when migrating from one version to the other. We are developing utilities to help you in the conversion process and will provide them to you at your request. QUESTION: Can I get a copy of the source code for MELCOR 2.1? ANSWER: Due to intellectual property issues, we will not be distributing this source code to anyone. If you have a need that requires you to insert your own algorithms into MELCOR, there may be other strategies to consider. Please contact the Code Librarian, John Reynolds, for more details. QUESTION: I have the MELCOR executables, but you didn't include a binary compatible with my system, or the binaries you included don't take advantage of my special or different hardware or operating system. What are my options? ANSWER: Please contact the Code Librarian, John Reynolds, about building an executable specific to your hardware. QUESTION: How do I get the H2C branch? ANSWER: We are not currently distributing the H2C binaries. If this is an issue, please contact the Code Librarian, John Reynolds, for details. QUESTION: What are some things I have to remember when running MELCOR on Linux/UNIX and Windows? ANSWER: The things you need to consider are listed below: Filename Case More details follow, but our recommendation for filename case is this: The input filename should always be uppercase, and should always be referenced as uppercase. This will allow you to avoid any problems relating to case. Windows allows upper- and lowercase filenames, but ignores case when opening a file. In contrast with Windows, other modern systems (including Linux) support both upper- and lowercase and make a distinction between case when opening files. Some older systems that MELCOR has been run on only allow uppercase filenames. To allow files to be opened on legacy systems that don't support lowercase filenames, MELCOR converts the filenames to uppercase by default. To avoid this behavior, put single quotes around the filenames when entered in the MELCOR input file. When single quotes are placed around filenames, case can be wrong and the file will still open on Windows. But when the input file is read on Linux, MELCOR will not be able to find the file unless the filename is exactly the same as listed in the input file (including case). File/Directory Delimiters Windows requires backslashes ("\") as file and directory delimiters, while the rest of the world uses forward slashes ("/"). But with MELCOR, we recommend you avoid backslashes. Your path strings will work on both systems if you use forward slashes. Using backslashes will limit your input files to Windows. Text File Format When transferring input files from Windows to Linux, the dos2unix utility must be run before MELCOR will be able to read them. When transferring them from Linux to Windows, the unix2dos utility must likewise be run. MELCOR plot files (.PTF) are binary, and can be created on one platform and used on another without modification. If you run the above-listed utilities on plot files, they'll be unreadable by the PTFRead utility. But other output and diagnostic files are ASCII and require the same conversion process before they'll be readable on the other system. To avoid guesswork: Use the Dos2Unix/Unix2Dos feature provided in the Melcor Source Assistant application. It will only convert the files that need to be converted, and will leave the binary files intact. Before running any file conversion utility, it's always wise to make a backup. |
||||||
 GALLERY | TECHNICAL REVIEW MEETINGS | TECHNICAL LIBRARY | NEWS |
||||||
| Sandia National Laboratories | U.S. Nuclear Regulatory Commission © Sandia Corporation | Site Contact | Privacy and Security |
||||||
