Search
Page 70 of 107. Showing 1,065 results (0.01 seconds)
Event contexts
The context or the "label" of the event is a specification to narrow the scope of the event. When someone specifies 'job' they don't normally mean all jobs, so a context is required to determine which job they are describing. A context can be specified in…Generating agendas
The qb::genframes() function returns a reference to a hash array, keyed to individual frames. This array is called an "agenda." Qb::genframes() contains a parser that can handle a number of ways of specifying lists of frames. Example Single frame 1 Frame…Creating a new SimpleCmd
that returns an array of SimpleCmd instances. For testing purposes, add an if __name__ == '__main__': so the submission dialog can be launched directly by running Python _script.py. Here…Process group labels
Process group labels exist to provide the developer with an abstract method of determining job relationships independent of the job name or job ID relative to the process group ID. In order to support this, the jobs must all be submitted under the same pr…Job ids
Explicit job ids are also available to be used as event specifiers in the event one just wants to reference the job by its ID. done-job-19234…Extra fields
The extra in the event specification refers to the type of event. Each type of event may require additional information. In the case of the job, it requires nothing more. However in the case of the subjob it requires the subjob's ID number. Example When t…Job type configuration
The purpose of the job.conf is to describe to Qube the vital statistics about the Job Type, and where to find the auxiliary files for both submission and execution. The format of the job.conf file is: [topic]key = value Example job.conf file.##[d…Submission front end
For the submission front-end, see the SimpleSubmit framework documentation. It is almost identical to the SimpleCmd framework except it calls the jobtype backend rather than a commandline. See the QubeGUI's "Help->SimpleCmd Developer Guide" for the docume…Execution back end
When designing the Job Type, the developer must decide on both the method to execute the job, and the name of the file to bind. Example Specifying a file binding is simple. You must include both the 'type' of binding, and the name of the file. execute_bin…Windows
worker_template_path="C:/Program Files/qube/types;//server/share/site/qube\types"…