[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: DRAFT specifications for DC flash

Hi Elton and Gerard,

I have attached a copy of the specs for the fADC-250 as a template for 
the fADC-100 specs. I would follow a similar format and would attach 
additional detailed material. I did that with the fADC-250, for example, 
and it helped in focusing the design. Let me know if you need a copy as 
an example. It is always good, in my opinion, to have a summary spec 
sheet followed by other pertinent information.

As for Elton questions on his draft, my answers are as follows:

Should we include the following (included in FADC250 specs)?
• Clock specification? Jitter/source -------Yes
• Data Latency-------Yes
• Trigger latency (only indirectly referenced below)-------Yes
• Linearity? INL/DNL?------Yes

Question/comment from Elton: I assume this is given by 72 events x 72 
channels x 100 12bit words/event = 0.778 Mbytes? Is this consistent with 
our rate estimates? (I don’t quite understand the statement about no 
zero-suppression if only 100 words is used per event)?---- The number of 
bytes will likely be much higher because there is more than just data 
being transferred like channel ID, Module #, etc. With zero suppression, 
you still need the a header and trailer, I think.

There is additional documentation that I would like to suggest. This is 
perhaps more important in trying to establish tasks that need to be 
addressed in the next few months or a year and may not entirely apply to 
the prototype stage:

1. Power Spreadsheet - dissipation/consumption per supply (Helps with 
debugging and specifying the crate for supply and cooling).
2. Cost Spreadsheet - Done.
3. User's Manual.
4. Test Program.
5. Scheduling.

I agree with Elton, if I understand, that we should perhaps devise some 
milestones once we iterate through the list a couple of times.

Regards,
Fernando



Elton Smith wrote:
> Hi Fernando and Lars,
>
> We are writing up the requirements for the drift chamber flash to be able
> to clarify what is expected from the first prototypes. I have edited
> Gerard's list of specifications for the flash ADC (March Electronics
> Meeting) and added questions/comments. I think this should be reviewed by
> the electronics group so that we can be clear on what needs to be included
> at least for the first prototype.
>
> Please get back to me by early next week, so we can iterate for use as a
> design goals for building the prototypes.
>
> Thanks, Elton.
>
> Elton Smith
> Jefferson Lab MS 12H5
> 12000 Jefferson Ave
> Suite # 16
> Newport News, VA 23606
> elton@jlab.org
> (757) 269-7625

FADC_SPEC.pdf

begin:vcard
fn:Fernando J. Barbosa
n:Barbosa;Fernando J.
org:Jefferson Lab
adr;dom:;;12000 Jefferson Ave.;Newport News;VA;23606
tel;work:757-269-7433
version:2.1
end:vcard