dolfin team mailing list archive

[Ola Skavhaug <skavhaug@xxxxxxxxx>]

On Thu, Sep 10, 2009 at 9:13 PM, Anders Logg<logg@xxxxxxxxx> wrote:
> On Thu, Sep 10, 2009 at 08:54:32PM +0200, Ola Skavhaug wrote:
>> On Thu, Sep 10, 2009 at 5:32 PM, Anders Logg<logg@xxxxxxxxx> wrote:
>> > There seem to be only a few issues remaining before we can make a
>> > release:
>> >
>> >  https://launchpad.net/dolfin/+milestone/0.93
>> >
>> > In summary:
>> >
>> >  1. Parallel parsing of MeshFunctions
>>
>> What is the status on the solution to this?
>>
>> The right fix is to extend MeshFunction storage to contain the mapping
>> from the mesh entity to vertex numbers. The quick fix (that would fix
>> vertex and cell MeshFunctions) would be to store the global cell
>> numbers read from file. The latter solution is simple, and could be
>> done with little effort, whereas the first is a bit more involved.
>> Your calls.
>
> I think we should make a release as soon as we can and then a new
> release in about a month. I have some things planned for that release.
>
> My suggestion is that we aim for the correct solution and postpone
> that to 0.94. Then it would be enough to make a call to
> not_working_in_parallel() in a suitable place (reading MeshFunctions).
>
> We also need to solve (or disable) 3. plotting from C++ in
> parallel. What's your opinion on that one?

>From a debugging point of view, having runtime plotting in parallel is
nice but not needed. The most important aspect of Viper is to provide
direct feedback when setting up a problem. Knowing that the scalar
version of dolfin works should be sufficient in this respect.

Ola

> --
> Anders
>
>
>> Ola
>>
>> >  2. Checking speedup
>> >  3. Plotting from C++ in parallel
>> >  4. Getting all demos to run or exit gracefully
>> >
>> > To solve (4), I've added a new function that can be called like this:
>> >
>> >  not_working_in_parallel("ODE solver");
>> >
>> > When solving ODEs and running in parallel, the following message is
>> > then printed:
>> >
>> >  Process 0: ODE solver is not (yet) working in parallel. Consider
>> >  filing a bug report at https://bugs.launchpad.net/dolfin
>> >
>> > The program will exit with status 10. It might be possible to catch
>> > this in the test scripts so that we can let the buildbots run all
>> > demos i parallel. Or we can check on (4) manually. Thoughts?
>> >
>> >
>> > -----BEGIN PGP SIGNATURE-----
>> > Version: GnuPG v1.4.9 (GNU/Linux)
>> >
>> > iEYEARECAAYFAkqpG/AACgkQTuwUCDsYZdFHBQCeKDnSVKvcqwLVR1qNO09PTqq3
>> > KjsAn3vAPrDFJQZfoG9iOatbuhOKh1PQ
>> > =SwA1
>> > -----END PGP SIGNATURE-----
>> >
>> > _______________________________________________
>> > DOLFIN-dev mailing list
>> > DOLFIN-dev@xxxxxxxxxx
>> > http://www.fenics.org/mailman/listinfo/dolfin-dev
>> >
>> >
>>
>>
>>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkqpT88ACgkQTuwUCDsYZdF90wCePsL8TicEFRLE8VE2/HS68RBS
> Gm8AoIS0Sql7FxjUoTtvJN1RZtt5ZSlx
> =2YnV
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/mailman/listinfo/dolfin-dev
>
>



-- 
Ola Skavhaug