Open phcerdan opened 10 years ago
Dear Pablo,
You are right I must add more document about the installation and compiling but I was quite busy during last weeks... The code has been tested and compiled by VTK 5.8 I havent try it by 6.2 so it might be that...
Regards, Mehdi
On 20 Jun 2014, at 05:29, "PHCerdan" notifications@github.com<mailto:notifications@github.com> wrote:
Hi there, thanks for sharing your code! I am trying to compile it using cmake in the git directory, but facing a problem not finding:
and also.
A few lines explaining the compiling process you are using would be awesome. I haven't find vtkVolumeRenderingFactory.h in my VTK 6.2 folder.
Thanks! Pablo
— Reply to this email directly or view it on GitHubhttps://github.com/mohammeb/VTKMultiVolumeRayCaster/issues/1.
Dear Mehdi,
Indeed very nice code and I'd like to use. I have tried to compile (after cmake) and I got immediately this error:
[ 7%] Generating vtkGPUMultiVolumeRayCastMapper_ShadeFS.cxx, vtkGPUMultiVolumeRayCastMapper_ShadeFS.h make[2]: ./vtkGPUMultiVolumeRayCastMapper_ShadeFS.cxx: Command not found make[2]: * [vtkGPUMultiVolumeRayCastMapper_ShadeFS.cxx] Error 127 make[1]: * [CMakeFiles/vtkGPUMultiVolumeRender.dir/all] Error 2 make: *\ [all] Error 2
I am not a VTK expert, let me know if I am doing something wrong.
I agree that few lines explaining the compiling process will be very nice.
Davide.
P.S. I am using VTK6.0.0 (which works when I compile the examples).
The problem can be that I didn't compile something needed from your code?
Follow the the value of the variables that I used to compile the VTK:
BUILD_DOCUMENTATION ON BUILD_EXAMPLES ON BUILD_SHARED_LIBS ON BUILD_TESTING ON CMAKE_BUILD_TYPE Debug CMAKE_INSTALL_PREFIX /usr/local VTK_EXTRA_COMPILER_WARNINGS OFF VTK_Group_Imaging ON VTK_Group_MPI OFF VTK_Group_Qt ON VTK_Group_Rendering ON VTK_Group_StandAlone ON VTK_Group_Tk ON VTK_Group_Views ON VTK_WRAP_JAVA OFF VTK_WRAP_PYTHON OFF VTK_WRAP_TCL OFF
I look forward to hear from you. Thanks.
Dear Davide,
You are right I must write some more documantation about how to install the code...
This might be related to the VTK version that you use (I have test the cose only with VTK 5.8) or the installation of VTK is not correctly done... Could you please tell me the version of Cmake and your operationg system also...
Best regards, Mehdi
On 25 Jun 2014, at 23:47, "Punzo" notifications@github.com<mailto:notifications@github.com> wrote:
Dear Mehdi,
Indeed very nice code and I'd like to use. I have tried to compile (after cmake) and I got immediately this error:
[ 7%] Generating vtkGPUMultiVolumeRayCastMapper_ShadeFS.cxx, vtkGPUMultiVolumeRayCastMapper_ShadeFS.h make[2]: ./vtkGPUMultiVolumeRayCastMapper_ShadeFS.cxx: Command not found make[2]: * [vtkGPUMultiVolumeRayCastMapper_ShadeFS.cxx] Error 127 make[1]: * [CMakeFiles/vtkGPUMultiVolumeRender.dir/all] Error 2 make: *\ [all] Error 2
I am not a VTK expert, let me know if I am doing something wrong.
I agree that few lines explaining the compiling process will be very nice.
Davide.
P.S. I am using VTK6.0.0 (which works when I compile the examples).
— Reply to this email directly or view it on GitHubhttps://github.com/mohammeb/VTKMultiVolumeRayCaster/issues/1#issuecomment-47110774.
Hi Mehdi,
I read your paper and I think you did a very good job. I read another paper of two years ago and the vtk multivolume rendering had a lot of limitation.
Do your code allow also different spacing (and size of the volume itself) for the different volume without artifacts?
So going back to my issue: I am running on ubuntu 14.04 64 bit. CMake is 2.8.11.2. ( Latest nvidia driver.) I think however that the problem can be related how I compiled VTK6.0. So as I have already reported the "main" vtk cmake variable:
BUILD_DOCUMENTATION ON BUILD_EXAMPLES ON BUILD_SHARED_LIBS ON BUILD_TESTING ON CMAKE_BUILD_TYPE Debug CMAKE_INSTALL_PREFIX /usr/local VTK_EXTRA_COMPILER_WARNINGS OFF VTK_Group_Imaging ON VTK_Group_MPI OFF VTK_Group_Qt ON VTK_Group_Rendering ON VTK_Group_StandAlone ON VTK_Group_Tk ON VTK_Group_Views ON VTK_WRAP_JAVA OFF VTK_WRAP_PYTHON OFF VTK_WRAP_TCL OFF
and with this settings I didn't have issues during the compilation of the VTK examples or small code of mine. If you can send me the list of variables that you used in the compilation of vtk5.8 I can try using the same setting of yours. I mean that I'd like to know if I need for example the wrapper. If you think can be useful I can send you the list of all the variable (the advanced mode).
Thank very much for your support.
Cheers,
Davide.
On 6/25/2014 7:05 PM, Mohammadmehdi wrote:
Dear Davide,
You are right I must write some more documantation about how to install the code...
This might be related to the VTK version that you use (I have test the cose only with VTK 5.8) or the installation of VTK is not correctly done... Could you please tell me the version of Cmake and your operationg system also...
Best regards, Mehdi
On 25 Jun 2014, at 23:47, "Punzo" notifications@github.com<mailto:notifications@github.com> wrote:
Dear Mehdi,
Indeed very nice code and I'd like to use. I have tried to compile (after cmake) and I got immediately this error:
[ 7%] Generating vtkGPUMultiVolumeRayCastMapper_ShadeFS.cxx, vtkGPUMultiVolumeRayCastMapper_ShadeFS.h make[2]: ./vtkGPUMultiVolumeRayCastMapper_ShadeFS.cxx: Command not found make[2]: * [vtkGPUMultiVolumeRayCastMapper_ShadeFS.cxx] Error 127 make[1]: * [CMakeFiles/vtkGPUMultiVolumeRender.dir/all] Error 2 make: *\ [all] Error 2
I am not a VTK expert, let me know if I am doing something wrong.
I agree that few lines explaining the compiling process will be very nice.
Davide.
P.S. I am using VTK6.0.0 (which works when I compile the examples).
— Reply to this email directly or view it on GitHubhttps://github.com/mohammeb/VTKMultiVolumeRayCaster/issues/1#issuecomment-47110774.
— Reply to this email directly or view it on GitHub https://github.com/mohammeb/VTKMultiVolumeRayCaster/issues/1#issuecomment-47137301.
This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
Dear Davide,
Thanks, infact the sceleton of the code is same as the previous paper but solving some of the issues...
Yes it does support; you can have both different size of volume and/or different spacing.
I dont see anything wrong in the compiling parameter but I cannt double check it with the actual parameter which I used since I am in Japan to attend a conference... What I can tell is that I did not changed any default parameter. I guess your cmake can not found the VTK build files somehow...
Best regards, Mehdi
On 26 Jun 2014, at 03:49, "Davide Punzo" notifications@github.com<mailto:notifications@github.com> wrote:
Hi Mehdi,
I read your paper and I think you did a very good job. I read another paper of two years ago and the vtk multivolume rendering had a lot of limitation.
Do your code allow also different spacing (and size of the volume itself) for the different volume without artifacts?
So going back to my issue: I am running on ubuntu 14.04 64 bit. CMake is 2.8.11.2. ( Latest nvidia driver.) I think however that the problem can be related how I compiled VTK6.0. So as I have already reported the "main" vtk cmake variable:
BUILD_DOCUMENTATION ON BUILD_EXAMPLES ON BUILD_SHARED_LIBS ON BUILD_TESTING ON CMAKE_BUILD_TYPE Debug CMAKE_INSTALL_PREFIX /usr/local VTK_EXTRA_COMPILER_WARNINGS OFF VTK_Group_Imaging ON VTK_Group_MPI OFF VTK_Group_Qt ON VTK_Group_Rendering ON VTK_Group_StandAlone ON VTK_Group_Tk ON VTK_Group_Views ON VTK_WRAP_JAVA OFF VTK_WRAP_PYTHON OFF VTK_WRAP_TCL OFF
and with this settings I didn't have issues during the compilation of the VTK examples or small code of mine. If you can send me the list of variables that you used in the compilation of vtk5.8 I can try using the same setting of yours. I mean that I'd like to know if I need for example the wrapper. If you think can be useful I can send you the list of all the variable (the advanced mode).
Thank very much for your support.
Cheers,
Davide.
On 6/25/2014 7:05 PM, Mohammadmehdi wrote:
Dear Davide,
You are right I must write some more documantation about how to install the code...
This might be related to the VTK version that you use (I have test the cose only with VTK 5.8) or the installation of VTK is not correctly done... Could you please tell me the version of Cmake and your operationg system also...
Best regards, Mehdi
On 25 Jun 2014, at 23:47, "Punzo" notifications@github.com<mailto:notifications@github.commailto:notifications@github.com> wrote:
Dear Mehdi,
Indeed very nice code and I'd like to use. I have tried to compile (after cmake) and I got immediately this error:
[ 7%] Generating vtkGPUMultiVolumeRayCastMapper_ShadeFS.cxx, vtkGPUMultiVolumeRayCastMapper_ShadeFS.h make[2]: ./vtkGPUMultiVolumeRayCastMapper_ShadeFS.cxx: Command not found make[2]: * [vtkGPUMultiVolumeRayCastMapper_ShadeFS.cxx] Error 127 make[1]: * [CMakeFiles/vtkGPUMultiVolumeRender.dir/all] Error 2 make: *\ [all] Error 2
I am not a VTK expert, let me know if I am doing something wrong.
I agree that few lines explaining the compiling process will be very nice.
Davide.
P.S. I am using VTK6.0.0 (which works when I compile the examples).
— Reply to this email directly or view it on GitHubhttps://github.com/mohammeb/VTKMultiVolumeRayCaster/issues/1#issuecomment-47110774.
— Reply to this email directly or view it on GitHub https://github.com/mohammeb/VTKMultiVolumeRayCaster/issues/1#issuecomment-47137301.
This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
— Reply to this email directly or view it on GitHubhttps://github.com/mohammeb/VTKMultiVolumeRayCaster/issues/1#issuecomment-47142557.
@Punzo I think the code is not compatible with VTK 6. VTK developers reformat files and are not really worried about backwards compatibility. I had the same error than you the first time I tried to compile it. That error trying to execute a cxx file is because cmake have not found vtkEncodeString. You should go to the CMakeLists and modify the lines: (-) COMMAND ${VTK_ENCODESTRING_EXE} (+) COMMAND /your/path/to/VTK/bin/vtkEncodeString-6.2
I have also added to CMake: include_directories(${PROJECT_SOURCE_DIR})
The error I have now is that it cannot find: #include "vtkVolumeRenderingFactory.h" I have checked in VTK git repo and they don't have it, so it must be a re-factored file. It should be easy to solve by @mohammeb, with a bit of playing in VTK 6! I am not going to use this software in the short term, so sorry to not provide any extra help.
Good luck!
Hi Pablo,
thanks you very much for the information, it was very helpful. Indeed I have also got your same issue about the "vtkVolumeRenderingFactory.h".
Cheers,
Davide.
Hi All,
I am actually planning on porting your code to VTK6 in the near future, would be happy to contribute it back if you are interested.
Best,
Hi, I try to import this project to VTK6.3. I succee import into VTK Library (VTKRenderVolumeOpenGL and VTKRenderVolume) but with wrong result. I can't see the second volume.
I'm sure the transfer function is containing some values in my data. But I just can't see it.
P.S. I got some wrong information.
Warning: In D:\SVNData\BCBTI\Lib\VTKx64\Common\Transforms\vtkTransform.cxx, line 194 vtkTransform (0000000005DFDDE0): InternalUpdate: doing hack to support legacy code. This is deprecated in VTK 4.2. May be removed in a future version.
Thanks.
Hello, I think it's my fault. When I adjust my transfer function of secondary volume, it's display on screen. But I have another problem. If I need to improve its performance, what should I do? By the way, my data is 512_512_400. the secondary data is 256 cube.
Hei, What is the fps now? Which machine are you using?
On 17 Oct 2015, at 20:24, La-La,Chen notifications@github.com<mailto:notifications@github.com> wrote:
Hello, I think it's my fault. When I adjust my transfer function of secondary volume, it's display on screen. But I have another problem. If I need to improve its performance, what should I do? By the way, my data is 512512400. the secondary data is 256 cube.
Reply to this email directly or view it on GitHubhttps://github.com/mohammeb/VTKMultiVolumeRayCaster/issues/1#issuecomment-148933821.
Hi, the fps is 1.26 run two volumes with 512 x 512 x 400 and 256^3 .
And my machine is as follow : CPU : Xeon E1231-v3 3.40GHz VGA : Nvidia 960GTX 2GB ram.
I will try to build on x64-release. If I have any result, I will tell you.
By the way, I build this with x64-debug on visual studio 2013.
Thanks.
I find the reason of my problem.
void vtkKWScalarField::Update()
GLint width;
glGetIntegerv(vtkgl::MAX_3D_TEXTURE_SIZE,&width);
this->Loaded=textureSize[0]<=width && textureSize[1]<=width && textureSize[2]<=width;//There is the point cause we needs to loading each frame.
Can you tell me some information about this ?
Thanks,
I think your GPU is not capable of loading big 3d textures in its memory... What kind and model of GPU are you using?
On 18 Oct 2015, at 11:32, La-La,Chen notifications@github.com<mailto:notifications@github.com> wrote:
I find the reason of my problem.
void vtkKWScalarField::Update() GLint width; glGetIntegerv(vtkgl::MAX_3D_TEXTURE_SIZE,&width); this->Loaded=textureSize[0]<=width && textureSize[1]<=width && textureSize[2]<=width;//There is the point cause we needs to loading each frame.
Can you tell me some information about this ?
Thanks,
Reply to this email directly or view it on GitHubhttps://github.com/mohammeb/VTKMultiVolumeRayCaster/issues/1#issuecomment-148987915.
I'm survey my problem. And I find a clue.
In function RenderSubVolume int loaded = texture!=0 && texture->IsLoaded() && this->GetTransformedInput()->GetMTime()<=texture->GetBuildTime() && (this->GetMaskInput() ? this->GetMaskInput()->GetMTime() <= texture->GetBuildTime() : true) && texture->GetLoadedCellFlag()==this->CellFlag;
In vtkOpenGLGPURenderMapper, Load is false only in first frame. But is vtkMultiOpenGLRenderMapper. Load is always false.
I can see the result and the result seems right.
But I don't know why I get fail resulf of loaded(loaded == false).
Can you run your code and test this line is always false each frame?
After test, I find I get loaded failure of this line. (this->GetTransformedInput()->GetMTime()<=texture->GetBuildTime() ) I will survey it and tell you the result.
thanks.
Sorry. I think I find the result.
I modify several lines for build success. But I misunderstand you means.
In version VTK6.3, Update function is removed. I modify the line [this->TransformedInput->Update();] to [this->TransformedInput->Modified();] when mapper is checking invalid rendering.
I'm sorry about this.
MeshRenderer Static Single + SliceRenderer Static Single + VolumeRendere Static Single:
Import Time:
Rendering Time of MeshRendrer:
Rendering Time of SliceRenderer:
Rendering Time of VolumeRenderer:
Total: 40.3189 ms Average: 20.1595 ms Standard deviation: TODO ms
Total: 2884.64 ms Average: 8.24183 ms Standard deviation: TODO ms
Total: 2900.12 ms Average: 16.5721 ms Standard deviation: TODO ms
MeshRenderer Static Single + SliceRenderer Static Single + VolumeRendere Static Single:
Import Time:
Rendering Time of MeshRendrer:
Rendering Time of SliceRenderer:
Rendering Time of VolumeRenderer:
Total: 24.6881 ms Average: 8.22935 ms Standard deviation: TODO ms
Total: 2863.67 ms Average: 8.22894 ms Standard deviation: TODO ms
Total: 2880.25 ms Average: 16.5532 ms Standard deviation: TODO ms
MeshRenderer Static Single + SliceRenderer Static Single + VolumeRendere Static Single:
Import Time:
Rendering Time of MeshRendrer:
Rendering Time of SliceRenderer:
Rendering Time of VolumeRenderer:
Total: 36.7 ms Average: 18.35 ms Standard deviation: TODO ms
Total: 2889.36 ms Average: 8.20841 ms Standard deviation: TODO ms
Total: 2908.55 ms Average: 16.5259 ms Standard deviation: TODO ms
MeshRenderer Static Multi + SliceRenderer Static Multi + VolumeRenderer Static Multi:
Import Time 1:
Import Time 2:
Rendering Time of MeshRendrer:
Rendering Time of SliceRenderer:
Rendering Time of VolumeRenderer:
Total: 29.553 ms Average: 14.7765 ms Standard deviation: TODO ms
Total: 2766.74 ms Average: 8.23436 ms Standard deviation: TODO ms
Total: 2783.27 ms Average: 16.5671 ms Standard deviation: TODO ms
MeshRenderer Static Multi + SliceRenderer Static Multi + VolumeRenderer Static Multi:
Import Time 1:
Import Time 2:
Rendering Time of MeshRendrer:
Rendering Time of SliceRenderer:
Rendering Time of VolumeRenderer:
Total: 13.4622 ms Average: 4.48741 ms Standard deviation: TODO ms
Total: 3066.81 ms Average: 8.20002 ms Standard deviation: TODO ms
Total: 3085.27 ms Average: 16.4988 ms Standard deviation: TODO ms
MeshRenderer Static Multi + SliceRenderer Static Multi + VolumeRenderer Static Multi:
Import Time 1:
Import Time 2:
Rendering Time of MeshRendrer:
Rendering Time of SliceRenderer:
Rendering Time of VolumeRenderer:
Total: 15.2439 ms Average: 7.62194 ms Standard deviation: TODO ms
Total: 2953.87 ms Average: 8.2052 ms Standard deviation: TODO ms
Total: 2969.55 ms Average: 16.4975 ms Standard deviation: TODO ms
MeshRenderer Dynamic Multi + SliceRenderer Dynamic Multi+ VolumeRenderer Dynamic Multi:
Import Time Dynamic 1:
Import Time Dynamic 2:
Rendering Time of MeshRendrer:
Total: 1.30041 ms Average: 0.130041 ms Standard deviation: TODO ms
Rendering Time of SliceRenderer:
Total: 203.073 ms Average: 20.3073 ms Standard deviation: TODO ms
Rendering Time of VolumeRenderer:
Total: 54.7343 ms Average: 6.84179 ms Standard deviation: TODO ms
Total: 2929.53 ms Average: 9.15477 ms Standard deviation: TODO ms
Total: 3044.85 ms Average: 19.0303 ms Standard deviation: TODO ms
MeshRenderer Dynamic Multi + SliceRenderer Dynamic Multi+ VolumeRenderer Dynamic Multi:
Import Time Dynamic 1:
Import Time Dynamic 2:
Rendering Time of MeshRendrer:
Total: 2.65003 ms Average: 0.294447 ms Standard deviation: TODO ms
Rendering Time of SliceRenderer:
Total: 171.87 ms Average: 17.187 ms Standard deviation: TODO ms
Rendering Time of VolumeRenderer:
Total: 42.838 ms Average: 5.35474 ms Standard deviation: TODO ms
Total: 2599.62 ms Average: 9.08958 ms Standard deviation: TODO ms
Total: 2698.82 ms Average: 18.8729 ms Standard deviation: TODO ms
MeshRenderer Dynamic Multi + SliceRenderer Dynamic Multi+ VolumeRenderer Dynamic Multi:
Import Time Dynamic 1:
Import Time Dynamic 2:
Rendering Time of MeshRendrer:
Total: 3.25909 ms Average: 0.325909 ms Standard deviation: TODO ms
Rendering Time of SliceRenderer:
Total: 138.657 ms Average: 12.6052 ms Standard deviation: TODO ms
Rendering Time of VolumeRenderer:
Total: 66.2205 ms Average: 7.35784 ms Standard deviation: TODO ms
Total: 2667.62 ms Average: 9.26258 ms Standard deviation: TODO ms
Total: 2785.43 ms Average: 19.3433 ms Standard deviation: TODO ms
MeshRenderer Dynamic Single + SliceRenderer Dynamic Single + Volume Dynamic Single:
Import Time Dynamic:
Rendering Time of MeshRendrer:
Total: 0.31143 ms Average: 0.0239562 ms Standard deviation: TODO ms
Rendering Time of SliceRenderer:
Total: 133.489 ms Average: 11.1241 ms Standard deviation: TODO ms
Rendering Time of VolumeRenderer:
Total: 21.2943 ms Average: 1.93584 ms Standard deviation: TODO ms
Total: 2965.82 ms Average: 8.72299 ms Standard deviation: TODO ms
Total: 2991.7 ms Average: 17.5982 ms Standard deviation: TODO ms
MeshRenderer Dynamic Single + SliceRenderer Dynamic Single + Volume Dynamic Single:
Import Time Dynamic:
Rendering Time of MeshRendrer:
Total: 0.368362 ms Average: 0.0283355 ms Standard deviation: TODO ms
Rendering Time of SliceRenderer:
Total: 153.776 ms Average: 11.8289 ms Standard deviation: TODO ms
Rendering Time of VolumeRenderer:
Total: 16.5053 ms Average: 1.50048 ms Standard deviation: TODO ms
Total: 2718.72 ms Average: 8.65834 ms Standard deviation: TODO ms
Total: 2770.69 ms Average: 17.6477 ms Standard deviation: TODO ms
MeshRenderer Dynamic Single + SliceRenderer Dynamic Single + Volume Dynamic Single:
Import Time Dynamic:
Rendering Time of MeshRendrer:
Total: 0.243382 ms Average: 0.0202818 ms Standard deviation: TODO ms
Rendering Time of SliceRenderer:
Total: 106.639 ms Average: 9.69448 ms Standard deviation: TODO ms
Rendering Time of VolumeRenderer:
Total: 12.8235 ms Average: 1.28235 ms Standard deviation: TODO ms
Total: 2711.01 ms Average: 8.57915 ms Standard deviation: TODO ms
Total: 2758.79 ms Average: 17.4607 ms Standard deviation: TODO ms
Hi, Thanks for sharing the code. I am completely new to VTK and of course multi-volume ray casting. Until now, I have installed VTK. I tried to compile the code thus provided using cmake. A solution file for the multivolume demo was created. I built it and nothing happened. I have no idea what to do next. how to use the code u provided. Please help me out with few basic installation steps and how to use the code. I have done few examples using VTK. Anyone, please help me. I really appreciate any help.
Hi there, thanks for sharing your code! I am trying to compile it using cmake in the git directory, but facing a problem not finding:
include "vtkVolumeRenderingFactory.h"
and also.
include <vtkstd/string>
A few lines explaining the compiling process you are using would be awesome. I haven't find vtkVolumeRenderingFactory.h in my VTK 6.2 folder.
Thanks! Pablo