LATC parameter files for MOOT

LATC parameters for MOOT

The table below shows one possible partitioning of LATC-destined configuration information. The goal is to minimize the number of parameters subject to the following constraints:

The information for any single parameter must have the same destination. To start, assume the destinations are just the LATC components: GEM, AEM, ARC, AFE, TEM, TIC, CCC, CRC, CFE, TCC, TRC, TFE, SPT, TDC, DFT). However, if the output for one of these is likely to be very large and also not particularly static over time, might choose to further divide it. For example, TFE might be subdivided by tower. In this case, any parameter with destination TFE would be converted to 16 new parameters, one per tower.
Information for a single parameter should be stable or, if subject to change, changes for all parts should occur on the same timescale.
Information for a single parameter should be managed by a single person or group (unless the information is very stable, in which case it might not matter).

PHA threshold registers

Name	Delegate	Destination	Reqd?	How static	Registers (à la lrd); other remarks
TKR tack delay	Timing	TEM	no	very	tkr_trgseq,tack_delay field
trg_align	Timing	TCC	no	very	tcc_trg_align register
CAL tack delay	Timing	TEM	no	very	cal_trgseq, tack_delay field
CRC delays	Timing	CRC	no	very	delay_1, _2, _3
cal_align	Timing	CCC	no	very	CCC trg_alignment register
ACD timing	Timing	AEM	yes	very	AEM trgseq
Timing defaults	Timing	DFT	yes	very	all from non-default Timing parameters above
Regions Of Interest	Trigger	GEM	yes	probably	ROI registers
window enable	Trigger	GEM	yes	probably	WIN part of GEM
trigger engines	Trigger	GEM	yes	probably	TAM engine registers, SCH registers
trigger enables	Trigger	GEM	yes	probably	Input enable registers (TIE)
Freeboard masking	ACD	AEM	yes	normally static	data_mask field in aem_configuration register
pha, veto masking	ACD	ARC	no	normally static	pha_enable and veto_enable
lo thresholds	ACD	AFE	no	?	veto dac and veto vernier register?
hi (CNO) thresholds	ACD	AFE	no	?	hld_dac registers?
data thresholds	ACD	ARC	no	relatively changeable
Operating bias voltage	ACD	AFE	no	very	AFE bias DAC registers
RC trimming	ACD	ARC	no	normally static	max PHA enable register
ACD defaults	ACD	DFT	yes	very	all of above for other parameters belonging to ACD delegate
Cal TEM data masks	CAL	TEM	no	mostly	TEM data masking registers
Cal TEM trigger masks	CAL	TIC	no	mostly	cal input mask registers
CCC masks	CAL	CCC	no	?	CCC layer mask registers; controller ouptu enable field of config. register
CFE enables	CAL	CFE	no	?	enables in CFE config 1 and config 0. Maybe also include other config 0 fields which have to do with range selection.
FIFO depths	CAL	CCC	no	very	CCC configuration register fifo fields (3)
thresholds	CAL	CFE	no	?	CFE registers FLE_DAC, FHE_DAC, LOG_ACPT, RNG_ULD_DAC
bias voltages	CAL	TIC	no	very	TIC cal bias dac
calorimeter defaults	CAL	DFT	yes	very	all of above for other parameters belonging to CAL delegate
trigger masks	TKR	TIC	no	?	TIC layer enables and output masks
TKR TEM data exceptional	TKR	TEM	no	mostly	TEM data masking registers
TCC masks	TKR	TCC	no	?	Input mask register, config register (output_enable field; maybe also cable_length field)
TFE masks	TKR	TFE	no	no	data_mask, trg_enable
splits	TKR	SPT	no	?	low, high registers
FIFO depths	TKR	TCC	no	very	Config register, fifo fields (3)
thresholds	TKR	TDC	no	?	tfe_dac, threshold field
bias voltages	TKR	TIC	no	very	tkr_bias_dac register
RC trimming	TKR	TRC	no	?	csr fields size_write_en, size
Tracker defaults	TKR	DFT	yes	very	all of above for other parameters belonging to TKR delegate

Notes

The only delegates concerned with LATC are Timing, Trigger, ACD, CAL and TKR. Furthermore, almost all their parameters are input to LATC; the rest (not in the table) go to PIG. See the xml delegate description for all parameters.

Parameters for most of the delegates are organized as a list, each member of which handles exceptional values, followed by a single parameter for all defaults. The parameter for the defaults is always required (Reqd is 'yes'); a parameter for exceptional values may not be.

All the separate parameters with destination GEM might not be necessary. If all the information is indeed static they could be combined into a single parameter.

There are about 40 parameters in the above table, so, using this scheme, there would be that many "precursor files" to be managed in order to create FSW inputs. However, about half of them are likely to be stable. Of these, several may even be empty of real content (no exceptional values in the category).

Initial draft: 8 September 2005
Add color coding: 23 August 2006
Last revised:

J. Bogart