View source for MAS array id and array list

This model is current as of mce_script/trunk r287.  This model is subject to change!  (Especially for experiments that will run multiple MCE on a single PC...)

For experiments with multiple MCEs / cryostats / arrays, the MCE scripts need to be told what configuration files to use.  To this end, each array is given a short one-word name.  The list of array names is put in the file <tt>$MAS_TEMPLATE/array_list</tt>.  The name of the array that the machine is currently operating should be put in the file <tt>/data/cryo/array_id</tt>.  When the system needs a version of <tt>experiment.cfg</tt> or <tt>array.cfg</tt>, it will source them from <tt>$MAS_TEMPLATE/experiment_NAME.cfg</tt> or <tt>$MAS_TEMPLATE/array_NAME.cfg</tt> resepctively.

== Example ==

For two arrays in Chile and in the lab, we make the array_list file:

  # List of array names and associated integers for userword
  CHILE         100043
  LAB           103203

The integer in the second column will be put into the 'user_word' field of the clock card, which ends up in the data frame header and can help identify the origin of data should it be mis-filed.  Don't use 0 in this list, but otherwise use whatever you want.  The value of 'cc box_id' might be a good idea, for forward compatibility.  You can use hex numbers, just prefix them with 0x.

To switch a computer into CHILE configuration, we put the word 'CHILE' in /data/cryo/array_id:
  $ echo CHILE > /data/cryo/array_id

Our different configurations are stored in the <tt>$MAS_TEMPLATE</tt> folder:
  $ ls $MAS_TEMPLATE
  array_CHILE.cfg
  array_LAB.cfg
  array_list
  config_create.bash
  config_header.bash
  config_run.bash
  experiment_CHILE.cfg
  experiment_LAB.cfg
  mas_aliases.bash
  mas_env.bash



== Don't forget... ==

Remember that the version of experiment.cfg being used for auto-tuning is the one in $MAS_DATA, and that this copy is only updated when the date (local time) changes.  If you want to force auto-tuning to use a fresh copy of the correct experiment.cfg, run set_directory after removing the existing experiment.cfg:
  $ set_directory                 # This makes sure current_data is up-to-date
  $ rm $MAS_DATA/experiment.cfg
  $ set_directory                 # This copies in the new experiment.cfg

If the MCE hardware/firmware is substantially different, it will also be necessary to update the mce.cfg file... do something like this:
  $ cd ~/src/mas/config
  $ sudo cp mce_CHILE.cfg /etc/mce/mce.cfg

[[Category:MAS]]