![]() The memory needed to run the whole anatomy is indeed pushing the processor to their limits, I will maybe create other files containing only an arm, a leg etc. Pathological anatomy could be a further step, beyond all sane anatomy. The whole file or parts of it can easily be exported into many other formats from the. All versions of Blender are always available and the file that I share is adapted to the latest version. They offer many interesting options (colors, complex organisation, between others that could be useful for anatomy). blend files are indeed meant to be used in Blender. Projects could share common data model (USD?), desktop and web viewer, authoring tools (Blender, 3D Slicer), etc. => This is obviously very difficult, would take a lot of work, but coordinating with OpenAnatomy project or other open efforts should help. I don’t know how would you incorporate anatomical variations, pathologies, different taxonomies, coordinate systems, manage versioning, accept additions or change requests from others, keeping the models in sync with various other anatomical atlases, how could you correlate the meshes with ground truth data (CT, MRI, ultrasound, cryosections, etc.). Scalability: Management of even this single specimen is quite complicated.=> It would be nice to document the list of known issues/missing parts clearly, near the download link, so that users know what to expect. For example, I could not visualize the lymphatic system. I was not able to show labels with callouts, as I saw it on some screenshots.A simple application that shows meshes and images like the OpenAnatomy web viewer would be sufficient, but it with virtual reality support. You can get a standalone Oculus Quest for $300, which should easily handle visualization of surface meshes and image cross-sections. Virtual reality support in the viewer is essential, interacting in with a mouse and keyboard on a 2D screen is just painful compared to having two 6-DOF controllers in an immersive 3D environment. => Instead of using Blender for distribution, it would be better to use a simpler viewer. It is mostly just the complexity of Blender, which is justified if you want to edit the model, but just for viewing feels too difficult. I also found that it was almost impossible to use it with a touchpad (I would have needed the middle button or reconfigure keyboard shortcuts). When I right-clicked and choose to show all items inside then it worked. ![]() I also found it hard (could not really figure out even in the end) why items does not show up if I open the eye icon (and all parents’ eye icons). Keyboard shortcuts help (without that I could not do anything), but not granular enough (just show/hide 6-8 major categories). Loading and setup of an atlas should be simpler. Some of them persistently change the preferences, so it somebody uses Blender for other purposes then he has to switch between the regular settings and the Z-anatomy recommended settings. There are a number of extra setup steps to adjust the application preferences.=> For authoring/editing it could be OK to require 32 GB RAM and desktop class GPU, but for users you would need to create decimated models (preferable by about a factor of 10x). My desktop with an i7 CPU, 32GB RAM, RTX 2080 could load the model without problems, but everything was still sluggish. My relatively strong Intel i7 ultrabook with 16GB RAM, and Intel Iris Plus Graphics could not handle it (I could barely rotate the viewin Blender, physical memory usage was near 100%). Higher than expected hardware requirements: It needs desktop computer or gaming laptop.Maybe with FYI, I’ve tried the atlas and it was a bit hard for me to use it. I take good note of your question and will investigate it would be a great option. ( Z-Anatomy on LinkedIn: Demo fonctions de base) dicom viewer (glitchy, slow, heavy computing…).Ĭlipping border (Alt+B) allows to get a rapid slicing effect but it is not editable each clipping box must be done one at a time. ![]() Using images on their original plane, definitely yes.įor the meshes, it is very different although it is possible to reproduce something comparable to a slice-scroll function with orthographic views and the ‘clip start’ option of the view menu every virtual plane created by the slicing through the mesh would be empty and let appear the inner side of the surface of the object the system would be a hack and have several serious disadvantages compared to a regular. dicom converted into a pile of images (.jpg/.png) and to apply a boolean operation with a cube to get a similar effect, and even to reproduce the MPR effect with a simple node setup and a script.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |