You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 46 Next »

LAT Trigger

Communications

Mailing list:

Post to the LAT trigger mailing list at triggerlist@glast.stanford.edu
which also has an Archive. You can subscribe to the list through the GLAST Mailing list page.

Phone numbers, E-mails

Trigger meetings

How to post material to trigger meetings and mailing list

Commissioning and Testing

  • Trigger Scheduler and Context:

The following table gives a representation of the Trigger Scheduler table and TAM Context information for the LAT muon runs to be taken during Commissioning.  Those muon runs are designated by test cases LAT-70x (flight configuration on ground) and LAT-71x (muon calibration).  The scheduler is shown in a form compatible with the online tool to generate trigger configurations, where the trigger engines are specified in hierarchical order.

 Engine

 external

solicited

periodic 

 CNO

CAL-HI 

 CAL-LO

TKR

 ROI

Zero-supp 

 Ranges

 Prescale

 Marker

 Inhibit

Avg Rate (Hz)

 0

 1

 x

 x

 x

 x

 x

 x

 x 

 enabled

 1-rng 

 0

 0

 no

0

 1

 0

 x

 x

 x

 x

 x

 0

 1

 enabled

 1-rng

 0

 0

 no

0

 2

 0

 1

 x

 x

 x

 x

 x

 x

 enabled

 1-rng

 0

 0

 no

0

 3

 0

 0

 1

 x

 x

 x

 x

 x

 disabled

 4-rng

 0

 0

 no

2

 4

 0

 0

 0

 1

 x

 1

 1

 1

 enabled

 4-rng

 0

 0

 no

200

 5

 0

 0

 0

 1

 x

 x

 x

 x

 enabled

 1-rng

255 

 0

 no

5

 6

 0

 0

 0

 0

 1

 x

 x

 x

 enabled

 1-rng

 0

 0

 no

100

 7

 0

 0

 0

 0

 0

 x

 1

 0

 enabled

 1-rng

 0

 0

 no

1500

 8

 0

 0

 0

 0

 0

 1

 0

 0

 enabled

 1-rng

 0

 0

 no

400

 9

 0

 0

 0

 0

 0

 1

 1

 1

 enabled

 1-rng

 0

 0

 no

700

 10

 0

 0

 0

 0

 0

 0

 1

 1

 enabled

 1-rng

49 

 0

 no

100

 11

 0

 0

 0

 0

 0

 0

 0

 0

 enabled

 1-rng

 0

 0

 no

0

 12-14

 

 

 

 

 

 

 

 

 

 

 

 0

 inhibit

 

 15

 

 

 

 

 

 

 

 

 

 

 

 5

 no

 

In this table, 1 = asserted, 0 = not asserted, and x = "don't care".  The Contrigurator evaluates the rule for engine 0 first, and given the rule above assigns 128 combinations of trigger conditions to engine 0.  It then evaluates the rule for engine 1, and from the remaining 128 unassigned combinations, it assigns the 32 combinations that are consistent with the rule to engine 1.  This continues on through engine 11, where the last of the 256 possible combinations -- in this case, no conditions asserted -- is mapped to engine 11.





Reviews & Presentations

Specifications and Technical Design Information


LAT document search
The JIRA software issue tracking system
I&T links: Online, facilities and integration, Instrument Analysis Group
Subsystems: Traker ELPDR, CAL Peer review, ACD electronics, Elex Hardware, Flight software docs
Building 33 cameras, Building 33 phones

  • No labels