Binary Version
Here is the output from "SctRodDaqVersion -l" for the release candidate SctRodDaqRelease3.0:VersionString:SctRodDaq_3_0 MajorVersion: 3 Minor Version: 0 Modifier: 0 Version: 3 BuildSystem: Linux pcei 2.4.18-27.7.cb2 #1 Mon Aug 25 11:23:19 BST 2003 i686 unknown BuildHost: pcei.hep.phy.cam.ac.uk BuildDate: 17:16:13 14 Jul 2004 RodDaq Version: SctRodDaq_3_0 CmtConfig: i686-rh73-gcc32 Dataflow Version: DF-00-05-00 OnlineVersion : online-00-19-01 RootVersion: 3.05/07 GccVersion: 3.2.3
Make sure your versions correspond to those above if you are trying to use the binary version!
New Features
This is a brief list of the main new features since SctRodDaqRelease2.1:- New DSP code - all of the scans should now work. There are some speed increases and general bug fixes.
- Multi-DSP and Multi-ROD now work
- Support for ROD RevE? (RevC? support may be dropped)
- Scalability and performance improvements of Fitting and Analysis. They both now scale to hundreds of modules without using too much RAM.
- New archiving service - much faster and smaller output. See SctRodDaqRelease4 though.
- Many GUI improvements including better database integration, and display of DCS conditions
- Full testing system
- Correctness testing: The analyses have been tested and compared with SCTDAQ automatically. This has greatly improved the correctness and robustness of the analysis/fitting
- Performance and scalability: The full-system has been tested with 384 (virtual) modules. All components are now much more reliable.
- Robustness: Most of the components have been run through valgrind to check for bugs and memory leaks. These components are "clean"
- SctApi: A low-level testing system has allowed much of the logic of the Api to be tested independantly of the hardware
- Real modules: It has been extensively tested with real modules at Cambridge and Oxford, including multi-ROD, multi-DSP
Known Issues for version 3.0
See also SctRodDaqRelease3.0 and SctRodDaqRelease3.01.- The response curve algorithm may incorrectly report that it has removed "2 (or more)" points from the response curve fit (due to the 8fC effect) when it has in fact only removed 1 point
- The response curve algorithm is slightly less aggressive than SCTDAQ at removing points affected by the 8fC effect. This is a pretty small effect tho (1 channel in 10,000 is affected by this).