70 likes | 156 Views
PULSAR Specifications for RECES and ISOLIST. Zeroth order start on “exploring” how a PULSAR scheme might look for isolation trigger and RECES Philosophy start simple add complication if necessary Only at the first step above. ISOLIST. List card performs two functions
E N D
PULSAR Specifications for RECES and ISOLIST • Zeroth order start on “exploring” how a PULSAR scheme might look for isolation trigger and RECES • Philosophy • start simple • add complication if necessary • Only at the first step above
ISOLIST • List card performs two functions • collect partial sums from the DCAS crates (ISOPick cards) • construct 5 sums from the partial sums corresponding to energy surrounding a cluster (excluding “potential leakage” in adjacent tower)
ISOLIST • Receives partial sums and adds from 6 IsoPicks • PULSAR could simply pass these on (allow the CPU at the end to add them up) • Receives IsoClique “end of buffer” signal • Pulsar needs to end event/buffer at this point since no more seeds will come for this event
RECES • Current scheme involves request vs phi/buffer from alpha • 48 32 bit words simplest thing would be to pack them all off to the CPU
RECES • The data from the SMXR->RECES • threshold exceeded for two thresholds for 4 wire sums for two Z ranges per wedge (sums over 4 time buckets) • two bits of buffer • Fixed size should make packaging and shipping data on simple • zero suppression not meaningful
To Do • First order strategy - send all the data on • variable size (number of clusters) makes the IsoList more (probably not too) difficult • Need to work out in detail • but no obvious reason to worry