Skip to Content.
Sympa Menu

star-fst-l - Re: [Star-fst-l] Access for FST Disk 1 Module 12

star-fst-l AT lists.bnl.gov

Subject: Star-fst-l mailing list

List archive

Chronological Thread  
  • From: "Visser, Gerard" <gvisser AT indiana.edu>
  • To: "Ye, Zhenyu" <yezhenyu AT uic.edu>
  • Cc: Star-fst L <star-fst-l AT lists.bnl.gov>
  • Subject: Re: [Star-fst-l] Access for FST Disk 1 Module 12
  • Date: Wed, 26 Jan 2022 19:09:28 +0000

Ok thanks. Yes, it may be a higher risk to run with some failing piece of the circuit showing this symptom if that failing piece is on the detector module itself. (I am sure that if the failure is on the cables or the PPB it does not add risk to the detector module.)

Back on the overall question, I really don't have a strong feeling which is best. I am just a little nervous that data taken at too low a bias will not prove to be good. If we could get more prompt complete assurance that the data works well for tracking purposes, that would make it much more palatable to run low bias, in my opinion. But this is not a question for me.

Sincerely,
     Gerard



From: Ye, Zhenyu <yezhenyu AT uic.edu>
Sent: Wednesday, January 26, 2022 2:00 PM
To: Visser, Gerard <gvisser AT indiana.edu>
Cc: Xu Sun <sunxuhit AT gmail.com>; Star-fst L <star-fst-l AT lists.bnl.gov>
Subject: Re: [Star-fst-l] Access for FST Disk 1 Module 12
 
Hi Gerard, 

I mean detector module.

Zhenyu

On Jan 26, 2022, at 12:53 PM, Visser, Gerard <gvisser AT indiana.edu> wrote:

Hi Zhenyu,
   Do you mean detector modules or HVPS modules?? I'm not at all worried about the latter.

    GV


From: Ye, Zhenyu <yezhenyu AT uic.edu>
Sent: Wednesday, January 26, 2022 1:47 PM
To: Xu Sun <sunxuhit AT gmail.com>
Cc: Visser, Gerard <gvisser AT indiana.edu>; Aschenauer Elke-Caroline <elke AT bnl.gov>; Star-fst L <star-fst-l AT lists.bnl.gov>; flemming videbaek <videbaek AT bnl.gov>; Hu, Yu <yuhu AT bnl.gov>
Subject: Re: Access for FST Disk 1 Module 12
 
This is ok with me. 

I would like to remind everyone that we have run out of good modules. So we don’t want to damage a potentially good module. 

Zhenyu

On Jan 26, 2022, at 12:38 PM, Xu Sun <sunxuhit AT gmail.com> wrote:

Hi Gerard,

I could set it to 100 muA and see what happens. The 100 muA is the current hardware limit.
If we want to set it even higher, I will need to increase the hardware limit.

Best,

Xu

On Wed, Jan 26, 2022 at 1:35 PM Visser, Gerard <gvisser AT indiana.edu> wrote:
hi Xu,
   Thanks.
  It is a reasonable concern, I don't know which will be worse for data quality - too low a bias vs. perhaps unstable bias. My complete WAG is too low may be worse.

   I think we can set a trip as high as 150-200 uA without worrying about any difference in risk of damage to our hardware, compared to 25 uA.

     Gerard


From: Xu Sun <sunxuhit AT gmail.com>
Sent: Wednesday, January 26, 2022 1:32 PM
To: Aschenauer Elke-Caroline <elke AT bnl.gov>
Cc: Visser, Gerard <gvisser AT indiana.edu>; Star-fst L <star-fst-l AT lists.bnl.gov>; flemming videbaek <videbaek AT bnl.gov>; Ye, Zhenyu <yezhenyu AT uic.edu>; Hu, Yu <yuhu AT bnl.gov>
Subject: Re: Access for FST Disk 1 Module 12
 
Hi Elke and Gerard,

The trip setpoint for disk 1 module 12 outer sector is 25 muA now and the rest of modules is 10 muA.
The issue is the current fluctuates when the HV is around 100V, see attached plots.
I could set a higher trip point for this module. But I am not sure how the fluctuating current will affect the data quality.

Best,

Xu




Archive powered by MHonArc 2.6.24.

Top of Page