Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Luter 345 Experiments
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Decoding of CODA Data and Creation of ROOT Output
(section)
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Get shortened URL
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===The word make-up=== The run count word simply recalls the run number of the data. This is used for labeling purposes. =====ADC Header Word===== [[File:QDC_Header_Word.png|thumb|none|900px||QDC Header Word]] =====TDC Header Word===== [[File:TDC_Header_Word.png|thumb|none|900px||TDC Header Word]] Starting from the left, the first five bits are the geographical location. We should always expect 11111 for this part because our location is constant. The next three bits denote the kind of word. A header word will read 010 and a data word will read 000. For the header word, the next eight bits denote the crate being used. Both the TDC and ADC are operating out of crate zero, so those should be expected to be all 0βs as well. These are followed by 2 constant zero bits. And finally there are five bits that tell how many data words follow the header word. The rest of the bits have no meaning (should always be 0βs). =====ADC Data Word===== [[File:QDC_Data_Word.png|thumb|none|900px|ADC Data Word]] =====TDC Data Word===== [[File:TDC_Data_Word.png|thumb|none|900px|TDC Data Word]] For a data word, the geo bits are the same. The three bits should read 000 to mean it is a data word. There will be three unimportant bits (again 0βs), followed by five channel bits. There will be one unimportant bit, and then the ADC will have a second unimportant bit, but the TDC will have a bit to determine valid data. If that valid bit is a 1 then the data is good. For both machines, there will be bits to determine whether the data is underthreshold or in overflow in that order. For our purposes, these bits should always be 0βs meaning that it is not underthreshold nor is it in overflow condition. The last 12 bits is the data itself. The closing word is simply a constant telling the analyzer to stop parsing when it reads this word. ====Example==== Here is the word from the previous sections, to break it down in these meanings: 11111 000 000 0000 001 00 000010000001 The first five bits are 11111, as expected. The next three are 000, meaning it is a data word. Three unimportant bits. It is coming from channel zero. Three unimportant bits. Not it underthreshold nor overflow. And then the last twelve bits are the data. Given the number of bits, it is usual (and useful) to express these words in hexadecimal format, or in the case of this example word: 0xF80084081
Summary:
Please note that all contributions to Luter 345 Experiments may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Luter 345 Experiments:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)