Difference: CriteriaToProofTheFEE (1 vs. 6)

Revision 6
16 Feb 2011 - Main.JoernWuestenfeld
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"
Here it follows a list of steps which have to be performed in order to poof the electronics on the MDC:
Line: 14 to 14
 

4) In the FEETestLogBook keep track of the problematic MB or OEPB and the files acquired.
Changed:
<
<
4) Test the FEE with HV on??
>
>
4) Test the FEE with HV on??
  • Make sure counting gas is in the chamber!!
 

5) Data taking with cosmics/pulser in order to have a cross check with "real data"??
Revision 5
11 Feb 2011 - Main.AttilioTarantola
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"
Here it follows a list of steps which have to be performed in order to poof the electronics on the MDC:
Changed:
<
<
1) Acquire a file (.hld) as described in OEPReadoutTest and check if all MBs deliver data (noise data).
>
>
1) Acquire a file (.hld) and make its analysis as described in OEPReadoutTest and check if all MBs deliver data (noise data). Open a TBrowser in ROOT and check the followings plots:
 
Changed:
<
<
2) Change the thresholds and acquire files with different settings (threshold 30, 40, 50, 60) and look if increasing the threshold values the number of dataword for each MB decreases. Check if there are MBs which deliver a large amount of data.
>
>
a) TDVvsMBO - noise pattern TDC vs MB

b) CalibratinData - calibration data pattern TDC vs MB and calibration slope

c) BitFlips - bit flip vs MB
 
Deleted:
<
<
3) Acquire calibration data and check the correct amount of dataword delivered by each TDCs.
 

4) In the FEETestLogBook keep track of the problematic MB or OEPB and the files acquired.
Revision 4
04 Feb 2011 - Main.AttilioTarantola
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"
Here it follows a list of steps which have to be performed in order to poof the electronics on the MDC:

1) Acquire a file (.hld) as described in OEPReadoutTest and check if all MBs deliver data (noise data).

2) Change the thresholds and acquire files with different settings (threshold 30, 40, 50, 60) and look if increasing the threshold values the number of dataword for each MB decreases.
Changed:
<
<
Check is there are MBs which deliver a large amount of data.
>
>
Check if there are MBs which deliver a large amount of data.
 

3) Acquire calibration data and check the correct amount of dataword delivered by each TDCs.
Changed:
<
<
4) In the FEETestLogBook keep track of the problematic MB or OEPB.
>
>
4) In the FEETestLogBook keep track of the problematic MB or OEPB and the files acquired.
 
Changed:
<
<
4) Test with HV??
>
>
4) Test the FEE with HV on??
 

5) Data taking with cosmics/pulser in order to have a cross check with "real data"??
Revision 3
04 Feb 2011 - Main.AttilioTarantola
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"
Here it follows a list of steps which have to be performed in order to poof the electronics on the MDC:
Changed:
<
<
1) Acquire a file (.hld) and check if all MB deliver data (noise data). ExamplesOfPlots. For the chambers which are not in the final position on the HADES frame, this test must be repeated once the final position is reached.
>
>
1) Acquire a file (.hld) as described in OEPReadoutTest and check if all MBs deliver data (noise data).
 
Changed:
<
<
2) Change the thresholds and look if decreasing the threshold values the number of dataword for each MB decreases.
>
>
2) Change the thresholds and acquire files with different settings (threshold 30, 40, 50, 60) and look if increasing the threshold values the number of dataword for each MB decreases. Check is there are MBs which deliver a large amount of data.
 
Changed:
<
<
3) Acquire calibration data and check the correct amount of dataword delivered by each TDC.
>
>
3) Acquire calibration data and check the correct amount of dataword delivered by each TDCs.
 

4) In the FEETestLogBook keep track of the problematic MB or OEPB.

4) Test with HV??
Changed:
<
<
5) Data taking with cosmics in order to have a cross check with "real data"??
>
>
5) Data taking with cosmics/pulser in order to have a cross check with "real data"??
 

Revision 2
04 Feb 2011 - Main.AttilioTarantola
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"
Changed:
<
<
1) Acquire a file and check if all MB deliver data (noise data). ExamplesOfPlots. For the chamber which are not in the final position on the
>
>
Here it follows a list of steps which have to be performed in order to poof the electronics on the MDC:

1) Acquire a file (.hld) and check if all MB deliver data (noise data). ExamplesOfPlots. For the chambers which are not in the final position on the
  HADES frame, this test must be repeated once the final position is reached.

2) Change the thresholds and look if decreasing the threshold values the number of dataword for each MB decreases.
Changed:
<
<
3) Aquire calibration data and check the correct amount of dataword delivered by each TDC.
>
>
3) Acquire calibration data and check the correct amount of dataword delivered by each TDC.
 

4) In the FEETestLogBook keep track of the problematic MB or OEPB.

4) Test with HV??
Changed:
<
<
5) Data taking with cosmics in order to have a cross check with "real data"
>
>
5) Data taking with cosmics in order to have a cross check with "real data"??
 

 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Hades Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)