Re: [Paraview] ParaView + OpenVR (UNCLASSIFIED)

[Benson Muite]

Hi,

Does binary release version work for you? (At present only Windows is 
available), seem to be a few things to fix on Linux & Mac.



Have you tried build using flags similar to binary release version?
https://blog.kitware.com/taking-paraview-into-virtual-reality/

Benson

On 01/19/2018 01:29 AM, Su, Simon M CIV USARMY RDECOM ARL (US) wrote:

CLASSIFICATION: UNCLASSIFIED

Hello,

I am wondering how to build a version of ParaView with OpenVR plugin? Which 
version of OpenVR shall I use? I used the OpenVR from 
https://github.com/ValveSoftware/openvr  with just basic/minimal cmake option. 
I am using the following  cmake line for ParaView

cmake ..\paraview -DCMAKE_INSTALL_PREFIX=U:\tools\ParaView\ParaView 
-DCMAKE_BUILD_TYPE=Release -G Ninja -DPARAVIEW_ENABLE_PYTHON:BOOL=ON 
-DBUILD_TESTING:BOOL=OFF -DPARAVIEW_QT_VERSION=5 -DPARAVIEW_USE_MPI:BOOL=ON 
-DPARAVIEW_USE_VISITBRIDGE:BOOL=ON 
-DBOOST_INCLUDEDIR=U:/tools/boost/boost-1.65.1/include/boost-1_65_1 
-DBOOST_ROOT=U:/tools/boost/boost-1.65.1 -DModule_vtkAcceleratorsVTKm:BOOL=ON 
-DModule_vtkRenderingOpenVR:BOOL=ON -DPARAVIEW_BUILD_PLUGIN_OpenVR:BOOL=ON 
-DOPENVR_INCLUDE_DIR=U:/tools/OpenVR/OpenVR/include 
-DOPENVR_LIBRARY=U:/tools/OpenVR/OpenVR/lib/openvr_api64.lib

I am running into the following error

C:\Users\one\build\ParaView\b>ninja
[47/14039] Building CXX object 
VTK\Rendering\OpenVR\CMakeFiles\vtkRenderingOpenVR.dir\vtkOpenVRRenderWindow.cxx.obj
FAILED: 
VTK/Rendering/OpenVR/CMakeFiles/vtkRenderingOpenVR.dir/vtkOpenVRRenderWindow.cxx.obj
C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx64\x64\cl.exe
  /nologo /TP -DMPICH_IGNORE_CXX_SEEK -DVTK_IN_VTK -D_CRT_NONSTDC_NO_DEPRECATE 
