Hello I still am having problems understanding where and how data is stored in the workbench.
I have been exploring the code and, for example, Step 3 is all about Volume Rendering, and everything is done "magicaly". I can't find the algorithm that accesses the data structure to generate and shoot rays (I am supposing volume rendering is here done using some ray casting algorithm). So... Help? Thank you! Miguel On 22.10.2012 14:37, Miguel Nunes wrote: > thank you Sascha! > > So, anyone around with experience in these data structures and > generating the volume itself? > > On 19.10.2012 21:10, Sascha Zelzer wrote: >> Hi, >> >> On 10/19/2012 05:39 PM, Miguel Nunes wrote: >>> Hello again, >>> >>> As you may remember from my past topic, I am trying to build a plug-in >>> with OpenCL to render volumes for medical imaging. I managed to create >>> my plugin by generating also a new MITK-based project, compile >>> everything, managed to have some basic OpenCL functions and Kernels >>> running on the GPU (just for testing) and I am now looking forward to >>> develop some cool stuff with MITK. >> Great :) >> >>> I have been looking around the MITK documentation but I am finding hard >>> to find the proper documentation regarding the data structures and how >>> to generate a volume texture from a data set. Probably I didn't >>> searched enough to find this information. >>> >>> Let`s say I want to open the Pic3D.nrrd example provided by you. How can >>> I access the data, generate a Volume and having access to all the >>> accelerating data structures (bounding boxes, for example)? where can I >>> find this information? >> I am not an expert in rendering techniques, there are other people in >> the MITK team who might want to add some information here. >> >> I think the best way would be to write your own "mapper" and attach it >> to a mitk::DataNode: >> >> http://docs.mitk.org/nightly-qt4/classmitk_1_1Mapper.html >> >> http://docs.mitk.org/nightly-qt4/classmitk_1_1DataNode.html#a51a8601ffc2e3b94a393adad060b4b90 >> >> >> Have a look at some mappers in the MITK source code how they access >> the data and generate visual output. >> >> There is also a factory mechanism which you could use later to >> "permanently" add your mapper to mitk::DataNodes. >> >> Unfortunately, I don't know of any nice tutorial explaining the >> technique in detail. >> >>> Also, and just out of curiosity, how can I deactivate the 4 >>> visualization widgets present in the "display" tab? >> You can switch off the MITK_BUILD_org.mitk.gui.qt.stdmultiwidgeteditor >> CMake variable in your MITK build configuration. You then need to >> provide your own "render window editor". >> >> Best, >> Sascha >> >>> Kind regards, >>> Miguel >>> >>> ------------------------------------------------------------------------------ >>> >>> Everyone hates slow websites. So do we. >>> Make your web apps faster with AppDynamics >>> Download AppDynamics Lite for free today: >>> http://p.sf.net/sfu/appdyn_sfd2d_oct >>> _______________________________________________ >>> mitk-users mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/mitk-users > -- Miguel Nunes, MSc. mail: [email protected] Early Stage Researcher tel: +43(0)1 20501 30504 VRVis Zentrum fuer Virtual Reality und Visualisierung Forschungs-GmbH FN: 195369h, HG Wien Donau-City-Straße 1 +43(0)1 20501 30100 A-1220 Wien, Austria web:<http://www.vrvis.at> ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
