> I click Apply and get smacked in the face with an error dialog. > I open up a PDB dataset and it is different. > GUI that four remote servers are connected. > I connect with it from my desktop (Mac OS X). > I run pvserver in parallel, and it does not give any weird outputs. > I compile with 4.1.0 and am getting some errors. > I have recently compiled paraview 4.2.0 on our clusters in the same way > header as the data is pretty static - atomic radii, colors, etc. > We should probably just statically compile the file in, or convert it to a > It looks like there is a packaging issue, and the XML file cannot be found. > vtkMolecule in addition to the vtkPolyData I think it has always produced. > I think I know the cause, the PDB reader was modified to produce a > on better ways of redistributing the other data types. > nicely work on most polydata and unstructured grid sources. > you do, I can find some workarounds of these issues. > Do you have a particular use case driving parallel PDB capability? If > string arrays in it, which it seems D3 does not handle. > would normally say that you can use the D3 filter to distribute the data > investigating various options of improving on the 4.1 functionality. > was code in 4.1 that automatically redistributed data from serial readers > They are not related to why the dataset is no longer distributed. > kind of model doesn’t usually get that big, though, probably. > molecular people would appreciate being able to visualize their stuff. > I got it from what appears to be the PDB canonical source, so I assumed our > I do not have an urgent need to view this data. We'll make sure that this is fixed very soon. The molecule data gets into the range that requires parallel Next message: Cannot get parallelism working in paraview 4.2.0 on our clusters (works with 4.1.0).Previous message: Cannot get parallelism working in paraview 4.2.0 on our clusters (works with 4.1.0).Cannot get parallelism working in paraview 4.2.0 on our clusters (works with 4.1.0) Berk Geveci berk.geveci at We should still report this, so that developers are aware of this and users who encounter this issue get a clue about what is happening and what can be done.Cannot get parallelism working in paraview 4.2.0 on our clusters (works with 4.1.0) However, implementing this is probably not trivial, it could slow down rendering, should not be necessary for commonly occurring volume sizes, and there are multiple workarounds (increase TDR delay or downsample volume), so I don't think this will be very high on the priority list of VTK developers. VtkGPUVolumeRa圜astMapper could be changed to perform processing in smaller batches. I don't see an effect of maximum GPU memory size, so maybe this mechanism is broken in Slicer or VTK. When setting GPU memory usage limit to a lower value then the volume supposed to be downscaled in the mapper to fit in that size. However, I think the GPU raycast mapper could be improved to reduce the chance of this error. While searching for solutions for TDR error on the web, I've found that many scientific software has this error and the recommended solution is to increase TDR delay, so this seems to be a common solution. I could still get TDR on maximum quality. I've "fixed" the issue by increasing TDR delay to 10 seconds (by adding TdrDelay=10 to registry ) and setting the image's data type to unsigned char, and using Adaptive or Normal setting. It seems that the GPU is simply too busy because of the huge workload. Details were described in the system logs: it was a TDR (, ). Same steps doesn't cause a crash in 4.8.1 Switch to VR, enable rendering, slide the transfer function down to about 5, center and zoom into the specimen. This is on a laptop with i7 chip + Quadro K4100M GPU rendering is set to 4GB (which is the memory this card has). This is with regular volume rendering, not with experimental option. 0004572: Volume rendering gives TDR error on windows 10 with quadro K4100MĤ.9.0- r27246 on windows 10 crashes with a dataset that works fine on 4.8.1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |