[cram-developers] CRAM meeting notes

[Georg Bartels]

Hi,

over the summer, Jan and Moritz (in dicussion with Michal, Hartmut and
Asil) have worked on logging of low-level data in a MongoDB database
outside of CRAM. That tool-chain does not use execution traces but is
working during plan execution. My impression was that they preferred
this new tool-chain over execution traces.

Our discussion this week was how to proceed with execution traces (now
that an alternative system is in active use + they are the only core
package without unit-tests) in the future. My point was that execution
traces seem to offer features the new tool-chain does not have, and they
are there and probably working. Hence, my suggestion to add unit-tests
(and maybe a tutorial or two) to clarify and document their usage in
case someone wants to use/extent them in the future again. As both Jan
and Moritz were not in Bremen, we did not make any decision on Tuesday.
Hence, we could continue discussing online. ;)

Hope this clears things up a bit.

Cheers,
Georg.


 On 12/18/2013 04:49 PM, Lorenz Mösenlechner wrote:
> Hi,
> 
> just a question: why do you want to get rid of support for execution
> traces? I always thought they are an important feature of CRAM so I wonder
> what the problem with them is. Could someone please clarify? :)
> 
> Thanks,
> Lorenz
> 
> 
> 
> On Tue, Dec 17, 2013 at 11:22 AM, Georg Bartels <
> georg.bartels at cs.uni-bremen.de> wrote:
> 
>> Hi all,
>>
>> please find attached the minutes of today's CRAM developers meeting in
>> Bremen.
>>
>> Cheers,
>> Georg.
>>
>> _______________________________________________
>> cram-developers mailing list
>> cram-developers at informatik.uni-bremen.de
>> https://mailman.informatik.uni-bremen.de/mailman/listinfo/cram-developers
>>
>>
>