from:"Mark Olesen"

Re: [Paraview] Writing XML VTK Binary files from C++

2017-11-30 Thread Mark Olesen

When you say "writing binary", you need to distinguish between three 
possibilities.

1) writing binary "inline" (actually base64 encoded)
2) writing binary "append" (actually base64 encoded)
3) writing raw binary "append" (really raw binary)

Since you already have ASCII writing working and its content is 
"inline", it won't take much more to get binary inline working.
By "inline", I mean when the output is placed between the   
markers. Eg,


content


For the binary case, the content is written as base64-encoded data, 
which means that your output writer for these sections needs to pass the 
content through a base64 layer to do the encoding for you.


If it helps as reference, we have the same thing in OpenFOAM, except 
that we only write vtu and vtp files (we don't have rectilinear meshes).


In the repo https://develop.openfoam.com/Development/OpenFOAM-plus
we have a foamVtkBase64Formatter and a foamVtkBase64Layer (both under 
src/fileFormats/vtk/format/) that add a base64Layer to encode and output 
as base64 (src/OpenFOAM/db/IOstreams/hashes/base64Layer.[CH]).


You'll see that the foamVtkBase64Layer and base64Layer are quite low 
level means of adding an tiny encoding buffer (3 chars size) to 
intercept output prior to sending through to a std::ostream. It take 
very little effort to adopt for your output and thus quite easy to drop 
in instead of your current ASCII outputter.  For it too work easily, 
however, you should make sure that you need to generate your output 
content with a write() method instead of using '<<'. This allows 
somewhat easy switching between something like a foamVtkAsciiFormatter 
and the binary version, but more importantly it makes it easier to track 
the output state.


When browsing through the code, you may also notice that we have support 
for writing in appended format (raw and base64). However, I would not 
advise you to tackle that immediately. There are a few more things to 
watch out for here, but more importantly it will change many more things 
on the calling side.


I hope this information helps you.
/mark

--
Dr Mark OLESEN
Principal Engineer, ESI-OpenCFD
ESI GmbH | Einsteinring 24 | 85609 Munich | GERMANY
www.openfoam.com | www.esi-group.com | mark.ole...@esi-group.com


On 11/30/17 18:00, Stegmeier, Nicholas wrote:

Hello,

I am new to Paraview and C++ coming from a mostly mathematics 
background. I am emailing to get resources or help on writing binary XML 
VTK files from C++.


I have finally succeeded in using the ASCII XML VTK format for a 2D 
rectilinear CFD application. My ".pvtr" file is shown below.


How can I write this file and my other XML VTK files in binary from C++? 
Do I need a special C++ library?

___
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

Re: [Paraview] Best file fomat for big data

2017-11-30 Thread Mark Olesen

A few months back there was a suggestion on the mailing list that you 
can apparently write a single vtk geometry and then use something like 
"map data" to load the new, updated fields (perhaps Ken posted it? - 
don't know any other details).


I agree that these vtk format limitations can be quite frustrating and 
cause quite a bit of data bloat on the disk. For these situations, I 
would normally resort to using EnSight format. This gives you full 
separation of geometry and data, with moving or non-moving geometries 
etc. EnSight does support a server-of-servers data format, which makes 
it possible to a sub-case for each process and then load them together, 
but I've never used it. Instead we have the master process write a 
single file and stream the geometry and fields information across.
The additional overhead of moving data across the network is offset by 
the fact that the filer only has a single process writing to it.


If it helps, you can take a look at the foamToEnsight utility for a 
quick overview: https://develop.openfoam.com
The harder bits are located under src/conversion/ensight/mesh/, 
src/conversion/ensight/output/, src/conversion/ensight/part/


If you find another possibility, please let us know since it will be of 
interest for other people too.


Cheers,
/mark

--
Dr Mark OLESEN
Principal Engineer, ESI-OpenCFD
ESI GmbH | Einsteinring 24 | 85609 Munich | GERMANY
Mob. +49 171 9710 149
www.openfoam.com | www.esi-group.com | mark.ole...@esi-group.com


On 11/30/17 11:13, a...@yandex.ru wrote:
Hi! I just finish my own CFD simulation on 256 processors. The program 
made graphics output in 2000 time points. So large number of outputs I 
need to prepare smooth animation. I use XML VTK ascii format. So I have 
now 2000 pvtu files and 2000*256=512000 vtu files. I have problems with 
such big number of files. Now I understand that may be it was not the 
best idea to use VTK format.
I have the one fixed unstructured grid with ~10^7 cells, about ten CFD 
variables on the cells and several thousands output points. My program 
is MPI parallel and output time points are irregular over time. So I'd 
like to keep value of time in the files (as I know it is impossible in 
the VTK format). And I'd like to use ParaView for the visualization.
What is the better format for storing big amount of CFD data that I be 
able to write in parallel and load in the ParaView?

Thank in advance!

___
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

Re: [Paraview] Use different scalars as timesteps in legacy VTK file

2017-04-28 Thread Mark Olesen

I saw something a few weeks back from someone who mentioned writing out an 
initial vtk file with geometry/data and then using a data mapper for subsequent 
times. I don't have any other details, but may be it is something to search for.

For your original point: I have encountered the same problem with using the vtk 
formats (even with xml).
Each file is completely autonomous, meaning that you are duplicating geometry 
numerous times.
If you have separate files for each field, the situation becomes even worse.
For most of these cases, writing into EnSight format can be an alternative 
(assuming we are talking about mesh data here), but of course adds an 
additional level of complexity when writing. However, if your mesh solely of a 
single element type (eg, the recent posting "Which file format to use for time 
series on tetrahedral mesh"), then writing EnSight format will not be so 
terrible (ie, you won't need to sort elements).

Cheers,
/mark

From: ParaView  on behalf of Nicolas Cedilnik 

Sent: Friday, April 28, 2017 8:46:56 AM
To: paraview@paraview.org
Subject: [Paraview] Use different scalars as timesteps in legacy VTK file

Hello,

I answer my own email because I'm still addressing the same issue as before.
Would it be possible to use the different scalar values in a legacy vtk
file as time steps that paraview can animate?
I'm still looking for a way to avoid storing the same mesh structure in
different files.

Thanks

--
Nicolas Cedilnik
___
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
___
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

Re: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues.

2017-04-19 Thread Mark Olesen

Hi Tom and Utkarsh,

I finally had time to take a closer look.
There is a corresponding merge-request 
https://gitlab.kitware.com/vtk/vtk/merge_requests/2716

Cheers,
/mark


From: Tom Fahner <tom.fah...@gmail.com>
Sent: Monday, April 3, 2017 3:24:19 PM
To: Utkarsh Ayachit
Cc: Mark Olesen; ParaView
Subject: Re: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some 
weird visualization issues.

Hi Utkarsh,

I finally had some time to look into this issue a bit further. I have a 
testcase for you of an Ahmed body that also shows the weird missing of the data.

The case with some intermediate result (approx 400 MB) can be found here:
https://we.tl/ZZwy4ZGL1K

The case without that result (approx 125 MB) can be found here:
https://we.tl/3dSqgyd4zG

Hope this helps in finding the issue. Please let me know if you need more 
information.

Best Regards,
Tom


2017-03-16 13:25 GMT+01:00 Tom Fahner 
<tom.fah...@gmail.com<mailto:tom.fah...@gmail.com>>:
Hi,

Let me check if that is possible, I do not think I can share this particular 
one. I will come back to you.

Tom

2017-03-16 13:12 GMT+01:00 Utkarsh Ayachit 
<utkarsh.ayac...@kitware.com<mailto:utkarsh.ayac...@kitware.com>>:
Tom,

Do you have a dataset to reproduce this issue? There were changes in
the reader in this past release, so it's conceivable that it
introduced a bug.

Utkarsh

On Thu, Mar 16, 2017 at 8:08 AM, Mark Olesen 
<mark.ole...@esi-group.com<mailto:mark.ole...@esi-group.com>> wrote:
> Hi Tom,
>
> So if foamToVTK works, it sounds like a reader bug. Maybe somewhere where the 
> prism order is getting swapped - or something else where the reader's cell 
> modeller is getting into trouble.
> It may not work, but if you try to export from paraview to VTK format (ie, 
> use the OpenFOAM reader for reading). Then with some effort it might be able 
> to identify which cells are different. Presumably the cell ordering will be 
> preserved in both cases, but still not 100% trivial. Either way, we need to 
> figure out which cell types are causing the issue, or an off-by-one of 
> whatever.
>
> /mark
> 
> From: Tom Fahner <tom.fah...@gmail.com<mailto:tom.fah...@gmail.com>>
> Sent: Thursday, March 16, 2017 12:47:05 PM
> To: Mark Olesen
> Cc: ParaView
> Subject: Re: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some 
> weird visualization issues.
>
> Hi Mark,
>
> I have no polyhedral cells (hybrid tetrahedron/prism mesh), so I guess 
> changing "decompose polyhedral on/off" does not make sense. In fact the 
> smaller mesh that I tested with before did show the correct visualization and 
> that mesh had polyhedral/hexagonal cells. It did not matter whether I used 
> decompose polyhedral on/off. I also have experienced the slicing issues from 
> time to time with various paraview versions with polyhedral meshes, but the 
> effect was typically much less severe than in the current situation.
>
> Using foamToVTK (with and without the -poly option) does indeed work and 
> provides the correct visualization. So yes this can be a workaround for now, 
> but I than rather go back to 5.1.2.
>
> Regards,
> Tom
>
> 2017-03-16 11:44 GMT+01:00 Mark Olesen 
> <mark.ole...@esi-group.com<mailto:mark.ole...@esi-group.com><mailto:mark.ole...@esi-group.com<mailto:mark.ole...@esi-group.com>>>:
> Hi Tom,
>
> Sorry, no answers - only questions/ideas:
>
> Is decompose polyhedral on or off? How do things look using the other setting?
> If the number of cells corresponds to checkMesh - then you either have no 
> polyhedra, or decompose polyhedral is off.
> If you use foamToVTK (with and without -poly) and then read the VTK file back 
> in, how does that compare?
> Using foamToEnsight could be yet another check, but without the option to 
> decompose polyhedra.
>
> In most paraview versions I've had issues with slicing through polyhedron 
> (eg, from the motorBike tutorial).
> The symptoms are either holes in the visual (like you have) or crashing the 
> program. I haven't checked if this is better/worse in 5.3.0.
>
> Cheers,
> /mark
> 
> From: ParaView 
> <paraview-boun...@paraview.org<mailto:paraview-boun...@paraview.org><mailto:paraview-boun...@paraview.org<mailto:paraview-boun...@paraview.org>>>
>  on behalf of Tom Fahner 
> <tom.fah...@gmail.com<mailto:tom.fah...@gmail.com><mailto:tom.fah...@gmail.com<mailto:tom.fah...@gmail.com>>>
> Sent: Thursday, March 16, 2017 9:39:49 AM
> To: ParaView
> Subject: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird 
> visualization issues.
>
> Dear

Re: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues.

2017-03-16 Thread Mark Olesen

Hi Tom,

Sorry, no answers - only questions/ideas:

Is decompose polyhedral on or off? How do things look using the other setting?
If the number of cells corresponds to checkMesh - then you either have no 
polyhedra, or decompose polyhedral is off.
If you use foamToVTK (with and without -poly) and then read the VTK file back 
in, how does that compare?
Using foamToEnsight could be yet another check, but without the option to 
decompose polyhedra.

In most paraview versions I've had issues with slicing through polyhedron (eg, 
from the motorBike tutorial).
The symptoms are either holes in the visual (like you have) or crashing the 
program. I haven't checked if this is better/worse in 5.3.0.

Cheers,
/mark

From: ParaView  on behalf of Tom Fahner 

Sent: Thursday, March 16, 2017 9:39:49 AM
To: ParaView
Subject: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird 
visualization issues.

Dear all,

Please find attached two images that show my OpenFOAM model in ParaView 5.3.0. 
It was the standard Binary Installers package downloaded from the website for 
64 bit linux (OpenSUSE Leap 42.1).

The correct number of cells is reported in the information tab (when compared 
to OpenFOAM's checkMesh result). The patches are
all rendered nicely, but it looks like some cells are missing in the 
domain/volume.

Is there some setting that I need to apply?

Please note that the mesh has about 25.8 million cells, for smaller meshes this 
was not a problem. A colleague had similar issues.
ParaView version 5.1.2 did not have this problem, ParaView 5.2 was not able to 
open the OpenFOAM files at all.

Best regards,
Tom

--
T.C. Fahner
e: tom.fah...@gmail.com

___
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

Re: [Paraview] ruler filter in paraview-git

2017-02-02 Thread Mark Olesen

Hi Shawn,

Thanks for the quick reply. The confusion is indeed unfortunately and might be 
cause to consider different names before this becomes a FAQ.

Beyond that, it is a pleasant surprise to see that the 'old' ruler has improved 
functionality compared to the 5.0.1 version. The additional Ctrl-1, Ctrl-2 keys 
for picking the end points make a *very* welcome addition!

Cheers,
/mark


From: Shawn Waldon <shawn.wal...@kitware.com>
Sent: Thursday, February 2, 2017 3:59 PM
To: Mark Olesen
Cc: paraview@paraview.org
Subject: Re: [Paraview] ruler filter in paraview-git

Hi Mark,

So the confusion is that there are now two rulers in ParaView.  The one under 
the filters menu is the one you are seeing.  It was added so that the user 
could measure the dataset in each dimension (and possibly it could be extended 
to selecting other measurements).  The older behavior is the Ruler under the 
Sources menu (it doesn't take an input dataset, but you can freely set its end 
points).  The fact that they are named the same means that the Ctrl-Space 
search favors the one in the filters menu.  Perhaps we could change the name of 
one of them to make it more clear?

HTH,
Shawn

On Thu, Feb 2, 2017 at 9:51 AM, Mark Olesen 
<mark.ole...@esi-group.com<mailto:mark.ole...@esi-group.com>> wrote:
I don't know if this is a regression or change of feature or what exactly.
Using paraview 5.2.0-g332666c (64bit, linux) and the 'ruler' filter only seems 
to have the following properties:
* x/y/z axis enumeration.

That's all. In a previous version (5.0.1) there was also the ability to specify 
the begin/end points and even to select them on an existing mesh point. Now the 
ruler just seems to display the overall length of the object in a particular 
axis.

Is this a feature or bug?

Cheers,
/mark
___
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

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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/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:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] ruler filter in paraview-git

2017-02-02 Thread Mark Olesen

I don't know if this is a regression or change of feature or what exactly.
Using paraview 5.2.0-g332666c (64bit, linux) and the 'ruler' filter only seems 
to have the following properties:
* x/y/z axis enumeration.

That's all. In a previous version (5.0.1) there was also the ability to specify 
the begin/end points and even to select them on an existing mesh point. Now the 
ruler just seems to display the overall length of the object in a particular 
axis.

Is this a feature or bug?

Cheers,
/mark
___
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

Re: [Paraview] combining in on-screen and off-screen in one build

2017-01-19 Thread Mark Olesen

That is rather unfortunate - I guess that I misunderstood what the commits were 
doing.
On the bright side: at least I have a definitive statement about what works and 
what doesn't.

Many thanks for the quick answer.
/mark


From: Utkarsh Ayachit <utkarsh.ayac...@kitware.com>
Sent: Thursday, January 19, 2017 5:40:14 PM
To: Mark Olesen
Cc: paraview@paraview.org
Subject: Re: [Paraview] combining in on-screen and off-screen in one build

To the best of my knowledge, that's not possible, it's not possible to
have GPU accelerated OpenGL and OSMesa in the same build of ParaView.
You have to do separate builds. ParaView does support using osmesa and
libGL provided by Mesa itself in the same build, but that won't be
using GPU, in that case.



On Thu, Jan 19, 2017 at 11:15 AM, Mark Olesen <mark.ole...@esi-group.com> wrote:
> Hi Utkarsh,
>
> Yes we need an off-screen rendering for the server and X11/GPU accelerated 
> for the client.
> As per the FAQ: Can ParaView be built with X11/GPU accelerated OpenGL and 
> OSMesa in the same build?
>
> If I build with osmesa, it seems that I must use PARAVIEW_BUILD_QT_GUI=OFF 
> and VTK_USE_X=OFF to get a build (I'll need to re-verify, since I've tried so 
> many combination). But this seems to preclude building for both hardware and 
> software rendering in the same build?
>
> /mark
> 
> From: Utkarsh Ayachit <utkarsh.ayac...@kitware.com>
> Sent: Thursday, January 19, 2017 4:44:08 PM
> To: Mark Olesen
> Cc: paraview@paraview.org
> Subject: Re: [Paraview] combining in on-screen and off-screen in one build
>
> Mark,
>
> Can you elaborate? When you say opengl + osmesa, do you mean as in
> Mesa+X and OSMesa ?
>
> Utkarsh
>
> On Thu, Jan 19, 2017 at 10:34 AM, Mark Olesen <mark.ole...@esi-group.com> 
> wrote:
>> From commits it looks like 
>> http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D isn't up-to-date. 
>> Can someone offer the cmake variable combinations that I need to compile a 
>> combined build with both opengl + osmesa? If this works well, I'd like to be 
>> using that sooner rather than later.
>>
>> Thanks,
>> /mark
>>
>> ___
>> 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
___
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

[Paraview] combining in on-screen and off-screen in one build

2017-01-19 Thread Mark Olesen

>From commits it looks like 
>http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D isn't up-to-date. 
>Can someone offer the cmake variable combinations that I need to compile a 
>combined build with both opengl + osmesa? If this works well, I'd like to be 
>using that sooner rather than later.

Thanks,
/mark

___
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

Re: [Paraview] ParaView and Qt 5

2017-01-18 Thread Mark Olesen

I'm trying to compile a paraview using a Qt5 (5.7.1) that I've compiled with 
'-qt-xcb' to avoid too many dependencies. When compiling paraview (git 
version), I supposed that the following would be sufficient to convey which qt 
to use:

cmake -DPARAVIEW_BUILD_QT_GUI=ON 
-DQT_QMAKE_EXECUTABLE:FILEPATH=/software/path/qt-5.7.1/bin/qmake 
-DPARAVIEW_QT_VERSION:STRING=5  ...

However, the find_package(Qt5) locates the system Qt and its cmake file, which 
bombs out:

CMake Error at CMake/ParaViewQt.cmake:65 (find_package):
  Could not find a configuration file for package "Qt5" that is compatible
  with requested version "5.6".
  The following configuration files were considered but not accepted:
/usr/lib64/cmake/Qt5/Qt5Config.cmake, version: 5.5.1
/usr/lib64/cmake/Qt5/Qt5Config.cmake, version: 5.5.1
Call Stack (most recent call first):
  Qt/Widgets/CMakeLists.txt:200 (pv_find_package_qt)


Which config variables am I missing?

Thanks,
/mark

From: ParaView  on behalf of Utkarsh Ayachit 

Sent: Monday, January 16, 2017 7:51:36 PM
To: ParaView Developers
Cc: ParaView
Subject: [Paraview] ParaView and Qt 5

Folks,

With upcoming release (5.3), we plan to move to using Qt 5 by default.
Qt 5 has been out since 2012 and it is well supported on modern
platforms. ParaView will continue to build with Qt 4 until further
notice, but we highly recommend custom application developers and
plugin developers to move to Qt 5 at the earliest since active
development and testing for ParaView will happen with Qt 5.

Changes [1] that landed in master earlier today update ParaView to now
use QOpenGLWidget for rendering which creates a frame buffer object to
do all the rendering in. If you have custom mapper or rendering code
that assumed it was rendering to the default onscreen frame buffer, it
will not work correctly and will need to be updated. Please use the
mailing, if you encounter any such issues. For everything else, the
changes should be fairly transparent except in exceptions documented
here [2].

In the upcoming weeks, we will update the superbuild and dashboards to
build and test using Qt 5.

Thanks,
Utkarsh


[1] https://gitlab.kitware.com/paraview/paraview/merge_requests/1279
[2] 
https://gitlab.kitware.com/paraview/paraview/blob/master/Utilities/Doxygen/pages/MajorAPIChanges.md#changes-in-53
___
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
___
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

[Paraview] using tree widgets

2017-01-13 Thread Mark Olesen

I'm currently using an ArraySelectionDomain to select items from (a very long)  
list of mesh-parts (string names) as per 
http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Drop_down_list_with_values_from_input_file

It would be quite helpful if I could structure my list and use a 
tree-selection, but AFICT the closest thing might be a CompositeTreeDomain, but 
either this doesn't actually fit or I haven't figured out how to make it work.

Is this realistic to attempt?
/mark
___
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

Re: [Paraview] upgrading reader module/plugin

2017-01-13 Thread Mark Olesen

Hi Utkarsh,

With many thanks to your hints, I also dug around to see what command_button 
was doing and this corresponds nicely what I needed. I'll put it here for 
anyone browsing the archives.

Cheers
/mark

void fireCommand(vtkSMProperty* prop)
{
vtkSMProxy* pxy = this->proxy();
prop->Modified();
pxy->UpdateProperty(pxy->GetPropertyName(prop));
}

void fireCommand(vtkSMIntVectorProperty* prop, bool checked)
{
vtkSMProxy* pxy = this->proxy();
prop->SetElement(0, checked); // Toogle bool
prop->Modified();
pxy->UpdateProperty(pxy->GetPropertyName(prop));
}



From: Utkarsh Ayachit <utkarsh.ayac...@kitware.com>
Sent: Tuesday, January 10, 2017 9:05 PM
To: Mark Olesen
Cc: paraview@paraview.org
Subject: Re: [Paraview] upgrading reader module/plugin

Mark,

After you've changed a property, you need to call
vtkSMProxy::UpdateVTKObjects() (or vtkSMProxy::UpdateProperty()) to
push those values for them to have any effect. However, in a panel,
you'd rather not do that.

Utkarsh

On Mon, Jan 9, 2017 at 12:31 PM, Mark Olesen <mark.ole...@esi-group.com> wrote:
> The SetImmediateUpdate seems be needed for cases where I do bypass the 
> addPropertyLink mechanism. Eg,
>
> QCheckBox* b = new QCheckBox(this);
> setButtonProperties(b, showPointNumbers_);  //<- text, tips etc...
> form->addWidget(b, 0, 1, Qt::AlignLeft);
>
> connect(b, SIGNAL(toggled(bool)), this, SLOT(showPointNumbers(bool)));
> showPointNumbers_->SetImmediateUpdate(true);
>
> and then
>
> void pqFoamBlockMeshControls::showPointNumbers(bool checked)
> {
> showPointNumbers_->SetElement(0, checked);
>
> // Update the active view
> if (this->view())
> {
> this->view()->render();
> }
> }
>
> Without the SetImmediateUpdate, the toggle of the showPointNumbers property 
> doesn't get propagated to the reader until sometime later. Maybe the key is 
> to signal directly to the reader?
>
> ____
> From: Utkarsh Ayachit <utkarsh.ayac...@kitware.com>
> Sent: Monday, January 9, 2017 4:18 PM
> To: Mark Olesen
> Cc: paraview@paraview.org
> Subject: Re: [Paraview] upgrading reader module/plugin
>
> I don't think `SetImmediateUpdate` should be needed any more. Are you
> sure it's needed? If I remember correctly, it's one of the obselete
> ivars that should truly be deprecated and removed.
>
> On Mon, Jan 9, 2017 at 4:10 AM, Mark Olesen <mark.ole...@esi-group.com> wrote:
>> Hi Utkarsh,
>>
>> The addPropertyLink works exactly as desired and triggers the necessary 
>> update mechanism. For a few places I still have direct connect() to catch 
>> the signal and do something additional with it, but that was expected. I 
>> don't know why I still need an SetImmediateUpdate to get the changes 
>> propagated properly, but that can wait. The most important thing is that I 
>> can now load my reader module in paraview 5.2 and move forward.
>>
>> Thank you,
>> /mark
>>
>> 
>> From: Utkarsh Ayachit <utkarsh.ayac...@kitware.com>
>> Sent: Thursday, January 5, 2017 4:52:32 AM
>> To: Mark Olesen
>> Cc: paraview@paraview.org
>> Subject: Re: [Paraview] upgrading reader module/plugin
>>
>> Mark,
>>
>> As you can expect, connecting Qt widgets to vtkSMProperty's on proxies
>> in a two-way-link is common in ParaView panels and hence ParaView
>> provides quite a few ways for doing that. For your use-case, where
>> you're connecting a QCheckBox to an IntVectorProperty on the proxy,
>> your pqPropertyWidget subclass can do something like the following:
>>
>> Assuming your XML for the group is as follows:
>>
>> QCheckBox *checkbox = ...
>> vtkSMProperty* smProperty = smgroup->GetProperty("InterpolateFields");
>> this->addPropertyLink(checkbox, "checked", SIGNAL(toggled(bool), smProperty);
>>
>> That should do it.
>>
>> Utkarsh
>>
>> On Wed, Jan 4, 2017 at 9:48 AM, Mark Olesen <mark.ole...@esi-group.com> 
>> wrote:
>>> I'm currently upgrading a reader module from using a 
>>> pqAutoGeneratedObjectPanel to a using a property group widget (as per 
>>> http://www.paraview.org/Wiki/Plugin_HowTo#Adding_Customizations_for_Properties_Panel).
>>>
>>> I have my bunch of properties in a PropertyGroup and have a panel_widget 
>>> associated with them. Everything loads up, and using printf() I can verify 
>>> that the property values are all being updated.
>>> However, no

Re: [Paraview] upgrading reader module/plugin

2017-01-09 Thread Mark Olesen

The SetImmediateUpdate seems be needed for cases where I do bypass the 
addPropertyLink mechanism. Eg,

QCheckBox* b = new QCheckBox(this);
setButtonProperties(b, showPointNumbers_);  //<- text, tips etc...
form->addWidget(b, 0, 1, Qt::AlignLeft);

connect(b, SIGNAL(toggled(bool)), this, SLOT(showPointNumbers(bool)));
showPointNumbers_->SetImmediateUpdate(true);

and then 

void pqFoamBlockMeshControls::showPointNumbers(bool checked)
{
showPointNumbers_->SetElement(0, checked);

// Update the active view
if (this->view())
{
this->view()->render();
}
}

Without the SetImmediateUpdate, the toggle of the showPointNumbers property 
doesn't get propagated to the reader until sometime later. Maybe the key is to 
signal directly to the reader?


From: Utkarsh Ayachit <utkarsh.ayac...@kitware.com>
Sent: Monday, January 9, 2017 4:18 PM
To: Mark Olesen
Cc: paraview@paraview.org
Subject: Re: [Paraview] upgrading reader module/plugin

I don't think `SetImmediateUpdate` should be needed any more. Are you
sure it's needed? If I remember correctly, it's one of the obselete
ivars that should truly be deprecated and removed.

On Mon, Jan 9, 2017 at 4:10 AM, Mark Olesen <mark.ole...@esi-group.com> wrote:
> Hi Utkarsh,
>
> The addPropertyLink works exactly as desired and triggers the necessary 
> update mechanism. For a few places I still have direct connect() to catch the 
> signal and do something additional with it, but that was expected. I don't 
> know why I still need an SetImmediateUpdate to get the changes propagated 
> properly, but that can wait. The most important thing is that I can now load 
> my reader module in paraview 5.2 and move forward.
>
> Thank you,
> /mark
>
> 
> From: Utkarsh Ayachit <utkarsh.ayac...@kitware.com>
> Sent: Thursday, January 5, 2017 4:52:32 AM
> To: Mark Olesen
> Cc: paraview@paraview.org
> Subject: Re: [Paraview] upgrading reader module/plugin
>
> Mark,
>
> As you can expect, connecting Qt widgets to vtkSMProperty's on proxies
> in a two-way-link is common in ParaView panels and hence ParaView
> provides quite a few ways for doing that. For your use-case, where
> you're connecting a QCheckBox to an IntVectorProperty on the proxy,
> your pqPropertyWidget subclass can do something like the following:
>
> Assuming your XML for the group is as follows:
>
> QCheckBox *checkbox = ...
> vtkSMProperty* smProperty = smgroup->GetProperty("InterpolateFields");
> this->addPropertyLink(checkbox, "checked", SIGNAL(toggled(bool), smProperty);
>
> That should do it.
>
> Utkarsh
>
> On Wed, Jan 4, 2017 at 9:48 AM, Mark Olesen <mark.ole...@esi-group.com> wrote:
>> I'm currently upgrading a reader module from using a 
>> pqAutoGeneratedObjectPanel to a using a property group widget (as per 
>> http://www.paraview.org/Wiki/Plugin_HowTo#Adding_Customizations_for_Properties_Panel).
>>
>> I have my bunch of properties in a PropertyGroup and have a panel_widget 
>> associated with them. Everything loads up, and using printf() I can verify 
>> that the property values are all being updated.
>> However, not only does it seems rather clunky, I cannot get the "Apply" 
>> button on the property panel to notice when the property values have been 
>> updated.
>>
>> Here's a basic sketch of what I have:
>>
>> // Get the property from the group (with down-cast):
>> interpolateFields_ = group->GetProperty("interpolate");
>>
>> // Provide a checkbox as widget for it - two-column layout.
>>   QCheckBox* b = new QCheckBox(prop->GetXMLLabel(), this);
>>   form->addWidget(b, row, col, Qt::AlignLeft);
>>
>> // Connect to slot:
>> connect(b, SIGNAL(toggled(bool)), this, SLOT(interpolateFields(bool)));
>>
>> // This is ugly, but seems to be needed???
>> interpolateFields_->SetImmediateUpdate(true);
>>
>> // And the slot itself
>> void interpolateFields(bool checked)
>> {
>> interpolateFields_->SetElement(0, checked);
>> // this->setModified();
>> //^^^ used to work with pqAutoGeneratedObjectPanel
>> }
>>
>> I used to rely on the setModified() method from the 
>> pqAutoGeneratedObjectPanel, but now can't seem to get from the SMproxy to 
>> the pqProxy or whatever.
>>
>> Or am I going about this entirely the wrong way?
>> FWIW, here are the relevant sub-entries from the XML, in case there is 
>> something missing there:
>>
>> >   name="InterpolateFields"
>>

Re: [Paraview] upgrading reader module/plugin

2017-01-09 Thread Mark Olesen

Hi Utkarsh,

The addPropertyLink works exactly as desired and triggers the necessary update 
mechanism. For a few places I still have direct connect() to catch the signal 
and do something additional with it, but that was expected. I don't know why I 
still need an SetImmediateUpdate to get the changes propagated properly, but 
that can wait. The most important thing is that I can now load my reader module 
in paraview 5.2 and move forward.

Thank you,
/mark


From: Utkarsh Ayachit <utkarsh.ayac...@kitware.com>
Sent: Thursday, January 5, 2017 4:52:32 AM
To: Mark Olesen
Cc: paraview@paraview.org
Subject: Re: [Paraview] upgrading reader module/plugin

Mark,

As you can expect, connecting Qt widgets to vtkSMProperty's on proxies
in a two-way-link is common in ParaView panels and hence ParaView
provides quite a few ways for doing that. For your use-case, where
you're connecting a QCheckBox to an IntVectorProperty on the proxy,
your pqPropertyWidget subclass can do something like the following:

Assuming your XML for the group is as follows:

QCheckBox *checkbox = ...
vtkSMProperty* smProperty = smgroup->GetProperty("InterpolateFields");
this->addPropertyLink(checkbox, "checked", SIGNAL(toggled(bool), smProperty);

That should do it.

Utkarsh

On Wed, Jan 4, 2017 at 9:48 AM, Mark Olesen <mark.ole...@esi-group.com> wrote:
> I'm currently upgrading a reader module from using a 
> pqAutoGeneratedObjectPanel to a using a property group widget (as per 
> http://www.paraview.org/Wiki/Plugin_HowTo#Adding_Customizations_for_Properties_Panel).
>
> I have my bunch of properties in a PropertyGroup and have a panel_widget 
> associated with them. Everything loads up, and using printf() I can verify 
> that the property values are all being updated.
> However, not only does it seems rather clunky, I cannot get the "Apply" 
> button on the property panel to notice when the property values have been 
> updated.
>
> Here's a basic sketch of what I have:
>
> // Get the property from the group (with down-cast):
> interpolateFields_ = group->GetProperty("interpolate");
>
> // Provide a checkbox as widget for it - two-column layout.
>   QCheckBox* b = new QCheckBox(prop->GetXMLLabel(), this);
>   form->addWidget(b, row, col, Qt::AlignLeft);
>
> // Connect to slot:
> connect(b, SIGNAL(toggled(bool)), this, SLOT(interpolateFields(bool)));
>
> // This is ugly, but seems to be needed???
> interpolateFields_->SetImmediateUpdate(true);
>
> // And the slot itself
> void interpolateFields(bool checked)
> {
> interpolateFields_->SetElement(0, checked);
> // this->setModified();
> //^^^ used to work with pqAutoGeneratedObjectPanel
> }
>
> I used to rely on the setModified() method from the 
> pqAutoGeneratedObjectPanel, but now can't seem to get from the SMproxy to the 
> pqProxy or whatever.
>
> Or am I going about this entirely the wrong way?
> FWIW, here are the relevant sub-entries from the XML, in case there is 
> something missing there:
>
>name="InterpolateFields"
>   command="SetInterpolateVolFields"
>   number_of_elements="1"
>   default_values="1"
>   animateable="0">
>   
>   
> 
>
>label="General Controls"
> panel_widget="my_reader_controls">
> 
> ...
>   
>
> Unfortunately, the  Examples/Plugins/PropertyWidgets is a bit scanty here.
>
> Thanks for any advice,
>
> /mark
>
>
> ___
> 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
___
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

[Paraview] upgrading reader module/plugin

2017-01-04 Thread Mark Olesen

I'm currently upgrading a reader module from using a pqAutoGeneratedObjectPanel 
to a using a property group widget (as per 
http://www.paraview.org/Wiki/Plugin_HowTo#Adding_Customizations_for_Properties_Panel).

I have my bunch of properties in a PropertyGroup and have a panel_widget 
associated with them. Everything loads up, and using printf() I can verify that 
the property values are all being updated.
However, not only does it seems rather clunky, I cannot get the "Apply" button 
on the property panel to notice when the property values have been updated.

Here's a basic sketch of what I have:

// Get the property from the group (with down-cast):
interpolateFields_ = group->GetProperty("interpolate");

// Provide a checkbox as widget for it - two-column layout.
  QCheckBox* b = new QCheckBox(prop->GetXMLLabel(), this);
  form->addWidget(b, row, col, Qt::AlignLeft);

// Connect to slot:
connect(b, SIGNAL(toggled(bool)), this, SLOT(interpolateFields(bool)));

// This is ugly, but seems to be needed???
interpolateFields_->SetImmediateUpdate(true);

// And the slot itself
void interpolateFields(bool checked)
{
interpolateFields_->SetElement(0, checked);
// this->setModified();
//^^^ used to work with pqAutoGeneratedObjectPanel
}

I used to rely on the setModified() method from the pqAutoGeneratedObjectPanel, 
but now can't seem to get from the SMproxy to the pqProxy or whatever.

Or am I going about this entirely the wrong way?
FWIW, here are the relevant sub-entries from the XML, in case there is 
something missing there:


  
  


  

...
  

Unfortunately, the  Examples/Plugins/PropertyWidgets is a bit scanty here.

Thanks for any advice,

/mark


___
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

Re: [Paraview] defining new reader

2010-07-29 Thread Mark Olesen

On Thu, 2010-07-29 at 12:09 -0400, Andy Bauer wrote:
The test file to be read in shouldn't be too large so that the test
actually completes fairly quickly. My best recommendation is to see
how other readers are being test. What type of output does your
reader produce?

It produces an UnstructuredGrid.
Actually it's here if you're interested in taking a look:
http://github.com/olesenm/VTK/blob/custom/IO/vtkProStarReader.h
http://github.com/olesenm/VTK/blob/custom/IO/vtkProStarReader.cxx

The xml layer is still on the Paraview side of things though:
http://github.com/olesenm/ParaView/blob/custom/Servers/ServerManager/Resources/readers.xml

I can easily whip up some small test files with various cell shapes
(tet, polyhedral) etc, but I'm not not actually sure how this is
supposed to be used to check that reader is working correctly.

I would like to get it integrated though into paraview/vtk though.
For CFD geometries (not results), it's a fairly simple, robust,
ASCII-based format that covers all (linear) 2/3-D cell types.

/mark

DISCLAIMER:
This electronic transmission (and any attachments thereto) is intended solely
for the use of the addressee(s). It may contain confidential or legally
privileged information. If you are not the intended recipient of this message,
you must delete it immediately and notify the sender. Any unauthorized use or
disclosure of this message is strictly prohibited. Faurecia does not guarantee
the integrity of this transmission and shall therefore never be liable if the
message is altered or falsified nor for any virus, interception or damage to
your system.

___
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] defining new reader

2010-07-27 Thread Mark Olesen

On Tue, 2010-07-27 at 21:45 -0400, Andy Bauer wrote:
 It looks like the nii file is a NifTI file type which there is a
 plugin for the reader.  If you go to Tools-Plugin Manager you can
 select the NifTI reader and choose Load Selected to the load the
 plugin.  Then you should be able to read in the file without any extra
 work.  
 
 If that doesn't work you can check out the paraview wiki information
 about plugins at http://paraview.org/Wiki/ParaView#Plugins for
 information on creating your own plugin reader.


On a related note: I have a reader that would be useful to contribute to
VTK/paraview. How simple/complex should the test files be for future
dashboard tests?

/mark



DISCLAIMER:
This electronic transmission (and any attachments thereto) is intended solely 
for the use of the addressee(s). It may contain confidential or legally 
privileged information. If you are not the intended recipient of this message, 
you must delete it immediately and notify the sender. Any unauthorized use or 
disclosure of this message is strictly prohibited. Faurecia does not guarantee 
the integrity of this transmission and shall therefore never be liable if the 
message is altered or falsified nor for any virus, interception or damage to 
your system.

___
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: CMake Error at Utilities/VTKClientServer/vtkClientServer.cmake]

2010-04-23 Thread Mark Olesen

 Forwarded Message 
 From: Mark Olesen mark.ole...@faurecia.com
 To: ParaView Developers paraview-develop...@paraview.org
 Subject: CMake Error at
 Utilities/VTKClientServer/vtkClientServer.cmake
 Date: Fri, 23 Apr 2010 16:41:53 +0200

 Since pulling paraview from the new git repository (the last commit now
 being commit be0d83598f), I can't get the cmake stage working at all.

 Building on linux x86_64 (opensuse 11.2) with gcc-4.4.3, qt-4.5.3
 (system version) and cmake-2.8.1

 Here are the parameters that I'm using:

 cmake
 -DCMAKE_INSTALL_PREFIX:PATH=/data/app/OpenFOAM/local/ThirdParty-dev/platforms/linux64Gcc/paraview-3.9.0
 -DVTK_USE_TK:BOOL=OFF
 -DBUILD_SHARED_LIBS:BOOL=ON
 -DVTK_USE_RPATH:BOOL=OFF
 -DCMAKE_BUILD_TYPE:STRING=Release
 -DPARAVIEW_INSTALL_DEVELOPMENT:BOOL=ON
 -DPARAVIEW_GENERATE_PROXY_DOCUMENTATION:BOOL=ON
 -DPARAVIEW_BUILD_QT_GUI=ON
 /data/app/OpenFOAM/local/ThirdParty-dev/paraview-3.9.0

 I'm building in the directory:
 /data/app/OpenFOAM/local/ThirdParty-dev/platforms/build-linux64Gcc/paraview-3.9.0

 This is the error that I'm receiving

 CMake Error at Utilities/VTKClientServer/vtkClientServer.cmake:16
 (INCLUDE):
   include could not find load file:

 /data/app/OpenFOAM/local/ThirdParty-dev/platforms/build-linux64Gcc/paraview-3.9.0/Utilities/Xdmf2/vtk/Utilities/vtkXdmfKit.cmake
 Call Stack (most recent call first):
   Utilities/VTKClientServer/vtkClientServer.cmake:37
 (PV_PRE_WRAP_VTK_CS)
   Utilities/VTKClientServer/Xdmf2/CMakeLists.txt:7 (PV_WRAP_VTK_CS)

 It is apparently looking for a vtkXdmfKit.cmake file within the build
 directory. If I configure a somewhat older version (from the github
 repo: commit 71854e3754), it goes through without any issues.

 Can anyone give a hint at what might have changed to cause this error?

 In the newer git repo, I can checkout a version from March 24 (same date
 as my old github version), but have the same cmake error even although
 they are ostensibly the same versions.

 What am I missing?

 /mark

DISCLAIMER:
This electronic transmission (and any attachments thereto) is intended solely 
for the use of the addressee(s). It may contain confidential or legally 
privileged information. If you are not the intended recipient of this message, 
you must delete it immediately and notify the sender. Any unauthorized use or 
disclosure of this message is strictly prohibited. Faurecia does not guarantee 
the integrity of this transmission and shall therefore never be liable if the 
message is altered or falsified nor for any virus, interception or damage to 
your system.

___
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] [Fwd: CMake Error at Utilities/VTKClientServer/vtkClientServer.cmake]

2010-04-23 Thread Mark Olesen

...
 If you run then cmake, you'll get exactly the error you posted.
 Go back to your ParaView source repository (not the Xdmf2 subdir) and issue
 
 % git submodule update
 Submodule path 'Utilities/Xdmf2': checked out
 '17f7aadc96a0a72c0f8f6e21cd37900db73b1b1f'
 
 then try running cmake again. I bet it'll work then.
 
 Hope that helps.

Perfect - that did it.

Thanks.
/mark



DISCLAIMER:
This electronic transmission (and any attachments thereto) is intended solely 
for the use of the addressee(s). It may contain confidential or legally 
privileged information. If you are not the intended recipient of this message, 
you must delete it immediately and notify the sender. Any unauthorized use or 
disclosure of this message is strictly prohibited. Faurecia does not guarantee 
the integrity of this transmission and shall therefore never be liable if the 
message is altered or falsified nor for any virus, interception or damage to 
your system.

___
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] Probleme to make paraview

2010-04-19 Thread Mark Olesen

On Mon, 2010-04-19 at 10:19 +0200, Stéphane Le Borgne wrote:
 Hi all,
 
 I can't resolve this problem.
 When i compile Paraview, (under Centos 5.x) i always have this
 message :
 
 Linking CXX executable ../../../../../bin/QVTKCxxTests
 /usr/bin/ld: warning: libmpi.so.0, needed
 by ../../../../../bin/libvtkParallel.so.pv3.8, not found (try using
 -rpath or -rpath-link)
 ../../../../../bin/libvtkParallel.so.pv3.8: undefined reference to
 `MPI_Comm_rank'
 ../../../../../bin/libvtkParallel.so.pv3.8: undefined reference to
 `MPI_Win_unlock'
 ../../../../../bin/libvtkParallel.so.pv3.8: undefined reference to
 `ompi_mpi_op_lor'
 ../../../../../bin/libvtkParallel.so.pv3.8: undefined reference to
 `MPI_Abort'
 ../../../../../bin/libvtkParallel.so.pv3.8: undefined reference to
 `ompi_mpi_comm_null'
 
 But libmpi.so is in the PATH.


Is it in the LD_LIBRARY_PATH though?
Or visible via '/sbin/ldconfig -p' ?



/mark


DISCLAIMER:
This electronic transmission (and any attachments thereto) is intended solely 
for the use of the addressee(s). It may contain confidential or legally 
privileged information. If you are not the intended recipient of this message, 
you must delete it immediately and notify the sender. Any unauthorized use or 
disclosure of this message is strictly prohibited. Faurecia does not guarantee 
the integrity of this transmission and shall therefore never be liable if the 
message is altered or falsified nor for any virus, interception or damage to 
your system.

___
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] Paraview: python script from the command line

2010-03-24 Thread Mark Olesen

On Tue, 2010-03-23 at 19:23 -0400, Utkarsh Ayachit wrote:
 I've added a new --script option to specify python script to be run on 
 startup.

This is a bit off-topic, but got me thinking about command-line options
again.

Would there be a way to specify multiple '--data=...' on the
command-line?
For example,

paraview --data=myMesh.foam --data=skin.obj --data=slice.stl

to load several files at once.

/mark


DISCLAIMER:
This electronic transmission (and any attachments thereto) is intended solely 
for the use of the addressee(s). It may contain confidential or legally 
privileged information. If you are not the intended recipient of this message, 
you must delete it immediately and notify the sender. Any unauthorized use or 
disclosure of this message is strictly prohibited. Faurecia does not guarantee 
the integrity of this transmission and shall therefore never be liable if the 
message is altered or falsified nor for any virus, interception or damage to 
your system.

___
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] packaging branded problem

2010-03-17 Thread Mark Olesen

On Wed, 2010-03-17 at 09:01 -0400, Eric E. Monson wrote:
 Thanks, Dave. I really appreciate all of the work on the install and
 packaging stuff, and how quickly you've been making the changes we
 need.

Agreed - it's nice to see that we are now able to build a paraview that
can relocated and still be usable for building plugins without needing
to sed edit a pile of *cmake any more.
And to boot, it'll presumably make the cut for the 3.8 release!

/mark



DISCLAIMER:
This electronic transmission (and any attachments thereto) is intended solely 
for the use of the addressee(s). It may contain confidential or legally 
privileged information. If you are not the intended recipient of this message, 
you must delete it immediately and notify the sender. Any unauthorized use or 
disclosure of this message is strictly prohibited. Faurecia does not guarantee 
the integrity of this transmission and shall therefore never be liable if the 
message is altered or falsified nor for any virus, interception or damage to 
your system.

___
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] Development Install Tree

2010-03-15 Thread Mark Olesen

On Fri, 2010-03-12 at 13:11 -0500, Dave Partyka wrote:
 I just tried this on my Debian machine and the biggest executable in
 my bin dir weighs in at 2.5 MB. Note that this is a Debug build as my
 Release build tree is a bit out of date at the moment. Also all of the
 CMake files appear to be in
 ParaView-3.7.0-Linux-x86_64/lib/paraview-3.7/CMake/ and all of the vtk
 libs are in in ParaView-3.7.0-Linux-x86_64/lib/paraview-3.7/. So this
 is really puzzling. Have you tried doing this from a fresh clean
 build?

I just tried it again (from a fresh build directory and with
GENERATE_FILTERS_DOCUMENTATION:BOOL=ON instead of make
HTMLDocumentation) and it looks a fair bit better. I suspect my
previous problems might have been from mixing build and install
directories.

Using cpack, I no long have monster binaries, just that the VPIC lib
seems to have gone missing:

paraview-real: error while loading shared libraries: libVPIC.so:
cannot open shared object file: No such file or directory

... but it is also getting missed for the make install target too, so
the problem is elsewhere. As a stop-gap, sync'ing the library from the
build directory did the trick.


Apart from the inconvenience of using cpack (I really just want to
create an installed version and not a tar.gz that I have to subsequently
unpack and rename the directories to suit my own conventions), I'm a
disconcerted by that fact that the cpack variant also seems to miss
installing a fair number of files (see attached diff from ls -1R
outputs).

Apart from various missing headers, the resulting cpack'ed installation
doesn't work for building plugins later on since it is missing
vtkWrapClientServer.

make[2]: *** No rule to make target
`paraview-3.7.0/bin/vtkWrapClientServer', needed by ...


The installation with make install did work though.


This seems to be the current status:
- use separate build and install directories!
- use make install -- cpack misses too many files and is too clumsy
for a local install.
- GENERATE_FILTERS_DOCUMENTATION should work, but doesn't.
- make HTMLDocumentation doesn't seem to work either


These tests were made against this commit level:

commit a75e52603fe6c70b36a6a6523f962fc598919a63
Author: KWSys Robot kwro...@kitware.com  
Date:   Fri Mar 12 05:01:10 2010 + 

KWSys Nightly Date Stamp




/mark


DISCLAIMER:
This electronic transmission (and any attachments thereto) is intended solely 
for the use of the addressee(s). It may contain confidential or legally 
privileged information. If you are not the intended recipient of this message, 
you must delete it immediately and notify the sender. Any unauthorized use or 
disclosure of this message is strictly prohibited. Faurecia does not guarantee 
the integrity of this transmission and shall therefore never be liable if the 
message is altered or falsified nor for any virus, interception or damage to 
your system.

--- ls-1R.cpack 2010-03-15 10:36:32.0 +0100
+++ ls-1R.install   2010-03-15 10:36:26.0 +0100
@@ -1,10 +1,12 @@
-paraview-3.7.0-cpack:
+paraview-3.7.0-install:
 bin
 doc
 include
 lib
+plugins
 
-paraview-3.7.0-cpack/bin:
+paraview-3.7.0-install/bin:
+kwProcessXML
 lproj
 paraview
 pvdataserver
@@ -12,14 +14,15 @@
 pvserver
 smTestDriver
 vtkEncodeString
+vtkWrapClientServer
 
-paraview-3.7.0-cpack/doc:
+paraview-3.7.0-install/doc:
 paraview.qch
 
-paraview-3.7.0-cpack/include:
+paraview-3.7.0-install/include:
 paraview-3.7
 
-paraview-3.7.0-cpack/include/paraview-3.7:
+paraview-3.7.0-install/include/paraview-3.7:
 alglib
 DICOMAppHelper.h
 DICOMCallback.h
@@ -465,8 +468,14 @@
 vtkAbstractArray.h
 vtkAbstractCellLocator.h
 vtkAbstractInterpolatedVelocityField.h
+vtkAbstractIterator.h
+vtkAbstractIterator.txx
+vtkAbstractList.h
+vtkAbstractList.txx
+vtkAbstractMap.h
 vtkAbstractMapper3D.h
 vtkAbstractMapper.h
+vtkAbstractMap.txx
 vtkAbstractParticleWriter.h
 vtkAbstractPicker.h
 vtkAbstractPointLocator.h
@@ -532,6 +541,10 @@
 vtkArrayIteratorTemplate.h
 vtkArrayIteratorTemplateImplicit.txx
 vtkArrayIteratorTemplate.txx
+vtkArrayMap.h
+vtkArrayMapIterator.h
+vtkArrayMapIterator.txx
+vtkArrayMap.txx
 vtkArrayNorm.h
 vtkArrayRange.h
 vtkArrayReader.h
@@ -725,6 +738,7 @@
 vtkConnectivityFilter.h
 vtkConstrained2DLayoutStrategy.h
 vtkConstrainedPointHandleRepresentation.h
+vtkContainer.h
 vtkContext2D.h
 vtkContextActor.h
 vtkContextDevice2D.h
@@ -1102,6 +1116,10 @@
 vtkHandleWidget.h
 vtkHardwareSelectionPolyDataPainter.h
 vtkHardwareSelector.h
+vtkHashMap.h
+vtkHashMapIterator.h
+vtkHashMapIterator.txx
+vtkHashMap.txx
 vtkHAVSVolumeMapper.h
 vtkHAVSVolumeMapper_k2BeginFP.h
 vtkHAVSVolumeMapper_k2EndFP.h
@@ -1391,6 +1409,8 @@
 vtkKMeansDistanceFunctor.h
 vtkKMeansStatistics.h
 vtkKochanekSpline.h
+vtkKWProcessStatistics.h
+vtkKWRemoteExecute.h
 vtkLabeledDataMapper.h
 vtkLabeledTreeMapDataMapper.h
 vtkLabelHierarchyAlgorithm.h
@@ -1430,6 +1450,10 @@
 vtkLineWidget2.h
 vtkLineWidget.h
 vtkLinkEdgels.h
+vtkLinkedList.h

Re: [Paraview] Development Install Tree

2010-03-12 Thread Mark Olesen


 Just about all of the bugs related to the development install feature
 have been fixed. If anyone has any issues with them please feel free
 to report a bug.

New bug report added:
http://www.paraview.org/Bug/view.php?id=10411


0010411: Development install tree cannot find documentation Description
With PARAVIEW_INSTALL_DEVELOPMENT turned on.

It looks like the same problem that Paul reported:
www.mail-archive.com/paraview@paraview.org/msg06349.html

- make  make HTMLDocumentation  make install

Both Documentation/ and doc/ directories exist in the install
directory, but paraview reports the following:

QTextBrowser: No document for
qthelp://paraview.org/paraview/ParaViewFilters.html





DISCLAIMER:
This electronic transmission (and any attachments thereto) is intended solely 
for the use of the addressee(s). It may contain confidential or legally 
privileged information. If you are not the intended recipient of this message, 
you must delete it immediately and notify the sender. Any unauthorized use or 
disclosure of this message is strictly prohibited. Faurecia does not guarantee 
the integrity of this transmission and shall therefore never be liable if the 
message is altered or falsified nor for any virus, interception or damage to 
your system.



DISCLAIMER:
This electronic transmission (and any attachments thereto) is intended solely 
for the use of the addressee(s). It may contain confidential or legally 
privileged information. If you are not the intended recipient of this message, 
you must delete it immediately and notify the sender. Any unauthorized use or 
disclosure of this message is strictly prohibited. Faurecia does not guarantee 
the integrity of this transmission and shall therefore never be liable if the 
message is altered or falsified nor for any virus, interception or damage to 
your system.

___
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] Development Install Tree

2010-03-09 Thread Mark Olesen

On Thu, 2010-03-04 at 16:42 -0500, Dave Partyka wrote:
 Greetings Everyone,
 
 
 I have recently commited a fair amount of changes to ParaView that
 lets a developer create a functional development tree that could be
 distributed. The development tree includes all the necessary headers,
 libraries, CMake files and executable tools one would need for
 developing ParaView branded applications and Plugins without building 
 your own ParaView.


For the hard-test with PARAVIEW_INSTALL_DEVELOPMENT turned on.

- make  make install
- relocate the built tree somewhere else
- rename the source tree to another name (to check if the source tree
really isn't needed).

After doing this, and setting ParaView_DIR to point to the new location,
building a separate plugin still fails, due to the following bits from
the plug CMakeLists.txt:

   FIND_PACKAGE(ParaView REQUIRED)
   INCLUDE(${PARAVIEW_USE_FILE})


The $ParaView_DIR/ParaViewConfig.cmake is found and it contains
references to the now non-existent paraview source directory.

If I move $ParaView_DIR/ParaViewConfig.cmake out of the way, the
$ParaView_DIR/lib/paraview-3.7/ParaViewConfig.cmake file is correctly
found and the build succeeds.

Is there a make target that I should be using to avoid this (eg, make
somewhatclean) or should I just move the file out of the way and be
done with it?

/mark



DISCLAIMER:
This electronic transmission (and any attachments thereto) is intended solely 
for the use of the addressee(s). It may contain confidential or legally 
privileged information. If you are not the intended recipient of this message, 
you must delete it immediately and notify the sender. Any unauthorized use or 
disclosure of this message is strictly prohibited. Faurecia does not guarantee 
the integrity of this transmission and shall therefore never be liable if the 
message is altered or falsified nor for any virus, interception or damage to 
your system.

___
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] Development Install Tree

2010-03-09 Thread Mark Olesen

On Tue, 2010-03-09 at 09:08 -0500, Dave Partyka wrote:
 Mark, do you mind reporting this as a bug. The feedback you have
 provided has been very helpful.

Done - http://www.paraview.org/Bug/view.php?id=10394


/mark


DISCLAIMER:
This electronic transmission (and any attachments thereto) is intended solely 
for the use of the addressee(s). It may contain confidential or legally 
privileged information. If you are not the intended recipient of this message, 
you must delete it immediately and notify the sender. Any unauthorized use or 
disclosure of this message is strictly prohibited. Faurecia does not guarantee 
the integrity of this transmission and shall therefore never be liable if the 
message is altered or falsified nor for any virus, interception or damage to 
your system.

___
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] Development Install Tree

2010-03-05 Thread Mark Olesen


 I have recently commited a fair amount of changes to ParaView that
 lets a developer create a functional development tree that could be
 distributed. The development tree includes all the necessary headers,
 libraries, CMake files and executable tools one would need for
 developing ParaView branded applications and Plugins without building
 your own ParaView. 

Seems to have covered many issues. The includes are now landing in the
correct place, but I'm still uncertain about what is or should be going
on with the bin/ vs. lib/paraview-VER files on installation.

I've added a note to the existing issue:

http://www.paraview.org/Bug/view.php?id=8712


/mark





DISCLAIMER:
This electronic transmission (and any attachments thereto) is intended solely 
for the use of the addressee(s). It may contain confidential or legally 
privileged information. If you are not the intended recipient of this message, 
you must delete it immediately and notify the sender. Any unauthorized use or 
disclosure of this message is strictly prohibited. Faurecia does not guarantee 
the integrity of this transmission and shall therefore never be liable if the 
message is altered or falsified nor for any virus, interception or damage to 
your system.

___
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] missing wavefront/obj reader

2010-02-03 Thread Mark Olesen

On Tue, 2009-12-08 at 10:31 -0500, Berk Geveci wrote:
 I am guessing it is an oversight.
 
 -berk
 
 On Tue, Dec 8, 2009 at 8:28 AM, Mark Olesen
 mark.ole...@emcontechnologies.com wrote:
  I was recently had some .obj files to view and noticed to my surprise
  that ParaView doesn't support reading them - I'd guess since they aren't
  mentioned in the Servers/ServerManager/Resources/readers.xml
 
  Is there any reason that they aren't enabled? Or just an oversight?


Who at kitware can make a commit with
   BUG: Added missing vtkOBJReader to ServerManager Resources
?


An example of the (trivial) change required is attached.


/mark
-- 
Mark Olesen mark.ole...@emcontechnologies.com
EMCON Technologies Germany (Augsburg) GmbH

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.

diff --git a/Servers/ServerManager/Resources/readers.xml 
b/Servers/ServerManager/Resources/readers.xml
index 43e28a1..9ed6239 100644
--- a/Servers/ServerManager/Resources/readers.xml
+++ b/Servers/ServerManager/Resources/readers.xml
@@ -3377,6 +3377,30 @@
!-- End byureader --
/SourceProxy

+   SourceProxy name=byureader class=vtkOBJReader label=Wavefront OBJ 
Reader
+ Documentation
+   short_help=Read Wavefront .OBJ files.
+   long_help=Read Wavefront .OBJ files to produce polygonal data.
+   The OBJ reader reads data stored in Wavefront .OBJ format.
+   The expected file extension is .obj, the datasets resulting from 
reading these files are polygonal.
+ /Documentation
+ StringVectorProperty
+name=FileName
+animateable=0
+command=SetFileName
+number_of_elements=1
+FileListDomain name=files/
+Documentation
+  This property specifies the file name for the OBJ reader.
+/Documentation
+ /StringVectorProperty
+ Hints
+  ReaderFactory extensions=obj
+  file_description=Wavefront OBJ Files/
+ /Hints
+   !-- End vtkOBJReader --
+   /SourceProxy
+
SourceProxy name=gaussiancubereader class=vtkGaussianCubeReader
 label=Gaussian Cube Reader
  Documentation
___
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] Exporting ICEM CFD Mesh to ParaView

2010-01-19 Thread Mark Olesen

On Mon, 2010-01-18 at 19:37 -0200, Rafael Castaneda wrote:
 Hi,
 
 I'm trying to export a mesh generated in ICEM CFD to ParaView. I
 realized that I can export the mesh to Exodus II format and then open
 it with ParaView, but no information about the parts of the mesh is
 loaded, just the blocks. 
 
 Any reader available to export geometry and mesh from ICEM CFD to
 ParaView ? I would like that the MultiBlockDataSet generated as result
 have information about the parts created in ICEM CFD.

Writing it as a Fluent mesh might work, but haven't tried it myself.

/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

[Paraview] missing wavefront/obj reader

2009-12-08 Thread Mark Olesen

I was recently had some .obj files to view and noticed to my surprise
that ParaView doesn't support reading them - I'd guess since they aren't
mentioned in the Servers/ServerManager/Resources/readers.xml

Is there any reason that they aren't enabled? Or just an oversight?

/mark
-- 
Mark Olesen mark.ole...@emcontechnologies.com
EMCON Technologies Germany (Augsburg) GmbH

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] Button for LittleEndian / BigEndian in PV 3.6.1

2009-11-11 Thread Mark Olesen

 while switching from ParaView 3.4 to 3.6.1, I recognized that the
 button for choosing LittleEndian / BigEndian has been deleted. Has
 this button just been moved to some other place and I didn't get it or
 do I have to use some python scripting for loading LittleEndian /
 BigEndian files (Ensight Gold format)?

As I remember, the old panel was slightly broken in that you couldn't
use automatic endian detection at all. The new panel now uses the
automatic endian detection and does away with the old explicit choice.

Should we assume from your question that the automatic detection isn't
working for your files?

/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

[Paraview] Improving vtkDataArraySelection ... and a question of the general philosophy

2009-11-04 Thread Mark Olesen

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] Git repository (mirror)

