Release Notes for R04-11-02 (last updated 01/31/2006, ST):

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

• Installing LATTE
• Upgrading LATTE
• Troubleshooting
• Dependencies, Bug Fixes, and New Features
• Supplemental Notes/Information
• Module and Component Version Information

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.5 is installed.  If not, download it from: http://www.python.org
   • Python should not be installed to a path with spaces in it (ie. C:\Program Files)
3. After the Python installation add the Python 2.3.5 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.
   • LATTE should not be installed to a path with spaces in it.

   Setting up the cfg files:

6. 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.
7. 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.
8. Modify runId.cfg and change the machineId to a value that is unique within your site.
9. In order to start Run Control with the modified configuration use the --config configName.cfg command line option.
10. 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).

Verifying LATTE installation:

11. Make sure VxWorks network parameters are set properly.  If not, enter "bootChange" at the VxWorks prompt and enter the correct values.
12. On VxWorks, enter  "< startup-mv2304.vx" or "< startup-mv2304-open.vx".  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.
13. Open up a Command Prompt and change the directory to "%ONLINE_ROOT%\LATTE\start".
14. Type "runcontrolmain --server gitot --config configName.cfg"
15. Load a schema as follows:
    • For GASU based teststands with a TEM, load the schema minimalTemGasuSchemaPri.xml.
    • For GASU based teststands with no TEM, load the schema minimalGasuSchemaPri.xml.
    • For non-GASU based teststands, load the schema minimalTemSchema.xml.
16. Load and run test application testAppMinimal.py from %ONLINE_ROOT%\LATTE\tests\apps.
17. Enter number of events to take (usually 5 is sufficient).
18. You should observe the proper running of the test and number of events taken displayed on the console and on the status panel.

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.

Running Run Control:
 Run Control needs to be started from the LATTE\start directory as follows:
    runcontrolmain  --server servername --config configFilename --schema schemaFileName
Example:
    runcontrolmain  --server gitot --config runControl.cfg --schema %ONLINE_ROOT%\repos\simpleTemSchema.xml
If you need to change the schema without exiting Run Control you can use the “Select Schema” File menu option. 

Upgrading LATTE:

• Prior to installation, the old LATTE directories should be renamed to Online_Pxx-xx-xx and VxWorks_Pxx-xx-xx, where xx-xx-xx is the previous release number.  This allows the user to go back to an earlier release if there is a problem with the latest one.
• After installation, runControl.cfg file needs to be carried over to the new installation.  If you have created a runControl.cfg in the start directory, this needs to be copied to the new LATTE\start directory.  If runControl.cfg exists in another directory and you are using the "runcontrolmain --config" option to specify a configuration file location, then there is no need to move the file.
• Also the LATTE\start\runId.cfg file from earlier releases needs to be copied over to the new installation directory.  The machine ids needs to be updated to ensure uniqueness.  runId.cfg.sample file contains comments indicating machine id assignments for each subsystem.  This scheme allows for 100 teststands per subsystem and 999999 runs per teststand.  If Run Control fails to access the runId.cfg after loading the application script, it will throw an exception.  In addition, if you created a brand new runId.cfg by copying from runId.cfg.sample and fail to change the machine id from its current value of 0, Run Control will throw an exception as well.
• If you create additional batch files to provide a customized runControl.cfg to Run Control, please do not create it under the LATTE installation directory.  Instead use your subsystem root directory (ie. ACD_ROOT, CAL_ROOT, etc.).  This way, when you install a new LATTE release, you won't have to carry over your batch files to the new directory.

Troubleshooting:

• If you have any of the following environment variables defined:
      ACD_ROOT, CAL_ROOT, ELX_ROOT, INT_ROOT, TKR_ROOT, TRG_ROOT
  you may get an error stating that the digestData file does not exist.  This is due to the fact that Run Control now validates subsystem scripts as well as core LATTE scripts.  When the subsystem installation packages are ready this won't be a problem; however, until then you need to do the following after your LATTE installation completes:
  • Open up a Command Prompt.
  • Type "cd %ONLINE_ROOT%\LATTE\setup".
  • Type "createDigestData %XXX_ROOT% c:\Python23 XXX_01-00-00" where XXX is your subsystem prefix.  The third parameter is not important right now but it should have your subsystem release tag in the future.
