Opened 8 years ago

Closed 8 years ago

#940 closed help (fixed)

Submitting HadGEM2 from the command line?

Reported by: peterh Owned by: simon
Component: UMUI Keywords: SUBMIT
Cc: Platform: HECToR
UM Version: 6.6.3


I currently setting up am ensemble of perturbed parameter (in TRIFFID) HadGEM2 atmosphere-only jobs. I therefore need to submit these runs from the command line, rather than from within the UMUI. Is there a way to do this at the moment, and if not, how complicated would it be to set up?

Change History (5)

comment:1 Changed 8 years ago by grenville

Hi Peter

Our ensemble expert is in Germany at the moment - he'll be back next week and will contact you then.


comment:2 Changed 8 years ago by simon

  • Owner changed from um_support to simon
  • Platform set to <select platform>
  • Status changed from new to accepted


It's relatively simple to submit from the command line. Can you give me more details
of the perturbations and a runid of an example job and I can then advise on the best
way to proceed.

Sorry for the delay is replying, I've hardly been in the office in last month
for various reasons.


comment:3 Changed 8 years ago by peterh

Thanks for getting back to me. I've managed to get this working now. Just to check though, after copying the contents of umui_jobs/$expt to a folder on HECTOR with a date- and time- specific name, do I just need to run SUBMIT and then qsub the umuisubmit_run script?

The perturbations I've made are to the code, 8 parameters specific to TRIFFID are read in from the namelist in CNTLATM rather than as defined in an include file within the model code. An example job is xhrcd.

comment:4 Changed 8 years ago by simon

Hi Peter,

Glad to hear you've solved this by yourself. Your solution is exactly how I would do it. If you need any more advice, let me know.


comment:5 Changed 8 years ago by ros

  • Platform changed from <select platform> to HECToR
  • Resolution set to fixed
  • Status changed from accepted to closed
  • UM Version changed from <select version> to 6.6.3
Note: See TracTickets for help on using tickets.