[Halld-online] Comments on DAQ system

[David Lawrence]

Hi Sergey,

  Here is some feedback on the DAQ configuration system you’ve been working on.

1. The “setups.sh” is dedicated to DAQ only and not a generic system for setting software
    packages. Maybe we should consider renaming it to something like “daq_setup.sh” 

2.  In regards to the “pro”, “dev”, and “old” directories under /gluex. First,
    should we have a directory /gluex/DAQ to place the DAQ-specific things in?
    That would put it more in parallel with the /gluex/controls and /gluex/monitoring directories
    that already exist. Also, I think we should just go ahead and check out the tagged
    versions that the pro, dev, old links are pointing to into the hdsys account so that links
    don’t point back to your private directory. I realize it is only temporary, but we should just
    go ahead make it official. (It really makes me cringe to see anything in hdsys or hdops point
    back to a private directory! ;) )

3. I mentioned this to you earlier, but I’ll just repeat it here. The current system automatically
    starts EB, platform, and rcgui on whatever machine setups.sh is run on. This is not such
    a problem for the platform and rcgui, but things like the EB, ER, and FCS will likely
    be run on specific hosts. We should invent some mechanism for specifying this. I think
    adding this to the COOL configuration might be best since we already use information
    from there to tell where the coda_roc processes are run. However, you may have other
    thoughts.


I’ll send any additional feedback as I get more familiar with the system.

Regards,
-David