Subject: Re: Draft of changes to protocols.... From: Hal Evans Date: Wed, 26 Apr 2006 15:03:11 -0400 To: mverzocc@fnal.gov CC: Sabine Lammers , Hal Evans Hi Marco, I've gone through your COOR changes proposal at: http://www-d0.fnal.gov/~mverzocc/l1cal.txt As far as I can tell, you've covered all the changes that will need to be made. (Thanks very much for going through this so carefully!) I only have a couple of questions/comments, which I include below labeled by their item number in your list. 3.a) General EM, Jet, Tau syntax i) Since we're asking COOR to make checks on the validity of the parameters, should we also include a check that "maxeta" is consistent with what is coded in the firmware? ii) The proposal that you make for the new "lowthres" parameter is a good one. It could perhaps be made more straightforward by using it as an optional parameter: lowthres="O". This would mean: - TCC would contain default values for the parameter (3 and 5 GeV?) - COOR would have to check that "lowthres = something" is only specified once per object (jet,em) Do you think that this scheme would make it simpler to program COOR, or is it just an unecessary complication? 3.e) ICR flags i) I believe that the firmware ended up with 3 of these flags, as you have indicated. But we need to double-check the latest version of the code to make sure. Sabine: could you check this (or point me to where the current code lives)? ii) Is the motivation for including these ICR enable flags in COOR to be able to track them more easily in the early stages of testing? I would imagine that we would make the final choice of whether to use the ICR or not for each class rather quickly and then stick with that choice for the rest of D0. If that is the case, it might be simpler to just leave the setting of these parameters up to TCC? New item) reference set for L2 masks I'm assuming that this will be set in TCC (or is it hard-coded in the firmware?). Is there any reason/possibility to have it known to COOR? Cheers - Hal Marco Verzocchi wrote: > Hi > I have prepared a draft of the changes to the COOR > resource programming and to the XML syntax which > has all the changes except: > * 2 new acoplanarity terms > * assignment of framework bits. > > This is I believe one thing which is urgently needed and > which was being discussed at the L1Cal meeting today. > I am not sending around to Philippe and Scott immediately > because I would prefer that somebody else (Sabine) has > a look at it and checks for missing stuff or things which > are not clear. > > The format is changes relative to the documents which > Philippe and Scott have prepared in the past and it may not > be entirely clear for everybody. > > One thing which should be discussed (in particular with > Scott) is whether we want to have everything fully configurable > from COOR (that's what my draft assumes) or whether in > some cases we are just happy with a configuration file > read by TCC after a reset or during startup (this will > simplify things a lot for COOR). > > My draft is at http://www-d0.fnal.gov/~mverzocc/l1cal.txt > In a few cases I have not fully specified the data format, > because I don't know how you (i.e. Mike + Philippe) want > this data (ex: tau ratio 8 bits between 0 and 1.....)... > > Cheers > Marco > > PS I would like to converge on these modifications by the > end of the week, because I need to have Scott to do the > relevant changes in COOR before we put triggers in > the database..... > -- ^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v Hal Evans hgevans@indiana.edu http://hep.physics.indiana.edu/~hgevans/ Tel: (812)856-3828 Fax: (812)855-5533 253 Swain Hall West Indiana University 727 E. Third St. Bloomington, IN 47405 v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^