Re: [Paraview] A Forward Connection Over two ssh Tunnel

ote: >> Very cool! Thanks for sharing, Axel. It will be nice to link this page >> from the Wiki as a reference/example, if that's okay. >> >> Utkarsh >> >> On Mon, Aug 18, 2014 at 6:12 PM, Huebl, Axel wrote: >>> Dear Ehsan, >>> >>>

Re: [Paraview] A Forward Connection Over two ssh Tunnel

cool! Thanks for sharing, Axel. It will be nice to link this page > from the Wiki as a reference/example, if that's okay. > > Utkarsh > > On Mon, Aug 18, 2014 at 6:12 PM, Huebl, Axel wrote: >> Dear Ehsan, >> >> I use a similar setup as Burlen, tunneling tw

Re: [Paraview] A Forward Connection Over two ssh Tunnel

Dear Ehsan, I use a similar setup as Burlen, tunneling twice over a login node to our cluster's head node. It also needs `GatewayPorts clientspecified` in the head node's sshd_config to work with maximum comfort. Feel free to check our wiki: https://github.com/ComputationalRadiationPhysics/picon

Re: [Paraview] what if you have two qt-installations?

ng > The correspinding HEADER-varinant are ok, though. > What does this tell me? > > Regards, > Bertwim > > > On 08/06/2014 11:34 AM, Huebl, Axel wrote: >> Dear Bertwim, >> >> >> good to hear that. >> >> sorry - CMAKE_PREFIX_PATH is an e

Re: [Paraview] what if you have two qt-installations?

veFileDialogEventPlayer.cxx:(.text+0x2b4): undefined reference to > `qt_filedialog_save_filename_hook' > CMakeFiles/QtTesting.dir/pqNativeFileDialogEventPlayer.cxx.o: In > function `pqNativeFileDialogEventPlayer::stop()': > > > etc. > > Any ideas? > > > >

Re: [Paraview] what if you have two qt-installations?

Dear Bertwim, have you tried prepending/setting the CMAKE_PREFIX_PATH to your qt5 install dir? Best, Axel On 05.08.2014 18:07, B.W.H. van Beest wrote: > Hi Burien, thanks for responding. > > I have done you suggested, but to no avail. > Somehow, the path to the executable qmake is not suffici

Re: [Paraview] Building Piston

Hi, looking at the piston code [1] in piston/piston_math.h that looks like a thrust-related problem to me. ``` #if THRUST_DEVICE_BACKEND == THRUST_DEVICE_BACKEND_CUDA #include "cuda_runtime.h" #else #include typedef struct float3 // ... ``` Checking Piston's `CMakeLists.txt` it

Re: [Paraview] Render View: Edit View Options Gone?

d property, so make sure you > have the "gear" toggled. > Check these posts out: > > http://www.kitware.com/blog/home/post/621 > http://www.kitware.com/blog/home/post/673 > http://www.kitware.com/blog/home/post/491 > > Utkarsh > > On Tue, Jul 8, 2014 at

[Paraview] Render View: Edit View Options Gone?

Hi, is the Button for changing lightning, "Edit View Options", in the "Render View" gone in the current master (g5493984) ? The 4.1 release still has that option. Best, Axel smime.p7s Description: S/MIME Cryptographic Signature ___ Powered by www.k

Re: [Paraview] Nvidia K20x on cluster

-k20m-/ Probably the K20Xm should still allow to set it to ALL_ON - can you confirm that? Good luck! Axel On 08.07.2014 12:55, Huebl, Axel wrote: > I think that is true for most cards, but K20 series should still support > to switch the "GPU Operation Mode" (GOM) via nvidia-s

Re: [Paraview] Nvidia K20x on cluster

I think that is true for most cards, but K20 series should still support to switch the "GPU Operation Mode" (GOM) via nvidia-settings: http://blogs.fau.de/zeiser/2013/09/09/xserver-virtualgl-on-nvidia-k20m-gpgpus/ nvidia-smi --gom=0 [...] (0 = ALL_ON) Best, Axel On 08.07.2014 11:33, Feli

Re: [Paraview] Nvidia K20x on cluster

To add to that question: is the PISTON / Dax support in Paraview already a stable alternative to avoid X11 at all? Thanks, Axel On 07.07.2014 16:36, Felipe Bordeu wrote: > Hello, > > We have a computer (node in a cluster) with 2 Nvidia K20x GPUs (plus a > chipset for low-end visu). Is It possi

Re: [Paraview] Config OSMesa Software Rendering

Axel Huebl On 06.07.2014 11:59, Huebl, Axel wrote: > Interesting but somehow it helps to write all the problems and steps up > again. > > I fixed the issue(s) now as follows: > > - tried a pvbatch example (parallelSphere.py) and fixed the python > install first, by setti

[Paraview] XDMF Join Strided: Memory Footprint

with striding, and using the "Calculator" filter to generate the vector field. By that the memory usage stays at a low footprint all the time. Best regards, Axel Huebl -- Axel Huebl Diploma Student Phone +49 351 260 3582 https://www.hzdr.de/crp Computational Radiation Physics Laser Partic

Re: [Paraview] Config OSMesa Software Rendering

RROR: src/ParaView/VTK/Filters/Parallel/vtkPKdTree.cxx, line 295 vtkPKdTree (0x6022160) (process 0) NumberOfDatasets = 0, cannot determine volume bounds." (same for my xdmf/hdf5 data sets). Best regards, Axel Huebl On 05.07.2014 13:47, Huebl, Axel wrote: > Hi ParaView list, > >

[Paraview] Config OSMesa Software Rendering

rendering threshold to 0MB. and usually end up with an error in OpenGLInit (see attached). Do you have any ideas? Best regards, Axel Huebl -- Axel Huebl Diploma Student Phone +49 351 260 3582 https://www.hzdr.de/crp Computational Radiation Physics Laser Particle Acceleration Division Helmhol

Re: [Paraview] Particles-in-Cells: Two XDMF files?

Hey, did anyone else try combining a mesh and a polydata data set in *one* xdmf file with paraview before? Best, Axel On 24.02.2014 15:45, Huebl, Axel wrote: > Hi ParaView mailing list, > > > we are adding paraview/xdmf support to our particle-in-cell code > PIConGPU [1] righ

[Paraview] Particles-in-Cells: Two XDMF files?

Hi ParaView mailing list, we are adding paraview/xdmf support to our particle-in-cell code PIConGPU [1] right now. To start with the general topology: The particle in cell algorithm stores field data (scalars and vectors) on a grid, in the simplest case a 3DCoRectMesh. In between the mesh points