Closed dinardo closed 6 years ago
Hi @dinardo maybe also attach the code with which you are recording the data, along with the used configuration. When chaning VCal - are you in the CtrlReg = 4 (high region)? Is your chip properly calibrated/trimmed?
/Simon
Hi Simon, on my CERN public area:
/afs/cern.ch/user/d/dinardo/public/
you can find the tar.gz file ROCtest.tar.gz with the python code, runDTBextCLKtrg.py, and the ROC parameter files.
Yes, I tried also with CtrlReg = 4 and CtrlReg = 0 and the px.value is always 125.0
Many thanks,
Hi Mauro,
i've been testing your code with inject=True, trigsource=int, but removed the externalClock (btw: Are you running FW 4.6 on external Clock? This should not work) and the clockstretch.
Doing this, I get different pulse heights for different vcal values, meaning I cannot reproduce your issue. Did you try it with these settings?
Hi Paul, I do have FW = 4.6
I don't remember I've used your settings. I think yes, because I've tried different things, but any way I'll try them again.
Unfortunately right now I'm at Fermilab for a test beam. I'll be back in my lab after the 15th of December.
Quick question, how to you print the pulse height ?
Many thanks for looking into this.
Hi Mauro,
since I've used your script, the output comes from the decodeData function, hence it's the px.value.
Dear Experts, I'm using the following [1] function to plot the pixel hits (taken from pxar/python/cmdline.py) unfortunately the px.value looks strange. I was expecting the charge in ADC counts, but I always get numbers like 125, sometime 124 or 126. This happens both when I inject with no matter which Vcal value, and also with random triggers on noisy pixels !
Perhaps you guys can give me some hints on what I'm doing wrong ? DTB:
The whole machinery is working, is just the pulse height that is bizarre.
Many thanks,
[1]