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

This sounds somewhat familiar to me from other complaints
like the 'logic for commit, readAscii is also mixed up in this module -
just a suggestion

flemming

----------------------------------------------------------------
Flemming Videbaek
Physics Department
Brookhaven National Laboratory

e-mail: videbaek@bnl.gov
phone: 631-344-4106
----- Original Message ----- 
From: "Djamel Ouerdane" <ouerdane@nbi.dk>
To: <brahms-dev-l@lists.bnl.gov>
Sent: Monday, November 08, 2004 6:11 AM
Subject: [Brahms-dev-l] Cannot commit ADC Gaps


> 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