<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Ok I'll proceed that way.</p>
<p>Thanks for your reply (that late).</p>
<p>Guillaume<br>
</p>
<br>
<div class="moz-cite-prefix">Le 16/02/2018 à 16:02, Raffaella De
Vita a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:4c4e9847-d471-c3d9-737b-0a6060788fb2@ge.infn.it">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Dear Guillaume,<br>
given the type of modification you need, I would be in favor of
deleting and recreating the table with the additional colums.
Since there is only one entry, it would take a few minutes to do
the change.<br>
Best regards,<br>
Raffaella<br>
<br>
<div class="moz-cite-prefix">Francois-Xavier Girod wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAOKxh47yw0e+ctiu58GtBOaCPXPvFg4VVZnM8pMYsFVviE6DAA@mail.gmail.com">
<div dir="ltr">Dear Guillaume
<div><br>
</div>
<div>I am not currently doing any mass decoding. I see a
couple people doing simulations on the batch farm, although
I doubt they could be affected.</div>
<div><br>
</div>
<div>Best regards</div>
<div>FX</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Feb 16, 2018 at 3:35 PM,
Guillaume CHRISTIAENS <span dir="ltr"><<a
href="mailto:guillaum@jlab.org" target="_blank"
moz-do-not-send="true">guillaum@jlab.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
In order to reduce Micromegas data size, we now use
"sparse samples" in MVT. To compute a time information
correctly we need this information to be accessible during
the decoding.<br>
<br>
Since it's an electronic feature that we didn't know
before facing this data size issue, ccdb table was not
made to hold this information. Then I would like to add 2
constants and thus 2 columns to the current DAQ table for
micromegas (/daq/config/bmt). It's only a 1-row table so
not too heavy.<br>
<br>
I think the only ways to add columns are to delete the
table and create a new one, or to create a duplicate table
with a different name (like /daq/config/bmt2). Even if
it's not the spirit of ccdb, I clearly prefer the first
solution, to keep clean and clear tables, and since it's
just adding column, retro-compatibility will be fine.<br>
<br>
The only issue I see is if someone is decoding a file at
the moment the table is deleted and then created again, he
may have errors.<br>
<br>
What do you think ?<br>
<br>
Regards,<br>
<br>
Guillaume<br>
<br>
<br>
______________________________<wbr>_________________<br>
Clas12_calcom mailing list<br>
<a href="mailto:Clas12_calcom@jlab.org" target="_blank"
moz-do-not-send="true">Clas12_calcom@jlab.org</a><br>
<a
href="https://mailman.jlab.org/mailman/listinfo/clas12_calcom"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://mailman.jlab.org/mailm<wbr>an/listinfo/clas12_calcom</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>