40m QIL Cryo_Lab CTN SUS_Lab CAML OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  ATF eLog  Not logged in ELOG logo
Entry  Fri Aug 20 15:36:01 2010, Dmass, Laser, Doubling, Spectrum Incoming. MZ1_2pn.pdf
    Reply  Wed Aug 25 22:18:35 2010, Dmass, Laser, Doubling, Spectrum Incoming. MZSpecSumDiff.pdf
       Reply  Wed Aug 25 22:58:12 2010, rana, Laser, Doubling, Spectrum Incoming. 
Message ID: 985     Entry time: Wed Aug 25 22:58:12 2010     In reply to: 984
Author: rana 
Type: Laser 
Category: Doubling 
Subject: Spectrum Incoming. 

For ease of use, isn't possible to just load the calibrations into EPICS so that the _OUT channels of these filter banks are calibrated into rads?

i.e. write a matlab or shell script that calculates the peak to peak values and then uses 'ezcawrite' to put the correct value into the GAIN field of that filter module.

Then as long as things don't drift at the 20% level, the data written to disk will be calibrated. There can even be a DAQ channel called PHASE_532 and PHASE_1064.

Then there could be a mDV script that just prints out the calibrated spectrum with noise budget automatically.


On the DAQ side, I was able to get the channel list with mDV by just pointing the mdv_config.m file at ganymede.ligo.caltech.edu (which is fb1 from the outside). However,

I didn't get any data. I looked on fb1 and for some reason, its running 2 copies of the daqd and nds jobs. fb (aka fb0) is just running 1 copy, as is normal. I suggest that

fb1 should only run daqd/nds from its own fb1 directories and that the fb processes on fb1 should be killed.


The NDSPROXY is a TCL script which we should run in the future on our future gateway machine, but not yet.

ELOG V3.1.3-