Feature requests

Suggested features for future versions of payu. These can also be submitted as issues in the tracker (assuming they are actually solvable!)

• Build automation

  This works to some extent but needs to be more user-friendly (e.g. don't look for config.yaml, ignore contents of config.yaml during build, etc..)

• Runscript generation

  Often NCI will ask for our "runscript" which obviously doesn't exist with Payu. I think we need some way to create a "run.sh" for an existing "work" directory, that just contains all the #PBS headers, module loads, and the mpirun call to the binary. I think this would help for people submitting tickets, and other work.

• Receipt generation

  The PBS log at the end of submission has a lot of useful info, but it's awkwardly only created after payu (and the model) finishes! But most of this info is just generated from "qstat -f". We should consolidate all the useful info about a job (commands calls, walltime, memused, etc etc) and print it into our own file, so that we don't need the PBS logs.

• Log runs

  ... then send those logs to some kind of database like Ganglia, like the one Scott has set up for the UM users.

• Calendar generalisation

  Calendar is great! We need to expand it to the other models

• Communicator drivers

  payu is basically broken under Intel MPI. I think we need a "communicator" drivers; one for openMPI and one for Intel MPI (and maybe one for Fujitsu MPI, etc..)

• Scheduler drivers

  Same for pbs. NCI is dumping PBSPro for Slurm on the next machine, might as well abstract these PBS calls. (and Fujitsu's pjsub on FX10)

• Platform drivers

  Much of what we do is raijin-specific, especially architecture. I think this info could be read from a "platform" driver.