Release will require documentation on the performance, optimisation and resource use of the model to support users when applying for compute time in competitive allocation schemes such as NCMAS.
In the Computational Details part of your application, you should focus on the assessment criteria of 3) Computational Feasibility and provide details on:
Scalability of your code(s) on each nominated facility:
Use scalability tables and/or plots.
For software with multi-node capability, applicants should present data relative to single node performance, not single core performance
Poor scaling may impact negatively on the merit of theapplication
Compute job resources at each nominated facility:
Provide details on typical job configurations for your workflows, including
expected wall times,
number of nodes/cores,
data dependencies,
expected throughput, and so on.
Provide a summary of the resource requirements in the form of an “SUbudget” for each request. This budget should list:
major steps in the project workflow(s),
the key methods/algorithms required, and
the SU requirements for each step.
Also describe other dependencies such as software and storage. • Storage at each nominated facility:
Describe data storage requirements and data life cycle for your project.
Algorithms and Workflows:
Describe parallelism in your application(s) and how this relates to mathematical algorithms used. Describe data movement and lifecycle.
Release will require documentation on the performance, optimisation and resource use of the model to support users when applying for compute time in competitive allocation schemes such as NCMAS.
From the NCMAS documentation:
In the Computational Details part of your application, you should focus on the assessment criteria of 3) Computational Feasibility and provide details on: