The code descriptions you provide are used by DOE and NERSC to evaluate the type and extent of machine resources that users require.
A code description should be provided for each of your project's most frequently used codes and applications. The information for each code is contained under a tab for that code. Click on the "Add another code" tab to type in your answers for another code.
If you want to remove a code description, click on its x button.
If renewing, please check:
- That you still intend to use all of the codes listed.
- Add new codes as needed.
- Check that the information provided for each code is still accurate.
The following information is requested for each code:
- Code Name: This is the name by which your code is known, e.g. NIMROD, AMBER.
- Code Description: Provide a brief description of the code. What does the code do, what are the science questions it addresses?
- What are the underlying physical models? Explain these briefly. Examples of physical models are electronic structure, fluid flow, MHD, electrostatics, electromagnets, nuclear structure, etc.
- What are the numerical techniques employed? Explain these briefly. Examples of numercal techniques are finite differences, finite elements, DFT, PIC, Monte Carlo, etc.
- What kind of grid/mesh is used? Check as many grid/mesh techniques as apply from the checklist.
- What kind of solver technology is used? Check as many solver techniques as apply from the checklist.
- Machines to be used: On which NERSC machines do you plan to run this code (assuming you get an award)?
- Percent of allocation: What percent of the project's overall allocation do you expect this code to use? Enter a number without the % sign. The numbers for all your codes should add up to 100.
- What is the range of processors or cores? What is the range of processors or cores you plan to use for typical production runs? For PDSF users: how many simultaneous jobs do you plan to run?
- How did you decide on this number? Which of the factors listed influence your choice? Check as many factors as apply from the checklist. You may enter additional factors in the Other box.
- Languages and Parallelization Methods Used: Check as many languages and communications libraries as apply from the checklist. You may enter additional languages or communications libraries in the Other box.
- Libraries Called: Check as many libraries as apply from the checklist. You may enter additional libraries in the Other box.
- Known code Performance Limitations: Check as many limits to performance as apply from the checklist. You may enter comments about limits to performance in the box (next section). You may enter additional (brief) limits to performance in the Other box. You can use IPM (Integrated Performance Monitoring) to help identify the limits to performance of your codes. If you need additional help, contact a consultant at email@example.com.
- Performance Comments: You may comment on the known limits to the code's performance.
- Does the code checkpoint? Select Yes or No.
- Plans for Code Development or Enhancement: Briefly describe your plans.