Purpose
This document describes the policy and procedures for using MCNP software on HiPerGator.
HiPerGator is a shared system, with many users working on open and sensitive data, as classified by UF Guidelines.
The MCNP code is distributed to its worldwide user community by the Radiation Safety Information Computational Center (RSICC), which is based at the Oak Ridge National Laboratory in Oak Ridge, Tennessee.
Policy
Software obtained from RSICC is export controlled under the jurisdiction of the U.S. Department of Energy, 10 CFR 810, or the U.S. Department of Commerce, 15 CFR 730-744. Additionally, RSICC distributes this software under guidance issued by the U.S. Department of Energy’s Office of Nonproliferation and Arms Control. The distribution and use of RSICC software is restricted and controlled under these regulations and guidelines. Individuals that request the software must be cleared through both an export control and a nonproliferation review process prior to the individual being granted a license to receive software for a specific end use.
Procedure
When a request is made to use MCNP software on HiPerGator, the PI or class instructor will work with UFIT Research Computing support staff to complete the following tasks:
Registration
A request to use MCNP software is registered by entering a request in UFIT Research Computing's support system. This will create a trackable service request.
What is Needed
To set up a MCNP group, UFIT Research Computing needs the following:
- PI or class information (with instructor listed)
- Specific users to add to the group (must include last name, first name and GatorLink username)
- Each group member’s authorization form from RSICC to use the softwareEach group member’s acceptance of the HiPerGator Account Request Acceptable Use Policy
- Amount of HiPerGator resources requested
When the procedure is not followed, the class will not be given access to the software or any resources.
Special Precautions
Single-user license agreement is code and version specific. The Licensee must be licensed for the specific version to which they are granted access. For example, an individual with a license only for MCNP5 should not be permitted access to MCNP6.1. Additionally, some individuals are only licensed for the executable versions of the code(s), and the system administrator(s) must ensure that such individuals do not have access to the source code.