It looks like the streamlines filter only accepts point data and the data on 
the mesh is cell data.  You can get around that by running the Point Data to 
Cell Data filter, although this seems like an odd restriction on the 
streamlines filter and you might want to add a feature request to the ParaView 
bug tracker if this is an issue.

-Ken


On 5/19/10 9:30 AM, "Joel Culina" <joel.cul...@acadiau.ca> wrote:



Good call!  I just need streamlines now, but the streamline filter is 'ghosted 
out'.  How do you get streamlines for my unstructured grid, unsteady data 
(i.e., I need streamlines at a fixed point in time)?

thanks
Joel

p.s. I'm getting people here converted to paraview!


-----Original Message-----
From: Moreland, Kenneth [mailto:kmo...@sandia.gov]
Sent: Wed 5/19/2010 9:51 AM
To: Joel Culina
Subject: Re: [Paraview] trouble reading in netCDF file

Are you sure that the data isn't simply flat?  It looks like the mesh extends 
on the order of 100,000 units in the x and y direction, and only about 150 
units in the height direction.  What happens if you apply the transform filter 
and scale the z by, say, 1000?

-Ken


On 5/18/10 3:58 PM, "Joel Culina" <joel.cul...@acadiau.ca> wrote:

Hi Ken,

I am now able to load FVCOM model (oceanographic) netCDF data into paraview by 
enabling Visit plug-ins (there exists a Visit plug-in for reading in FVCOM 
model data).

However, it plots variables that are functions of 3 spatial variables (in x, y 
and h) over 2D space (over x and y).  (Yet the horizontal coordinates x and y 
and the height h are all listed as 'variables' variables as opposed to 
'dimensions' variables.)  How using the appropriate filters can I derive 3D 
images; e.g. scalar fields over x, y and h?  Ultimately I wish to draw 
streamlines in 3D.

I've attached a small FVCOM file (2 time steps with 3D data).  In order to 
properly load this particular file, I had to run the following line of script:
upper1_0001_nc = VisItNETCDFDatabaseBridge(  
FileName='/array/home/jculina/Desktop/ParaView-3.8.0-RC1-Linux-x86_64/my_data/upper1_0001.nc'
 )
For some reason, it automatically reads SOME FVCOM files using the visit 
plug-in, but other FVCOM files (with similar names and .nc extension and visit 
plugins enabled), it reads in the files as netcdf files.

thanks alot!
Joel

-----Original Message-----
From: Moreland, Kenneth [mailto:kmo...@sandia.gov]
Sent: Wed 4/7/2010 11:09 AM
To: Joel Culina; paraview@paraview.org
Subject: Re: [Paraview] trouble reading in netCDF file

The netCDF reader in version understands the COARDS convention (a common subset 
of CF).  It sounds like the variable annotation you describe should be 
supported.  However, one major limitation of the netCDF reader is that it only 
supports reading variables of the same dimensions because it puts them all on 
the same grid.  So if you have selected to load variables with different 
dimensions, it will use the dimensions of the first variable and fail to load 
the rest.  That would explain the behavior you are getting since most netCDF 
files I have run into seem to have variables with low dimension listed first. 
(There is no particular reason for this.  It just seems to be what 
people/applications do.) If this is the case, you are probably also getting a 
lot of warnings from the netCDF reader about it and the Information panel will 
be missing many of your variables.  Try turning off all variables in the Object 
Inspector and turning on only one variable you are interested in.

If this is the problem, it should go away in version 3.8.  Realizing this the 
3.6 interface to the netCDF reader really sucks, I changed it to select 
dimensions instead of variables.  All variables conforming to the selected 
dimensions are loaded.  It makes using the netCDF reader much easier and 
problems like the one I described go away.  I also expanded the reader to 
understand most of the CF convention.

Unfortunately, don't use the CVS for this just yet.  I have recently discovered 
that a new netCDF reader that was apparently built for a specific use case but 
seems to screw up on most data was added to ParaView and it is overriding the 
existing netCDF reader.  We are trying to work on a resolution.

-Ken


On 4/6/10 6:02 PM, "Joel Culina" <joel.cul...@acadiau.ca> wrote:

Hi,

Thank you Ken for responding.

I suspect that your diagnosis is correct; the root of the problem, I believe, 
is that I am reading in netCDF data that follows the CF convention.   In 
particular, the grid is an unstructured triangular 2D grid ('poly data' grid in 
the venacular of paraview).  The 'dimensions' variables include integer 
identifiers for triangle nodes, but NOT lat, long, x, y, time etc.  Rather, 
these are included among the 'variables' variables (e.g. lat = lat(node)).

Is the problem indeed that the paraview netCDF reader cannot understand this 
particular netCDF-CF file?  Is there a way around this, without having to 
change the way the data is outputted (from netCDF-CF to netCDF-COARDS 
convention)?  Note that I can read into paraview certain variables by filtering 
out the 1-dimensional variables (lat, long etc.), but of course these variables 
do not have the correct dependencies (they should be dependent on the variables 
I filtered out - lat, long etc.)

thanks,
Joel



-----Original Message-----
From: Moreland, Kenneth [mailto:kmo...@sandia.gov]
Sent: Tue 4/6/2010 3:41 PM
To: Joel Culina; paraview@paraview.org
Subject: Re: [Paraview] trouble reading in netCDF file

It sounds like you are reading in an array with 0 or 1 dimensions (not 
including time).  Although the reader should happily create an image data of 
that structure, the standard rendering views only understand image data of 2 or 
3 dimensions.  Hence you get the error.

If you want to see the data in a plot, try adding the "Plot Data" filter.

-Ken


On 4/6/10 11:36 AM, "Joel Culina" <joel.cul...@acadiau.ca> wrote:



Hi,

I am trying to read in a netCDF file using Paraview 3.6.2.  It can 'see' the 
netCDF file, but when I attempt to read in the file by pressing 'Apply', I get 
the following error message:

ERROR: In 
/home/kitware/ParaView3/Utilities/BuildScripts/ParaView-3.6/ParaView3/Servers/Filters/vtkTexturePainter.cxx,
 line 280
vtkTexturePainter (0xb8a0000): Incorrect dimensionality.

I'm not sure which netCDF release created the netCDF file.  However, I read in 
a previous post that paraview 3.6.1 could handle netCDF 4, and since  "all 
netCDF files ever written can always be read by the latest netCDF release. That 
is, we guarantee backward data compatibility" then 3.6.2 should be able to 
handle my netCDF file (which wasn't created too recently).

I can read the netCDF file into MATLAB, so it isn't corrupt.

So what's the problem?

thanks
Joel



   ****      Kenneth Moreland
    ***      Sandia National Laboratories
***********
*** *** ***  email: kmo...@sandia.gov
**  ***  **  phone: (505) 844-8919
    ***      web:   http://www.cs.unm.edu/~kmorel







   ****      Kenneth Moreland
    ***      Sandia National Laboratories
***********
*** *** ***  email: kmo...@sandia.gov
**  ***  **  phone: (505) 844-8919
    ***      web:   http://www.cs.unm.edu/~kmorel








   ****      Kenneth Moreland
    ***      Sandia National Laboratories
***********
*** *** ***  email: kmo...@sandia.gov
**  ***  **  phone: (505) 844-8919
    ***      web:   http://www.cs.unm.edu/~kmorel





   ****      Kenneth Moreland
    ***      Sandia National Laboratories
***********
*** *** ***  email: kmo...@sandia.gov
**  ***  **  phone: (505) 844-8919
    ***      web:   http://www.cs.unm.edu/~kmorel

_______________________________________________
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

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

Reply via email to