[Dune] [#80] Backup and Restore of Grids.

[Andreas Dedner]

Hi Benedikt,
I am sorry that you feel that way - I think it is great that somebody 
with real problems
is using DUNE and also ALUGRID. I thought that I was responding to your
bug reports as quickly as I could...

IDs: there is a suggestion for a new boundary condition treatment - we 
here in Freiburg
        are not pushing this because what is there is working for us. I 
do not mind a
        new strategy although that means a hell of a lot of work for us 
- both in the grid
        development and in the numerics; but that is ok. You also worked 
on the idea,
        but nobody can tell me how to match up the boundary ids from the 
grid file
        (gmsh dgf or what ever) with the boundary index generated from 
the grid.
        Before the GridFactory does not allow fix a way to attach data 
from the grid generation
        with the index from the grid, I do not see how to use the new 
approach in my code.
        Since other people (including you) want to change the DUNE 
interface, these people
        should answer my question - which a stated a week ago in your 
FlySpray task.

H5: the problem here is that this seems much to sophisticated for our uses.
       The FlySpray task just refers to a simple read/write provided by 
the grid manager itself,
       This does not mean that we do not want to help developing or 
extending the DUNE interface in a way that would help
       you with this project - binding to DUNE would be profitable for 
all of us.
       As to discussion H5Fed at the meting...
       A problem is that these developer meeting are always very crowded 
with many topics -
       we meet once a year and again only for one day.
       Perhaps the reorganizers of developer meeting could add some time 
to the schedule where specific projects and
       their requirements of the DUNE interface cab be discussed - first 
a talk for everybody and then later some time
       for all who are interested to discuss consequences for DUNE.
Best
Andreas
      
       

Oswald Benedikt wrote:
> Hi Dune, somewhat more than a week ago I sent a mail to this list which was
> exactly concerned with this kind of subject:
>
> Our project H5Fed for storing (write/read) hierarchical meshes in a standardized way.
>
> Unfortunately, nobody cared about this, it seems.
>
> While I am convinced that a discussion about specific details of pointers etc are 
> certainly very relevant for the long term evolution and stability of Dune,
> from a more practical point of view I would sometimes wish that subjects 
> concerned with applications needs, namely backup and restore,
> or, I dare say, usage of boundary id's in ALUGrid, find more resonance
> in this list (and are not downgraded to minor significance in the flyspray).
>
> Thus, I repeat my plea: have a look at this project (h5.psi.ch)
>
> Our idea is to connect H5Fed to Dune in a transparent way, but we need feedback
> from the Developers.
>
> Thanks and have a quiet night, Benedikt
>
>
>
>
> -----Original Message-----
> From: dune-bounces+benedikt.oswald=psi.ch at dune-project.org on behalf of Dune
> Sent: Tue 20.10.2009 19:55
> To: dune at dune-project.org
> Subject: [Dune] [#80] Backup and Restore of Grids.
>  
> THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
>
> The following task has a new comment added:
>
> FS#80 - Backup and Restore of Grids.
> User who did this - Oliver Sander (sander)
>
> ----------
> Here's the UGGrid status: you can write grid hierarchies to disk, but you cannot read them.  This is the problem: in theory, UG has full backup/restore facilities.  However, in UG the domain boundaries are hard-wired in the C code.  Hence they are not included in the backup file.  To do a proper restore means to call the UG 'restore' method but get the domain information in there somehow from the side. I am convinced that this is feasible but it will need at least several days of work from someone who knows UG.
> ----------
>
> More information can be found at the following URL:
> http://www.dune-project.org/flyspray/index.php?do=details&task_id=80#comment1231
>
> You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
>
> _______________________________________________
> Dune mailing list
> Dune at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Dune mailing list
> Dune at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune
>