Bruno,
This temporary fix works. I was unable to create a small example to
illustrate the problem with the detail I desired, so unfortunately cannot
share this. The workflow that resolved this issue is as follows:
1. generate coarse mesh
2. load checkpoint
3. reinitialize and prepare associated
I think a temporary fix could be to
generate_coarse_mesh in the triangulation
load checkpoint
load data
And then for each step you want to load, to
clear
generate_coarse_mesh
load checkpoint
load data
Which when thinking about it looks a bit absurd. If you have a small
example i'd be happy to l
triangulation.clear() removes all data. Apparently, load() requires that
triangulation already contain a coarse mesh. Therefore clear() cannot work.
I'll write a small program that demonstrates the issue today.
Would it be to add a line in the implementation of load() which clears the
buffer? I
Nice to see you here on this forum, Jerett! :-)
I think that the checkpointing in deal.II probably assumes this process only
happens once, so I may be exceeding the design of the Triangulation class.
Quite possibly. What happens if you call triangulation.clear() between calls?
If that doesn
