-
Notifications
You must be signed in to change notification settings - Fork 32
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
Add option to save vispy generated meshdata #278
Comments
Hi @sanjayankur31 , |
Hi @Dhruvanshu-Joshi , yes that sounds correct. Do take a look at what common formats for storing mesh data are. I think the paraview docs do have some information on that. The ideal case would be that our code generates the mesh in a standard format so that any other tools can be used to then visualise it. (A complementary tweak could also be to allow our methods to then read these meshes and visualise them) Assigning this to you now. Thanks very much for working on this. A few notes:
|
Hi @sanjayankur31 , |
OK, lets use them to begin with then. I expect the user will have to specify the file name to save to, and we can check that it's either "obj" or "gz". Could you please work on a PR that will add the new option to save the mesh to begin with? |
Hey @sanjayankur31 |
This will allow visualisation in other tools, such as paraview.
This should be simple enough, given that vispy provides the required I/O functions. We only have to save the mesh after we generate it
https://vispy.org/api/vispy.io.mesh.html#vispy.io.mesh.read_mesh
The text was updated successfully, but these errors were encountered: