Skip to Content.
Sympa Menu

usatlas-hllhc-l2deputymgmt-nsf-l - Re: [Usatlas-hllhc-l2deputymgmt-nsf-l] Prioritized scope contingency/opportunity

usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov

Subject: U.S. ATLAS HL-LHC Upgrade Level 2 and Deputies-NSF only Management Mailing List

List archive

Chronological Thread  
  • From: "Begel, Michael" <begel AT bnl.gov>
  • To: "Lipeles, Elliot" <lipeles AT hep.upenn.edu>
  • Cc: "Usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov" <Usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov>
  • Subject: Re: [Usatlas-hllhc-l2deputymgmt-nsf-l] Prioritized scope contingency/opportunity
  • Date: Tue, 23 Jul 2019 17:36:23 +0000

Thanks! And there would be additional hardware for the Global Trigger and for FELIX which I have no idea how it would be covered internationally.

We'd also need the RoI firmware for Global Trigger.

Michael Begel


On Tue, Jul 23, 2019 at 1:01 PM Elliot Lipeles <lipeles AT hep.upenn.edu> wrote:
Hi Hal and Michael,

I don't recall making up the number for L1Track... and more importantly what do we assume it includes...

I would guess that it should be related to the NSF scope
-- L1Track Hardware + firmware 
    -- ~50% TPs --> ~$1M (assuming ~1/3 of AMTPs moved to L1Track, because rHTT not needed with L1Track)
    -- firmware???  - no model here but maybe half of the planned firmware for the baseline --> $1M
-- Global algorithm framework modifications
    -- again no model, but maybe half the firmware frame work labor $700k
-- Global algorithms
    -- this could be part of the existing algorithm opportunity.

Of course, on the DoE side there would be additional work:
  -- very different MUX firmware
  -- low-level firmware in GEP
  -- CTP interface firmware

Elliot


On Tue, Jul 23, 2019 at 11:49 AM Hal Evans <hgevans AT indiana.edu> wrote:

Thanks Michael,  Comments below.  -  Hal

On 7/23/19 11:38 AM, Begel, Michael wrote:
There are two priority 3's for Opportunity and no priority 4.
Will fix this...

Where did the $2M estimate for L1Track come from? This seems quite low compared to my expectations.
Elliot should comment here. I must admit that I've forgotten.

The prioritization for the NSW trigger processor might need comment since the reason sounds more important than some of the others.
Yes: there are a couple of issues here that reduce the priority. One is that this needs to be decided relatively early. Also, if it's not available on day one, L0Muon as a whole does not go down in flames.

Does the second HTT Scope Contingency include the impact of the first one? Same comment for the Muon ones.
No - what is quoted is the additional savings that would be realized after the first option is exercised.

Michael Begel


On Tue, Jul 23, 2019 at 11:22 AM Hal Evans <hgevans AT indiana.edu> wrote:
Dear L2Ms/DL2Ms,

Please find attached an updated version of the scope
contingency/opportunity spreadsheet. After reading over the
recommendations from PDR about this topic, we realized that we have been
asked to provide a prioritization for our contingency/opportunity items.
Clearly, any prioritization that we apply now will change in the future
as the realities of the situation at ATLAS evolve. So you should not
take this too seriously. However, since we're required to do it, here's
an attempt.

The basic criteria we applied in producing the prioritization are:

1. Scope Contingency: give highest priority (i.e. these options would be
exercised first) to those items that could conceivably be recovered later.

2. Scope Opportunity: give highest priority to those items that will
need to be done, but for which no plan currently exists.

3. Exact rankings within those criteria are largely random, and in any
case these ranking do not indicate how we would actually cut/add scope
should the need/opportunity arise. That will depend on the exact
situation at the time the decision needs to be made.

Let me know if you have any questions or comments. I'll post the new
version tomorrow unless there are strong objections.

Others in the PO should chime in if there's anything important I've left
out.

Cheers  -  Hal

--
^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 AT indiana.edu
            https://urldefense.proofpoint.com/v2/url?u=http-3A__pages.iu.edu_-7Ehgevans_&d=DwIDaQ&c=aTOVZmpUfPKZuaG9NO7J7Mh6imZbfhL47t9CpZ-pCOw&r=Z0wuTxQYnTTMlYma4lGZlO3skeCGVBrGGurYkWbhJsJuG5HaY82rmCNSdFOV7C4Z&m=F71kkH52FGCfYiLTi0jcjV7qzsasxBh1kXBWBtnBmOw&s=pgLOLjYmoJEQsp97RmbHu9H4Y487H4U3JOJAnzm0_L8&e=
  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^

_______________________________________________
Usatlas-hllhc-l2deputymgmt-nsf-l mailing list
Usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/usatlas-hllhc-l2deputymgmt-nsf-l
-- 
^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 AT indiana.edu
           http://pages.iu.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^
_______________________________________________
Usatlas-hllhc-l2deputymgmt-nsf-l mailing list
Usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/usatlas-hllhc-l2deputymgmt-nsf-l



Archive powered by MHonArc 2.6.24.

Top of Page