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

Output of point data to VTK and NetCDF #1261

Open
jpthiele opened this issue Oct 1, 2024 · 3 comments
Open

Output of point data to VTK and NetCDF #1261

jpthiele opened this issue Oct 1, 2024 · 3 comments
Labels
priority: low Should be solved eventually workload: high Would take longer than a week

Comments

@jpthiele
Copy link

jpthiele commented Oct 1, 2024

For finite element codes (ultimately based on T8code.jl) we would like to try incorporating t8code.
Naturally the results would be point/vertex based and not element based in most cases.

The solution would be to introduce an additional point data type and matching function calls.
For code deduplication it would probably be worthwhile to have a full feature function that can output both
that gets called by the current function for only element data internally.

The alternative would be to implement the vtk output of the parallel mesh and point data in Julia directly,
but that would duplicate most of the code from t8code.

"Priority: medium"

@Davknapp
Copy link
Collaborator

Davknapp commented Oct 2, 2024

Hey @jpthiele

thank you for submitting this Issue. I just want to double check if I understand your Issue correctly.
Do you want to write out point-data to a VTK/NetCDF-file, or do you want to store data per point, that will be managed by t8code and eventually written to a VTK/NetCDF-file?

@jpthiele
Copy link
Author

jpthiele commented Oct 2, 2024

Ultimately results would be stored in a distributed linear algebra vector anyways so I don't think the second option would be needed in our code.
Practically, I would like a 'sibling function' for t8_forest_write_vtk_ext where I can also provide point data.

@Davknapp Davknapp added priority: low Should be solved eventually workload: high Would take longer than a week labels Oct 8, 2024
@Davknapp
Copy link
Collaborator

Davknapp commented Oct 8, 2024

Hey @jpthiele ,

in our current version of our vtk-writer we duplicate the points of our mesh by the number of elements that share this point. A quick introduction of your feature-proposal would also mean to duplicate the data of the points, probably resulting in a messy output.
We are currently working on a unique point-id, but it will take some time. Therefore a proper implementation of your feature-proposal will take some time, even though we think that it is a nice idea.
We will keep this issue open, but on our low-priority list and solve it eventually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low Should be solved eventually workload: high Would take longer than a week
Projects
None yet
Development

No branches or pull requests

2 participants