# # # Hosts that various CODA components should run on. # Format is: # # component_name hostname # # e.g. # PEB0 gluon53 # # Components that are not explicitly listed here # will be started on the node that the startup # script is run from. ROCs should not be set here # and will be ignored if they are. For ROCs, the # component name always corresponds to the node # and so is always used to start the coda_roc # process on the remote node. # # #-- hd_all_mc -- # # platform gluon46 # #RC gluon41 # DCFDC gluon50 # DCFCAL gluon50 # DCCDCSTPS gluon50 # DCTAG gluon50 # DCBCAL gluon50 # # FCSgluon47 gluon47 PEB0 gluonraid4 #EBER1 gluondaqbuff #SEB0 gluonraid5 #ERsoftROC gluonraid5 #ERraid0 gluonraid5 # #SEB0 gluondaqbuff #ERsoftROC gluondaqbuff #ERraid0 gluondaqbuff # SEB0 gluon50 ERsoftROC gluon50 ERraid0 gluon50 #--- 2 streams only !! --- #SEB1 gluonraid5 #ERraid1 gluonraid5 SEB1 gluondaqbuff ERraid1 gluondaqbuff #----------- # # USE_RAMDISK - Set this to "yes" for files to be written to # to the RAM disk on the node where the ERsoftROC # is running. If set to "no", files will be written # to rotating RAID partitions. (Partition will be # rotated between runs). HOSS (online skims) will # only run if this is set to "yes". # # USE_LOCAL - Set this to "yes" to have coda state transition # scripts run on the node where the ERsoftROC is # being run. If set to "no", the scripts will all be # run on the node where the platform is running. # Usually you'll want this set to "yes". # # USE_4part - This is an option for CDAQ (not CODA) that tells # it to write 4 streams simultaneously. This will # maximize the overall write rate for CDAQ. It will # have no affect if running CODA. USE_RAMDISK yes USE_LOCAL yes USE_4PART no #--- end --- # MONITOR yes MONITOR no #HOSS yes HOSS no