[Halld-tracking-hw] fADC range (was FDC meeting minutes...)

Fernando J. Barbosa barbosa at jlab.org
Tue Sep 21 10:49:44 EDT 2010


Hi Gerard,

I missed your email before I sent a reply to Naomi. My suggestion is to 
have the input range specified for real pulses out of the detectors, 
through the ASIC and 18 m of cable, add some margin and then use the 
fADC for validation. This is for one fADC assembly variant ("part 
number"). However, you may have a better plan to get the required 
information from the FDC and the CDC groups.

I should remind everyone that our schedule shows production of the 
fADC125s starting in January. So, we need to work diligently on this.

Best regards,
Fernando





Gerard Visser wrote:
> Hi Naomi & all,
>     The shaper is amplifying the pulse height, yes. But this is all 
> more complicated than people seem to be assuming. The shaper board, 
> and the ADC125 module, have a _frequency dependent_ response. First 
> there is the 'equalization filter' which ideally is set to cancel the 
> roll-off in frequency response of the cable (but may be set 
> differently, of course, for instance to also re-adjust some of the 
> 'tail cancellation' filter which is in the ASIC). Second there is the 
> shaping function itself, which squashes a tall skinny pulse into a 
> shorter wider pulse, but leaves a slower input pulse unaffected.
>     So in short, you can't just specify 'the' input range of the ADC, 
> and it is not a good idea to 'convert' the ADC scale into mV for 
> analysis - better just leave it as the ADC scale. And any discussion 
> about ADC input range needs to be in reference to some defined input 
> pulse shape.
>     On a more practical note, Fernando and I are working to get one of 
> the ADC boards to you at CMU soon. Then you can provide feedack to 
> change the gain by a numerical factor, _that_ will be unambiguous. If 
> it is decided to change the shaping time we need to do that first then 
> finalize the gain factor, because for instance a shorter shaping time 
> results in a need for lower gain factor so the skinny pulses don't get 
> clipped.
>     Thanks,
>
>         Gerard
>
> Naomi Jarvis wrote:
>> Oh I am sorry, I did know that once, I must have misread the table.
>>
>> So... is the shaper in our current configuration also amplifying the 
>> pulse height?  Does the 330mV from the preamp output at saturation 
>> correspond to our observed ~560mV shaper output?
>>
>> Would the new built-in shaping part of the new fADC also increase the 
>> pulse height, or can I just sum 330mV saturated preamp output + 50 mV 
>> pedestal and be confident that it will fit into 380mV new_fADC range ?
>>
>>
>> Naomi.
>>
>>
>>
>> On Sep 20, 2010, at 4:24 PM, Fernando J. Barbosa wrote:
>>
>>> Hi Naomi,
>>>
>>> The dynamic range in GlueX-doc-1364 is at the input and in fC, not 
>>> mV. For your configuration, the preamp differential output amplitude 
>>> is 380 fC x 0.57 mV/fC = 216.6 mV (5% linearity).
>>>
>>> Best regards,
>>> Fernando
>>>
>>>
>>>
>>>
>>>
>>> Naomi Jarvis wrote:
>>>> Hi Fernando and Gerard,
>>>>
>>>>
>>>> We are very happy with the 550mV fADC range, preamp and HVB 
>>>> combination that we now have here at CMU.  We were under the 
>>>> impression that the final fADC range was to be 0.5V.
>>>> Gluex doc 1364 shows our preamp as having 380mV dynamic range; at 
>>>> that point it is 5% non-linear, saturation is very approximately 
>>>> 520mV.
>>>> At present the pedestal requires ~25mV.  I believe we can correct 
>>>> off-line for the preamp performance some way after passing the 5% 
>>>> non-linear mark at 380mV towards 520mV.
>>>> Assuming the big CDC will initially be noisier, I would like to 
>>>> allow 50mV for its pedestal; then if this can be reduced we will 
>>>> have a happy increase in range.
>>>>
>>>> Would it be possible to give us a fADC range of 50mV (for pedestal) 
>>>> + 520mV preamp saturation point = 570mV?
>>>>
>>>> (Can you define the 520mV point more accurately?  I obtained this 
>>>> from amplitude spectra, from the scope it looks more like 560mV.)
>>>>
>>>>
>>>> Best regards,
>>>>
>>>> Naomi.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Sep 17, 2010, at 12:13 PM, Curtis A. Meyer wrote:
>>>>
>>>>> Hi Fernando -
>>>>>
>>>>>   We worked hard to get the dynamic range that we needed in the 
>>>>> CDC and I am
>>>>> not willing to give it up now. With regard to the peaking time, we 
>>>>> have always stated
>>>>> that in the CDC, we need 3-5 samples on the leading edge. This is 
>>>>> 24-40ns rise time.
>>>>> In the current setup, we have the shaper in front of the Flash 
>>>>> ADC. We are under the
>>>>> impression that this is built into the new flash ADC. That said, 
>>>>> the 35ns peaking time
>>>>> seems reasonable to us.
>>>>>
>>>>>  Curtis
>>>>> On 9/17/10 10:57 AM, Fernando J. Barbosa wrote:
>>>>>> Hi Gerard and Lubomir,
>>>>>>
>>>>>> The peaking time with the preamp and 18 m of cable is 14 ns and 
>>>>>> so it is the minimum one can achieve. I agree that 25 ns would be 
>>>>>> the minimum in trying to get three samples on the leading edge 
>>>>>> for timing interpolation. On the other hand, a 35 ns peaking time 
>>>>>> is very reasonable so we are perhaps considering optimizing this 
>>>>>> between 25 ns and 35 ns and based on the benefits of noise 
>>>>>> shaping. I don't think Lubomir included the time walk correction 
>>>>>> but this can be found on GlueX-doc-1364 for the ASIC (GAS-II).
>>>>>>
>>>>>> Regarding the assembly variants, I agree with Eugene that we 
>>>>>> should try to get one fADC125 but we need to consider this 
>>>>>> carefully. We have considered two fADC125 assembly versions, one 
>>>>>> for the CDC (low gain preamp) and the other for the FDC strips 
>>>>>> (high gain preamp) primarily based on fully using the ADC dynamic 
>>>>>> range. The preamp output ranges (@ saturation) are not the same 
>>>>>> in the configurations we are using: 430 mV for high gain and 330 
>>>>>> mV for low gain. If we set the ADC full scale (FS) at 430 mV 
>>>>>> (4095 on 12-bit), then 330 mV will be at 76% FS (3100 on 12-bit). 
>>>>>> Are we willing to sacrifice 25% of the ADC range on the CDC in 
>>>>>> exchange for one fADC125 version (based on saturation conditions)?
>>>>>>
>>>>>> However, there is another issue to consider if we are to have a 
>>>>>> single ADC. The output saturation at 430 mV is way out of the 
>>>>>> linear range and the output is 285 mV @ 5% linearity. For the CDC 
>>>>>> and the FDC:
>>>>>>
>>>>>> CDC - 330 mV @ Saturation, 207 mV @ 5% linearity
>>>>>> FDC Strips - 430 mV @ Saturation, 285 mV @ 5% linearity
>>>>>>
>>>>>> For a single ADC solution, I propose we set the ADC FS at 380 mV. 
>>>>>> We can set this even lower for a tighter linear range of interest.
>>>>>>
>>>>>> Best regards,
>>>>>> Fernando
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Gerard Visser wrote:
>>>>>>> Hi Lubomir,
>>>>>>>    We should perhaps discuss the shaping option ideas more fully 
>>>>>>> in the next meeting, I can call in. I didn't realize this was on 
>>>>>>> the agenda today.
>>>>>>>    In my opinion it is *feasible* to support two different 
>>>>>>> versions of the module with different shaping time. This amounts 
>>>>>>> only to different values for some capacitors, inductors, and 
>>>>>>> resistors to be used in assembly. The quantities are large 
>>>>>>> enough that there should be no significant cost impact, except 
>>>>>>> for probably a larger overall quantity of spares to be built. Of 
>>>>>>> course, I agree it is simpler to have only one version.
>>>>>>>    Presently the peaking time of the preamp-cable-ADC125 is 
>>>>>>> about 35 ns I believe. (Maybe a bit more in the case of the 
>>>>>>> cathodes if the detector capacitance affects it; it would make 
>>>>>>> sense but I don't know really.) We might try to reduce it but 14 
>>>>>>> ns seems to me too small - there will be too much amplitude 
>>>>>>> above the Nyquist zone, this has to degrade timing at some 
>>>>>>> point. Maybe some compromise value like 25 ns would be better to 
>>>>>>> try.
>>>>>>>    Anyway the starting point for this should probably be to 
>>>>>>> remove all explicit shaping from a channel, hook it up w/ preamp 
>>>>>>> and cable and a test pulser and input loading capacitor, and see 
>>>>>>> the pulse shape. This will exhibit the minimum achievable 
>>>>>>> peaking time; and we can also then we can calculate the shaping 
>>>>>>> time for the ADC board to get to the desired overall peaking time.
>>>>>>>    Can you describe the algorithm applied to ADC data to get the 
>>>>>>> timing measurement for page 514 work? Is there a fit here, or 
>>>>>>> just level-crossing using the same threshold e.g. 30mV? 
>>>>>>> Certainly an optimal timing algorithm will use more than 2 
>>>>>>> datapoints from the ADC, i.e., is not simply just a level 
>>>>>>> crossing and linear interpolation between two points.
>>>>>>>    Is the discriminator simulation 'perfect' or does it include 
>>>>>>> real-world distortions such as time walk (dispersion)?
>>>>>>>    Sincerely,
>>>>>>>
>>>>>>>        Gerard
>>>>>>>
>>>>>>>
>>>>>>> Lubomir Pentchev wrote:
>>>>>>>
>>>>>>>> The minutes of the last FDC meeting were posted at:
>>>>>>>>
>>>>>>>> http://www.jlab.org/Hall-D/software/wiki/index.php/Minutes-9-16-2010 
>>>>>>>>
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>     Lubomir
>>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Halld-tracking-hw mailing list
>>>>>>> Halld-tracking-hw at jlab.org
>>>>>>> https://mailman.jlab.org/mailman/listinfo/halld-tracking-hw
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Halld-tracking-hw mailing list
>>>>>> Halld-tracking-hw at jlab.org
>>>>>> https://mailman.jlab.org/mailman/listinfo/halld-tracking-hw
>>>>>
>>>>> -- 
>>>>> Prof. Curtis A. Meyer               Department of Physics
>>>>> Phone:      (412) 268-2745          Carnegie Mellon University
>>>>> Fax:        (412) 681-0648          Pittsburgh PA 15213-3890 
>>>>> cmeyer at ernest.phys.cmu.edu     http://www.curtismeyer.com/
>>>>>    _______________________________________________
>>>>> Halld-tracking-hw mailing list
>>>>> Halld-tracking-hw at jlab.org <mailto:Halld-tracking-hw at jlab.org>
>>>>> https://mailman.jlab.org/mailman/listinfo/halld-tracking-hw
>>> <barbosa.vcf>
>>
>>
>> _______________________________________________
>> Halld-tracking-hw mailing list
>> Halld-tracking-hw at jlab.org
>> https://mailman.jlab.org/mailman/listinfo/halld-tracking-hw
>> Received: from external-relay.indiana.edu (129.79.1.193) by
>>  IU-MSSG-HUB103.ads.iu.edu (10.79.1.152) with Microsoft SMTP Server 
>> (TLS) id
>>  14.0.702.0; Tue, 21 Sep 2010 09:47:25 -0400
>> Received: from mailman.jlab.org (mailman.jlab.org [129.57.64.97])    by
>>  external-relay.indiana.edu (8.14.4/8.14.4/IU Messaging Team) with 
>> ESMTP id
>>  o8LDlN1E018657    for <gvisser at indiana.edu>; Tue, 21 Sep 2010 
>> 09:47:25 -0400
>> Received: from mailman.jlab.org (mailman.jlab.org [129.57.64.97])    by
>>  mailman.jlab.org (8.13.6/8.13.8) with ESMTP id o8LDkDUo026685;    
>> Tue, 21 Sep
>>  2010 09:46:13 -0400
>> Received: from sm1.jlab.org (sm1.jlab.org [129.57.52.19])    by 
>> mailman.jlab.org
>>  (8.13.6/8.13.8) with ESMTP id o8LDkC8a026682    for
>>  <halld-tracking-hw at mailman.jlab.org>;    Tue, 21 Sep 2010 09:46:12 
>> -0400
>> Received: from imsva1.jlab.org (imsva1.jlab.org [129.57.52.17])    by
>>  sm1.jlab.org (8.13.6/8.13.8) with ESMTP id o8LDkBSt019808;    Tue, 
>> 21 Sep 2010
>>  09:46:11 -0400
>> Received: from imsva1.jlab.org (unknown [127.0.0.1])    by IMSA 
>> (Postfix) with
>>  ESMTP id D77D71004D;    Tue, 21 Sep 2010 09:46:11 -0400 (EDT)
>> Received: from p01c11m016.mxlogic.net (unknown [208.65.144.247])    by
>>  imsva1.jlab.org (Postfix) with ESMTP id 77CC910046;    Tue, 21 Sep 
>> 2010 09:46:11
>>  -0400 (EDT)
>> Received: from unknown [128.2.11.61] (EHLO smtp.andrew.cmu.edu)    by
>>  p01c11m016.mxlogic.net(mxl_mta-6.7.0-1) over TLS secured channel    
>> with ESMTP
>>  id 227b89c4.0.3571439.00-1926.4542388.p01c11m016.mxlogic.net    
>> (envelope-from
>>  <nsj at cmu.edu>); Tue, 21 Sep 2010 07:46:10 -0600 (MDT)
>> Received: from [128.237.250.0] ([128.237.250.0])    (user=nsjarvis 
>> mech=PLAIN (0
>>  bits))    by smtp.andrew.cmu.edu (8.14.3/8.14.3) with ESMTP id 
>> o8LDk6Uv004709
>>     (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);    
>> Tue, 21 Sep 2010
>>  09:46:06 -0400
>> From: Naomi Jarvis <nsj at cmu.edu>
>> In-Reply-To: <4C97C2ED.6080305 at jlab.org>
>> Date: Tue, 21 Sep 2010 09:46:05 -0400
>> Message-ID: <E78B60E3-C578-4F59-95D7-9A4AA72749CA at cmu.edu>
>> References: <Pine.LNX.4.64.1009161957590.5583 at jlabl1.jlab.org>    
>> <4C92BBEE.3050905 at indiana.edu>
>>     <4C9381C8.9040200 at jlab.org> <4C9393AC.8030709 at ernest.phys.cmu.edu>
>>     <AE383138-7B70-4A22-9564-5C5F02D0F249 at cmu.edu>
>>     <4C97C2ED.6080305 at jlab.org>
>> To: "Fernando J. Barbosa" <barbosa at jlab.org>
>> X-Mailer: Apple Mail (2.1081)
>> X-PMX-Version: 5.5.9.388399, Antispam-Engine: 2.7.2.376379,
>>     Antispam-Data: 2010.9.21.133616
>> X-SMTP-Spam-Clean: 8% (
>>     SUPERLONG_LINE 0.05, FROM_EDU_TLD 0, RDNS_NXDOMAIN 0, RDNS_SUSP 0,
>>     RDNS_SUSP_GENERIC 0, __C230066_P5 0, __CP_URI_IN_BODY 0, __CT 0,
>>     __CTE 0, __CT_TEXT_PLAIN 0, __FRAUD_CONTACT_NUM 0, __HAS_MSGID 0,
>>     __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0,
>>     __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0,
>>     __PHISH_SPEAR_STRUCTURE_1 0, __SANE_MSGID 0, __TO_MALFORMED_2 0,
>>     __USER_AGENT_APPLEMAIL 0, __X_MAILER_APPLEMAIL 0)
>> X-SMTP-Spam-Score: 8%
>> X-Scanned-By: MIMEDefang 2.60 on 128.2.11.61
>> X-Spam: exempt
>> X-MAIL-FROM: <nsj at cmu.edu>
>> X-SOURCE-IP: [128.2.11.61]
>> X-MIME-Autoconverted: from quoted-printable to 8bit by 
>> mailman.jlab.org id
>>     o8LDkC8a026682
>> CC: HallD _Tracking_HW <halld-tracking-hw at jlab.org>
>> Subject: [Halld-tracking-hw] fADC range (was FDC meeting minutes...)
>> X-BeenThere: halld-tracking-hw at jlab.org
>> X-Mailman-Version: 2.1.9
>> Precedence: list
>> List-Id: <halld-tracking-hw.jlab.org>
>> List-Unsubscribe: 
>> <https://mailman.jlab.org/mailman/listinfo/halld-tracking-hw>, 
>>     <mailto:halld-tracking-hw-request at jlab.org?subject=unsubscribe>
>> List-Archive: <https://mailman.jlab.org/pipermail/halld-tracking-hw>
>> List-Post: <mailto:halld-tracking-hw at jlab.org>
>> List-Help: <mailto:halld-tracking-hw-request at jlab.org?subject=help>
>> List-Subscribe: 
>> <https://mailman.jlab.org/mailman/listinfo/halld-tracking-hw>, 
>>     <mailto:halld-tracking-hw-request at jlab.org?subject=subscribe>
>> Content-Type: text/plain; charset="us-ascii"
>> Content-Transfer-Encoding: 7bit
>> Sender: <halld-tracking-hw-bounces at jlab.org>
>> Errors-To: halld-tracking-hw-bounces at jlab.org
>> Return-Path: halld-tracking-hw-bounces at jlab.org
>> X-MS-Exchange-Organization-AuthSource: IU-MSSG-HUB103.ads.iu.edu
>> X-MS-Exchange-Organization-AuthAs: Anonymous
>> X-MS-Exchange-Organization-PRD: jlab.org
>> X-MS-Exchange-Organization-SenderIdResult: SoftFail
>> Received-SPF: SoftFail (IU-MSSG-HUB103.ads.iu.edu: domain of 
>> transitioning
>>  halld-tracking-hw-bounces at jlab.org discourages use of 129.79.1.193 as
>>  permitted sender)
>> X-MS-Exchange-Organization-SCL: 0
>> X-MS-Exchange-Organization-PCL: 2
>> X-MS-Exchange-Organization-Antispam-Report: 
>> DV:3.3.5705.600;SID:SenderIDStatus SoftFail;OrigIP:129.79.1.193
>> X-MS-Exchange-Organization-AVStamp-Mailbox: MSFTFF;1;0;0 0 0
>> MIME-Version: 1.0
>>
>>
>> Oh I am sorry, I did know that once, I must have misread the table.
>>
>> So... is the shaper in our current configuration also amplifying the 
>> pulse height?  Does the 330mV from the preamp output at saturation 
>> correspond to our observed ~560mV shaper output?
>>
>> Would the new built-in shaping part of the new fADC also increase the 
>> pulse height, or can I just sum 330mV saturated preamp output + 50 mV 
>> pedestal and be confident that it will fit into 380mV new_fADC range ?
>>
>>
>> Naomi.
>>
>>
>>
>> On Sep 20, 2010, at 4:24 PM, Fernando J. Barbosa wrote:
>>
>>> Hi Naomi,
>>>
>>> The dynamic range in GlueX-doc-1364 is at the input and in fC, not 
>>> mV. For your configuration, the preamp differential output amplitude 
>>> is 380 fC x 0.57 mV/fC = 216.6 mV (5% linearity).
>>>
>>> Best regards,
>>> Fernando
>>>
>>>
>>>
>>>
>>>
>>> Naomi Jarvis wrote:
>>>> Hi Fernando and Gerard,
>>>>
>>>>
>>>> We are very happy with the 550mV fADC range, preamp and HVB 
>>>> combination that we now have here at CMU.  We were under the 
>>>> impression that the final fADC range was to be 0.5V.
>>>> Gluex doc 1364 shows our preamp as having 380mV dynamic range; at 
>>>> that point it is 5% non-linear, saturation is very approximately 
>>>> 520mV.
>>>> At present the pedestal requires ~25mV.  I believe we can correct 
>>>> off-line for the preamp performance some way after passing the 5% 
>>>> non-linear mark at 380mV towards 520mV.
>>>> Assuming the big CDC will initially be noisier, I would like to 
>>>> allow 50mV for its pedestal; then if this can be reduced we will 
>>>> have a happy increase in range.
>>>>
>>>> Would it be possible to give us a fADC range of 50mV (for pedestal) 
>>>> + 520mV preamp saturation point = 570mV?
>>>>
>>>> (Can you define the 520mV point more accurately?  I obtained this 
>>>> from amplitude spectra, from the scope it looks more like 560mV.)
>>>>
>>>>
>>>> Best regards,
>>>>
>>>> Naomi.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Sep 17, 2010, at 12:13 PM, Curtis A. Meyer wrote:
>>>>
>>>>> Hi Fernando -
>>>>>
>>>>>   We worked hard to get the dynamic range that we needed in the 
>>>>> CDC and I am
>>>>> not willing to give it up now. With regard to the peaking time, we 
>>>>> have always stated
>>>>> that in the CDC, we need 3-5 samples on the leading edge. This is 
>>>>> 24-40ns rise time.
>>>>> In the current setup, we have the shaper in front of the Flash 
>>>>> ADC. We are under the
>>>>> impression that this is built into the new flash ADC. That said, 
>>>>> the 35ns peaking time
>>>>> seems reasonable to us.
>>>>>
>>>>>  Curtis
>>>>> On 9/17/10 10:57 AM, Fernando J. Barbosa wrote:
>>>>>> Hi Gerard and Lubomir,
>>>>>>
>>>>>> The peaking time with the preamp and 18 m of cable is 14 ns and 
>>>>>> so it is the minimum one can achieve. I agree that 25 ns would be 
>>>>>> the minimum in trying to get three samples on the leading edge 
>>>>>> for timing interpolation. On the other hand, a 35 ns peaking time 
>>>>>> is very reasonable so we are perhaps considering optimizing this 
>>>>>> between 25 ns and 35 ns and based on the benefits of noise 
>>>>>> shaping. I don't think Lubomir included the time walk correction 
>>>>>> but this can be found on GlueX-doc-1364 for the ASIC (GAS-II).
>>>>>>
>>>>>> Regarding the assembly variants, I agree with Eugene that we 
>>>>>> should try to get one fADC125 but we need to consider this 
>>>>>> carefully. We have considered two fADC125 assembly versions, one 
>>>>>> for the CDC (low gain preamp) and the other for the FDC strips 
>>>>>> (high gain preamp) primarily based on fully using the ADC dynamic 
>>>>>> range. The preamp output ranges (@ saturation) are not the same 
>>>>>> in the configurations we are using: 430 mV for high gain and 330 
>>>>>> mV for low gain. If we set the ADC full scale (FS) at 430 mV 
>>>>>> (4095 on 12-bit), then 330 mV will be at 76% FS (3100 on 12-bit). 
>>>>>> Are we willing to sacrifice 25% of the ADC range on the CDC in 
>>>>>> exchange for one fADC125 version (based on saturation conditions)?
>>>>>>
>>>>>> However, there is another issue to consider if we are to have a 
>>>>>> single ADC. The output saturation at 430 mV is way out of the 
>>>>>> linear range and the output is 285 mV @ 5% linearity. For the CDC 
>>>>>> and the FDC:
>>>>>>
>>>>>> CDC - 330 mV @ Saturation, 207 mV @ 5% linearity
>>>>>> FDC Strips - 430 mV @ Saturation, 285 mV @ 5% linearity
>>>>>>
>>>>>> For a single ADC solution, I propose we set the ADC FS at 380 mV. 
>>>>>> We can set this even lower for a tighter linear range of interest.
>>>>>>
>>>>>> Best regards,
>>>>>> Fernando
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Gerard Visser wrote:
>>>>>>> Hi Lubomir,
>>>>>>>    We should perhaps discuss the shaping option ideas more fully 
>>>>>>> in the next meeting, I can call in. I didn't realize this was on 
>>>>>>> the agenda today.
>>>>>>>    In my opinion it is *feasible* to support two different 
>>>>>>> versions of the module with different shaping time. This amounts 
>>>>>>> only to different values for some capacitors, inductors, and 
>>>>>>> resistors to be used in assembly. The quantities are large 
>>>>>>> enough that there should be no significant cost impact, except 
>>>>>>> for probably a larger overall quantity of spares to be built. Of 
>>>>>>> course, I agree it is simpler to have only one version.
>>>>>>>    Presently the peaking time of the preamp-cable-ADC125 is 
>>>>>>> about 35 ns I believe. (Maybe a bit more in the case of the 
>>>>>>> cathodes if the detector capacitance affects it; it would make 
>>>>>>> sense but I don't know really.) We might try to reduce it but 14 
>>>>>>> ns seems to me too small - there will be too much amplitude 
>>>>>>> above the Nyquist zone, this has to degrade timing at some 
>>>>>>> point. Maybe some compromise value like 25 ns would be better to 
>>>>>>> try.
>>>>>>>    Anyway the starting point for this should probably be to 
>>>>>>> remove all explicit shaping from a channel, hook it up w/ preamp 
>>>>>>> and cable and a test pulser and input loading capacitor, and see 
>>>>>>> the pulse shape. This will exhibit the minimum achievable 
>>>>>>> peaking time; and we can also then we can calculate the shaping 
>>>>>>> time for the ADC board to get to the desired overall peaking time.
>>>>>>>    Can you describe the algorithm applied to ADC data to get the 
>>>>>>> timing measurement for page 514 work? Is there a fit here, or 
>>>>>>> just level-crossing using the same threshold e.g. 30mV? 
>>>>>>> Certainly an optimal timing algorithm will use more than 2 
>>>>>>> datapoints from the ADC, i.e., is not simply just a level 
>>>>>>> crossing and linear interpolation between two points.
>>>>>>>    Is the discriminator simulation 'perfect' or does it include 
>>>>>>> real-world distortions such as time walk (dispersion)?
>>>>>>>    Sincerely,
>>>>>>>
>>>>>>>        Gerard
>>>>>>>
>>>>>>>
>>>>>>> Lubomir Pentchev wrote:
>>>>>>>
>>>>>>>> The minutes of the last FDC meeting were posted at:
>>>>>>>>
>>>>>>>> http://www.jlab.org/Hall-D/software/wiki/index.php/Minutes-9-16-2010 
>>>>>>>>
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>     Lubomir
>>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Halld-tracking-hw mailing list
>>>>>>> Halld-tracking-hw at jlab.org
>>>>>>> https://mailman.jlab.org/mailman/listinfo/halld-tracking-hw
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Halld-tracking-hw mailing list
>>>>>> Halld-tracking-hw at jlab.org
>>>>>> https://mailman.jlab.org/mailman/listinfo/halld-tracking-hw
>>>>>
>>>>> -- 
>>>>> Prof. Curtis A. Meyer               Department of Physics
>>>>> Phone:      (412) 268-2745          Carnegie Mellon University
>>>>> Fax:        (412) 681-0648          Pittsburgh PA 15213-3890 
>>>>> cmeyer at ernest.phys.cmu.edu     http://www.curtismeyer.com/
>>>>>    _______________________________________________
>>>>> Halld-tracking-hw mailing list
>>>>> Halld-tracking-hw at jlab.org <mailto:Halld-tracking-hw at jlab.org>
>>>>> https://mailman.jlab.org/mailman/listinfo/halld-tracking-hw
>>> <barbosa.vcf>
>>
>>
>> _______________________________________________
>> Halld-tracking-hw mailing list
>> Halld-tracking-hw at jlab.org
>> https://mailman.jlab.org/mailman/listinfo/halld-tracking-hw
-------------- next part --------------
A non-text attachment was scrubbed...
Name: barbosa.vcf
Type: text/x-vcard
Size: 188 bytes
Desc: not available
Url : https://mailman.jlab.org/pipermail/halld-tracking-hw/attachments/20100921/c99f09dd/attachment.vcf 


More information about the Halld-tracking-hw mailing list