Hi,
as far as I know, unstructured grids in MITK have an experimental-like state as
they are currently not used by anyone in our departments. So I would expect
some more bugs and missing features. I wasn't even able to store a simple
unstructured grid (the one that is attached to the ticket you opened a few days
ago). All volume mapper options of unstructured grids crash. And so on, and so
on, and I just spend a few minutes so far. I don't believe that we currently
have enough resources to overhaul the whole thing, so contributing would be the
most promising approach to get things done at the moment, sorry.
What types of data do your grids have at the moment, as the one mentioned above
was just a surface or at least appeared to be one? In that case it could be a
more promising path for you to import plain surfaces to MITK instead.
Best,
Stefan
From: Bertram Sabrowsky-Hirsch
[mailto:[email protected]]
Sent: Mittwoch, 21. März 2018 11:19
To: [email protected]
Subject: [mitk-users] Using mitk::UnstructuredGrid for series of grids
Hi,
I am trying to import and visualize CFD data from an external tool in MITK. I
figured I can use mitk::UnstructuredGrid for this purpose, since it has a
m_GridSeries member. I do have the data for the time steps in separate .vtu
files that I load as separate mitk::UnstructuredGrid instances that I use to
extract the vtk::UnstructuredGrid (GetVtkUnstructuredGrid) and assemble in one
mitk::UnstructuredGrid instance (SetVtkUnstructuredGrid with the timestep) that
contains all timesteps. Everything works well this far: The timesteps show up
in the DataNodes Details widget, the m_GridSeries member is filled and I do see
the first timestep in the 3D visualization. However, the time slider (in the
ImageNavigator widget) does not seem to work. I called GetUpdatedTimeGeometry
after assembling the UnstructuredGrid to be sure and I confirmed that the time
geometry does contain multiple timesteps, but the ImageNavigator widget seems
not to recognize that.
Is my approach right so far (assemble the mitk::UnstructuredGrid from multiple
instances) or is there a better approach and what do I miss?
This is what the details widget shows for the data node containing my assembled
mitk::UnstructuredGrid:
UnstructuredGrid (0000024FC36D6870)
TimeGeometry: ProportionalTimeGeometry (0000024FC365B400)
TimeSteps: 51
FirstTimePoint: 0
StepDuration: 1 ms
Time Bounds: 0 - 51
GetGeometryForTimeStep(0): Geometry3D (0000024FC27CA060)
IndexToWorldTransform:
Matrix:
1 0 0
0 1 0
0 0 1
Offset: [37.4872, -32.9024, -18.974]
Center: [0, 0, 0]
Translation: [37.4872, -32.9024, -18.974]
Inverse:
1 0 0
0 1 0
0 0 1
Scale : 1 1 1
BoundingBox: ( 2.35031,11.1689 9.53366,15.3866 7.2686,13.5972
)
Origin: [37.4872, -32.9024, -18.974]
ImageGeometry: 0
Spacing: [1, 1, 1]
Thank you in advance!
Kind regards,
Bertram
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