-D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS -D_SCL_SECURE_NO_DEPRECATE 
-D_SCL_SECURE_NO_WARNINGS -DvtkRenderingOpenVR_EXPORTS -I. 
-IVTK\Rendering\OpenVR 
-IC:\Users\one\build\ParaView\paraview\VTK\Rendering\OpenVR -IVTK\Common\Core 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\Core -IVTK\Utilities\KWIML 
-IC:\Users\one\build\ParaView\paraview\VTK\Utilities\KWIML 
-IVTK\Utilities\KWSys 
-IC:\Users\one\build\ParaView\paraview\VTK\Utilities\KWSys 
-IVTK\ThirdParty\utf8 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\utf8 
-IVTK\Filters\Sources 
-IC:\Users\one\build\ParaView\paraview\VTK\Filters\Sources 
-IVTK\Common\ComputationalGeometry 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\ComputationalGeometry 
-IVTK\Common\DataModel 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\DataModel -IVTK\Common\Math 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\Math -IVTK\Common\Misc 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\Misc -IVTK\Common\System 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\System 
-IVTK\Common\Transforms 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\Transforms 
-IVTK\Common\ExecutionModel 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\ExecutionModel 
-IVTK\Filters\Core -IC:\Users\one\build\ParaView\paraview\VTK\Filters\Core 
-IVTK\Filters\General 
-IC:\Users\one\build\ParaView\paraview\VTK\Filters\General -IVTK\IO\Image 
-IC:\Users\one\build\ParaView\paraview\VTK\IO\Image -IVTK\Utilities\DICOMParser 
-IC:\Users\one\build\ParaView\paraview\VTK\Utilities\DICOMParser 
-IVTK\Utilities\MetaIO\vtkmetaio -IVTK\Utilities\MetaIO 
-IC:\Users\one\build\ParaView\paraview\VTK\Utilities\MetaIO 
-IVTK\ThirdParty\zlib 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\zlib 
-IVTK\ThirdParty\jpeg 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\jpeg -IVTK\ThirdParty\png 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\png 
-IVTK\ThirdParty\tiff\vtktiff\libtiff -IVTK\ThirdParty\tiff 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\tiff -IVTK\IO\XMLParser 
-IC:\Users\one\build\ParaView\paraview\VTK\IO\XMLParser -IVTK\IO\Core 
-IC:\Users\one\build\ParaView\paraview\VTK\IO\Core 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\lz4\vtklz4\lib 
-IVTK\ThirdParty\lz4\vtklz4 -IVTK\ThirdParty\lz4 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\lz4 
-IVTK\ThirdParty\expat 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\expat 
-IVTK\Imaging\Sources 
-IC:\Users\one\build\ParaView\paraview\VTK\Imaging\Sources -IVTK\Imaging\Core 
-IC:\Users\one\build\ParaView\paraview\VTK\Imaging\Core -IVTK\Interaction\Style 
-IC:\Users\one\build\ParaView\paraview\VTK\Interaction\Style 
-IVTK\Filters\Extraction 
-IC:\Users\one\build\ParaView\paraview\VTK\Filters\Extraction 
-IVTK\Filters\Statistics 
-IC:\Users\one\build\ParaView\paraview\VTK\Filters\Statistics 
-IVTK\Imaging\Fourier 
-IC:\Users\one\build\ParaView\paraview\VTK\Imaging\Fourier 
-IVTK\ThirdParty\alglib 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\alglib 
-IVTK\Rendering\Core -IC:\Users\one\build\ParaView\paraview\VTK\Rendering\Core 
-IVTK\Common\Color -IC:\Users\one\build\ParaView\paraview\VTK\Common\Color 
-IVTK\Filters\Geometry 
-IC:\Users\one\build\ParaView\paraview\VTK\Filters\Geometry 
-IVTK\Interaction\Widgets 

[Paraview] ParaView + OpenVR (UNCLASSIFIED)

[Su, Simon M CIV USARMY RDECOM ARL (US)]

CLASSIFICATION: UNCLASSIFIED

Hello,

I am wondering how to build a version of ParaView with OpenVR plugin? Which 
version of OpenVR shall I use? I used the OpenVR from 
https://github.com/ValveSoftware/openvr  with just basic/minimal cmake option. 
I am using the following  cmake line for ParaView 

cmake ..\paraview -DCMAKE_INSTALL_PREFIX=U:\tools\ParaView\ParaView 
-DCMAKE_BUILD_TYPE=Release -G Ninja -DPARAVIEW_ENABLE_PYTHON:BOOL=ON 
-DBUILD_TESTING:BOOL=OFF -DPARAVIEW_QT_VERSION=5 -DPARAVIEW_USE_MPI:BOOL=ON 
-DPARAVIEW_USE_VISITBRIDGE:BOOL=ON 
-DBOOST_INCLUDEDIR=U:/tools/boost/boost-1.65.1/include/boost-1_65_1 
-DBOOST_ROOT=U:/tools/boost/boost-1.65.1 -DModule_vtkAcceleratorsVTKm:BOOL=ON 
-DModule_vtkRenderingOpenVR:BOOL=ON -DPARAVIEW_BUILD_PLUGIN_OpenVR:BOOL=ON 
-DOPENVR_INCLUDE_DIR=U:/tools/OpenVR/OpenVR/include 
-DOPENVR_LIBRARY=U:/tools/OpenVR/OpenVR/lib/openvr_api64.lib

I am running into the following error

C:\Users\one\build\ParaView\b>ninja
[47/14039] Building CXX object 
VTK\Rendering\OpenVR\CMakeFiles\vtkRenderingOpenVR.dir\vtkOpenVRRenderWindow.cxx.obj
FAILED: 
VTK/Rendering/OpenVR/CMakeFiles/vtkRenderingOpenVR.dir/vtkOpenVRRenderWindow.cxx.obj
C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx64\x64\cl.exe
  /nologo /TP -DMPICH_IGNORE_CXX_SEEK -DVTK_IN_VTK -D_CRT_NONSTDC_NO_DEPRECATE 
