[Paraview] Paraview 3.6.1 and netCDF 4

[Matthew Dillon]

Ken,

Thats great, I really appreciate it. I guess I missed this file in the  
paraview dataset. I was not able to get this particular file to load,  
however, some of the other examples in that directory work quite well  
- thanks for the resource. The reader was automatically detected, so,  
I guess there is something wrong with the structure of the files I am  
creating. This is perfect though, I had no clue if the problem was me,  
the paraview binary, or a little bit of both. Now things have been  
whittled down a bit. Thanks, have a great day.

Matthew Dillon

On Nov 12, 2009, at 1:42 PM, Moreland, Kenneth wrote:

> There is an example netCDF file that comes with the VTK test data.   
> It is identical to the one from here:
>
> http://www.unidata.ucar.edu/software/netcdf/examples/tos_O1_2001-2002.nc
>
> On retrospect, I’m not sure that the netCDF that comes with ParaView  
> is version 4.  We may need to update it.
>
> -Ken
>
>
> On 11/12/09 3:36 PM, "Matthew Dillon" <mrdillon at alaska.edu> wrote:
>
> Ken,
>
> Thanks for the reply. I have tested with both *.nc and *.ncdf, with  
> no luck on the netCDF reader showing up on the list. I generated the  
> netCDF file using the netcdf4-python (http://code.google.com/p/netcdf4-python/ 
> ) interface, using the NETCDF4 and NETCDF3-CLASSIC filetypes. Both  
> types show coherent output when using the netCDF viewer "ncdump." I  
> checked the Paraview Dataset file to see if there were any netCDF  
> files, and did not come across any. I did however see there were  
> *.h5 (hdf5) files. The documentation states that these should have a  
> viewer as well, but when I opened one of these files, I was  
> presented with the same reader list as before, with no mention to an  
> hdf5 reader.
>
> Matthew
>
> On Nov 12, 2009, at 1:22 PM, Moreland, Kenneth wrote:
>
> ParaView first uses extensions to determine file type.  Files with  
> extension .nc or .ncdf are assumed to be netCDF files.  If you are  
> using another extension it should still work so long as the  
> extension does not conflict with any other extension used.  If no  
> file extension matches you should get a dialog box asking you what  
> type of reader to use.  If the file is detected as a valid netCDF  
> file, it should show up in that list.
>
> -Ken
>
>
> On 11/12/09 1:56 PM, "Matthew Dillon" <mrdillon at alaska.edu <x-msg://36/mrdillon@alaska.edu 
> > > wrote:
>
> Hi all, I have a question. I have been using VTK for some time now,
> and have recently been focusing my efforts on Paraview. I am running
> into a problem though. I am trying to import netCDF volume data. I am
> able to import the file using the raw binary filter, which works quite
> well, however, when I try to import a netCDF file with compressed
> variables, this approach does not work. Glancing through the
> documentation, it appears that the is a netCDF reader built in,
> however it doesn't look like my file is being associated with the
> netCDF reader when opening. A little about my setup: Mac OS X 10.6.1,
> Paraview 3.6.1 binary, netCDF 4.0.1. Any help on this would be really
> appreciated. Thanks!
>
> Matthew Dillon
> _______________________________________________
> Powered by www.kitware.com <http://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
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
>
>
>
>    ****      Kenneth Moreland
>     ***      Sandia National Laboratories
> ***********
> *** *** ***  email: kmorel at sandia.gov <x-msg://36/kmorel@sandia.gov>
> **  ***  **  phone: (505) 844-8919
>     ***      web:   http://www.cs.unm.edu/~kmorel
>
>
>
>
>
>    ****      Kenneth Moreland
>     ***      Sandia National Laboratories
> ***********
> *** *** ***  email: kmorel at sandia.gov
> **  ***  **  phone: (505) 844-8919
>     ***      web:   http://www.cs.unm.edu/~kmorel
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20091112/e5d77459/attachment.htm>