List view
- Due by January 31, 2021•1/1 issues closed
- Due by August 31, 2021•1/1 issues closed
For the simulation of problems in thin domains, such as coastal ocean (for engineering applications such as marine power generation), Firedrake implements a special class of meshes which have one structured direction. The connectivity in this structured direction is stored implicitly, and hence the scheme described above must be extended to handle this special case. This consists of providing enough metadata in the checkpoint file to determine that an extruded mesh was created, and to reconstruct it.
Due by May 31, 2021•1/1 issues closedFor many purposes, often offline analysis of results, but also after adaptivity, Firedrake users want to save a checkpoint file on N processes and subsequently reload it on P != N processes. The general scheme described above supports this since PETSc can save and reload its mesh topologies on differing process counts. As part of this, it provides remapping objects for the topology that facilitate this transfer. We will use these to develop redistribution primitives in Firedrake that the user can call to load and then transfer fields onto an appropriately redistributed mesh.
Due by April 30, 2021•1/1 issues closed