| 1 |
/home/prodtest/cvs/JSOC/doc/iris_lev0_on_front_back_end.txt |
| 2 |
|
| 3 |
The "real" IRIS datacapture machine is irisdc. This is called the front |
| 4 |
end machine. It runs /home/prodtest/cvs/JSOC/proj/datacapture/scripts/socdciris |
| 5 |
which in turn runs ingest_lev0_irisdc. This is as user prodtest. |
| 6 |
/home/prodtest/cvs/JSOC/proj/lev0/apps/ingest_lev0_irisdc.c is normally edited |
| 7 |
on irisdc. It must be coded to run on both the frontend and the backend |
| 8 |
(cl1n001) machines. It is run on the frontend by socdciris like so: |
| 9 |
|
| 10 |
ingest_lev0_irisdc vc=VC03 indir=/sds/soc2soc/iris outdir=/sds/soc2pipe/iris |
| 11 |
pipedir=/sds/pipe2soc/iris logfile=$log2 JSOC_DBNAME irisdb JSOC_DBHOST irisdc |
| 12 |
|
| 13 |
It is run on the backend by doingestlev0_IRIS.pl like so: |
| 14 |
|
| 15 |
ingest_lev0_irisdc vc=VC03 indir=/dds/soc2pipe/iris logfile=<log_file_name> |
| 16 |
ingest_lev0_irisdc vc=VC03 indir=/dds/soc2pipe/iris/rexmit logfile=<log_file_name> |
| 17 |
|
| 18 |
Note that an 'outdir=' must not be used in the bakend. This is how |
| 19 |
ingest_lev0_irisdc knows to rm the tlm and qac files from the indir after |
| 20 |
it has copied them to the /SUMs. |
| 21 |
|
| 22 |
|
| 23 |
/home/prodtest/cvs/JSOC/proj/lev0/apps/ingest_lev0_irisdc.c is normally edited |
| 24 |
on irisdc. It is then 'cvs commit' to the sunroom cvs/JSOC tree. |
| 25 |
It is made on irisdc as user prodtest. |
| 26 |
|
| 27 |
On n02, as user prodtest, do this: |
| 28 |
n02:/home/prodtest/cvs/JSOC/proj/lev0/apps> cvs update ingest_lev0_irisdc.c |
| 29 |
> cd /home/prodtest/cvs/JSOC |
| 30 |
> make ingest_lev0_irisdc |
| 31 |
(Then tell Art that the cvs/Development tree must be update. |
| 32 |
Basically we want to get the new executable in place, something like this): |
| 33 |
> cp _linux_x86_64/proj/lev0/apps/ingest_lev0_irisdc |
| 34 |
/home/jsoc/cvs/Development/JSOC/bin/linux_x86_64/ |
| 35 |
|
| 36 |
Run on cl1n001 as user jsocprod (actually this will be done |
| 37 |
by calling doingestlev0_IRIS.pl as user jsocprod): |
| 38 |
|
| 39 |
cl1n001:/home/jsocprod> ingest_lev0_irisdc vc=VC03 indir=/dds/soc2pipe/iris |
| 40 |
logfile=/tmp/iris.log1 |
| 41 |
|
| 42 |
To stop the doingestlev0_IRIS.pl and the ingest_lev0_irisdc it has spawned, |
| 43 |
run on cl1n001 as jsocprod: |
| 44 |
|
| 45 |
> stop_lev0_IRIS.pl |
| 46 |
|
| 47 |
=============================================================================== |
| 48 |
/home/prodtest/cvs/JSOC/proj/lev0/apps/build_lev1_iris.c: |
| 49 |
|
| 50 |
To stop build_lev1_iris on cl1n001: |
| 51 |
touch /usr/local/logs/lev1/build_mgr_stop_iris |
| 52 |
|
| 53 |
|
| 54 |
Make on n02 prodtest: |
| 55 |
n02:/home/prodtest/cvs/JSOC> make build_lev1_iris |
| 56 |
|
| 57 |
as user jsocprod on cl1n001 put in Development: |
| 58 |
cl1n001:/home/jsoc/cvs/Development/JSOC/bin/linux_x86_64> cp |
| 59 |
/home/prodtest/cvs/JSOC/bin/linux_x86_64/../../_linux_x86_64/proj/lev0/apps/build_lev1_iris . |
| 60 |
|
| 61 |
For test w/IRIS pre-launch: |
| 62 |
cl1n001:/home/jsocprod> build_lev1_mgr mode=recnum instru=iris dsin=iris_ground.lev0_dc1 dsout=iris_ground.lev1_dc1_TMP brec=0 erec=0 quicklook=1 logfile=/tmp/lev1.log |
| 63 |
|
| 64 |
cl1n001:/home/jsocprod> build_lev1_mgr |
| 65 |
mode=recnum instru=iris dsin=iris_ground.lev0_dc1 dsout=iris_ground.lev1_dc1 |
| 66 |
brec=0 erec=0 numrec=12 numcpu=8 numqsub=16 |
| 67 |
|
| 68 |
=============================================================================== |
| 69 |
|
| 70 |
On irisdc there is a cron job: |
| 71 |
30 20 * * * /home/prodtest/cvs/JSOC/proj/lev0/scripts/rsync_irisdc_jsoc.pl |
| 72 |
|
| 73 |
which rsync's: |
| 74 |
irisdc:/home/prodtest/cvs/JSOC to sunroom:/home/prodtest/irisdc_backup |
| 75 |
|
| 76 |
There are some files in this tree, like with dcs[0,1,2] which are unique to |
| 77 |
the datacapture machine. |
| 78 |
|
| 79 |
|
