[cram-developers] CRAM meeting notes

Moritz Tenorth tenorth at cs.uni-bremen.de
Wed Dec 18 18:03:39 CET 2013


Hi,

just a non-technical remark:

On 12/18/2013 05:55 PM, Gayane Kazhoyan wrote:
> It might take a while though, a month or two. Unless, of course, 
> Michael stops me from doing that, which I guess he will not because 
> I'm new and have no deadlines yet.
Today we got the news that the next RoboHow review (including a demo in 
our lab) will be in the first or second week of April, which is about 
one month earlier than expected. In addition, some of us will have to do 
work for the SAPHARI review in early February and the ACAT review at 
some time in Spring, and several EU proposals will be due April 23rd.

As much as I appreciate software documentation and maintenance work, I'd 
expect that all of us need to focus a bit more on the demos from January 
on. There are many cool parts involved, and having our own 'Bremen 
demos' will be a great thing as well, I think -- but it also involves a 
bit of infrastructure work (e.g. interfaces to other partners' code) 
that we should try to distribute among all of us. But we can plan this 
in detail once we are back from vacation in early January.

cheers
Moritz


>
> If somebody finds that it is crucial to get rid of execution traces 
> now and not include them in the next cram_core release we can discuss 
> that. (Although it looks like we're fine for now...)
>
> Gaya
>
>
> On Wed, Dec 18, 2013 at 5:17 PM, Georg Bartels 
> <georg.bartels at cs.uni-bremen.de 
> <mailto:georg.bartels at cs.uni-bremen.de>> wrote:
>
>     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
>     <mailto: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
>     <mailto:cram-developers at informatik.uni-bremen.de>
>     >>
>     https://mailman.informatik.uni-bremen.de/mailman/listinfo/cram-developers
>     >>
>     >>
>     >
>
>     _______________________________________________
>     cram-developers mailing list
>     cram-developers at informatik.uni-bremen.de
>     <mailto:cram-developers at informatik.uni-bremen.de>
>     https://mailman.informatik.uni-bremen.de/mailman/listinfo/cram-developers
>
>
>
>
>
> _______________________________________________
> cram-developers mailing list
> cram-developers at informatik.uni-bremen.de
> https://mailman.informatik.uni-bremen.de/mailman/listinfo/cram-developers

-- 
Dr. Moritz Tenorth     | tenorth at cs.uni-bremen.de
Universität Bremen     | Am Fallturm 1
29359 Bremen           | Germany
Tel: +49 421 218-64016 | ai.uni-bremen.de/team/moritz_tenorth

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.informatik.uni-bremen.de/pipermail/cram-developers/attachments/20131218/9251fe4a/attachment.html>


More information about the cram-developers mailing list