• If you get an error such as "bad marshal data" you may have the digestData but it may have been created with an old Python release.  In that case, follow the instructions above again to recreate the file.
• If you get an error similar to the following:
      ERROR:root:ImportError: Bad magic number in c:\LAT\CAL\Scripts\calu_init.pyo
  that means your byte codes were generated with a different Python version.  To fix this just delete all *.pyo and *.pyc files from your script directories.
• If you get an error saying:
        'python' is not recognized as an internal or external command, operable program or batch file.
  then your python installation directory may not be in your search path.  Edit your PATH environment variable and add C:\Python23 to it.       

Dependencies, Bug Fixes, and New Features:

Flight Software Release:

• This version of LATTE includes and requires the "R04-11-02" release of the flight software libraries.
• No changes were introduced between the R04-11-01 and R04-11-02 releases.

Qt and PyQt Related:

• This release requires and uses Qt 3.3.3, PyQt 3.14.1 and SIP 4.2.1.  All the required libraries can be found in the LATTE\ext directory.  Prerequisite for these libraries is Python 2.3.5.
• pyuic.exe is also provided in the same directory and should be used to generate python code from the .ui files.  The best way of doing this is to run setupLATTE.bat from the LATTE\start directory before running pyuic.  This way an older version of pyuic won't be used by mistake.  Also, please make sure you own a valid PyQt license if you are going to use pyuic.   
• If sub-systems are doing any GUI development using the Qt Designer, it is recommended that they download and compile Qt 3.3.x on their systems. 

LDF:

• This release requires and uses LDF v05-07-00.   Refer to the release notes (%ONLINE_ROOT%/LDF/doc/release_notes.txt) for more information.

Hippodraw:

• Hippodraw 1.14.8.5 is included with this release.

Run Control:

• [LTE-372] - ParameterVerifier tries to pass None as a string

Miscellaneous:

• [LTE-373] - DataExport checks writability of source directory instead of destination directory

Supplemental Notes/Information:

Plumbing Flags:

       The following flags can be used in a schema file under the <flags> tag to configure the FSW drivers and the LCB.  The flag name follows its default value along with a description of what the flag does.

• 'BoardId': 0x22
  LATp address of the LCB board.
• 'CmdrspFabric' : 'On'
  If set to On, this flag enables the relative node in the command response fabric.  If set to 'Off', it disables the node in the command response fabric.  If set to 'Ignore', the node status in the command response fabric is not affected by the plumbing operations.
• 'EnableInternal1PPS': 0
  If set to 1, enables the internal 1PPS by setting the corresponding bit in the CRU configuration register.
• 'EventFabric' : 'On'
  Same as previous flag, but for the event fabric.
• 'PowerPdu0' : False
  If set to true, PDU 0 is powered on.
• 'PowerPdu1' : False
  If set to true, PDU 1 is powered on.
• 'PowerPrimDab' : False
  If set to true, the primary side of the GASU is powered on.
• 'PowerSecDab' : False
  If set to true, the secondary side of the GASU is powered on.
• 'UseBitWide' : 0
  If set to 1, forces the LCB to work in bit wide mode.
• 'UsePdu1' : False
  If set to true, PDU 1 is used to provide power to this node.
• 'UseRedundant': 0
  If set to 1, forces the LCB to use the redundant side of the GASU.
• 'UseSecMainFeed': False
  Is set to true, the secondary main feed is used to provide power to the LAT.
• 'UseTrailingIclock': 0
  If set to 1, forces the LCB to clock its input data using the trailing edge of the clock.
• 'UseTrailingOclock': 0
  If set to 1, forces the LCB to clock its output data using the trailing edge of the clock.
• 'IgnoreMissingNodes': 1
  If set to 0, it will cause the removal from the command response and event fabrics of all the nodes which are not in the schema.  If applicable the power for these nodes will be turned off.
• 'UseRedundantConv': False
  If set to True, forces the LCB to use the redundant power supply for the ACD.

        The following table shows the flags that each functional block supports:

