Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple rod io #180

Open
fankiat opened this issue Jan 27, 2023 · 0 comments
Open

Multiple rod io #180

fankiat opened this issue Jan 27, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@fankiat
Copy link
Owner

fankiat commented Jan 27, 2023

CosseratRodIO currently does not support multiple rod IO. The user instead has to create an IO object for each rod in order to properly render each rod as a rod in Paraview, with separate xmf files for each rod. A preliminary workaround was to append all the nodes of Cosserat rods into a single array, and then add the array as lagrangian field into base IO, altogether bypassing the need for CosseratRodIO. This is slightly undesirable since the rendering in Paraview will render the rods as points and not as polylines.

Instead, the add_as_lagrangian_fields_for_io() function in the base IO class should handle multiple rods (i.e multiple grids) just like how add_as_eulerian_fields_for_io() handles multiple fields (albeit on the same grid). CosseratRodIO can then leverage that and add rods to the IO as needed, resulting in only one file for paraview rendering.

I will push an updated patch of this implementation in sopht-mpi (taking care of the parallel hdf5 writing). This should provide a better idea on how we can refactor and merge MPIIO to the base IO in sopht as planned in #146

@fankiat fankiat self-assigned this Feb 14, 2023
@fankiat fankiat added the enhancement New feature or request label Feb 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant