[Paraview] netcdf

[Samuel Key]

Rupert,

I can't help you with netcdf files/formats. However, the following two 
items could be of help.

(1) ParaView has a Transform filter that will translate and/or scale 
and/or rotate your datum set.

(2) In the coordinate 3-tuple (x,y,z). if all of your z-values are zero, 
then PV will "come up in a "2D" mode. There is a 2D/3D toggle button 
(button number 3) in the upper left location in each display frame that 
may be of help to you.

Samuel Key

FMA Development.


On 5/15/2017 1:37 AM, Rupert Gladstone wrote:
>
> Hi, I have a question about netcdf formats.  I am developing a coupled 
> ice sheet - ocean model.  Currently both models run in the same 
> cartesian coordinate system.  The ice model outputs unstructured .vtu 
> files, which paraview reads just fine.  The ocean model outputs 
> structured netcdf files.  If I naively select the "generic and CF 
> conventions" option when reading the ocean netcdf file then the data 
> display ok, but not to scale.  It seems like the structured fields 
> have been read in just fine, but the coordinate variables have not.  I 
> don't think the netcdf files are CF compliant.  I would like to be 
> able to read in both .vtu files and netcdf files and display the data 
> sets together on the same scale.
>
> Do you know what I need to do to read in the netcdf coordinate vars 
> correctly?  I am hoping that I can simply insert a post-processing 
> step to implement some minor manipulation to the ocean model output 
> files so that Paraview can read them in to scale.  Is it simply a case 
> of renaming the coordinate variables in the netcdf file such that they 
> have the same names as the corresponding dimensions?  Note that this 
> is not in general possible as some of the coordinate variables are 
> two-dimensional variables (in the horizontal plane), though for most 
> of the simulations we plan in the near future I can enforce that the 
> coord vars will have a one to one correspondence to the dimension vars 
> (i.e. I can enforce that coord vars are 1D).
>
> Is the ordering of dimensions important?
> Is the ordering of coordinate vars important?
> Is the naming of dimensions important?
> Is the naming of coord vars important?
> Can Paraview cope with 2D coord vars?  If so, how does Paraview know 
> which coordinate var applies to which var?
>
> Thanks very much for your help.
>
> Regards,
> Rupert Gladstone
>
>
> _______________________________________________
> 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:
> http://public.kitware.com/mailman/listinfo/paraview

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170515/baa75adb/attachment.html>