Using SLAC's Glast Data Servers
Three servers enable you to create your own custom datasets, access the full root-trees (digi, recon), and browse the data using the event display:
- Astro Data Server - Select events by time, region in sky, etc. (aka Glast Data Server)
- Pruner - Filter the Merit Ntuples by applying cuts and selecting columns.
- Peeler - Select full root trees for specific events.
This page describes the DataServer web interface for the batch submission of pruner and peeler jobs. Parameters for the batch jobs can be supplied through this interface, and are stored in a backend database used to create histories of jobs submitted by an individual. This information is then available to the user when configuring subsequent runs.
Notes:
- Logging in (for the first time). When you access the Welcome page for the first time, you will be asked to authenticate against the SLAC single sign-on CAS server before you are allowed to access data from a database.
You will need your SLAC Windows or Unix account:
- Admin Tab. From the Admin tab, you can logoff the SLAC network, or test the connection to the database of users (and their batch options).
Tip: Database testing is useful to make sure that you have all the privileges necessary for running this application.
- Default Parameters (from last job submitted). Default batch parameters are retrieved from a database, enabling you to populate initial data with values from the last job you submitted which can then be edited as appropriate for the next job.
Alternatively, from the History tab, you can choose a task from the Batch Submission History page that has a set of parameters closest to those you want to use for your next job. If dev or test link is selected, data is respectively retrieved from the developer's database or the test database.
- Error Messages. Error messages are displayed if some values are incorrect or exceed the range allowed (e.g., min run range larger than the max run range, TCut variables have improper names, etc). You can elect to ignore these warnings and submit the job, or go back and correct the error made in the view (editing) page.
- Expert Options. Expert options are also available to experienced users who are familiar with the batch submission options, and with the pruner/peeler environment options. An "expert" check box allows for these additional options to be added before the job is submitted.
Select this option only if you already know what the extra environment variables are for the pruner or peeler job you want to submit. They must have prefixes as indicated in the sample entries. Use the Select checkbox to confirm the choice of the key-value pair. If you run out of table space click on the plus (+) button to add more fields; minus (-) button to remove fields.
- Submitting a Job. After you have set up your pruner or peeler job options, click on the Submit button.
After a delay, the program will respond with a message telling you the ftp address where your output files will be located. You will receive an email notification when the batch job finishes.
Enter Pruner or Peeler parameters are as follows:
Pruner |
From this page you can create and edit the next set of pruner job options.
Note: Also see Peeler, which uses the same set of parameters as a Pruner job, except for a TCut; provides two additional ways to specify an event list for the peeler job
Batch Parameters |
Parameter Values |
Task Name: |
Choose the task name from the drop down list of predefined names.
Caution: If a task name is incorrect, the pruner batch job might not be able to find it, causing the job to fail. Always use the drop down list to designate a task name. |
E-mail: |
Enter the e-mail address where you want the job results to be sent (if different from the default address).
Note: By default, job results are sent to your SLAC e-mail address. To redirect this notification, enter any valid e-mail address. |
TCut: |
TCut provides for a pruner TCut; can be any expression that uses valid TCut parameters.
Note: Only parameter names are verified; the meaning of the expression is not. |
Min/Max run numbers: |
Min/Max run numbers allow for further reducing the number of runs. Can be omitted (in which case, the default values are assumed). Must obey min < max rule. |
|
Used to get a more verbose pruner/peeler batch job output. |
User Comment: |
Used to provide a meaningful description of your job (for later retrieval from history pane). |
Batch Options:
|
Provide a string for bsub options. |
Max Filesize:
|
Maximum file size of pruned file. (specify in MB) |
Environment Options: |
Set of key-value pairs for pruner/peeler batch job options. |
Branch Filter File: |
Expert mode only. Specifies file to be uploaded which has a set of key-value pairs in the form (+/- rule) to be provided to the pruner. Rules are used to add/remove branches from Ntuple ROOT files. |
Branch Filter List: |
Expert mode only. Set of key-value pairs to be provided for pruner branch filter in the same form as for Branch Filter File.
Note: These rules must not contradict each other, or the values used in a TCut expression. |
|
Peeler |
From this page you can create and edit the next set of peeler job options.
Uses the same set of parameters as a Pruner job, except for a TCut; provides two additional ways to specify an event list for the peeler job.
Batch Parameters |
Parameter Values |
Task Name: |
Chosen from a drop down list of predefined names.
Caution: If a name is incorrect, the pruner batch job might not be able to find it, causing the job to fail. Always use the drop down list to designate a task name. |
E-mail: |
Enter the e-mail address where you want the job results to be sent (if different from the default address).
Note: By default, job results are sent to your SLAC e-mail address. To redirect this notification, enter any valid e-mail address. |
File Types: |
Select type(s) of peeler files to be processed.
Note: At the time of this writing, Merit peeler types are not yet supported. |
Event File: |
Click on the Browse button and select a file which contains the list of event numbers you wish to be processed.
The events specified in this file will be displayed in the Event List; see next entry. |
Event List: |
The List of events stored in the Event File referenced above are displayed in the Event List.
Here you can manually enter additional events you wish to process. |
Min/Max run numbers: |
Min/Max run numbers allow for further reducing the number of runs.
Note: Default values are assumed if no entries are made in these fields; parameters entered must obey the min < max rule. |
Debug:
|
Used to get a more verbose pruner/peeler batch job output. |
User Comment: |
Use the comment field to provide a meaningful description of your job (for later retrieval from history database). |
Batch Options: |
Provide a string for bsub options. |
Max Filesize:
|
Maximum size of pruned file. (specify in MB) |
Environment Options: |
Set of key-value pairs for pruner/peeler batch job options. |
|
Owned by: Igor Pavlin
Last updated by: Chuck Patterson
03/16/2006 |
|
|