Configuring "original" Blu-Ice

The original project is in the blu-ice CVS project. This project represents a fork in the Blu-Ice development. New features will probably be added to the new Blu-Ice project as it is easier to maintain and configure. There are various reasons why you may want to use this version, so the configuration instructions are provided.

1. Modify blu-ice/scripts/ice.tcl to reflect your installation.
   • Change the DCS_DIR variable to point to your DCS root directory. Production level software at SSRL runs out of the /usr/local/dcs/ directory.

     For example:

     < set DCS_DIR "/usr/local/dcs/"
     ---
     > set DCS_DIR "/home/scottm/release-3_2/"
     

   • Modify the location of the tcl_clibs.so file to point at the appropriate build directory. By default, it is pointing at the irix build directory.

     < load $DCS_DIR/tcl_clibs/irix/tcl_clibs.so dcs_c_library
     ---
     > load $DCS_DIR/tcl_clibs/linux/tcl_clibs.so dcs_c_library
     

   • Modify ice.tcl to connect to your DCSS server.

     The Blu-Ice program is started with 1 argument - the name of the beam line that it needs to connect to. This argument is used within a large switch statement to initialize the Blu-Ice configuration.

     You will need to modify this switch statement either by changing an existing beam line configuration or by adding a new configuration. Some important parameters within this initialization are:

     • gBeamline(serverName) hostname location of the DCSS server.

     • gBeamline(serverPort) port on which Blu-Ice should attempt to connect to DCSS. This should correspond to the third port number entry in the serverPorts.txt file in DCSS's configuration.

     • gBeamline(title) sets the text of the window's frame at the top of the Blu-Ice.

     • gBeamline(beamlineId) used in various switch statements throught blu-ice.

     • gBeamline(simulation) changes the color of Blu-Ice only.

     • gBeamline(detector) lets Blu-Ice display appropiate detector modes and pictures

     • gBeamline(videoServerUrl) various web address of Axis camera servers.

     • gBeamline(hutchVideoPath)

     • gBeamline(sampleVideoPath)

     • gBeamline(ptzPath) web location of pan-tilt-zoom preset information

2. In blu-ice/data/ copy one of the existing files to the same directory using a new name:

   periodic_beamlineID.dat

   where beamlineID.dat is defined by the gBeamline(beamlineId) variable. Modify the new file to describe your current beam line's capabilities.

   Example:

      smblx5:~/release-3_2/blu-ice/data > cp periodic_bl92.dat periodic_bl92sim.dat
   

3. Modify the blu-ice/scripts/dice_tabs.tcl file and change the following line to reflect a connection to your own Diffraction Image Server.

   blctl92:~/release-3_2/blu-ice/scripts > cvs diff
   cvs diff: Diffing .
   Index: dice_tabs.tcl
   ===================================================================
   RCS file: /home/code/repository/blu-ice/scripts/dice_tabs.tcl,v
   retrieving revision 1.39
   diff -r1.39 dice_tabs.tcl
   136c136
   < 	Diffimage lastImage $gWindows(collect,diffimage,frame) 134.79.31.20 14001 500 500
   ---
   > 	Diffimage lastImage $gWindows(collect,diffimage,frame) localhost 14001 500 500
   

   The 14001 in the above example should correspond to guiPort which is specified on the command line when starting the Diffraction Image Server.