System usage: Difference between revisions
No edit summary |
|||
Line 40: | Line 40: | ||
=Data Taking= | =Data Taking= | ||
To collect data you must start data collection from an ioc through the command ('''NEED MORE INFO HERE''') | To collect data you must start data collection from an ioc through the command ('''NEED MORE INFO HERE''') | ||
gtReceiver# | gtReceiver# <server> <filename> <maxfilesize> | ||
where the # refers to the version number of the '''Receiver''' software. | where the # refers to the version number of the '''Receiver''' software. | ||
Revision as of 19:30, June 22, 2015
Details Pertaining to the Usage of the System
Just going to write a bunch of stuff here for now and sort it into something more digestible later on...
Starting the acquisition
The acquisition computer is located at digios1.onenet and we are using the logon name and password of dgs
ssh -X [email protected]
Note that on logon it will say dgs@helios1, this should be modified to match digios1.
The working directory of the acquisition gui is
/global/devel/systems/helios
and is based off of the mobacq directory.
To bring up the gui
heliosCommander
using _editable if you know what you are doing.
This will bring up the edm 1-12-3 (on helios1)' window as well as the RunControl gui. If it does not see Known Issues below. This script will also set environment variables such as
export EDMOBJECTS=/global/devel/extensions/dgs1/src/edm/setup export EDMHELPFILES=/global/devel/extensions/dgs1/src/edm/helpFiles export EDMBASE=/global/devel/extensions/dgs1/src/edm export EDM=/global/devel/extensions/dgs1/src/edm/edmMain/O.linux-x86/edm export EDMPVOBJECTS=/global/devel/extensions/dgs1/src/edm/setup export EDMFILES=/global/devel/extensions/dgs1/src/edm/setup export EDMDATAFILES=$EDMDATAFILES:/global/devel/systems/helios/edm/screens export EDMSCRIPTS=/global/devel/systems/helios/edm/scripts
Note that the EDMSCRIPTS location is where most of the scripts called through the gui run from and EDMDATAFILES holds the various gui screen files.
On RunControl gui select TS/Setup->IOC#, where # is the IOC number, to make sure IOC# has booted up. This calls a script called terminals with option #+2. For example to start IOC1
terminals 3
On RunControl gui select TS/Setup->SoftIOC to boot SoftIOC. This calls a script called terminals with option 1.
terminals 1
SoftIOC will then boot, ending with epics> gretClustGT.sav: 929 of 929 PV's connected. The soft IOC calls a script (NEED INFO HERE).
On RunControl gui select TS/Setup->Digitizer Setup. This calls a script called dig_setup. This script holds a lot of the meat for setting up the digitizers and getting the system running. A list of the parameters and their meanings can be found at File:Dig reg map with vba.xls but be aware that this file is subject to change. The most up to date version can be found on the internal svn site (NEED LINK TO SVN HERE).
If all scripts are set properly should be able to start acquisition at this point.
Data Taking
To collect data you must start data collection from an ioc through the command (NEED MORE INFO HERE)
gtReceiver# <server> <filename> <maxfilesize>
where the # refers to the version number of the Receiver software.
Known Issues
If error Fonts did not load, or something along these lines, then type following to fix
xset fp+ /usr/share/X11/fonts/100dpi