40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log  Not logged in ELOG logo
Entry  Wed Oct 23 00:05:17 2013, manasa, Update, SUS, Unstable Y arm ALS points to problems with ETMY suspension Y-SUS_All.png
    Reply  Wed Oct 23 09:17:33 2013, Steve, Update, SUS, ETMY sensors compared to ETMX ETMYglitching.pngOSEMsensorsETMY&X.pngETMYgettingKickedUp.pngdrive-damp.png
       Reply  Wed Oct 23 11:42:28 2013, rana, Update, SUS, ETMY sensors compared to ETMX 
       Reply  Wed Oct 23 15:48:06 2013, rana, Update, SUS, ETMY sensors compared to ETMX remote-control-cockroach.jpg
          Reply  Wed Oct 23 17:30:17 2013, jamie, Update, SUS, ETMY sensors compared to ETMX 
             Reply  Wed Oct 23 18:24:56 2013, rana, Update, SUS, ETMY sensors compared to ETMX 
                Reply  Wed Oct 23 18:28:01 2013, Jenne, Update, SUS, ETMY sensors compared to ETMX Screenshot-Untitled_Window.pngScreenshot-Untitled_Window-1.png
                   Reply  Thu Oct 24 10:31:25 2013, Steve, Update, SUS, ETMY sensors compared to ETMX 24h_glitching.pngdampingOffref.png
                   Reply  Tue Oct 29 10:51:16 2013, Masayuki, Update, SUS, ETMY sensors compared to ETMX 
                   Reply  Tue Oct 29 22:33:57 2013, rana, Update, SUS, ETMY sensors compared to ETMX Scratch-n-SniffStinkyDooBabyShowerGame1.jpg
                      Reply  Wed Oct 30 14:58:44 2013, Steve, HowTo, General, shutting down a computer 
                Reply  Thu Oct 24 12:00:11 2013, jamie, Update, CDS, fb acquisition of slow channels  
                   Reply  Fri Oct 25 01:46:33 2013, rana, Update, CDS, fb acquisition of slow channels  
Message ID: 9278     Entry time: Thu Oct 24 12:00:11 2013     In reply to: 9267     Reply to this: 9288
Author: jamie 
Type: Update 
Category: CDS 
Subject: fb acquisition of slow channels  

Quote:

 

 While that would be good - it doesn't address the EDCU problem at hand. After some verbal emailing, Jamie and I find that the master file in target/fb/ actually doesn't point to any of the EDCU files created by any of the FE machines. It is only using the C0EDCU.ini as well as the *_SLOW.ini files that were last edited in 2011 !!!

So....we have not been adding SLOW channels via the RCG build process for a couple years. Tomorrow morning, Jamie will edit the master file and fix this unless I get to it tonight. There a bunch of old .ini files in the daq/ dir that can be deleted too.

I took a look at the situation here so I think I have a better idea of what's going on (it's a mess, as usual):

The framebuilder looks at the "master" file

    /opt/rtcds/caltech/c1/target/fb/master

which lists a bunch of other files that contain lists of channels to acquire.  It looks like there might have been some notion to just use 

    /opt/rtcds/caltech/c1/chans/daq/C0EDCU.ini

as the master slow channels file.  Slow channels from all over the place have been added to this file, presumably by hand.  Maybe the idea was to just add slow channels manually as needed, instead of recording them all by default.  The full slow channels lists are in the

    /opt/rtcds/caltech/c1/chans/daq/C1EDCU_<model>.ini

files, none of which are listed in the fb master file.

There are also these old slow channel files, like

    /opt/rtcds/caltech/c1/chans/daq/SUS_SLOW.ini

There's a perplexing breakdown of channels spread out between these files and C1EDCU.ini:

controls@fb ~ 0$ grep MC3_URS /opt/rtcds/caltech/c1/chans/daq/C0EDCU.ini
[C1:SUS-MC3_URSEN_OVERFLOW]
[C1:SUS-MC3_URSEN_OUTPUT]
controls@fb ~ 0$ grep MC3_URS /opt/rtcds/caltech/c1/chans/daq/MCS_SLOW.ini
[C1:SUS-MC3_URSEN_INMON]
[C1:SUS-MC3_URSEN_OUT16]
[C1:SUS-MC3_URSEN_EXCMON]
controls@fb ~ 0$

why some of these channels are in one file and some in the other I have no idea.  If the fb finds multiple of the same channel if will fail to start, so at least we've been diligent about keeping disparate lists in the different files.

So I guess the question is if we want to automatically record all slow channels by default, in which case we add in the C1EDCU_<model>.ini files, or if we want to keep just adding them in by hand, in which case we keep the status quo.  In either case we should probably get rid of the *_SLOW.ini files (by maybe integrating their channels in C0EDCU.ini), since they're old and just confusing things.

In the mean time, I added C1:FEC-45_CPU_METER to C0EDCU.ini, so that we can keep track of the load there.

 

ELOG V3.1.3-