2009-10-30 Thread Mark Olesen

 Yes. At least until we move away from cvs, at which point we may have
 to redo it due to repo changes.

Okay.
Strangely enough just after sending off my query, I am now getting an
error 404 on most of the repositories (including
http://github.com/Kitware).  Oh well, I'll wait and see...



-- 
Mark Olesen mark.ole...@emcontechnologies.com
EMCON Technologies Germany (Augsburg) GmbH

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] Git repository (mirror)

2009-10-30 Thread Mark Olesen

 Hi Berk, 
 
 Is it be possible to have an http access to this mirror (it would be
 very handy to access it over a proxy)? 

Even if the clone only mentions the git: protocol, you can also use a
http transport.

git://github.com/Kitware/ParaView.git
or
http://github.com/Kitware/ParaView.git


Depending on your site, you might also be able to use an ssh tunnel.
Eg,
ssh -N -L 2203:github.com:9418 SOMEHOST
and then
git://localhost:2203/Kitware/ParaView.git

/none

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] Writing XML VTK Binary files from C++

Re: [Paraview] Best file fomat for big data

Re: [Paraview] Use different scalars as timesteps in legacy VTK file

Re: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues.

Re: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues.

Re: [Paraview] ruler filter in paraview-git

[Paraview] ruler filter in paraview-git

