[Dune-devel] [Dune-Commit] [Commit] dune-grid - 545f73a: Start working on a backup restore facility in YaspGrid

[Steffen Müthing]

Hi,

Am 02.10.2014 um 13:41 schrieb Dominic Kempf <dominic.r.kempf at gmail.com>:

> Hey Oliver,
> there is several reasons, that dgf is not suitabel as a backup format:
> - It does not cover all the options that are needed to *fully* restore a YaspGrid.
>   A small example is the parameter keepPhysicalOverlap (bool).
> - It doesnt support tensorproduct grids.
> - With my format, only the coordinates relevant to a processor are stored in that
>   processors backup file. I dont see how such thing could be realized through dgf
>   (seems to me like it takes the same file on every rank)
> Best,
> Dominic
> 
> PS: Just read your next mail: Seems like the first point could hold for VTK too,
> if Paraview tries to verify the XML schema. Also, I dont think we want an XML 
> parser in dune-grid, do we?

+1. Adding a dune-grid dependency on an XML parser library would probably create some
interesting discussions on this list… ;-)

One thing I just noticed: Any file format should definitely contain a version marker, just
In case someone comes along and implements an awesome new feature that requires storing
additional data. I don’t necessarily propose supporting parsing multiple format versions, just add
a little check at the start and throw a tantrum if the version number is not what we expect…

Steffen


> 
> 
> On Thu, Oct 2, 2014 at 1:23 PM, Oliver Sander <sander at igpm.rwth-aachen.de> wrote:
> Am 02.10.2014 um 13:20 schrieb Oliver Sander:
> > Am 02.10.2014 um 13:10 schrieb Oliver Sander:
> >> Am 02.10.2014 um 13:02 schrieb Dominic Kempf:
> >>> Hey Oliver,
> >>> Yes, I was writing my very own ascii thing. I mad several assumptions when
> >>> thinking about the format:
> >>> 1) All grids to be restored were saved through the same facility. For all
> >>> other uses, one should consider the dgfparser.
> >>> 2) The amount of data to be stored is rather small (even for tensorproduct
> >>> grids)
> >>> 3) The output should be readable by the human eye.
> >>> With these in mind, I decided, that a self-defined self-explanatory ascii
> >>> format will be most the most efficient (in the sense of coding time) way to
> >>> achieve it. If you provide good reasons for a more standard format, I could
> >>> reconsider though.
> >>
> >> Hi Dominic,
> >> I have no compelling reason for your use case, I am simply not a fan of reinventing
> >> yet another file format.  Earlier this week I wrote VTK file reading for an application
> >> of mine, and that was simple and pretty using tinyxml2.
> >> If you think that "for all other uses, one should consider the dgfparser",
> >> how about using the dgf format for backup/restore right away?
> >
> 
> [apologies for the previous empty mail]
> 
> It appears that the vtk format also supports tensor-product grids natively
> ("RectilinearGrid").  Using that would allow to visualize backup files in
> Paraview.
> Best,
> Oliver
> 
> 
> >
> >
> >
> >>
> >> Best,
> >> Oliver
> >>
> >>
> >>> Best,
> >>> Dominic
> >>>
> >>> On Thu, Oct 2, 2014 at 12:52 PM, Oliver Sander <sander at igpm.rwth-aachen.de>
> >>> wrote:
> >>>
> >>>> Hi Dominic,
> >>>> great you're working on the restoring facility.  From browsing the commit
> >>>> logs it seems like
> >>>> you are inventing a new ascii format.  Did you consider something
> >>>> standard, like XML or similar?
> >>>> Thanks,
> >>>> Oliver
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Dune-devel mailing list
> >>>> Dune-devel at dune-project.org
> >>>> http://lists.dune-project.org/mailman/listinfo/dune-devel
> >>>>
> >>>>
> >>>
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> Dune-devel mailing list
> >> Dune-devel at dune-project.org
> >> http://lists.dune-project.org/mailman/listinfo/dune-devel
> >>
> >
> >
> >
> >
> > _______________________________________________
> > Dune-devel mailing list
> > Dune-devel at dune-project.org
> > http://lists.dune-project.org/mailman/listinfo/dune-devel
> >
> 
> 
> 
> _______________________________________________
> Dune-devel mailing list
> Dune-devel at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune-devel
> 
> 
> _______________________________________________
> Dune-devel mailing list
> Dune-devel at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune-devel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.dune-project.org/pipermail/dune-devel/attachments/20141002/483b79a7/attachment.sig>