-D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS -D_SCL_SECURE_NO_DEPRECATE 
-D_SCL_SECURE_NO_WARNINGS -DvtkRenderingOpenVR_EXPORTS -I. 
-IVTK\Rendering\OpenVR 
-IC:\Users\one\build\ParaView\paraview\VTK\Rendering\OpenVR -IVTK\Common\Core 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\Core -IVTK\Utilities\KWIML 
-IC:\Users\one\build\ParaView\paraview\VTK\Utilities\KWIML 
-IVTK\Utilities\KWSys 
-IC:\Users\one\build\ParaView\paraview\VTK\Utilities\KWSys 
-IVTK\ThirdParty\utf8 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\utf8 
-IVTK\Filters\Sources 
-IC:\Users\one\build\ParaView\paraview\VTK\Filters\Sources 
-IVTK\Common\ComputationalGeometry 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\ComputationalGeometry 
-IVTK\Common\DataModel 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\DataModel -IVTK\Common\Math 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\Math -IVTK\Common\Misc 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\Misc -IVTK\Common\System 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\System 
-IVTK\Common\Transforms 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\Transforms 
-IVTK\Common\ExecutionModel 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\ExecutionModel 
-IVTK\Filters\Core -IC:\Users\one\build\ParaView\paraview\VTK\Filters\Core 
-IVTK\Filters\General 
-IC:\Users\one\build\ParaView\paraview\VTK\Filters\General -IVTK\IO\Image 
-IC:\Users\one\build\ParaView\paraview\VTK\IO\Image -IVTK\Utilities\DICOMParser 
-IC:\Users\one\build\ParaView\paraview\VTK\Utilities\DICOMParser 
-IVTK\Utilities\MetaIO\vtkmetaio -IVTK\Utilities\MetaIO 
-IC:\Users\one\build\ParaView\paraview\VTK\Utilities\MetaIO 
-IVTK\ThirdParty\zlib 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\zlib 
-IVTK\ThirdParty\jpeg 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\jpeg -IVTK\ThirdParty\png 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\png 
-IVTK\ThirdParty\tiff\vtktiff\libtiff -IVTK\ThirdParty\tiff 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\tiff -IVTK\IO\XMLParser 
-IC:\Users\one\build\ParaView\paraview\VTK\IO\XMLParser -IVTK\IO\Core 
-IC:\Users\one\build\ParaView\paraview\VTK\IO\Core 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\lz4\vtklz4\lib 
-IVTK\ThirdParty\lz4\vtklz4 -IVTK\ThirdParty\lz4 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\lz4 
-IVTK\ThirdParty\expat 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\expat 
-IVTK\Imaging\Sources 
-IC:\Users\one\build\ParaView\paraview\VTK\Imaging\Sources -IVTK\Imaging\Core 
-IC:\Users\one\build\ParaView\paraview\VTK\Imaging\Core -IVTK\Interaction\Style 
-IC:\Users\one\build\ParaView\paraview\VTK\Interaction\Style 
-IVTK\Filters\Extraction 
-IC:\Users\one\build\ParaView\paraview\VTK\Filters\Extraction 
-IVTK\Filters\Statistics 
-IC:\Users\one\build\ParaView\paraview\VTK\Filters\Statistics 
-IVTK\Imaging\Fourier 
-IC:\Users\one\build\ParaView\paraview\VTK\Imaging\Fourier 
-IVTK\ThirdParty\alglib 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\alglib 
-IVTK\Rendering\Core -IC:\Users\one\build\ParaView\paraview\VTK\Rendering\Core 
-IVTK\Common\Color -IC:\Users\one\build\ParaView\paraview\VTK\Common\Color 
-IVTK\Filters\Geometry 
-IC:\Users\one\build\ParaView\paraview\VTK\Filters\Geometry 
-IVTK\Interaction\Widgets 
-IC:\Users\one\build\ParaView\paraview\VTK\Interaction\Widgets 
-IVTK\Filters\Hybrid -IC:\Users\one\build\ParaView\paraview\VTK\Filters\Hybrid 
-IVTK\Filters\Modeling 
-IC:\Users\one\build\ParaView\paraview\VTK\Filters\Modeling -IVTK\Imaging\Color 
-IC:\Users\one\build\ParaView\paraview\VTK\Imaging\Color -IVTK\Imaging\General 

Re: [Paraview] ParaView 5.x not showing all objects available in Pipeline Browser

