D0X Setup and Running

Setup in the D0 environment is via:

d0setup xframe

on any of the d0 platforms. d0setup will run a procedure in the xframe area, which will in turn define "logicals" and "symbols", including the symbol d0x which is used to run the program.

VMS

On VMS, the setup_xframe.com procedure will ask you if you are sitting in front of a color or b/w terminal. In addition, it will define logicals which point to a few RCP files which are (or might be) needed (see below). To change from color to b/w or vice versa, you can either rerun the procedure or use the symbols d0x_color and d0x_bw to change defaults.

unix

On UNIX platforms, setup_xframe will set the default interface to be in color. For a b/w interface, use the alias d0x_bw and for a color interface use the alias d0x_color.

RCP files

RCP files are used by the program when accessing various D0 offline packages (see D0 packages). At present, the RCPs that need to be defined are:

qcd_jet_correction_rcp (for CAFIX)

ftraks_rcp (for COMPUTE_EM_QUALITY [CLEANEM])

tags_map_rcp (for UDST_TO_DST)

calevt_rcp (for CAFIX?)

cafix_rcp (for CAFIX)

correctem_rcp (for CAFIX)

cleanmu_rcp (for COMPUTE_MU_QUALITY [CLEANMU])

cleanem_rcp (for COMPUTE_EM_QUALITY [CLEANEM])

trd_analysis_rcp (for COMPUTE_EM_QUALITY [CLEANEM])

trd_rcp (for COMPUTE_EM_QUALITY [CLEANEM])

Note that on the VMS systems, these RCPs are logicals, whereas on UNIX they are pointers (or links). d0setup xframe will define the correct logicals on VMS systems, and will create the proper links on UNIX systems. For UNIX, this unfortunately means that you will have a set of link files hanging around! They will not disappear when d0x exits, and if you want to run d0x more than once (run it, exit, run it again) from two different areas, you will have to <d0setup xframe each time in order to get the RCP links defined! You can then delete these RCP links each time you define them, or leave them alone (they don't take up any real space). Note that for UNIX, you will have to fire up d0x from an area where you have the write privileges to create these link files. An alias clean_d0x has been provided on UNIX machines which will "clean up" these little RCP droppings. Since each time you want to fire up d0x on UNIX an environmental variable is set to the place where the RCP links are created. The script clean_d0x will delete the links using this variable.

d0x options

Options to d0x are the same basic X/Windows options available to all applications which are invoked via application name (as opposed to typing "run ..." on the VMS system). The ones which are most useful are:

    d0x -title "title"      puts the title string "title" up in the main window
        -display a.b.c      sends the X/Window display to host a.b.c instead of
                            the usual (set via SET DISPLAY/CREATE...)
        -iconic             startup as icon (why would you care...???)

Look in any decent X/Windows manual for the full set of options.

Running d0x

Invoke the program by:

d0x

You should see the following appear:

Non Illegitimus Carborundum? Translates to

"Don't let the bastards grind you down". Not real Latin, but close enough.

Notice the 4 menu items:

File (see Data Access)

Tools (see D0X Tools)

Control (see D0X Control

Help Menus

The underscore under the letter tells you that if you push the ALT key and the letter, you get the same as if you had clicked on the item. For instance, ALT-F will open the File menu.