5. Customize Desktop App

In some cases the defaults used to submit a batch job may not work on your given cluster or you may just want to remove some form options presented to the user and fill in hard-coded values. All of these cases and more can easily be customized in the following files:

bc_desktop/local/cluster_desktop.yml

Form configuration file that describes a given Desktop app along with form attributes presented to the user. Replace cluster_desktop with a representable name, in the previous section we used cluster1.yml and cluster2.yml to describe the desktops for the various clusters. For each form configuration file underneath bc_desktop/local/, a separate desktop app will be presented as an option to the user.

bc_desktop/local/submit/custom_submit.yml.erb

Describes how the batch job should be submitted to your cluster. Replace custom_submit with a descriptive name. Be sure that the name of this file is specified in the bc_desktop/local/cluster_desktop.yml form configuration file, so that when a user submits the form, the specified submission configuration is used when submitting the batch job.

Note

The .erb file extension will cause the YAML configuration file to be processed using the eRuby (Embedded Ruby) templating system. This allows you to embed Ruby code into the YAML configuration file for flow control, variable substitution, and more.

Documentation

• 5.1. Modify Form Attributes
  • 5.1.1. Change to Gnome Desktop
  • 5.1.2. Remove Form Field
  • 5.1.3. Hard-code a Form Field
  • 5.1.4. Change a Label
  • 5.1.5. Add Help Message to Field
  • 5.1.6. Change Field Default Value
• 5.2. Custom Job Submission
  • 5.2.1. Slurm
  • 5.2.2. Torque
  • 5.2.3. LSF
  • 5.2.4. PBS Professional