[Omid Mahabadi]

Thanks Ken. I will try this on other machines. BTW I have version 3.0 of
OpenGL:
$ glxinfo | grep "OpenGL version"
OpenGL version string: 3.0 Mesa 10.5.9

Best regards,
Omid
--
Omid Mahabadi, Ph.D., P.Eng.
President & Geomechanics Specialist
Geomechanica Inc

Suite 900 – 390 Bay Street,
Toronto, On, M5H 2Y2
Canada

http://www.geomechanica.com/
Tel: +1-647-478-9767
Cell: +1-416-824-2408
Skype: omid82

Standalone licenses and cloud subscriptions for Irazu 2D/3D geomechanics
simulation software are now available: http://irazu.geomechanica.com


This message contains confidential information and is intended only for the
individual named. If you are not the named addressee, you should not
disseminate, distribute or copy this email. Please notify me immediately by
email if you have received this email by mistake and delete this email from
your system. Email transmission cannot be guaranteed to be secure or
error-free, as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses. The sender,
therefore, does not accept liability for any errors or omissions in the
contents of this message which arise as a result of email transmission. If
verification is required, please request a hard-copy version. Geomechanica
Inc.

On Tue, Jan 16, 2018 at 10:31 AM, Moreland, Kenneth 
wrote:

> Omid,
>
>
>
> The only other thing I can think of is that there is something odd about
> the OpenGL driver/hardware on your system that for some reason is not
> supporting the coincident topology resolution in ParaView. ParaView changed
> its rendering system from OpenGL 1.3 to OpenGL 3.1 in version 5, the
> version that you report seeing the issue.
>
>
>
> Once again, I recommend trying to run ParaView on a completely different
> computer if you can find access to one. You might also try updating the
> OpenGL drivers on your computer. Beyond that, I am out of ideas.
>
>
>
> -Ken
>
>
>
> *From: *Omid Mahabadi 
> *Date: *Tuesday, January 16, 2018 at 7:58 AM
> *To: *"Moreland, Kenneth" 
> *Cc: *"paraview@paraview.org" 
>
> *Subject: *[EXTERNAL] Re: [Paraview] ParaView 5.x not showing all objects
> available in Pipeline Browser
>
>
>
> Hi Ken,
>
> Thanks for your feedback and sorry for my late reply. Somehow I didn't get
> this message and only found your reply after searching in my mailbox.
>
>
>
> I tried various values for the Z Shift, increasing it by one order of
> magnitude until reaching a value of 200, restarting in between changes.
> This didn't help.
>
>
>
> I haven't really made any other changes in ParaView settings. I even
> restored to defaults a couple of times. I've been using Linux Mint 17 and
> have also experienced the same issue on Ubuntu 14.04 both 64 bit.
>
>
>
> Thanks
>
>
> Best regards,
>
> Omid
>
>
>
>
>
>
>
> On Wed, Jan 10, 2018 at 12:45 PM, Moreland, Kenneth 
> wrote:
>
> Omid,
>
>
>
> Even after applying the Threshold filter, I cannot replicate your problem.
> I’ve tried on both ParaView 5.2 and 5.4. Both work fine for me.
>
>
>
> My settings are the default. “Resolve Coincident Topology” is set to
> “Shift z-buffer when rendering lines and points”. “Z Shift” is set to
> 0.002. (Polygon offset should not matter in this mode.) You could try
> increasing the Z Shift to fix the problem. Note that you have to restart
> ParaView in order for these options to take effect.
>
>
>
> It is possible that there is some quirk with the rendering system on your
> computer that does not implement the topology resolution. Do you happen to
> have another computer on which you can try to run this? I also noted that
> if I turn on OSPRay rendering, I do get the missing line issue you
> describe. There might be other display/rendering parameters that cause
> issues. But the defaults should be fine, so unless you have done some
> tinkering you should be OK.
>
>
>
> -Ken
>
>
>
> *From:* Omid Mahabadi [mailto:omid.mahab...@geomechanica.com]
> *Sent:* Wednesday, January 10, 2018 9:21 AM
> *To:* Moreland, Kenneth 
> *Cc:* paraview@paraview.org
> *Subject:* [EXTERNAL] Re: [Paraview] ParaView 5.x not showing all objects
> available in Pipeline Browser
>
>
>
> Hi Ken,
>
> Thanks for the detailed reply. I could not get anything out of the
> settings dialog as per your suggestion. Did you have a combination of those
> settings that might work for my files?
>
> I can also see the image you sent; that's usually fine. However, I
> typically apply a Threshold filter to the _basic_ files (Scalar: alive;
> min: 0.1; max: 1). In this case, the _basic_ object is always drawn in
> front of the _broken_joint_ object.
>
> In addition, I visualize dozens of these files every day so Transforming
> every single object is a bit tedious.
>
> Thank you,
>
> Omid
>
>
>
>
>
> On Mon, Jan 8, 2018 at 5:56 PM, Moreland, Kenneth 
> wrote:
>
> Omid,
>
>
>
> I am unable 

