2 Using DART
The first screen that you get after starting DART lets you select a keystore to use for authentication, see figure 3.
This keystore file must contain your private key (signed by a trusted certification authority) and the certificates of the certification authorities (CA) used in the DEISA network. The Keystore file must be a valid Java Keystore (JKS) or in the pkcs12 format (extension p12). The file is used for authentication during the retrieval of data from a DEISA accounting server. You have to enter your password for the keystore in the configuration dialog (see Figure 3) before you can click NEXT to go on. If you are a DEISA user you should have installed UNICORE for job submission. You can use the same keystore file that you are using for UNICORE without any changes. Normally the UNICORE keystore can be found under $USER_HOME/.unicore/keystore. If you don't have your own certificate and key read the Certificate Guide first. With the File button in this first screen you can select the location of the keystore file to use, by default DART tries to locate the keystore used by UNICORE.
The next step is to set the generic settings. You will see a screen like in Figure 4. In main there are three areas: the role selection, the date period selection and the site selection.
Role selection: The DEISA accounting service specifies the access roles DEISA user, DEISA project, DEISA site and DEISA supervisor. A DEISA user is every person who is allowed to submit jobs in the DEISA network. The DEISA user is permitted to see only the records of his own jobs. The DEISA project role is for PIs, co-PIs, project leaders and project controllers. These persons are permitted to see all records related to their project(s). The DEISA site role is for DEISA staff only. These persons are allowed to see all jobs that ran on their own site and all jobs that ran on other sites by users which are registered at their site. The DEISA supervisor role is for DEISA management.
If you are a DEISA user: choose the 'DEISA user' role and enter your username.
If you are a DEISA PI or co-PI: choose the 'DEISA project' role and enter the name of your project or, if you are authorised for more than one project, you can use the wild card option '*' or the single word 'all' to display the usage for all your projects instead of entering each project one by one.
If you are a DEISA Site Administrator: choose the 'DEISA site' role and enter the short DEISA site name (BSC, CINECA, CSC, ECMWF, EPCC, FJZ, HLRS, IDRIS, LRZ, RZG or SARA).
Date selection: Select a start date and a end date for a period of your choice. Each Date must be in the YYYY-MM-DD format. Be warned that long periods will cause long retrieval times.
Site selection: Here you can select the sites from which data should be retrieved. Maybe if you never started a job at LRZ there won't be usage records for you. Selecting only the necessary sites may improve performance of data retrieval because only the necessary accounting services will be queried.
By clicking on the NEXT button the retrieval will start. This step can take a little time.
After the retrieval has finished you will see the report screen (see Figure 4). In the tabs you will find a total report for the whole selected period, and a tab for each month in this period. Be warned if you specified only a few days of a month, the month screen will also contain only the data for this part of the month.
Sample: Startdate = 2006-05-15, Enddate = 2006-07-21
The view for May will contain all records from May 15 to May 31.
The view for June will contain all records from June 1 to June 30.
The view for July will contain all records from July 1 to July 21.
The Total view will contain all records from May 15 to July 21.
Records from May 5 or July 25 are NOT included in any of this report screens!
Usage is displayed as 'job time' (the wall clock time of the job multiplied with the number of reserved cores) and 'CPU time' (the total CPU time used on all cores).
For 'job time', two values are displayed: a normalised value in standardised DEISA core-hours and the non-normalised core-h(ours). For 'CPU time', only one value is displayed: the CPU time in standardised DEISA core-hours.
The normalised value is obtained by employing a conversion factor, which relates the execution system time to a reference system time (currently a Power4 CPU running at 1.7GHz). The Job time will, in principle, always be larger than the CPU time.
Export: It may be useful to export the report data. Maybe you will use them in a report or a presentation. There are two easy ways to export the data. The first way is to mark the interesting part in a table. By pressing Ctrl-C you can copy the data to the clipboard. Now you can paste the data in an OpenOffice Calc or an Excel Chart by pressing Ctrl-V. Or right click at the table to open a popup menu for this task.
The other way is the use of the Export button in the top of the window. By pressing this button the total report will be exported into a semicolon separated text file (see Figure 6).
The meaning of the values in this files are (from left to right): project name, user name, site name, machine name, count of jobs, walltime, job time std core-h, job time, cpu time std core-h.
If you like you can create a new report using the New Report button, now. Or you can store the settings you made and leave DART. Saving the settings decrease the work of typing in most of the settings again at the next program start.