S. Hagopian November 8, 1991 Version 1.0 MUODIS - Muon Event Display I. INTRODUCTION MUODIS is the D0 Wide Angle Muon system (WAMUS) event display. It is part of the PIXIE library, which can be run in various frameworks. Hooks are set up for PIXIE in D0USER and EXAMINE2. (See .DOCs) It displays module outlines, hits, cells, and tracks. There are two main types of displays - "views" where the viewer is at a distance outside the whole muon detector, and only modules that have hits are displayed, and "cuts", where a cross-section of the detector is displayed and hits and tracks from these modules are projected onto this plane. Not all tracks and hits are displayed in a cut view. There is also a "TRACK BLOWUP", which is centered around a track, with 2 views, bend plane and non-bend plane. II. GETTING a MUON DISPLAY A. Program builder The package MUODIS must be included in the package list to get the MUON event display. To get combined displays, including CAL and ZTRAKS as well as WAMUS and SAMUS, use the package ALL_DISPLAY_COMBINED. (The % indicates it is a combined package). B. LINK The normal D0USER link does not include the event display package. One needs to do: $@MUONS_D0USER.LNK DI3000. Also, it is usually best to do a $LIBT PIXIE in order to pick up the latest event display routines and parameters. C. Setup for RUN 1. DI3000 logicals If the DI3000 logicals are not automatically setup, do $SETUP DI3000 or find out where DI3000 is stored on your node and execute DILOGIN.COM The sharable version of DI3000 should be requested by the command: $ DISETSHR EXT HI $SETDRV cod1 cod2 ! to setup the DI3000 device Drivers. The first driver should correspond to the type of terminal you are logged on to; the second one to a hardcopy device[ e.g. TLP ]. For more information see D0$DOCS:DI3000_GUIDE.DOC 2. PIXIE logicals. The event display needs a RCP file to define the views to be displayed and the interactive parameters which control them. For the WAMUS display, the file needed is D0$PIXIE:PX_MUODIS.RCP. The corresponding logical is PX_MUODIS_RCP. The user may redirect the RCP logicals to their own files. It also needs STP files to define the geometry. Logicals pointing to the default files are defined in the program builder file, MUONS_USER.COM. If the user has included the package ALL_DISPLAY, the command file D0$D0USER:EVENT_DISPLAY.COM must also be executed. (This procedure does $SETDRV and sets up the STP files.) D. RUNNING 1. Running EXAMINE2 After "BEGIN PROCESSING" in EXAMINE2, choose menu item "EVENT DISPLAY" in the INTERRUPT menu. 2. Running D0USER. There are two ways to use event display. The first is to turn on the interactive menu and then, while analyzing events, do a DISPLAY EVENT. This will start at a random event. One can also turn on the automatic event display by doing EVENT DISPLAYS (7) before starting the run. It will ask how many events and their particular IDs (if -1 then assumes consecutive). III. MUODIS MENU SUB_LEVEL: MUON Event Display PIXIE Select: {command, #, HELP (#), MENU, BACK} > help 1: All Views 2: Tk Blowup 3: Y-Z View 4: X-Y View 5: X-Z View 6: YZ cut 7: XY cut 8: ZX cut 9. R-Z view 10. MUON DUMP 11: NEXT Event 12: ZOOM 13: ROTATE 14: PICK 15: HARDCOPY 16: MODIFY 17: GO TO Event 18: Change Display Mode 19: Superimpose(On/Off) 20: Set Path 21: Dump Event 22: Write Event 23: Other Options 24: COMPACK System Menu For further information on menu items 11 - 24, see D0$PIXIE:PX_SYSTEM.DOC -------------------------------------------------------------------------------- *MUODIS Menu Title * Function & Remark * -------------------------------------------------------------------------------- ALL VIEWS - shows all modules which have at least one hit and all tracks (with each line given a track number). A 0 is placed at the point (0,0,0) to guide the eye. The Y-Z view, X-Y view and X-Z view are show separately. TK Blowup - Blow-up around a particular track by invoking the TRACK view and answering the questions. Details of the implementation will change with time. Y-Z View - shows all modules which have at least one hit and all tracks (with each line given a track number). The view point is on the X-Axis, outside the detector. X-Y View - shows all modules which have at least one hit and all tracks (with each line given a track number). The view point is on the Z-Axis, outside the detector. X-Z View - shows all modules which have at least one hit and all tracks (with each line given a track number). The view point is on the Y-Axis, outside the detector. YZ cut - Cross-section of WAMUS in Y-Z plane at X=0. (WAMUS SIDE VIEW). Hits and tracks that go thru these modules (and ones parallel to them) are projected onto this plane. (Not all hits and tracks are displayed) XY cut - Cross-section of WAMUS in X-Y plane at Z=0. (WAMUS END VIEW). Hits and tracks that go thru these modules (and ones parallel to them) are projected onto this plane. (Not all hits and tracks are displayed) XZ cut - Cross-section of WAMUS in X-Z plane at Y=0. (WAMUS TOP VIEW). Hits and tracks that go thru these modules (and ones parallel to them) are projected onto this plane. (Not all hits and tracks are displayed) R-Z view - Muon tracks are projected onto the R-Z plane. Tracks with 180.GE.phi.GE.0 are projected to +R Tracks with 360.GE.phi.GE.180 are projected to -R MUON DUMP - Gives choices to dump MUD1 (raw muon hit bank), MUOT (muon track bank) or MUPRT (dump both). If CALL EVE is selected, the dump is shown in the EVE editor. Otherwise a file called MUO_nnnnnnnn_mmmmmmmm.DMP is created (nnnnnnnn is the run number and mmmmmmmm is the event number of the event being dumped). The file contains the EVENT header printout and the reqeusted bank printout. IV. MUODIS PARAMTERS in PX_MUODIS.RCP: -------------------------------------------------------------------------------- * Parameter Name * Default[Type] * Remark * -------------------------------------------------------------------------------- 'MUON DRAW CELLS' 1 '1 = DRAW LATCH CELL,2=DRAW GANGED CELLS,0=NO CELLS' 'MUON DRAW HITS' 1 '1 = DRAW HITS, 0 = NO HITS DRAWN' 'MUON DRAW TRACKS' 1 '1 = DRAW TRACKS, 0 = NO TRACKS' 'MUON HITS ON TKS' 1 '1 = DRAW HITS ON TRACKS, 0 = NO' 'MUON TIME DIV' 1 '1 = TIME DIV IN XY VIEW =1 ON, =0 OFF' 'MUON DRIFT TIME' 1 'DRIFT TIME SOLUTIONS =1 ON, =0 OFF' 'MUON TRIG COUNTER' 0 '1 = ON, 0 = OFF ' 'MUON DRAW MAGNET' 0 '1 = DRAW MAGNET, 0 = NO MAGNET' 'MUON LABEL CHAM' 1 '1 = Label chambers, 0 = no labels' 'MUON ONLY' .TRUE. ' Muon Only' 'MUON TK FIT' .FALSE. ' T- plot only tk with good fit;F- plot all' 'COSMIC RAY' FALSE ' ' 'TRACK PTMIN' 1.0000 ' ' 'TRACK DPT' 5.0000 ' ' 'ALL PHI PICK' 0 '0=NO PICK,1=PICK using CAL PHI,DPHI' 'MUON TK BANK' 1 'Bank to draw muon trk:1=MUOT,2=MUON,3=PMUO' 'MUON CUT LAYERS' 1 '0=all,1=a layer,2=CEN only' V. MUODIS SCREENS in PX_MUODIS.RCP: Each basic menu has own screen parameters. Here we show an example, for the YZ cut. !--------------------------------------------------------- ! Definition of MUODIS Screens !--------------------------------------------------------- 'NAME' 'YZ CUT' ' YZ CUT' 'PICKABLE' F ' TRUE if pickable' 'VIEW3D' .FALSE. ' True if eD viewport' 'KEEPCIRCLE' .TRUE. ' True if circles are kept' 'VPORTXMIN' -1.0000 ' X min Viewport' 'VPORTXMAX' 1.0000 ' X max Viewport' 'VPORTYMIN' -1.0000 ' Y min Viewport' 'VPORTYMAX' 1.0000 ' Y max Viewport' 'WINDOWXMIN' -1100.0000 ' X Min Window limit' 'WINDOWXMAX' 1100.0000 ' X Max Window limit' 'WINDOWYMIN' 0.0000 ' Y Min Window limit' 'WINDOWYMAX' -1.0000 ' Y Max Window limit' 'VIEWREFX' 0.0000 ' X View reference pnt' 'VIEWREFY' 0.0000 ' Y View reference pnt' 'VIEWREFZ' 0.0000 ' Z View reference pnt' 'UPVECX' 0.0000 ' X Up vector' 'UPVECY' 1.0000 ' Y Up vector' 'UPVECZ' 0.0000 ' Z Up vector' 'CAMX' 0.0000 ' X Camera point' 'CAMY' 0.0000 ' Y Camera point' 'CAMZ' 1.0000 ' Z Camera point' VI. DOCUMENTATION 1. D0$DOCS:GRAPHICS_GUIDE.DOC - gives an introduction to D0 graphics and references to other documentation. 2. D0$DOCS:DI3000_GUIDE.DOC - gives an introduction to the use of the commercial graphics package, DI3000, and hints on using it on various devices. 3. D0$D0USER:D0USER_GUIDE.MEM - gives more than introduction to D0USER which provides an offline framework. 4. D0$EXAMINE2:EXAMINE_GUIDE.DOC - Users guide to EXAMINE, the ONLINE event monitoring framework. 5. D0$PIXIE:PIXIE_GUIDE.DOC - General guide to PIXIE Event Display