System usage: Difference between revisions
No edit summary |
No edit summary |
||
| Line 27: | Line 27: | ||
Note that the '''EDMSCRIPTS''' location is where most of the scripts called through the gui run from. | Note that the '''EDMSCRIPTS''' location is where most of the scripts called through the gui run from. | ||
On '''RunControl''' gui select '''TS/Setup->SoftIOC''' to boot SoftIOC. This calls a script called | 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 | 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_setupmob]]. This script holds a lot of the ''meat'' for setting up the digitizers and getting the system running. | |||
=Known Issues= | =Known Issues= | ||
If error ''Fonts did not load'', or something along these lines, then type following to fix | If error ''Fonts did not load'', or something along these lines, then type following to fix | ||
xset fp+ /usr/share/X11/fonts/100dpi | xset fp+ /usr/share/X11/fonts/100dpi | ||
Revision as of 22:47, June 2, 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.
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_setupmob. This script holds a lot of the meat for setting up the digitizers and getting the system running.
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