Re: [Paraview] Reading netCDF files Earth models

[Moreland, Kenneth]

Manochehr,

ParaView always renders in a Cartesian space. So if you want the lat/lon/depth 
values to look like a sphere, the coordinates have to be converted and you will 
loose the original values. I can see the point of your use case. It just never 
came up before. It seems reasonable to be able to save the original lat/lon 
values in a field, so I raised a bug for it.

https://gitlab.kitware.com/paraview/paraview/issues/17943

As far as getting the coordinates in a script, it is possible but not 
recommended. If you need to access field or coordinate values directly, it is 
usually best to do so in a programmable filter.

-Ken

Sent from my iPad

On Jan 18, 2018, at 7:06 AM, Manochehr Bahavar 
> wrote:

Hi Aashish,

Thank you for your reply. That will be great if it gets looked into:) Going 
back and forth between coordinate systems may be a little confusing, but I will 
give it a try and see how it works out.


Could you also point me in the right direction for getting the latitude, 
longitude and depth arrays? As I mentioned in my reply to Ken (below), using 
Python, I go as far as getting the extents and bounds but cannot get the actual 
values.

Thank you again for your quick reply and useful suggestions.

Best,

—manoch



On Jan 17, 2018, at 10:29 PM, Aashish Chaudhary 
> wrote:

Hi Manoch,

I think what you want is not possible right now but let us get back to you on 
it as something we might want to look into before we can say it for sure. One 
workaround would be you load the data (uncheck the sphere coordinate system), 
apply the filter, and then write the data back as NetCDF. It is not ideal by 
any means. You can also look into vtkSphericalTransform (if you want to convert 
data back to spherical coordinate system) but you will not get the exact shape 
of earth which is a ellipsoid (which I am not sure if you would be interested 
in anyways).

Hope this helps.

On Wed, Jan 17, 2018 at 7:12 PM Manochehr Bahavar 
> wrote:
Ken,

Thanks for your reply. The problem with that approach is that all the features 
I am interested in make sense if they are plotted on a sphere (they approximate 
the Earth surface). So, there is no builtin solution for that?

One more question: How can I access the actual latitude, longitude and depth 
parameter values using Python. I can see their extent and bounds, but I can not 
see how I can access the individual values:

temp.GetBounds()
(0.0, 359.0, -89.0, 89.0, -2750.0, 50.0)
temp.GetDimensions()
(360, 179, 57)
temp.GetExtent()
(0, 359, 0, 178, 0, 56)
temp.GetCenter()
(179.5, 0.0, -1350.0)
temp.GetNumberOfPoints()
3673080L

Really appreciate your help

—manoch


On Jan 17, 2018, at 3:57 PM, Moreland, Kenneth 
> wrote:

Manochehr,

If you uncheck the “Spherical Coordiantes” option, then the longitude, 
latitude, and depth values will be preserved as x, y, and z coordinates. 
(Instead of translated to a sphere, the data will appear in a rectangle.)

-Ken


On 1/17/18, 4:34 PM, "ParaView on behalf of Manochehr Bahavar" 
 on behalf 
of man...@iris.washington.edu> wrote:

   Hello,

   I am trying to see if I can visualize my netCDF Earth models (longitude, 
latitude,depth) using ParaView. I have been able to load the models, with the 
"Spherical Coordinates" option selected. However it appears that I now lose my 
coordinates and depth values and as a result to extract a subset, I have to use 
the depth index (not the actual depth value). Is there a way to preserve the 
latitude, longitude and depth values and work with ParaView using the actual 
values (not their index) directly?

   Thank you,

   —manoch
   ___
   Powered by www.kitware.com

   Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

   Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

   Search the list archives at: http://markmail.org/search/?q=ParaView

   Follow this link to subscribe/unsubscribe:
   https://paraview.org/mailman/listinfo/paraview



