xml mesh required in Unicorn?

Asked by Anthony Ashley on 2014-08-19


We are looking for a high performance fluid solver, and are interested in fenics, specifically Unicorn. We have liked many aspects of fenics, but one issue we have seen is that it requires the conversion of a mesh into an xml format, requiring storage. Eventually we would like to be running unicorn on very fine (and large) meshes that would change between individual simulations, as we are investigating shape optimization.

Does unicorn remove this requirement for the conversion and storage of the mesh before the simulation can begin?

Thank you for any help in this matter!

Anthony Ashley
Rensselaer Polytechnic Institute
PhD Student, Aerospace Engineering

Question information

English Edit question
Unicorn Edit question
No assignee Edit question
Last query:
Last reply:
Cem Degirmenci (ncde) said : #1

which version of dolfin-hpc are you using? since 2012 we support binary file format.

we have a converter code for converting xml meshes to binary meshes which take less space
and be read efficiently in parallel using mpi-io with name dolfin_post
I don't know if you have access to this repository
can you inform me about it?


Can you help with this problem?

Provide an answer of your own, or ask Anthony Ashley for more information if necessary.

To post a message you must log in.