Go Back

Frequently Asked Questions (FAQ)

1. I just want to calculate a dose from a release. How do I create a new set of inputs?
GENII is not particularly “user friendly” and can initially be difficult to understand. Please look in the \FRAMES\Documentation directory that is installed with the code and review the “Getting Started with GENII” directions. It is necessary to:

  • Define a scenario of exposure and create the appropriate Conceptual Model diagram in FRAMES
  • Individually enter the appropriate values in each module’s User Interface
  • Run each module
  • Decide how best to view the intermediate and final results

2. Why should I install GENII and FRAMES in a c:\FRAMES directory and not in c:\Program Files?
Many parts of GENII are legacy Fortran coding; Fortran is not adept at handling “strings” of text. In particular, there are limits on the length of file names – which includes the complete path of the file name. In addition, the current Fortran implementations scan the file names until they end – or until they come to a space. Thus, a location such as c:\Program Files fails because the codes think that they are looking at a file named c:\Program and get lost.

3. My GENII case seems to work, and then gives an error message partway through. What could be wrong?
In addition to the limitations on spaces in file names, some of the older GENII executable files are limited to the original DOS file name structure of 8 character names with 3 character suffixes. You should always make sure that the names you assign to GENII cases are 8 characters or fewer.

4. My FRAMES home screen does not look like the examples and/or I am unable to select individual icons from the selections on the left-hand side. What’s wrong?
It is likely that you are using a recent operating system, either Windows 8 or Windows 10. Both of these have features that interfere with Visual Basic coding used in the FRAMES and GENII User Interfaces. (Thank you, Microsoft.) We have found that it is necessary to disable the touch screen capabilities of computers running these operating systems while using FRAMES and GENII. The following has been found to resolve the issues:

  • Access the Device Manager: In Windows 10, this is usually found using Control Panel > Administrative Tools > Computer Management > Device manager.
  • Click on Human Interactive Devices
  • Run each module
  • Disable the capabilities for:
    • HID Compliant Touch Screen
    • HID Compliant Pen (if applicable, e.g. for Microsoft Surface computers).

    This will allow the VB TreeView control to function normally. The settings may be returned to normal at the completion of a Frames/GENII session.

    5. I am a non-USA user of the codes; my cases do not save properly and do not run to completion. What can I do??
    Some European computers use a different set of defaults than US computers ("," rather than "." for decimal, words other than "True" and "False" for logicals). Check in the computer’s “Control Panel”/”Region and Language” – set to “English (United States)”. Note that many of the intermediate files are written by Visual Basic, which will adapt to the host language – but that the underlying Fortran routines expect the dot “.” as decimal and “T” or “True” and “F” or “False” (as a minimum) for logical settings. The settings may be returned to normal at the completion of a Frames/GENII session.

    A "Change Settings" routine provided by some Italian users (in Italian!) is included in the FRAMES directory for resolving these issues if needed. (If you can’t figure out the Italian, use the manual method of going to “Control Panel”/”Region and Language” – set to “English (United States)”…).

    6. Why are FRAMES and GENII so slow?
    Some users have reported significant decreases in speed. We have found that Microsoft Endpoint Protection antivirus software scans output files excessively. If you are using this antivirus software, we recommend that you set it to not scan the \FRAMES directory and its subdirectories.

RAMP is a new initiative at the United States Nuclear Regulatory Commission to distribute, maintain, develop and provide training on NRC sponsored Radiation Protection Codes.

The codes in RAMP are RASCAL, RADTRAD, VARSKIN, HABIT, GALE, DandD, PiMAL (a Graphical Users Interface), Radiological Toolbox, XOQDOQ, PAVAN, ARCON96 and MILDOS.

Phase I of RAMP includes codes that are fully sponsored by the US NRC. We hope to incorporate more codes in the future. To suggest a code, please emails us at RAMP@nrc.gov.

The NRC is not charging for codes. RAMP is a voluntary program that charges for membership. Funds from this membership go directly into the research and development of codes.

Yes, Licensees can join RAMP. Contact us at RAMP@nrc.gov.

RAMP member countries have formal International Research Cooperative Agreements with the US NRC. Contact RAMP@nrc.gov to see if your country is one. The NRC is currently developing international research agreements with four countries (i.e., the Republic of Korea, South Africa, Canada, and the United Arab Emirates) and the Taiwan Economic and Cultural Representatives’ office that have expressed interest through our outreach activities. The NRC anticipates the first five agreements to be signed in March, April and May of 2015. Other countries that have shown an interest in joining RAMP are Switzerland, France, India, Finland, and Brazil.

It depends. RAMP has several layers of registration and membership. For information click on the registration link on the homepage of the RAMP website.

See each code’s website for that information.

RAMP Users’ Meetings are held twice a year. The international users’ meeting is held in the Spring and a domestic Users’ meeting held in the Fall. Meetings will include training on various codes and discussion sessions with developers to provide input on future updates of the codes.

RAMP does not give out the source code.

See each codes’ website for that information.