JSOC/doc/iris_lev0_on_front_back_end.txt - view

Return to iris_lev0_on_front_back_end.txt CVS log

Up to [Development] / JSOC / doc

File: [Development] / JSOC / doc / iris_lev0_on_front_back_end.txt (download)
Revision: 1.6, Mon Jun 24 16:28:42 2013 UTC (9 years, 11 months ago) by prodtest
Branch: MAIN
CVS Tags: Ver_LATEST, Ver_DRMSLATEST, Ver_9-5, Ver_9-41, Ver_9-4, Ver_9-3, Ver_9-2, Ver_9-1, Ver_9-0, Ver_8-8, Ver_8-7, Ver_8-6, Ver_8-5, Ver_8-4, Ver_8-3, Ver_8-2, Ver_8-12, Ver_8-11, Ver_8-10, Ver_8-1, NetDRMS_Ver_LATEST, NetDRMS_Ver_9-5, NetDRMS_Ver_9-41, NetDRMS_Ver_9-4, NetDRMS_Ver_9-3, NetDRMS_Ver_9-2, NetDRMS_Ver_9-1, NetDRMS_Ver_9-0, NetDRMS_Ver_8-8, NetDRMS_Ver_8-7, NetDRMS_Ver_8-6, NetDRMS_Ver_8-5, NetDRMS_Ver_8-4, NetDRMS_Ver_8-3, NetDRMS_Ver_8-2, NetDRMS_Ver_8-12, NetDRMS_Ver_8-11, NetDRMS_Ver_8-10, NetDRMS_Ver_8-1, HEAD
Changes since 1.5: +10 -3 lines

*** empty log message ***

		/home/prodtest/cvs/JSOC/doc/iris_lev0_on_front_back_end.txt

The "real" IRIS datacapture machine is irisdc. This is called the front
end machine. It runs /home/prodtest/cvs/JSOC/proj/datacapture/scripts/socdciris
which in turn runs ingest_lev0_irisdc. This is as user prodtest.
/home/prodtest/cvs/JSOC/proj/lev0/apps/ingest_lev0_irisdc.c is normally edited
on irisdc. It must be coded to run on both the frontend and the backend
(cl1n001) machines. It is run on the frontend by socdciris like so:

ingest_lev0_irisdc vc=VC03 indir=/sds/soc2soc/iris outdir=/sds/soc2pipe/iris
pipedir=/sds/pipe2soc/iris logfile=$log2 JSOC_DBNAME irisdb JSOC_DBHOST irisdc

It is run on the backend by doingestlev0_IRIS.pl like so:

ingest_lev0_irisdc vc=VC03 indir=/dds/soc2pipe/iris logfile=<log_file_name>
ingest_lev0_irisdc vc=VC03 indir=/dds/soc2pipe/iris/rexmit logfile=<log_file_name>

Note that an 'outdir=' must not be used in the bakend. This is how
ingest_lev0_irisdc knows to rm the tlm and qac files from the indir after
it has copied them to the /SUMs.


/home/prodtest/cvs/JSOC/proj/lev0/apps/ingest_lev0_irisdc.c is normally edited
on irisdc. It is then 'cvs commit' to the sunroom cvs/JSOC tree.
It is made on irisdc as user prodtest.

On n02, as user prodtest, do this:
n02:/home/prodtest/cvs/JSOC/proj/lev0/apps> cvs update ingest_lev0_irisdc.c
> cd /home/prodtest/cvs/JSOC
> make ingest_lev0_irisdc
(Then tell Art that the cvs/Development tree must be update.
Basically we want to get the new executable in place, something like this):
> cp _linux_x86_64/proj/lev0/apps/ingest_lev0_irisdc
/home/jsoc/cvs/Development/JSOC/bin/linux_x86_64/

Run on cl1n001 as user jsocprod (actually this will be done
by calling doingestlev0_IRIS.pl as user jsocprod):

cl1n001:/home/jsocprod> ingest_lev0_irisdc vc=VC03 indir=/dds/soc2pipe/iris
logfile=/tmp/iris.log1

To stop the doingestlev0_IRIS.pl and the ingest_lev0_irisdc it has spawned,
run on cl1n001 as jsocprod:

> stop_lev0_IRIS.pl

===============================================================================
/home/prodtest/cvs/JSOC/proj/lev0/apps/build_lev1_iris.c:

To stop build_lev1_iris on cl1n001:
touch /usr/local/logs/lev1/build_mgr_stop_iris


Make on n02 prodtest:
n02:/home/prodtest/cvs/JSOC> make build_lev1_iris

as user jsocprod on cl1n001 put in Development:
cl1n001:/home/jsoc/cvs/Development/JSOC/bin/linux_x86_64> cp
/home/prodtest/cvs/JSOC/bin/linux_x86_64/../../_linux_x86_64/proj/lev0/apps/build_lev1_iris .

For test w/IRIS pre-launch:
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

cl1n001:/home/jsocprod> build_lev1_mgr
mode=recnum instru=iris dsin=iris_ground.lev0_dc1 dsout=iris_ground.lev1_dc1
brec=0 erec=0 numrec=12 numcpu=8 numqsub=16

===============================================================================

On irisdc there is a cron job:
30 20 * * * /home/prodtest/cvs/JSOC/proj/lev0/scripts/rsync_irisdc_jsoc.pl

which rsync's:
 irisdc:/home/prodtest/cvs/JSOC to sunroom:/home/prodtest/irisdc_backup

There are some files in this tree, like with dcs[0,1,2] which are unique to
the datacapture machine.

Karen Tian