Difference between revisions of "TODO"
Rfarinelli (talk | contribs) (Tag: Visual edit) |
Rfarinelli (talk | contribs) (→List of bug and problems) (Tag: Visual edit) |
||
Line 12: | Line 12: | ||
* Only 33% of the hits has a cluster on both sides of the L2, while in principle it should be 100% --> problem due to ROC? | * Only 33% of the hits has a cluster on both sides of the L2, while in principle it should be 100% --> problem due to ROC? | ||
− | + | * FEB_label 2 and 21 dont have calibration. Right now we are using random calibration for EFINE and TFINE | |
− | * | ||
− | |||
− | |||
− | |||
− | |||
== Possible solutions to be confirmed == | == Possible solutions to be confirmed == | ||
Line 27: | Line 22: | ||
* FEB_label = 36, chip 2, channel 3 | * FEB_label = 36, chip 2, channel 3 | ||
* FEB_label = 43, chip 2, channel 45 | * FEB_label = 43, chip 2, channel 45 | ||
+ | |||
+ | The following channel are not used in GRAAL: (chip,channel) --> (43,3), (46,26), (73,3), (87,45) and they are different from the one shown above | ||
3/4 of these channels (ch. 3 and 45) are located on the edge of the anode-FEB connector (see [[L2_FEB_pinout]]). | 3/4 of these channels (ch. 3 and 45) are located on the edge of the anode-FEB connector (see [[L2_FEB_pinout]]). | ||
Line 33: | Line 30: | ||
TO-DO: | TO-DO: | ||
* Check and confirm that removing these channels the very high charge noise disappears (for all runs) | * Check and confirm that removing these channels the very high charge noise disappears (for all runs) | ||
− | * Check the FEB-anode connection | + | * Check the FEB-anode connection -> DONE |
* Check the position of these FEBs --> are they close to some potential noise source? | * Check the position of these FEBs --> are they close to some potential noise source? | ||
Line 41: | Line 38: | ||
* The reconstruction is too slow with event.C -> lSolved by changing the arrays to vectors. | * The reconstruction is too slow with event.C -> lSolved by changing the arrays to vectors. | ||
+ | * FEB from 0 to 15 are noisy at channel 62 -> removed the channel and use as new TP channel | ||
+ | * Peaking background on FEB=6 && channel = 62 --> removed the channel | ||
==== No signal from FEB 2 and 30 ==== | ==== No signal from FEB 2 and 30 ==== |
Revision as of 21:40, 23 June 2019
See also:
https://wiki.fe.infn.it/besiii/index.php/Data_decode_TODO
https://wiki.fe.infn.it/besiii/index.php/GUFI_TODO
Contents
List of bug and problems[edit | edit source]
- The radius used on the L2 do not correspond to the real one
- µTPC disabled up to now
- Only 33% of the hits has a cluster on both sides of the L2, while in principle it should be 100% --> problem due to ROC?
- FEB_label 2 and 21 dont have calibration. Right now we are using random calibration for EFINE and TFINE
Possible solutions to be confirmed[edit | edit source]
The charge measured with random trigger is above 10fC, up to 50 fC[edit | edit source]
This is due to few channels with very high noise:
- FEB_label = 21, chip 2, channel 3
- FEB_label = 23, chip 1, channel 26
- FEB_label = 36, chip 2, channel 3
- FEB_label = 43, chip 2, channel 45
The following channel are not used in GRAAL: (chip,channel) --> (43,3), (46,26), (73,3), (87,45) and they are different from the one shown above
3/4 of these channels (ch. 3 and 45) are located on the edge of the anode-FEB connector (see L2_FEB_pinout).
TO-DO:
- Check and confirm that removing these channels the very high charge noise disappears (for all runs)
- Check the FEB-anode connection -> DONE
- Check the position of these FEBs --> are they close to some potential noise source?
Solved[edit | edit source]
- Charge decrease as the threshold increases -> due to some error in setting the threshold. Now if the thr_sigma*n_sigma < 1, threshold is increased by 1.
- The reconstruction is too slow with event.C -> lSolved by changing the arrays to vectors.
- FEB from 0 to 15 are noisy at channel 62 -> removed the channel and use as new TP channel
- Peaking background on FEB=6 && channel = 62 --> removed the channel
No signal from FEB 2 and 30[edit | edit source]
This is due to missing calibration files (raw data should be present):
- FEB 30 (calibration files available) has been restored
- FEB 2 (calibration files not available) will be provided soon with a temporary mock-up calibration (based on TP scan performed with GUFI)