def submit( self , data_file):
"""
Will submit a new simulation of case given by @data_file.
The return value is a Job instance from the
ert.job_queue.queue.job module which can be used to query the
status of the job while it is running.
"""
(path_base , ext) = os.path.splitext( data_file )
(run_path , base) = os.path.split( path_base )
argv = [ self.ecl_version , path_base , "%s" % ecl_util.get_num_cpu( data_file )]
return JobQueue.submit( self , self.ecl_cmd , run_path , base , argv)
def submit( self , data_file):
"""
Will submit a new simulation of case given by @data_file.
The return value is a Job instance from the
ert.job_queue.queue.job module which can be used to query the
status of the job while it is running.
"""
(path_base , ext) = os.path.splitext( data_file )
(run_path , base) = os.path.split( path_base )
argv = [ self.ecl_version , path_base , "%s" % ecl_util.get_num_cpu( data_file )]
return JobQueue.submit( self , self.ecl_cmd , run_path , base , argv)
def __init__(self ,
driver = None ,
driver_type = None,
driver_options = None,
ecl_version = None,
ecl_cmd = None,
max_running = 0,
size = 0):
"""
Create a new queue instance to manage ECLIPSE simulations.
The constructor will create a new EclQueue instance which can
be used to manage ECLIPSE simulations. All the ECLIPSE
simulations managed by this queue instance will be 'of the
same type', i.e. they will run the same ECLIPSE version using
the same command to run ECLIPSE.
The queue starts running (i.e. managing jobs) as soon as it is
created. Subsequently the user must add jobs to run using the
submit() method, or alternatively the submit() method of an
EclCase instance.
The queue will run in a separate thread, and there is nothing
preventing your script from finishing (i.e. exit) even though
the queue thread is still running; in that case the jobs which
are still waiting in the queue will not be started[1]. To
protect against this premature exit you must use on of the
methods:
- queue.block_waiting()
- queue.block()
- while queue.running:
.....
All simulations which have been started by the queue instance
will continue running even if the queue itself goes out of
scope and the script exits.
There are many arguments to the constructor, all of them are
optional with sensible default values. There are essentially
three groups of arguments:
Driver related arguments
------------------------
driver: This should be an instance of Driver (or one of the
descendants LSFDriver, LocalDriver, or ...) from the
ert.job_queue.driver module. If the driver is None the
queue will instanstiate a driver itself.
driver_type: If the driver is None the queue needs to
instantiate a private driver. It will then instantiate a
driver of the type given by driver_type.
driver_options: If the queue needs to instantiate a private
driver it will pass the options given by the
driver_options argument to the driver constructor.
There is some dependance between the driver related arguments;
if a @driver argument is passed the @driver_type and
@driver_options arguments are not considered.
ECLIPSE related arguments
-------------------------
ecl_version: The ECLIPSE version used when simulating. This
should be a string of the type "2009.1".
ecl_cmd: The path to the executable used to invoke
ECLIPSE. The executable will be invoked with commandline
arguments:
version data_file num_cpu
And this executable is responsible for then starting the
real ECLIPSE binary.
Other arguments
---------------
max_running: The maximum number of jobs the queue can run
concurrently. The default value max_running=0 means that
the queue can start an unlimited number of jobs; in the
case of e.g. LSF the default value can be sensible,
otherwise you should probably set a value.
size: This is the total number of simulations we want to run
with the queue; this is further documented in the
ert.job_queue.queue.JobQueue class.
Use example
-----------
import ert.ecl.ecl as ecl
import ert.job_queue.driver as driver
queue = ecl.EclQueue( driver_type = driver.LOCAL , max_running = 4 , size = 100)
data_file_fmt = "/path/to/ECLIPSE/sim%d/ECL.DATA"
for i in range(100):
queue.submit( data_file_fmt % i )
queue.block()
[1]: It should be possible with a fork based solution to let
the queue stay alive and continue managing jobs even
after the main thread has exited - not yet :-(
"""
if ecl_cmd is None:
ecl_cmd = ecl_default.default.ecl_cmd
if driver_type is None:
driver_type = ecl_default.default.driver_type
if ecl_version is None:
ecl_version = ecl_default.default.ecl_version
self.ecl_version = ecl_version
self.ecl_cmd = ecl_cmd
if driver is None:
if driver_options is None:
driver_options = ecl_default.default.driver_options[ driver_type ]
driver = queue_driver.Driver( driver_type , max_running = max_running , options = driver_options )
JobQueue.__init__( self , driver , size = size)
def __init__(self,
driver=None,
driver_type=None,
driver_options=None,
ecl_version=None,
ecl_cmd=None,
max_running=0,
size=0):
"""
Create a new queue instance to manage ECLIPSE simulations.
The constructor will create a new EclQueue instance which can
be used to manage ECLIPSE simulations. All the ECLIPSE
simulations managed by this queue instance will be 'of the
same type', i.e. they will run the same ECLIPSE version using
the same command to run ECLIPSE.
The queue starts running (i.e. managing jobs) as soon as it is
created. Subsequently the user must add jobs to run using the
submit() method, or alternatively the submit() method of an
EclCase instance.
The queue will run in a separate thread, and there is nothing
preventing your script from finishing (i.e. exit) even though
the queue thread is still running; in that case the jobs which
are still waiting in the queue will not be started[1]. To
protect against this premature exit you must use on of the
methods:
- queue.block_waiting()
- queue.block()
- while queue.running:
.....
All simulations which have been started by the queue instance
will continue running even if the queue itself goes out of
scope and the script exits.
There are many arguments to the constructor, all of them are
optional with sensible default values. There are essentially
three groups of arguments:
Driver related arguments
------------------------
driver: This should be an instance of Driver (or one of the
descendants LSFDriver, LocalDriver, or ...) from the
ert.job_queue.driver module. If the driver is None the
queue will instanstiate a driver itself.
driver_type: If the driver is None the queue needs to
instantiate a private driver. It will then instantiate a
driver of the type given by driver_type.
driver_options: If the queue needs to instantiate a private
driver it will pass the options given by the
driver_options argument to the driver constructor.
There is some dependance between the driver related arguments;
if a @driver argument is passed the @driver_type and
@driver_options arguments are not considered.
ECLIPSE related arguments
-------------------------
ecl_version: The ECLIPSE version used when simulating. This
should be a string of the type "2009.1".
ecl_cmd: The path to the executable used to invoke
ECLIPSE. The executable will be invoked with commandline
arguments:
version data_file num_cpu
And this executable is responsible for then starting the
real ECLIPSE binary.
Other arguments
---------------
max_running: The maximum number of jobs the queue can run
concurrently. The default value max_running=0 means that
the queue can start an unlimited number of jobs; in the
case of e.g. LSF the default value can be sensible,
otherwise you should probably set a value.
size: This is the total number of simulations we want to run
with the queue; this is further documented in the
ert.job_queue.queue.JobQueue class.
Use example
-----------
import ert.ecl.ecl as ecl
import ert.job_queue.driver as driver
queue = ecl.EclQueue( driver_type = driver.LOCAL , max_running = 4 , size = 100)
data_file_fmt = "/path/to/ECLIPSE/sim%d/ECL.DATA"
for i in range(100):
queue.submit( data_file_fmt % i )
queue.block()
[1]: It should be possible with a fork based solution to let
the queue stay alive and continue managing jobs even
after the main thread has exited - not yet :-(
"""
if ecl_cmd is None:
ecl_cmd = ecl_default.default.ecl_cmd
if driver_type is None:
driver_type = ecl_default.default.driver_type
if ecl_version is None:
ecl_version = ecl_default.default.ecl_version
self.ecl_version = ecl_version
self.ecl_cmd = ecl_cmd
if driver is None:
if driver_options is None:
driver_options = ecl_default.default.driver_options[
driver_type]
driver = queue_driver.Driver(driver_type,
max_running=max_running,
options=driver_options)
JobQueue.__init__(self, driver, size=size)