|
Size: 1793
Comment:
|
← Revision 16 as of 2021-03-09 04:24:00 ⇥
Size: 1414
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
== This all seems to be obsolete now; needs some TLC == |
|
| Line 7: | Line 9: |
| The process is running inside a screen on megatron. | The process runs inside of GNU screen on megatron. It relies on `mysql` and `apache2`. |
| Line 9: | Line 11: |
| The restart procedures for megatron are as follows: * service mysql start * service apache2 start * screen (conlog is run from within a screen) * tcsh # just because the environment script below assumes csh instead of bash) * cd /cvs/cds/rtcds/caltech/c1/target/conlog/conlogepics * source conlog_environment.txt * ./starup.c1conlog * Enter: Ctrl+a , d to exit the screen and leave the conlog running To re-start the process if you only killed the screen, you need to start up a screen, set your environment, and then run the startup.c1conlog script : |
It is started by [[http://upstart.ubuntu.com/|upstart]], which is the Ubuntu init system. The main configuration script is: |
| Line 22: | Line 13: |
| tcsh cd /cvs/cds/rtcds/caltech/c1/target/conlog/conlogepics source conlog_environment.txt ./startup.c1conlog |
/etc/init/conlog.conf |
| Line 27: | Line 15: |
| This will leave you at an epics prompt, which means the code is running. (That's why I left it running in a screen for now). Just disconnect from that screen session without closing it to keep the Conlog running. | You can start/stop the process using the upstart utilites: {{{ $ sudo start conlog $ sudo stop conlog $ status conlog }}} There should NOT really be a need to do this, but if you want to attach to the screen session to see what's going on you can do so like this: {{{ screen -x CONLOG }}} If you accidentally kill the process, restart it as described above ("sudo start conlog"). |
| Line 30: | Line 28: |
/ligo/caltech/data/conlog/c1/add_channel_names /ligo/caltech/data/conlog/c1/remove_channel_names Then start up medm as follows: |
|
| Line 37: | Line 29: |
| cd ~/ryan/ medm -x -macro "IFO=C1" medm/CONLOG.adl |
$TARGET/conlog/add_channel_names $TARGET/conlog/remove_channel_names |
| Line 41: | Line 32: |
| Then click the Add channel list button or Remove channel list button. | Then use the conlog MEDM screen reload the channel lists: {{{ $MEDM/MISC/CONLOG.adl }}} |
| Line 44: | Line 38: |
| /ligo/caltech/data/conlog/c1/use_channel_names | {{{ $TARGET/conlog/use_channel_names }}} |
aLIGO EPICs log (conlog)
This all seems to be obsolete now; needs some TLC
The aLIGO EPICS log (conlog) for the 40m is 'working' at: http://192.168.113.209/conlog/conlog.php
The process runs inside of GNU screen on megatron. It relies on mysql and apache2.
It is started by upstart, which is the Ubuntu init system. The main configuration script is:
/etc/init/conlog.conf
You can start/stop the process using the upstart utilites:
$ sudo start conlog $ sudo stop conlog $ status conlog
There should NOT really be a need to do this, but if you want to attach to the screen session to see what's going on you can do so like this:
screen -x CONLOG
If you accidentally kill the process, restart it as described above ("sudo start conlog").
To change the list of channels when the conlog is running, you need to edit the file (s):
$TARGET/conlog/add_channel_names $TARGET/conlog/remove_channel_names
Then use the conlog MEDM screen reload the channel lists:
$MEDM/MISC/CONLOG.adl
To change the channels before running the conlog from a blank database, you would edit:
$TARGET/conlog/use_channel_names
(I believe this should be read whenever the conlog is restarted, but I'm only sure it does the first time you start conlog).