Registration

Proposals
Interims
Final Reports

Dates

Kickoff
Evaluations
Expo
STI
Wiki

School Map
Sponsors

Mail

Challenge
Technical Guide


Past Participant Survey

GUTS

Guidelines for Selecting a Project

When choosing a project for the Challenge, one of the most important considerations is that it be something that can be done in the short time of the program. Projects are judged on overall quality and by the progress made by the team during the competition year. It is important to submit a project that is complete. It is also important to choose a project in which you have a genuine interest.

When examining projects, the judges consider the scientific content; the effectiveness of the computational approach; the creativity, innovation, and initiative shown in developing and carrying out the project; and the clarity of the presentation of the work.

For more information about guidelines for the projects, please see

http://www.challenge.nm.org/About/guidelines.shtml

See also the list of Areas of Science Appropriate for Challenge Projects.

http://www.challenge.nm.org/About/areas.shtml

Project Requirements and Restrictions

The following rules apply to all projects for the Challenge:

• Your project problem MUST represent a real science or mathematics problem from the approved list of appropriate science areas for the Challenge. To be competitive, you must clearly demonstrate that the solution requires the use of a high-performance computering resources.

• The final version of your computer application software must be written in FORTRAN, C, C++, or Java programming language. If you wish to use another programming language, it must be approved, in advance, by consult@challenge.nm.org.

• Your project cannot involve live vertebrate animal experimentation.

• If you choose the Category B (noncompetitive) track this year, you can work on the same project again next year. You must submit a final report each year.

• If you want to use human subjects in your Challenge project, you must get approval beforehand from the Challenge Executive Committee.