----------------------
SctRodDaq Release 2.01
----------------------


This release contains all the core functionality needed by macro
assembly.  There are still some notable goodies to come, but this
will do characterization and so on.

See the changelog file for a list of features and changes.

If you have the source release, please see BUILD
If you have the binary release or you have built the source release,
move onto INSTALL
Then read the rest of this file.

-----------------------------
Modifying configuration files
-----------------------------

To get the test system running, you need to go to the directory:
$SCT_DAQ_ROOT/installed/config/databases
and copy Hardware_template.data.xml to Hardware.data.xml
and modify it.  You need to change the "Name" fields to the machine
names (not localhost).  You also need to make sure the "BinaryTag"
field is set to the correct CMTCONFIG string for you machine - either
"i686-rh73-gcc292" or "i686-rh73-gcc32" depending on your compiler. 
(Note these are the only supported versions).

To get anything more complex running, you need to have DCS/PVSS set up
correctly.  You should then use the partition file
$SCT_DAQ_ROOT/installed/config/databases/SCT.data.xml modifying if
necessary.

There is also the partition configuration file 
$SCT_DAQ_ROOT/installed/config/databases/SCT_nodcs.data.xml which
is useful if you have modules but no DCS.  It is a copy of 
SCT.data.xml but with the DCS stuff removed.

You will also need to generate a configuration file for your RODs -
look at the examples in $SCT_DAQ_ROOT/installed/config/rods


-------
Running
-------

Here are some quick notes on running the software.
If you have set everything up correctly and are just going to use the
test system, then you should be able to make everything go by running
the script "start".  After a while the IGUI interface will appear
and so will another window which is the main interface (SctGui).

First use IGUI to boot the system and bring it up to the running state.
 You may wish to change the MRS defaults to see more of what is going
on using the MRS tab.  Then switch to our GUI.  First, configure it
from the Display->Configuration menu.  You should then be able to use
the SCTDAQExcerciser from the Tests menu if you are using the
SCT_test.data.xml configuration file or using one of the other choices
on that menu if you're using SCT.data.xml and have real hardware.
Hopefully something will happen.  We are working on proper
documentation for the user interface.

There are many programs in the release, but one very useful one is
"SctRodDaqVersion" which prints out lots of useful information (use "-h"
as an argument to get help on using it).  This information is also
available in the about box in the GUI.

------------
Known Issues
------------

Here is a list of known issues with this release.  For a more up-to-date 
list, please see our website at http://www.hep.phy.cam.ac.uk/~atlasdaq
and in particular the Wiki linked there.  You are strongly encouraged to
use the Wiki and add/modify as you feel appropriate.

    * There is a DSP bug that means that all the channels are read-out when charge is being injected. This means that any scan which injects charge actually returns (scan + 3*0 fC response). For this reason we have truncated threshold scans at 90mV. However, it still cause huge numbers of defects and problems for many tests.

    * The modules need to have a hard reset after the pipeline test

    * The full bypass test has some issues (we're working on this)

    * Due to lack of PMG synchronisation, sometimes not all the processes are ready when the system is in the "Loaded" state. This lasts for only a few seconds.

    * The archiving is still very slow when there are lots of defects. 
    
    

Good Luck!
The SctRodDaq Developers