___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

___
Powered by www.kitware.com

Visit other Kitware open-source 

Re: [Paraview] Reading netCDF files Earth models

[Manochehr Bahavar]

Hi Aashish,

Thank you for your reply. That will be great if it gets looked into:) Going 
back and forth between coordinate systems may be a little confusing, but I will 
give it a try and see how it works out.


Could you also point me in the right direction for getting the latitude, 
longitude and depth arrays? As I mentioned in my reply to Ken (below), using 
Python, I go as far as getting the extents and bounds but cannot get the actual 
values.

Thank you again for your quick reply and useful suggestions.

Best,

—manoch



> On Jan 17, 2018, at 10:29 PM, Aashish Chaudhary 
>  wrote:
> 
> Hi Manoch, 
> 
> I think what you want is not possible right now but let us get back to you on 
> it as something we might want to look into before we can say it for sure. One 
> workaround would be you load the data (uncheck the sphere coordinate system), 
> apply the filter, and then write the data back as NetCDF. It is not ideal by 
> any means. You can also look into vtkSphericalTransform (if you want to 
> convert data back to spherical coordinate system) but you will not get the 
> exact shape of earth which is a ellipsoid (which I am not sure if you would 
> be interested in anyways). 
> 
> Hope this helps. 
> 
> On Wed, Jan 17, 2018 at 7:12 PM Manochehr Bahavar  > wrote:
> Ken,
> 
> Thanks for your reply. The problem with that approach is that all the 
> features I am interested in make sense if they are plotted on a sphere (they 
> approximate the Earth surface). So, there is no builtin solution for that?
> 
> One more question: How can I access the actual latitude, longitude and depth 
> parameter values using Python. I can see their extent and bounds, but I can 
> not see how I can access the individual values:
> 
> temp.GetBounds()
> (0.0, 359.0, -89.0, 89.0, -2750.0, 50.0)
> temp.GetDimensions()
> (360, 179, 57)
> temp.GetExtent()
> (0, 359, 0, 178, 0, 56)
> temp.GetCenter()
> (179.5, 0.0, -1350.0)
> temp.GetNumberOfPoints()
> 3673080L
> 
> Really appreciate your help
> 
> —manoch
> 
> 
>> On Jan 17, 2018, at 3:57 PM, Moreland, Kenneth > > wrote:
>> 
>> Manochehr,
>> 
>> If you uncheck the “Spherical Coordiantes” option, then the longitude, 
>> latitude, and depth values will be preserved as x, y, and z coordinates. 
>> (Instead of translated to a sphere, the data will appear in a rectangle.)
>> 
>> -Ken
>> 
>> 
>> On 1/17/18, 4:34 PM, "ParaView on behalf of Manochehr Bahavar" 
>>  on 
>> behalf of man...@iris.washington.edu > 
>> wrote:
>> 
>>Hello,
>> 
>>I am trying to see if I can visualize my netCDF Earth models (longitude, 
>> latitude,depth) using ParaView. I have been able to load the models, with 
>> the "Spherical Coordinates" option selected. However it appears that I now 
>> lose my coordinates and depth values and as a result to extract a subset, I 
>> have to use the depth index (not the actual depth value). Is there a way to 
>> preserve the latitude, longitude and depth values and work with ParaView 
>> using the actual values (not their index) directly?
>> 
>>Thank you,
>> 
>>—manoch
>>___
>>Powered by www.kitware.com 
>> 
>>Visit other Kitware open-source projects at 
>> http://www.kitware.com/opensource/opensource.html 
>> 
>> 
>>Please keep messages on-topic and check the ParaView Wiki at: 
>> http://paraview.org/Wiki/ParaView 
>> 
>>Search the list archives at: http://markmail.org/search/?q=ParaView 
>> 
>> 
>>Follow this link to subscribe/unsubscribe:
>>https://paraview.org/mailman/listinfo/paraview 
>> 
>> 
>> 
> 
> ___
> Powered by www.kitware.com 
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html 
> 
> 
> Please keep messages on-topic and check the ParaView Wiki at: 
> http://paraview.org/Wiki/ParaView 
> 
> Search the list archives at: http://markmail.org/search/?q=ParaView 
> 
> 
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview 
> 

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list