First time here? Checkout the FAQ!
0 votes
by (190 points)
edited by
Dear Team,

I was hoping that you could answer a question about recording Local Activation Times please? Simply:

Is it possible (or might it become possible in the near future) to specify a subset of mesh nodes/vertices at which local activation times should be recorded?

The reason for this is simply a storage issue when running many jobs in parallel. For our purposes, we don't need LAT at the simulation resolution, a reduced resolution mesh would be enough. We can specify the nodes in advance.

Related to this storage problem: is it possible (or might it become possible in the near future) to save LAT in binary instead of ascii?

Thanks very much

Sam (and collaborator)

1 Answer

0 votes
by (7.8k points)

Thank you for the input and for using openCARP!

Clearly from a performance perspective binary data would be helpfull in your situation. Generally speaking, we try to keep the number of different formats as low as possible, as formats add to the costs on multiple axes (maintainance, documentation, training, ..). Also, binary data has the disadvantage of increasing the difficulty for people to add their own post-processing steps.

I would advise to process the LAT data as a post-processing step in each simulation job. You can interpolate LATs onto your coarser mesh or do at least a conversion to binary. Meshtool can help you with that. See "meshtool interpolate nodedata" and "meshtool collect".

Best wishes,

Welcome to openCARP Q&A. Ask questions and receive answers from other members of the community. For best support, please use appropriate TAGS!
architecture, carputils, documentation, experiments, installation-containers-packages, limpet, slimfem, website, governance