Search

Search

Help

Page 12 of 1,195. Showing 11,950 results (0.022 seconds)

  1. Job Types

    The Job Type is one of the most powerful aspects of the Qube Remote Control system. With a Job Type, a developer can separate the application functionality into an interface and an underlying implementation. The interface is the "front end" that registers…
    Qube 6.4Oct 19, 2012
  2. Events

    Breaking down the event specification syntax, is generalized into these 4 parts: --- Some simple example callback triggers are: complete-job-self: called when this job is complete done-job-self: called when this job is complete…
    Qube 6.4Sep 27, 2013
  3. qbusers

    qbusers | qbusers | qbusers | Permission Codes | qbusers | qbusers | qbusers modifies the user permissions for an individual user Description Modifies the user permissions for an individual user. To modify the default permissions for all users not explici…
    Qube 6.4Oct 17, 2012
  4. Event names

    The name is the component of the event which details when the event should take place. This is either pre-defined, or user-defined. The possible pre-defined event names for jobs are: complete Job is set to complete done Job is set to complete or killed or…
    Qube 6.4Oct 12, 2012
  5. Simple Job Type front end

    Here is an Perl example of a typical job front end that can handle a job that is based on frames. Example use lib ../api/perl; use qb; my %env = %ENV; my $frames = qb::genframes("1-300"); my $data = { "env" = \%env, "cmdline" = /bin/sleep . int(rand(40) +…
    Qube 6.4Oct 22, 2012
  6. Event types

    The type of the event allows the system to identify the kind of event referred to. The available pre-defined names are relative to the specification of the type. The "types" of events are: job Specifies the entire job subjob Specifies a single subjob work…
    Qube 6.4Sep 27, 2013
  7. Editing existing SimpleCmds

    It is common to edit the default values of the SimpleCmd parameters to tailor them to your site. This can be done by opening up the associated .py file under simplecmds (SimpleCmds Location) and then adjusting the default= values for the options. 1. Locat…
    Qube 6.4Apr 15, 2013
  8. 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…
    Qube 6.4Sep 27, 2013
  9. 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…
    Qube 6.4Oct 12, 2012
  10. Creating a new SimpleCmd

    Creating a SimpleCmd and adding it to the QubeGUI is a relatively straight-forward process. Since the QubeGUI will scan the simplecmds directory for any Python files, it will pick up any newly developed files. These files will contain a create() command t…
    Qube 6.4Apr 15, 2013