GAEM	'CmdrspFabric', 'EventFabric', 'UsePdu1', 'UseRedundantConv'
GCRU	'EnableInternal1PPS'
GEBM	'CmdrspFabric'
GEPU	'CmdrspFabric', 'EventFabric', 'UsePdu1', 'UseRedundantConv'
GGEM	'CmdrspFabric', 'EventFabric'
GLCB	'BoardId', 'UseRedundant', 'UseBitWide', 'UseTrailingIClock', 'UseTrailingOClock', 'IgnoreMissingNodes'
GPDU	'CmdrspFabric'
GSIU	'CmdrspFabric', 'EventFabric', 'UseSecMainFeed', 'PowerPdu0', 'PowerPdu1', 'PowerPrimDab', 'PowerSecDab'
GTEM:	'CmdrspFabric', 'EventFabric', 'UsePdu1'

        In the case of GSIU definition, the following convention should be used:

        ID=0 corresponds to SIU_ext
        ID=1 corresponds to SIU_0
        ID=2 corresponds to SIU_1
 

Command Line Options:

usage: startupMainGUI.py --config <configname> --server <servername> [--appdir <appdirname>]
 [--cmddebug <cmddebugname>] [--evtdebug <evtdebugname>] [--fswmsglevel <fswmsglevelname>]
 [--noreload <noreloadname>] [--schema <schemaname>] [--securedir <securedirname>]
 [--app <appname>] [--ocsport <ocsportname>] [--initforce] [--noerrfile] [--norcoverride] [--ocsverbose]
 [--oesforce] [--playback] [--paramverify]

Detailed explanation:

Mandatory options:
--server to specify the hostname or the IP address of the teststand crate to connect to.
--config to specify the run control configuration file to use.

Optional options:
--app Specify the standalone application or suite to run.
   Typically used by test or suite runners.
--appdir Specify the application directory
--cmddebug Specify command client debug mode (defaults to 0).
   If this option is specified then all register accesses from the command client is logged to the logger.
--evtdebug Specify event client debug mode (defaults to 0)
   The following debug modes are available and can be added together for combinations:
        0: No Debug
        1: Debug All
        2: Event Dump
        4: Warnings
        8: Parser Output
        16: Error Output
--fswmsglevel Specify the FSW message level for the OCS manager task.
--initforce Force command-response and event fabrics initialization on the SBC.
--noerrfile Disable error archive file output.
--noplumbing Do not automatically plumb the LAT upon connection.
--norcoverride Prevents the run conditions to be overridden with NOT-DEFINED.
--noreload Specify a file that contains prefixes of modules which should not be reloaded when a user script is selected.
    This list gets appended to the default list which currently contains the following prefixes 'scipy', 'weave', 'qwt', 'xml', 'pyexpat', 'win32'.
    The file should contain one prefix per line.
--ocsverbose Enable fabrics initialization messages on the SBC.
--ocsport Define the port used to connect to OCS
--oesforce Force our OES socket to be the default event server for the SBC.
--paramverify Force the parameter verifier to come up even if running in non-secure mode
--playback Indicate that Run Control should command the event server to play back the next event from its file.  Since this is done using the GLT's self trigger command, the state of the internal trigger enable bit deterimines whether the application or Run Control will issue the self trigger command.No events will be delivered if the application has the internal trigger enabled, but doesn't issue CMD_SELF_TRIGGERs.
--schema Specify the schema file to load.
--securedir The full path to the secure directory where the password file ("passwords") and the user permissions file ("security.cfg") is stored.  If this switch is specified then RunControl is started in secure mode.
 

Run Report Tags:

The following table contains a list of all LATTE supported tags which may appear in a run report (rcReport.out):

Version Information:

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

