From - Tue Jan 30 17:49:36 2001
To: Ashmanskas Bill <ashmansk@hep.uchicago.edu>,
        Punzi Giovanni <giovanni.punzi@pi.infn.it>
From: Stefano Belforte <stefano.belforte@ts.infn.it>
Subject: db and cold start and SVT config

A new task for db/cold_start/high level config.

Actually a clarification of existing things.
About the AMS microcode.

I have put in my test version of svtvme a modified
ams cold start routint (that I believe to work,
but not tested with data flow yet)
that generates AMS ucode on the fly.
A lot of abbellishment is still to do like
all the checksum stuff (we  may need to encapsulate
some of the functions in smart_write_from_file into
callable form so that can be reused) but the basic
I think is stable.
The think I write about is the input for the
various possible confdigurations.
At present I added yet another file in svt_config
area, namely ams_w06.AMS-UCODE similar to the REGS
file. You may look at it, should be self-explaining:
belforte@b0dap30/~#37> cat
/cdf/code-common/cdfonline/svt_config/ams_w06.AMS-UCODE
VERSION 1
IGNOREHOLD 1
IGNOREROADLIMIT 1
ADD5OVER6 1

I imagine 1 to mean true, 0 to mean false. I will add
comments (// should be supported as I stole Bill's code).
The present idea is that if a microcode map is found,
cold start laods the map, otherwise use the -USEQ file
to decided which ucode to generate. THis can easily
be removed once we feel confident.

For you is the task to incorporate the information
now in AMS-UCODE file into the DB/metakey/... and
into the simulation configuration (hold is irrelevant
for simulation, but raod limit and 4/5 need to
be known) and I do not know if and in which other
places (do pattern etc. need to know about 4/4 vs.
4/5 ?).
Also you may want to take this chance to advice on
different file name/format as you find fit.