Hey Jean, Thanks for your reply.
Yes I remember that issue as we discussed about it. Since that issue was only for one element, I also tried doing save() for more than one elements, it still does not work. I doubt it is related to that issue. As Timo has pointed below, he says that this is because the save() method does not store the triangulation vertices. It only stores the refinement information. Here is the documentation <https://www.dealii.org/8.4.1/doxygen/deal.II/classTriangulation.html> where in the *"Serializing (loading or storing) triangulations"* section it says that serializing stores vertices and its location. " . More specifically, the information that is stored is everything that defines the mesh such as vertex locations, vertex indices, how vertices are connected to cells, boundary indicators, subdomain ids, material ids, etc. " I am not sure what to do now. There is confusion between what this function does and what documentation says. One way to load a mesh which is different from the mesh at instant 0 could be to store the total displacement as a solution vector, and then deserialize() it and add to the coordinates of the mesh loaded using load(). This is because, load() just loads the mesh which is same as the mesh at instant 0. Is there any other way ? On Friday, July 8, 2016 at 4:03:53 AM UTC-4, Jean-Paul Pelteret wrote: > > Hi Rajat, > > I suspect that this might be related to this issue > <https://github.com/dealii/dealii/issues/2661>, but we should wait for > confirmation from someone with more knowledge on how the triangulation > class works. > > Regards, > J-P > > On Friday, July 8, 2016 at 9:56:07 AM UTC+2, RAJAT ARORA wrote: >> >> >> Hello all, >> >> I am observing some strange behavior with >> Parallel::distributed::triangulation<dim>::save(const * char) function. >> >> I make a triangulation and then move its vertices and then save it to a >> file. >> >> After saving the triangulation and I load it in a different function. >> However, this loaded triangulation is not consistent with the one saved. >> >> I am attaching a code that demonstrate this strange behavior / bug. >> Although, I am using parallel::distributed::triangulation, I run it with >> zero elements and on one processor. >> >> The output in the "femesh" file is as follows: >> >> original cell number 1 >> Vertex 0: 0 0 >> Vertex 1: 1 0 >> Vertex 2: 0 1 >> Vertex 3: 1 1 >> >> before writing to file >> cell number 1 >> Vertex 0: 0 0 >> Vertex 1: 0.75 0 >> Vertex 2: 0 1 >> Vertex 3: 0.75 1 >> >> after loading from file >> cell number 1 >> Vertex 0: 0 0 >> Vertex 1: 1 0 >> Vertex 2: 0 1 >> Vertex 3: 1 1 >> >> >> >> Thanks for your help. >> >> >> -- The deal.II project is located at http://www.dealii.org/ For mailing list/forum options, see https://groups.google.com/d/forum/dealii?hl=en --- You received this message because you are subscribed to the Google Groups "deal.II User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to dealii+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
