Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

seeking to run an ensemble in one job

M

m_mineter@ed_ac_uk

Member
We are seeking to  run a 20 member  ensemble (B_20TR_CAM5_CN) with different starting points.  Each case only require 72 cores, and would more readily be scheduled as say one 1440 core job, rather than 20 of 72 core jobs. I'm exploring how to restructure  the ${CASE}.run  and associated scripts to achieve this in an "ensemble.run" script,  so one job can a) initiate and apirun each case in the ensemble; b)  wait for all cases to run to completion; c) do postrun archiving etc; d) cause resubmission. Two thought arise:  Has anyone already taken this approach?  Has anyone already decided this is impractical?!Thanks! 
 
You must log in or register to reply here.
Top