[Dune-devel] [GSoC] Performance testing: more detailed schedule

[Miha Čančula]

Hello,

I'm really sorry about not responding earlier, but something has come up.

My (school) mentor informed me that I will have to defend my master's
thesis by the start of september rather than by the start of October as I
thought. Although the thesis itself is finished, I have to get it out to
print this week, and they do want me to prepare some new pictures. So I
would really like to get this week off, polish the thesis and print it.
After that, I'll get back on track with DUNE.

As you might imagine, this hit me rather by surprise, and it messes up my
plans as I was counting on doing it all after the finish of coding. I
realize this is already the second departure from DUNE because of my
school, and the end of coding is coming pretty soon, so I'm not sure if I
will be able to meet my goals in the end. I will try though, and at least
now I know I'll be able to focus entirely on this for the whole september :)

Regards,
Miha


2013/8/20 Christian Engwer <christian.engwer at uni-muenster.de>

> Hi Miha,
>
> I think the documentation is really important, as I'm not able to help
> you implement the autoomake stuff, if I don't know what you want to
> achieve...
>
> Christian
>
> On Sun, Aug 18, 2013 at 09:45:05PM +0200, Christian Engwer wrote:
> > Hi Miha,
> >
> > > I've been thinking of using intermediate files and a wildcard target
> > > (pattern rule), so that you would add something like
> > >
> > > perftest_myexample: myexample perftest_myexample.log
> > >
> > > and there would be a general rule
> > >
> > > %_perftest.log:
> > >   <run the test here>
> > >
> > > If will try such a rule today, unless you have a better suggestion.
> >
> > As I have written a while ago, I suggest to look at the code in
> > dune-common/am/checklog this is an automake snippet, which can be
> > included in the Makefiles and provides a new target "make
> > checklog". The list of tests etc. is available in different makefile
> > variables, so the new phony target can directly loop through these
> > lists and run the necessary compile operations and execute the tests.
> >
> > > > It would be great, to have a short readme in doc, which explains, how
> > > > the tests interact with the buildsystem and what the user is supposed
> > > > to do.
> > > >
> >
> > > Yes, of course. But first the interaction should work :)
> >
> > If you can desccribe the current state for cmake, I can comment on how
> > this can be achieved with automake
> >
> > > > Then I have some additional comments...
> > > > - all test should be performed in the build directory, this is then
> > > >   also the place where results should be stored.
> > > > - it would be convenient to have all results in a seperate
> > > >   subdirectory (of the build dir) and then the html files again in a
> > > >   sub dir.
> > > >
> > > I agree, will make it that way.
> > >
> > > > - in order to be able to integrate the perftests with the autobuild
> > > >   services, it is necessary to seperate data aquisition and
> > > >   storage. Therefore it ise necessary to write some kind of log files
> > > >   which can then be transferred to the server (or is this already
> > > >   integrated?).
> > > >
> > > This is somewhat separated right now. There are separate python
> modules,
> > > but so far the main script calls them all in sequence.
> > > Log files are generated in any case, and are optionally deleted
> afterwards.
> > > There shouldn't be problems there.
> > > The flow of data is like this: (measure -> logfile), (logfile -> sqlite
> > > database), (database -> HTML).
> >
> > OK, then it shouldn't be a problem to do this later.
> >
> >
> > Ciao
> > Christian
> >
> > _______________________________________________
> > Dune-devel mailing list
> > Dune-devel at dune-project.org
> > http://lists.dune-project.org/mailman/listinfo/dune-devel
> >
>
> --
> Prof. Dr. Christian Engwer
> Institut für Numerische und Angewandte Mathematik
> Fachbereich Mathematik und Informatik der Universität Münster
> Einsteinstrasse 62
> 48149 Münster
>
> E-Mail  christian.engwer at uni-muenster.de
> Telefon +49 251 83-35067
> FAX             +49 251 83-32729
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dune-project.org/pipermail/dune-devel/attachments/20130820/3c68e02a/attachment.htm>