Release Notes for P04-04-01 (last updated 09/16/2004):

The latest revision of this document is located here. The notes for the previous release are located here.

Installing LATTE

These procedures cover a Windows installation. If you wish to install LATTE under Unix/Linux, refer to the separate procedure.

Installing Truegrid Pro NFS Server for Windows NT/2000/XP

Please refer to the instructions here to install the NFS server.

Installing LATTE

  1. LATTE installation requires administrative privileges. Please make sure you are logged in with administrative privileges.
  2. Make sure Python 2.3 or later is installed. If not, download it from: http://www.python.org
  3. After the Python installation add the Python 2.3 installation directory to your PATH.
  4. Download and install Win32 Extensions for Python here: http://sourceforge.net/project/showfiles.php?group_id=78018
  5. Download LATTE_Pxx-xx-xx_py2.3.exe from http://www-glast.slac.stanford.edu/IntegrationTest/ONLINE/updates/default.htm. Start the installer and follow the onscreen instructions.
  6. Verifying LATTE installation:

  7. Make sure VxWorks network parameters are set properly. If not, enter "bootChange" and enter the correct values.
  8. On VxWorks, enter  "< startup-ACD-P.vx" or "< startup-ACD-R.vx" for GASU and "< startup-ltem.vx" for an LCB based non-GASU system. If only one of these startup scripts is ever used with a given test stand, you can use the "bootChange" VxWorks command to launch the startup script at boot time.
  9. Open up a Command Prompt and change the directory to "%ONLINE_ROOT%\LATTE\tests".
  10. Type "..\start\setupLATTE.bat
  11. For GASU-based teststands, type:
        "python -i test_evt_aem.py --server gitot --schema %ONLINE_ROOT%\LATTE\repos\simpleGasuSchema.xml"
  12. For CAL teststands, type:
        "python -i test_evt_cal.py --server gitot --schema %ONLINE_ROOT%\LATTE\repos\simpleTemSchema.xml"
  13. For TKR teststands, type:
        "python -i test_evt_tkr.py --server gitot --schema %ONLINE_ROOT%\LATTE\repos\simpleTemSchema.xml"

     Press Enter.
     At the ">>>" prompt, type "test()" and press Enter. You should see the event data or a running counter being displayed.

  14. Displaying software and hardware versions:
    In order to run the "versions" utility, at the command prompt change the directory to "%ONLINE_ROOT%\LATTE" and type "versions.bat --server servername --schema schemaName". This should output version info for all modules (VxWorks and python) loaded, and all hardware defined in the given schema that is connected.

    To begin writing LATTE scripts, refer to the test scripts in the %ONLINE_ROOT%\tests\apps directory for orientation.

    Setting up the cfg files:

  15. For Run Control to operate properly runControl.cfg.sample and runId.cfg.sample should be copied as configName.cfg and runId.cfg respectively and modified based on subsystem requirements.
  16. Modify configName.cfg and add any additional instrument types, particle types, orientation and phase values. All the other settings can be changed within the Run Control preferences dialog.
  17. Modify runId.cfg and change the machineId to a value that is unique within your site.
  18. In order to start Run Control with the modified configuration use the --config configName.cfg command line option.
  19. If you have copied runId.cfg to a location other than the LATTE\start directory specify its location in the runId.cfg directory entry in preferences (Don't forget to click on the SAVE button after making the changes).

Upgrading LATTE:

Troubleshooting:

Dependencies, Bug Fixes, and New Features:

Flight Software Release:

Qt and PyQt Related:

Hippodraw:

Functional blocks and registers:

Run Control:

Client & Servers:

Schema and Configuration:

Trigger Interface:

Miscellaneous:

Version Information:

(Retrieved by running versions.bat --server servername --schema schemaName while in %ONLINE_ROOT%\LATTE directory)

Module

Version

LATTE.client.gBits 2.2
LATTE.client.gCmdCli 2.5
LATTE.client.gCommand 2.3
LATTE.client.gEvtCli 2.16
LATTE.client.gException 2.8
LATTE.client.gLog 2.6
LATTE.client.gLoopback 2.2
LATTE.client.gNode 2.2
LATTE.client.gOptions 2.3
LATTE.client.gRegister 2.3
LATTE.client.gResponse 2.5
LATTE.client.gSocket 2.5
LATTE.database.gAEM 2.9
LATTE.database.gAttr 2.13
LATTE.database.gCRU 2.4
LATTE.database.gConstraint 2.1
LATTE.database.gDb 2.13
LATTE.database.gEBM 2.5
LATTE.database.gEGU 2.2
LATTE.database.gGEM 2.8
LATTE.database.gGLT 2.5
LATTE.database.gGroup 2.1
LATTE.database.gHSK 1.8
LATTE.database.gHdb 1.6
LATTE.database.gLAT 2.10
LATTE.database.gLCB 2.2
LATTE.database.gMem 1.4
LATTE.database.gNAT 2.4
LATTE.database.gOCS 2.11
LATTE.database.gPDU 2.5
LATTE.database.gRule 2.1
LATTE.database.gSchemaConfig 2.27
LATTE.database.gTEM 2.18
LATTE.database.gVersions 2.13
LATTE.database.gXBR 2.13
LDF.LDF 5.1.2
OCS (server) 1.1
PyQt 3.11
Python 0x20304f0
Qt 3.3.1
cfitsio 2.470
logging 0.4.9.2
sihippo 1.11.0
xml 0.8.3
Component

Version

TEM  
GCRC  
GTRC  
AEM  
GARC  
GAFE  


Please contact Selim Tuvi, Ric Claus, Lester Miller or Jim Panetta if you have problems or any questions (Contacts Page)

Back