[Fwd: Re: [Brahms-dev-l] Cannot commit ADC Gaps]

I replied to myself by mistake, I sent this message right after my 
complaint about
the gap module.

Djam


Hello again,

You can ignore this message. I was unwittingly using a version of the 
tof adc gap module
that was older than the one fixed precisely for this problem a month ago.

Djam

attached mail follows:

Hello again,

You can ignore this message. I was unwittingly using a version of the 
tof adc gap module
that was older than the one fixed precisely for this problem a month ago.

Djam



Djamel Ouerdane wrote:

> Hello devl's,
>
> Because I'd like to make new DSTs for the 63 GeV runs, I refined the 
> TOF calibration.
> I could commit some new time offsets without any problems last week 
> but now,
> when I want to commit ADC gap stuff, the script runs smoothly but 
> something
> weird occurs then : the comment string I want to attach to the values 
> I am committing
> is obviously greater than 16 characters but still, I get a warning 
> that it is shorter
> than that. That's a 1st hint that something does not propagate 
> correctly. When I then check
> the DB values either from the DAQ website or from one of the brat 
> based browser, I get
> the old values (which are plain wrong by the way). This confirms that 
> somewhere in
> the commit chain, the input is not propagated.
> As I said, it works fine for other calibration parameters like time 
> offsets. Any clue ?
>
> Djam
>
>
> _______________________________________________
> Brahms-dev-l mailing list
> Brahms-dev-l@lists.bnl.gov
> http://lists.bnl.gov/mailman/listinfo/brahms-dev-l




_______________________________________________
Brahms-dev-l mailing list
Brahms-dev-l@lists.bnl.gov
http://lists.bnl.gov/mailman/listinfo/brahms-dev-l