Add Purkinje support to batch simulations and minor fixes #61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Sachetto,
In this pull request, there is now support to execute Purkinje simulations using the 'MonoAlg3D_batch' binary with MPI. Also, there are few additions to the solver, like a new script to concatenate a ALG and FIBERS files into a single one, a new function to print UUID of the GPU device and I included a new field to the output 'pmj_delay.csv' that tells when a propagation block occurs in a terminal during a Purkinje coupled simulation.
Regarding fixes, I found a minor error when saving the output file using the 'MonoAlg3D_converter'. Looks like the filename string was missing the end of character '\0', so the file could not be read directly from Paraview without renaming it.
Also, I am working on a new 'save_mesh' function that can calculate and plot the LAT together with multiple AP traces from different cells in the grid. Finally, I am trying to improve the performance of the 'activation_time' calculus, which is serial right now. It will be good if we could use a #pragma statement, but we need to avoid race conditions when writing to the 'persistent_data' struct. All these working in progress are written in the 'ToDo'.
Best regards,
Lucas