Last Updated on Thursday, November 30, 2000 at 10:41:56.
The 'DAC_setting' parameter is inside the event header parameter list.
I have written the file PhoRaw000065s000.root with FASTBUS data. It was
some problems using current TPhPlastic streamer function. To write the
file I used the TPhRawData class which contains the raw data
array from the FASTBUS, the structure of this array is the same as
FBPackedHits array in TPhAbsRawHitFBc0.
This file should be used to debug TPhAbsRawHitFBc0.
The file had been moved to HPSS.
/Andrei.
The DAQ server now support several TCP connection to the same port (7002) for
event distribution.
/Andrei
To TOF,Trigger:
Run 123 contains FASTBUS data.
Format: TPhRAwData
Name: TOF
Readout sequence: ADC[7],TDC[5]
Gate: internal
File was temporary copied to phobosx:/data/7/tempdata.
/Andrei
From now on, starting from run 139, the event header contains event
building time stamp (time when the event was build in phatdaq) with
the microsecond resolution.
The header.GetDate() function returns time in seconds since
00:00 Universal Coordinated Time, January 1, 1970.
The header.GetTime() returns time in nanoseconds. See man pages for
clock_gettime() POSIX function.
There is no time stamp for event detection (time when event was detected
by trigger electronics).
/Andrei
The pedestal files created after today's morning (run140) failed to
process. The reason is that bunches of events got frozen: they have
exactly the same data for several events (10 to 50 as seen by yes).
The same structure is with pedestal data taken from the socket.
The SICOSM and SICAL looks OK.
There possible some format error in the first couple events in the run.
E.g. too long event length, events with the same event number etc.
It was always like this before. The general cure is to skip first 10
events of the run. We are working to fix it.
/Andrei
Trigger counters have been added to the DAQ event.
They are in the TPRawData class name "TRIG", this object contains 16
32-bit counters, they can be extracted using GetArray function (be
careful with byte swapping). The following channels are hooked up:
[0] - A2A. PN-PP coincidence
[1] - B12.16. RHIC request. (0-120usec after injection)
[2] - A1A. PN
[3] - A1B. PP
[4] - C1.1. Gate to Trigger ADC (for debugging). Disconnected on July 28.
[5] - C10.C L1 to Silicon (for debugging)
[6] - A3A. PN+PP
[7] - A3B. Cosmic Silicon, later on 07/19 I noticed that it was (PN+PP)*RHIC
[8] - A10B. CC - crossing clock 12 usec. Applied 07/20, run 805.
Starting from the run 184, TPhRawData object 'TOF' had been renamed to
'Plastic'. This was request from Nigel and Mike. The current event
structure is as follows:
>TPhSubEventArray Name: event_2_656
TPhRawHitFECn0Eng99 Name:FEC_1
TPhRawHitFECn0Eng99 Name:FEC_2
TPhRawData Name:Plastic
TPhRawData Name:Trig
An example macro to read this events from a file (or a socket) and make
simple histograms is fatalysis.C, it is in repository.
/Andrei
The sync signal is set every 10 sec and reset after event readout.
The trigger mask can be obtained using TPhEventHeader::GetTriggerMask() function.
Some time between 6/18 and 7/02 the format of the DAC_setting parameter was mistakenly changed toi hex format. It is returned back do decimal on 7/08
Fastbus Busy is ORed with the main Busy. Fastbus readout = 3-4 msec. The Silicon readout = 2msec
The trigger is (PN+PP)*RHIC + (ZDCP+ZDCN), FASTBUS BUSY is ORed with the main BUSY.
TDC[4]-paddles,
FASTBUS readout: TDC[5]-ZDC, ADC[6]-paddles, ADC[7]-ZDC, TDC[16]-TOF, ADC[25]-TOF
New scaler channel hooked up:
[8] - A10B. CC - crossing clock 12 usec. Applied 07/20, run 805.
Found that TrigBit[3] was set not from B3B (PN*PP*CC*~RHIC) gate but A3B (PN+PP). Don't
know when this mistake occured.
The reset of the TrigBit[3] comes at the and of main 'Busy'. Previously it was at the end
of 'Busy MDB'.
New FEC no. 3 is added. The total event size became 27+ KB. The socket limit was changed to 28 KB. If it is 32 KB - the Silicon stop working.
Block mode for Fastbus is working, The trigBit setting is as follows:
TrigBit[3] - B1B gate, (PN*PP*CC*~RHIC)
TrigBit[2] - Silicon Cosmic
The delayed trigger signals are connected to the TDC16 channels 32-47. These signals should be used instead of old trigger bits since they carry more information and are generated in more correct way.
Keep in mind that all TDC are in autorange mode:
in the range 0-100 ns the resolution is 25 ps
in the range 100-800 ns the resolution is 200 ns.
All trigger signals on TDC16[32:48] have been delayed relative to the main trigger by 564 ns by 300 feet twisted pair cable. To be registered properly the signals going to this cable should be longer than 50ns. The following signals are connected and checked:
Autorange is disabled. New resolution is 200 ps. It will be kept like this until Phat is modified to take care about range bit (bit23) in the data word.
The long awaited TrigBits are implemented. Those are bits 16-30 in the trigger mask in
event header. They correspond to the Trigger TDC16[32:46] . The bit is set when
corresponding channel in TDC has non-overflowed value. That means that there was signal
detected on this channel in the time interval between 564ns before the main trigger and
236ns after it.
Finally:
Trigger scalers connection:
[0] - A2A. PN-PP coincidence
[1] - B12.16. RHIC request. (0-120usec after injection)
[2] - A1A. PN
[3] - A1B. PP
[4] - B2C. ZDC
[5] - A4D. SPEC
[6] - A3A. PN+PP
[7] - B1C. ~PN*PP*CC
[8] - A10B. CC
[9] - B1D. ~PN*PP*SPEC*CC
[10] - B12.15. Yellow beam request. Added 08/09/99 08:38 During Run 1299