This file is l2_data_path_support_notes.txt in http://www.pa.msu.edu/hep/d0/ftp/l2/framework/hardware/general/ ------------------------------------------------------------------------------- Dealing with the crates required by the L2 Data Path but dropped from readout 9-Jan-2002 COOR needs to send TCC the following requirements 1) SpTrg #1 wants to Readout Geo Sect # 50, and 100 2) SpTrg #10 wants to Readout Geo Sect # 50, 110, 111, 112, 120 3) The L2 trigger system needs the input from Geo Sect # 110, 111, 112. These crates must receive a L1 Accept every time any of the L1 Specfic Trigger Fires. This set of crates, called the "L2 Data Path", is defined to ensure that the L2 Global always receives the data from all its inputs for all events. TCC needs to program the L1FW Output FOMs so that when SpTrg #1 gets a L1 Accept send L1 Accepts to Geo Sect # 50, 100, AND 110, 111, 112 when SpTrg #10 gets a L1 Accept send L1 Accepts to Geo Sect # 50, 110, 111, 112, 120 That is straightforward, TCC just needs to always add the TCC needs to program the L2FW output FOMs so that when SpTrg #1 gets a L1 Accept and is Accepted by L2 Global the L2FW sends L2 Accepts to Geo Sect # 50, 100 (*) the L2FW sends L2 Rejects to Geo Sect # 110, 111, 112 when SpTrg #1 gets a L1 Accept and is Rejected by L2 Global (not typical) the L2FW sends L2 Accepts to Geo Sect # (none) the L2FW sends L2 Rejects to Geo Sect # 50, 100, 110, 111, 112 when SpTrg #10 gets a L1 Accept and is Accepted by L2 Global the L2FW sends L2 Accepts to Geo Sect # 50, 110, 111, 112, 120 the L2FW sends L2 Rejects to Geo Sect # (none) when SpTrg #10 gets a L1 Accept and is Rejected by L2 Global the L2FW sends L2 Accepts to Geo Sect # (none) the L2FW sends L2 Rejects to Geo Sect # 50, 110, 111, 112, 120 (*) That is the important point. Simplified L2FW diagram: +--------+ +--------+ +--------+ 128 | L1 | 128 .---| L2 | 128 | L2 | 128 -/----| Accept |-/--------+ | Accept |-/------| Accept |---/------ SpTrg| TRMs | SpTrg .--+---| AONMs | SpTrg | FOMs | GeoSect +--------+ | | +--------+ +--------+ | | +--------+ | | +--------+ +--------+ 128 | L2 | 128 | `---| L2 | 128 | L2 | 128 -/----| Answer |-/-----+ | Reject |-/------| Reject |---/------ SpTrg| TRMs | SpTrg `--X--O| AONMs | SpTrg | FOMs | GeoSect +--------+ ^ +--------+ +--------+ | |_Proposed change = ignore these inputs Problem: When SpTrg #1 gets a L1 Accept and is Accepted by the L2 Answer the L2 Reject AONM which feeds the L2 Reject FOM, as it is programmed now, will set its its SpTrg #1 output low. Proposal: The proposal is to change the programming of the L2 Reject AONM so that it asserts its output whenever the SpTrg #1 L1 Accept is asserted (whether L2 Answer is asserted or not). Furthermore, we would ignore the L2 Answer for ALL Specifc Triggers. This corresponds to turning the L2 Reject AONM into a passthru card for the L1 Specific Trigger Fired Mask. We would then program the L2 Reject FOM for Spec Trig #1 to reject GeoSect # 110, 111, 112. In fact we would program it to reject Geo Sect # 50, 100, 110, 111, 112. This is just like the programming of the L1FW Output FOM. ALL Specific Triggers would be programmed like the L1FW Output FOM. e.g. SpTrg #10 would send L2 Rejects to Geo Sect # 50, 110, 111, 112, 120. This sheme will generate additional Geo Sect L2 Reject that will be SUPPRESSED in the SCL Hub End whenever the corresponding Geo Sect L2 Accept is found asserted. We would make no change to the programming of the L2 Accept AONM, which will continue to implement 128x L1 Specific Trigger Fired AND corresponding L2 Answer Asserted. We would program the L2 Accept FOM for Spec Trig #1 to only accept the "truely needed" Geo Sect # 50, 100. ALL Specific Triggers would be programmed in the L2 Accept FOM to only send L2 Accept to the Geo Sect they truely want to readout. e.g. SpTrg #10 would send L2 Accepts to Geo Sect # 50, 110, 111, 112, 120. Case by case: when ONLY SpTrg #1 gets a L1 Accept when SpTrg #1 gets a L1 Accept and is Accepted by L2 Global the L2FW sends L2 Accepts to Geo Sect # 50, 100 the L2FW sends L2 Rejects to Geo Sect # 110, 111, 112 (50, 100, are suppressed) when SpTrg #1 gets a L1 Accept and is Rejected by L2 Global (not typical) the L2FW sends L2 Accepts to Geo Sect # (none) the L2FW sends L2 Rejects to Geo Sect # 50, 100, 110, 111, 112 when ONLY SpTrg #10 gets a L1 Accept when SpTrg #10 gets a L1 Accept and is Accepted by L2 Global the L2FW sends L2 Accepts to Geo Sect # 50, 110, 111, 112, 120 the L2FW sends L2 Rejects to Geo Sect # (none) (50,110,111,112,120 suppressed) when SpTrg #10 gets a L1 Accept and is Rejected by L2 Global the L2FW sends L2 Accepts to Geo Sect # (none) the L2FW sends L2 Rejects to Geo Sect # 50, 110, 111, 112, 120 when BOTH SpTrg #1 and #10 get a L1 Accept when SpTrg #1 AND #10 get L1 Accept and SpTrg #1 is Accepted, #10 Accepted the L2FW sends L2 Accepts to Geo Sect # 50, 100, 110, 111, 112, 120 the L2FW sends L2 Rejects to Geo Sect # (none) (50,100,110,111,112,120 suppressed) when SpTrg #1 AND #10 get L1 Accept and SpTrg #1 is Accepted, #10 Rejected the L2FW sends L2 Accepts to Geo Sect # 50, 100 the L2FW sends L2 Rejects to Geo Sect # 110, 111, 112, 120 (50, 100 are suppressed) when SpTrg #1 AND #10 get L1 Accept and SpTrg #1 is Rejected, #10 Accepted the L2FW sends L2 Accepts to Geo Sect # 50, 110, 111, 112, 120 the L2FW sends L2 Rejects to Geo Sect # 100 (50,110,111,112,120 suppressed) when SpTrg #1 AND #10 get L1 Accept and SpTrg #1 is Rejected, #10 Rejected the L2FW sends L2 Accepts to Geo Sect # (none) the L2FW sends L2 Rejects to Geo Sect # 50, 100, 110, 111, 112, 120