Submits a job of reconstruction, simulation, microdst reading or any else job using a fortran or a car-file for NA38 and/or NA50. +------+------------------------+ | dimu | pro [subpro] [options] | +------+------------------------+ where pro is either (case ignored) : GEA for GEANT handling ,or JET for simulation program MIC for microDSt reading REC for reconstruction program FOR for any program steered by a FORTRAN file CAR for any program steered by a CAR file subpro can be any string, of which the first 3 characters are taken into account when storing information for a subsequent call of dimu with the same subpro. dimu will present a panel with obvious fields to fill in. These fields are generally pre-filled according to the informations stored in a "lasting_globalv" file for all DIMU previously invoked. Using the given informations, dimu will create a script file, named as the jobname, which will be sent to batch or executed interactively. The following helps can also be displayed using the PF1 key in any of the DIMU panels. Note that the PF keys are located at the right hand-side of the keyboard, with the d2 (CERN) convention. Options are : ------------- -col if you want to open a coloured xterm window (not yet implemented) -d1 if you want to have the CCIN2P3 key-mapping -d2 if you want to have the CERN key-mapping (default) -deb to get some debug in the execution of dimu -mail if you want to receive a mail at the end of execution of the job -next if you want dimu to increment the 1st input tape number -win in order to open a Xterm window to run dimu -xx internal use for window handling +------------------------------------------+ | Remarks concerning the first panel | +------------------------------------------+ Submission : ------------ The submission time must be given in minutes, in the units of the batch site. Instead of a numerical value, you can also type in I in order to run interactively, or N to see the created files without execution, or T to execute interactively the created exec until the loading of the program. The submission site is the one from which you invoke dimu. On Anastasie and Basta at in2p3.fr, you can select a given system (HP or RS) where you wish to run the job. By default (Any), the job is sent to any available system. Cradle or Fortran : ------------------- When dimu FOR is called, a fortran file (with extension .f) must be given. Otherwise, a cradle (with extension .cra) is required. Please do not write the extension when the fortran (cradle) name is asked. For dimu GEA, JET, MIC and REC, there is a minimum cradle in the group directory, to be copied onto your own cradle when your cradle is missing. The fortran (or cradle) will be copied to "jobname.f (or .cra)" in order to be available at the execution time. Data : ------ A data file is required when you invoke dimu GEA, JET, MIC or REC, it is not mandatory for dimu CAR or FOR, depending on your own code. If a data file is requested but doesn't exist, it will be copied from the group_directory if pro is GEA, JET, MIC or REC. If not, a warning message appears on the screen and the job will not be sent for execution. The data file will be copied into jobname.data in order to be available at the execution time. Input and output file(s) : -------------------------- If you invoke dimu GEA, JET, MIC or REC, the needed input and output files are automatically requested according to the program name and eventually to the cradle content (for input) or to the data content (for output). Otherwise, neither input nor output file are predefined. Once the needed input/output files are filled in, a new line appears in order to define additional input or output files. For those, you will have to define the logical unit and the format. Input and output files can be either tapes or files (for which you have to define the full name (with its extension), as well as its location, according to the following rules : - your current directory when location is not given; - your home directory when location is A; - the group/experiment directory when location is G. You can ask for chained volumes by giving several tape names concatenated with "+" sign. If more than 2 volumes are needed you add "+" at the end of the line, so that a new line appears, where you can continue your request. For example, VS3001+VS3008+ on the first line will activate an additionnal line where you will be able to enter VS3015+VS3022. The same syntax is applied for the fseq (sequence definition) (e.g. 1-30+1-30+ on the first line, 1-25+1-21 on the second line). Source file : ------------- The source file must exist on either your current directory (default) or your home directory (defined as A on the panel) or the group/experiment directory (defined as G on the panel). +-----------------------------------------+ | Remarks concerning the second panel | +-----------------------------------------+ Jobname : --------- Jobname is chosen by dimu using the first five letters of the cradle (or fortran) followed by an incremental number... You can overwrite it at your convenience. Libraries : ----------- Default libraries are given according primo to your lasting_globalv file when it exists and secundo to the requested program... You can overwrite them at your convenience and ensure that they exist on a known directory (group_directory or cern/pro/lib directory). Standard files : ---------------- Standard files are the ones nedded by the NA38/NA50 standard programs, i.e. essentially input and output files for geometrical and hardware parameters. When dimu CAR or FOR are invoked only the parameter file is proposed. You can overwrite whatever file you want. You have to ensure that the given file is either on your current directory (nothing to fill), or on your home directory (if specified as A) or on the group/experiment directory (if specified as G). Other pam_files : ----------------- According to the number of +PAM cards in your cradle, you may need to build a fortran using more than one car (or pam) file. You can define them here under the form d1/fn1 d2/fn2 etc... with the same correspondance as above between "d1, "d2", etc and directory(ies). Compilation options : --------------------- The specification "-save" will save the created fortran under the name "jobname.f". The specifications "-g" or "-xdb" or "-dbx" will allow you to make interactive debug of the program (in that case, execution time must be "I"). Other needs : ------------- For your convenience, you can include some unusual specifications in the last lines of the panel... All specifications are translated in lowercases. PF Keys : --------- Using the PF11 key allows you to edit files, according to the cursor position. If the cursor is on line 2 (job line), the exec will edit the script just before to be executed. If the cursor points onto the parameter or the constant file, the exec lifi is executed. (c) A.Romana 3 2 48 76 111 74 110 122 128 162 161 185 5 3 48 61 75 95 112 61 75 84 112 123 128 148 159 147 159 185