Short write-ups of utilities in ~daq/bin ============================================ daqctl - prints to stdout a short summary for each accelerator burst. Usefull for online monitoring during the data taking. (see a note) daqprn - prints to stdout contents of data records in "human" format. (see a note) dumpev - produce a raw hexadecimal dump of the data records. evrtest - an example of usage of shared memory in fortran program. file2shm - copies given file to shared memory. getrig - reads data file(s) and filters the trigger events. logserver - listens the network requests from logclients on OS9 and copies what they send to stdout. ;-) onlu - produces a number of histogramms to see what is going on during the data taking. (see a note) runcontrol - the main script to start, stop, pause and resume the data taking (e.g. > runcontrol start > runcontrol stop ) shm2file - copies contents of shared memory to a file shmclient - copies contents of shared memory on remote host to the shared mamory on local host. shmcreate - creates a shared memory segment. shmdbg - allows to inspect and modify the shared memory. shmkill - marks the shared memory for deletetion. shmreset - resets the the VIR and writers PIDs. shmserver - serves the requests of remote hosts to copy the shared memory via network (see shmclient) sstart - magic to prevent the duplication start of some critical utilities (e.g. shmserver,tcp2shm ...) tcp2file - listens the network for DAQ requests and copies the data to a file. tcp2shm - listens the network for DAQ requests and copies the data to shared memory. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - NOTE: Utilities daqctl, daqprn, dumpev and onlu can read both from a file and from shared memory. usage: daqprn without parameters it will try to attach to shared memory daqprn ~/scratch/run99/calib it will open one by one all the files ...calib001, 002, 003 ... daqprn ~/scratch/tun99/calib005 it will open only one file - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ********** C A U T I O N !!!!! ************ The utilities daqctl, daqprn, dumpev, evrtest are absolutely safe and you may run as many instances of each as you want. Only one instance of onlu should be running on the system because it keeps the histogramms in global memory which is always the same. I hardly believe that two or more instances of onlu can share it. Even so the result will always be crazy. To look at the histogramms type > paw paw> onlu and you will be served with easy-to-learn graphical interface supplemented with simple keystrokes commands like (usualy for the next set of pictures), q (to quit) and so forth. Running any other utility is not always safe for data taking. Usualy they could be found in scrips designed for special purposes like start the data taking, stop or pause or resume it. If you are not completely understand what they do you are advised to avoid using them. Better use scripts the main of which is runcontrol. The best way to keep all the above away from your troubles is using the rampex GUI: login as daq and type > rampex& and good luck! Your comments and suggestions are always wellcome. M. Ukhanov 1999 25 March.