Q: What has changed from version 1.5.1 to 1.6.0
A:

Feature Summary

The 1.6.0 release of LDAS was tagged in CVS on May 23, 2005. This version added the ability to generate md5sums for each output RDS frame file which is logged to a file for use in data movement between systems over the network. The default compression level for RDS output frames was changed from 6 (six) to 1 (one) for performance reasons. The support for GEO frames was improved in the RDS generation command. The FrVerify utility was enhanced to verify metadata in the frame file against the name of the frame file. The database server was upgraded from DB2 8.1.5 to DB2 8.2.1. This is the first of two releases requested by DASWG in preparation of the astrowatch dry run testing of LIGO software prior to the S5 Science Run.

Summary by API

Control and Monitor

Under the "Test LDAS" tab, a new test has been added. It is the first tab on the page and will execute all the other tests giving a summary of execution status at completion of the final test.

The E11 and S4 time ranges have been added to the time widget.

The way to modify resource variables via cmonClient has been greatly modified. With the new interface, the variables can be sorted by clicking the column heading. Also, resource can be added and deleted via the new interface.

Frame API

The FrameCPP library has been enhanced in several ways. First, it will add a FrHistory structure for any frame it writes.

The FrVerify program has been enhanced to verify the metadata presented in the frame file name against the associated values in the frame file. FrVerify will also display the checksum values (calculated verses read) when a discrepency is found.

Much work has been done to support merging of GEO frames. Unfortunately not all work needed for this has been completed. The createRDS command can now support multiple type fields in its query.

The createRDS command now generates a file of md5sum values. This allows for integrity checking when files are moved.

The default compression level has been changed from 6 to 1 for performance reasons. Also, all commands that allow for frame generation now support compression of the frame data.

diskcachAPI

The resource variable ::CHECK_FOR_MOUNT_PT_CONFLICT has been added to all bypassing of the check for mount point conflicts.

Build process

Using the build-ldas script no longer requires a tested version of gcc to be used. The option flag -warn-unsupported-compiler has been added to allow the use of untested version of gcc.

The build process has been enhanced to properly use the TEXINPUTS environment variable by ignoring if it is set in the user's environment and only use the value defined in the Makefile.

System Testing

System testing has been enhanced by changing all nightly tests to use dataStandAlone command. This allows testing of LDAS without any use of the mpiAPI or wrapperAPI.

Resource file changes

cmonClient
added resource var to exclude old versions from add/delete resource

;## desc=version below which does not support add resource
set ::RESOURCE_VERSION 1.5.70

added resource to control the number of backup copies of resource files
when changes are made via cmonClient
;## desc=max number of bak files for resource changes
set ::RESOURCE_BAK_LEVEL 5

metadataAPI
deleted obsolete resources

set ::DEFAULTMAIL mailto:$::env(LOGNLOGNAME)@ligo.caltech.edu 
;##desc=default job output directory, mod=no 
set ::DEFAULTFILE file:/ 
;## desc=statementbinding, mod=no  
set ::BIND_COUNT 0  
;## desc=loop testing, mod=no  
set ::LOOPTEST 0
;## desc=required variables, mod=no    
lappend ::REQUIRED_VARIABLES DEFAULTMAIL DEFAULTFILE

managerAPI
rearrange some vars so they are not viewable via cmonClient

;## THIS SECTION IS NOT VIEWABLE VIA CMONCLIENT
    
;## initializes queue names - do not modify this!!  
array set ::QUEUE [ list USERS {} COMMAND {} ]
    
;## checks to see if somebody modified the previous line and broke things
lappend ::REQUIRED_VARIABLES QUEUE(USERS)
    
;## name of file that maintains sequence counts between restarts - do not modify!
set ::KEYFILE [ file join seqKEYS ]
    
LD_ASSUME_KERNEL no longer specifies a legacy kernel model
;## desc=env ! mod=no
set ::EXTRA_ENV "LD_PRELOAD=\$libmalloc\$libstdc LD_ASSUME_KERNEL="

LDASapi.rsc
Corrected the case for metaserver part of variable name
;## desc=number of milliseconds defining a ping timeout for specific host
set ::PING_TIME_PANIC_LIMIT_MS_metaserver 2000
added resource to control the number of backup copies of resource files
when changes are made via cmonClient

set ::RESOURCE_BAK_LEVEL 5

LDASmpi.rsc
add the following to specify shell to use to log into nodes
;## desc=use this rsh base command (might need to use ssh).
set ::MPI_RSH_COMMAND /usr/bin/rsh

diskcacheAPI
;## The ::CHECK_FOR_MOUNT_PT_CONFLICT was added initially as a diagnostic
;## tool for PR2753. The conclusion is that looking up of duplicates is
;## not the source of the observed slow down. The default value of 1
;## should be used used unless experimenting with system performance.
;## desc=1 if system should check for mount point conflicts, 0 otherwise
set ::CHECK_FOR_MOUNT_PT_CONFLICT 1

LDCG Software upgrades

Nine third party software packages were upgraded.

The current upgraded packages and thier current rlease number are: cvs 1.11.20, firefox 1.0.4, rsync 2.6.4, lftp 3.1.1, top 3.5.1, FrameL 6.18, ganglia 2.5.7, apache 2.0.53, and tkcvs 7.2. Mozilla has been dropped as a package built as part of the LDCG Software repository.

Other changes

A download link, Download, has been added to the LDAS Software Index on the main ldas web page to obtain various distribution tar balls. This modification supersedes the previous method where the ldas source tarball distribution was made available at the very top of the CVS access page. The current method not only has the latest source distribution, but also the other source and binary distributions provided by LDAS. These go back to release 1.2.0 of LDAS.

DB2 has been upgraded from 8.1.5 to 8.2.1. This has increased the database performance.

Problem Report Summary




Back to LDAS FAQ