load_env

The command load_env sets environment variables defined in the config_env.xml file. This file has to be in the directory where the macroserver is running. The variables needed for the auto_beamshutter, auto_filter and exafs are formattd in a different way. All the other variables are defined in the miscellaneous part of the tree.

<?xml version="1.0" encoding="UTF-8"?>

<sw>
<feature>
 <name>auto_filter</name>
 <parameters>
   <FilterMax>100</FilterMax>
   <FilterMin>10</FilterMin>
   <FilterAbsorber>motoms2</FilterAbsorber>
   <AutoFilter>False</AutoFilter>
 </parameters>
</feature>
<feature>
 <name>auto_beamshutter</name>
 <parameters>
   <BeamshutterSignal>counter1</BeamshutterSignal>
   <BeamshutterLimit>10</BeamshutterLimit>
   <BeamshutterTime>5</BeamshutterTime>
   <AutoBeamshutter>False</AutoBeamshutter>
 </parameters>
</feature>
<feature>
 <name>exafs</name>
 <parameters>
   <ExafsIntTimes>1, 2, 3, 4</ExafsIntTimes>
 </parameters>
</feature>
<miscellaneous>
  <name>miscellaneous</name>
  <TestEnvironment>1, 2, 3, 4</TestEnvironment>
  <TestEnvironment2>hallo</TestEnvironment2>
</miscellaneous>
</sw>

There is no error if any of the features or variables for the auto_filter, auto_beamshutter or exafs are not defined. The old settings are kept.

For the miscellaneous part, the tag (for example: TestEnvironment) would be the name of the variable in spock and the text (for the TestEnvironment tag: 1, 2, 3, 4) would be the value of this variable.



2019-11-13