Re: [Paraview] combining in on-screen and off-screen in one build

[Paraview] combining in on-screen and off-screen in one build

Re: [Paraview] ParaView and Qt 5

[Paraview] using tree widgets

Re: [Paraview] upgrading reader module/plugin

Re: [Paraview] upgrading reader module/plugin

Re: [Paraview] upgrading reader module/plugin

[Paraview] upgrading reader module/plugin

Re: [Paraview] defining new reader

Re: [Paraview] defining new reader

[Paraview] [Fwd: CMake Error at Utilities/VTKClientServer/vtkClientServer.cmake]

Re: [Paraview] [Fwd: CMake Error at Utilities/VTKClientServer/vtkClientServer.cmake]

Re: [Paraview] Probleme to make paraview

Re: [Paraview] Paraview: python script from the command line

Re: [Paraview] packaging branded problem

Re: [Paraview] Development Install Tree

Re: [Paraview] Development Install Tree

Re: [Paraview] Development Install Tree

Re: [Paraview] Development Install Tree

Re: [Paraview] Development Install Tree

Re: [Paraview] missing wavefront/obj reader

Re: [Paraview] Exporting ICEM CFD Mesh to ParaView

[Paraview] missing wavefront/obj reader

Re: [Paraview] Button for LittleEndian / BigEndian in PV 3.6.1

[Paraview] Improving vtkDataArraySelection ... and a question of the general philosophy

Re: [Paraview] Git repository (mirror)

Re: [Paraview] Git repository (mirror)

34 matches

Site Navigation

Mail list logo

Footer information