[Paraview] Implementing an Interactive Reader
Hi, I would like to write a reader plugin which allows some kind of interaction: after reading the whole dataset (which is particle data and will be mapped to a imagedata), the user should be able to select a volume of interest. Thereupon, the reader has to reread the dataset and map it to the imagedata with the new extent. I don't want to use the create subset filter, because I don't want the VOI to be of a lower resolution. Any ideas how I could use a box-widget to specify a volume of interest and cause the reader to reread the data mapping it to the new imagedata? Thanks in advance, Sonja Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzende des Aufsichtsrats: MinDir'in Baerbel Brumme-Bothe Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender), Dr. Ulrich Krafft (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ___ 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
Re: [Paraview] Interpretation of histogram of deformation field magnitude?
On the properties panel for the Histogram filter, you choose the array to generate histogram from. Currently the panel doesn't not support selecting the magnitude of a vector array (only 1 component). In your case, by default the 0th component of the GlyphVector is chosen, which can be negative and hence the plot. To generate a histogram for the magnitude of the vector, apply another calculator with the expression: mag(GlyphVector) and then generate a histogram using the Result array. Utkarsh On Tue, Nov 3, 2009 at 8:15 PM, motes motes mort.mo...@gmail.com wrote: I have loaded a deformation field (.mhd file) in paraview made with itk: 1) open .mhd file 2) connect the calculate and use the below expression: MetaImage_X*iHat+MetaImage_Y*jHat+0*kHat 3) Add glyph filter. The result looks like this: http://37133.vs.webtropia.com/apache2-default/test/deform.png But now I would like to create a histogram over the magnitude of the deformation field. I have therefore selected: Filters-Data Analysis-Histogram. In the display tab I have selected GlypVector_total (Magnitude) and under User Data Array I have selected MetaImage. The result looks like this: http://37133.vs.webtropia.com/apache2-default/test/hist.png But how should it be interpretated? I assume that the y-axis is the pixel count and the x-axis is the magnitude size. But should the magnitudes (Norm) not always be positive? And as can be seen from the deformation field its only a small part of the image that is deformed. I would therefore expect a large number of pixels to have 0 magnitude, but that is not the case. Any input are welcome! ___ 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 ___ 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
[Paraview] [Fwd: Re: Evaluating Paraview to visualize Tough2 data]
---BeginMessage--- Dave, Attached is the tout.tec file which is a tough2 file converted with a program called ext. This program produces files that can be read by Tecplot. I tried to load the file with the plugin method that you described below. It does not work and produces an error message. Do you have an idea why that is? I also attched a file channel.tec. This is a standard .tec file not converted from tough2. Do you now why the tout.tec file is not accepted. would this work better with the new ParaView native Tecplot reader? Cheers, Johan David E DeMarle schreef: I just realized it only comes with _some_ of the binary releases, namely both linux releases and the 32 bit windows release. (I gather we couldn't get enough of Visit to compile on mac and win64 platforms.) On win32 for example, install paraview, then go to tools-Manage Plugins/Extensions...-Load Look in paraview's bin/plugins/VisItReaderPlugin. There you will find VisitReaderPlugin.dll (linux will be libVisitReaderPlugin.so). Once you load that the file open dialog will be able to open more files including TecPlot Files (beta)(*.tp *.plt *.tec). hth, David E DeMarle Kitware, Inc. RD Engineer 28 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-371-3971 x109 On Wed, Oct 28, 2009 at 5:30 AM, Johan de Koning johan.dekon...@hybridsolutions.nl wrote: David, Where can I find the Visit bridge plugin? Regards, Johan David E DeMarle schreef: Yes, currently the best option to do so is found in the Visit bridge plugin. I believe that only supports ASCII tecplot files. We are working on a ParaView native Tecplot reader, but I do not think that is even in the development head yet. David E DeMarle Kitware, Inc. RD Engineer 28 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-371-3971 x109 On Tue, Oct 27, 2009 at 9:33 AM, Johan de Koning johan.dekon...@hybridsolutions.nl wrote: Hello David, Thanks for the info. One question, can Paraview import Tecplot files? I have a way to convert Tough2 files to Tecplot readable files. Regards, Johan David E DeMarle schreef: Hello Johan, You have several options to get Tough2 data into ParaView. First, ask the paraview mailing list. It is possible someone there has experience with the Tough2 format and might even have a reader ready. After that is may be easiest to find a common file format. Ie one that Tough2 can export to and ParaView can read in. A mostly complete list of formats ParaView accepts is here: http://paraview.org/OnlineHelpCurrent/ParaViewReaders.html I say mostly complete because this doesn't include the Visit bridge or any file formats that are readable via Plugins (see below). After that, there is the Python route. Tough2 files can almost certainly be processed via Python scripts (perhaps Tough2 has a native Python interface but if not they could always be processed manually). ParaView's Python programmable source can be used to make a quick Python based reader. The job of any reader is to parse the file format and produce vtkDataObjects that ParaView can process. An example of a simple python reader is here: http://www.paraview.org/Wiki/Here_are_some_more_examples_of_simple_ParaView_3_python_filters. After that, there is the C++ plugin route. Note that there are paths in both Python and C++ to link into Fortran codes, so you may be able to link either into Tough2 directly. As with the Python route, this route would involve writing code to ingest the Tough2 files and create the VTK data structures that ParaView can process. In this case the code would be written in C++ instead of Python. The place to start learning how to do that is here: http://www.paraview.org/Wiki/Plugin_HowTo#Adding_a_Reader Finally, Kitware will do this sort of work under contract. Ie you could pay us to write the reader and it will probably be cheaper in the long run to do that than to code it in house. We do flexible hourly support contracts for small projects (under $25K), we offer our best dual tier hourly rates to project over $25K, and we also offer fixed price contracts for work that is clearly defined (this task is) and generally more than a person month of effort (a reader for for Tough2 would be less than a month of effort). I'm not personally familiar with the Tough2 file format, but in the past we've found that adding a new reader or writer to VTK generally takes between 20 to 60 hours of effort. (It varies depending on the complexity of the file format.) This time includes the effort of documenting the class, writing a test, and ensuring that it functions correctly on all platforms. cheers, David E DeMarle Kitware, Inc. RD Engineer 28 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-371-3971 x109 Variables = X Y P T SG SW X1 X2 PCAP DG DW Zone F=FEPOINT I= 100 J= 81 2.50E+01 2.50E+01 8.591700E+06 2.00E+02 5.435800E-03 9.945600E-01 1.00E+00 0.00E+00
Re: [Paraview] Selected point size/location problems
On Tue, Nov 3, 2009 at 1:16 PM, David Doria daviddo...@gmail.com wrote: Here is the procedure to generated the issue: 1) Add a cone source 2) Use select points on to select on of the points. (http://www.rpi.edu/~doriad/Paraview_List/Selection/setup.png) 3) zoom in to the point you selected. You will see that it is not actually on the corner where it should be (http://www.rpi.edu/~doriad/Paraview_List/Selection/surface.png). Why is this? 4) Change the cone's representation from 'surface' to 'points'. You will see that the two points do not coincide. (same problem as in #3) 5) Change the point size. You will see that the white point gets bigger, but the selected (pink)point is still very small (http://www.rpi.edu/~doriad/Paraview_List/Selection/pointsize.png). Is there a way to change this? Shouldn't it be changing the color of the actual point anyway instead of adding a new point? Any thoughts on this? Thanks, David Another thing I forgot to mention - there seems to be significant z-fighting happening between the selected (pink) point and the actual (white) point. That is, when I interact with the object (for example rotate), if I stop the interaction, about half of the time the point will be pink and the other half it will be white. This causes significant confusion because there is no way to know if the point is actually selected. Is anyone else having this type of issue lately? Thanks, David ___ 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
[Paraview] Tecplot Paraview error
Hello, Attached is the tout.tp file which is a tough2 file converted with a program called ext. This program produces files that can be read by Tecplot. I tried to load the file in Paraview with the VisItReaderPlugin loaded. I was told that with this plugin Tecplot files can be read. It does not work and produces an error message. Does anybody have an idea why that is? The error message says that there is an error in line 386 of the vtkVisItDatabase.cxx Thanks, Johan Variables = X Y P T SG SW X1 X2 PCAP DG DW Zone F=FEPOINT I= 100 J= 81 2.50E+01 2.50E+01 8.591700E+06 2.00E+02 5.435800E-03 9.945600E-01 1.00E+00 0.00E+00 0.00E+00 4.618600E+01 7.122400E+02 7.50E+01 2.50E+01 8.592700E+06 3.00E+02 1.000600E-02 9.899900E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.25E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.75E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.25E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.75E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 3.25E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 3.75E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 4.25E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 4.75E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.50E+01 7.50E+01 8.592700E+06 3.00E+02 1.000600E-02 9.899900E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 7.50E+01 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.25E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.75E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.25E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.75E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 3.25E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 3.75E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 4.25E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 4.75E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.50E+01 1.25E+02 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 7.50E+01 1.25E+02 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.25E+02 1.25E+02 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.75E+02 1.25E+02 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.25E+02 1.25E+02 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.75E+02 1.25E+02 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 3.25E+02 1.25E+02 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 3.75E+02 1.25E+02 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 4.25E+02 1.25E+02 8.592700E+06
Re: [Paraview] Tecplot Paraview error
if you change your header to: Variables = X, Y, P, T, SG, SW, X1, X2, PCAP, DG, DW Zone N=100, E=81, F=FEPOINT, ET=QUADRILATERAL You should be able to read this file. I guess. Good luck. On Wed, Nov 4, 2009 at 2:23 PM, Johan de Koning johan.dekon...@hybridsolutions.nl wrote: Hello, Attached is the tout.tp file which is a tough2 file converted with a program called ext. This program produces files that can be read by Tecplot. I tried to load the file in Paraview with the VisItReaderPlugin loaded. I was told that with this plugin Tecplot files can be read. It does not work and produces an error message. Does anybody have an idea why that is? The error message says that there is an error in line 386 of the vtkVisItDatabase.cxx Thanks, Johan Variables = X Y P T SG SW X1 X2 PCAP DG DW Zone F=FEPOINT I= 100 J= 81 2.50E+01 2.50E+01 8.591700E+06 2.00E+02 5.435800E-03 9.945600E-01 1.00E+00 0.00E+00 0.00E+00 4.618600E+01 7.122400E+02 7.50E+01 2.50E+01 8.592700E+06 3.00E+02 1.000600E-02 9.899900E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.25E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.75E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.25E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.75E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 3.25E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 3.75E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 4.25E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 4.75E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.50E+01 7.50E+01 8.592700E+06 3.00E+02 1.000600E-02 9.899900E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 7.50E+01 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.25E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.75E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.25E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.75E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 3.25E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 3.75E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 4.25E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 4.75E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.50E+01 1.25E+02 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 7.50E+01 1.25E+02 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.25E+02 1.25E+02 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.75E+02 1.25E+02 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.25E+02 1.25E+02 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.75E+02 1.25E+02 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 3.25E+02 1.25E+02 8.592700E+06 3.00E+02 1.00E-02
Re: [Paraview] Selected point size/location problems
Hello! On Wed, Nov 4, 2009 at 2:21 PM, David Doria daviddo...@gmail.com wrote: On Tue, Nov 3, 2009 at 1:16 PM, David Doria daviddo...@gmail.com wrote: -[cut]- [ Selected points marker are not at the same position/coordinates as the corresponding geometry-points. (depending on current scale,..) ] -[cut]- Is anyone else having this type of issue lately? Yes, I can confirm this issue. And this seems to be a relatively new, cause ParaView 3.4 (released in Oct, 2008) didn't show this behaviour (contrary to the current release (3.6.1) and the latest cvs-code). Did you make a Bug Report? mirko -- Real programmers don't document; if it was hard to write, it should be hard to understand. ___ 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
Re: [Paraview] Selected point size/location problems
On Wed, Nov 4, 2009 at 8:55 AM, mirko heuegger mheueg...@gmail.com wrote: Hello! On Wed, Nov 4, 2009 at 2:21 PM, David Doria daviddo...@gmail.com wrote: On Tue, Nov 3, 2009 at 1:16 PM, David Doria daviddo...@gmail.com wrote: -[cut]- [ Selected points marker are not at the same position/coordinates as the corresponding geometry-points. (depending on current scale,..) ] -[cut]- Is anyone else having this type of issue lately? Yes, I can confirm this issue. And this seems to be a relatively new, cause ParaView 3.4 (released in Oct, 2008) didn't show this behaviour (contrary to the current release (3.6.1) and the latest cvs-code). Did you make a Bug Report? mirko No, typically I like someone to confirm the problem before I make a bug report. I'll create the report now. Utkarsh, is this part of the same issue with the new extract selection panel? Can we get a guess at an expected completion date just for information sake? Sometimes I will proceed differently if I know the problem will be fixed tomorrow vs next month. Thanks, David ___ 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
Re: [Paraview] Selected point size/location problems
Utkarsh, is this part of the same issue with the new extract selection panel? Can we get a guess at an expected completion date just for information sake? Sometimes I will proceed differently if I know the problem will be fixed tomorrow vs next month. David, I wouldn't think this has anything to do with the changes to the panel, and more with the coincident topology resolution choices we made. But I cannot understand why the two points would not be displaced by the same value -- that needs some debugging. As far as the time estimate goes, it's really hard to tell right now, but I'd think we can aim at this for 3.8 which is due early next year. Utkarsh ___ 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
Re: [Paraview] Selected point size/location problems
Please add it to the bug tracker so we don't loose track of it. Thanks Utkarsh On Wed, Nov 4, 2009 at 9:16 AM, Utkarsh Ayachit utkarsh.ayac...@kitware.com wrote: Utkarsh, is this part of the same issue with the new extract selection panel? Can we get a guess at an expected completion date just for information sake? Sometimes I will proceed differently if I know the problem will be fixed tomorrow vs next month. David, I wouldn't think this has anything to do with the changes to the panel, and more with the coincident topology resolution choices we made. But I cannot understand why the two points would not be displaced by the same value -- that needs some debugging. As far as the time estimate goes, it's really hard to tell right now, but I'd think we can aim at this for 3.8 which is due early next year. Utkarsh ___ 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
Re: [Paraview] Selected point size/location problems
On Wed, Nov 4, 2009 at 9:16 AM, Utkarsh Ayachit utkarsh.ayac...@kitware.com wrote: Please add it to the bug tracker so we don't loose track of it. Thanks Utkarsh Ok, thanks. I added it here: http://public.kitware.com/Bug/view.php?id=9838 Thanks, David ___ 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
Re: [Paraview] Ordered xml inputs?
On Tue, Nov 3, 2009 at 11:31 AM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
There are two ways:
1 Use attribute port_index on the InputProperty to specify which
input port it's going to eg.
InputProperty name=Source port_index=0 command=AddInputConnection ...
/
InputProperty name=Target port_index=1 command=AddInputConnection ...
/
2 Use helper methods defined on the filter eg.
void AddSource(vtkAlgorithmOutput* input) {
this-AddInputConnection(0, input); }
void AddTarget(vtkAlgorithmOutput* input) {
this-AddInputConnection(1, input); }
And use these as the command's for your two input properties.
Utkarsh
Hm, I tried the port_index method, but it still crashes when run from
Paraview. My filter works fine from c++ (see Example.cxx). Would you
mind taking a look to see if you can find the discrepancy between how
I setup the pipeline in the c++ code vs in the XML? One thing I
noticed is that in the Input Editor that opens when I begin to apply
the plugin, the input ports are not listed in the same (correct) order
as they are in the xml (specified by port_index). Could that point to
the problem? If so, why is it happening?
http://www.rpi.edu/~doriad/Paraview_List/LandmarkFilter/
Thanks,
David
___
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
Re: [Paraview] Selected point size/location problems
Thanks for writing this bug. And just for information, the links (in this report) will not work, cause the urls contains tailing brackets. Is it possible that you fix that? thx in advance. mirko Ah, sorry about that. Unfortunately users cannot edit bug reports (can this be changed?). Thanks, David ___ 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
Re: [Paraview] Selected point size/location problems
Hello! On Wed, Nov 4, 2009 at 3:56 PM, David Doria daviddo...@gmail.com wrote: Thanks for writing this bug. And just for information, the links (in this report) will not work, cause the urls contains tailing brackets. Ah, sorry about that. Unfortunately users cannot edit bug reports (can this be changed?). I have no Idea about that. But Adding a Link to the bug-report, referring to this thread (eg http://markmail.org/thread/hj6qkllhvwnmpqrr), might be helpful. thx in advance. mirko -- Real programmers don't document; if it was hard to write, it should be hard to understand. ___ 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
Re: [Paraview] Tecplot Paraview error
vtkTecplotReader is now ready for use via ParaView. The 'Variables' and 'Zone' sections / lines need to be changed as Hom suggested. This is a zone of type Finite Element Data in Tecplot term (or vtkUnstructuredGrid). The number of nodes (points, 100), number of elements (cells, 81), and the elements (cells) type, ET=QUADRILATERAL, need to be explicitly provided in the zone header line. The original zone line, I=100 J=81, would be parsed as an ordered zone (corresponding to vtkStructuredGrid) which would be assumed to have (100 - 1) x (81 - 1 ) cells, causing the loading error. Please replace file extension 'tp' with 'tec', or update the latest ParaViewReaders.xml (which supports file extension 'tp') and this ASCII file can be loaded in ParaView directly via vtkTecplotReader. As of right now, vtkTecplotReader is a simplified version of the ASCII file reader and more functionalities may be added if necessary. For any problem with this reader, please feel free to let me know. Thanks to Hom for the help. Thanks. -Zhanping -- Zhanping Liu, PhD Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-371-3971 x 138 http://www.zhanpingliu.org On Wed, Nov 4, 2009 at 8:51 AM, Hom Nath Gharti hng.em...@gmail.com wrote: if you change your header to: Variables = X, Y, P, T, SG, SW, X1, X2, PCAP, DG, DW Zone N=100, E=81, F=FEPOINT, ET=QUADRILATERAL You should be able to read this file. I guess. Good luck. On Wed, Nov 4, 2009 at 2:23 PM, Johan de Koning johan.dekon...@hybridsolutions.nl wrote: Hello, Attached is the tout.tp file which is a tough2 file converted with a program called ext. This program produces files that can be read by Tecplot. I tried to load the file in Paraview with the VisItReaderPlugin loaded. I was told that with this plugin Tecplot files can be read. It does not work and produces an error message. Does anybody have an idea why that is? The error message says that there is an error in line 386 of the vtkVisItDatabase.cxx Thanks, Johan Variables = X Y P T SG SW X1 X2 PCAP DG DW Zone F=FEPOINT I= 100 J= 81 2.50E+01 2.50E+01 8.591700E+06 2.00E+02 5.435800E-03 9.945600E-01 1.00E+00 0.00E+00 0.00E+00 4.618600E+01 7.122400E+02 7.50E+01 2.50E+01 8.592700E+06 3.00E+02 1.000600E-02 9.899900E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.25E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.75E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.25E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.75E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 3.25E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 3.75E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 4.25E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 4.75E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.50E+01 7.50E+01 8.592700E+06 3.00E+02 1.000600E-02 9.899900E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 7.50E+01 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.25E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.75E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.25E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.75E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 3.25E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 3.75E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02
Re: [Paraview] Ordered xml inputs?
David,
I had a short glance at your code and there are two things I find intriging:
1) Your XML mixes the port_index=. and helper method approach for property
SourceDataSet:
InputProperty
name=SourceDataSet
port_index=2
command=AddSourceConnection
clean_command=RemoveAllSources
You'll have to change the command to AddInputConnection, in particular because
method AddSourceConnection is merely declared in your *.h file, but there is
nowhere any corresponding code for it. (It's not inherited from class
vtkPolyDataAlgorithm.)
2) Same holds for the clean command: RemoveAllSources() is referenced in the
XML, declared in the header file, but not defined. Whereas RemoveAllInputs() is
inherited from class vtkAlgorithm.
Sven
- Original Message -
From: David Doria daviddo...@gmail.com
To: ParaView paraview@paraview.org
CC: ParaView paraview@paraview.org
Sent: 11/04/09 15:48:06
Subject: [Paraview] Ordered xml inputs?
On Tue, Nov 3, 2009 at 11:31 AM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
There are two ways:
1 Use attribute port_index on the InputProperty to specify which
input port it's going to eg.
InputProperty name=Source port_index=0 command=AddInputConnection ...
/
InputProperty name=Target port_index=1 command=AddInputConnection ...
/
2 Use helper methods defined on the filter eg.
void AddSource(vtkAlgorithmOutput* input) {
this-AddInputConnection(0, input); }
void AddTarget(vtkAlgorithmOutput* input) {
this-AddInputConnection(1, input); }
And use these as the command's for your two input properties.
Utkarsh
Hm, I tried the port_index method, but it still crashes when run from
Paraview. My filter works fine from c++ (see Example.cxx). Would you
mind taking a look to see if you can find the discrepancy between how
I setup the pipeline in the c++ code vs in the XML? One thing I
noticed is that in the Input Editor that opens when I begin to apply
the plugin, the input ports are not listed in the same (correct) order
as they are in the xml (specified by port_index). Could that point to
the problem? If so, why is it happening?
http://www.rpi.edu/~doriad/Paraview_List/LandmarkFilter/
Thanks,
David
___
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
___
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
[Paraview] Improving vtkDataArraySelection ... and a question of the general philosophy
I was looking at making some minor tweaks to vtkDataArraySelection and started wondering why some things are being done the way they are. First off I'll explain what I wanted. I'd like an additional method int AddArray(const char* name, int defaultStatus); The behaviour is as per AddArray(const char*), but with the ability to specify which default status should be used when it is created. [ I really cannot figure out a workaround for adding an array entry with an unselected state that doesn't automatically trigger this-Modified(); ] Then the questions begin: The method probably doesn't exist in that form since nobody thought they needed it. However, it could also be that having multiple signatures is frowned upon in VTK. Or are there problems with binding to other languages? Having said that, the methods are surrounded by a BTX/ETX pair so wrapping may not be the problem, but I'm not sure. After taking a slightly closer look, I also noticed that the internals use a vtkstd::vectorvtkstd::string and a vtkstd::vectorint for the storage. If there is a std::string under the hood, is there any other reason (beyond language wrapping) that we have everything with (const char*) parameters instead of (const vtkstd::string)? Is it only historical that a vtkstd::vectorint is used for storing a bool state? Or is there a desire to avoid the std::vectorbool specialization? Thanks, /mark This e-mail message and any attachments may contain legally privileged, confidential or proprietary Information, or information otherwise protected by law of EMCON Technologies, its affiliates, or third parties. This notice serves as marking of its Confidential status as defined in any confidentiality agreements concerning the sender and recipient. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. ___ 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
Re: [Paraview] Ordered xml inputs?
On Wed, Nov 4, 2009 at 10:31 AM, Sven Buijssen sven.buijs...@tu-dortmund.de wrote: David, I had a short glance at your code and there are two things I find intriging: 1) Your XML mixes the port_index=. and helper method approach for property SourceDataSet: InputProperty name=SourceDataSet port_index=2 command=AddSourceConnection clean_command=RemoveAllSources You'll have to change the command to AddInputConnection, in particular because method AddSourceConnection is merely declared in your *.h file, but there is nowhere any corresponding code for it. (It's not inherited from class vtkPolyDataAlgorithm.) 2) Same holds for the clean command: RemoveAllSources() is referenced in the XML, declared in the header file, but not defined. Whereas RemoveAllInputs() is inherited from class vtkAlgorithm. Sven Ah, sorry, you are correct - those were copy/paste errors! However, now that those things are fixed (http://www.rpi.edu/~doriad/Paraview_List/LandmarkFilter/LandmarkTransformFilter.xml) when I apply the filter in Paraview and set the inputs using the Input Editor, I get a whole bunch of these errors: vtkCompositeDataPipeline (0xa82e288): Input port 0 of algorithm vtkLandmarkTransformFilter(0xa82e240) has 0 connections but is not optional. vtkCompositeDataPipeline (0xa82e288): Input port 1 of algorithm vtkLandmarkTransformFilter(0xa82e240) has 2 connections but is not repeatable. etc, etc. Why would this be? Thanks, David ___ 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
[Paraview] So basic operation
My problem seems as simple as 123: I have an elevation image and I want to create a terrain model by taking elevation in the image. So my idea was to create a plane at the image resolution, then use WarpByScalar to warp it according to the image content. But WarpByScalar warps according to an a point data scalar field, which requires that I put the image in the point data of the plane and... I did not find the way to do it. So 2 questions: - how to associate a scalar or vector field to an existing geometry set? - is it the right way to proceed for my problem? _ Nouveau Windows 7 : Trouvez le PC qui vous convient. En savoir plus. http://clk.atdmt.com/FRM/go/181574580/direct/01/___ 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
Re: [Paraview] Tecplot Paraview error
Fred: You may update your ParaView with the latest version of the CVS repository. Thanks. -Zhanping On Wed, Nov 4, 2009 at 11:08 AM, Fred Fred stan1...@hotmail.fr wrote: Yes, I have a question: you wrote vtkTecplotReader is now ready for use via ParaView but in which version of ParaView is it included? -- Date: Wed, 4 Nov 2009 10:17:28 -0500 From: zhanping@kitware.com To: hng.em...@gmail.com CC: paraview@paraview.org Subject: Re: [Paraview] Tecplot Paraview error vtkTecplotReader is now ready for use via ParaView. The 'Variables' and 'Zone' sections / lines need to be changed as Hom suggested. This is a zone of type Finite Element Data in Tecplot term (or vtkUnstructuredGrid). The number of nodes (points, 100), number of elements (cells, 81), and the elements (cells) type, ET=QUADRILATERAL, need to be explicitly provided in the zone header line. The original zone line, I=100 J=81, would be parsed as an ordered zone (corresponding to vtkStructuredGrid) which would be assumed to have (100 - 1) x (81 - 1 ) cells, causing the loading error. Please replace file extension 'tp' with 'tec', or update the latest ParaViewReaders.xml (which supports file extension 'tp') and this ASCII file can be loaded in ParaView directly via vtkTecplotReader. As of right now, vtkTecplotReader is a simplified version of the ASCII file reader and more functionalities may be added if necessary. For any problem with this reader, please feel free to let me know. Thanks to Hom for the help. Thanks. -Zhanping -- Zhanping Liu, PhD Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-371-3971 x 138 http://www.zhanpingliu.org On Wed, Nov 4, 2009 at 8:51 AM, Hom Nath Gharti hng.em...@gmail.comwrote: if you change your header to: Variables = X, Y, P, T, SG, SW, X1, X2, PCAP, DG, DW Zone N=100, E=81, F=FEPOINT, ET=QUADRILATERAL You should be able to read this file. I guess. Good luck. On Wed, Nov 4, 2009 at 2:23 PM, Johan de Koning johan.dekon...@hybridsolutions.nl wrote: Hello, Attached is the tout.tp file which is a tough2 file converted with a program called ext. This program produces files that can be read by Tecplot. I tried to load the file in Paraview with the VisItReaderPlugin loaded. I was told that with this plugin Tecplot files can be read. It does not work and produces an error message. Does anybody have an idea why that is? The error message says that there is an error in line 386 of the vtkVisItDatabase.cxx Thanks, Johan Variables = X Y P T SG SW X1 X2 PCAP DG DW Zone F=FEPOINT I= 100 J= 81 2.50E+01 2.50E+01 8.591700E+06 2.00E+02 5.435800E-03 9.945600E-01 1.00E+00 0.00E+00 0.00E+00 4.618600E+01 7.122400E+02 7.50E+01 2.50E+01 8.592700E+06 3.00E+02 1.000600E-02 9.899900E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.25E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.75E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.25E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.75E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 3.25E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 3.75E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 4.25E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 4.75E+02 2.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.50E+01 7.50E+01 8.592700E+06 3.00E+02 1.000600E-02 9.899900E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 7.50E+01 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.25E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 1.75E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01 1.00E+00 0.00E+00 0.00E+00 4.619200E+01 7.122200E+02 2.25E+02 7.50E+01 8.592700E+06 3.00E+02 1.00E-02 9.90E-01
Re: [Paraview] So basic operation
Use Resample with Dataset with Input=Image Data and Source=Plane to associate the height field with the points on the plane. Then you can apply WarpByScalar. Utkarsh On Wed, Nov 4, 2009 at 10:58 AM, Fred Fred stan1...@hotmail.fr wrote: My problem seems as simple as 123: I have an elevation image and I want to create a terrain model by taking elevation in the image. So my idea was to create a plane at the image resolution, then use WarpByScalar to warp it according to the image content. But WarpByScalar warps according to an a point data scalar field, which requires that I put the image in the point data of the plane and... I did not find the way to do it. So 2 questions: - how to associate a scalar or vector field to an existing geometry set? - is it the right way to proceed for my problem? Nouveau Windows 7 : Trouvez le PC qui vous convient. En savoir plus. ___ 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 ___ 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
Re: [Paraview] So basic operation
Why not just run Clean To Grid on the image data? That will convert it to an
unstructured grid that can be directly warped.
elevation image - Clean To Grid - Warp By Scalar
-Ken
On 11/4/09 9:39 AM, Utkarsh Ayachit utkarsh.ayac...@kitware.com wrote:
Use Resample with Dataset with Input=Image Data and Source=Plane to
associate the height field with the points on the plane. Then you can
apply WarpByScalar.
Utkarsh
On Wed, Nov 4, 2009 at 10:58 AM, Fred Fred stan1...@hotmail.fr wrote:
My problem seems as simple as 123: I have an elevation image and I want to
create a terrain model by taking elevation in the image.
So my idea was to create a plane at the image resolution, then use
WarpByScalar to warp it according to the image content.
But WarpByScalar warps according to an a point data scalar field, which
requires that I put the image in the point data of the plane and... I did
not find the way to do it.
So 2 questions:
- how to associate a scalar or vector field to an existing geometry set?
- is it the right way to proceed for my problem?
Nouveau Windows 7 : Trouvez le PC qui vous convient. En savoir plus.
___
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
___
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
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
[Paraview] pre processor tough2 geothermal reservoir simulator
Hello, I am using a geothermal reservoir simulator called Tough2. For post-processing I use Paraview. Now I am also looking for an open source pre-processing software that can create grids. It has to be flexible since I plan to explicitly model natural fractures that are present in the underground reservoirs that contain the hot water. Does anyone have a suggestion? Thanks in advance, Johan ___ 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
Re: [Paraview] Ordered xml inputs?
David, Looking at the xml, you have added a clean_command to all the properties which is RemoveAllInputs. CleanCommand is called before a property is pushed. So before each property value is pushed all other inputs are removed. And hence the error. If your filter only takes 1 connection per input port, then simply replace all AddInputConnection commands by SetInputConnection and remove the clean_command attribute all together. I've attached a modified xml. Utkarsh On Wed, Nov 4, 2009 at 10:42 AM, David Doria daviddo...@gmail.com wrote: On Wed, Nov 4, 2009 at 10:31 AM, Sven Buijssen sven.buijs...@tu-dortmund.de wrote: David, I had a short glance at your code and there are two things I find intriging: 1) Your XML mixes the port_index=. and helper method approach for property SourceDataSet: InputProperty name=SourceDataSet port_index=2 command=AddSourceConnection clean_command=RemoveAllSources You'll have to change the command to AddInputConnection, in particular because method AddSourceConnection is merely declared in your *.h file, but there is nowhere any corresponding code for it. (It's not inherited from class vtkPolyDataAlgorithm.) 2) Same holds for the clean command: RemoveAllSources() is referenced in the XML, declared in the header file, but not defined. Whereas RemoveAllInputs() is inherited from class vtkAlgorithm. Sven Ah, sorry, you are correct - those were copy/paste errors! However, now that those things are fixed (http://www.rpi.edu/~doriad/Paraview_List/LandmarkFilter/LandmarkTransformFilter.xml) when I apply the filter in Paraview and set the inputs using the Input Editor, I get a whole bunch of these errors: vtkCompositeDataPipeline (0xa82e288): Input port 0 of algorithm vtkLandmarkTransformFilter(0xa82e240) has 0 connections but is not optional. vtkCompositeDataPipeline (0xa82e288): Input port 1 of algorithm vtkLandmarkTransformFilter(0xa82e240) has 2 connections but is not repeatable. etc, etc. Why would this be? Thanks, David ___ 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 ServerManagerConfiguration ProxyGroup name=filters !-- == -- SourceProxy name=LandmarkTransformFilter class=vtkLandmarkTransformFilter label=LandmarkTransformFilter Documentation long_help=Align two point sets using vtkLandmarkTransform to compute the best transformation between the two point sets. short_help=vtkLandmarkTransformFilter. /Documentation InputProperty name=SourceLandmarks port_index=0 command=SetInputConnection ProxyGroupDomain name=groups Group name=sources/ Group name=filters/ /ProxyGroupDomain DataTypeDomain name=input_type DataType value=vtkPolyData/ /DataTypeDomain Documentation Set the source data set. This data set that will move towards the target data set. /Documentation /InputProperty InputProperty name=TargetLandmarks port_index=1 command=SetInputConnection ProxyGroupDomain name=groups Group name=sources/ Group name=filters/ /ProxyGroupDomain DataTypeDomain name=input_type DataType value=vtkPolyData/ /DataTypeDomain Documentation Set the target data set. This data set will stay stationary. /Documentation /InputProperty InputProperty name=SourceDataSet port_index=2 command=SetInputConnection ProxyGroupDomain name=groups Group name=sources/ Group name=filters/ /ProxyGroupDomain DataTypeDomain name=input_type DataType value=vtkPolyData/ /DataTypeDomain Documentation Set the source data set landmark points. /Documentation /InputProperty /SourceProxy !-- End LandmarkTransformFilter -- /ProxyGroup !-- End Filters Group -- /ServerManagerConfiguration ___ 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
Re: [Paraview] Ordered xml inputs?
On Wed, Nov 4, 2009 at 2:32 PM, Utkarsh Ayachit utkarsh.ayac...@kitware.com wrote: David, Looking at the xml, you have added a clean_command to all the properties which is RemoveAllInputs. CleanCommand is called before a property is pushed. So before each property value is pushed all other inputs are removed. And hence the error. If your filter only takes 1 connection per input port, then simply replace all AddInputConnection commands by SetInputConnection and remove the clean_command attribute all together. I've attached a modified xml. Utkarsh Ah ha! Fantastic, it's working now, thanks all. I have added a handful of things I've learned along the way to http://www.paraview.org/Wiki/Plugin_HowTo if someone wants to look it over for clarity/correctness etc. Thanks again, David ___ 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