Module	Version
CMX[cmx_asBuiltSpy]	V2-4-2
CMX[cmx_asBuilt]	V2-2-2
EMP[asc]	V0-0-5
FILE[file_hdr_rtos]	V2-3-0
Ft	1.0b1
Ft.Xml	1.0b1
GNAT[gnat_vme]	V2-0-1
GNAT[gnat_xbrd]	V2-0-1
LATC[lat_init]	V6-2-0
LATTE	2.3
LATTE.browser	2.5
LATTE.browser.Browser	2.5
LATTE.browser.BrowserImpl	2.15
LATTE.browser.BrowserPreferences	2.2
LATTE.browser.BrowserReadme	2.1
LATTE.browser.bar	2.1
LATTE.browser.barw	2.3
LATTE.browser.browserPreferencesImpl	2.2
LATTE.browser.doublehisto	2.3
LATTE.browser.imagedata	2.1
LATTE.browser.listmean	2.1
LATTE.browser.mask	2.1
LATTE.browser.multibar	2.5
LATTE.browser.radiomask	2.1
LATTE.browser.towerwidget	2.2
LATTE.browser.towerwidgetImpl	2.2
LATTE.browser.trgConsumer	2.7
LATTE.browser.trgDisplay	2.10
LATTE.browser.trgDisplayImpl	2.17
LATTE.browser.userAppBrowser	2.9
LATTE.browser.userAppBrowserGui	1.2
LATTE.browser.userAppLeaf	2.4
LATTE.browser.userAppLoader	2.6
LATTE.browser.userAppTree	2.4
LATTE.client	2.5
LATTE.client.gBits	2.5
LATTE.client.gCmdCli	2.7
LATTE.client.gCommand	2.3
LATTE.client.gEvtCli	2.37
LATTE.client.gException	2.13
LATTE.client.gFswMessages	2.4
LATTE.client.gLog	2.8
LATTE.client.gLoopback	2.2
LATTE.client.gNode	2.2
LATTE.client.gOcsMessages	2.4
LATTE.client.gOpcode	2.1
LATTE.client.gOptions	2.5
LATTE.client.gRegister	2.3
LATTE.client.gResponse	2.6
LATTE.client.gSocket	2.13
LATTE.consumer	1.2
LATTE.consumer.consumer	1.5
LATTE.consumer.consumerPlotter	1.10
LATTE.consumer.standardLDF	1.7
LATTE.consumer.standardPlotter	1.10
LATTE.consumer.standardPlotterGui	1.4
LATTE.consumer.standardPlotterGuiImpl	1.2
LATTE.copyright_SLAC	1.2
LATTE.database	2.5
LATTE.database.gAEM	2.17
LATTE.database.gAttr	2.17
LATTE.database.gCRU	2.8
LATTE.database.gConstraint	2.3
LATTE.database.gDb	2.22
LATTE.database.gEBM	2.10
LATTE.database.gEGU	2.4
LATTE.database.gEPU	2.1
LATTE.database.gFabrics	2.5
LATTE.database.gGEM	2.19
LATTE.database.gGLT	2.7
LATTE.database.gGroup	2.1
LATTE.database.gHSK	1.14
LATTE.database.gHdb	1.8
LATTE.database.gLAT	2.18
LATTE.database.gLCB	2.12
LATTE.database.gMem	1.5
LATTE.database.gNAT	2.4
LATTE.database.gOCS	2.29
LATTE.database.gPDU	2.12
LATTE.database.gPlumber	2.13
LATTE.database.gRule	2.4
LATTE.database.gSIU	2.1
LATTE.database.gSchemaConfig	2.80
LATTE.database.gTEM	2.27
LATTE.database.gTPG	2.4
LATTE.database.gVersions	2.33
LATTE.database.gXBR	2.17
LATTE.dispatch	2.2
LATTE.dispatch.dispatcher	2.1
LATTE.dispatch.errors	2.1
LATTE.dispatch.robustapply	2.1
LATTE.dispatch.saferef	2.1
LATTE.gosed	1.2
LATTE.gosed.GOSEDACD	1.7
LATTE.gosed.GOSEDACDImpl	1.9
LATTE.gosed.GOSEDCAL	1.8
LATTE.gosed.GOSEDCALImpl	1.9
LATTE.gosed.GOSEDCALTKR	1.10
LATTE.gosed.GOSEDCALTKRImpl	1.11
LATTE.gosed.GOSEDData	1.13
LATTE.gosed.GOSEDDataImpl	1.10
LATTE.gosed.GOSEDPainter	1.18
LATTE.gosed.GOSEDPreferences	1.7
LATTE.gosed.GOSEDPreferencesImpl	1.18
LATTE.gosed.GOSEDReadme	1.2
LATTE.gosed.GOSEDTKR	1.4
LATTE.gosed.GOSEDTKRImpl	1.2
LATTE.gosed.GOSEDTWR	1.4
LATTE.gosed.GOSEDTWRImpl	1.2
LATTE.gosed.GOSED_LDF	1.44
LATTE.gosed.GOTED	1.2
LATTE.gosed.GOTEDImpl	1.7
LATTE.gosed.ServerPreferences	1.2
LATTE.gosed.ServerPreferencesImpl	1.10
LATTE.gosed.colorScale	1.3
LATTE.gosed.gosed	1.11
LATTE.gosed.gosedImpl	1.32
LATTE.logger	2.2
LATTE.logger.AlertGuiImpl	1.5
LATTE.logger.MSGLogGUI	2.2
LATTE.logger.MSGLogGUIImpl	2.12
LATTE.logger.socketLogging	1.2
LATTE.monitoring	1.4
LATTE.monitoring.Collector	1.6
LATTE.monitoring.HskAlarms	1.9
LATTE.monitoring.HskCli	1.3
LATTE.monitoring.HskCollector	1.8
LATTE.monitoring.HskGuiReceiver	1.9
LATTE.monitoring.HskPacketDecoder	1.3
LATTE.monitoring.HskPacketRetriever	1.2
LATTE.monitoring.HskReceiver	1.9
LATTE.monitoring.HskRecorder	1.7
LATTE.monitoring.HskRegisters	1.2
LATTE.monitoring.HskRetriever	1.9
LATTE.monitoring.HskSqlGuiReceiver	1.7
LATTE.monitoring.HskSqlInterface	1.7
LATTE.monitoring.HskSqlSvr	1.4
LATTE.monitoring.HskSvr	1.13
LATTE.monitoring.Receiver	1.2
LATTE.monitoring.Recorder	1.3
LATTE.monitoring.Retriever	1.3
LATTE.monitoring.TrendMaps	1.9
LATTE.monitoring.Trendable	1.2
LATTE.monitoring.testTrending	1.3
LATTE.monitoring.tools	1.3
LATTE.monitoring.tools.monitoringDbSyncIn	1.1
LATTE.monitoring.tools.monitoringDbSyncOut	1.5
LATTE.monitoring.tools.parseFswHsk	1.3
LATTE.power	1.3
LATTE.power.GpibPwrCtrl	1.2
LATTE.power.GpibPwrCtrlImpl	1.2
LATTE.power.PorcinePanel	1.8
LATTE.runcontrol	2.2
LATTE.runcontrol.Argument	2.1
LATTE.runcontrol.ArgumentImpl	2.2
LATTE.runcontrol.EnvMon	2.3
LATTE.runcontrol.EnvMonImpl	2.19
LATTE.runcontrol.EnvMonSetRange	2.1
LATTE.runcontrol.FEpowerUp	2.16
LATTE.runcontrol.FSM	2.0
LATTE.runcontrol.GlobalPanel	2.4
LATTE.runcontrol.GlobalPanelImpl	2.20
LATTE.runcontrol.LATsweep	2.13
LATTE.runcontrol.PowerPanel	2.1
LATTE.runcontrol.PowerPanelImpl	2.10
LATTE.runcontrol.RunControl	2.5
LATTE.runcontrol.RunControlCommon	2.44
LATTE.runcontrol.RunControlFSM	2.2
LATTE.runcontrol.RunControlGUI	2.3
LATTE.runcontrol.RunControlGUIImpl	2.2
LATTE.runcontrol.RunControlMain	2.56
LATTE.runcontrol.RunControlMainGUI	2.3
LATTE.runcontrol.RunControlMainGUIImpl	2.19
LATTE.runcontrol.fits2ldf	2.1
LATTE.runcontrol.ldf2fits	2.2
LATTE.runcontrol.rcArchiver	2.3
LATTE.runcontrol.rcCommentPanel	2.4
LATTE.runcontrol.rcComplStatus	2.5
LATTE.runcontrol.rcEndRunDlg	2.3
LATTE.runcontrol.rcEndRunDlgImpl	2.4
LATTE.runcontrol.rcFitsWriter	2.5
LATTE.runcontrol.rcHouseKeeping	2.4
LATTE.runcontrol.rcLogin	2.2
LATTE.runcontrol.rcLoginImpl	2.1
LATTE.runcontrol.rcParamVerifier	2.3
LATTE.runcontrol.rcParamVerifyGUI	2.3
LATTE.runcontrol.rcParamVerifyGUIImpl	2.6
LATTE.runcontrol.rcPreferencesGUI	2.7
LATTE.runcontrol.rcPreferencesGUIImpl	2.15
LATTE.runcontrol.rcPreferencesManager	2.19
LATTE.runcontrol.rcPythonShell	2.1
LATTE.runcontrol.rcReportGen	2.12
LATTE.runcontrol.rcRunIdHelper	2.2
LATTE.runcontrol.rcScmCfgSelector	2.1
LATTE.runcontrol.rcSecurityMan	2.5
LATTE.runcontrol.rcStatusMonitor	2.11
LATTE.runcontrol.rcSuite	2.22
LATTE.runcontrol.rcTestReport	2.5
LATTE.runcontrol.rcTransitions	2.134
LATTE.runcontrol.rcUsers	2.2
LATTE.runcontrol.rcUtil	2.12
LATTE.start	1.2
LATTE.start.startupGUI	1.1
LATTE.start.startupMainGUI	2.14
LATTE.tests	1.2
LATTE.tools	2.2
LATTE.tools.AcdHWMultiplexer	2.2
LATTE.tools.DataDistributor	2.7
LATTE.tools.DataDistributorPoll	2.3
LATTE.tools.DataExport	2.8
LATTE.tools.FreeSpace	2.1
LATTE.tools.MailAlert	1.2
LATTE.tools.gAlert	1.5
LATTE.tools.guiBridges	2.8
LATTE.tools.taskEngine	2.2
LATTE.trigger	2.3
LATTE.trigger.NullObjects	2.3
LATTE.trigger.TrgAbstract	2.1
LATTE.trigger.TrgCmdCounters	2.1
LATTE.trigger.TrgCnoCounters	1.1
LATTE.trigger.TrgCoincidences	2.1
LATTE.trigger.TrgConditions	2.2
LATTE.trigger.TrgConditionsValue	2.2
LATTE.trigger.TrgEngines	2.1
LATTE.trigger.TrgEventCounter	2.1
LATTE.trigger.TrgGem	2.9
LATTE.trigger.TrgGemAbstract	2.3
LATTE.trigger.TrgGemCounters	2.2
LATTE.trigger.TrgGemPeriodicCondition	2.1
LATTE.trigger.TrgGemRegisterGeometry	2.2
LATTE.trigger.TrgGemRegisters	2.9
LATTE.trigger.TrgGemSequence	2.1
LATTE.trigger.TrgInputEnables	2.2
LATTE.trigger.TrgMiniGLT	2.4
LATTE.trigger.TrgMiniGLTAbstract	2.1
LATTE.trigger.TrgMiniGLTRegisters	2.1
LATTE.trigger.TrgObject	2.3
LATTE.trigger.TrgPPSTimer	1.1
LATTE.trigger.TrgPeriodic	2.1
LATTE.trigger.TrgRoiAsTiles	2.1
LATTE.trigger.TrgRoiAsVeto	2.1
LATTE.trigger.TrgSequence	2.1
LATTE.trigger.TrgTileCounters	2.1
LATTE.trigger.TrgTower	2.1
LATTE.trigger.TrgTriggerCounters	2.1
LATTE.trigger.TrgUsingTiles	2.1
LATTE.trigger.rcDefaultTrigger	2.2
LATTE.trigger.rcTrgFunctions	2.3
LATTE.trigger.rcTrgGem	2.11
LATTE.trigger.rcTrgMiniGLT	2.8
LCBD[lcbd]	V1-2-10
LDF.LDF	5.7.0
LEM[lem]	V4-2-1
LEM[lem_cli]	V4-2-1
LEM[lem_lists]	V4-2-1
MSG[msg_mt]	V2-0-3
MSG[msg_print]	V2-0-3
LatSimOcs.c	2.16
MySQLdb	1.1.8
Numeric	23.6
OCS(server)	2.1
OCS[ocs]	V7-8-1
OES[oes]	V6-4-2
PBS[pbs]	V2-9-0
PIG[pig_flying]	V8-0-0
PIG[pig_power]	V8-0-0
PyQt	3.14.1
Python	0x20305f0
Qt	3.3.3
SIP	0x40201
VXW[vxw_eeprom]	V6-1-4
ZLIB[zlib_inflate]	V2-1-0
cfitsio	2.510
logging	0.4.9.5
sihippo	1.14.8.5
startup-mv2304.vx	1.4
xml	0.8.3

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

Back