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.
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
- LATTE installation requires administrative privileges. Please make sure
you are logged in with administrative privileges.
- Make sure Python 2.3 or later is installed. If not, download it from:
http://www.python.org
- After the Python installation add the Python 2.3 installation directory to
your PATH.
- Download and install Win32 Extensions for Python here:
http://sourceforge.net/project/showfiles.php?group_id=78018
- 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.
Verifying LATTE installation:
- Make sure VxWorks network parameters are set properly. If not, enter
"bootChange" and enter the correct values.
- 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.
- Open up a Command Prompt and change the directory to "%ONLINE_ROOT%\LATTE\tests".
- Type "..\start\setupLATTE.bat
- For GASU-based teststands, type:
"python -i test_evt_aem.py --server gitot --schema
%ONLINE_ROOT%\LATTE\repos\simpleGasuSchema.xml" - For CAL teststands,
type:
"python -i test_evt_cal.py --server gitot --schema
%ONLINE_ROOT%\LATTE\repos\simpleTemSchema.xml"
- 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.
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:
- 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.
- 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.
- Modify runId.cfg and change the machineId to a value that is unique within
your site.
- In order to start Run Control with the modified configuration use the
--config configName.cfg command line option.
- 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).
- 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.
- If you have any of the following environment variables defined:
ACD_ROOT, CAL_ROOT, ELX_ROOT, INT_ROOT, TKR_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.
Flight Software Release:
Qt and PyQt Related:
- This release requires and uses Qt 3.3.1 and PyQt 3.11. All the required
libraries can be found in the LATTE\ext directory.
- 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.
Hippodraw:
- Hippodraw 1.11.0 is included with this release.
Functional blocks and registers:
- Added a prescale capability to the ACD software counters.
Run Control:
- Added "Parameter Verifier". When Run Control is launched in 'secure
mode' all run conditions and all parameters entered by the operator needs to
be signed off on. Currently the following run conditions get automatically
added to the verifier:
- Schema File
- Particle Type
- Orientation
- Site
- Instrument Type
- Phase
Additionally user scripts can add the parameters to be verified using the
following method:
self.getParameterVerifier().add(parName,
parValue)
When the parameter verifier GUI is displayed the operator needs put a
check next to each parameter and enter his/her correct password in order to
initiate the test.
- Added delete flag to addExportedFiles(file, delete=False) False is
default.
- Connect to or disconnect from the message logger if the logger
preferences change.
- Make sure we update the application's lat and xbrd when a new schema is
loaded.
Client & Servers:
-
Added getContributionStatus and getContributionStatusStr methods to the
event client.
-
Removed support for archive_xxx methods from the event client.
-
Added GEM and ACD contributions to the canned event
-
Added iteration over the event to overwrite the marker in all
contributions.
Schema and Configuration:
- Added <serialnos> tag to allow for hardware serial no reporting in the
configuration. See simpleTemSchemaSerial.xml for an example.
- Added getAllOpaque and getAllSerialNos methods to GLAT to provide access
to all opaque blocks and all serialnos entries.
- Added writeConfig and exposed writeSchema and writeConfig to GLAT.
- Fixed unCompressSequence for the case when the sequence string is empty.
- Added schemas for testing include tag and dead and noisy strips.
- Changed schema and configuration parsing and dumping to use
xml.dom.minidom.
- It is now possible to add a macro to represent the preference inside a
path preference.
An example of this would be adding the current instrument type value in the
path:
C:\LAT\CAL\Schema\@lastinstrumenttype
Trigger Interface:
- Added support for external triggering.
Miscellaneous:
- Previously Qt and PyQt versions were not being reported in the run
report.
- use-ACD-P.vx, use-ACD-R.vx scripts have now been added to the \Vxworks
directory.
(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