From berk.geveci at kitware.com  Wed Jul  1 07:54:38 2015
From: berk.geveci at kitware.com (Berk Geveci)
Date: Wed, 1 Jul 2015 07:54:38 -0400
Subject: [Paraview] Particle Trace from PIV Data
In-Reply-To: <CALOQFAGA3X1M5S1Nxi4zCjm6AL8uEUgaQVALdQJ78+LyrtBXug@mail.gmail.com>
References: <CALOQFAGA3X1M5S1Nxi4zCjm6AL8uEUgaQVALdQJ78+LyrtBXug@mail.gmail.com>
Message-ID: <CAE32kpVyPeXVRywSGst3CMWOBB3sze92zpbLT+wUEcuxNP253A@mail.gmail.com>

Hi Prem,

It would be great if you could share some data to reproduce.

Best,
-berk

On Tue, Jun 30, 2015 at 10:37 AM, Prem Midha <pmidha3 at gatech.edu> wrote:

> I am having trouble with ParaVIEW crashing when trying to view the results
> of a Particle Trace.  It seems to compute without errors, however when I
> hit play, the program crashes.  My input is a series of time-resolved
> discrete vector fields obtained from particle image velocimetry (PIV).  I
> export the field into a series of csv files containing coordinates and
> velocities (x,y,z=0,u,v,w=0).
>
> Has anyone else had issues with this?  Any help would be greatly
> appreciated!
>
> Thanks,
> Prem
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150701/3984999f/attachment.html>

From berk.geveci at kitware.com  Wed Jul  1 08:08:18 2015
From: berk.geveci at kitware.com (Berk Geveci)
Date: Wed, 1 Jul 2015 08:08:18 -0400
Subject: [Paraview] reading classic *.cosmo files in versions greater
	than 3
In-Reply-To: <D1B808DE.312C3%bak@lanl.gov>
References: <D1B808DE.312C3%bak@lanl.gov>
Message-ID: <CAE32kpUtz2xB-P9HmYmJDOB01ge37OCcfLL-87BExogC2B+HhQ@mail.gmail.com>

Hi Bucky,

ParaView 4.3 uses a reader code from the CosmoTools library. This is unlike
previous versions which had a built-in reader. The new reader code is
up-to-date with the current HACC output and is maintained the the HACC
team. Hence the difference. Looking at the CosmoTools library, there seems
to be a compile time option to set the integer types to 32 bits
(TYPE_IDS_64BITS). However, since this is a compile time option in
CosmoTools, the only way to get at this is to recompile CosmoTools and
ParaView. If you are interested in pursuing this option, we can help. We
can't really change the binaries we distribute since the 64 bit tags is
currently what HACC outputs.

Best,
-berk


On Tue, Jun 30, 2015 at 10:50 AM, Kashiwa, Bucky <bak at lanl.gov> wrote:

> We have been very happily reading classical *.cosmo formatted datafiles
> using version 3.98.1, but when reading the same files in subsequent
> versions (4.0, 4.1, 4.2, 4.3) the data get read, but wrongly interpreted.
> I did the diff of the PCosmoReader.h between v3.98.1 and v4.3.1 which
> suggested to me that the last number in the cosmo data (called ?tag?) is
> now int64_t rather than integer.  So if we write the cosmo data with type
> MPI_2INTEGER (~ fortran kind=SELECTED_INT_KIND(15)) then the data are read
> correctly by the v4.3.1 cosmo reader (without byte swap).
>
> If I select the ?Adaptive cosmo reader? from the reader list, it displays
> a button for the ?Tag Size? which can be 32-bit or 64-bit.  This button
> does not appear on the ?Cosmology Files? choice from the reader list.
>
> Could it be that the build system is somehow failing to place the ?Tag
> Size? button on the ?Cosmology Files? Properties panel?  If so, it would
> be wonderful to get it put there so that we can have the choice of Tag
> Size on the very useful .cosmo datafiles.  If not, please let us know if
> we are stuck with a 64-bit Tag Size.
>
> Thanks very much.
> ======================================================================73
> <>Bucky Kashiwa PhD, PE  <> Post: MS B216, Los Alamos, NM  87545       <>
> <>  Ofc: TA3-SM123-RM276 <>Email: bak at lanl.gov, kashiwa at qwest.net      <>
> <>Voice: 505-667-8812    <>  Fax: 505-665-5926  <>
>                          <> Home: 505-988-7332  <> Cell: 505-795-5581  <>
> =======================================================================73
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150701/8d2ca3ae/attachment.html>

From cory.quammen at kitware.com  Wed Jul  1 09:59:38 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 1 Jul 2015 09:59:38 -0400
Subject: [Paraview] segfault playing a simulation
In-Reply-To: <559381DE.5030504@gmail.com>
References: <55895735.2030202@gmail.com>
 <CAB5Fpx4BDY+JDKBbA5Lt02Yt1RLaaZY6TPW9azpZsGf-aWTD7Q@mail.gmail.com>
 <559381DE.5030504@gmail.com>
Message-ID: <CAB5Fpx6H7dY-j86vut03OuVr+7smd+1YwGqL2e771tRE0xdkxw@mail.gmail.com>

Sergi,

I can confirm the crash you are seeing in the same location in the code.
I'm looking for the cause.

What software produced these data files?

Thanks,
Cory

On Wed, Jul 1, 2015 at 1:59 AM, Sergi Mateo Bellido <
sergi.mateo.bellido at gmail.com> wrote:

>  Hi Cory,
>
> Thanks for your answer. I reproduced the segfault in two different ways,
> but it's always after loading a data set:
> - After loading a data set, I tried to play the simulation ->segfault
> - After loading a data set, I tried to filter some fields from the model
> (Pointer array status). As soon as I clicked the 'apply' button, paraview
> crashed with a segfault.
>
> Thanks,
> Sergi
>
>
>
> On 06/30/2015 06:21 AM, Cory Quammen wrote:
>
> Hi Sergi,
>
>  Could you clarify when you are seeing this crash? Is it right when
> starting ParaView or when first loading a data set?
>
>  Thanks,
> Cory
>
> On Tue, Jun 23, 2015 at 8:55 AM, Sergi Mateo Bellido <
> sergi.mateo.bellido at gmail.com> wrote:
>
>>  Hi,
>>
>> I'm trying to reproduce a simulation with ParaView 4.3.1 and it always
>> crashes when I start it. You can find the backtrace below:
>>
>> =========================================================
>> Process id 6681 Caught SIGSEGV at 0x925b124 address not mapped to object
>> Program Stack:
>> WARNING: The stack trace will not use advanced capabilities because this
>> is a release build.
>> 0x7f54ce081d40 : ??? [(???) ???:-1]
>> 0x7f54ce19caf6 : ??? [(???) ???:-1]
>> 0x7f54cb123736 : vtkXMLPStructuredDataReader::CopySubExtent(int*, int*,
>> long long*, int*, int*, long long*, int*, int*, vtkDataArray*,
>> vtkDataArray*) [(libvtkIOXML-pv4.3.so.1) ???:-1]
>> 0x7f54cb12389f :
>> vtkXMLPStructuredDataReader::CopyArrayForPoints(vtkDataArray*,
>> vtkDataArray*) [(libvtkIOXML-pv4.3.so.1) ???:-1]
>> 0x7f54cb11cc1f : vtkXMLPDataReader::ReadPieceData()
>> [(libvtkIOXML-pv4.3.so.1) ???:-1]
>> 0x7f54cb11ca14 : vtkXMLPDataReader::ReadPieceData(int)
>> [(libvtkIOXML-pv4.3.so.1) ???:-1]
>> 0x7f54cb124d7a : vtkXMLPStructuredDataReader::ReadXMLData()
>> [(libvtkIOXML-pv4.3.so.1) ???:-1]
>> 0x7f54cb1280eb : vtkXMLReader::RequestData(vtkInformation*,
>> vtkInformationVector**, vtkInformationVector*) [(libvtkIOXML-pv4.3.so.1)
>> ???:-1]
>> 0x7f54cb1273b6 : vtkXMLReader::ProcessRequest(vtkInformation*,
>> vtkInformationVector**, vtkInformationVector*) [(libvtkIOXML-pv4.3.so.1)
>> ???:-1]
>> 0x7f54cd6200f9 : vtkFileSeriesReader::RequestData(vtkInformation*,
>> vtkInformationVector**, vtkInformationVector*)
>> [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1]
>> 0x7f54cd61f07f : vtkFileSeriesReader::ProcessRequest(vtkInformation*,
>> vtkInformationVector**, vtkInformationVector*)
>> [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1]
>> 0x7f54d2706204 : vtkExecutive::CallAlgorithm(vtkInformation*, int,
>> vtkInformationVector**, vtkInformationVector*)
>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>> 0x7f54d27016cc : vtkDemandDrivenPipeline::ExecuteData(vtkInformation*,
>> vtkInformationVector**, vtkInformationVector*)
>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>> 0x7f54d2700201 : vtkCompositeDataPipeline::ExecuteData(vtkInformation*,
>> vtkInformationVector**, vtkInformationVector*)
>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>> 0x7f54d2704067 : vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>> vtkInformationVector**, vtkInformationVector*)
>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>> 0x7f54d271d959 :
>> vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>> vtkInformationVector**, vtkInformationVector*)
>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>> 0x7f54d26fe387 :
>> vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*)
>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>> 0x7f54d2704010 : vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>> vtkInformationVector**, vtkInformationVector*)
>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>> 0x7f54d271d959 :
>> vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>> vtkInformationVector**, vtkInformationVector*)
>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>> 0x7f54d26fe387 :
>> vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*)
>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>> 0x7f54d2704010 : vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>> vtkInformationVector**, vtkInformationVector*)
>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>> 0x7f54d271d959 :
>> vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>> vtkInformationVector**, vtkInformationVector*)
>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>> 0x7f54d27035ae : vtkDemandDrivenPipeline::UpdateData(int)
>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>> 0x7f54d271e87f : vtkStreamingDemandDrivenPipeline::Update(int)
>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>> 0x7f54cd98fa7f :
>> vtkPVDataRepresentation::ProcessViewRequest(vtkInformationRequestKey*,
>> vtkInformation*, vtkInformation*)
>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>> 0x7f54cd973d79 :
>> vtkGeometryRepresentation::ProcessViewRequest(vtkInformationRequestKey*,
>> vtkInformation*, vtkInformation*)
>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>> 0x7f54cd975d71 :
>> vtkGeometryRepresentationWithFaces::ProcessViewRequest(vtkInformationRequestKey*,
>> vtkInformation*, vtkInformation*)
>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>> 0x7f54cd9bd388 :
>> vtkPVView::CallProcessViewRequest(vtkInformationRequestKey*,
>> vtkInformation*, vtkInformationVector*)
>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>> 0x7f54cd9bd552 : vtkPVView::Update()
>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>> 0x7f54cd9acb78 : vtkPVRenderView::Update()
>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>> 0x7f54d780ac30 : vtkPVRenderViewCommand(vtkClientServerInterpreter*,
>> vtkObjectBase*, char const*, vtkClientServerStream const&,
>> vtkClientServerStream&, void*)
>> [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1]
>> 0x7f54d4e135e0 : vtkClientServerInterpreter::CallCommandFunction(char
>> const*, vtkObjectBase*, char const*, vtkClientServerStream const&,
>> vtkClientServerStream&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>> 0x7f54d4e18393 :
>> vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream
>> const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>> 0x7f54d4e16832 :
>> vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&,
>> int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>> 0x7f54d4e16ced :
>> vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&)
>> [(libvtkClientServer-pv4.3.so.1) ???:-1]
>> 0x7f54d5b26cec :
>> vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool)
>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>> 0x7f54d5b26958 : vtkPVSessionCore::ExecuteStream(unsigned int,
>> vtkClientServerStream const&, bool)
>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>> 0x7f54d5b25203 : vtkPVSessionBase::ExecuteStream(unsigned int,
>> vtkClientServerStream const&, bool)
>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>> 0x7f54cdcae44f : vtkSMViewProxy::Update()
>> [(libvtkPVServerManagerRendering-pv4.3.so.1) ???:-1]
>> 0x7f54cdf2f6f7 : vtkSMAnimationScene::TickInternal(double, double,
>> double) [(libvtkPVAnimation-pv4.3.so.1) ???:-1]
>> 0x7f54cf415cab : vtkAnimationCue::Tick(double, double, double)
>> [(libvtkCommonCore-pv4.3.so.1) ???:-1]
>> 0x7f54cdf23268 : vtkAnimationPlayer::Play()
>> [(libvtkPVAnimation-pv4.3.so.1) ???:-1]
>> 0x7f54d7851619 : vtkSMAnimationSceneCommand(vtkClientServerInterpreter*,
>> vtkObjectBase*, char const*, vtkClientServerStream const&,
>> vtkClientServerStream&, void*)
>> [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1]
>> 0x7f54d4e135e0 : vtkClientServerInterpreter::CallCommandFunction(char
>> const*, vtkObjectBase*, char const*, vtkClientServerStream const&,
>> vtkClientServerStream&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>> 0x7f54d4e18393 :
>> vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream
>> const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>> 0x7f54d4e16832 :
>> vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&,
>> int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>> 0x7f54d4e16ced :
>> vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&)
>> [(libvtkClientServer-pv4.3.so.1) ???:-1]
>> 0x7f54d5b436d4 : vtkSIProperty::ProcessMessage(vtkClientServerStream&)
>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>> 0x7f54d5b4377e : vtkSIProperty::Push(paraview_protobuf::Message*, int)
>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>> 0x7f54d5b4459e : vtkSIProxy::Push(paraview_protobuf::Message*)
>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>> 0x7f54d5b2884a :
>> vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*)
>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>> 0x7f54d5b27484 : vtkPVSessionCore::PushState(paraview_protobuf::Message*)
>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>> 0x7f54d5b2514d : vtkPVSessionBase::PushState(paraview_protobuf::Message*)
>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>> 0x7f54d5d859b7 : vtkSMProxy::UpdateProperty(char const*, int)
>> [(libvtkPVServerManagerCore-pv4.3.so.1) ???:-1]
>> 0x7f54d6d8aa07 : pqVCRController::onPlay()
>> [(libvtkpqComponents-pv4.3.so.1) ???:-1]
>> 0x7f54cfa98258 : QMetaObject::activate(QObject*, QMetaObject const*, int,
>> void**) [(libQtCore.so.4) ???:-1]
>> 0x7f54d01102f2 : QAction::triggered(bool) [(libQtGui.so.4) ???:-1]
>> 0x7f54d0111710 : QAction::activate(QAction::ActionEvent) [(libQtGui.so.4)
>> ???:-1]
>> 0x7f54d04fd514 : ??? [(???) ???:-1]
>> 0x7f54d04fd7ab : QAbstractButton::mouseReleaseEvent(QMouseEvent*)
>> [(libQtGui.so.4) ???:-1]
>> 0x7f54d05d15ea : QToolButton::mouseReleaseEvent(QMouseEvent*)
>> [(libQtGui.so.4) ???:-1]
>> 0x7f54d0175ac1 : QWidget::event(QEvent*) [(libQtGui.so.4) ???:-1]
>> 0x7f54d04fca3f : QAbstractButton::event(QEvent*) [(libQtGui.so.4) ???:-1]
>> 0x7f54d05d422d : QToolButton::event(QEvent*) [(libQtGui.so.4) ???:-1]
>> 0x7f54d011759e : QApplicationPrivate::notify_helper(QObject*, QEvent*)
>> [(libQtGui.so.4) ???:-1]
>> 0x7f54d011e533 : QApplication::notify(QObject*, QEvent*) [(libQtGui.so.4)
>> ???:-1]
>> 0x7f54cfa802f3 : QCoreApplication::notifyInternal(QObject*, QEvent*)
>> [(libQtCore.so.4) ???:-1]
>> 0x7f54d011a656 : QApplicationPrivate::sendMouseEvent(QWidget*,
>> QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool)
>> [(libQtGui.so.4) ???:-1]
>> 0x7f54d019ca94 : ??? [(???) ???:-1]
>> 0x7f54d019b877 : QApplication::x11ProcessEvent(_XEvent*) [(libQtGui.so.4)
>> ???:-1]
>> 0x7f54d01c4805 : ??? [(???) ???:-1]
>> 0x7f54cfa7f375 :
>> QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
>> [(libQtCore.so.4) ???:-1]
>> 0x7f54cfa7f748 : QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
>> [(libQtCore.so.4) ???:-1]
>> 0x7f54cfa8414b : QCoreApplication::exec() [(libQtCore.so.4) ???:-1]
>> 0x407785 : main [(paraview) ???:-1]
>> 0x7f54ce06cec5 : __libc_start_main [(libc.so.6) ???:-1]
>> 0x4074da : QMainWindow::event(QEvent*) [(paraview) ???:-1]
>> =========================================================
>>
>> Thanks,
>>
>> Sergi Mateo
>> sergi.mateo.bellido at 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
>>
>>
>
>
>  --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150701/d8f9f2af/attachment.html>

From aashish.chaudhary at kitware.com  Wed Jul  1 10:07:26 2015
From: aashish.chaudhary at kitware.com (Aashish Chaudhary)
Date: Wed, 1 Jul 2015 10:07:26 -0400
Subject: [Paraview] Volume rendering on OS X with Nvidia graphics card
In-Reply-To: <D1B73894.7C9A5%hahnse@ornl.gov>
References: <D1B70E83.7C984%hahnse@ornl.gov> <D1B73894.7C9A5%hahnse@ornl.gov>
Message-ID: <CAEw35Z8pt6iNDgXeeQRbE_NP8LgoY1tZtVmDnok-jxnCJ8EjVQ@mail.gmail.com>

Hi Steven,

This is odd since the OpenGL2 mapper should have detected FBO support. I
will have a look at it.

- aashish

On Mon, Jun 29, 2015 at 6:06 PM, Hahn, Steven E. <hahnse at ornl.gov> wrote:

>  I am observing some odd results with volume rendering using ParaView
> 4.3.1 and ParaView master on OS X machines with NVIDIA graphics cards
> including a Geforce 650m in a macbook pro and a Quadro K5000 in a mac pro.
> On the mac pro, changing between the NVIDIA web driver and OS X default
> driver has no effect.
>
>  1) After loading a vtkImageData file and selecting the volume
> representation and the GPU based volume rendering mode, the image
> disappears. The other volume rendering modes show the image correctly. I
> also tried building ParaView master with the OpenGL2 rendering backend and
> in that case the GPU based volume rendering mode displays only some of the
> surfaces (2-4, the exact number depends on the camera position) and not the
> entire volume.
>
>  2) I also tried loading a small vtkStructuredGrid (attached) into
> ParaView master built with the OpenGL2 rendering backend and get the
> warning below.  There are substantial artifacts that are not present when
> the OpenGL rendering backend is used. These artifacts don?t appear when I
> load the same file in ParaView 4.3.1 or ParaView master build with the
> OpenGL rendering backend.
>
>   Warning: In
> ../VTK/Rendering/VolumeOpenGL2/vtkOpenGLProjectedTetrahedraMapper.cxx, line
> 151
>
> vtkOpenGLProjectedTetrahedraMapper (0x7fdc49d3a140): Missing FBO support.
> The algorithm may produce visual artifacts.
>
>
>  I tried running glxinfo and under OpenGL extensions it does
> list GL_ARB_framebuffer_object, GL_ARB_draw_buffers and
> GL_ARB_texture_float. VTK, however, doesn?t appear to be detecting this.
>
>
>  Sincerely,
>
> Steven Hahn
>
> _______________________________________________
> 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
>
>


-- 



*| Aashish Chaudhary | Technical Leader         | Kitware Inc.            *
*| http://www.kitware.com/company/team/chaudhary.html
<http://www.kitware.com/company/team/chaudhary.html>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150701/6fb4bda4/attachment.html>

From mvanmoer at illinois.edu  Wed Jul  1 10:06:02 2015
From: mvanmoer at illinois.edu (Vanmoer, Mark W)
Date: Wed, 1 Jul 2015 14:06:02 +0000
Subject: [Paraview] using pvbatch to write pvti/vti file sets
In-Reply-To: <CAMaOp+H4ynhBVPoS=DHTj1_CDWG+tdcyaad7ECj+BkVEGS5obg@mail.gmail.com>
References: <7F781841FF1E044388AFA42B70703A7A8A2116AE@CHIMBX6.ad.uillinois.edu>,
 <CAMaOp+H4ynhBVPoS=DHTj1_CDWG+tdcyaad7ECj+BkVEGS5obg@mail.gmail.com>
Message-ID: <7F781841FF1E044388AFA42B70703A7A8A2117C1@CHIMBX6.ad.uillinois.edu>

Hi Andy,

D'oh! sorry, pvbatch does work as expected.

Mark
________________________________
From: Andy Bauer [andy.bauer at kitware.com]
Sent: Tuesday, June 30, 2015 8:22 PM
To: Vanmoer, Mark W
Cc: paraview at paraview.org
Subject: Re: [Paraview] using pvbatch to write pvti/vti file sets

Hi Mark,

Is that a typo or are you really using pvpython? You said "aprun -n 32 pvpython myscript.py". Otherwise I don't see anything that shouldn't work.

Best,
Andy

On Tue, Jun 30, 2015 at 6:22 PM, Vanmoer, Mark W <mvanmoer at illinois.edu<mailto:mvanmoer at illinois.edu>> wrote:
Hi ParaView,

When using the client GUI, Save Data will write out a pvti/vti data set with a vti for each processor. When trying this with pvbatch I'm only getting a single vti. I'm calling the pvbatch with

aprun -n 32 pvpython myscript.py

which I think should generate 1 pvti and 32 vtis. This is using ParaView 4.1.0.

myscript.py is a hack, I'm reading a pvti that's split into 8192 vtis and trying to re-write out fewer, say 32 or 64. This is part of troubleshooting what I think might be a lustre issue.

# myscript.py
try: paraview.simple
except: from paraview.simple import *
servermanager.Connect()
reader = XMLPartitionedImageDataReader(FileName=['test-input.pvti'])
writer = XMLPImageDataWriter()
writer.Input = reader
writer.CompressorType = 'ZLib'
writer.FileName = 'test-output.pvti'
writer.UpdatePipeline()

Is what I want to do possible? If not, is there a recommended way to merge vtis?
Mark
_______________________________________________
Powered by www.kitware.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kitware.com&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=FYRr2IRSLUsU98QEhG1ScsWGNG85f-iklhRsXaWue-k&s=9fediAVmL563U6KShySm176URh1DM70ETlyJhG8u7AM&e=>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kitware.com_opensource_opensource.html&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=FYRr2IRSLUsU98QEhG1ScsWGNG85f-iklhRsXaWue-k&s=Wj5hjGAR74CfOQUDW0sw88EMHMgFNZ_zek_tUhu6Gz4&e=>

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView<https://urldefense.proofpoint.com/v2/url?u=http-3A__paraview.org_Wiki_ParaView&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=FYRr2IRSLUsU98QEhG1ScsWGNG85f-iklhRsXaWue-k&s=FJbIuTSIIxRiTve_tWtxdGDmx7WllU6S2qWQwqxJZo8&e=>

Search the list archives at: http://markmail.org/search/?q=ParaView<https://urldefense.proofpoint.com/v2/url?u=http-3A__markmail.org_search_-3Fq-3DParaView&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=FYRr2IRSLUsU98QEhG1ScsWGNG85f-iklhRsXaWue-k&s=CqMwVmWlDzCrB7VRgV7ofoZRLZHY6rTyAM0AuudwUxQ&e=>

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview<https://urldefense.proofpoint.com/v2/url?u=http-3A__public.kitware.com_mailman_listinfo_paraview&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=FYRr2IRSLUsU98QEhG1ScsWGNG85f-iklhRsXaWue-k&s=HOk0AAYBmDzFL50zt2aO4uUhQmkSaL3IRTByEtTKWCk&e=>

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

From andy.bauer at kitware.com  Wed Jul  1 10:23:35 2015
From: andy.bauer at kitware.com (Andy Bauer)
Date: Wed, 1 Jul 2015 10:23:35 -0400
Subject: [Paraview] using pvbatch to write pvti/vti file sets
In-Reply-To: <7F781841FF1E044388AFA42B70703A7A8A2117C1@CHIMBX6.ad.uillinois.edu>
References: <7F781841FF1E044388AFA42B70703A7A8A2116AE@CHIMBX6.ad.uillinois.edu>
 <CAMaOp+H4ynhBVPoS=DHTj1_CDWG+tdcyaad7ECj+BkVEGS5obg@mail.gmail.com>
 <7F781841FF1E044388AFA42B70703A7A8A2117C1@CHIMBX6.ad.uillinois.edu>
Message-ID: <CAMaOp+EwQQfwc7=S-P7qRjHEtnTKaxKqBHR+a-rJFK5-DPkwZQ@mail.gmail.com>

Great -- I like the easy questions :)

On Wed, Jul 1, 2015 at 10:06 AM, Vanmoer, Mark W <mvanmoer at illinois.edu>
wrote:

>  Hi Andy,
>
> D'oh! sorry, pvbatch does work as expected.
>
> Mark
>  ------------------------------
> *From:* Andy Bauer [andy.bauer at kitware.com]
> *Sent:* Tuesday, June 30, 2015 8:22 PM
> *To:* Vanmoer, Mark W
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] using pvbatch to write pvti/vti file sets
>
>   Hi Mark,
>
>  Is that a typo or are you really using pvpython? You said "aprun -n 32
> pvpython myscript.py". Otherwise I don't see anything that shouldn't work.
>
>  Best,
>  Andy
>
> On Tue, Jun 30, 2015 at 6:22 PM, Vanmoer, Mark W <mvanmoer at illinois.edu>
> wrote:
>
>> Hi ParaView,
>>
>> When using the client GUI, Save Data will write out a pvti/vti data set
>> with a vti for each processor. When trying this with pvbatch I'm only
>> getting a single vti. I'm calling the pvbatch with
>>
>> aprun -n 32 pvpython myscript.py
>>
>> which I think should generate 1 pvti and 32 vtis. This is using ParaView
>> 4.1.0.
>>
>> myscript.py is a hack, I'm reading a pvti that's split into 8192 vtis and
>> trying to re-write out fewer, say 32 or 64. This is part of troubleshooting
>> what I think might be a lustre issue.
>>
>> # myscript.py
>> try: paraview.simple
>> except: from paraview.simple import *
>> servermanager.Connect()
>> reader = XMLPartitionedImageDataReader(FileName=['test-input.pvti'])
>> writer = XMLPImageDataWriter()
>> writer.Input = reader
>> writer.CompressorType = 'ZLib'
>> writer.FileName = 'test-output.pvti'
>> writer.UpdatePipeline()
>>
>> Is what I want to do possible? If not, is there a recommended way to
>> merge vtis?
>> Mark
>> _______________________________________________
>> Powered by www.kitware.com
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kitware.com&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=FYRr2IRSLUsU98QEhG1ScsWGNG85f-iklhRsXaWue-k&s=9fediAVmL563U6KShySm176URh1DM70ETlyJhG8u7AM&e=>
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kitware.com_opensource_opensource.html&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=FYRr2IRSLUsU98QEhG1ScsWGNG85f-iklhRsXaWue-k&s=Wj5hjGAR74CfOQUDW0sw88EMHMgFNZ_zek_tUhu6Gz4&e=>
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__paraview.org_Wiki_ParaView&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=FYRr2IRSLUsU98QEhG1ScsWGNG85f-iklhRsXaWue-k&s=FJbIuTSIIxRiTve_tWtxdGDmx7WllU6S2qWQwqxJZo8&e=>
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__markmail.org_search_-3Fq-3DParaView&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=FYRr2IRSLUsU98QEhG1ScsWGNG85f-iklhRsXaWue-k&s=CqMwVmWlDzCrB7VRgV7ofoZRLZHY6rTyAM0AuudwUxQ&e=>
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__public.kitware.com_mailman_listinfo_paraview&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=FYRr2IRSLUsU98QEhG1ScsWGNG85f-iklhRsXaWue-k&s=HOk0AAYBmDzFL50zt2aO4uUhQmkSaL3IRTByEtTKWCk&e=>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150701/3609a6e7/attachment.html>

From sergi.mateo.bellido at gmail.com  Wed Jul  1 13:27:11 2015
From: sergi.mateo.bellido at gmail.com (Sergi Mateo Bellido)
Date: Wed, 01 Jul 2015 19:27:11 +0200
Subject: [Paraview] segfault playing a simulation
In-Reply-To: <CAB5Fpx6H7dY-j86vut03OuVr+7smd+1YwGqL2e771tRE0xdkxw@mail.gmail.com>
References: <55895735.2030202@gmail.com>	<CAB5Fpx4BDY+JDKBbA5Lt02Yt1RLaaZY6TPW9azpZsGf-aWTD7Q@mail.gmail.com>	<559381DE.5030504@gmail.com>
 <CAB5Fpx6H7dY-j86vut03OuVr+7smd+1YwGqL2e771tRE0xdkxw@mail.gmail.com>
Message-ID: <559422EF.3070304@gmail.com>

Hi Cory,

Thanks for your time. These data files have been produced by a software 
that I'm developing with some colleagues.

Best regards,

Sergi

On 07/01/2015 03:59 PM, Cory Quammen wrote:
> Sergi,
>
> I can confirm the crash you are seeing in the same location in the 
> code. I'm looking for the cause.
>
> What software produced these data files?
>
> Thanks,
> Cory
>
> On Wed, Jul 1, 2015 at 1:59 AM, Sergi Mateo Bellido 
> <sergi.mateo.bellido at gmail.com <mailto:sergi.mateo.bellido at gmail.com>> 
> wrote:
>
>     Hi Cory,
>
>     Thanks for your answer. I reproduced the segfault in two different
>     ways, but it's always after loading a data set:
>     - After loading a data set, I tried to play the simulation ->segfault
>     - After loading a data set, I tried to filter some fields from the
>     model (Pointer array status). As soon as I clicked the 'apply'
>     button, paraview crashed with a segfault.
>
>     Thanks,
>     Sergi
>
>
>
>     On 06/30/2015 06:21 AM, Cory Quammen wrote:
>>     Hi Sergi,
>>
>>     Could you clarify when you are seeing this crash? Is it right
>>     when starting ParaView or when first loading a data set?
>>
>>     Thanks,
>>     Cory
>>
>>     On Tue, Jun 23, 2015 at 8:55 AM, Sergi Mateo Bellido
>>     <sergi.mateo.bellido at gmail.com
>>     <mailto:sergi.mateo.bellido at gmail.com>> wrote:
>>
>>         Hi,
>>
>>         I'm trying to reproduce a simulation with ParaView 4.3.1 and
>>         it always crashes when I start it. You can find the backtrace
>>         below:
>>
>>         =========================================================
>>         Process id 6681 Caught SIGSEGV at 0x925b124 address not
>>         mapped to object
>>         Program Stack:
>>         WARNING: The stack trace will not use advanced capabilities
>>         because this is a release build.
>>         0x7f54ce081d40 : ??? [(???) ???:-1]
>>         0x7f54ce19caf6 : ??? [(???) ???:-1]
>>         0x7f54cb123736 :
>>         vtkXMLPStructuredDataReader::CopySubExtent(int*, int*, long
>>         long*, int*, int*, long long*, int*, int*, vtkDataArray*,
>>         vtkDataArray*) [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>         0x7f54cb12389f :
>>         vtkXMLPStructuredDataReader::CopyArrayForPoints(vtkDataArray*, vtkDataArray*)
>>         [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>         0x7f54cb11cc1f : vtkXMLPDataReader::ReadPieceData()
>>         [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>         0x7f54cb11ca14 : vtkXMLPDataReader::ReadPieceData(int)
>>         [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>         0x7f54cb124d7a : vtkXMLPStructuredDataReader::ReadXMLData()
>>         [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>         0x7f54cb1280eb : vtkXMLReader::RequestData(vtkInformation*,
>>         vtkInformationVector**, vtkInformationVector*)
>>         [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>         0x7f54cb1273b6 :
>>         vtkXMLReader::ProcessRequest(vtkInformation*,
>>         vtkInformationVector**, vtkInformationVector*)
>>         [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>         0x7f54cd6200f9 :
>>         vtkFileSeriesReader::RequestData(vtkInformation*,
>>         vtkInformationVector**, vtkInformationVector*)
>>         [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1]
>>         0x7f54cd61f07f :
>>         vtkFileSeriesReader::ProcessRequest(vtkInformation*,
>>         vtkInformationVector**, vtkInformationVector*)
>>         [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1]
>>         0x7f54d2706204 : vtkExecutive::CallAlgorithm(vtkInformation*,
>>         int, vtkInformationVector**, vtkInformationVector*)
>>         [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>         0x7f54d27016cc :
>>         vtkDemandDrivenPipeline::ExecuteData(vtkInformation*,
>>         vtkInformationVector**, vtkInformationVector*)
>>         [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>         0x7f54d2700201 :
>>         vtkCompositeDataPipeline::ExecuteData(vtkInformation*,
>>         vtkInformationVector**, vtkInformationVector*)
>>         [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>         0x7f54d2704067 :
>>         vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>         vtkInformationVector**, vtkInformationVector*)
>>         [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>         0x7f54d271d959 :
>>         vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>         vtkInformationVector**, vtkInformationVector*)
>>         [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>         0x7f54d26fe387 :
>>         vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*)
>>         [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>         0x7f54d2704010 :
>>         vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>         vtkInformationVector**, vtkInformationVector*)
>>         [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>         0x7f54d271d959 :
>>         vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>         vtkInformationVector**, vtkInformationVector*)
>>         [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>         0x7f54d26fe387 :
>>         vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*)
>>         [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>         0x7f54d2704010 :
>>         vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>         vtkInformationVector**, vtkInformationVector*)
>>         [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>         0x7f54d271d959 :
>>         vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>         vtkInformationVector**, vtkInformationVector*)
>>         [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>         0x7f54d27035ae : vtkDemandDrivenPipeline::UpdateData(int)
>>         [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>         0x7f54d271e87f :
>>         vtkStreamingDemandDrivenPipeline::Update(int)
>>         [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>         0x7f54cd98fa7f :
>>         vtkPVDataRepresentation::ProcessViewRequest(vtkInformationRequestKey*,
>>         vtkInformation*, vtkInformation*)
>>         [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>         0x7f54cd973d79 :
>>         vtkGeometryRepresentation::ProcessViewRequest(vtkInformationRequestKey*,
>>         vtkInformation*, vtkInformation*)
>>         [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>         0x7f54cd975d71 :
>>         vtkGeometryRepresentationWithFaces::ProcessViewRequest(vtkInformationRequestKey*,
>>         vtkInformation*, vtkInformation*)
>>         [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>         0x7f54cd9bd388 :
>>         vtkPVView::CallProcessViewRequest(vtkInformationRequestKey*,
>>         vtkInformation*, vtkInformationVector*)
>>         [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>         0x7f54cd9bd552 : vtkPVView::Update()
>>         [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>         0x7f54cd9acb78 : vtkPVRenderView::Update()
>>         [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>         0x7f54d780ac30 :
>>         vtkPVRenderViewCommand(vtkClientServerInterpreter*,
>>         vtkObjectBase*, char const*, vtkClientServerStream const&,
>>         vtkClientServerStream&, void*)
>>         [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1]
>>         0x7f54d4e135e0 :
>>         vtkClientServerInterpreter::CallCommandFunction(char const*,
>>         vtkObjectBase*, char const*, vtkClientServerStream const&,
>>         vtkClientServerStream&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>         0x7f54d4e18393 :
>>         vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream
>>         const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>         0x7f54d4e16832 :
>>         vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream
>>         const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>         0x7f54d4e16ced :
>>         vtkClientServerInterpreter::ProcessStream(vtkClientServerStream
>>         const&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>         0x7f54d5b26cec :
>>         vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream
>>         const&, bool) [(libvtkPVServerImplementationCore-pv4.3.so.1)
>>         ???:-1]
>>         0x7f54d5b26958 : vtkPVSessionCore::ExecuteStream(unsigned
>>         int, vtkClientServerStream const&, bool)
>>         [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>         0x7f54d5b25203 : vtkPVSessionBase::ExecuteStream(unsigned
>>         int, vtkClientServerStream const&, bool)
>>         [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>         0x7f54cdcae44f : vtkSMViewProxy::Update()
>>         [(libvtkPVServerManagerRendering-pv4.3.so.1) ???:-1]
>>         0x7f54cdf2f6f7 : vtkSMAnimationScene::TickInternal(double,
>>         double, double) [(libvtkPVAnimation-pv4.3.so.1) ???:-1]
>>         0x7f54cf415cab : vtkAnimationCue::Tick(double, double,
>>         double) [(libvtkCommonCore-pv4.3.so.1) ???:-1]
>>         0x7f54cdf23268 : vtkAnimationPlayer::Play()
>>         [(libvtkPVAnimation-pv4.3.so.1) ???:-1]
>>         0x7f54d7851619 :
>>         vtkSMAnimationSceneCommand(vtkClientServerInterpreter*,
>>         vtkObjectBase*, char const*, vtkClientServerStream const&,
>>         vtkClientServerStream&, void*)
>>         [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1]
>>         0x7f54d4e135e0 :
>>         vtkClientServerInterpreter::CallCommandFunction(char const*,
>>         vtkObjectBase*, char const*, vtkClientServerStream const&,
>>         vtkClientServerStream&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>         0x7f54d4e18393 :
>>         vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream
>>         const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>         0x7f54d4e16832 :
>>         vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream
>>         const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>         0x7f54d4e16ced :
>>         vtkClientServerInterpreter::ProcessStream(vtkClientServerStream
>>         const&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>         0x7f54d5b436d4 :
>>         vtkSIProperty::ProcessMessage(vtkClientServerStream&)
>>         [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>         0x7f54d5b4377e :
>>         vtkSIProperty::Push(paraview_protobuf::Message*, int)
>>         [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>         0x7f54d5b4459e :
>>         vtkSIProxy::Push(paraview_protobuf::Message*)
>>         [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>         0x7f54d5b2884a :
>>         vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*)
>>         [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>         0x7f54d5b27484 :
>>         vtkPVSessionCore::PushState(paraview_protobuf::Message*)
>>         [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>         0x7f54d5b2514d :
>>         vtkPVSessionBase::PushState(paraview_protobuf::Message*)
>>         [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>         0x7f54d5d859b7 : vtkSMProxy::UpdateProperty(char const*, int)
>>         [(libvtkPVServerManagerCore-pv4.3.so.1) ???:-1]
>>         0x7f54d6d8aa07 : pqVCRController::onPlay()
>>         [(libvtkpqComponents-pv4.3.so.1) ???:-1]
>>         0x7f54cfa98258 : QMetaObject::activate(QObject*, QMetaObject
>>         const*, int, void**) [(libQtCore.so.4) ???:-1]
>>         0x7f54d01102f2 : QAction::triggered(bool) [(libQtGui.so.4)
>>         ???:-1]
>>         0x7f54d0111710 : QAction::activate(QAction::ActionEvent)
>>         [(libQtGui.so.4) ???:-1]
>>         0x7f54d04fd514 : ??? [(???) ???:-1]
>>         0x7f54d04fd7ab :
>>         QAbstractButton::mouseReleaseEvent(QMouseEvent*)
>>         [(libQtGui.so.4) ???:-1]
>>         0x7f54d05d15ea : QToolButton::mouseReleaseEvent(QMouseEvent*)
>>         [(libQtGui.so.4) ???:-1]
>>         0x7f54d0175ac1 : QWidget::event(QEvent*) [(libQtGui.so.4) ???:-1]
>>         0x7f54d04fca3f : QAbstractButton::event(QEvent*)
>>         [(libQtGui.so.4) ???:-1]
>>         0x7f54d05d422d : QToolButton::event(QEvent*) [(libQtGui.so.4)
>>         ???:-1]
>>         0x7f54d011759e : QApplicationPrivate::notify_helper(QObject*,
>>         QEvent*) [(libQtGui.so.4) ???:-1]
>>         0x7f54d011e533 : QApplication::notify(QObject*, QEvent*)
>>         [(libQtGui.so.4) ???:-1]
>>         0x7f54cfa802f3 : QCoreApplication::notifyInternal(QObject*,
>>         QEvent*) [(libQtCore.so.4) ???:-1]
>>         0x7f54d011a656 :
>>         QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*,
>>         QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool)
>>         [(libQtGui.so.4) ???:-1]
>>         0x7f54d019ca94 : ??? [(???) ???:-1]
>>         0x7f54d019b877 : QApplication::x11ProcessEvent(_XEvent*)
>>         [(libQtGui.so.4) ???:-1]
>>         0x7f54d01c4805 : ??? [(???) ???:-1]
>>         0x7f54cfa7f375 :
>>         QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
>>         [(libQtCore.so.4) ???:-1]
>>         0x7f54cfa7f748 :
>>         QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
>>         [(libQtCore.so.4) ???:-1]
>>         0x7f54cfa8414b : QCoreApplication::exec() [(libQtCore.so.4)
>>         ???:-1]
>>         0x407785 : main [(paraview) ???:-1]
>>         0x7f54ce06cec5 : __libc_start_main [(libc.so.6) ???:-1]
>>         0x4074da : QMainWindow::event(QEvent*) [(paraview) ???:-1]
>>         =========================================================
>>
>>         Thanks,
>>
>>         Sergi Mateo
>>         sergi.mateo.bellido at gmail.com
>>         <mailto:sergi.mateo.bellido at gmail.com>
>>
>>         _______________________________________________
>>         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
>>
>>
>>
>>
>>     -- 
>>     Cory Quammen
>>     R&D Engineer
>>     Kitware, Inc.
>
>
>
>
> -- 
> Cory Quammen
> R&D Engineer
> Kitware, Inc.

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

From deq11009 at fe.up.pt  Wed Jul  1 13:44:32 2015
From: deq11009 at fe.up.pt (deq11009)
Date: Wed, 01 Jul 2015 18:44:32 +0100
Subject: [Paraview] Wrong fetched data
Message-ID: <5000545d13da0baa4fa1c3d1e3c44423@fe.up.pt>

Hi,

I am currently using Paraview 4.2, 64, in Windows. (but tried 4.3 and 
same problem happened)

My case is Ensight transient. Cylinder with 3.6 million cells, 
two-phase flow.

I created a python code, which I run from the shell in the GUI.


The main parts of the code are:


enscase = EnSightReader(CaseFileName = direcp + 'ensfinal.case')
...
axis = Line()
...
rAxis = ResampleWithDataset(Input = enscase , Source = axis)
...
rAxis.SMProxy.UpdatePipeline(7) # enscase.SMProxy yields same problem
rAxis.UpdatePipelineInformation()
dAxis = servermanager.Fetch(rAxis)



Now, for example:
print dAxis.GetPointData().GetArray(7).GetValue(150)
which gives me the value 150 of the phase array.

This data is wrong. On the other hand, if I go to the GUI Pipeline and 
create a Spreadsheet, the values are the real ones (confirmed in 
Fluent).

So, the fetched data in the python shell is, for some reason, wrong.
What is my mistake?


Thanks
Filipe Direito


From cory.quammen at kitware.com  Wed Jul  1 14:53:49 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 1 Jul 2015 14:53:49 -0400
Subject: [Paraview] Changing the "solid color" to white for screenshots
 and exporting
In-Reply-To: <B7F2E4B7-0326-4D06-835E-4A3ED3C353ED@uvm.edu>
References: <5E9FE600-EDB4-49C5-B800-38816B8CA2CF@uvm.edu>
 <CAB5Fpx6KFvD6aUZX7MZTWwdDt1hy9+m9=4k=SfDm3uzVw8tBjQ@mail.gmail.com>
 <B7F2E4B7-0326-4D06-835E-4A3ED3C353ED@uvm.edu>
Message-ID: <CAB5Fpx4x=pbnjWAOEkJNPW0cO+USLwqwUobXS8Csn8BLeSqNKg@mail.gmail.com>

Hi Ryan,

When you zoom in on your grid in the black and white image, do the thick
lines change to two thinner lines? What I think is going on is that your
grid lines are so close together that some of them have a zero-pixel gap
between them, making them appear thicker.

Thanks,
Cory

On Wed, Jul 1, 2015 at 2:43 PM, Ryan Crocker <rcrocker at uvm.edu> wrote:

> Hi Cory,
>
> So this is what my grid looks like rendered in wireframe, notice the weird
> line thicknesses.
>
>
>
> and here it is rendered in surface with edges, where it look a normal grid.
>
>
>  Jun 29, 2015, at 9:20 PM, Cory Quammen <cory.quammen at kitware.com> wrote:
>
> Ryan,
>
> I thought this would be straight forward but it does not seem to be.  I
>> want to basically just get a picture of my grid with no background and a
>> few contours which are lines.  To do this i?m trying to set the the color
>> of the default ?Solid Color? to white.  No matter what i do it?s always
>> grey or off white in the view port and when i print it.
>
>
> When you set your object to white, it is still being rendered with
> lighting, hence the gray surface.
>
>
>> I?ve come close by using wireframe but that makes my grid look weird
>> (some lines are wider than others for some reason).  Is there a way to do
>> this with surface with edges?  That representation of my grid actually
>> looks like a grid.
>>
>
> In Wireframe representation, you all the lines should be the same width.
> If that's not the case, it is a bug. Can you post a picture showing the
> different line widths?
>
> Thanks,
> Cory
>
>
>>
>> _______________________________________________
>> 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
>>
>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150701/f8532775/attachment.html>

From cory.quammen at kitware.com  Wed Jul  1 15:27:41 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 1 Jul 2015 15:27:41 -0400
Subject: [Paraview] Changing the "solid color" to white for screenshots
 and exporting
In-Reply-To: <B534264A-BA03-4381-8213-1B0FE89CDA50@uvm.edu>
References: <5E9FE600-EDB4-49C5-B800-38816B8CA2CF@uvm.edu>
 <CAB5Fpx6KFvD6aUZX7MZTWwdDt1hy9+m9=4k=SfDm3uzVw8tBjQ@mail.gmail.com>
 <B7F2E4B7-0326-4D06-835E-4A3ED3C353ED@uvm.edu>
 <CAB5Fpx5GrEcty8B9GXwcX+XWYUDq=5Ga3TsRcV9FxBijCbY=uQ@mail.gmail.com>
 <B534264A-BA03-4381-8213-1B0FE89CDA50@uvm.edu>
Message-ID: <CAB5Fpx5wako3SvewbUs_pOJCwxfQKUfi355r+oor1ARbmyDNxg@mail.gmail.com>

Ryan,

I thought of another thing to try with your original data: under Backface
Styling, change the Backface Representation to "Cull Backface". This should
remove the edges from the backside of your data set.

If that doesn't work, can you share a data set?

To turn off lighting and set the color to white, I did what you did, but set

r.Ambient = 1.0
r.AmbientColor = [1, 1, 1]

That made the surface white without lighting.

Cory


On Wed, Jul 1, 2015 at 3:10 PM, Ryan Crocker <rcrocker at uvm.edu> wrote:

> When i zoom in they look the same, or it switches to other lines.  I
> thought it might have something to do with the fact that my 2D simulation
> actually dose have a thickness in the z-direction.  So i cut  a slice and
> now the issue with the lines is gone but it look alike this with the left
> to right cross in each cell (below script).  Is there a way to turn off the
> lighting so that i just get a flat, white surface.  I wrote a python script
> for it but it does not seem  to work.  I just get a black solid color.
>
> *RenderView1 = GetRenderView()
> **RenderView1.LightSwitch = 0
> **RenderView1.UseLight = 0
> **r = GetDisplayProperties()*
>
> *r.Ambient = 0.0*
>
>
>
> On Jul 1, 2015, at 11:52 AM, Cory Quammen <cory.quammen at kitware.com>
> wrote:
>
> Hi Ryan,
>
> When you zoom in on your grid in the black and white image, do the thick
> lines change to two thinner lines? What I think is going on is that your
> grid lines are so close together that some of them have a zero-pixel gap
> between them, making them appear thicker.
>
> Thanks,
> Cory
>
> On Wed, Jul 1, 2015 at 2:43 PM, Ryan Crocker <rcrocker at uvm.edu> wrote:
>
>> Hi Cory,
>>
>> So this is what my grid looks like rendered in wireframe, notice the
>> weird line thicknesses.
>> <grid_plot.jpg>
>>
>>
>> and here it is rendered in surface with edges, where it look a normal
>> grid.
>>
>>
>> <surfgrid_plot.jpg>
>>
>> On Jun 29, 2015, at 9:20 PM, Cory Quammen <cory.quammen at kitware.com>
>> wrote:
>>
>> Ryan,
>>
>> I thought this would be straight forward but it does not seem to be.  I
>>> want to basically just get a picture of my grid with no background and a
>>> few contours which are lines.  To do this i?m trying to set the the color
>>> of the default ?Solid Color? to white.  No matter what i do it?s always
>>> grey or off white in the view port and when i print it.
>>
>>
>> When you set your object to white, it is still being rendered with
>> lighting, hence the gray surface.
>>
>>
>>> I?ve come close by using wireframe but that makes my grid look weird
>>> (some lines are wider than others for some reason).  Is there a way to do
>>> this with surface with edges?  That representation of my grid actually
>>> looks like a grid.
>>>
>>
>> In Wireframe representation, you all the lines should be the same width.
>> If that's not the case, it is a bug. Can you post a picture showing the
>> different line widths?
>>
>> Thanks,
>> Cory
>>
>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>>
>>
>>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150701/70c61234/attachment.html>

From houssen at ipgp.fr  Wed Jul  1 16:49:37 2015
From: houssen at ipgp.fr (houssen)
Date: Wed, 01 Jul 2015 22:49:37 +0200
Subject: [Paraview]
 =?utf-8?q?Fwd=3A_How_to_plug_into_paraview_his_own_wri?=
 =?utf-8?q?ter_=3F?=
In-Reply-To: <CAB5Fpx6hLd4Of0iopNU-zEpVV9X=w8-2tPjGChm=sp1OPaM9fA@mail.gmail.com>
References: <86347d91c723cd90b081325c08b678ec@imap.ipgp.fr>
 <CAB5Fpx6hLd4Of0iopNU-zEpVV9X=w8-2tPjGChm=sp1OPaM9fA@mail.gmail.com>
Message-ID: <8fc449b95eac010b5d9af85b836c351e@imap.ipgp.fr>

Hi Cory,

I had to spread my time over several topics these days... So I had not 
much time to get back to the paraview writer.

I believe I have done pretty much everything for the writer to work but 
at save time, I still get this error :
~> ERROR: In 
/home/houssen/Programs/ParaView/ParaView-v4.3.1-source/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, 
line 307
vtkSIWriterProxy (0x5cc38e0): Failed to create myWriter. Aborting for 
debugging purposes.
The writer instance is not created for some reason.

At this point, I run paraview, I load the plugin with "tools / manage 
plugins" (load seems OK), I open some data, I save with "my writer" (I 
see my writer in the save GUI + I am asked for a file-to-save name), I 
click OK and then it crahses. I believe the xml file is wrong and / or 
something is missing... But I didn't yet figured it out. It seems I have 
no pvserver (see in the mail) : can this trigger the crash ? Do I need a 
pvserver for the writer to work ?

I answered your question in the mail.

Franck

Le 2015-06-30 6:08, Cory Quammen a ?crit?:
> Hi Franck,
>
> It looks like you've been making progress, so I'll answer your
> questions from your second email.
>
> ?
>
>> Question 1 : how to write myWriter.xml ?
>>
>> 1.1. seems I must set <InputProperty command="SetInputConnection"
>> name="Input"> in myWriter.xml. Does this means I will also have to
>> implement myWriter::SetInputConnection ?
>
> No. Your writer will inherit from subclass of vtkAlgorithm, the class
> that defines "SetInputConnection", and you should not need to 
> override
> it. XdmfWriter inherits from vtkDataObjectAlgorithm, which itself
> inherits vtkAlgorithm.
> ?
>
>> 1.2. seems I must set <StringVectorProperty name="FileName"
>> command="SetFileName"> in myWriter.xml. Does this means I will also
>> have to implement myWriter::SetFileName ?
>
> Yes, like vtkXdmfWriter.
>
>  2.2 in myWriter.hpp, I need to derive from a vtkObject this way
> (like XdmfWriter.cpp does)
>
>> ew (); // Needed to be plugged into paraview
>> ? ? vtkTypeMacro ( myWriter, vtkDataObjectAlgorithm ); // Needed
>> to be plugged into paraview
>> + suppress copy constructor and operator=
>>
>> Am I correct ?
>>
>> Yes.
>>
>> Question 3 : in myWriter.cpp, on
> I am supposed to be called back (to get focus back) when I click the
> "save data" button ? Here, how can I get data to be saved (data that 
> I
> can see in paraview viewer befo
>
>> n ParaView, when you choose, File -> Save Data, the data from the
>> selected Pipeline Browser object will be saved. This will have some
>> kind of data type, e.g., vtkImageData, vtkPolyData, etc. What kind
>> of data type would you like your writer to support?

Structured and likely also unstructured grids

>>
>> The data should
> in the member function myWriter::RequestData(). This is where you
> should write your data.?

OK (I suppose I'll get vtkStructuredGrid / vtkUnstructuredGrid as 
vtkObject in myWriter::RequestData according to 
http://www.vtk.org/Wiki/VTK/Tutorials/New_Pipeline#Typical_Pipeline_Execution)

>
>  Finally, myWriter.xml seems OK. myWriter.*pp compile OK. Paraview
> finds myWriter.xml at run time (exporting PV_PLUGIN_PATH) and loads
> libmywriter.so without problem. I see the writer in the "save data"
> GUI (drop down list with different save formats). I save with
> myWriter, I get a (basic) GUI with file name only (no extra 
> parameter)
> : I crash when I click "OK, save" with this error message :
>  ERROR: In /.../ParaView-v4.3.1-sourc
>
>> ailed to create myWriter. Aborting for debugging purposes.
>>
>> vtkSIWriterProxy does this at line 303 :
>> vtkObjectBase* obj = this->Interpreter->NewInstance(className);
>> but obj is NULL.
>>
>> I get obj is NULL because I missed something in myWriter
>> implementation : what did I miss ?
>>
>> Are you running pvserver separately and connecting to it with the
>> client? If so, make sure PV_PLUGIN_PATH is defined in the
>> environment in which pvserver is run. Have you tried to load your
>> plugin through the Tools -> Manage Plugins... dialog?
>>

No I just run a client. I don't need the server : is it necessary for 
the writer to work ?

~> paraview &
~> ps -aux | grep pvserver
houssen   5315  0.0  0.0  14544   948 pts/0    S+   22:38   0:00 grep 
pvserver
~> ps -aux | grep paraview
houssen   5313 16.0  1.1 1175692 179424 pts/0  S    22:38   0:01 
/home/houssen/Programs/ParaView/ParaView-v4.3.1-source/local/lib/paraview-4.3/paraview
houssen   5317  0.0  0.0  14544   944 pts/0    S+   22:38   0:00 grep 
paraview


>> I hope that helps get you further in writing your data files.
>>
>> Thanks,
>> Cory
>> ?
>> Can somebody help
> t me some clue ?
>
>  FH
>
>  -------- Message original --------
>  Objet: How to plug into paraview his own writer ?
>  Date: 2015-06-12 15:54
>  De: houssen <houssen at imap.ipgp.fr [6]>
>  ?: <paraview at paraview.org [7]>
>
>  I followed 2 tutorials (
>
> Links:
> ------
> [1] http://www.kitware.com
> [2] http://www.kitware.com/opensource/opensource.html
> [3] http://paraview.org/Wiki/ParaView
> [4] http://markmail.org/search/?q=ParaView
> [5] http://public.kitware.com/mailman/listinfo/paraview
> [6] mailto:houssen at imap.ipgp.fr
> [7] mailto:paraview at paraview.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: myWriter.tar.gz
Type: application/x-gzip
Size: 1591 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150701/8116c72b/attachment.bin>

From normvcr at telus.net  Wed Jul  1 17:29:50 2015
From: normvcr at telus.net (Norman Goldstein)
Date: Wed, 01 Jul 2015 14:29:50 -0700
Subject: [Paraview] ParaView builds part of VTK
Message-ID: <55945BCE.7060407@telus.net>

I am running on fedora 20, x86-64, and have successfully built ParaView 
4.3 and the VTK 6.2 subset that comes along for the ride. 
(congratulations to the devel team that have prepared such a painless 
build for this complex system!).  I am wondering what is the most 
painless / recommended way for me to have access to all of VTK 6.2:

1.  Somehow tell the ParaView build system to build all of VTK (not just 
the part it needs),
2.  Run a separate build on the VTK folder that ships with ParaView,
3.  Do an independent install of VTK 6.2 (this would mean having a 
potential problem with two installs of VTK), or
4.  Tell ParaView to use an externally built VTK 6.2

For the #4, I know there is the cmake flag

-DUSE_EXTERNAL_VTK:BOOL=ON

but I am not clear what else needs to be done to make #4 work

Thanks

From cunrein at micron.com  Wed Jul  1 17:37:26 2015
From: cunrein at micron.com (cunrein)
Date: Wed, 1 Jul 2015 15:37:26 -0600
Subject: [Paraview] Adding functionality to the apply event
Message-ID: <55945D96.5040503@micron.com>

Hello List,

In a [much much] older version of ParaView, I have a working 
filter/objectPanel pair that inherits from pqAutoGeneratedObjectPanel 
and overloads the accept method.  I want to update this to work with 
PV4.3.  ObjectPanels have been replaced with the PropertyPanel.  Do I 
want to inherit from pqPropertyPanel and overload the apply method?  If 
so, is there a CMake macro to add this?  It doesn't look like 
ADD_PARAVIEW_OBJECT_PANEL will work with the new panel philosophy.  If 
creating a new panel is not the right thing to do anymore, how do I add 
functionality to the apply event?

Thanks, Chris

From deytonjh at ornl.gov  Wed Jul  1 18:12:10 2015
From: deytonjh at ornl.gov (Jordan Deyton)
Date: Wed, 01 Jul 2015 18:12:10 -0400
Subject: [Paraview] Zooming through the ParaViewWeb API
Message-ID: <559465BA.2030506@ornl.gov>

ParaViewWeb gurus,

Is there a correct way to send a zoom request through the ParaViewWeb API?

I'm especially looking at the PVW MouseHandler (documentation here -- 
http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/api/protocols.ParaViewWebMouseHandler)

I have had some success by sending a right-click with a small y value 
(looks like it needs to be between 0 and 1), the action set to "none", 
and buttonRight set to "true". However, when I afterward rotate the view 
(using the same RPC call with different methods), the rendered object 
just vanishes, although the axes and legend are still there.

Jordan

-- 
Jordan Deyton
Oak Ridge National Laboratory
Telephone: (865) 574-1091
Email: deytonjh at ornl.gov


From deytonjh at ornl.gov  Wed Jul  1 18:06:50 2015
From: deytonjh at ornl.gov (Jordan Deyton)
Date: Wed, 01 Jul 2015 18:06:50 -0400
Subject: [Paraview] Mismatched image size returned from ViewPort image
 render
In-Reply-To: <CAPiw4fDbCdE5paPW5xopwueV9qTsHFsKzui07OQ2=9nHmZ9utQ@mail.gmail.com>
References: <54F61A57.8050704@ornl.gov>
 <CAPiw4fDbCdE5paPW5xopwueV9qTsHFsKzui07OQ2=9nHmZ9utQ@mail.gmail.com>
Message-ID: <5594647A.1000305@ornl.gov>

Scott, et al,

It appears nothing has changed in the latest nightly build.

However, I have found that the remote X display I'm using is set to a 
resolution of 640x480. Given that info, it might make sense that 
ParaView is not rendering anything bigger than 636x420 if it's 
restricted to the X display's size. Is it possible to get around the 
size of the remote X display when rendering something offscreen with 
ParaView?

Jordan

Jordan Deyton
Oak Ridge National Laboratory
Telephone: (865) 574-1091
Email: deytonjh at ornl.gov

On 3/4/2015 12:15 PM, Scott Wittenburg wrote:
> Hi Jordan,
>
>    I wonder if that is the issue that is addressed in this topic:
>
> http://review.source.kitware.com/#/t/5425/
>
>    If so, I think this fix may be merged soon, as it has already been 
> approved.  If you built the ParaView release you're running yourself, 
> you could always try to check out the topic and see if it fixes the 
> issue you're seeing.
>
> Cheers,
> Scott
>
>
>
>
> On Tue, Mar 3, 2015 at 1:32 PM, Jordan Deyton <deytonjh at ornl.gov 
> <mailto:deytonjh at ornl.gov>> wrote:
>
>     ParaView gurus,
>
>     I am working on a project that uses the JSON RPC protocols
>     provided by ParaViewWeb. I've noticed that the image quality for
>     ViewPorts seems bad regardless of what is specified in the call to
>     viewport.image.render (docs here:
>     http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/api/protocols.ParaViewWebViewPortImageDelivery
>     <http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#%21/api/protocols.ParaViewWebViewPortImageDelivery>
>     ).
>
>     After decoding the returned image from the Base64 encoding, the
>     JPEG image comes out as 636x420, while the quality is listed as
>     100 and the original size is 1440x850.
>
>     The JSON object passed to viewport.image.render looks like
>
>     {"args":[{
>         "localtime":1425413914878,
>         "view":-1,
>         "size":[1440,850],
>         "quality":100}]
>     }
>
>     While the returned object from that RPC call looks like
>
>     {
>         "image": "very long encoded image text here",
>         "localTime": 0,
>         "stale": false,
>         "size": [1440,850],
>         "format": "jpeg;base64",
>         "global_id": "315",
>         "mtime": 3068929,
>         "workTime": 1
>     }
>
>     I've used two separate Base64 decoders, and both result in a JPEG
>     image that is 636x420, not the reported 1440x850.
>
>     Any idea what could be the problem here? Is this a bug in
>     ParaViewWeb? I'm running the latest stable ParaView release
>     (4.3.1) on RHEL.
>
>     Thanks,
>     Jordan
>
>     -- 
>     Jordan Deyton
>     Oak Ridge National Laboratory
>     Telephone: (865) 574-1091 <tel:%28865%29%20574-1091>
>     Email: deytonjh at ornl.gov <mailto:deytonjh at ornl.gov>
>
>     _______________________________________________
>     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
>
>

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

From scott.wittenburg at kitware.com  Wed Jul  1 18:22:08 2015
From: scott.wittenburg at kitware.com (Scott Wittenburg)
Date: Wed, 1 Jul 2015 16:22:08 -0600
Subject: [Paraview] Mismatched image size returned from ViewPort image
	render
In-Reply-To: <5594647A.1000305@ornl.gov>
References: <54F61A57.8050704@ornl.gov>
 <CAPiw4fDbCdE5paPW5xopwueV9qTsHFsKzui07OQ2=9nHmZ9utQ@mail.gmail.com>
 <5594647A.1000305@ornl.gov>
Message-ID: <CAPiw4fA-YDCPiULPDBpND57J9dBa+zVERhCSxjOXcQYMUGdC3g@mail.gmail.com>

The "viewport.image.render" rpc call includes the browser viewport size as
a parameter, and the server-side peer window should resize itself so that
you get the correct image in your browser.  However, if the remote display
is configured to have a maximum size of 640 x 480, then I do not believe
there is any way to request a larger image from the client side.  Perhaps
someone else knows otherwise though.

Cheers,
Scott



On Wed, Jul 1, 2015 at 4:06 PM, Jordan Deyton <deytonjh at ornl.gov> wrote:

>  Scott, et al,
>
> It appears nothing has changed in the latest nightly build.
>
> However, I have found that the remote X display I'm using is set to a
> resolution of 640x480. Given that info, it might make sense that ParaView
> is not rendering anything bigger than 636x420 if it's restricted to the X
> display's size. Is it possible to get around the size of the remote X
> display when rendering something offscreen with ParaView?
>
> Jordan
>
> Jordan Deyton
> Oak Ridge National Laboratory
> Telephone: (865) 574-1091
> Email: deytonjh at ornl.gov
>
> On 3/4/2015 12:15 PM, Scott Wittenburg wrote:
>
> Hi Jordan,
>
>     I wonder if that is the issue that is addressed in this topic:
>
>  http://review.source.kitware.com/#/t/5425/
>
>     If so, I think this fix may be merged soon, as it has already been
> approved.  If you built the ParaView release you're running yourself, you
> could always try to check out the topic and see if it fixes the issue
> you're seeing.
>
>  Cheers,
> Scott
>
>
>
>
> On Tue, Mar 3, 2015 at 1:32 PM, Jordan Deyton <deytonjh at ornl.gov> wrote:
>
>> ParaView gurus,
>>
>> I am working on a project that uses the JSON RPC protocols provided by
>> ParaViewWeb. I've noticed that the image quality for ViewPorts seems bad
>> regardless of what is specified in the call to viewport.image.render (docs
>> here:
>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/api/protocols.ParaViewWebViewPortImageDelivery
>> ).
>>
>> After decoding the returned image from the Base64 encoding, the JPEG
>> image comes out as 636x420, while the quality is listed as 100 and the
>> original size is 1440x850.
>>
>> The JSON object passed to viewport.image.render looks like
>>
>> {"args":[{
>>     "localtime":1425413914878,
>>     "view":-1,
>>     "size":[1440,850],
>>     "quality":100}]
>> }
>>
>> While the returned object from that RPC call looks like
>>
>> {
>>     "image": "very long encoded image text here",
>>     "localTime": 0,
>>     "stale": false,
>>     "size": [1440,850],
>>     "format": "jpeg;base64",
>>     "global_id": "315",
>>     "mtime": 3068929,
>>     "workTime": 1
>> }
>>
>> I've used two separate Base64 decoders, and both result in a JPEG image
>> that is 636x420, not the reported 1440x850.
>>
>> Any idea what could be the problem here? Is this a bug in ParaViewWeb?
>> I'm running the latest stable ParaView release (4.3.1) on RHEL.
>>
>> Thanks,
>> Jordan
>>
>> --
>> Jordan Deyton
>> Oak Ridge National Laboratory
>> Telephone: (865) 574-1091
>> Email: deytonjh at ornl.gov
>>
>> _______________________________________________
>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150701/4d0f7e6e/attachment.html>

From scott.wittenburg at kitware.com  Wed Jul  1 18:28:08 2015
From: scott.wittenburg at kitware.com (Scott Wittenburg)
Date: Wed, 1 Jul 2015 16:28:08 -0600
Subject: [Paraview] Zooming through the ParaViewWeb API
In-Reply-To: <559465BA.2030506@ornl.gov>
References: <559465BA.2030506@ornl.gov>
Message-ID: <CAPiw4fAd2pc1k+tvd1qz-k0Ygesuyaj1FfxqgOGw_wur8OcBKw@mail.gmail.com>

Here is a sample from my websocket frames just now:

[48,4996973606207488,{},"viewport.mouse.interaction",[{"view":353,"action":"move","altKey":false,"ctrlKey":false,"shiftKey":false,"metaKey":false,"buttonLeft":false,"buttonMiddle":false,"buttonRight":true,"x":0.7654596100278551,"y":0.38173817381738173}]]

It seems the "action" should be set to "move" rather than "none", as in the
documentation you linked, "none" does not seem to be an option.  Also, as
that documentation states, x and y should be normalized to [0, 1], as you
correctly guessed.  And finally, you may need to provide all the parameters
with values like I show above, not just the ones you are interested in.

But at any rate, this should not then affect the center of rotation, but it
sounds like in your case maybe it is?  Can you see if moving just a *tiny*
bit keeps at least some of the object in view?

Cheers,
Scott

On Wed, Jul 1, 2015 at 4:12 PM, Jordan Deyton <deytonjh at ornl.gov> wrote:

> ParaViewWeb gurus,
>
> Is there a correct way to send a zoom request through the ParaViewWeb API?
>
> I'm especially looking at the PVW MouseHandler (documentation here --
> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/api/protocols.ParaViewWebMouseHandler
> )
>
> I have had some success by sending a right-click with a small y value
> (looks like it needs to be between 0 and 1), the action set to "none", and
> buttonRight set to "true". However, when I afterward rotate the view (using
> the same RPC call with different methods), the rendered object just
> vanishes, although the axes and legend are still there.
>
> Jordan
>
> --
> Jordan Deyton
> Oak Ridge National Laboratory
> Telephone: (865) 574-1091
> Email: deytonjh at ornl.gov
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150701/35864d9b/attachment.html>

From sebastien.jourdain at kitware.com  Wed Jul  1 19:06:05 2015
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Wed, 1 Jul 2015 17:06:05 -0600
Subject: [Paraview] Mismatched image size returned from ViewPort image
	render
In-Reply-To: <CAPiw4fA-YDCPiULPDBpND57J9dBa+zVERhCSxjOXcQYMUGdC3g@mail.gmail.com>
References: <54F61A57.8050704@ornl.gov>
 <CAPiw4fDbCdE5paPW5xopwueV9qTsHFsKzui07OQ2=9nHmZ9utQ@mail.gmail.com>
 <5594647A.1000305@ornl.gov>
 <CAPiw4fA-YDCPiULPDBpND57J9dBa+zVERhCSxjOXcQYMUGdC3g@mail.gmail.com>
Message-ID: <CABObKxf1+5J_d4k=Y7s+oQynKJP2n2ExA5L_w3oAxuv2NFa4vg@mail.gmail.com>

Can you change the remote X setting to have a larger resolution?

Seb

On Wed, Jul 1, 2015 at 4:22 PM, Scott Wittenburg <
scott.wittenburg at kitware.com> wrote:

> The "viewport.image.render" rpc call includes the browser viewport size as
> a parameter, and the server-side peer window should resize itself so that
> you get the correct image in your browser.  However, if the remote display
> is configured to have a maximum size of 640 x 480, then I do not believe
> there is any way to request a larger image from the client side.  Perhaps
> someone else knows otherwise though.
>
> Cheers,
> Scott
>
>
>
> On Wed, Jul 1, 2015 at 4:06 PM, Jordan Deyton <deytonjh at ornl.gov> wrote:
>
>>  Scott, et al,
>>
>> It appears nothing has changed in the latest nightly build.
>>
>> However, I have found that the remote X display I'm using is set to a
>> resolution of 640x480. Given that info, it might make sense that ParaView
>> is not rendering anything bigger than 636x420 if it's restricted to the X
>> display's size. Is it possible to get around the size of the remote X
>> display when rendering something offscreen with ParaView?
>>
>> Jordan
>>
>> Jordan Deyton
>> Oak Ridge National Laboratory
>> Telephone: (865) 574-1091
>> Email: deytonjh at ornl.gov
>>
>> On 3/4/2015 12:15 PM, Scott Wittenburg wrote:
>>
>> Hi Jordan,
>>
>>     I wonder if that is the issue that is addressed in this topic:
>>
>>  http://review.source.kitware.com/#/t/5425/
>>
>>     If so, I think this fix may be merged soon, as it has already been
>> approved.  If you built the ParaView release you're running yourself, you
>> could always try to check out the topic and see if it fixes the issue
>> you're seeing.
>>
>>  Cheers,
>> Scott
>>
>>
>>
>>
>> On Tue, Mar 3, 2015 at 1:32 PM, Jordan Deyton <deytonjh at ornl.gov> wrote:
>>
>>> ParaView gurus,
>>>
>>> I am working on a project that uses the JSON RPC protocols provided by
>>> ParaViewWeb. I've noticed that the image quality for ViewPorts seems bad
>>> regardless of what is specified in the call to viewport.image.render (docs
>>> here:
>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/api/protocols.ParaViewWebViewPortImageDelivery
>>> ).
>>>
>>> After decoding the returned image from the Base64 encoding, the JPEG
>>> image comes out as 636x420, while the quality is listed as 100 and the
>>> original size is 1440x850.
>>>
>>> The JSON object passed to viewport.image.render looks like
>>>
>>> {"args":[{
>>>     "localtime":1425413914878,
>>>     "view":-1,
>>>     "size":[1440,850],
>>>     "quality":100}]
>>> }
>>>
>>> While the returned object from that RPC call looks like
>>>
>>> {
>>>     "image": "very long encoded image text here",
>>>     "localTime": 0,
>>>     "stale": false,
>>>     "size": [1440,850],
>>>     "format": "jpeg;base64",
>>>     "global_id": "315",
>>>     "mtime": 3068929,
>>>     "workTime": 1
>>> }
>>>
>>> I've used two separate Base64 decoders, and both result in a JPEG image
>>> that is 636x420, not the reported 1440x850.
>>>
>>> Any idea what could be the problem here? Is this a bug in ParaViewWeb?
>>> I'm running the latest stable ParaView release (4.3.1) on RHEL.
>>>
>>> Thanks,
>>> Jordan
>>>
>>> --
>>> Jordan Deyton
>>> Oak Ridge National Laboratory
>>> Telephone: (865) 574-1091
>>> Email: deytonjh at ornl.gov
>>>
>>> _______________________________________________
>>> 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
>>
>>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150701/5f00c928/attachment.html>

From sebastien.jourdain at kitware.com  Wed Jul  1 19:09:03 2015
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Wed, 1 Jul 2015 17:09:03 -0600
Subject: [Paraview] Zooming through the ParaViewWeb API
In-Reply-To: <CAPiw4fAd2pc1k+tvd1qz-k0Ygesuyaj1FfxqgOGw_wur8OcBKw@mail.gmail.com>
References: <559465BA.2030506@ornl.gov>
 <CAPiw4fAd2pc1k+tvd1qz-k0Ygesuyaj1FfxqgOGw_wur8OcBKw@mail.gmail.com>
Message-ID: <CABObKxd4_4sbWYg+hE=Fmfw5cDp7=K7WF8Bb_7n5im=-1pMTdg@mail.gmail.com>

Scott is right, the x,y values are normalized, so depending on your screen
size if your image is 1000 pixel wide and you want to reflect a move of 10
pixel, you should send a x of 10/1000=0.01.

On Wed, Jul 1, 2015 at 4:28 PM, Scott Wittenburg <
scott.wittenburg at kitware.com> wrote:

> Here is a sample from my websocket frames just now:
>
>
> [48,4996973606207488,{},"viewport.mouse.interaction",[{"view":353,"action":"move","altKey":false,"ctrlKey":false,"shiftKey":false,"metaKey":false,"buttonLeft":false,"buttonMiddle":false,"buttonRight":true,"x":0.7654596100278551,"y":0.38173817381738173}]]
>
> It seems the "action" should be set to "move" rather than "none", as in
> the documentation you linked, "none" does not seem to be an option.  Also,
> as that documentation states, x and y should be normalized to [0, 1], as
> you correctly guessed.  And finally, you may need to provide all the
> parameters with values like I show above, not just the ones you are
> interested in.
>
> But at any rate, this should not then affect the center of rotation, but
> it sounds like in your case maybe it is?  Can you see if moving just a
> *tiny* bit keeps at least some of the object in view?
>
> Cheers,
> Scott
>
>
> On Wed, Jul 1, 2015 at 4:12 PM, Jordan Deyton <deytonjh at ornl.gov> wrote:
>
>> ParaViewWeb gurus,
>>
>> Is there a correct way to send a zoom request through the ParaViewWeb API?
>>
>> I'm especially looking at the PVW MouseHandler (documentation here --
>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/api/protocols.ParaViewWebMouseHandler
>> )
>>
>> I have had some success by sending a right-click with a small y value
>> (looks like it needs to be between 0 and 1), the action set to "none", and
>> buttonRight set to "true". However, when I afterward rotate the view (using
>> the same RPC call with different methods), the rendered object just
>> vanishes, although the axes and legend are still there.
>>
>> Jordan
>>
>> --
>> Jordan Deyton
>> Oak Ridge National Laboratory
>> Telephone: (865) 574-1091
>> Email: deytonjh at ornl.gov
>>
>> _______________________________________________
>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150701/5a22dd60/attachment.html>

From hermano_lustosa at hotmail.com  Thu Jul  2 00:25:06 2015
From: hermano_lustosa at hotmail.com (Hermano ...)
Date: Thu, 2 Jul 2015 07:25:06 +0300
Subject: [Paraview] Supress windows on pv_web_visualizer.py
Message-ID: <COL127-W212DB71416372ABEE510B81970@phx.gbl>

Hello everyone

I am using Paraview Web with the Jetty launcher and the Web Visualizer. Anytime a new page is loaded for a new visualization, also a new window appears on my desktop (I am using ubuntu with KDE installed, and running the web server locally for test purposes). I'd like to know if there is a way to supress theses windows with the visualizations. They are a little bit annoying.
To me it's enough to show the visualization on the browser only.

I ran pv_web_visualizer.py with --help , but there wasn't any option related to my "issue". So I wonder if there's a way of doing it.

Thanks in advance.

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

From normvcr at telus.net  Thu Jul  2 01:57:34 2015
From: normvcr at telus.net (Norman Goldstein)
Date: Wed, 01 Jul 2015 22:57:34 -0700
Subject: [Paraview] Creating a vtp file
Message-ID: <5594D2CE.9080805@telus.net>

 From net examples and on-line docs, I have gleaned some of the info to 
create a full 1-piece vtp file:

Call
vtkXMLPolyDataWriter::SetInputData( vtkDataObject 
<http://www.vtk.org/doc/nightly/html/classvtkDataObject.html> *)

where you pass in a vtkPolyData, which you first set up with the methods:

SetVerts
SetLines
SetPolys
SetStrips

and the parent method

SetPoints

What I have not figured out is how to set the vtp fields
PointData and CellData

Any pointers much appreciated ...




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

From cory.quammen at kitware.com  Thu Jul  2 07:40:12 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 2 Jul 2015 07:40:12 -0400
Subject: [Paraview] Creating a vtp file
In-Reply-To: <5594D2CE.9080805@telus.net>
References: <5594D2CE.9080805@telus.net>
Message-ID: <CAB5Fpx4fs2en+LDUK0WcYj9kaA=iW0yv8MhaLaZAK-1=SUZqLA@mail.gmail.com>

Hi Norman,

To set point data, you can first get the point data object with

vtkPointData* pointData = polydata->GetPointData();

Then you can add arrays to it:

vtkFloatArray* myArrray = vtkFloatArray::New();
myArray->SetName("myArray");
myArray->SetNumberOfComponents(1);
myArray->SetNumberOfTuples(polydata->GetNumberOfPoints());
// Set array elements here...

pointData->AddArray(myArray);

The same holds true for cell data, just replace PointData with CellData,
and set the number of tuples to the number of cells instead of the number
of points.

Hope this helps,

Cory


On Thu, Jul 2, 2015 at 1:57 AM, Norman Goldstein <normvcr at telus.net> wrote:

>  From net examples and on-line docs, I have gleaned some of the info to
> create a full 1-piece vtp file:
>
> Call
> vtkXMLPolyDataWriter::SetInputData( vtkDataObject
> <http://www.vtk.org/doc/nightly/html/classvtkDataObject.html> *)
>
> where you pass in a vtkPolyData, which you first set up with the methods:
>
> SetVerts
> SetLines
> SetPolys
> SetStrips
>
> and the parent method
>
> SetPoints
>
> What I have not figured out is how to set the vtp fields
> PointData and CellData
>
> Any pointers much appreciated ...
>
>
>
>
>
> _______________________________________________
> 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
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150702/a930ddb2/attachment.html>

From mctolille at netcourrier.com  Thu Jul  2 09:39:52 2015
From: mctolille at netcourrier.com (mctolille at netcourrier.com)
Date: Thu,  2 Jul 2015 15:39:52 +0200 (CEST)
Subject: [Paraview] Probe location in a script
Message-ID: <ea-mime-55953f28-5f6b-59a2e5c4@www-2.netcourrier.com>


Hi everybody,

I am a new Paraview user. I am trying to extract points from a bunch of vtu files. It is pretty easily done with "probe location". But since I have a lot of files, I would like to automatize the process (with a macro or a python script). 

Could someone maybe show me how it's done?

My best guess is that I should have the following in a python script:
Probelocation.ProbeType.Center = [10.0,20.0,30.0] 
assuming I want to probe at x=10, y=20, z=30. But then, I don't really know how to retrieve the variables values at that location.

Thanks a lot,
Mc Fly

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

From cory.quammen at kitware.com  Thu Jul  2 09:55:04 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 2 Jul 2015 09:55:04 -0400
Subject: [Paraview] Probe location in a script
In-Reply-To: <ea-mime-55953f28-5f6b-59a2e5c4@www-2.netcourrier.com>
References: <ea-mime-55953f28-5f6b-59a2e5c4@www-2.netcourrier.com>
Message-ID: <CAB5Fpx7K7Qo65vJ6a2Lgb=E_RjdH+=kPVy6VnKLedVVMHr-vkw@mail.gmail.com>

Hi McFly,

The Python Tracing facility in ParaView is perfect for this kind of task.
It records a trace of your actions in the ParaView GUI to a Python script
that you can modify a bit to process a bunch of files. To turn on tracing,
choose the Tools -> Start Trace menu item.

More info on tracing is available in the ParaView User Guide [1] under
section 1.6.2.

Best regards,
Cory

[1] http://www.paraview.org/paraview-guide/

On Thu, Jul 2, 2015 at 9:39 AM, <mctolille at netcourrier.com> wrote:

>
> Hi everybody,
>
> I am a new Paraview user. I am trying to extract points from a bunch of
> vtu files. It is pretty easily done with "probe location". But since I have
> a lot of files, I would like to automatize the process (with a macro or a
> python script).
>
> Could someone maybe show me how it's done?
>
> My best guess is that I should have the following in a python script:
> Probelocation.ProbeType.Center = [10.0,20.0,30.0]
> assuming I want to probe at x=10, y=20, z=30. But then, I don't really
> know how to retrieve the variables values at that location.
>
> Thanks a lot,
> Mc Fly
>
> _______________________________________________
> 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
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150702/cb5a211a/attachment.html>

From antech777 at gmail.com  Thu Jul  2 10:19:26 2015
From: antech777 at gmail.com (Andrew)
Date: Thu, 2 Jul 2015 17:19:26 +0300
Subject: [Paraview] IntegrateVariables filter (add variables)
In-Reply-To: <CANMVBVyi0Vs1rSKzFK=tjNFdumb9rpV1+_PGwGy+tJd_YdQg-A@mail.gmail.com>
References: <CANMVBVyi0Vs1rSKzFK=tjNFdumb9rpV1+_PGwGy+tJd_YdQg-A@mail.gmail.com>
Message-ID: <CANMVBVwRdXLjuia2Z2M3UHzgpjnnn+bcGvp2HL=8eggGc2z5ag@mail.gmail.com>

Hello.
I use ParaView to visualize Code_Saturne (CFD) calculation results (ParaVis
module in Salome). But I cannot integrate any variable except coordinates
and area or volume. I tried the "Cell data to point data" before
IntegrateVariables, it changed nothing. I asked this question on Salome and
CFD-Online forums, but noone replied me. Please, help.
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150702/e46e1d12/attachment.html>

From mctolille at netcourrier.com  Thu Jul  2 10:47:28 2015
From: mctolille at netcourrier.com (mctolille at netcourrier.com)
Date: Thu,  2 Jul 2015 16:47:28 +0200 (CEST)
Subject: [Paraview] Probe location in a script
In-Reply-To: <CAB5Fpx7K7Qo65vJ6a2Lgb=E_RjdH+=kPVy6VnKLedVVMHr-vkw@mail
 .gmail.com>
Message-ID: <ea-mime-55954f00-d32-abacf55@www-1.netcourrier.com>

Thanks for the tip. I actually already used tracing in order to find the command:
??? Probelocation.ProbeType.Center = [10.0,20.0,30.0] 

But the problem is that I don't know how to access to the data (rho, vx, vy...) at that location in the python script

And since tracing does not capture "Save data", I don't even know how to write the data in a file

Cheers,
Mc Fly




Date : 02/07/2015 15:55:04 CEST

Hi McFly,


The Python Tracing facility in ParaView is perfect for this kind of task. It records a trace of your actions in the ParaView GUI to a Python script that you can modify a bit to process a bunch of files. To turn on tracing, choose the Tools -> Start Trace menu item.



More info on tracing is available in the ParaView User Guide [1] under section 1.6.2.



Best regards,

Cory



[1]?http://www.paraview.org/paraview-guide/


On Thu, Jul 2, 2015 at 9:39 AM, <mctolille at netcourrier.com> wrote:


Hi everybody,

I am a new Paraview user. I am trying to extract points from a bunch of vtu files. It is pretty easily done with "probe location". But since I have a lot of files, I would like to automatize the process (with a macro or a python script). 

Could someone maybe show me how it's done?

My best guess is that I should have the following in a python script:
Probelocation.ProbeType.Center = [10.0,20.0,30.0] 
assuming I want to probe at x=10, y=20, z=30. But then, I don't really know how to retrieve the variables values at that location.

Thanks a lot,
Mc Fly


_______________________________________________
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






-- 

Cory Quammen
R&D Engineer
Kitware, Inc.


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

From andy.bauer at kitware.com  Thu Jul  2 10:50:55 2015
From: andy.bauer at kitware.com (Andy Bauer)
Date: Thu, 2 Jul 2015 10:50:55 -0400
Subject: [Paraview] IntegrateVariables filter (add variables)
In-Reply-To: <CANMVBVwRdXLjuia2Z2M3UHzgpjnnn+bcGvp2HL=8eggGc2z5ag@mail.gmail.com>
References: <CANMVBVyi0Vs1rSKzFK=tjNFdumb9rpV1+_PGwGy+tJd_YdQg-A@mail.gmail.com>
 <CANMVBVwRdXLjuia2Z2M3UHzgpjnnn+bcGvp2HL=8eggGc2z5ag@mail.gmail.com>
Message-ID: <CAMaOp+GdRcL2+bUpyEj22KGVbdjiCBuB-hN=sNkUo5Axfrra+w@mail.gmail.com>

Have you tried doing the Integrate Variables filter with something like the
Wavelet source? If that works for you as expected, can you share a
representative data set that you're having problems with?

Regards,
Andy

On Thu, Jul 2, 2015 at 10:19 AM, Andrew <antech777 at gmail.com> wrote:

> Hello.
> I use ParaView to visualize Code_Saturne (CFD) calculation results
> (ParaVis module in Salome). But I cannot integrate any variable except
> coordinates and area or volume. I tried the "Cell data to point data"
> before IntegrateVariables, it changed nothing. I asked this question on
> Salome and CFD-Online forums, but noone replied me. Please, help.
> Thanks.
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150702/8245c2c4/attachment.html>

From andy.bauer at kitware.com  Thu Jul  2 10:58:59 2015
From: andy.bauer at kitware.com (Andy Bauer)
Date: Thu, 2 Jul 2015 10:58:59 -0400
Subject: [Paraview] IntegrateVariables filter (add variables)
In-Reply-To: <CANMVBVx06m_or+HGo9Xj-O1SsfqJy-eh9RaEPHRLe1+k4+siOg@mail.gmail.com>
References: <CANMVBVyi0Vs1rSKzFK=tjNFdumb9rpV1+_PGwGy+tJd_YdQg-A@mail.gmail.com>
 <CANMVBVwRdXLjuia2Z2M3UHzgpjnnn+bcGvp2HL=8eggGc2z5ag@mail.gmail.com>
 <CAMaOp+GdRcL2+bUpyEj22KGVbdjiCBuB-hN=sNkUo5Axfrra+w@mail.gmail.com>
 <CANMVBVx06m_or+HGo9Xj-O1SsfqJy-eh9RaEPHRLe1+k4+siOg@mail.gmail.com>
Message-ID: <CAMaOp+HFHw2OKunV=bCyhuyj5tf1Ava7wi1FxKe28xzpFJC_Vg@mail.gmail.com>

Hi,

Please keep the discussions on the mailing list so that everyone can follow.

Thanks,
Andy

On Thu, Jul 2, 2015 at 10:57 AM, Andrew <antech777 at gmail.com> wrote:

> Hello.
> Thanks for advice! I didn't try Wavelet source, but I will as soon as
> possible and will report the result. Surely I can share an example of
> results:
> https://drive.google.com/open?id=0BzPt_Ya8Zu8nU2NRT2NWN1ZxV0U
> Files are in "postprocessing" directory (open the RESULTS.case file)
> and have an EnSight Gold format.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150702/63598218/attachment.html>

From dkxls23 at gmail.com  Thu Jul  2 11:07:42 2015
From: dkxls23 at gmail.com (Armin Wehrfritz)
Date: Thu, 02 Jul 2015 18:07:42 +0300
Subject: [Paraview] Probe location in a script
In-Reply-To: <ea-mime-55954f00-d32-abacf55@www-1.netcourrier.com>
References: <ea-mime-55954f00-d32-abacf55@www-1.netcourrier.com>
Message-ID: <559553BE.3060005@gmail.com>

Here is a little script that shows you how to read and write dataset in 
ParaView using a simple for loop.

Hope this helps.

-Armin




On 07/02/2015 05:47 PM, mctolille at netcourrier.com wrote:
> Thanks for the tip. I actually already used tracing in order to find the
> command:
>      Probelocation.ProbeType.Center = [10.0,20.0,30.0]
>
> But the problem is that I don't know how to access to the data (rho, vx,
> vy...) at that location in the python script
>
> And since tracing does not capture "Save data", I don't even know how to
> write the data in a file
>
> Cheers,
> Mc Fly
>
>
>
>
> Date : 02/07/2015 15:55:04 CEST
>
> Hi McFly,
>
> The Python Tracing facility in ParaView is perfect for this kind of
> task. It records a trace of your actions in the ParaView GUI to a Python
> script that you can modify a bit to process a bunch of files. To turn on
> tracing, choose the Tools -> Start Trace menu item.
>
> More info on tracing is available in the ParaView User Guide [1] under
> section 1.6.2.
>
> Best regards,
> Cory
>
> [1] http://www.paraview.org/paraview-guide/
>
> On Thu, Jul 2, 2015 at 9:39 AM, <mctolille at netcourrier.com
> <mailto:mctolille at netcourrier.com>> wrote:
>
>     __
>
>     Hi everybody,
>
>     I am a new Paraview user. I am trying to extract points from a bunch
>     of vtu files. It is pretty easily done with "probe location". But
>     since I have a lot of files, I would like to automatize the process
>     (with a macro or a python script).
>
>     Could someone maybe show me how it's done?
>
>     My best guess is that I should have the following in a python script:
>     Probelocation.ProbeType.Center = [10.0,20.0,30.0]
>     assuming I want to probe at x=10, y=20, z=30. But then, I don't
>     really know how to retrieve the variables values at that location.
>
>     Thanks a lot,
>     Mc Fly
>
>     _______________________________________________
>     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
>
>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: probe.py
Type: text/x-python
Size: 976 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150702/9b388fa2/attachment.py>

From scott.wittenburg at kitware.com  Thu Jul  2 11:15:49 2015
From: scott.wittenburg at kitware.com (Scott Wittenburg)
Date: Thu, 2 Jul 2015 09:15:49 -0600
Subject: [Paraview] Supress windows on pv_web_visualizer.py
In-Reply-To: <COL127-W212DB71416372ABEE510B81970@phx.gbl>
References: <COL127-W212DB71416372ABEE510B81970@phx.gbl>
Message-ID: <CAPiw4fCDuU75Ex=EHrzpJMq-sKCNCjk1GqhGbeyyH0i+XJvisQ@mail.gmail.com>

As far as I know, the only way to do that would be to rebuild ParaView with
OSMesa support and stop using your GPU to do the rendering.  This will
cause things to be rendered slower, but you would no longer see the peer
window.  If anyone out there knows how to get an OpenGL context to do
GPU-based rendering that doesn't require an actual window, I hope they will
chime in.

Cheers,
Scott

On Wed, Jul 1, 2015 at 10:25 PM, Hermano ... <hermano_lustosa at hotmail.com>
wrote:

> Hello everyone
>
> I am using Paraview Web with the Jetty launcher and the Web Visualizer.
> Anytime a new page is loaded for a new visualization, also a new window
> appears on my desktop (I am using ubuntu with KDE installed, and running
> the web server locally for test purposes). I'd like to know if there is a
> way to supress theses windows with the visualizations. They are a little
> bit annoying.
> To me it's enough to show the visualization on the browser only.
>
> I ran pv_web_visualizer.py with --help , but there wasn't any option
> related to my "issue". So I wonder if there's a way of doing it.
>
> Thanks 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150702/636b1f28/attachment.html>

From 9331922 at qq.com  Thu Jul  2 11:29:41 2015
From: 9331922 at qq.com (=?gb18030?B?uqm6qQ==?=)
Date: Thu, 2 Jul 2015 23:29:41 +0800
Subject: [Paraview] =?gb18030?b?16q3oqO6UmVtb3RlIHZpc3VhbGl6YXRpb24gY29u?=
 =?gb18030?q?figuration_of_paraview?=
Message-ID: <tencent_0768A9D223BCE6FB5C8FBDDD@qq.com>

Hi, everyone. 
I intend to use the paraview remote visualization by run pvserver and paraview on different computer in a LAN environment. However, the paraview client cannot connect to pvserver as there is no DNS in LAN, and the server configuration has the syntax "cs://localhost:11111". It seems that pvserver must be configured as a domain resource, which is impractical in LAN. I wonder if the pvserver can be configured just using IP address, or other configurations needed. Can somebody provide me useful suggestions?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150702/6d20d422/attachment.html>

From dave.demarle at kitware.com  Thu Jul  2 11:57:38 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 2 Jul 2015 11:57:38 -0400
Subject: [Paraview]
	=?utf-8?b?6L2s5Y+R77yaUmVtb3RlIHZpc3VhbGl6YXRpb24gY29u?=
	=?utf-8?q?figuration_of_paraview?=
In-Reply-To: <tencent_0768A9D223BCE6FB5C8FBDDD@qq.com>
References: <tencent_0768A9D223BCE6FB5C8FBDDD@qq.com>
Message-ID: <CANjZAi8SLc073vGZ8FiA7yN8JiuBMnpqYQfAU9hAD5G5V0RDeg@mail.gmail.com>

cs://A.B.C.D:port should work too where A.B.C.D are the ip address.

Also, don't forget the reverse connection capability, where the server
initiates the contact back to the waiting client. This is helpful with
firewalls and when the exact address of the server is not known ahead of
time (as when running on a compute node assigned by a scheduler).




David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Thu, Jul 2, 2015 at 11:29 AM, ?? <9331922 at qq.com> wrote:

>
>
> Hi, everyone.
>
> I intend to use the paraview remote visualization by run pvserver and paraview on different computer in a LAN environment. However, the paraview client cannot connect to pvserver as there is no DNS in LAN, and the server configuration has the syntax "cs://localhost:11111". It seems that pvserver must be configured as a domain resource, which is impractical in LAN. I wonder if the pvserver can be configured just using IP address, or other configurations needed. Can somebody provide me useful suggestions?
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150702/cf2a7f9c/attachment.html>

From normvcr at telus.net  Thu Jul  2 12:37:45 2015
From: normvcr at telus.net (Norman Goldstein)
Date: Thu, 02 Jul 2015 09:37:45 -0700
Subject: [Paraview] Creating a vtp file
In-Reply-To: <CAB5Fpx4fs2en+LDUK0WcYj9kaA=iW0yv8MhaLaZAK-1=SUZqLA@mail.gmail.com>
References: <5594D2CE.9080805@telus.net>
 <CAB5Fpx4fs2en+LDUK0WcYj9kaA=iW0yv8MhaLaZAK-1=SUZqLA@mail.gmail.com>
Message-ID: <559568D9.8010102@telus.net>

Yes, thanks, that is exactly what I needed.

PS
I was getting memory errors when using myArrray->InsertNextTuple1( value )
This cleared up when I switched to myArrray->InsertTuple1( index, value ).


On 07/02/2015 04:40 AM, Cory Quammen wrote:
> Hi Norman,
>
> To set point data, you can first get the point data object with
>
> vtkPointData* pointData = polydata->GetPointData();
>
> Then you can add arrays to it:
>
> vtkFloatArray* myArrray = vtkFloatArray::New();
> myArray->SetName("myArray");
> myArray->SetNumberOfComponents(1);
> myArray->SetNumberOfTuples(polydata->GetNumberOfPoints());
> // Set array elements here...
>
> pointData->AddArray(myArray);
>
> The same holds true for cell data, just replace PointData with 
> CellData, and set the number of tuples to the number of cells instead 
> of the number of points.
>
> Hope this helps,
>
> Cory
>
>
> On Thu, Jul 2, 2015 at 1:57 AM, Norman Goldstein <normvcr at telus.net 
> <mailto:normvcr at telus.net>> wrote:
>
>     From net examples and on-line docs, I have gleaned some of the
>     info to create a full 1-piece vtp file:
>
>     Call
>     vtkXMLPolyDataWriter::SetInputData( vtkDataObject
>     <http://www.vtk.org/doc/nightly/html/classvtkDataObject.html> *)
>
>     where you pass in a vtkPolyData, which you first set up with the
>     methods:
>
>     SetVerts
>     SetLines
>     SetPolys
>     SetStrips
>
>     and the parent method
>
>     SetPoints
>
>     What I have not figured out is how to set the vtp fields
>     PointData and CellData
>
>     Any pointers much appreciated ...
>
>
>
>
>
>     _______________________________________________
>     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
>
>
>
>
> -- 
> Cory Quammen
> R&D Engineer
> Kitware, Inc.

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

From deytonjh at ornl.gov  Thu Jul  2 13:03:48 2015
From: deytonjh at ornl.gov (Deyton, Jordan H.)
Date: Thu, 2 Jul 2015 17:03:48 +0000
Subject: [Paraview] Zooming through the ParaViewWeb API
In-Reply-To: <CABObKxd4_4sbWYg+hE=Fmfw5cDp7=K7WF8Bb_7n5im=-1pMTdg@mail.gmail.com>
References: <559465BA.2030506@ornl.gov>
 <CAPiw4fAd2pc1k+tvd1qz-k0Ygesuyaj1FfxqgOGw_wur8OcBKw@mail.gmail.com>,
 <CABObKxd4_4sbWYg+hE=Fmfw5cDp7=K7WF8Bb_7n5im=-1pMTdg@mail.gmail.com>
Message-ID: <1435856629989.63440@ornl.gov>

I wasn't really sure what to use for the action.


(I will double check that I'm sending the full request with all parameters.) I'll try using "move" instead of "none". I'll also try programmatically sending a very small mouse movement with the left click, and report back if I can find anything out.


Thanks!

Jordan


________________________________
From: Sebastien Jourdain <sebastien.jourdain at kitware.com>
Sent: Wednesday, July 01, 2015 7:09 PM
To: Scott Wittenburg
Cc: Deyton, Jordan H.; paraview at paraview.org
Subject: Re: [Paraview] Zooming through the ParaViewWeb API

Scott is right, the x,y values are normalized, so depending on your screen size if your image is 1000 pixel wide and you want to reflect a move of 10 pixel, you should send a x of 10/1000=0.01.

On Wed, Jul 1, 2015 at 4:28 PM, Scott Wittenburg <scott.wittenburg at kitware.com<mailto:scott.wittenburg at kitware.com>> wrote:
Here is a sample from my websocket frames just now:

[48,4996973606207488,{},"viewport.mouse.interaction",[{"view":353,"action":"move","altKey":false,"ctrlKey":false,"shiftKey":false,"metaKey":false,"buttonLeft":false,"buttonMiddle":false,"buttonRight":true,"x":0.7654596100278551,"y":0.38173817381738173}]]

It seems the "action" should be set to "move" rather than "none", as in the documentation you linked, "none" does not seem to be an option.  Also, as that documentation states, x and y should be normalized to [0, 1], as you correctly guessed.  And finally, you may need to provide all the parameters with values like I show above, not just the ones you are interested in.

But at any rate, this should not then affect the center of rotation, but it sounds like in your case maybe it is?  Can you see if moving just a *tiny* bit keeps at least some of the object in view?

Cheers,
Scott


On Wed, Jul 1, 2015 at 4:12 PM, Jordan Deyton <deytonjh at ornl.gov<mailto:deytonjh at ornl.gov>> wrote:
ParaViewWeb gurus,

Is there a correct way to send a zoom request through the ParaViewWeb API?

I'm especially looking at the PVW MouseHandler (documentation here -- http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/api/protocols.ParaViewWebMouseHandler)

I have had some success by sending a right-click with a small y value (looks like it needs to be between 0 and 1), the action set to "none", and buttonRight set to "true". However, when I afterward rotate the view (using the same RPC call with different methods), the rendered object just vanishes, although the axes and legend are still there.

Jordan

--
Jordan Deyton
Oak Ridge National Laboratory
Telephone: (865) 574-1091<tel:%28865%29%20574-1091>
Email: deytonjh at ornl.gov<mailto:deytonjh at ornl.gov>

_______________________________________________
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<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


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

From deytonjh at ornl.gov  Thu Jul  2 13:05:32 2015
From: deytonjh at ornl.gov (Deyton, Jordan H.)
Date: Thu, 2 Jul 2015 17:05:32 +0000
Subject: [Paraview] Mismatched image size returned from ViewPort image
 render
In-Reply-To: <CABObKxf1+5J_d4k=Y7s+oQynKJP2n2ExA5L_w3oAxuv2NFa4vg@mail.gmail.com>
References: <54F61A57.8050704@ornl.gov>
 <CAPiw4fDbCdE5paPW5xopwueV9qTsHFsKzui07OQ2=9nHmZ9utQ@mail.gmail.com>
 <5594647A.1000305@ornl.gov>
 <CAPiw4fA-YDCPiULPDBpND57J9dBa+zVERhCSxjOXcQYMUGdC3g@mail.gmail.com>,
 <CABObKxf1+5J_d4k=Y7s+oQynKJP2n2ExA5L_w3oAxuv2NFa4vg@mail.gmail.com>
Message-ID: <1435856734324.14777@ornl.gov>

I don't have access to the system right now, but I can try and report back.


Thanks,

Jordan?


________________________________
From: Sebastien Jourdain <sebastien.jourdain at kitware.com>
Sent: Wednesday, July 01, 2015 7:06 PM
To: Scott Wittenburg
Cc: Deyton, Jordan H.; paraview at paraview.org
Subject: Re: [Paraview] Mismatched image size returned from ViewPort image render

Can you change the remote X setting to have a larger resolution?

Seb

On Wed, Jul 1, 2015 at 4:22 PM, Scott Wittenburg <scott.wittenburg at kitware.com<mailto:scott.wittenburg at kitware.com>> wrote:
The "viewport.image.render" rpc call includes the browser viewport size as a parameter, and the server-side peer window should resize itself so that you get the correct image in your browser.  However, if the remote display is configured to have a maximum size of 640 x 480, then I do not believe there is any way to request a larger image from the client side.  Perhaps someone else knows otherwise though.

Cheers,
Scott



On Wed, Jul 1, 2015 at 4:06 PM, Jordan Deyton <deytonjh at ornl.gov<mailto:deytonjh at ornl.gov>> wrote:
Scott, et al,

It appears nothing has changed in the latest nightly build.

However, I have found that the remote X display I'm using is set to a resolution of 640x480. Given that info, it might make sense that ParaView is not rendering anything bigger than 636x420 if it's restricted to the X display's size. Is it possible to get around the size of the remote X display when rendering something offscreen with ParaView?

Jordan

Jordan Deyton
Oak Ridge National Laboratory
Telephone: (865) 574-1091<tel:%28865%29%20574-1091>
Email: deytonjh at ornl.gov<mailto:deytonjh at ornl.gov>

On 3/4/2015 12:15 PM, Scott Wittenburg wrote:
Hi Jordan,

   I wonder if that is the issue that is addressed in this topic:

http://review.source.kitware.com/#/t/5425/

   If so, I think this fix may be merged soon, as it has already been approved.  If you built the ParaView release you're running yourself, you could always try to check out the topic and see if it fixes the issue you're seeing.

Cheers,
Scott




On Tue, Mar 3, 2015 at 1:32 PM, Jordan Deyton <deytonjh at ornl.gov<mailto:deytonjh at ornl.gov>> wrote:
ParaView gurus,

I am working on a project that uses the JSON RPC protocols provided by ParaViewWeb. I've noticed that the image quality for ViewPorts seems bad regardless of what is specified in the call to viewport.image.render (docs here: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/api/protocols.ParaViewWebViewPortImageDelivery<http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#%21/api/protocols.ParaViewWebViewPortImageDelivery> ).

After decoding the returned image from the Base64 encoding, the JPEG image comes out as 636x420, while the quality is listed as 100 and the original size is 1440x850.

The JSON object passed to viewport.image.render looks like

{"args":[{
    "localtime":1425413914878,
    "view":-1,
    "size":[1440,850],
    "quality":100}]
}

While the returned object from that RPC call looks like

{
    "image": "very long encoded image text here",
    "localTime": 0,
    "stale": false,
    "size": [1440,850],
    "format": "jpeg;base64",
    "global_id": "315",
    "mtime": 3068929,
    "workTime": 1
}

I've used two separate Base64 decoders, and both result in a JPEG image that is 636x420, not the reported 1440x850.

Any idea what could be the problem here? Is this a bug in ParaViewWeb? I'm running the latest stable ParaView release (4.3.1) on RHEL.

Thanks,
Jordan

--
Jordan Deyton
Oak Ridge National Laboratory
Telephone: (865) 574-1091<tel:%28865%29%20574-1091>
Email: deytonjh at ornl.gov<mailto:deytonjh at ornl.gov>

_______________________________________________
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<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<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


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

From jtxqhao at gmail.com  Thu Jul  2 23:41:02 2015
From: jtxqhao at gmail.com (Yu Yu)
Date: Fri, 3 Jul 2015 11:41:02 +0800
Subject: [Paraview] Supress windows on pv_web_visualizer.py
In-Reply-To: <CAPiw4fCDuU75Ex=EHrzpJMq-sKCNCjk1GqhGbeyyH0i+XJvisQ@mail.gmail.com>
References: <COL127-W212DB71416372ABEE510B81970@phx.gbl>
 <CAPiw4fCDuU75Ex=EHrzpJMq-sKCNCjk1GqhGbeyyH0i+XJvisQ@mail.gmail.com>
Message-ID: <CAF5M-Cng-1PnVqTDnjZ_hiMQK0DSLnrvexZxOZB_d1H-DXTzZQ@mail.gmail.com>

May be can try this, put the following line in simple.py, CreateView
function to suppress the window
view.UseOffscreenRendering = 1

On Thu, Jul 2, 2015 at 11:15 PM, Scott Wittenburg <
scott.wittenburg at kitware.com> wrote:

> As far as I know, the only way to do that would be to rebuild ParaView
> with OSMesa support and stop using your GPU to do the rendering.  This will
> cause things to be rendered slower, but you would no longer see the peer
> window.  If anyone out there knows how to get an OpenGL context to do
> GPU-based rendering that doesn't require an actual window, I hope they will
> chime in.
>
> Cheers,
> Scott
>
> On Wed, Jul 1, 2015 at 10:25 PM, Hermano ... <hermano_lustosa at hotmail.com>
> wrote:
>
>> Hello everyone
>>
>> I am using Paraview Web with the Jetty launcher and the Web Visualizer.
>> Anytime a new page is loaded for a new visualization, also a new window
>> appears on my desktop (I am using ubuntu with KDE installed, and running
>> the web server locally for test purposes). I'd like to know if there is a
>> way to supress theses windows with the visualizations. They are a little
>> bit annoying.
>> To me it's enough to show the visualization on the browser only.
>>
>> I ran pv_web_visualizer.py with --help , but there wasn't any option
>> related to my "issue". So I wonder if there's a way of doing it.
>>
>> Thanks 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
>>
>>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/28b28ad3/attachment.html>

From fzgkkk at 126.com  Fri Jul  3 00:03:37 2015
From: fzgkkk at 126.com (=?GBK?B?uLbX97ni?=)
Date: Fri, 3 Jul 2015 12:03:37 +0800 (CST)
Subject: [Paraview] some problems about saving point set rendered by Point
	Sprite mode
Message-ID: <57db9c7b.6ed1.14e52158110.Coremail.fzgkkk@126.com>

Dear all the Paraview users?

I have some problems about saving point set rendered by Point Sprite mode
both in eps format and in jpg format in paraview.

(1) When I employed eps format to save the current screen, it gives me
nothing but the points without any rendering, just like fig.1 below.
The reason I think maybe either that Point Sprite mode can not any more
encourage the eps saving or that there is something wrong in the saving process

(2) Then I used jpg format to save, but the only successful one is provided by
choosing the default resolution (925 * 718 here)(fig.2). Others may finally lead to
failure(fig.3). Now I get no point about this.

Does anyone get the solution? I need your help!

Best regards
Zuoguang Fu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/ab7ba8f1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fig.1.jpg
Type: image/jpeg
Size: 20647 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/ab7ba8f1/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fig.2.jpg
Type: image/jpeg
Size: 80963 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/ab7ba8f1/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fig.3.jpg
Type: image/jpeg
Size: 20173 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/ab7ba8f1/attachment-0002.jpg>

From antech777 at gmail.com  Fri Jul  3 02:18:46 2015
From: antech777 at gmail.com (Andrew)
Date: Fri, 3 Jul 2015 09:18:46 +0300
Subject: [Paraview] IntegrateVariables filter (add variables)
Message-ID: <CANMVBVzhWqOyqutPj5xvt4fdFiufR_TEiWaK0+GUxX=ukooYJQ@mail.gmail.com>

Hello.
I tried WaveLet filter and IntegrateVariables works with it. But I need my
flow field variables (pressure, velocity e.t.c.) to be processed.
Calculator filter accept that variables (I can visualise result), but
Integrate filter "doesn't see" the result of Calculator (and it also
doesn't see any flow field variables if it's source is a results file or
"cell data to point data"). I gave a link on example files to be processed
in previous message (see below).
Thanks for your attention...




>> Andrew (antech777 at gmail.com) 02.07.2015
====================================
>> Hello.
>> Thanks for advice! I didn't try Wavelet source, but I will as soon as
possible
>> and will report the result. Surely I can share an example of results:
>> https://drive.google.com/open?id=0BzPt_Ya8Zu8nU2NRT2NWN1ZxV0U
>> Files are in "postprocessing" directory (open the RESULTS.case file)
and have
>> an EnSight Gold format.



>> Andy Bauer <andy.bauer at kitware.com> 02.07.2015
==========================================
>> Have you tried doing the Integrate Variables filter with something like
the Wavelet
>> source? If that works for you as expected, can you share a
representative data set that
>> you're having problems with?
----------------
>> Regards,
>> Andy


>> Andrew (antech777 at gmail.com) 02.07.2015
====================================
>> Hello.
>> I use ParaView to visualize Code_Saturne (CFD) calculation results
(ParaVis module >> in Salome). But I cannot integrate any variable except
coordinates and area
>> or volume.
>> I tried the "Cell data to point data" before IntegrateVariables, it
changed nothing.
>> I asked this question on Salome and CFD-Online forums, but noone replied
me.
>> Please, help.
---------------
>> Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/d1ccb474/attachment.html>

From mctolille at netcourrier.com  Fri Jul  3 04:21:02 2015
From: mctolille at netcourrier.com (mctolille at netcourrier.com)
Date: Fri,  3 Jul 2015 10:21:02 +0200 (CEST)
Subject: [Paraview] Probe location in a script
In-Reply-To: <559553BE.3060005@gmail.com>
Message-ID: <ea-mime-559645ee-595f-3f33053@www-2.netcourrier.com>

Thanks for the script, but how can I now access the data that were found by ProbeLocation? How can I put them in a variable, print them on the screen?

Cheers,
Mc Fly




---- Message d'origine ----
De : "Armin Wehrfritz" <dkxls23 at gmail.com>
? : paraview at paraview.org
Objet : Re: [Paraview] Probe location in a script
Date : 02/07/2015 17:07:42 CEST

Here is a little script that shows you how to read and write dataset in 
ParaView using a simple for loop.

Hope this helps.

-Armin




On 07/02/2015 05:47 PM, mctolille at netcourrier.com wrote:
> Thanks for the tip. I actually already used tracing in order to find the
> command:
> Probelocation.ProbeType.Center = [10.0,20.0,30.0]
>
> But the problem is that I don't know how to access to the data (rho, vx,
> vy...) at that location in the python script
>
> And since tracing does not capture "Save data", I don't even know how to
> write the data in a file
>
> Cheers,
> Mc Fly
>
>
>
>
> Date : 02/07/2015 15:55:04 CEST
>
> Hi McFly,
>
> The Python Tracing facility in ParaView is perfect for this kind of
> task. It records a trace of your actions in the ParaView GUI to a Python
> script that you can modify a bit to process a bunch of files. To turn on
> tracing, choose the Tools -> Start Trace menu item.
>
> More info on tracing is available in the ParaView User Guide [1] under
> section 1.6.2.
>
> Best regards,
> Cory
>
> [1] http://www.paraview.org/paraview-guide/
>
> On Thu, Jul 2, 2015 at 9:39 AM, <mctolille at netcourrier.com
> <mailto:mctolille at netcourrier.com>> wrote:
>
> __
>
> Hi everybody,
>
> I am a new Paraview user. I am trying to extract points from a bunch
> of vtu files. It is pretty easily done with "probe location". But
> since I have a lot of files, I would like to automatize the process
> (with a macro or a python script).
>
> Could someone maybe show me how it's done?
>
> My best guess is that I should have the following in a python script:
> Probelocation.ProbeType.Center = [10.0,20.0,30.0]
> assuming I want to probe at x=10, y=20, z=30. But then, I don't
> really know how to retrieve the variables values at that location.
>
> Thanks a lot,
> Mc Fly
>
> _______________________________________________
> 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
>
>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
>
> _______________________________________________
> 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


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

From cory.quammen at kitware.com  Fri Jul  3 09:31:00 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 3 Jul 2015 09:31:00 -0400
Subject: [Paraview] Probe location in a script
In-Reply-To: <ea-mime-559645ee-595f-3f33053@www-2.netcourrier.com>
References: <559553BE.3060005@gmail.com>
 <ea-mime-559645ee-595f-3f33053@www-2.netcourrier.com>
Message-ID: <CAB5Fpx61GbBq4Rk=eU-_-nyFCtsDGNuz5dsCX2yDWa6j6nqfaw@mail.gmail.com>

Mc Fly,

ParaView always runs as a client-server application, even when just using
the GUI without connecting to a remote server (i.e., the "builtin" server).
The data resides on the server, while the commands you execute are on the
client. Hence, you need to move the data from the server to the client to
access it directly.

Fortunately, this is easy. Let's assume that your ProbeLocation filter is
named "Probelocation". Then all you need to do is run

polyData = servermanager.Fetch(Probelocation)

This brings the probe data, in the form of a vtkPolyData, over to the
client side. Now you can access the probed data through the PointData
attribute of the polyData object:

pointData = polyData.GetPointData()
rhoArray = pointData.GetArray('rho')
value = rhoArray.GetTuple(0)

I hope that helps. For more information on using Fetch, see [1].

Cheers,
Cory

[1] http://www.paraview.org/Wiki/ParaView/Python_Scripting#Source_Proxies



On Fri, Jul 3, 2015 at 4:21 AM, <mctolille at netcourrier.com> wrote:

>  Thanks for the script, but how can I now access the data that were found
> by ProbeLocation? How can I put them in a variable, print them on the
> screen?
>
> Cheers,
> Mc Fly
>
>
>
>
> ---- Message d'origine ----
> De : "Armin Wehrfritz" <dkxls23 at gmail.com>
> ? : paraview at paraview.org
> Objet : Re: [Paraview] Probe location in a script
> Date : 02/07/2015 17:07:42 CEST
>
>
> Here is a little script that shows you how to read and write dataset in
> ParaView using a simple for loop.
>
> Hope this helps.
>
> -Armin
>
>
>
>
> On 07/02/2015 05:47 PM, mctolille at netcourrier.com wrote:
> > Thanks for the tip. I actually already used tracing in order to find the
> > command:
> > Probelocation.ProbeType.Center = [10.0,20.0,30.0]
> >
> > But the problem is that I don't know how to access to the data (rho, vx,
> > vy...) at that location in the python script
> >
> > And since tracing does not capture "Save data", I don't even know how to
> > write the data in a file
> >
> > Cheers,
> > Mc Fly
> >
> >
> >
> >
> > Date : 02/07/2015 15:55:04 CEST
> >
> > Hi McFly,
> >
> > The Python Tracing facility in ParaView is perfect for this kind of
> > task. It records a trace of your actions in the ParaView GUI to a Python
> > script that you can modify a bit to process a bunch of files. To turn on
> > tracing, choose the Tools -> Start Trace menu item.
> >
> > More info on tracing is available in the ParaView User Guide [1] under
> > section 1.6.2.
> >
> > Best regards,
> > Cory
> >
> > [1] http://www.paraview.org/paraview-guide/
> >
> > On Thu, Jul 2, 2015 at 9:39 AM, <mctolille at netcourrier.com
> > <mailto:mctolille at netcourrier.com>> wrote:
> >
> > __
> >
> > Hi everybody,
> >
> > I am a new Paraview user. I am trying to extract points from a bunch
> > of vtu files. It is pretty easily done with "probe location". But
> > since I have a lot of files, I would like to automatize the process
> > (with a macro or a python script).
> >
> > Could someone maybe show me how it's done?
> >
> > My best guess is that I should have the following in a python script:
> > Probelocation.ProbeType.Center = [10.0,20.0,30.0]
> > assuming I want to probe at x=10, y=20, z=30. But then, I don't
> > really know how to retrieve the variables values at that location.
> >
> > Thanks a lot,
> > Mc Fly
> >
> > _______________________________________________
> > 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
> >
> >
> >
> >
> > --
> > Cory Quammen
> > R&D Engineer
> > Kitware, Inc.
> >
> >
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> 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
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/1f20eba5/attachment.html>

From dkxls23 at gmail.com  Fri Jul  3 09:36:35 2015
From: dkxls23 at gmail.com (Armin Wehrfritz)
Date: Fri, 03 Jul 2015 16:36:35 +0300
Subject: [Paraview] Probe location in a script
In-Reply-To: <ea-mime-559645ee-595f-3f33053@www-2.netcourrier.com>
References: <ea-mime-559645ee-595f-3f33053@www-2.netcourrier.com>
Message-ID: <55968FE3.6020800@gmail.com>

I typically use VTK directly when I want to access the raw data from 
python/numpy.  See the series of Blog post by Berk Geveci for more 
information on that: http://kitware.com/blog/home/post/709

In ParaView, to my understanding, you first have to get the data from 
the backend to the frontend with "servermanager.Fetch".  I attached a 
modified version of the script that shows you how to do this in a 
quick-and-dirty way.  See more here: 
http://www.paraview.org/Wiki/ParaView/Python_Scripting

If there is a better way to get access to the raw data, I would be 
really happy to learn how to do this.

Best regards,
Armin





On 07/03/2015 11:21 AM, mctolille at netcourrier.com wrote:
> Thanks for the script, but how can I now access the data that were found
> by ProbeLocation? How can I put them in a variable, print them on the
> screen?
>
> Cheers,
> Mc Fly
>
>
>
>
> ---- Message d'origine ----
> De : "Armin Wehrfritz" <dkxls23 at gmail.com>
> ? : paraview at paraview.org
> Objet : Re: [Paraview] Probe location in a script
> Date : 02/07/2015 17:07:42 CEST
>
> Here is a little script that shows you how to read and write dataset in
> ParaView using a simple for loop.
>
> Hope this helps.
>
> -Armin
>
>
>
>
> On 07/02/2015 05:47 PM, mctolille at netcourrier.com wrote:
>  > Thanks for the tip. I actually already used tracing in order to find the
>  > command:
>  > Probelocation.ProbeType.Center = [10.0,20.0,30.0]
>  >
>  > But the problem is that I don't know how to access to the data (rho, vx,
>  > vy...) at that location in the python script
>  >
>  > And since tracing does not capture "Save data", I don't even know how to
>  > write the data in a file
>  >
>  > Cheers,
>  > Mc Fly
>  >
>  >
>  >
>  >
>  > Date : 02/07/2015 15:55:04 CEST
>  >
>  > Hi McFly,
>  >
>  > The Python Tracing facility in ParaView is perfect for this kind of
>  > task. It records a trace of your actions in the ParaView GUI to a Python
>  > script that you can modify a bit to process a bunch of files. To turn on
>  > tracing, choose the Tools -> Start Trace menu item.
>  >
>  > More info on tracing is available in the ParaView User Guide [1] under
>  > section 1.6.2.
>  >
>  > Best regards,
>  > Cory
>  >
>  > [1] http://www.paraview.org/paraview-guide/
>  >
>  > On Thu, Jul 2, 2015 at 9:39 AM, <mctolille at netcourrier.com
>  > <mailto:mctolille at netcourrier.com>> wrote:
>  >
>  > __
>  >
>  > Hi everybody,
>  >
>  > I am a new Paraview user. I am trying to extract points from a bunch
>  > of vtu files. It is pretty easily done with "probe location". But
>  > since I have a lot of files, I would like to automatize the process
>  > (with a macro or a python script).
>  >
>  > Could someone maybe show me how it's done?
>  >
>  > My best guess is that I should have the following in a python script:
>  > Probelocation.ProbeType.Center = [10.0,20.0,30.0]
>  > assuming I want to probe at x=10, y=20, z=30. But then, I don't
>  > really know how to retrieve the variables values at that location.
>  >
>  > Thanks a lot,
>  > Mc Fly
>  >
>  > _______________________________________________
>  > 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
>  >
>  >
>  >
>  >
>  > --
>  > Cory Quammen
>  > R&D Engineer
>  > Kitware, Inc.
>  >
>  >
>  > _______________________________________________
>  > 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
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: probe2.py
Type: text/x-python
Size: 1154 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/956a33fc/attachment.py>

From andy.bauer at kitware.com  Fri Jul  3 09:51:47 2015
From: andy.bauer at kitware.com (Andy Bauer)
Date: Fri, 3 Jul 2015 09:51:47 -0400
Subject: [Paraview] IntegrateVariables filter (add variables)
In-Reply-To: <CANMVBVzhWqOyqutPj5xvt4fdFiufR_TEiWaK0+GUxX=ukooYJQ@mail.gmail.com>
References: <CANMVBVzhWqOyqutPj5xvt4fdFiufR_TEiWaK0+GUxX=ukooYJQ@mail.gmail.com>
Message-ID: <CAMaOp+ESZBK3NZibsK3oD=_v-eC2-r+J-f3xDibxbBB-rDXeYw@mail.gmail.com>

Hi,

The issue is that you're using a multiblock data set that has fields
defined over only some of the blocks. In the Information tab under Data
Arrays you'll see the list of arrays with "(partial)" in their name. It
will only do the integration for variables that are defined over all
blocks. You can test this out by using the calculator filter to generate a
field over all of the blocks and then use the Integrate Variables filter.

To integrate the partial arrays you'll need the extract block filter to
extract the blocks corresponding to the arrays you want to integrate and
then you can use the Integrate Variables filter.

Regards,
Andy

On Fri, Jul 3, 2015 at 2:18 AM, Andrew <antech777 at gmail.com> wrote:

> Hello.
> I tried WaveLet filter and IntegrateVariables works with it. But I need my
> flow field variables (pressure, velocity e.t.c.) to be processed.
> Calculator filter accept that variables (I can visualise result), but
> Integrate filter "doesn't see" the result of Calculator (and it also
> doesn't see any flow field variables if it's source is a results file or
> "cell data to point data"). I gave a link on example files to be processed
> in previous message (see below).
> Thanks for your attention...
>
>
>
>
> >> Andrew (antech777 at gmail.com) 02.07.2015
> ====================================
> >> Hello.
> >> Thanks for advice! I didn't try Wavelet source, but I will as soon as
> possible
> >> and will report the result. Surely I can share an example of results:
> >> https://drive.google.com/open?id=0BzPt_Ya8Zu8nU2NRT2NWN1ZxV0U
> >> Files are in "postprocessing" directory (open the RESULTS.case file)
> and have
> >> an EnSight Gold format.
>
>
>
> >> Andy Bauer <andy.bauer at kitware.com> 02.07.2015
> ==========================================
> >> Have you tried doing the Integrate Variables filter with something like
> the Wavelet
> >> source? If that works for you as expected, can you share a
> representative data set that
> >> you're having problems with?
> ----------------
> >> Regards,
> >> Andy
>
>
> >> Andrew (antech777 at gmail.com) 02.07.2015
> ====================================
> >> Hello.
> >> I use ParaView to visualize Code_Saturne (CFD) calculation results
> (ParaVis module >> in Salome). But I cannot integrate any variable except
> coordinates and area
> >> or volume.
> >> I tried the "Cell data to point data" before IntegrateVariables, it
> changed nothing.
> >> I asked this question on Salome and CFD-Online forums, but noone
> replied me.
> >> Please, help.
> ---------------
> >> Thanks.
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/7772bacb/attachment.html>

From cory.quammen at kitware.com  Fri Jul  3 10:05:30 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 3 Jul 2015 10:05:30 -0400
Subject: [Paraview] Wrong fetched data
In-Reply-To: <5000545d13da0baa4fa1c3d1e3c44423@fe.up.pt>
References: <5000545d13da0baa4fa1c3d1e3c44423@fe.up.pt>
Message-ID: <CAB5Fpx5xsoTOeBdtEGLBMEDVG5YonkPb5maRPKVpCbbYCJzeGA@mail.gmail.com>

Hi Filipe,

Perhaps the array at index 7 is not the array you are expecting? Could you
access the array by name instead, .e.g.,

dAxis.GetPointData().GetArray('variable_name').GetValue(150)

and see if that works better?

Thanks,
Cory

On Wed, Jul 1, 2015 at 1:44 PM, deq11009 <deq11009 at fe.up.pt> wrote:

> Hi,
>
> I am currently using Paraview 4.2, 64, in Windows. (but tried 4.3 and same
> problem happened)
>
> My case is Ensight transient. Cylinder with 3.6 million cells, two-phase
> flow.
>
> I created a python code, which I run from the shell in the GUI.
>
>
> The main parts of the code are:
>
>
> enscase = EnSightReader(CaseFileName = direcp + 'ensfinal.case')
> ...
> axis = Line()
> ...
> rAxis = ResampleWithDataset(Input = enscase , Source = axis)
> ...
> rAxis.SMProxy.UpdatePipeline(7) # enscase.SMProxy yields same problem
> rAxis.UpdatePipelineInformation()
> dAxis = servermanager.Fetch(rAxis)
>
>
>
> Now, for example:
> print dAxis.GetPointData().GetArray(7).GetValue(150)
> which gives me the value 150 of the phase array.
>
> This data is wrong. On the other hand, if I go to the GUI Pipeline and
> create a Spreadsheet, the values are the real ones (confirmed in Fluent).
>
> So, the fetched data in the python shell is, for some reason, wrong.
> What is my mistake?
>
>
> Thanks
> Filipe Direito
>
> _______________________________________________
> 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
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/3f22a97e/attachment.html>

From antech777 at gmail.com  Fri Jul  3 10:19:48 2015
From: antech777 at gmail.com (Andrew)
Date: Fri, 3 Jul 2015 17:19:48 +0300
Subject: [Paraview] IntegrateVariables filter (add variables)
In-Reply-To: <CAMaOp+ESZBK3NZibsK3oD=_v-eC2-r+J-f3xDibxbBB-rDXeYw@mail.gmail.com>
References: <CANMVBVzhWqOyqutPj5xvt4fdFiufR_TEiWaK0+GUxX=ukooYJQ@mail.gmail.com>
 <CAMaOp+ESZBK3NZibsK3oD=_v-eC2-r+J-f3xDibxbBB-rDXeYw@mail.gmail.com>
Message-ID: <CANMVBVydqMD=8fJhopu=JBDe2NQBpc4cqq=+4cYBS-RoGpTe9g@mail.gmail.com>

*Andy Bauer*
Thanks!
I don't know how to generate "common" field from partial blocks with
Calculator but I'm familiar with Extract Blocks cause I use it to extract
boundaries. AFAIR, I tried to integrate on the extracted boundary without
success but I will play with Extract Block filter in different ways, hope
I'll find the solution. If not, I will write on this mailing list (I have a
holydays for month so I will be online in august).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/0aaddaf7/attachment.html>

From cory.quammen at kitware.com  Fri Jul  3 10:58:10 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 3 Jul 2015 10:58:10 -0400
Subject: [Paraview] Adding functionality to the apply event
In-Reply-To: <55945D96.5040503@micron.com>
References: <55945D96.5040503@micron.com>
Message-ID: <CAB5Fpx4XYz6dfpboZgg=tEq4V_Jkw33QiSHONp_a63RC2aeUUg@mail.gmail.com>

Hi Chris,

The pqPropertiesPanel fires off applied() and applied(pqProxy *) signals
when the "Apply" button is clicked. Would it work for you to connect one of
these signals to a slot in a custom Qt-side class in your plugin? If so,
can make your plugin an autostart plugin (see [1]) to instantiate your Qt
class, and connect it to signals fired from the pqPropertiesPanel. You
should be able to do this by looping over all the pqPropertiesPanels like
this in your plugin's custom Qt class onStart() slot:

foreach (pqPropertiesPanel* ppanel,
mainWindow->findChildren<pqPropertiesPanel*>())
{
  connect(ppanel, SIGNAL(applied()), myCustomQtObject, SLOT(onApplied()));
}

where you do your additional actions in the onApplied() slot.

Please let me know if that wasn't clear.

Cory

[1] http://www.paraview.org/Wiki/Plugin_HowTo#Autostart_Plugins

On Wed, Jul 1, 2015 at 5:37 PM, cunrein <cunrein at micron.com> wrote:

> Hello List,
>
> In a [much much] older version of ParaView, I have a working
> filter/objectPanel pair that inherits from pqAutoGeneratedObjectPanel and
> overloads the accept method.  I want to update this to work with PV4.3.
> ObjectPanels have been replaced with the PropertyPanel.  Do I want to
> inherit from pqPropertyPanel and overload the apply method?  If so, is
> there a CMake macro to add this?  It doesn't look like
> ADD_PARAVIEW_OBJECT_PANEL will work with the new panel philosophy.  If
> creating a new panel is not the right thing to do anymore, how do I add
> functionality to the apply event?
>
> Thanks, Chris
> _______________________________________________
> 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
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/85206300/attachment.html>

From cory.quammen at kitware.com  Fri Jul  3 11:24:49 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 3 Jul 2015 11:24:49 -0400
Subject: [Paraview] Bug for vti in Paraview 4.3
In-Reply-To: <CAN6g8QLTmDWbwDQ8NiRWW-mmN4NVPOarYxJUMGZ5XhtyhinvwA@mail.gmail.com>
References: <CAN6g8QJLXrLFKQ2HcUHoCJrVFTBgGYQcWnh=Pg185yCPV1U3rw@mail.gmail.com>
 <dacee5cee63f476faaa2a396b65ba30a@SRV00045.soton.ac.uk>
 <CAN6g8QLTmDWbwDQ8NiRWW-mmN4NVPOarYxJUMGZ5XhtyhinvwA@mail.gmail.com>
Message-ID: <CAB5Fpx4317JDsTyqyBTWzTOC6+4134paZy7wm-mMbJLSoJjQ3Q@mail.gmail.com>

Hi Gabe,

Thank you for providing  the sample data set. I see the same problem with
the clipping filter you report. In fact, I believe this bug in the bug
tracker is related [1]. To work around this, you could run the Extract
Surface filter and clip by scalars.

As for the problem you report with opacity mapping on surfaces, I do see
problems with the Slice representation on the original data while setting
opacity below the 0 data value to 0 and the opacity above 0 to 1. If I
change the representation to Surface, the opacity mapping seems to work as
expected.

I hope that helps,
Cory

[1] http://www.vtk.org/Bug/view.php?id=13712

On Fri, Jun 19, 2015 at 5:31 AM, Gabe Weymouth <G.D.Weymouth at soton.ac.uk>
wrote:

> Ok, I've put a sample up on dropbox. Note that this uses the
> "format=append" - I'm not sure if the binary data will be readable if
> you're using a different system.
>
> ?
>    sample.vti <https://www.dropbox.com/s/9ht9zr9njulpstn/sample.vti?dl=0>
> ?
>
>
> On Jun 18, 2015 11:10 PM, "Berk Geveci" <berk.geveci at kitware.com> wrote:
>
>> Can you share the dataset with us?
>>
>> Best,
>> -berk
>>
>> On Thu, Jun 18, 2015 at 7:43 AM, Gabe Weymouth <G.D.Weymouth at soton.ac.uk
>> <mailto:G.D.Weymouth at soton.ac.uk>> wrote:
>> I downloaded the newest stable build of paraview yesterday (upgrading
>> from 4.1) so I could utilize the new features in pvpython (Screenshot,
>> etc). Unfortunately, I ran into what appears to be a bug in the handling of
>> clipping/opacity for vti files.
>>
>> I have a 2D field that ranges from -20 to 110 and I need to isolate the
>> negative regions and discard the positive regions. I do this by clipping
>> (type: scalar, value: 0, inside out). In the new version, this clips the
>> entire field - nothing remains.
>>
>> An alternative method that smooths out the transition is to map the
>> scalar from -2 to 2, setting zero opacity at 2. In the new version of
>> paraview, this blanks out both the positive and negative values, leaving
>> only the region between -2 to 2. A color map without opacity works as
>> expected, and the legend shows the correct opacity behaviour.
>>
>> Playing around with the range of the transfer function, the negative
>> values begin to blank out when the positive limit is set below 20. This
>> would seem to indicate a bug in the application of the transfer function to
>> the image grid surface render.
>>
>> If I repeat the tests using a vtr file and identical data, both clipping
>> and opacity work as expected. I see the same results on my mac and linux
>> workstation.
>>
>>
>> Gabriel D Weymouth
>> Southampton Marine and Maritime Institute Lecturer
>> University of Southampton
>> Boldrewood Campus, Building 176, Room 3029
>> Southampton, SO16 7QF, UK
>>
>> _______________________________________________
>> 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
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/304d064d/attachment-0001.html>

From cory.quammen at kitware.com  Fri Jul  3 11:35:46 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 3 Jul 2015 11:35:46 -0400
Subject: [Paraview] Bug for vti in Paraview 4.3
In-Reply-To: <CAB5Fpx4317JDsTyqyBTWzTOC6+4134paZy7wm-mMbJLSoJjQ3Q@mail.gmail.com>
References: <CAN6g8QJLXrLFKQ2HcUHoCJrVFTBgGYQcWnh=Pg185yCPV1U3rw@mail.gmail.com>
 <dacee5cee63f476faaa2a396b65ba30a@SRV00045.soton.ac.uk>
 <CAN6g8QLTmDWbwDQ8NiRWW-mmN4NVPOarYxJUMGZ5XhtyhinvwA@mail.gmail.com>
 <CAB5Fpx4317JDsTyqyBTWzTOC6+4134paZy7wm-mMbJLSoJjQ3Q@mail.gmail.com>
Message-ID: <CAB5Fpx7Lzmq3hGtxQMZZkwjyLHAQyTSwBNaLQR2G8jZ+ZkOwAg@mail.gmail.com>

Gabe,

I filed a bug report about the opacity problem

http://www.vtk.org/Bug/view.php?id=15563

Thanks,
Cory

On Fri, Jul 3, 2015 at 11:24 AM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Hi Gabe,
>
> Thank you for providing  the sample data set. I see the same problem with
> the clipping filter you report. In fact, I believe this bug in the bug
> tracker is related [1]. To work around this, you could run the Extract
> Surface filter and clip by scalars.
>
> As for the problem you report with opacity mapping on surfaces, I do see
> problems with the Slice representation on the original data while setting
> opacity below the 0 data value to 0 and the opacity above 0 to 1. If I
> change the representation to Surface, the opacity mapping seems to work as
> expected.
>
> I hope that helps,
> Cory
>
> [1] http://www.vtk.org/Bug/view.php?id=13712
>
> On Fri, Jun 19, 2015 at 5:31 AM, Gabe Weymouth <G.D.Weymouth at soton.ac.uk>
> wrote:
>
>> Ok, I've put a sample up on dropbox. Note that this uses the
>> "format=append" - I'm not sure if the binary data will be readable if
>> you're using a different system.
>>
>> ?
>>    sample.vti <https://www.dropbox.com/s/9ht9zr9njulpstn/sample.vti?dl=0>
>> ?
>>
>>
>> On Jun 18, 2015 11:10 PM, "Berk Geveci" <berk.geveci at kitware.com> wrote:
>>
>>> Can you share the dataset with us?
>>>
>>> Best,
>>> -berk
>>>
>>> On Thu, Jun 18, 2015 at 7:43 AM, Gabe Weymouth <G.D.Weymouth at soton.ac.uk
>>> <mailto:G.D.Weymouth at soton.ac.uk>> wrote:
>>> I downloaded the newest stable build of paraview yesterday (upgrading
>>> from 4.1) so I could utilize the new features in pvpython (Screenshot,
>>> etc). Unfortunately, I ran into what appears to be a bug in the handling of
>>> clipping/opacity for vti files.
>>>
>>> I have a 2D field that ranges from -20 to 110 and I need to isolate the
>>> negative regions and discard the positive regions. I do this by clipping
>>> (type: scalar, value: 0, inside out). In the new version, this clips the
>>> entire field - nothing remains.
>>>
>>> An alternative method that smooths out the transition is to map the
>>> scalar from -2 to 2, setting zero opacity at 2. In the new version of
>>> paraview, this blanks out both the positive and negative values, leaving
>>> only the region between -2 to 2. A color map without opacity works as
>>> expected, and the legend shows the correct opacity behaviour.
>>>
>>> Playing around with the range of the transfer function, the negative
>>> values begin to blank out when the positive limit is set below 20. This
>>> would seem to indicate a bug in the application of the transfer function to
>>> the image grid surface render.
>>>
>>> If I repeat the tests using a vtr file and identical data, both clipping
>>> and opacity work as expected. I see the same results on my mac and linux
>>> workstation.
>>>
>>>
>>> Gabriel D Weymouth
>>> Southampton Marine and Maritime Institute Lecturer
>>> University of Southampton
>>> Boldrewood Campus, Building 176, Room 3029
>>> Southampton, SO16 7QF, UK
>>>
>>> _______________________________________________
>>> 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
>>
>>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/95436255/attachment.html>

From normvcr at telus.net  Sun Jul  5 02:15:18 2015
From: normvcr at telus.net (Norman Goldstein)
Date: Sat, 04 Jul 2015 23:15:18 -0700
Subject: [Paraview] "zoom to box not quite right"
In-Reply-To: <55945BCE.7060407@telus.net>
References: <55945BCE.7060407@telus.net>
Message-ID: <5598CB76.3020407@telus.net>

I have noticed that "zoom to box" does not result in the zoom that the 
user has requested.
There seems to be a tracker on this:

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

Other than this little thing, kudos to paraview.

Thanks.


From cory.quammen at kitware.com  Sun Jul  5 09:18:41 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Sun, 5 Jul 2015 09:18:41 -0400
Subject: [Paraview] "zoom to box not quite right"
In-Reply-To: <5598CB76.3020407@telus.net>
References: <55945BCE.7060407@telus.net>
	<5598CB76.3020407@telus.net>
Message-ID: <CAB5Fpx6xbsdFv5iTwSTY6hAs-aEZe6bThqXi5ccGFs+PpKdT_g@mail.gmail.com>

Hi Norman,

Thanks for pointing this out. I added a note to the bug tracker to the
effect of "using a 2D rectangle to specify a zoom-in region under
perspective projection is tricky". For fun, you could try turning on the
"Camera Parallel Projection" option. It is much more straightforward to map
the rectangle you have selected to camera zoom, so you should see "better"
results this way.

Cheers,
Cory

On Sun, Jul 5, 2015 at 2:15 AM, Norman Goldstein <normvcr at telus.net> wrote:

> I have noticed that "zoom to box" does not result in the zoom that the
> user has requested.
> There seems to be a tracker on this:
>
> http://www.paraview.org/Bug/view.php?id=13596
>
> Other than this little thing, kudos to paraview.
>
> Thanks.
>
> _______________________________________________
> 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
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150705/94e08572/attachment.html>

From amiramir12345 at outlook.com  Sun Jul  5 17:33:49 2015
From: amiramir12345 at outlook.com (Amir A)
Date: Sun, 5 Jul 2015 16:33:49 -0500
Subject: [Paraview] PNetCDF 64 bit Error
Message-ID: <SNT152-W359A8CBA850A518F233036ED940@phx.gbl>

I am getting an error when loading a NetCDF file that is written using CDF-5 mode using pnetcdf library. This is the error output:


ERROR: In /home1/01249/gda/modules/paraview/ParaView-v4.3.1-source/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 784vtkPVCompositeDataPipeline (0x2aaab6364390): Algorithm vtkVisItMFIXCDFReader(0x2aaab635b0e0) returned failure for request: vtkInformation (0x2aaab6263000)  Debug: Off  Modified Time: 885475  Reference Count: 1  Registered Events: (none)  Request: REQUEST_DATA_OBJECT  ALGORITHM_AFTER_FORWARD: 1  FORWARD_DIRECTION: 0


When I run ncmpidump on the data file it shows the following:
netcdf data_in {// file format: CDF-5 (big variables)dimensions:	x = 1024;	y = 1024 ;	z = 1024 ;variables:	double data(x, y, z) ;
// global attributes:		:CDF-5 mode = 1 ;}

There is no problem if I create the file using the classical mode for a smaller dimension (<2^32), and I can load it into paraview.However, for large problems I have to enable CDF-5.

I am using paraview 4.3.1.

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

From 9331922 at qq.com  Sun Jul  5 21:43:08 2015
From: 9331922 at qq.com (=?gb18030?B?uqm6qQ==?=)
Date: Mon, 6 Jul 2015 09:43:08 +0800
Subject: [Paraview] Running paraview in C/S mode
Message-ID: <tencent_66371AB53EA17EBA7BE3D407@qq.com>

Hi everyone. I intend to run paraview in C/S mode to use remote and parallel visualization in my lab. As the network is LAN, I simply fill the server ip address in paraview's host value. However, the connection process returns "Socket error in call to connect. No route to host." I aslo use test the connectivity using ping command and the result is positive. Besides, I test the C/S function using one machine as client and server, and the connection is completed as well, which proves the port is working. So I really don't know what is going wrong here. Please help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150706/9ca4baa5/attachment.html>

From dinu.patirniche at gmail.com  Mon Jul  6 08:47:39 2015
From: dinu.patirniche at gmail.com (Dinu Patirniche)
Date: Mon, 6 Jul 2015 14:47:39 +0200
Subject: [Paraview] Box clipping is very slow and wasteful!
Message-ID: <CAGGY7Dp5P7QQ-Wm=F=hwKYVL_GQ_smcYBCgzKbYNHMCdt6RH5g@mail.gmail.com>

Hi everybody,

I'm new to this forum, and I am not entirely sure if this is the right
place to post this question, so please direct me to the right corner if
that should be the case.

Ok - to the technical bit now: I am using paraview 4.3.1 to load a 2gb vtk
dataset. One the volume is loaded, I see a memory increase of about 7gb.
Now, as a very first thing, I want to clip the volume, to about a 10th
(with the box option selected from the clip menu). Now, I set up the box
from which I want to extract the volume - but the entire rest of physical
memory (about 5gb) gets eaten up plus another 32gb swap space. By than,
paraview gets killed and I have to start all over again. So why is it that
selecting a small range out of a 7gb volume ends up taking least 37gbs of
memory?

Thanks.
Dinu.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150706/e531a3ff/attachment.html>

From dkxls23 at gmail.com  Mon Jul  6 09:26:51 2015
From: dkxls23 at gmail.com (Armin Wehrfritz)
Date: Mon, 06 Jul 2015 16:26:51 +0300
Subject: [Paraview] Box clipping is very slow and wasteful!
In-Reply-To: <CAGGY7Dp5P7QQ-Wm=F=hwKYVL_GQ_smcYBCgzKbYNHMCdt6RH5g@mail.gmail.com>
References: <CAGGY7Dp5P7QQ-Wm=F=hwKYVL_GQ_smcYBCgzKbYNHMCdt6RH5g@mail.gmail.com>
Message-ID: <559A821B.5020307@gmail.com>

This indicates that ParaView is not selecting a subset of your current 
dataset, but creates a new one.  Things like that happen, when you have 
a structured dataset and apply e.g. the threshold or clipping filter. 
By this, you do not only duplicate a part of the orignal data, you also 
create a unstructured dataset which uses significantly more memory than 
a structured dataset.

So, which kind of dataset do you have?

If you have a structured grid (e.g. vtkImageData, vtkRectilinearGrid, 
vtkStructuredGrid) then you could use the "Extract Subset" instead of 
the clipping filter.

-Armin





On 07/06/2015 03:47 PM, Dinu Patirniche wrote:
> Hi everybody,
>
> I'm new to this forum, and I am not entirely sure if this is the right
> place to post this question, so please direct me to the right corner if
> that should be the case.
>
> Ok - to the technical bit now: I am using paraview 4.3.1 to load a 2gb
> vtk dataset. One the volume is loaded, I see a memory increase of about
> 7gb. Now, as a very first thing, I want to clip the volume, to about a
> 10th (with the box option selected from the clip menu). Now, I set up
> the box from which I want to extract the volume - but the entire rest of
> physical memory (about 5gb) gets eaten up plus another 32gb swap space.
> By than, paraview gets killed and I have to start all over again. So why
> is it that selecting a small range out of a 7gb volume ends up taking
> least 37gbs of memory?
>
> Thanks.
> Dinu.
>
>
>
> _______________________________________________
> 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
>

From sevensam at udel.edu  Mon Jul  6 09:56:45 2015
From: sevensam at udel.edu (Jesse Samluk)
Date: Mon, 6 Jul 2015 09:56:45 -0400
Subject: [Paraview] Custom animation help? (Corrected image)
Message-ID: <A9BF9A24-AFD8-41DD-8F0C-446AD9B8702C@udel.edu>

Greetings all,

  I sent this message last week, but errantly sent the .tif image which made it a huge file. The JPG is now attached.

   I?m trying to make an animation in Paraview. I took a stab at it before with Paraview, but I recall it as being tedious. Maybe I can get some pointers from the experts.

  So, the attached imaged is a cube view of the electromagnetic response over sea ice. What Im trying to do with this animation is two things:

  1.) Move the horizontal slice and Y-Z vertical slice (the slice without the tubes) up and down, and side to side, respectively, such that as if you selected the particular slide in the Pipeline browser, you could drag the slice in question and move it manually to see the different responses. Therefore I?m trying to automate it.

  2.) Rotate it about the z-axis 5 degrees (to about 180) at each iteration and return, then rotate it 5 degrees at each iteration about the y-axis (till about 45 degrees) and return. These rotations will occur while ?action item" 1 is happening.

   Any thoughts/suggestions?

    Thanks!
    Jesse
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150706/db022051/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: YZPlaneInitialForParaview.jpeg
Type: image/jpeg
Size: 27388 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150706/db022051/attachment.jpeg>

From deq11009 at fe.up.pt  Mon Jul  6 10:23:18 2015
From: deq11009 at fe.up.pt (deq11009)
Date: Mon, 06 Jul 2015 15:23:18 +0100
Subject: [Paraview] Wrong fetched data
In-Reply-To: <CAB5Fpx5xsoTOeBdtEGLBMEDVG5YonkPb5maRPKVpCbbYCJzeGA@mail.gmail.com>
References: <5000545d13da0baa4fa1c3d1e3c44423@fe.up.pt>
 <CAB5Fpx5xsoTOeBdtEGLBMEDVG5YonkPb5maRPKVpCbbYCJzeGA@mail.gmail.com>
Message-ID: <f79e260d16a28fb08f353b8626184dee@fe.up.pt>

Hi,

Thank you for your reply.

No, the mistake is not there. In the meantime I did realize what is 
exactly happening.

I have, say, 200 timesteps.
 From 0 to 6, data obtained from my code matches the data when I just 
use the GUI.
Starting in timestep 7 (always) till the end, data (for all timesteps) 
is the data from the last timestep.
So, when in python shell I go to timestep 6, I see timestep 6. But when 
I go to timestep 7, or 100, or 133, I see timestep 199. At the same 
time, if I go to the GUI, everything is ok.

By coincidence, the ".case" time step data is organized in seven 
columns. Is this related to the problem?

Thank you
Filipe Direito


On 03.07.2015 15:05, Cory Quammen wrote:
> Hi Filipe,
>
> Perhaps the array at index 7 is not the array you are expecting? 
> Could
> you access the array by name instead, .e.g.,
>
> dAxis.GetPointData().GetArray(variable_name).GetValue(150)
>
> and see if that works better?
>
> Thanks,
> Cory
>
> On Wed, Jul 1, 2015 at 1:44 PM, deq11009 <deq11009 at fe.up.pt [6]>
> wrote:
>
>> Hi,
>>
>> I am currently using Paraview 4.2, 64, in Windows. (but tried 4.3
>> and same problem happened)
>>
>> My case is Ensight transient. Cylinder with 3.6 million cells,
>> two-phase flow.
>>
>> I created a python code, which I run from the shell in the GUI.
>>
>> The main parts of the code are:
>>
>> enscase = EnSightReader(CaseFileName = direcp + ensfinal.case)
>> ...
>> axis = Line()
>> ...
>> rAxis = ResampleWithDataset(Input = enscase , Source = axis)
>> ...
>> rAxis.SMProxy.UpdatePipeline(7) # enscase.SMProxy yields same
>> problem
>> rAxis.UpdatePipelineInformation()
>> dAxis = servermanager.Fetch(rAxis)
>>
>> Now, for example:
>> print dAxis.GetPointData().GetArray(7).GetValue(150)
>> which gives me the value 150 of the phase array.
>>
>> This data is wrong. On the other hand, if I go to the GUI Pipeline
>> and create a Spreadsheet, the values are the real ones (confirmed in
>> Fluent).
>>
>> So, the fetched data in the python shell is, for some reason,
>> wrong.
>> What is my mistake?
>>
>> Thanks
>> Filipe Direito
>>
>> _______________________________________________
>> Powered by www.kitware.com [1]
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html [2]
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView [3]
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>> [4]
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview [5]


From amiramir12345 at outlook.com  Mon Jul  6 11:24:06 2015
From: amiramir12345 at outlook.com (Amir A)
Date: Mon, 6 Jul 2015 10:24:06 -0500
Subject: [Paraview] PNetCDF 64 bit Error
In-Reply-To: <SNT152-W359A8CBA850A518F233036ED940@phx.gbl>
References: <SNT152-W359A8CBA850A518F233036ED940@phx.gbl>
Message-ID: <SNT152-W6C7BDD2CF4F993EE7262AED930@phx.gbl>

A small pnetcdf file is attached.

The output of ncmpidump is the following:
netcdf data_in {// file format: CDF-5 (big variables)dimensions:	x = 4 ;	y = 4 ;	z = 4 ;variables:	double data(x, y, z) ;
// global attributes:		:CDF-5 mode = 1 ;data:
 data =  -1.83667601732677e-48, -1.49975978266186e-32, 0, 1.49975978266186e-32,  -1.49975978266186e-32, -1.22464679914735e-16, 0, 1.22464679914735e-16,  0, 0, -0, -0,  1.49975978266186e-32, 1.22464679914735e-16, -0, -1.22464679914735e-16,  -1.49975978266186e-32, -1.22464679914735e-16, 0, 1.22464679914735e-16,  -1.22464679914735e-16, -1, 0, 1,  0, 0, -0, -0,  1.22464679914735e-16, 1, -0, -1,  0, 0, -0, -0,  0, 0, -0, -0,  -0, -0, 0, 0,  -0, -0, 0, 0,  1.49975978266186e-32, 1.22464679914735e-16, -0, -1.22464679914735e-16,  1.22464679914735e-16, 1, -0, -1,  -0, -0, 0, 0,  -1.22464679914735e-16, -1, 0, 1 ;} 


From: amiramir12345 at outlook.com
To: paraview at paraview.org
Subject: PNetCDF 64 bit Error
Date: Sun, 5 Jul 2015 16:33:49 -0500




I am getting an error when loading a NetCDF file that is written using CDF-5 mode using pnetcdf library. This is the error output:


ERROR: In /home1/01249/gda/modules/paraview/ParaView-v4.3.1-source/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 784vtkPVCompositeDataPipeline (0x2aaab6364390): Algorithm vtkVisItMFIXCDFReader(0x2aaab635b0e0) returned failure for request: vtkInformation (0x2aaab6263000)  Debug: Off  Modified Time: 885475  Reference Count: 1  Registered Events: (none)  Request: REQUEST_DATA_OBJECT  ALGORITHM_AFTER_FORWARD: 1  FORWARD_DIRECTION: 0


When I run ncmpidump on the data file it shows the following:
netcdf data_in {// file format: CDF-5 (big variables)dimensions:	x = 1024;	y = 1024 ;	z = 1024 ;variables:	double data(x, y, z) ;
// global attributes:		:CDF-5 mode = 1 ;}

There is no problem if I create the file using the classical mode for a smaller dimension (<2^32), and I can load it into paraview.However, for large problems I have to enable CDF-5.

I am using paraview 4.3.1.

 		 	   		   		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150706/a35c925a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: data_in.nc
Type: application/x-netcdf
Size: 1024 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150706/a35c925a/attachment.nc>

From u.utku.turuncoglu at be.itu.edu.tr  Mon Jul  6 14:23:00 2015
From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr)
Date: Mon, 6 Jul 2015 21:23:00 +0300 (EEST)
Subject: [Paraview] PNetCDF 64 bit Error
In-Reply-To: <SNT152-W6C7BDD2CF4F993EE7262AED930@phx.gbl>
References: <SNT152-W359A8CBA850A518F233036ED940@phx.gbl>
 <SNT152-W6C7BDD2CF4F993EE7262AED930@phx.gbl>
Message-ID: <38139.5.170.98.88.1436206980.squirrel@webmail.be.itu.edu.tr>

Hi,

As i know there is a large file support option and you could select during
ParaView installation. I am not sure about it's value in the binary
distribution of ParaView. By the way, the NetCDF library used in the
ParaView reader could only support NetCDF classic as default and you might
need to install from source using NetCDF4 library.

I hope it helps,
Regards,

--ufuk

> A small pnetcdf file is attached.
>
> The output of ncmpidump is the following:
> netcdf data_in {// file format: CDF-5 (big variables)dimensions:	x = 4 ;	y
> = 4 ;	z = 4 ;variables:	double data(x, y, z) ;
> // global attributes:		:CDF-5 mode = 1 ;data:
>  data =  -1.83667601732677e-48, -1.49975978266186e-32, 0,
> 1.49975978266186e-32,  -1.49975978266186e-32, -1.22464679914735e-16, 0,
> 1.22464679914735e-16,  0, 0, -0, -0,  1.49975978266186e-32,
> 1.22464679914735e-16, -0, -1.22464679914735e-16,  -1.49975978266186e-32,
> -1.22464679914735e-16, 0, 1.22464679914735e-16,  -1.22464679914735e-16,
> -1, 0, 1,  0, 0, -0, -0,  1.22464679914735e-16, 1, -0, -1,  0, 0, -0, -0,
>  0, 0, -0, -0,  -0, -0, 0, 0,  -0, -0, 0, 0,  1.49975978266186e-32,
> 1.22464679914735e-16, -0, -1.22464679914735e-16,  1.22464679914735e-16,
> 1, -0, -1,  -0, -0, 0, 0,  -1.22464679914735e-16, -1, 0, 1 ;}
>
>
> From: amiramir12345 at outlook.com
> To: paraview at paraview.org
> Subject: PNetCDF 64 bit Error
> Date: Sun, 5 Jul 2015 16:33:49 -0500
>
>
>
>
> I am getting an error when loading a NetCDF file that is written using
> CDF-5 mode using pnetcdf library. This is the error output:
>
>
> ERROR: In
> /home1/01249/gda/modules/paraview/ParaView-v4.3.1-source/VTK/Common/ExecutionModel/vtkExecutive.cxx,
> line 784vtkPVCompositeDataPipeline (0x2aaab6364390): Algorithm
> vtkVisItMFIXCDFReader(0x2aaab635b0e0) returned failure for request:
> vtkInformation (0x2aaab6263000)  Debug: Off  Modified Time: 885475
> Reference Count: 1  Registered Events: (none)  Request:
> REQUEST_DATA_OBJECT  ALGORITHM_AFTER_FORWARD: 1  FORWARD_DIRECTION: 0
>
>
> When I run ncmpidump on the data file it shows the following:
> netcdf data_in {// file format: CDF-5 (big variables)dimensions:	x =
> 1024;	y = 1024 ;	z = 1024 ;variables:	double data(x, y, z) ;
> // global attributes:		:CDF-5 mode = 1 ;}
>
> There is no problem if I create the file using the classical mode for a
> smaller dimension (<2^32), and I can load it into paraview.However, for
> large problems I have to enable CDF-5.
>
> I am using paraview 4.3.1.
>
>  		 	   		   		 	   		  _______________________________________________
> 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
>


From dave.demarle at kitware.com  Mon Jul  6 14:43:06 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Mon, 6 Jul 2015 14:43:06 -0400
Subject: [Paraview] PNetCDF 64 bit Error
In-Reply-To: <38139.5.170.98.88.1436206980.squirrel@webmail.be.itu.edu.tr>
References: <SNT152-W359A8CBA850A518F233036ED940@phx.gbl>
 <SNT152-W6C7BDD2CF4F993EE7262AED930@phx.gbl>
 <38139.5.170.98.88.1436206980.squirrel@webmail.be.itu.edu.tr>
Message-ID: <CANjZAi_xA_OAqAoS1-5-r1auDeN5DaCTYvpBnJB1dq7bhJeCxg@mail.gmail.com>

> distribution of ParaView. By the way, the NetCDF library used in the
> ParaView reader could only support NetCDF classic as default and you might
> need to install from source using NetCDF4 library.
>
>
ParaView has supported netcdf4 since 3.14. 3.14.0 only through our internal
libnetcdf/hdf; 3.14.1 added it through external too.

However, I do not know if anyone has used the pnetcdf variant. You may be
the first Amir.

Can anyone else on the list comment on the status of pnetcdf support in
ParaView?



> I hope it helps,
> Regards,
>
> --ufuk
>
> > A small pnetcdf file is attached.
> >
> > The output of ncmpidump is the following:
> > netcdf data_in {// file format: CDF-5 (big variables)dimensions:      x
> = 4 ; y
> > = 4 ; z = 4 ;variables:       double data(x, y, z) ;
> > // global attributes:         :CDF-5 mode = 1 ;data:
> >  data =  -1.83667601732677e-48, -1.49975978266186e-32, 0,
> > 1.49975978266186e-32,  -1.49975978266186e-32, -1.22464679914735e-16, 0,
> > 1.22464679914735e-16,  0, 0, -0, -0,  1.49975978266186e-32,
> > 1.22464679914735e-16, -0, -1.22464679914735e-16,  -1.49975978266186e-32,
> > -1.22464679914735e-16, 0, 1.22464679914735e-16,  -1.22464679914735e-16,
> > -1, 0, 1,  0, 0, -0, -0,  1.22464679914735e-16, 1, -0, -1,  0, 0, -0, -0,
> >  0, 0, -0, -0,  -0, -0, 0, 0,  -0, -0, 0, 0,  1.49975978266186e-32,
> > 1.22464679914735e-16, -0, -1.22464679914735e-16,  1.22464679914735e-16,
> > 1, -0, -1,  -0, -0, 0, 0,  -1.22464679914735e-16, -1, 0, 1 ;}
> >
> >
> > From: amiramir12345 at outlook.com
> > To: paraview at paraview.org
> > Subject: PNetCDF 64 bit Error
> > Date: Sun, 5 Jul 2015 16:33:49 -0500
> >
> >
> >
> >
> > I am getting an error when loading a NetCDF file that is written using
> > CDF-5 mode using pnetcdf library. This is the error output:
> >
> >
> > ERROR: In
> >
> /home1/01249/gda/modules/paraview/ParaView-v4.3.1-source/VTK/Common/ExecutionModel/vtkExecutive.cxx,
> > line 784vtkPVCompositeDataPipeline (0x2aaab6364390): Algorithm
> > vtkVisItMFIXCDFReader(0x2aaab635b0e0) returned failure for request:
> > vtkInformation (0x2aaab6263000)  Debug: Off  Modified Time: 885475
> > Reference Count: 1  Registered Events: (none)  Request:
> > REQUEST_DATA_OBJECT  ALGORITHM_AFTER_FORWARD: 1  FORWARD_DIRECTION: 0
> >
> >
> > When I run ncmpidump on the data file it shows the following:
> > netcdf data_in {// file format: CDF-5 (big variables)dimensions:      x =
> > 1024; y = 1024 ;      z = 1024 ;variables:    double data(x, y, z) ;
> > // global attributes:         :CDF-5 mode = 1 ;}
> >
> > There is no problem if I create the file using the classical mode for a
> > smaller dimension (<2^32), and I can load it into paraview.However, for
> > large problems I have to enable CDF-5.
> >
> > I am using paraview 4.3.1.
> >
> >
>        _______________________________________________
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150706/7a2f4255/attachment.html>

From m.schlottke-lakemper at aia.rwth-aachen.de  Mon Jul  6 14:41:47 2015
From: m.schlottke-lakemper at aia.rwth-aachen.de (Schlottke-Lakemper, Michael)
Date: Mon, 6 Jul 2015 18:41:47 +0000
Subject: [Paraview] PNetCDF 64 bit Error
In-Reply-To: <38139.5.170.98.88.1436206980.squirrel@webmail.be.itu.edu.tr>
References: <SNT152-W359A8CBA850A518F233036ED940@phx.gbl>
 <SNT152-W6C7BDD2CF4F993EE7262AED930@phx.gbl>
 <38139.5.170.98.88.1436206980.squirrel@webmail.be.itu.edu.tr>
Message-ID: <5DE6D86A-230D-434A-AA2C-DC2511213CCD@aia.rwth-aachen.de>


I am getting an error when loading a NetCDF file that is written using
CDF-5 mode using pnetcdf library. This is the error output:
According to the Parallel NetCDF website, CFD-5 is not supported by the NetCDF library at all: https://trac.mcs.anl.gov/projects/parallel-netcdf/wiki/FileLimits

Thus I think you either need to modify your ParaView sources to use the parallel netcdf library for reading NetCDF files, or you could write your own reader plugin.

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

From deytonjh at ornl.gov  Mon Jul  6 18:42:12 2015
From: deytonjh at ornl.gov (Jordan Deyton)
Date: Mon, 06 Jul 2015 18:42:12 -0400
Subject: [Paraview] Zooming through the ParaViewWeb API
In-Reply-To: <1435856629989.63440@ornl.gov>
References: <559465BA.2030506@ornl.gov>
 <CAPiw4fAd2pc1k+tvd1qz-k0Ygesuyaj1FfxqgOGw_wur8OcBKw@mail.gmail.com>,
 <CABObKxd4_4sbWYg+hE=Fmfw5cDp7=K7WF8Bb_7n5im=-1pMTdg@mail.gmail.com>
 <1435856629989.63440@ornl.gov>
Message-ID: <559B0444.9020808@ornl.gov>

I figured out my problem. Basically, the API has an expected chain of 
mouse interaction requests:

When zooming:
1 - (fired when ctrl+right-mouse is pressed)
/action/: down
/states/: buttonRight and ctrlKey should be true
/y/: should be the current, normalized zoom (something between 0 and 1)
2 - (fired when mouse moves along y-axis)
/action/: move
/states/: buttonRight and ctrlKey should be true
/y/: should be the current, normalized zoom based on the change in y
3 - (fired when scrolling stops)
/action/: up
/states/: buttonRight and ctrlKey should be false this time
/y/: should be the current, normalized zoom

When rotating:
1 - (fired when left-mouse is pressed)
/action/: down
/states/: buttonLeft is true
/x,y/: should be the current cursor location, normalized
2 - (fired when mouse moves)
/action/: move
/states/: buttonLeft is true
/x,y/: should be the current cursor location, normalized
3 - (fired when left-mouse is released)
/action/: up
/states/: buttonLeft should be false this time
/x,y/: should be the current cursor location, normalized

As long as those requests take place in the right order, everything 
works as expected. Thanks for the clues, guys.

Jordan

Jordan Deyton
Oak Ridge National Laboratory
Telephone: (865) 574-1091
Email: deytonjh at ornl.gov

On 7/2/2015 1:03 PM, Deyton, Jordan H. wrote:
>
> I wasn't really sure what to use for the action.
>
>
> (I will double check that I'm sending the full request with all 
> parameters.) I'll try using "move" instead of "none". I'll also try 
> programmatically sending a very small mouse movement with the left 
> click, and report back if I can find anything out.
>
>
> Thanks!
>
> Jordan
>
>
> ------------------------------------------------------------------------
> *From:* Sebastien Jourdain <sebastien.jourdain at kitware.com>
> *Sent:* Wednesday, July 01, 2015 7:09 PM
> *To:* Scott Wittenburg
> *Cc:* Deyton, Jordan H.; paraview at paraview.org
> *Subject:* Re: [Paraview] Zooming through the ParaViewWeb API
> Scott is right, the x,y values are normalized, so depending on your 
> screen size if your image is 1000 pixel wide and you want to reflect a 
> move of 10 pixel, you should send a x of 10/1000=0.01.
>
> On Wed, Jul 1, 2015 at 4:28 PM, Scott Wittenburg 
> <scott.wittenburg at kitware.com <mailto:scott.wittenburg at kitware.com>> 
> wrote:
>
>     Here is a sample from my websocket frames just now:
>
>     [48,4996973606207488,{},"viewport.mouse.interaction",[{"view":353,"action":"move","altKey":false,"ctrlKey":false,"shiftKey":false,"metaKey":false,"buttonLeft":false,"buttonMiddle":false,"buttonRight":true,"x":0.7654596100278551,"y":0.38173817381738173}]]
>
>
>     It seems the "action" should be set to "move" rather than "none",
>     as in the documentation you linked, "none" does not seem to be an
>     option.  Also, as that documentation states, x and y should be
>     normalized to [0, 1], as you correctly guessed.  And finally, you
>     may need to provide all the parameters with values like I show
>     above, not just the ones you are interested in.
>
>     But at any rate, this should not then affect the center of
>     rotation, but it sounds like in your case maybe it is?  Can you
>     see if moving just a *tiny* bit keeps at least some of the object
>     in view?
>
>     Cheers,
>     Scott
>
>
>     On Wed, Jul 1, 2015 at 4:12 PM, Jordan Deyton <deytonjh at ornl.gov
>     <mailto:deytonjh at ornl.gov>> wrote:
>
>         ParaViewWeb gurus,
>
>         Is there a correct way to send a zoom request through the
>         ParaViewWeb API?
>
>         I'm especially looking at the PVW MouseHandler (documentation
>         here --
>         http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/api/protocols.ParaViewWebMouseHandler
>         <http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#%21/api/protocols.ParaViewWebMouseHandler>)
>
>         I have had some success by sending a right-click with a small
>         y value (looks like it needs to be between 0 and 1), the
>         action set to "none", and buttonRight set to "true". However,
>         when I afterward rotate the view (using the same RPC call with
>         different methods), the rendered object just vanishes,
>         although the axes and legend are still there.
>
>         Jordan
>
>         -- 
>         Jordan Deyton
>         Oak Ridge National Laboratory
>         Telephone: (865) 574-1091 <tel:%28865%29%20574-1091>
>         Email: deytonjh at ornl.gov <mailto:deytonjh at ornl.gov>
>
>         _______________________________________________
>         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
>         <http://paraview.org/Wiki/ParaView>
>
>         Search the list archives at:
>         http://markmail.org/search/?q=ParaView
>         <http://markmail.org/search/?q=ParaView>
>
>         Follow this link to subscribe/unsubscribe:
>         http://public.kitware.com/mailman/listinfo/paraview
>
>
>
>     _______________________________________________
>     Powered by www.kitware.com <http://www.kitware.com>
>
>     Visit other Kitware open-source projects at
>     http://www.kitware.com/opensource/opensource.html
>     <http://www.kitware.com/opensource/opensource.html>
>
>     Please keep messages on-topic and check the ParaView Wiki at:
>     http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
>
>     Search the list archives at:
>     http://markmail.org/search/?q=ParaView
>     <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

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

From Jonathan_England at amat.com  Tue Jul  7 06:08:18 2015
From: Jonathan_England at amat.com (Jonathan_England at amat.com)
Date: Tue, 7 Jul 2015 10:08:18 +0000
Subject: [Paraview] pvserver 4.3.1 for linux available?
Message-ID: <9FB544F7B8D99E42ABADFEEB0BC26EE421C56BE9@045-SN2MPN2-051.045d.mgd.msft.net>

I have successfully implemented some macros to run under Paraview 4.3.1 on my windows laptop.  I now want to run this as a client / server on a remote system running unix.   I installed the latest paraview 4.3.1 from the linux tar.gz file on to the remote computer, but this only contains pvserver 3.8.1.  The version mismatch does not allow me to connect.  I have verified that I can connect successfully if I run paraview 3.8.1 on my laptop.

Is pvserver 4.3.1 for unix available?   I have searched and cannot find it anywhere, and  I really don't want to have to start compiling, so binary executables would be wonderful.

Regards

Dr Jonathan England

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

From dave.demarle at kitware.com  Tue Jul  7 11:58:40 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Tue, 7 Jul 2015 11:58:40 -0400
Subject: [Paraview] pvserver 4.3.1 for linux available?
In-Reply-To: <9FB544F7B8D99E42ABADFEEB0BC26EE421C56BE9@045-SN2MPN2-051.045d.mgd.msft.net>
References: <9FB544F7B8D99E42ABADFEEB0BC26EE421C56BE9@045-SN2MPN2-051.045d.mgd.msft.net>
Message-ID: <CANjZAi-Qc+ZsEmkVSUAwFhD596w4ai36tEoMamSNJMkJAE0ehw@mail.gmail.com>

I suspect your PATH is putting a different pvserver in the way.

What does "which pvserver" return?



David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Tue, Jul 7, 2015 at 6:08 AM, <Jonathan_England at amat.com> wrote:

>  I have successfully implemented some macros to run under Paraview 4.3.1
> on my windows laptop.  I now want to run this as a client / server on a
> remote system running unix.   I installed the latest paraview 4.3.1 from
> the linux tar.gz file on to the remote computer, but this only contains
> pvserver 3.8.1.  The version mismatch does not allow me to connect.  I have
> verified that I can connect successfully if I run paraview 3.8.1 on my
> laptop.
>
>
>
> Is pvserver 4.3.1 for unix available?   I have searched and cannot find it
> anywhere, and  I really don?t want to have to start compiling, so binary
> executables would be wonderful.
>
>
>
> Regards
>
>
>
> Dr Jonathan England
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150707/f332e9e3/attachment.html>

From oksana_golovnya at mail.ru  Tue Jul  7 10:39:59 2015
From: oksana_golovnya at mail.ru (=?UTF-8?B?T2tzYW5h?=)
Date: Tue, 07 Jul 2015 17:39:59 +0300
Subject: [Paraview] =?utf-8?q?Molecular_dynamics_from_lammps?=
Message-ID: <1436279999.571994242@f345.i.mail.ru>


Dear community ,
I am trying to visualize array of atoms with their displacement vectors in Paraview. The structure is complicated and cannot be represented by StructuredGrid. The goal is to have slices with surface vectors (displacement) and atoms. I have tried two ways:
1. ??????  Generate a vtk file. In this case I have a polydata of points and vectors, but I cannot use SurfaceVectors filter in this dataset. I tried Delaunay3D filter to produce a grid, but it produces too many cells, which do not represent my structure properly, and instead of one vector per atom I have some strange distribution.
2. ??????  Load lammps dump file. In this case after MergeBlocks and Calculator filters I have unstructured grid with points and vectors, but cannot use this vectors in Slice->SurfaceVector pipeline anyway. SurfaceVectors are inactive.
I understand that in the first case I need to generate a grid with each atom inside one cell. However, I do not know how to do it. And in the second I do not understand why SurfaceVectors are inactive on the unstructured grid? I would appreciate any help, explanation or reference how to do it right.
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150707/60793b1e/attachment.html>

From amiramir12345 at outlook.com  Tue Jul  7 17:28:32 2015
From: amiramir12345 at outlook.com (Amir A)
Date: Tue, 7 Jul 2015 16:28:32 -0500
Subject: [Paraview] PNetCDF 64 bit Error
In-Reply-To: <CANjZAi_xA_OAqAoS1-5-r1auDeN5DaCTYvpBnJB1dq7bhJeCxg@mail.gmail.com>
References: <SNT152-W359A8CBA850A518F233036ED940@phx.gbl>
 <SNT152-W6C7BDD2CF4F993EE7262AED930@phx.gbl>,
 <38139.5.170.98.88.1436206980.squirrel@webmail.be.itu.edu.tr>,
 <CANjZAi_xA_OAqAoS1-5-r1auDeN5DaCTYvpBnJB1dq7bhJeCxg@mail.gmail.com>
Message-ID: <SNT152-W122C50079BCEE25EA8B00DED920@phx.gbl>

So one of the reasons I have to use CDF-5 is that netcdf4 does not support large arrays (>2GiB), but CDF-5 does.So I have a question: Is it possible to break a large file into netcdf4 files and write a parent wrapper around it  and use that as input to paraview? What I mean is to write a pvti (or similar) parent file, that links smaller netcdf files together. Paraview recognizes netcdf4, so that should not be a problem.If this works, then the size limitation of netcdf would not be a problem and I can avoid going the CDF-5 route.
From: dave.demarle at kitware.com
Date: Mon, 6 Jul 2015 14:43:06 -0400
Subject: Re: [Paraview] PNetCDF 64 bit Error
To: u.utku.turuncoglu at be.itu.edu.tr
CC: amiramir12345 at outlook.com; paraview at paraview.org



distribution of ParaView. By the way, the NetCDF library used in the

ParaView reader could only support NetCDF classic as default and you might

need to install from source using NetCDF4 library.



ParaView has supported netcdf4 since 3.14. 3.14.0 only through our internal libnetcdf/hdf; 3.14.1 added it through external too.
However, I do not know if anyone has used the pnetcdf variant. You may be the first Amir.
Can anyone else on the list comment on the status of pnetcdf support in ParaView?
 

I hope it helps,

Regards,



--ufuk



> A small pnetcdf file is attached.

>

> The output of ncmpidump is the following:

> netcdf data_in {// file format: CDF-5 (big variables)dimensions:      x = 4 ; y

> = 4 ; z = 4 ;variables:       double data(x, y, z) ;

> // global attributes:         :CDF-5 mode = 1 ;data:

>  data =  -1.83667601732677e-48, -1.49975978266186e-32, 0,

> 1.49975978266186e-32,  -1.49975978266186e-32, -1.22464679914735e-16, 0,

> 1.22464679914735e-16,  0, 0, -0, -0,  1.49975978266186e-32,

> 1.22464679914735e-16, -0, -1.22464679914735e-16,  -1.49975978266186e-32,

> -1.22464679914735e-16, 0, 1.22464679914735e-16,  -1.22464679914735e-16,

> -1, 0, 1,  0, 0, -0, -0,  1.22464679914735e-16, 1, -0, -1,  0, 0, -0, -0,

>  0, 0, -0, -0,  -0, -0, 0, 0,  -0, -0, 0, 0,  1.49975978266186e-32,

> 1.22464679914735e-16, -0, -1.22464679914735e-16,  1.22464679914735e-16,

> 1, -0, -1,  -0, -0, 0, 0,  -1.22464679914735e-16, -1, 0, 1 ;}

>

>

> From: amiramir12345 at outlook.com

> To: paraview at paraview.org

> Subject: PNetCDF 64 bit Error

> Date: Sun, 5 Jul 2015 16:33:49 -0500

>

>

>

>

> I am getting an error when loading a NetCDF file that is written using

> CDF-5 mode using pnetcdf library. This is the error output:

>

>

> ERROR: In

> /home1/01249/gda/modules/paraview/ParaView-v4.3.1-source/VTK/Common/ExecutionModel/vtkExecutive.cxx,

> line 784vtkPVCompositeDataPipeline (0x2aaab6364390): Algorithm

> vtkVisItMFIXCDFReader(0x2aaab635b0e0) returned failure for request:

> vtkInformation (0x2aaab6263000)  Debug: Off  Modified Time: 885475

> Reference Count: 1  Registered Events: (none)  Request:

> REQUEST_DATA_OBJECT  ALGORITHM_AFTER_FORWARD: 1  FORWARD_DIRECTION: 0

>

>

> When I run ncmpidump on the data file it shows the following:

> netcdf data_in {// file format: CDF-5 (big variables)dimensions:      x =

> 1024; y = 1024 ;      z = 1024 ;variables:    double data(x, y, z) ;

> // global attributes:         :CDF-5 mode = 1 ;}

>

> There is no problem if I create the file using the classical mode for a

> smaller dimension (<2^32), and I can load it into paraview.However, for

> large problems I have to enable CDF-5.

>

> I am using paraview 4.3.1.

>

>                                                                                 _______________________________________________

> 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


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

From aka at alphanet.ch  Wed Jul  8 03:42:14 2015
From: aka at alphanet.ch (aka at alphanet.ch)
Date: Wed, 08 Jul 2015 09:42:14 +0200
Subject: [Paraview] Impossible to see a movement.
Message-ID: <20150708074214.ED383124F2D5@shakotay.alphanet.ch>

Hi, 

I am using Paraview with Salome-Meca + Code_Aster and I have e little 
problem : impossible to see the movement of a part that is moving. 

In fact the simulation is very simple : I have 2 cylinders, one is fixed by 
one face and the other have a movement on a face. The simulation converges 
and when I open the mmed or rmed file (result) with Paraview, impossible to 
see any movement even if I clic "play". 

Simply nothing happens. 

Can please someone help me ? 

Best regards, 

Amka

From canismajorwuff at gmail.com  Wed Jul  8 07:29:56 2015
From: canismajorwuff at gmail.com (Canis Major)
Date: Wed, 8 Jul 2015 13:29:56 +0200
Subject: [Paraview] Axis substitution filter
Message-ID: <CAC8evrENaKb=UXL4KhRn=x3XE8_ZKKeSUL4xYrJmGFREqq28pw@mail.gmail.com>

Hi,

I have a 2D geomtery and vector fields in Y-Z axis, is there a filter, or
smth what can help me switch them into X-Y?

With Best Regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150708/53cc9d6e/attachment.html>

From cory.quammen at kitware.com  Wed Jul  8 08:07:29 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 8 Jul 2015 07:07:29 -0500
Subject: [Paraview] Axis substitution filter
In-Reply-To: <CAC8evrENaKb=UXL4KhRn=x3XE8_ZKKeSUL4xYrJmGFREqq28pw@mail.gmail.com>
References: <CAC8evrENaKb=UXL4KhRn=x3XE8_ZKKeSUL4xYrJmGFREqq28pw@mail.gmail.com>
Message-ID: <CAB5Fpx7nLOq8RT22WuEOecfFqvdEFE1zCmbiCeYVUZp8p97Jhw@mail.gmail.com>

If your vector field name is "v", then you should be able to use the
Calculator filter with the expression

(v_Y*iHat) + (v_X*jHat)

The result will be an array with three elements, but that shouldn't be a
problem.

HTH,
Cory

On Wed, Jul 8, 2015 at 6:29 AM, Canis Major <canismajorwuff at gmail.com>
wrote:

> Hi,
>
> I have a 2D geomtery and vector fields in Y-Z axis, is there a filter, or
> smth what can help me switch them into X-Y?
>
> With Best Regards,
>
> _______________________________________________
> 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
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150708/d316c204/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Jul  8 09:44:45 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 08 Jul 2015 13:44:45 +0000
Subject: [Paraview] Impossible to see a movement.
In-Reply-To: <20150708074214.ED383124F2D5@shakotay.alphanet.ch>
References: <20150708074214.ED383124F2D5@shakotay.alphanet.ch>
Message-ID: <CADHSJjBqUBn7yScdubZkM1v4+WWi3AwegXyjuTJFuT9LjN22XA@mail.gmail.com>

Do you have a sample dataset to share? That'll make this easier.

Typically, movement comes from one of the following:
1. Readers: the reader itself translates the points in the grid as time
changes
2. Filters: if the grid doesn't change but has attributes that indicate the
displacement, one can apply a filter to transform the grid using those
displacement vectors.

Utkarsh

On Wed, Jul 8, 2015 at 3:59 AM <aka at alphanet.ch> wrote:

> Hi,
>
> I am using Paraview with Salome-Meca + Code_Aster and I have e little
> problem : impossible to see the movement of a part that is moving.
>
> In fact the simulation is very simple : I have 2 cylinders, one is fixed by
> one face and the other have a movement on a face. The simulation converges
> and when I open the mmed or rmed file (result) with Paraview, impossible to
> see any movement even if I clic "play".
>
> Simply nothing happens.
>
> Can please someone help me ?
>
> Best regards,
>
> Amka
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150708/95fd37c7/attachment.html>

From krishnapai09 at gmail.com  Wed Jul  8 14:25:13 2015
From: krishnapai09 at gmail.com (Krishna Pai)
Date: Wed, 8 Jul 2015 14:25:13 -0400
Subject: [Paraview] How does ParaView handle local rendering of geometry
	computed remotely?
Message-ID: <CAPHwKk4MQ712ohKjL6avaZ27sYKzk-scHZRVOfn6FLJP_fSqtg@mail.gmail.com>

Dear all:


How does ParaView handle local rendering of geometry computed remotely? In
other words, once an object has been rendered locally, and I start rotating
it with my mouse, am I manipulating a locally stored copy of the object,
and, if so, will that copy change only when I change the object?s
properties (by adding a filter, changing its coloring, etc.)?


I noticed that ParaView would freeze when I applied filters to my data set,
but would rotate smoothly once the filters had been applied.


Regards,

Krishna
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150708/14ad0a06/attachment.html>

From dave.demarle at kitware.com  Wed Jul  8 14:30:23 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Wed, 8 Jul 2015 14:30:23 -0400
Subject: [Paraview] How does ParaView handle local rendering of geometry
 computed remotely?
In-Reply-To: <CAPHwKk4MQ712ohKjL6avaZ27sYKzk-scHZRVOfn6FLJP_fSqtg@mail.gmail.com>
References: <CAPHwKk4MQ712ohKjL6avaZ27sYKzk-scHZRVOfn6FLJP_fSqtg@mail.gmail.com>
Message-ID: <CANjZAi8LT4SjW-o+NHODe9ow9az-Ma217dCPFX+4Cm0xnbE01Q@mail.gmail.com>

Yes, if the surface mesh is smaller than the limit set in your preferences,
the rendering infrastructure sends them from the root node of the server to
the client. Until something changes that mesh, the client takes over
rendering. Once the pipeline changes, then the server has generate a new
mesh and send it over the wire.



David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Wed, Jul 8, 2015 at 2:25 PM, Krishna Pai <krishnapai09 at gmail.com> wrote:

> Dear all:
>
>
> How does ParaView handle local rendering of geometry computed remotely? In
> other words, once an object has been rendered locally, and I start rotating
> it with my mouse, am I manipulating a locally stored copy of the object,
> and, if so, will that copy change only when I change the object?s
> properties (by adding a filter, changing its coloring, etc.)?
>
>
> I noticed that ParaView would freeze when I applied filters to my data
> set, but would rotate smoothly once the filters had been applied.
>
>
> Regards,
>
> Krishna
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150708/bac6e9cd/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Jul  8 16:47:47 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 08 Jul 2015 20:47:47 +0000
Subject: [Paraview] Impossible to see a movement.
In-Reply-To: <559D7FFA.5030301@alphanet.ch>
References: <20150708074214.ED383124F2D5@shakotay.alphanet.ch>
 <CADHSJjBqUBn7yScdubZkM1v4+WWi3AwegXyjuTJFuT9LjN22XA@mail.gmail.com>
 <559D7FFA.5030301@alphanet.ch>
Message-ID: <CADHSJjC+cznjPdcX18140ZPEU4wqaiS8J_WF+-=4QTLFuv1aTg@mail.gmail.com>

Amel,

The dataset didn't come through, I am afraid. Is it may be easier to upload
it somewhere eg. dropbox/google drive?

Utkarsh

On Wed, Jul 8, 2015 at 3:54 PM A. Kapetanovic <aka at alphanet.ch> wrote:

> WARNING: this mail was modified in transit:
>    defanged (renamed/protected) 07.hdf because file type unknown. Rename
> defang-0.binary to 07.hdf if you want to access the file anyway
>
> More details at:
>    http://www.alphanet.ch/alphanet/anti-spam.html
> Hi,
>
> Thanks for your reply.
>
> Of course I have data to share. The rmed result comressed file is too
> big (35 MB), so I send here the hdf and comm files, you only need to
> compute the (3) meshes and to run the simulation to have this rmed file.
>
> Say me if you need something else, I hope all is clear enough like this
>  :)
>
> Amel
>
>
> Le 08. 07. 15 15:44, Utkarsh Ayachit a ?crit :
> > Do you have a sample dataset to share? That'll make this easier.
> >
> > Typically, movement comes from one of the following:
> > 1. Readers: the reader itself translates the points in the grid as time
> > changes
> > 2. Filters: if the grid doesn't change but has attributes that indicate
> > the displacement, one can apply a filter to transform the grid using
> > those displacement vectors.
> >
> > Utkarsh
> >
> > On Wed, Jul 8, 2015 at 3:59 AM <aka at alphanet.ch
> > <mailto:aka at alphanet.ch>> wrote:
> >
> >     Hi,
> >
> >     I am using Paraview with Salome-Meca + Code_Aster and I have e little
> >     problem : impossible to see the movement of a part that is moving.
> >
> >     In fact the simulation is very simple : I have 2 cylinders, one is
> >     fixed by
> >     one face and the other have a movement on a face. The simulation
> >     converges
> >     and when I open the mmed or rmed file (result) with Paraview,
> >     impossible to
> >     see any movement even if I clic "play".
> >
> >     Simply nothing happens.
> >
> >     Can please someone help me ?
> >
> >     Best regards,
> >
> >     Amka
> >     _______________________________________________
> >     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
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150708/519a6dad/attachment.html>

From mosha at ntu.edu.sg  Wed Jul  8 23:05:35 2015
From: mosha at ntu.edu.sg (Sha Mo)
Date: Thu, 9 Jul 2015 03:05:35 +0000
Subject: [Paraview] How to use multiprocessing in pvpython?
Message-ID: <C8ADB5AB-4EDB-46A8-A8B5-FC0933C3E316@ntu.edu.sg>

In order to use multi-core cpu well, I want to use multiprocessing module in paraview python script. But following error was occurred when I try to run following code on Paraview Python Shell:

import multiprocessing
pool = multiprocessing.Pool(processes=4)

paraview version 4.3.1
Process PoolWorker-1:
Traceback (most recent call last):
Process PoolWorker-2:
paraview: Fatal IO error 2 (No such file or directory) on X server :0.
  File "/usr/lib/python2.7/multiprocessing/process.py", line 249, in _bootstrap
Process PoolWorker-3:
paraview: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
paraview: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Process PoolWorker-4:
paraview: Fatal IO error 2 (No such file or directory) on X server :0.
Process PoolWorker-5:
paraview: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Process PoolWorker-6:
paraview: Fatal IO error 2 (No such file or directory) on X server :0.
Process PoolWorker-8:
Process PoolWorker-7:
paraview: Fatal IO error 2 (No such file or directory) on X server :0.
paraview: Fatal IO error 2 (No such file or directory) on X server :0.
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
paraview: ../../src/xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted (core dumped)

I wonder whether it is wrong way to use parallel programming on pvpython?
[SG50]
________________________________
CONFIDENTIALITY: This email is intended solely for the person(s) named and may be confidential and/or privileged. If you are not the intended recipient, please delete it, notify us and do not copy, use, or disclose its contents.
Towards a sustainable earth: Print only when necessary. Thank you.

From cory.quammen at kitware.com  Wed Jul  8 23:52:59 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 8 Jul 2015 22:52:59 -0500
Subject: [Paraview] How to use multiprocessing in pvpython?
In-Reply-To: <C8ADB5AB-4EDB-46A8-A8B5-FC0933C3E316@ntu.edu.sg>
References: <C8ADB5AB-4EDB-46A8-A8B5-FC0933C3E316@ntu.edu.sg>
Message-ID: <CAB5Fpx5Ym5t+fB=ktRxOYhubyoPNYhwpy1qogUB4VkZF0tMR-Q@mail.gmail.com>

It looks like all threads are attempting to open a display on an xserver
but Xlib has not been initialized to use multiple threads.

Interestingly, I can execute your code in my development build of pvpython
just fine under Ubuntu 14.04.

May I ask what you are planning to do with the multiprocessing package?
Maybe there is another way you can accomplish it without the
multiprocessing package?

- Cory

On Wed, Jul 8, 2015 at 10:05 PM, Sha Mo <mosha at ntu.edu.sg> wrote:

> In order to use multi-core cpu well, I want to use multiprocessing module
> in paraview python script. But following error was occurred when I try to
> run following code on Paraview Python Shell:
>
> import multiprocessing
> pool = multiprocessing.Pool(processes=4)
>
> paraview version 4.3.1
> Process PoolWorker-1:
> Traceback (most recent call last):
> Process PoolWorker-2:
> paraview: Fatal IO error 2 (No such file or directory) on X server :0.
>   File "/usr/lib/python2.7/multiprocessing/process.py", line 249, in
> _bootstrap
> Process PoolWorker-3:
> paraview: Fatal IO error 11 (Resource temporarily unavailable) on X server
> :0.
> paraview: Fatal IO error 11 (Resource temporarily unavailable) on X server
> :0.
> Process PoolWorker-4:
> paraview: Fatal IO error 2 (No such file or directory) on X server :0.
> Process PoolWorker-5:
> paraview: Fatal IO error 11 (Resource temporarily unavailable) on X server
> :0.
> Process PoolWorker-6:
> paraview: Fatal IO error 2 (No such file or directory) on X server :0.
> Process PoolWorker-8:
> Process PoolWorker-7:
> paraview: Fatal IO error 2 (No such file or directory) on X server :0.
> paraview: Fatal IO error 2 (No such file or directory) on X server :0.
> [xcb] Unknown sequence number while processing queue
> [xcb] Most likely this is a multi-threaded client and XInitThreads has not
> been called
> [xcb] Aborting, sorry about that.
> paraview: ../../src/xcb_io.c:274: poll_for_event: Assertion
> `!xcb_xlib_threads_sequence_lost' failed.
> Aborted (core dumped)
>
> I wonder whether it is wrong way to use parallel programming on pvpython?
> [SG50]
> ________________________________
> CONFIDENTIALITY: This email is intended solely for the person(s) named and
> may be confidential and/or privileged. If you are not the intended
> recipient, please delete it, notify us and do not copy, use, or disclose
> its contents.
> Towards a sustainable earth: Print only when necessary. Thank you.
> _______________________________________________
> 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
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150708/cade4a67/attachment.html>

From mosha at ntu.edu.sg  Thu Jul  9 00:07:38 2015
From: mosha at ntu.edu.sg (Sha Mo)
Date: Thu, 9 Jul 2015 04:07:38 +0000
Subject: [Paraview] How to use multiprocessing in pvpython?
In-Reply-To: <CAB5Fpx5Ym5t+fB=ktRxOYhubyoPNYhwpy1qogUB4VkZF0tMR-Q@mail.gmail.com>
References: <C8ADB5AB-4EDB-46A8-A8B5-FC0933C3E316@ntu.edu.sg>
 <CAB5Fpx5Ym5t+fB=ktRxOYhubyoPNYhwpy1qogUB4VkZF0tMR-Q@mail.gmail.com>
Message-ID: <0030FB7B-4DF6-4893-89A1-606AAB23A90B@ntu.edu.sg>

Thanks Cory for your reply.

My developing environment is Ubuntu 14.04 + Paraview 4.3.
This issue will occur when I run those code in both Paraview Python Shell under GUI and pvpython command line.

I am attempting to implement a python script filter to handle my CFD in paraview pipeline, and my machine has multi-core cpu, meanwhile the filter has large part of separated calculation. So I think I can separate them into parts and use multi-processing to handle them.

For now, my script just use one core cpu, it?s slow and wasted.

Thank you.


? 2015?7?9????11:52?Cory Quammen <cory.quammen at kitware.com<mailto:cory.quammen at kitware.com>> ???

It looks like all threads are attempting to open a display on an xserver but Xlib has not been initialized to use multiple threads.

Interestingly, I can execute your code in my development build of pvpython just fine under Ubuntu 14.04.

May I ask what you are planning to do with the multiprocessing package? Maybe there is another way you can accomplish it without the multiprocessing package?

- Cory

On Wed, Jul 8, 2015 at 10:05 PM, Sha Mo <mosha at ntu.edu.sg<mailto:mosha at ntu.edu.sg>> wrote:
In order to use multi-core cpu well, I want to use multiprocessing module in paraview python script. But following error was occurred when I try to run following code on Paraview Python Shell:

import multiprocessing
pool = multiprocessing.Pool(processes=4)

paraview version 4.3.1
Process PoolWorker-1:
Traceback (most recent call last):
Process PoolWorker-2:
paraview: Fatal IO error 2 (No such file or directory) on X server :0.
  File "/usr/lib/python2.7/multiprocessing/process.py", line 249, in _bootstrap
Process PoolWorker-3:
paraview: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
paraview: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Process PoolWorker-4:
paraview: Fatal IO error 2 (No such file or directory) on X server :0.
Process PoolWorker-5:
paraview: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Process PoolWorker-6:
paraview: Fatal IO error 2 (No such file or directory) on X server :0.
Process PoolWorker-8:
Process PoolWorker-7:
paraview: Fatal IO error 2 (No such file or directory) on X server :0.
paraview: Fatal IO error 2 (No such file or directory) on X server :0.
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
paraview: ../../src/xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted (core dumped)

I wonder whether it is wrong way to use parallel programming on pvpython?
[SG50]
________________________________
CONFIDENTIALITY: This email is intended solely for the person(s) named and may be confidential and/or privileged. If you are not the intended recipient, please delete it, notify us and do not copy, use, or disclose its contents.
Towards a sustainable earth: Print only when necessary. Thank you.
_______________________________________________
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



--
Cory Quammen
R&D Engineer
Kitware, Inc.

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

From aka at alphanet.ch  Thu Jul  9 00:19:00 2015
From: aka at alphanet.ch (A. Kapetanovic)
Date: Thu, 09 Jul 2015 06:19:00 +0200
Subject: [Paraview] Impossible to see a movement.
In-Reply-To: <CADHSJjC+cznjPdcX18140ZPEU4wqaiS8J_WF+-=4QTLFuv1aTg@mail.gmail.com>
References: <20150708074214.ED383124F2D5@shakotay.alphanet.ch>
 <CADHSJjBqUBn7yScdubZkM1v4+WWi3AwegXyjuTJFuT9LjN22XA@mail.gmail.com>
 <559D7FFA.5030301@alphanet.ch>
 <CADHSJjC+cznjPdcX18140ZPEU4wqaiS8J_WF+-=4QTLFuv1aTg@mail.gmail.com>
Message-ID: <559DF634.5090807@alphanet.ch>

Utkarsh,

I did something on google drive, I shared the file with your e-mail and 
here you have the url :

https://drive.google.com/open?id=0B_ag1ge2Wc1nSS10M1JYampTb00

I hope all is OK like this, it's the first time I use google drive. Say 
me please if something misses.

Regards   :)


Le 08. 07. 15 22:47, Utkarsh Ayachit a ?crit :
> Amel,
>
> The dataset didn't come through, I am afraid. Is it may be easier to
> upload it somewhere eg. dropbox/google drive?
>
> Utkarsh
>
> On Wed, Jul 8, 2015 at 3:54 PM A. Kapetanovic <aka at alphanet.ch
> <mailto:aka at alphanet.ch>> wrote:
>
>     WARNING: this mail was modified in transit:
>         defanged (renamed/protected) 07.hdf because file type unknown.
>     Rename defang-0.binary to 07.hdf if you want to access the file anyway
>
>     More details at:
>     http://www.alphanet.ch/alphanet/anti-spam.html
>     Hi,
>
>     Thanks for your reply.
>
>     Of course I have data to share. The rmed result comressed file is too
>     big (35 MB), so I send here the hdf and comm files, you only need to
>     compute the (3) meshes and to run the simulation to have this rmed file.
>
>     Say me if you need something else, I hope all is clear enough like
>     this   :)
>
>     Amel
>
>
>     Le 08. 07. 15 15:44, Utkarsh Ayachit a ?crit :
>      > Do you have a sample dataset to share? That'll make this easier.
>      >
>      > Typically, movement comes from one of the following:
>      > 1. Readers: the reader itself translates the points in the grid
>     as time
>      > changes
>      > 2. Filters: if the grid doesn't change but has attributes that
>     indicate
>      > the displacement, one can apply a filter to transform the grid using
>      > those displacement vectors.
>      >
>      > Utkarsh
>      >
>      > On Wed, Jul 8, 2015 at 3:59 AM <aka at alphanet.ch
>     <mailto:aka at alphanet.ch>
>      > <mailto:aka at alphanet.ch <mailto:aka at alphanet.ch>>> wrote:
>      >
>      >     Hi,
>      >
>      >     I am using Paraview with Salome-Meca + Code_Aster and I have
>     e little
>      >     problem : impossible to see the movement of a part that is
>     moving.
>      >
>      >     In fact the simulation is very simple : I have 2 cylinders,
>     one is
>      >     fixed by
>      >     one face and the other have a movement on a face. The simulation
>      >     converges
>      >     and when I open the mmed or rmed file (result) with Paraview,
>      >     impossible to
>      >     see any movement even if I clic "play".
>      >
>      >     Simply nothing happens.
>      >
>      >     Can please someone help me ?
>      >
>      >     Best regards,
>      >
>      >     Amka
>      >     _______________________________________________
>      >     Powered by www.kitware.com <http://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
>      >
>

From aymeric.naze at gmail.com  Thu Jul  9 08:26:24 2015
From: aymeric.naze at gmail.com (Aymeric NAZE)
Date: Thu, 9 Jul 2015 14:26:24 +0200
Subject: [Paraview] Orient created vectors
Message-ID: <CAM4K3YdAJ+XvjbShzT3uJL3ntYwwitjUPdryzrx5pZUOGEa4LQ@mail.gmail.com>

Hello,

I'm using Paraview 4.3.1 (64-bit) to display data from a tecplot format
file.

Data is points coordinates (x,y,z) and vectors coordinates (u,v,w) for each
point.


   - I have created vectors with "Calculator" filter (Result =
   u*iHat+v*jHat+w*kHat) and it creates vectors with thewanted coordinates (I
   can see that in the spreadsheet view)


   - Then I made a glyph to display these vectors as arrows.

Magnitude is displayed without problem but i did'nt find how to orient
correctly the vectors.
Whether i check or not the "Orient" feature it doesn't change anything :
vectors are always oriented along the x axis...

Does anybody can help me on that issue ?

Thanks so much in advance.

Regards,

Aymeric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/7d737e72/attachment.html>

From cory.quammen at kitware.com  Thu Jul  9 08:29:06 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 9 Jul 2015 07:29:06 -0500
Subject: [Paraview] Orient created vectors
In-Reply-To: <CAM4K3YdAJ+XvjbShzT3uJL3ntYwwitjUPdryzrx5pZUOGEa4LQ@mail.gmail.com>
References: <CAM4K3YdAJ+XvjbShzT3uJL3ntYwwitjUPdryzrx5pZUOGEa4LQ@mail.gmail.com>
Message-ID: <CAB5Fpx5ZZb2UQP86on6-YT+Mqx6DfUc3j6K0deo8nTOaY2iHAg@mail.gmail.com>

Hi Aymeric,

Did you choose the "Result" array as the "Vectors" property in the
Properties panel of the Glyph filter?

HTH,
Cory

On Thu, Jul 9, 2015 at 7:26 AM, Aymeric NAZE <aymeric.naze at gmail.com> wrote:

> Hello,
>
> I'm using Paraview 4.3.1 (64-bit) to display data from a tecplot format
> file.
>
> Data is points coordinates (x,y,z) and vectors coordinates (u,v,w) for
> each point.
>
>
>    - I have created vectors with "Calculator" filter (Result =
>    u*iHat+v*jHat+w*kHat) and it creates vectors with thewanted coordinates (I
>    can see that in the spreadsheet view)
>
>
>    - Then I made a glyph to display these vectors as arrows.
>
> Magnitude is displayed without problem but i did'nt find how to orient
> correctly the vectors.
> Whether i check or not the "Orient" feature it doesn't change anything :
> vectors are always oriented along the x axis...
>
> Does anybody can help me on that issue ?
>
> Thanks so much in advance.
>
> Regards,
>
> Aymeric
>
> _______________________________________________
> 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
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/0bcb95b0/attachment.html>

From cory.quammen at kitware.com  Thu Jul  9 08:54:39 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 9 Jul 2015 07:54:39 -0500
Subject: [Paraview] How to use multiprocessing in pvpython?
In-Reply-To: <0030FB7B-4DF6-4893-89A1-606AAB23A90B@ntu.edu.sg>
References: <C8ADB5AB-4EDB-46A8-A8B5-FC0933C3E316@ntu.edu.sg>
 <CAB5Fpx5Ym5t+fB=ktRxOYhubyoPNYhwpy1qogUB4VkZF0tMR-Q@mail.gmail.com>
 <0030FB7B-4DF6-4893-89A1-606AAB23A90B@ntu.edu.sg>
Message-ID: <CAB5Fpx6Tk9KC4LeWp=0T+Boh9LWh4NCCX8Lw8m4Dq6j81zFzxg@mail.gmail.com>

I see. Thanks for explaining what you are working on. Unfortunately, I
don't have an answer for you on how to make it work.

Perhaps you could work around this problem by creating a subprocess with
another plain Python console in your ParaView Python script where you
execute your CFD code with the multiprocessing package in the subprocess
and then read the data in your ParaView pipeline after that process is
complete?

Cory

On Wed, Jul 8, 2015 at 11:07 PM, Sha Mo <mosha at ntu.edu.sg> wrote:

>  Thanks Cory for your reply.
>
>  My developing environment is Ubuntu 14.04 + Paraview 4.3.
> This issue will occur when I run those code in both Paraview Python Shell
> under GUI and pvpython command line.
>
>  I am attempting to implement a python script filter to handle my CFD in
> paraview pipeline, and my machine has multi-core cpu, meanwhile the filter
> has large part of separated calculation. So I think I can separate them
> into parts and use multi-processing to handle them.
>
>  For now, my script just use one core cpu, it?s slow and wasted.
>
>  Thank you.
>
>
>  ? 2015?7?9????11:52?Cory Quammen <cory.quammen at kitware.com> ???
>
>  It looks like all threads are attempting to open a display on an xserver
> but Xlib has not been initialized to use multiple threads.
>
>  Interestingly, I can execute your code in my development build of
> pvpython just fine under Ubuntu 14.04.
>
>  May I ask what you are planning to do with the multiprocessing package?
> Maybe there is another way you can accomplish it without the
> multiprocessing package?
>
>  - Cory
>
> On Wed, Jul 8, 2015 at 10:05 PM, Sha Mo <mosha at ntu.edu.sg> wrote:
>
>> In order to use multi-core cpu well, I want to use multiprocessing module
>> in paraview python script. But following error was occurred when I try to
>> run following code on Paraview Python Shell:
>>
>> import multiprocessing
>> pool = multiprocessing.Pool(processes=4)
>>
>> paraview version 4.3.1
>> Process PoolWorker-1:
>> Traceback (most recent call last):
>> Process PoolWorker-2:
>> paraview: Fatal IO error 2 (No such file or directory) on X server :0.
>>   File "/usr/lib/python2.7/multiprocessing/process.py", line 249, in
>> _bootstrap
>> Process PoolWorker-3:
>> paraview: Fatal IO error 11 (Resource temporarily unavailable) on X
>> server :0.
>> paraview: Fatal IO error 11 (Resource temporarily unavailable) on X
>> server :0.
>> Process PoolWorker-4:
>> paraview: Fatal IO error 2 (No such file or directory) on X server :0.
>> Process PoolWorker-5:
>> paraview: Fatal IO error 11 (Resource temporarily unavailable) on X
>> server :0.
>> Process PoolWorker-6:
>> paraview: Fatal IO error 2 (No such file or directory) on X server :0.
>> Process PoolWorker-8:
>> Process PoolWorker-7:
>> paraview: Fatal IO error 2 (No such file or directory) on X server :0.
>> paraview: Fatal IO error 2 (No such file or directory) on X server :0.
>> [xcb] Unknown sequence number while processing queue
>> [xcb] Most likely this is a multi-threaded client and XInitThreads has
>> not been called
>> [xcb] Aborting, sorry about that.
>> paraview: ../../src/xcb_io.c:274: poll_for_event: Assertion
>> `!xcb_xlib_threads_sequence_lost' failed.
>> Aborted (core dumped)
>>
>> I wonder whether it is wrong way to use parallel programming on pvpython?
>> [SG50]
>> ________________________________
>> CONFIDENTIALITY: This email is intended solely for the person(s) named
>> and may be confidential and/or privileged. If you are not the intended
>> recipient, please delete it, notify us and do not copy, use, or disclose
>> its contents.
>> Towards a sustainable earth: Print only when necessary. Thank you.
>> _______________________________________________
>> 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
>>
>
>
>
>  --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/59575bad/attachment.html>

From aymeric.naze at gmail.com  Thu Jul  9 08:56:34 2015
From: aymeric.naze at gmail.com (Aymeric NAZE)
Date: Thu, 9 Jul 2015 14:56:34 +0200
Subject: [Paraview] Orient created vectors
In-Reply-To: <CAB5Fpx5ZZb2UQP86on6-YT+Mqx6DfUc3j6K0deo8nTOaY2iHAg@mail.gmail.com>
References: <CAM4K3YdAJ+XvjbShzT3uJL3ntYwwitjUPdryzrx5pZUOGEa4LQ@mail.gmail.com>
 <CAB5Fpx5ZZb2UQP86on6-YT+Mqx6DfUc3j6K0deo8nTOaY2iHAg@mail.gmail.com>
Message-ID: <CAM4K3YeSBB+eavXBKA+jUPzTdfASeM-pWRNkOqnBbdD6NcbGow@mail.gmail.com>

Hello,

Thanks for considering my problem.

Yes, in the Glyph Filter I have the following *Active Attributes* :

   - *Scalars *: FF wich is the magnitude in the (x,y) plane (calculated
   with another "calculator" filter : FF=(U^2+V^2)^0.5) : it's the length of
   the arrows I want to display.


   - *Vectors *: Result (vectors from the previously described calculator)


2015-07-09 14:29 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:

> Hi Aymeric,
>
> Did you choose the "Result" array as the "Vectors" property in the
> Properties panel of the Glyph filter?
>
> HTH,
> Cory
>
> On Thu, Jul 9, 2015 at 7:26 AM, Aymeric NAZE <aymeric.naze at gmail.com>
> wrote:
>
>> Hello,
>>
>> I'm using Paraview 4.3.1 (64-bit) to display data from a tecplot format
>> file.
>>
>> Data is points coordinates (x,y,z) and vectors coordinates (u,v,w) for
>> each point.
>>
>>
>>    - I have created vectors with "Calculator" filter (Result =
>>    u*iHat+v*jHat+w*kHat) and it creates vectors with thewanted coordinates (I
>>    can see that in the spreadsheet view)
>>
>>
>>    - Then I made a glyph to display these vectors as arrows.
>>
>> Magnitude is displayed without problem but i did'nt find how to orient
>> correctly the vectors.
>> Whether i check or not the "Orient" feature it doesn't change anything :
>> vectors are always oriented along the x axis...
>>
>> Does anybody can help me on that issue ?
>>
>> Thanks so much in advance.
>>
>> Regards,
>>
>> Aymeric
>>
>> _______________________________________________
>> 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
>>
>>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/e58c1fe5/attachment.html>

From cory.quammen at kitware.com  Thu Jul  9 09:03:39 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 9 Jul 2015 08:03:39 -0500
Subject: [Paraview] Orient created vectors
In-Reply-To: <CAM4K3YeSBB+eavXBKA+jUPzTdfASeM-pWRNkOqnBbdD6NcbGow@mail.gmail.com>
References: <CAM4K3YdAJ+XvjbShzT3uJL3ntYwwitjUPdryzrx5pZUOGEa4LQ@mail.gmail.com>
 <CAB5Fpx5ZZb2UQP86on6-YT+Mqx6DfUc3j6K0deo8nTOaY2iHAg@mail.gmail.com>
 <CAM4K3YeSBB+eavXBKA+jUPzTdfASeM-pWRNkOqnBbdD6NcbGow@mail.gmail.com>
Message-ID: <CAB5Fpx49Pm4tnm_cduJspQXFLzA27R+WXgN8C5XABBsdY3hbfg@mail.gmail.com>

Can you verify that the second and third components of your Result vector
field have a range outside [0, 0]? You can get this information under the
Information tab in the Data Arrays table.

On Thu, Jul 9, 2015 at 7:56 AM, Aymeric NAZE <aymeric.naze at gmail.com> wrote:

> Hello,
>
> Thanks for considering my problem.
>
> Yes, in the Glyph Filter I have the following *Active Attributes* :
>
>    - *Scalars *: FF wich is the magnitude in the (x,y) plane (calculated
>    with another "calculator" filter : FF=(U^2+V^2)^0.5) : it's the length of
>    the arrows I want to display.
>
>
>    - *Vectors *: Result (vectors from the previously described calculator)
>
>
> 2015-07-09 14:29 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>
>> Hi Aymeric,
>>
>> Did you choose the "Result" array as the "Vectors" property in the
>> Properties panel of the Glyph filter?
>>
>> HTH,
>> Cory
>>
>> On Thu, Jul 9, 2015 at 7:26 AM, Aymeric NAZE <aymeric.naze at gmail.com>
>> wrote:
>>
>>> Hello,
>>>
>>> I'm using Paraview 4.3.1 (64-bit) to display data from a tecplot format
>>> file.
>>>
>>> Data is points coordinates (x,y,z) and vectors coordinates (u,v,w) for
>>> each point.
>>>
>>>
>>>    - I have created vectors with "Calculator" filter (Result =
>>>    u*iHat+v*jHat+w*kHat) and it creates vectors with thewanted coordinates (I
>>>    can see that in the spreadsheet view)
>>>
>>>
>>>    - Then I made a glyph to display these vectors as arrows.
>>>
>>> Magnitude is displayed without problem but i did'nt find how to orient
>>> correctly the vectors.
>>> Whether i check or not the "Orient" feature it doesn't change anything :
>>> vectors are always oriented along the x axis...
>>>
>>> Does anybody can help me on that issue ?
>>>
>>> Thanks so much in advance.
>>>
>>> Regards,
>>>
>>> Aymeric
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>>
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/072b92b5/attachment.html>

From eric.g.younkin at noaa.gov  Thu Jul  9 09:29:39 2015
From: eric.g.younkin at noaa.gov (Eric Younkin - NOAA Federal)
Date: Thu, 9 Jul 2015 09:29:39 -0400
Subject: [Paraview] PCL Plugin
Message-ID: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>

I am currently working on building the Paraview PCL Plugin as found here
<http://www.paraview.org/Wiki/ParaView/PCL_Plugin/Download_And_Build_Instructions>.
I was wondering if anyone has had any success building the plugin with PCL
versions later than 1.5.1.  The latest info I've found was several years
old.

Thanks.

-- 
Eric Younkin LTJG/NOAA
HSTP Liaison - East
Marine Operations Center - Atlantic
439 W York St
Norfolk, VA 23510
Cell: 828-331-8197
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/e2d3e1d0/attachment.html>

From aymeric.naze at gmail.com  Thu Jul  9 09:53:07 2015
From: aymeric.naze at gmail.com (Aymeric NAZE)
Date: Thu, 9 Jul 2015 15:53:07 +0200
Subject: [Paraview] Orient created vectors
In-Reply-To: <CAB5Fpx49Pm4tnm_cduJspQXFLzA27R+WXgN8C5XABBsdY3hbfg@mail.gmail.com>
References: <CAM4K3YdAJ+XvjbShzT3uJL3ntYwwitjUPdryzrx5pZUOGEa4LQ@mail.gmail.com>
 <CAB5Fpx5ZZb2UQP86on6-YT+Mqx6DfUc3j6K0deo8nTOaY2iHAg@mail.gmail.com>
 <CAM4K3YeSBB+eavXBKA+jUPzTdfASeM-pWRNkOqnBbdD6NcbGow@mail.gmail.com>
 <CAB5Fpx49Pm4tnm_cduJspQXFLzA27R+WXgN8C5XABBsdY3hbfg@mail.gmail.com>
Message-ID: <CAM4K3YcYe_Eo8jYVWVWuaU3mHssPa=DnSFBjdmK3eyh8tr0RQA@mail.gmail.com>

Information regarding my Result vector field in Data Arrays (under
"Information" tab in the calculator filter) :

   - *Data Type* : double
   - *Data Ranges* : [-1.26, 0.01], [-0.01, 0.76], [-0.16, 0.27]


2015-07-09 15:03 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:

> Can you verify that the second and third components of your Result vector
> field have a range outside [0, 0]? You can get this information under the
> Information tab in the Data Arrays table.
>
> On Thu, Jul 9, 2015 at 7:56 AM, Aymeric NAZE <aymeric.naze at gmail.com>
> wrote:
>
>> Hello,
>>
>> Thanks for considering my problem.
>>
>> Yes, in the Glyph Filter I have the following *Active Attributes* :
>>
>>    - *Scalars *: FF wich is the magnitude in the (x,y) plane (calculated
>>    with another "calculator" filter : FF=(U^2+V^2)^0.5) : it's the length of
>>    the arrows I want to display.
>>
>>
>>    - *Vectors *: Result (vectors from the previously described
>>    calculator)
>>
>>
>> 2015-07-09 14:29 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>>
>>> Hi Aymeric,
>>>
>>> Did you choose the "Result" array as the "Vectors" property in the
>>> Properties panel of the Glyph filter?
>>>
>>> HTH,
>>> Cory
>>>
>>> On Thu, Jul 9, 2015 at 7:26 AM, Aymeric NAZE <aymeric.naze at gmail.com>
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> I'm using Paraview 4.3.1 (64-bit) to display data from a tecplot format
>>>> file.
>>>>
>>>> Data is points coordinates (x,y,z) and vectors coordinates (u,v,w) for
>>>> each point.
>>>>
>>>>
>>>>    - I have created vectors with "Calculator" filter (Result =
>>>>    u*iHat+v*jHat+w*kHat) and it creates vectors with thewanted coordinates (I
>>>>    can see that in the spreadsheet view)
>>>>
>>>>
>>>>    - Then I made a glyph to display these vectors as arrows.
>>>>
>>>> Magnitude is displayed without problem but i did'nt find how to orient
>>>> correctly the vectors.
>>>> Whether i check or not the "Orient" feature it doesn't change anything
>>>> : vectors are always oriented along the x axis...
>>>>
>>>> Does anybody can help me on that issue ?
>>>>
>>>> Thanks so much in advance.
>>>>
>>>> Regards,
>>>>
>>>> Aymeric
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>>
>>>
>>> --
>>> Cory Quammen
>>> R&D Engineer
>>> Kitware, Inc.
>>>
>>
>>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/0a7c8ffa/attachment.html>

From berk.geveci at kitware.com  Thu Jul  9 10:02:12 2015
From: berk.geveci at kitware.com (Berk Geveci)
Date: Thu, 9 Jul 2015 10:02:12 -0400
Subject: [Paraview] Molecular dynamics from lammps
In-Reply-To: <1436279999.571994242@f345.i.mail.ru>
References: <1436279999.571994242@f345.i.mail.ru>
Message-ID: <CAE32kpXt3KL4L5h4qXiCpvqFfAev5N-QJ91nA8Z91uVS2zv3xA@mail.gmail.com>

Dear Oksana,

You do need to generate a volumetric mesh first and then slice it to
generate a polygonal mesh. The volumetric mesh needs to interpolate your
values in space somehow. This is what Delaunay would give you - it will
generate a mesh where each atom is a node of a tetrahedra and the values
are interpolated over the tets. Is the interpolation the cause of "which do
not represent my structure properly"? What do you expect the slice to look
like? Maybe you need to project the closest atoms to the slice instead of
interpolating?

Best,
-berk

On Tue, Jul 7, 2015 at 10:39 AM, Oksana <oksana_golovnya at mail.ru> wrote:

> Dear community,
>
> I am trying to visualize array of atoms with their displacement vectors in
> Paraview. The structure is complicated and cannot be represented by
> StructuredGrid. The goal is to have slices with surface vectors
> (displacement) and atoms. I have tried two ways:
>
> 1.       Generate a vtk file. In this case I have a polydata of points
> and vectors, but I cannot use SurfaceVectors filter in this dataset. I
> tried Delaunay3D filter to produce a grid, but it produces too many cells,
> which do not represent my structure properly, and instead of one vector per
> atom I have some strange distribution.
>
> 2.       Load lammps dump file. In this case after MergeBlocks and
> Calculator filters I have unstructured grid with points and vectors, but
> cannot use this vectors in Slice->SurfaceVector pipeline anyway.
> SurfaceVectors are inactive.
>
> I understand that in the first case I need to generate a grid with each
> atom inside one cell. However, I do not know how to do it. And in the
> second I do not understand why SurfaceVectors are inactive on the
> unstructured grid? I would appreciate any help, explanation or reference
> how to do it right.
>
> Thanks.
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/b12e97f2/attachment.html>

From cory.quammen at kitware.com  Thu Jul  9 10:12:16 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 9 Jul 2015 09:12:16 -0500
Subject: [Paraview] Orient created vectors
In-Reply-To: <CAM4K3YcYe_Eo8jYVWVWuaU3mHssPa=DnSFBjdmK3eyh8tr0RQA@mail.gmail.com>
References: <CAM4K3YdAJ+XvjbShzT3uJL3ntYwwitjUPdryzrx5pZUOGEa4LQ@mail.gmail.com>
 <CAB5Fpx5ZZb2UQP86on6-YT+Mqx6DfUc3j6K0deo8nTOaY2iHAg@mail.gmail.com>
 <CAM4K3YeSBB+eavXBKA+jUPzTdfASeM-pWRNkOqnBbdD6NcbGow@mail.gmail.com>
 <CAB5Fpx49Pm4tnm_cduJspQXFLzA27R+WXgN8C5XABBsdY3hbfg@mail.gmail.com>
 <CAM4K3YcYe_Eo8jYVWVWuaU3mHssPa=DnSFBjdmK3eyh8tr0RQA@mail.gmail.com>
Message-ID: <CAB5Fpx5Lgi-yQxwrp43S4goeO40x56P9pFU94OGKWSzN_i+fcw@mail.gmail.com>

Hmm, well it does indeed have non-zero Y and Z components. Could you share
this dataset?

Thanks,
Cory

On Thu, Jul 9, 2015 at 8:53 AM, Aymeric NAZE <aymeric.naze at gmail.com> wrote:

> Information regarding my Result vector field in Data Arrays (under
> "Information" tab in the calculator filter) :
>
>    - *Data Type* : double
>    - *Data Ranges* : [-1.26, 0.01], [-0.01, 0.76], [-0.16, 0.27]
>
>
> 2015-07-09 15:03 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>
>> Can you verify that the second and third components of your Result vector
>> field have a range outside [0, 0]? You can get this information under the
>> Information tab in the Data Arrays table.
>>
>> On Thu, Jul 9, 2015 at 7:56 AM, Aymeric NAZE <aymeric.naze at gmail.com>
>> wrote:
>>
>>> Hello,
>>>
>>> Thanks for considering my problem.
>>>
>>> Yes, in the Glyph Filter I have the following *Active Attributes* :
>>>
>>>    - *Scalars *: FF wich is the magnitude in the (x,y) plane
>>>    (calculated with another "calculator" filter : FF=(U^2+V^2)^0.5) : it's the
>>>    length of the arrows I want to display.
>>>
>>>
>>>    - *Vectors *: Result (vectors from the previously described
>>>    calculator)
>>>
>>>
>>> 2015-07-09 14:29 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>>>
>>>> Hi Aymeric,
>>>>
>>>> Did you choose the "Result" array as the "Vectors" property in the
>>>> Properties panel of the Glyph filter?
>>>>
>>>> HTH,
>>>> Cory
>>>>
>>>> On Thu, Jul 9, 2015 at 7:26 AM, Aymeric NAZE <aymeric.naze at gmail.com>
>>>> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I'm using Paraview 4.3.1 (64-bit) to display data from a tecplot
>>>>> format file.
>>>>>
>>>>> Data is points coordinates (x,y,z) and vectors coordinates (u,v,w) for
>>>>> each point.
>>>>>
>>>>>
>>>>>    - I have created vectors with "Calculator" filter (Result =
>>>>>    u*iHat+v*jHat+w*kHat) and it creates vectors with thewanted coordinates (I
>>>>>    can see that in the spreadsheet view)
>>>>>
>>>>>
>>>>>    - Then I made a glyph to display these vectors as arrows.
>>>>>
>>>>> Magnitude is displayed without problem but i did'nt find how to orient
>>>>> correctly the vectors.
>>>>> Whether i check or not the "Orient" feature it doesn't change anything
>>>>> : vectors are always oriented along the x axis...
>>>>>
>>>>> Does anybody can help me on that issue ?
>>>>>
>>>>> Thanks so much in advance.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Aymeric
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Cory Quammen
>>>> R&D Engineer
>>>> Kitware, Inc.
>>>>
>>>
>>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>>
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/b8696203/attachment.html>

From casey.goodlett at kitware.com  Thu Jul  9 10:39:51 2015
From: casey.goodlett at kitware.com (Casey Goodlett)
Date: Thu, 9 Jul 2015 10:39:51 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
Message-ID: <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>

Hi Eric,

Thanks for your interest in the PCL plugin, I have used the plugin more
recently than PCL 1.5.1.  I last tested with ParaView 4.1 and PCL master
(from around February of this year).  I have a few small patches to the
plugin, and I'll share those shortly.   What errors are you seeing in the
build?

What features of PCL are you interested in using in ParaView?  There are
binaries of ParaView/PCL built here if that helps.

http://www.kitware.com/blog/home/post/650

Best,

-- 
Casey B Goodlett, PhD
Technical Leader
Kitware, Inc. - North Carolina Office
http://www.kitware.com
(919) 969-6990 x310
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/81ec993e/attachment.html>

From eric.g.younkin at noaa.gov  Thu Jul  9 10:53:42 2015
From: eric.g.younkin at noaa.gov (Eric Younkin - NOAA Federal)
Date: Thu, 9 Jul 2015 10:53:42 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
Message-ID: <CAFe6qKgoBR7HU6MHCDTKr_HCxBGu_eU3St2D5+UjQ3zrBwqcbg@mail.gmail.com>

Casey,

I am mostly interested in the feature extraction routines and Paraview
integration with the Velodyne VLP-16.  I'd like to experiment with PCL
algorithms to try and pick out fixed objects such as buoys or piers from a
VLP-16 mounted on our research vessel as we travel up the coast.  I think
most of my errors are from attempting to build using Visual Studio 2013 pro
and older Qt/PCL versions.  If I can use the most recent versions, that
might help things.

The binaries you linked to here still require installation of Paraview and
PCL correct?

Thanks,
Eric

On Thu, Jul 9, 2015 at 10:39 AM, Casey Goodlett <casey.goodlett at kitware.com>
wrote:

> Hi Eric,
>
> Thanks for your interest in the PCL plugin, I have used the plugin more
> recently than PCL 1.5.1.  I last tested with ParaView 4.1 and PCL master
> (from around February of this year).  I have a few small patches to the
> plugin, and I'll share those shortly.   What errors are you seeing in the
> build?
>
> What features of PCL are you interested in using in ParaView?  There are
> binaries of ParaView/PCL built here if that helps.
>
> http://www.kitware.com/blog/home/post/650
>
> Best,
>
> --
> Casey B Goodlett, PhD
> Technical Leader
> Kitware, Inc. - North Carolina Office
> http://www.kitware.com
> (919) 969-6990 x310
>



-- 
Eric Younkin LTJG/NOAA
HSTP Liaison - East
Marine Operations Center - Atlantic
439 W York St
Norfolk, VA 23510
Cell: 828-331-8197
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/011e9623/attachment.html>

From cory.quammen at kitware.com  Thu Jul  9 11:00:54 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 9 Jul 2015 10:00:54 -0500
Subject: [Paraview] segfault playing a simulation
In-Reply-To: <559422EF.3070304@gmail.com>
References: <55895735.2030202@gmail.com>
 <CAB5Fpx4BDY+JDKBbA5Lt02Yt1RLaaZY6TPW9azpZsGf-aWTD7Q@mail.gmail.com>
 <559381DE.5030504@gmail.com>
 <CAB5Fpx6H7dY-j86vut03OuVr+7smd+1YwGqL2e771tRE0xdkxw@mail.gmail.com>
 <559422EF.3070304@gmail.com>
Message-ID: <CAB5Fpx7AdTrtGAsq9OjoW36=-dWFDzUAGrtCF+fqqa4hLenoDg@mail.gmail.com>

Hi Sergi,

I played with your data set a little but haven't found what is wrong. I am
suspicious of two things in the data file, the extent and the offset in the
second data array (it looks too small).

What are the dimensions of your grid? Note that the whole extent upper
values need to be the dimension - 1, e.g., for a 300x300x300 grid, the
whole extent should be 0 299 0 299 0 299.

Thanks,
Cory

On Wed, Jul 1, 2015 at 12:27 PM, Sergi Mateo Bellido <
sergi.mateo.bellido at gmail.com> wrote:

>  Hi Cory,
>
> Thanks for your time. These data files have been produced by a software
> that I'm developing with some colleagues.
>
> Best regards,
>
> Sergi
>
>
> On 07/01/2015 03:59 PM, Cory Quammen wrote:
>
> Sergi,
>
>  I can confirm the crash you are seeing in the same location in the code.
> I'm looking for the cause.
>
>  What software produced these data files?
>
>  Thanks,
> Cory
>
> On Wed, Jul 1, 2015 at 1:59 AM, Sergi Mateo Bellido <
> sergi.mateo.bellido at gmail.com> wrote:
>
>>  Hi Cory,
>>
>> Thanks for your answer. I reproduced the segfault in two different ways,
>> but it's always after loading a data set:
>> - After loading a data set, I tried to play the simulation ->segfault
>> - After loading a data set, I tried to filter some fields from the model
>> (Pointer array status). As soon as I clicked the 'apply' button, paraview
>> crashed with a segfault.
>>
>> Thanks,
>> Sergi
>>
>>
>>
>> On 06/30/2015 06:21 AM, Cory Quammen wrote:
>>
>> Hi Sergi,
>>
>>  Could you clarify when you are seeing this crash? Is it right when
>> starting ParaView or when first loading a data set?
>>
>>  Thanks,
>> Cory
>>
>> On Tue, Jun 23, 2015 at 8:55 AM, Sergi Mateo Bellido <
>> sergi.mateo.bellido at gmail.com> wrote:
>>
>>>  Hi,
>>>
>>> I'm trying to reproduce a simulation with ParaView 4.3.1 and it always
>>> crashes when I start it. You can find the backtrace below:
>>>
>>> =========================================================
>>> Process id 6681 Caught SIGSEGV at 0x925b124 address not mapped to object
>>> Program Stack:
>>> WARNING: The stack trace will not use advanced capabilities because this
>>> is a release build.
>>> 0x7f54ce081d40 : ??? [(???) ???:-1]
>>> 0x7f54ce19caf6 : ??? [(???) ???:-1]
>>> 0x7f54cb123736 : vtkXMLPStructuredDataReader::CopySubExtent(int*, int*,
>>> long long*, int*, int*, long long*, int*, int*, vtkDataArray*,
>>> vtkDataArray*) [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>> 0x7f54cb12389f :
>>> vtkXMLPStructuredDataReader::CopyArrayForPoints(vtkDataArray*,
>>> vtkDataArray*) [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>> 0x7f54cb11cc1f : vtkXMLPDataReader::ReadPieceData()
>>> [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>> 0x7f54cb11ca14 : vtkXMLPDataReader::ReadPieceData(int)
>>> [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>> 0x7f54cb124d7a : vtkXMLPStructuredDataReader::ReadXMLData()
>>> [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>> 0x7f54cb1280eb : vtkXMLReader::RequestData(vtkInformation*,
>>> vtkInformationVector**, vtkInformationVector*) [(libvtkIOXML-pv4.3.so.1)
>>> ???:-1]
>>> 0x7f54cb1273b6 : vtkXMLReader::ProcessRequest(vtkInformation*,
>>> vtkInformationVector**, vtkInformationVector*) [(libvtkIOXML-pv4.3.so.1)
>>> ???:-1]
>>> 0x7f54cd6200f9 : vtkFileSeriesReader::RequestData(vtkInformation*,
>>> vtkInformationVector**, vtkInformationVector*)
>>> [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1]
>>> 0x7f54cd61f07f : vtkFileSeriesReader::ProcessRequest(vtkInformation*,
>>> vtkInformationVector**, vtkInformationVector*)
>>> [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1]
>>> 0x7f54d2706204 : vtkExecutive::CallAlgorithm(vtkInformation*, int,
>>> vtkInformationVector**, vtkInformationVector*)
>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>> 0x7f54d27016cc : vtkDemandDrivenPipeline::ExecuteData(vtkInformation*,
>>> vtkInformationVector**, vtkInformationVector*)
>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>> 0x7f54d2700201 : vtkCompositeDataPipeline::ExecuteData(vtkInformation*,
>>> vtkInformationVector**, vtkInformationVector*)
>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>> 0x7f54d2704067 :
>>> vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>> vtkInformationVector**, vtkInformationVector*)
>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>> 0x7f54d271d959 :
>>> vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>> vtkInformationVector**, vtkInformationVector*)
>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>> 0x7f54d26fe387 :
>>> vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*)
>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>> 0x7f54d2704010 :
>>> vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>> vtkInformationVector**, vtkInformationVector*)
>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>> 0x7f54d271d959 :
>>> vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>> vtkInformationVector**, vtkInformationVector*)
>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>> 0x7f54d26fe387 :
>>> vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*)
>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>> 0x7f54d2704010 :
>>> vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>> vtkInformationVector**, vtkInformationVector*)
>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>> 0x7f54d271d959 :
>>> vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>> vtkInformationVector**, vtkInformationVector*)
>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>> 0x7f54d27035ae : vtkDemandDrivenPipeline::UpdateData(int)
>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>> 0x7f54d271e87f : vtkStreamingDemandDrivenPipeline::Update(int)
>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>> 0x7f54cd98fa7f :
>>> vtkPVDataRepresentation::ProcessViewRequest(vtkInformationRequestKey*,
>>> vtkInformation*, vtkInformation*)
>>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>> 0x7f54cd973d79 :
>>> vtkGeometryRepresentation::ProcessViewRequest(vtkInformationRequestKey*,
>>> vtkInformation*, vtkInformation*)
>>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>> 0x7f54cd975d71 :
>>> vtkGeometryRepresentationWithFaces::ProcessViewRequest(vtkInformationRequestKey*,
>>> vtkInformation*, vtkInformation*)
>>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>> 0x7f54cd9bd388 :
>>> vtkPVView::CallProcessViewRequest(vtkInformationRequestKey*,
>>> vtkInformation*, vtkInformationVector*)
>>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>> 0x7f54cd9bd552 : vtkPVView::Update()
>>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>> 0x7f54cd9acb78 : vtkPVRenderView::Update()
>>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>> 0x7f54d780ac30 : vtkPVRenderViewCommand(vtkClientServerInterpreter*,
>>> vtkObjectBase*, char const*, vtkClientServerStream const&,
>>> vtkClientServerStream&, void*)
>>> [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1]
>>> 0x7f54d4e135e0 : vtkClientServerInterpreter::CallCommandFunction(char
>>> const*, vtkObjectBase*, char const*, vtkClientServerStream const&,
>>> vtkClientServerStream&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>> 0x7f54d4e18393 :
>>> vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream
>>> const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>> 0x7f54d4e16832 :
>>> vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&,
>>> int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>> 0x7f54d4e16ced :
>>> vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&)
>>> [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>> 0x7f54d5b26cec :
>>> vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool)
>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>> 0x7f54d5b26958 : vtkPVSessionCore::ExecuteStream(unsigned int,
>>> vtkClientServerStream const&, bool)
>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>> 0x7f54d5b25203 : vtkPVSessionBase::ExecuteStream(unsigned int,
>>> vtkClientServerStream const&, bool)
>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>> 0x7f54cdcae44f : vtkSMViewProxy::Update()
>>> [(libvtkPVServerManagerRendering-pv4.3.so.1) ???:-1]
>>> 0x7f54cdf2f6f7 : vtkSMAnimationScene::TickInternal(double, double,
>>> double) [(libvtkPVAnimation-pv4.3.so.1) ???:-1]
>>> 0x7f54cf415cab : vtkAnimationCue::Tick(double, double, double)
>>> [(libvtkCommonCore-pv4.3.so.1) ???:-1]
>>> 0x7f54cdf23268 : vtkAnimationPlayer::Play()
>>> [(libvtkPVAnimation-pv4.3.so.1) ???:-1]
>>> 0x7f54d7851619 : vtkSMAnimationSceneCommand(vtkClientServerInterpreter*,
>>> vtkObjectBase*, char const*, vtkClientServerStream const&,
>>> vtkClientServerStream&, void*)
>>> [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1]
>>> 0x7f54d4e135e0 : vtkClientServerInterpreter::CallCommandFunction(char
>>> const*, vtkObjectBase*, char const*, vtkClientServerStream const&,
>>> vtkClientServerStream&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>> 0x7f54d4e18393 :
>>> vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream
>>> const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>> 0x7f54d4e16832 :
>>> vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&,
>>> int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>> 0x7f54d4e16ced :
>>> vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&)
>>> [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>> 0x7f54d5b436d4 : vtkSIProperty::ProcessMessage(vtkClientServerStream&)
>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>> 0x7f54d5b4377e : vtkSIProperty::Push(paraview_protobuf::Message*, int)
>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>> 0x7f54d5b4459e : vtkSIProxy::Push(paraview_protobuf::Message*)
>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>> 0x7f54d5b2884a :
>>> vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*)
>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>> 0x7f54d5b27484 :
>>> vtkPVSessionCore::PushState(paraview_protobuf::Message*)
>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>> 0x7f54d5b2514d :
>>> vtkPVSessionBase::PushState(paraview_protobuf::Message*)
>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>> 0x7f54d5d859b7 : vtkSMProxy::UpdateProperty(char const*, int)
>>> [(libvtkPVServerManagerCore-pv4.3.so.1) ???:-1]
>>> 0x7f54d6d8aa07 : pqVCRController::onPlay()
>>> [(libvtkpqComponents-pv4.3.so.1) ???:-1]
>>> 0x7f54cfa98258 : QMetaObject::activate(QObject*, QMetaObject const*,
>>> int, void**) [(libQtCore.so.4) ???:-1]
>>> 0x7f54d01102f2 : QAction::triggered(bool) [(libQtGui.so.4) ???:-1]
>>> 0x7f54d0111710 : QAction::activate(QAction::ActionEvent)
>>> [(libQtGui.so.4) ???:-1]
>>> 0x7f54d04fd514 : ??? [(???) ???:-1]
>>> 0x7f54d04fd7ab : QAbstractButton::mouseReleaseEvent(QMouseEvent*)
>>> [(libQtGui.so.4) ???:-1]
>>> 0x7f54d05d15ea : QToolButton::mouseReleaseEvent(QMouseEvent*)
>>> [(libQtGui.so.4) ???:-1]
>>> 0x7f54d0175ac1 : QWidget::event(QEvent*) [(libQtGui.so.4) ???:-1]
>>> 0x7f54d04fca3f : QAbstractButton::event(QEvent*) [(libQtGui.so.4) ???:-1]
>>> 0x7f54d05d422d : QToolButton::event(QEvent*) [(libQtGui.so.4) ???:-1]
>>> 0x7f54d011759e : QApplicationPrivate::notify_helper(QObject*, QEvent*)
>>> [(libQtGui.so.4) ???:-1]
>>> 0x7f54d011e533 : QApplication::notify(QObject*, QEvent*)
>>> [(libQtGui.so.4) ???:-1]
>>> 0x7f54cfa802f3 : QCoreApplication::notifyInternal(QObject*, QEvent*)
>>> [(libQtCore.so.4) ???:-1]
>>> 0x7f54d011a656 : QApplicationPrivate::sendMouseEvent(QWidget*,
>>> QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool)
>>> [(libQtGui.so.4) ???:-1]
>>> 0x7f54d019ca94 : ??? [(???) ???:-1]
>>> 0x7f54d019b877 : QApplication::x11ProcessEvent(_XEvent*)
>>> [(libQtGui.so.4) ???:-1]
>>> 0x7f54d01c4805 : ??? [(???) ???:-1]
>>> 0x7f54cfa7f375 :
>>> QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
>>> [(libQtCore.so.4) ???:-1]
>>> 0x7f54cfa7f748 : QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
>>> [(libQtCore.so.4) ???:-1]
>>> 0x7f54cfa8414b : QCoreApplication::exec() [(libQtCore.so.4) ???:-1]
>>> 0x407785 : main [(paraview) ???:-1]
>>> 0x7f54ce06cec5 : __libc_start_main [(libc.so.6) ???:-1]
>>> 0x4074da : QMainWindow::event(QEvent*) [(paraview) ???:-1]
>>> =========================================================
>>>
>>> Thanks,
>>>
>>> Sergi Mateo
>>> sergi.mateo.bellido at 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
>>>
>>>
>>
>>
>>  --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>>
>>
>>
>
>
>  --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/0ab53eb5/attachment.html>

From aymeric.naze at gmail.com  Thu Jul  9 11:03:18 2015
From: aymeric.naze at gmail.com (Aymeric NAZE)
Date: Thu, 9 Jul 2015 17:03:18 +0200
Subject: [Paraview] Orient created vectors
In-Reply-To: <CAB5Fpx5Lgi-yQxwrp43S4goeO40x56P9pFU94OGKWSzN_i+fcw@mail.gmail.com>
References: <CAM4K3YdAJ+XvjbShzT3uJL3ntYwwitjUPdryzrx5pZUOGEa4LQ@mail.gmail.com>
 <CAB5Fpx5ZZb2UQP86on6-YT+Mqx6DfUc3j6K0deo8nTOaY2iHAg@mail.gmail.com>
 <CAM4K3YeSBB+eavXBKA+jUPzTdfASeM-pWRNkOqnBbdD6NcbGow@mail.gmail.com>
 <CAB5Fpx49Pm4tnm_cduJspQXFLzA27R+WXgN8C5XABBsdY3hbfg@mail.gmail.com>
 <CAM4K3YcYe_Eo8jYVWVWuaU3mHssPa=DnSFBjdmK3eyh8tr0RQA@mail.gmail.com>
 <CAB5Fpx5Lgi-yQxwrp43S4goeO40x56P9pFU94OGKWSzN_i+fcw@mail.gmail.com>
Message-ID: <CAM4K3YdQZDhAqAy--jj6bNFy0VYKkwO-=s7Xz-VY7evJJ=DGJw@mail.gmail.com>

Thank you for your reactivity.

You will find below a dropbox link to 2 files :

   - the dataset : 27.8 Mo
   - the state file (ontaining the calculators and glyph) : 261 ko


https://www.dropbox.com/sh/fu8mji13ov79crb/AAAFcFvCKccEu-qcP5YZtguPa?dl=0


2015-07-09 16:12 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:

> Hmm, well it does indeed have non-zero Y and Z components. Could you share
> this dataset?
>
> Thanks,
> Cory
>
> On Thu, Jul 9, 2015 at 8:53 AM, Aymeric NAZE <aymeric.naze at gmail.com>
> wrote:
>
>> Information regarding my Result vector field in Data Arrays (under
>> "Information" tab in the calculator filter) :
>>
>>    - *Data Type* : double
>>    - *Data Ranges* : [-1.26, 0.01], [-0.01, 0.76], [-0.16, 0.27]
>>
>>
>> 2015-07-09 15:03 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>>
>>> Can you verify that the second and third components of your Result
>>> vector field have a range outside [0, 0]? You can get this information
>>> under the Information tab in the Data Arrays table.
>>>
>>> On Thu, Jul 9, 2015 at 7:56 AM, Aymeric NAZE <aymeric.naze at gmail.com>
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> Thanks for considering my problem.
>>>>
>>>> Yes, in the Glyph Filter I have the following *Active Attributes* :
>>>>
>>>>    - *Scalars *: FF wich is the magnitude in the (x,y) plane
>>>>    (calculated with another "calculator" filter : FF=(U^2+V^2)^0.5) : it's the
>>>>    length of the arrows I want to display.
>>>>
>>>>
>>>>    - *Vectors *: Result (vectors from the previously described
>>>>    calculator)
>>>>
>>>>
>>>> 2015-07-09 14:29 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>>>>
>>>>> Hi Aymeric,
>>>>>
>>>>> Did you choose the "Result" array as the "Vectors" property in the
>>>>> Properties panel of the Glyph filter?
>>>>>
>>>>> HTH,
>>>>> Cory
>>>>>
>>>>> On Thu, Jul 9, 2015 at 7:26 AM, Aymeric NAZE <aymeric.naze at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I'm using Paraview 4.3.1 (64-bit) to display data from a tecplot
>>>>>> format file.
>>>>>>
>>>>>> Data is points coordinates (x,y,z) and vectors coordinates (u,v,w)
>>>>>> for each point.
>>>>>>
>>>>>>
>>>>>>    - I have created vectors with "Calculator" filter (Result =
>>>>>>    u*iHat+v*jHat+w*kHat) and it creates vectors with thewanted coordinates (I
>>>>>>    can see that in the spreadsheet view)
>>>>>>
>>>>>>
>>>>>>    - Then I made a glyph to display these vectors as arrows.
>>>>>>
>>>>>> Magnitude is displayed without problem but i did'nt find how to
>>>>>> orient correctly the vectors.
>>>>>> Whether i check or not the "Orient" feature it doesn't change
>>>>>> anything : vectors are always oriented along the x axis...
>>>>>>
>>>>>> Does anybody can help me on that issue ?
>>>>>>
>>>>>> Thanks so much in advance.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Aymeric
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Cory Quammen
>>>>> R&D Engineer
>>>>> Kitware, Inc.
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Cory Quammen
>>> R&D Engineer
>>> Kitware, Inc.
>>>
>>
>>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/0af0760e/attachment.html>

From casey.goodlett at kitware.com  Thu Jul  9 11:14:43 2015
From: casey.goodlett at kitware.com (Casey Goodlett)
Date: Thu, 9 Jul 2015 11:14:43 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAFe6qKgoBR7HU6MHCDTKr_HCxBGu_eU3St2D5+UjQ3zrBwqcbg@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <CAFe6qKgoBR7HU6MHCDTKr_HCxBGu_eU3St2D5+UjQ3zrBwqcbg@mail.gmail.com>
Message-ID: <CAOqyOuG9-w-TFEXJO1+8EvtAQLK-JJE3Rr8XqVLG=JObe69sNg@mail.gmail.com>

On Thu, Jul 9, 2015 at 10:53 AM, Eric Younkin - NOAA Federal <
eric.g.younkin at noaa.gov> wrote:

> Casey,
>
> I am mostly interested in the feature extraction routines and Paraview
> integration with the Velodyne VLP-16.  I'd like to experiment with PCL
> algorithms to try and pick out fixed objects such as buoys or piers from a
> VLP-16 mounted on our research vessel as we travel up the coast.  I think
> most of my errors are from attempting to build using Visual Studio 2013 pro
> and older Qt/PCL versions.  If I can use the most recent versions, that
> might help things.
>

Sounds like a cool project.  You may need to add some additional wrappers
for feature extraction if you are looking for things beyond the sample
consensus models that we have.  I dont think any of the point feature
histogram utilities are currently wrapped.

Windows builds of the whole stack are a bit tricky.  Feel free to share
your error messages, and I'll help where I can.

The plugin does not include support for the VLP-16 in its current state.
We have another project VeloView <https://github.com/Kitware/VeloView> that
builds a paraview plugin for VLP-16.  I have used this in combination with
the PCL plugin in the past, but the build is not straightforward at this
time.



> The binaries you linked to here still require installation of Paraview and
> PCL correct?
>
>
This binary is ParaView with the pcl plugin built and packaged.  If you
download this it includes paraview and PCL.

-- 
Casey B Goodlett, PhD
Technical Leader
Kitware, Inc. - North Carolina Office
http://www.kitware.com
(919) 969-6990 x310
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/cb7126b2/attachment.html>

From eric.g.younkin at noaa.gov  Thu Jul  9 11:33:19 2015
From: eric.g.younkin at noaa.gov (Eric Younkin - NOAA Federal)
Date: Thu, 9 Jul 2015 11:33:19 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAOqyOuG9-w-TFEXJO1+8EvtAQLK-JJE3Rr8XqVLG=JObe69sNg@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <CAFe6qKgoBR7HU6MHCDTKr_HCxBGu_eU3St2D5+UjQ3zrBwqcbg@mail.gmail.com>
 <CAOqyOuG9-w-TFEXJO1+8EvtAQLK-JJE3Rr8XqVLG=JObe69sNg@mail.gmail.com>
Message-ID: <CAFe6qKg-_LHR3tHZ10H78PZJcF2rAVV8bEOH_y_Bt0h+C9jMyw@mail.gmail.com>

Thanks Casey.  For someone with only moderate programming experience, how
difficult would you say creating those additional wrappers and building a
VLP-16 paraview plugin would be?  Do you happen to have any resources or
guides for doing so?

I will continue to look at building from source and check out Project
Tango.  Thanks for the link.

Thanks,
Eric

On Thu, Jul 9, 2015 at 11:14 AM, Casey Goodlett <casey.goodlett at kitware.com>
wrote:

>
> On Thu, Jul 9, 2015 at 10:53 AM, Eric Younkin - NOAA Federal <
> eric.g.younkin at noaa.gov> wrote:
>
>> Casey,
>>
>> I am mostly interested in the feature extraction routines and Paraview
>> integration with the Velodyne VLP-16.  I'd like to experiment with PCL
>> algorithms to try and pick out fixed objects such as buoys or piers from a
>> VLP-16 mounted on our research vessel as we travel up the coast.  I think
>> most of my errors are from attempting to build using Visual Studio 2013 pro
>> and older Qt/PCL versions.  If I can use the most recent versions, that
>> might help things.
>>
>
> Sounds like a cool project.  You may need to add some additional wrappers
> for feature extraction if you are looking for things beyond the sample
> consensus models that we have.  I dont think any of the point feature
> histogram utilities are currently wrapped.
>
> Windows builds of the whole stack are a bit tricky.  Feel free to share
> your error messages, and I'll help where I can.
>
> The plugin does not include support for the VLP-16 in its current state.
> We have another project VeloView <https://github.com/Kitware/VeloView>
> that builds a paraview plugin for VLP-16.  I have used this in combination
> with the PCL plugin in the past, but the build is not straightforward at
> this time.
>
>
>
>> The binaries you linked to here still require installation of Paraview
>> and PCL correct?
>>
>>
> This binary is ParaView with the pcl plugin built and packaged.  If you
> download this it includes paraview and PCL.
>
> --
> Casey B Goodlett, PhD
> Technical Leader
> Kitware, Inc. - North Carolina Office
> http://www.kitware.com
> (919) 969-6990 x310
>



-- 
Eric Younkin LTJG/NOAA
HSTP Liaison - East
Marine Operations Center - Atlantic
439 W York St
Norfolk, VA 23510
Cell: 828-331-8197
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/97732795/attachment.html>

From eric.g.younkin at noaa.gov  Thu Jul  9 15:00:53 2015
From: eric.g.younkin at noaa.gov (Eric Younkin - NOAA Federal)
Date: Thu, 9 Jul 2015 15:00:53 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAFe6qKg-_LHR3tHZ10H78PZJcF2rAVV8bEOH_y_Bt0h+C9jMyw@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <CAFe6qKgoBR7HU6MHCDTKr_HCxBGu_eU3St2D5+UjQ3zrBwqcbg@mail.gmail.com>
 <CAOqyOuG9-w-TFEXJO1+8EvtAQLK-JJE3Rr8XqVLG=JObe69sNg@mail.gmail.com>
 <CAFe6qKg-_LHR3tHZ10H78PZJcF2rAVV8bEOH_y_Bt0h+C9jMyw@mail.gmail.com>
Message-ID: <CAFe6qKhUiTADyYM9OTyWZg5RtvctezOxnREXnL40BsR-Ny=EoA@mail.gmail.com>

I should also mention that I have been reading this paper
<http://www.paraview.org/Wiki/images/1/1e/Paper.pdf> and a few other
sources.  I think I have a basic idea of the framework.

On Thu, Jul 9, 2015 at 11:33 AM, Eric Younkin - NOAA Federal <
eric.g.younkin at noaa.gov> wrote:

> Thanks Casey.  For someone with only moderate programming experience, how
> difficult would you say creating those additional wrappers and building a
> VLP-16 paraview plugin would be?  Do you happen to have any resources or
> guides for doing so?
>
> I will continue to look at building from source and check out Project
> Tango.  Thanks for the link.
>
> Thanks,
> Eric
>
> On Thu, Jul 9, 2015 at 11:14 AM, Casey Goodlett <
> casey.goodlett at kitware.com> wrote:
>
>>
>> On Thu, Jul 9, 2015 at 10:53 AM, Eric Younkin - NOAA Federal <
>> eric.g.younkin at noaa.gov> wrote:
>>
>>> Casey,
>>>
>>> I am mostly interested in the feature extraction routines and Paraview
>>> integration with the Velodyne VLP-16.  I'd like to experiment with PCL
>>> algorithms to try and pick out fixed objects such as buoys or piers from a
>>> VLP-16 mounted on our research vessel as we travel up the coast.  I think
>>> most of my errors are from attempting to build using Visual Studio 2013 pro
>>> and older Qt/PCL versions.  If I can use the most recent versions, that
>>> might help things.
>>>
>>
>> Sounds like a cool project.  You may need to add some additional wrappers
>> for feature extraction if you are looking for things beyond the sample
>> consensus models that we have.  I dont think any of the point feature
>> histogram utilities are currently wrapped.
>>
>> Windows builds of the whole stack are a bit tricky.  Feel free to share
>> your error messages, and I'll help where I can.
>>
>> The plugin does not include support for the VLP-16 in its current state.
>> We have another project VeloView <https://github.com/Kitware/VeloView>
>> that builds a paraview plugin for VLP-16.  I have used this in combination
>> with the PCL plugin in the past, but the build is not straightforward at
>> this time.
>>
>>
>>
>>> The binaries you linked to here still require installation of Paraview
>>> and PCL correct?
>>>
>>>
>> This binary is ParaView with the pcl plugin built and packaged.  If you
>> download this it includes paraview and PCL.
>>
>> --
>> Casey B Goodlett, PhD
>> Technical Leader
>> Kitware, Inc. - North Carolina Office
>> http://www.kitware.com
>> (919) 969-6990 x310
>>
>
>
>
> --
> Eric Younkin LTJG/NOAA
> HSTP Liaison - East
> Marine Operations Center - Atlantic
> 439 W York St
> Norfolk, VA 23510
> Cell: 828-331-8197
>



-- 
Eric Younkin LTJG/NOAA
HSTP Liaison - East
Marine Operations Center - Atlantic
439 W York St
Norfolk, VA 23510
Cell: 828-331-8197
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/ac67233c/attachment.html>

From utkarsh.ayachit at kitware.com  Thu Jul  9 17:05:39 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 09 Jul 2015 21:05:39 +0000
Subject: [Paraview] Impossible to see a movement.
In-Reply-To: <559DF634.5090807@alphanet.ch>
References: <20150708074214.ED383124F2D5@shakotay.alphanet.ch>
 <CADHSJjBqUBn7yScdubZkM1v4+WWi3AwegXyjuTJFuT9LjN22XA@mail.gmail.com>
 <559D7FFA.5030301@alphanet.ch>
 <CADHSJjC+cznjPdcX18140ZPEU4wqaiS8J_WF+-=4QTLFuv1aTg@mail.gmail.com>
 <559DF634.5090807@alphanet.ch>
Message-ID: <CADHSJjD=Sx3BFrKQZ3+PBWB1eG+qE+hnmu3=2EE9L_9voe1wPw@mail.gmail.com>

Amel,

What's the Result_DEPL array? Is that displacement? Assuming that, I
applied two calculators: first to convert the Result_DEPL array to a 3
component vector and the second to translate the coordinate positions using
the vector computed by the previous one. If the Result_DEPL changes in your
dataset over time, you'll see the movement.

State file attached.

Utarsh

On Thu, Jul 9, 2015 at 12:19 AM A. Kapetanovic <aka at alphanet.ch> wrote:

> Utkarsh,
>
> I did something on google drive, I shared the file with your e-mail and
> here you have the url :
>
> https://drive.google.com/open?id=0B_ag1ge2Wc1nSS10M1JYampTb00
>
> I hope all is OK like this, it's the first time I use google drive. Say
> me please if something misses.
>
> Regards   :)
>
>
> Le 08. 07. 15 22:47, Utkarsh Ayachit a ?crit :
> > Amel,
> >
> > The dataset didn't come through, I am afraid. Is it may be easier to
> > upload it somewhere eg. dropbox/google drive?
> >
> > Utkarsh
> >
> > On Wed, Jul 8, 2015 at 3:54 PM A. Kapetanovic <aka at alphanet.ch
> > <mailto:aka at alphanet.ch>> wrote:
> >
> >     WARNING: this mail was modified in transit:
> >         defanged (renamed/protected) 07.hdf because file type unknown.
> >     Rename defang-0.binary to 07.hdf if you want to access the file
> anyway
> >
> >     More details at:
> >     http://www.alphanet.ch/alphanet/anti-spam.html
> >     Hi,
> >
> >     Thanks for your reply.
> >
> >     Of course I have data to share. The rmed result comressed file is too
> >     big (35 MB), so I send here the hdf and comm files, you only need to
> >     compute the (3) meshes and to run the simulation to have this rmed
> file.
> >
> >     Say me if you need something else, I hope all is clear enough like
> >     this   :)
> >
> >     Amel
> >
> >
> >     Le 08. 07. 15 15:44, Utkarsh Ayachit a ?crit :
> >      > Do you have a sample dataset to share? That'll make this easier.
> >      >
> >      > Typically, movement comes from one of the following:
> >      > 1. Readers: the reader itself translates the points in the grid
> >     as time
> >      > changes
> >      > 2. Filters: if the grid doesn't change but has attributes that
> >     indicate
> >      > the displacement, one can apply a filter to transform the grid
> using
> >      > those displacement vectors.
> >      >
> >      > Utkarsh
> >      >
> >      > On Wed, Jul 8, 2015 at 3:59 AM <aka at alphanet.ch
> >     <mailto:aka at alphanet.ch>
> >      > <mailto:aka at alphanet.ch <mailto:aka at alphanet.ch>>> wrote:
> >      >
> >      >     Hi,
> >      >
> >      >     I am using Paraview with Salome-Meca + Code_Aster and I have
> >     e little
> >      >     problem : impossible to see the movement of a part that is
> >     moving.
> >      >
> >      >     In fact the simulation is very simple : I have 2 cylinders,
> >     one is
> >      >     fixed by
> >      >     one face and the other have a movement on a face. The
> simulation
> >      >     converges
> >      >     and when I open the mmed or rmed file (result) with Paraview,
> >      >     impossible to
> >      >     see any movement even if I clic "play".
> >      >
> >      >     Simply nothing happens.
> >      >
> >      >     Can please someone help me ?
> >      >
> >      >     Best regards,
> >      >
> >      >     Amka
> >      >     _______________________________________________
> >      >     Powered by www.kitware.com <http://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
> >      >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/65fe6e03/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sample.pvsm
Type: application/octet-stream
Size: 146168 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150709/65fe6e03/attachment.obj>

From jeffrey.c.becker at nasa.gov  Thu Jul  9 17:55:30 2015
From: jeffrey.c.becker at nasa.gov (Jeff Becker)
Date: Thu, 9 Jul 2015 14:55:30 -0700
Subject: [Paraview] displaying multiple timesteps
Message-ID: <559EEDD2.90100@nasa.gov>

Hi. I have a bunch of image files f_0.vti, f_1.vti etc. I am using 
ParaView's play button to go through them. However, the files are ~6G in 
size, so reading files between each time step takes a while. Is there 
any good way to speed this up? Thanks.

-jeff

From cory.quammen at kitware.com  Fri Jul 10 01:15:27 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 10 Jul 2015 00:15:27 -0500
Subject: [Paraview] Use viscm to design color maps for ParaView 4.4
Message-ID: <CAB5Fpx4JY7KvHdnDyY1hCZ8HcM+HDhjb0xGXRJrP++kyPHUrEw@mail.gmail.com>

Dear ParaView community,

I wrote a blog post on the Python color map design utility viscm by Stefan
van der Walt and Nathaniel Smith and how to get the color maps it produces
into ParaView. van der Walt and Smith used this utility to design proposed
replacements for matplotlib's default color map, one of which is included
as a file you can import into ParaView.

You can read the post here:
http://www.kitware.com/blog/home/post/932

Cheers, and happy color mapping,
Cory

-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150710/cb9e3ab2/attachment.html>

From aka at alphanet.ch  Fri Jul 10 03:27:45 2015
From: aka at alphanet.ch (aka at alphanet.ch)
Date: Fri, 10 Jul 2015 09:27:45 +0200
Subject: [Paraview] Impossible to see a movement.
In-Reply-To: <CADHSJjD=Sx3BFrKQZ3+PBWB1eG+qE+hnmu3=2EE9L_9voe1wPw@mail.gmail.com>
References: <20150708074214.ED383124F2D5@shakotay.alphanet.ch>
 <CADHSJjBqUBn7yScdubZkM1v4+WWi3AwegXyjuTJFuT9LjN22XA@mail.gmail.com>
 <559D7FFA.5030301@alphanet.ch>
 <CADHSJjC+cznjPdcX18140ZPEU4wqaiS8J_WF+-=4QTLFuv1aTg@mail.gmail.com>
 <559DF634.5090807@alphanet.ch>
 <CADHSJjD=Sx3BFrKQZ3+PBWB1eG+qE+hnmu3=2EE9L_9voe1wPw@mail.gmail.com>
Message-ID: <20150710072745.DC6FF1252212@shakotay.alphanet.ch>

Utarsh, 

Thank you for your reply, I will try to do what you say this week-end. 

Another fact is a few strange : when I opened my rmed file with Paraview 
(using for this the http://www.alneos.com/telechargement/paraview-avec-med 
software), I simply could clic on the "Wrap" button (or a name near that) 
and, when I clic "Play" after I can see the movement... 

This same "Wrap" button is disabled (for this simualtion) in my Salome-Meca 
Paraview module, with which I work, and I don't understand why... 

Amel 


Utkarsh Ayachit writes: 

> Amel, 
> 
> What's the Result_DEPL array? Is that displacement? Assuming that, I
> applied two calculators: first to convert the Result_DEPL array to a 3
> component vector and the second to translate the coordinate positions using
> the vector computed by the previous one. If the Result_DEPL changes in your
> dataset over time, you'll see the movement. 
> 
> State file attached. 
> 
> Utarsh 
> 
> On Thu, Jul 9, 2015 at 12:19 AM A. Kapetanovic <aka at alphanet.ch> wrote: 
> 
>> Utkarsh, 
>>
>> I did something on google drive, I shared the file with your e-mail and
>> here you have the url : 
>>
>> https://drive.google.com/open?id=0B_ag1ge2Wc1nSS10M1JYampTb00 
>>
>> I hope all is OK like this, it's the first time I use google drive. Say
>> me please if something misses. 
>>
>> Regards   :) 
>>
>>
>> Le 08. 07. 15 22:47, Utkarsh Ayachit a ?crit :
>> > Amel,
>> >
>> > The dataset didn't come through, I am afraid. Is it may be easier to
>> > upload it somewhere eg. dropbox/google drive?
>> >
>> > Utkarsh
>> >
>> > On Wed, Jul 8, 2015 at 3:54 PM A. Kapetanovic <aka at alphanet.ch
>> > <mailto:aka at alphanet.ch>> wrote:
>> >
>> >     WARNING: this mail was modified in transit:
>> >         defanged (renamed/protected) 07.hdf because file type unknown.
>> >     Rename defang-0.binary to 07.hdf if you want to access the file
>> anyway
>> >
>> >     More details at:
>> >     http://www.alphanet.ch/alphanet/anti-spam.html
>> >     Hi,
>> >
>> >     Thanks for your reply.
>> >
>> >     Of course I have data to share. The rmed result comressed file is too
>> >     big (35 MB), so I send here the hdf and comm files, you only need to
>> >     compute the (3) meshes and to run the simulation to have this rmed
>> file.
>> >
>> >     Say me if you need something else, I hope all is clear enough like
>> >     this   :)
>> >
>> >     Amel
>> >
>> >
>> >     Le 08. 07. 15 15:44, Utkarsh Ayachit a ?crit :
>> >      > Do you have a sample dataset to share? That'll make this easier.
>> >      >
>> >      > Typically, movement comes from one of the following:
>> >      > 1. Readers: the reader itself translates the points in the grid
>> >     as time
>> >      > changes
>> >      > 2. Filters: if the grid doesn't change but has attributes that
>> >     indicate
>> >      > the displacement, one can apply a filter to transform the grid
>> using
>> >      > those displacement vectors.
>> >      >
>> >      > Utkarsh
>> >      >
>> >      > On Wed, Jul 8, 2015 at 3:59 AM <aka at alphanet.ch
>> >     <mailto:aka at alphanet.ch>
>> >      > <mailto:aka at alphanet.ch <mailto:aka at alphanet.ch>>> wrote:
>> >      >
>> >      >     Hi,
>> >      >
>> >      >     I am using Paraview with Salome-Meca + Code_Aster and I have
>> >     e little
>> >      >     problem : impossible to see the movement of a part that is
>> >     moving.
>> >      >
>> >      >     In fact the simulation is very simple : I have 2 cylinders,
>> >     one is
>> >      >     fixed by
>> >      >     one face and the other have a movement on a face. The
>> simulation
>> >      >     converges
>> >      >     and when I open the mmed or rmed file (result) with Paraview,
>> >      >     impossible to
>> >      >     see any movement even if I clic "play".
>> >      >
>> >      >     Simply nothing happens.
>> >      >
>> >      >     Can please someone help me ?
>> >      >
>> >      >     Best regards,
>> >      >
>> >      >     Amka
>> >      >     _______________________________________________
>> >      >     Powered by www.kitware.com <http://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
>> >      >
>> > 
>>

From christophe.trophime at lncmi.cnrs.fr  Fri Jul 10 07:52:09 2015
From: christophe.trophime at lncmi.cnrs.fr (Christophe Trophime)
Date: Fri, 10 Jul 2015 13:52:09 +0200 (CEST)
Subject: [Paraview] How to display only certain parts of a geometry?
In-Reply-To: <416976069.2536202.1436528937837.JavaMail.zimbra@lncmi.cnrs.fr>
Message-ID: <1009439766.2536834.1436529129453.JavaMail.zimbra@lncmi.cnrs.fr>

Hi, 
I wish to use Paraview to display data stored in EnSight Gold format. 
I would like to display only certain parts of the geometry. 
In EnSight it's quite easy to select the parts you want to display. 
How can I do the same in Paraview? 

Thanks for any hints 
Best regards 
C 



Christophe TROPHIME 
Research Engineer 

CNRS - LNCMI 
25, rue des Martyrs 
BP 166 
38042 GRENOBLE Cedex 9 
FRANCE 

Tel : +33 (0)4 76 88 90 02 
Fax : +33 (0) 4 76 88 10 01 
Office U 19 
M at il : christophe.trophime at lncmi.cnrs.fr 

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

From alexandre.ancel at cemosis.fr  Fri Jul 10 09:16:58 2015
From: alexandre.ancel at cemosis.fr (Alexandre Ancel)
Date: Fri, 10 Jul 2015 15:16:58 +0200
Subject: [Paraview] How to display only certain parts of a geometry?
In-Reply-To: <1009439766.2536834.1436529129453.JavaMail.zimbra@lncmi.cnrs.fr>
References: <416976069.2536202.1436528937837.JavaMail.zimbra@lncmi.cnrs.fr>
 <1009439766.2536834.1436529129453.JavaMail.zimbra@lncmi.cnrs.fr>
Message-ID: <CADR2tx70QHYGjZGMTkJJWCUSe-_fy6MN8TuV9zN6+--FiQoNyw@mail.gmail.com>

Hello,

If I am not wrong, loading Ensight Gold files in ParaView will be seen as a
Multi-Block Dataset in the Information section of the data. You can then
use the "Extract Block" filter to extract the different parts of the data.

Hope it helps

Best regards,
Alexandre Ancel

On Fri, Jul 10, 2015 at 1:52 PM, Christophe Trophime <
christophe.trophime at lncmi.cnrs.fr> wrote:

> Hi,
> I wish to use Paraview to display data stored in EnSight Gold format.
> I would like to display only certain parts of the geometry.
> In EnSight it's quite easy to select the parts you want to display.
> How can I do the same in Paraview?
>
> Thanks for any hints
> Best regards
> C
>
>
>
> Christophe TROPHIME
> Research Engineer
>
>     CNRS - LNCMI
> 25, rue des Martyrs
> BP 166
> 38042 GRENOBLE Cedex 9
> FRANCE
>
> Tel : +33 (0)4 76 88 90 02
> Fax : +33 (0) 4 76 88 10 01
> Office U 19
> M at il : christophe.trophime at lncmi.cnrs.fr
>
>
> _______________________________________________
> 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
>
>


-- 
Alexandre Ancel
Docteur, Ing?nieur de recherche / Phd, Research Engineer
Cemosis <http://www.cemosis.fr> - alexandre.ancel at cemosis.fr
Tel: +33 (0)3 68 8*5 02 06*
IRMA - 7, rue Ren? Descartes
67 000 Strasbourg, France
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150710/07418a68/attachment.html>

From lyon at fnal.gov  Fri Jul 10 09:34:50 2015
From: lyon at fnal.gov (Adam Lyon)
Date: Fri, 10 Jul 2015 08:34:50 -0500
Subject: [Paraview] Can I parallelize different input files?
Message-ID: <CANjddW23Bd6DODMSbv9aqrYfipxa5H8gdkvGSu87mjnL39xkfA@mail.gmail.com>

Hi - I have 12 fairly large vti files (each one is a simulation of part of
the magnetic field of my particle physics detector). Each file covers a
distinct part of the total volume, so that all 12 together covers the whole
thing. This would seem to be a perfect opportunity to try to parallelize
Paraview's handling of these files - one CPU per vti file.  I have a
machine with lots of cores at my disposal. Will Paraview recognize by
itself that it can parallelize its operations, one CPU per vti file, or do
I need to do something to make that happen? There's no overlap between the
files - will that be a problem? My plan is to run a pvserver on the
many-core CPU machine and connect to it via my Mac. Any advice would be
helpful and appreciated!  Thanks! -- Adam
*-----*

*Adam L. Lyon*
*Scientist; Associate Division Head for Systems for Scientific Applications*

Scientific Computing Division & Muon g-2 Experiment
Fermi National Accelerator Laboratory
630 840 5522 office
www.fnal.gov
lyon at fnal.gov

Connect with us!
Newsletter <http://www.fnal.gov/pub/today/>  |  Facebook
<https://www.facebook.com/Fermilab>  |  Twitter
<https://twitter.com/Fermilab>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150710/deb4ce52/attachment.html>

From utkarsh.ayachit at kitware.com  Fri Jul 10 10:27:13 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 10 Jul 2015 14:27:13 +0000
Subject: [Paraview] Impossible to see a movement.
In-Reply-To: <20150710072745.DC6FF1252212@shakotay.alphanet.ch>
References: <20150708074214.ED383124F2D5@shakotay.alphanet.ch>
 <CADHSJjBqUBn7yScdubZkM1v4+WWi3AwegXyjuTJFuT9LjN22XA@mail.gmail.com>
 <559D7FFA.5030301@alphanet.ch>
 <CADHSJjC+cznjPdcX18140ZPEU4wqaiS8J_WF+-=4QTLFuv1aTg@mail.gmail.com>
 <559DF634.5090807@alphanet.ch>
 <CADHSJjD=Sx3BFrKQZ3+PBWB1eG+qE+hnmu3=2EE9L_9voe1wPw@mail.gmail.com>
 <20150710072745.DC6FF1252212@shakotay.alphanet.ch>
Message-ID: <CADHSJjDno9=YiFdFmQs71GCy=LtPQwkCj+O7yvynGi84ge03XQ@mail.gmail.com>

That would be questions to ask to the folks who developed the reader, I am
afraid. I suspect the "Wrap" button expected an array of certain shape/name
and that's missing in your dataset. I suspect its the fact that your DEPL
array is a 4 component array, rather than 3 -- but that's just a wild guess.

Utkarsh

On Fri, Jul 10, 2015 at 3:27 AM <aka at alphanet.ch> wrote:

> Utarsh,
>
> Thank you for your reply, I will try to do what you say this week-end.
>
> Another fact is a few strange : when I opened my rmed file with Paraview
> (using for this the http://www.alneos.com/telechargement/paraview-avec-med
> software), I simply could clic on the "Wrap" button (or a name near that)
> and, when I clic "Play" after I can see the movement...
>
> This same "Wrap" button is disabled (for this simualtion) in my Salome-Meca
> Paraview module, with which I work, and I don't understand why...
>
> Amel
>
>
> Utkarsh Ayachit writes:
>
> > Amel,
> >
> > What's the Result_DEPL array? Is that displacement? Assuming that, I
> > applied two calculators: first to convert the Result_DEPL array to a 3
> > component vector and the second to translate the coordinate positions
> using
> > the vector computed by the previous one. If the Result_DEPL changes in
> your
> > dataset over time, you'll see the movement.
> >
> > State file attached.
> >
> > Utarsh
> >
> > On Thu, Jul 9, 2015 at 12:19 AM A. Kapetanovic <aka at alphanet.ch> wrote:
> >
> >> Utkarsh,
> >>
> >> I did something on google drive, I shared the file with your e-mail and
> >> here you have the url :
> >>
> >> https://drive.google.com/open?id=0B_ag1ge2Wc1nSS10M1JYampTb00
> >>
> >> I hope all is OK like this, it's the first time I use google drive. Say
> >> me please if something misses.
> >>
> >> Regards   :)
> >>
> >>
> >> Le 08. 07. 15 22:47, Utkarsh Ayachit a ?crit :
> >> > Amel,
> >> >
> >> > The dataset didn't come through, I am afraid. Is it may be easier to
> >> > upload it somewhere eg. dropbox/google drive?
> >> >
> >> > Utkarsh
> >> >
> >> > On Wed, Jul 8, 2015 at 3:54 PM A. Kapetanovic <aka at alphanet.ch
> >> > <mailto:aka at alphanet.ch>> wrote:
> >> >
> >> >     WARNING: this mail was modified in transit:
> >> >         defanged (renamed/protected) 07.hdf because file type unknown.
> >> >     Rename defang-0.binary to 07.hdf if you want to access the file
> >> anyway
> >> >
> >> >     More details at:
> >> >     http://www.alphanet.ch/alphanet/anti-spam.html
> >> >     Hi,
> >> >
> >> >     Thanks for your reply.
> >> >
> >> >     Of course I have data to share. The rmed result comressed file is
> too
> >> >     big (35 MB), so I send here the hdf and comm files, you only need
> to
> >> >     compute the (3) meshes and to run the simulation to have this rmed
> >> file.
> >> >
> >> >     Say me if you need something else, I hope all is clear enough like
> >> >     this   :)
> >> >
> >> >     Amel
> >> >
> >> >
> >> >     Le 08. 07. 15 15:44, Utkarsh Ayachit a ?crit :
> >> >      > Do you have a sample dataset to share? That'll make this
> easier.
> >> >      >
> >> >      > Typically, movement comes from one of the following:
> >> >      > 1. Readers: the reader itself translates the points in the grid
> >> >     as time
> >> >      > changes
> >> >      > 2. Filters: if the grid doesn't change but has attributes that
> >> >     indicate
> >> >      > the displacement, one can apply a filter to transform the grid
> >> using
> >> >      > those displacement vectors.
> >> >      >
> >> >      > Utkarsh
> >> >      >
> >> >      > On Wed, Jul 8, 2015 at 3:59 AM <aka at alphanet.ch
> >> >     <mailto:aka at alphanet.ch>
> >> >      > <mailto:aka at alphanet.ch <mailto:aka at alphanet.ch>>> wrote:
> >> >      >
> >> >      >     Hi,
> >> >      >
> >> >      >     I am using Paraview with Salome-Meca + Code_Aster and I
> have
> >> >     e little
> >> >      >     problem : impossible to see the movement of a part that is
> >> >     moving.
> >> >      >
> >> >      >     In fact the simulation is very simple : I have 2 cylinders,
> >> >     one is
> >> >      >     fixed by
> >> >      >     one face and the other have a movement on a face. The
> >> simulation
> >> >      >     converges
> >> >      >     and when I open the mmed or rmed file (result) with
> Paraview,
> >> >      >     impossible to
> >> >      >     see any movement even if I clic "play".
> >> >      >
> >> >      >     Simply nothing happens.
> >> >      >
> >> >      >     Can please someone help me ?
> >> >      >
> >> >      >     Best regards,
> >> >      >
> >> >      >     Amka
> >> >      >     _______________________________________________
> >> >      >     Powered by www.kitware.com <http://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
> >> >      >
> >> >
> >>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150710/a92c9c9e/attachment.html>

From casey.goodlett at kitware.com  Fri Jul 10 10:43:01 2015
From: casey.goodlett at kitware.com (Casey Goodlett)
Date: Fri, 10 Jul 2015 10:43:01 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAFe6qKhUiTADyYM9OTyWZg5RtvctezOxnREXnL40BsR-Ny=EoA@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <CAFe6qKgoBR7HU6MHCDTKr_HCxBGu_eU3St2D5+UjQ3zrBwqcbg@mail.gmail.com>
 <CAOqyOuG9-w-TFEXJO1+8EvtAQLK-JJE3Rr8XqVLG=JObe69sNg@mail.gmail.com>
 <CAFe6qKg-_LHR3tHZ10H78PZJcF2rAVV8bEOH_y_Bt0h+C9jMyw@mail.gmail.com>
 <CAFe6qKhUiTADyYM9OTyWZg5RtvctezOxnREXnL40BsR-Ny=EoA@mail.gmail.com>
Message-ID: <CAOqyOuH60D5LXthUwvSUViCWLqvrTz1z5a9wu-aCX3c4g-GEgQ@mail.gmail.com>

Eric,

That paper describes the approach for filter wrapping.  You will also need
to compile VeloView against your paraview build and then include the
VeloView plugin alongside the PCL plugin.

Hope that helps.

On Thu, Jul 9, 2015 at 3:00 PM, Eric Younkin - NOAA Federal <
eric.g.younkin at noaa.gov> wrote:

> I should also mention that I have been reading this paper
> <http://www.paraview.org/Wiki/images/1/1e/Paper.pdf> and a few other
> sources.  I think I have a basic idea of the framework.
>
> On Thu, Jul 9, 2015 at 11:33 AM, Eric Younkin - NOAA Federal <
> eric.g.younkin at noaa.gov> wrote:
>
>> Thanks Casey.  For someone with only moderate programming experience, how
>> difficult would you say creating those additional wrappers and building a
>> VLP-16 paraview plugin would be?  Do you happen to have any resources or
>> guides for doing so?
>>
>> I will continue to look at building from source and check out Project
>> Tango.  Thanks for the link.
>>
>> Thanks,
>> Eric
>>
>> On Thu, Jul 9, 2015 at 11:14 AM, Casey Goodlett <
>> casey.goodlett at kitware.com> wrote:
>>
>>>
>>> On Thu, Jul 9, 2015 at 10:53 AM, Eric Younkin - NOAA Federal <
>>> eric.g.younkin at noaa.gov> wrote:
>>>
>>>> Casey,
>>>>
>>>> I am mostly interested in the feature extraction routines and Paraview
>>>> integration with the Velodyne VLP-16.  I'd like to experiment with PCL
>>>> algorithms to try and pick out fixed objects such as buoys or piers from a
>>>> VLP-16 mounted on our research vessel as we travel up the coast.  I think
>>>> most of my errors are from attempting to build using Visual Studio 2013 pro
>>>> and older Qt/PCL versions.  If I can use the most recent versions, that
>>>> might help things.
>>>>
>>>
>>> Sounds like a cool project.  You may need to add some additional
>>> wrappers for feature extraction if you are looking for things beyond the
>>> sample consensus models that we have.  I dont think any of the point
>>> feature histogram utilities are currently wrapped.
>>>
>>> Windows builds of the whole stack are a bit tricky.  Feel free to share
>>> your error messages, and I'll help where I can.
>>>
>>> The plugin does not include support for the VLP-16 in its current
>>> state.  We have another project VeloView
>>> <https://github.com/Kitware/VeloView> that builds a paraview plugin for
>>> VLP-16.  I have used this in combination with the PCL plugin in the past,
>>> but the build is not straightforward at this time.
>>>
>>>
>>>
>>>> The binaries you linked to here still require installation of Paraview
>>>> and PCL correct?
>>>>
>>>>
>>> This binary is ParaView with the pcl plugin built and packaged.  If you
>>> download this it includes paraview and PCL.
>>>
>>> --
>>> Casey B Goodlett, PhD
>>> Technical Leader
>>> Kitware, Inc. - North Carolina Office
>>> http://www.kitware.com
>>> (919) 969-6990 x310
>>>
>>
>>
>>
>> --
>> Eric Younkin LTJG/NOAA
>> HSTP Liaison - East
>> Marine Operations Center - Atlantic
>> 439 W York St
>> Norfolk, VA 23510
>> Cell: 828-331-8197
>>
>
>
>
> --
> Eric Younkin LTJG/NOAA
> HSTP Liaison - East
> Marine Operations Center - Atlantic
> 439 W York St
> Norfolk, VA 23510
> Cell: 828-331-8197
>



-- 
Casey B Goodlett, PhD
Technical Leader
Kitware, Inc. - North Carolina Office
http://www.kitware.com
(919) 969-6990 x310
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150710/bc617c82/attachment.html>

From michael.grabietz at img-online.de  Fri Jul 10 10:39:56 2015
From: michael.grabietz at img-online.de (Michael Grabietz)
Date: Fri, 10 Jul 2015 16:39:56 +0200
Subject: [Paraview] Impossible to see a movement.
In-Reply-To: <20150710072745.DC6FF1252212@shakotay.alphanet.ch>
References: <20150708074214.ED383124F2D5@shakotay.alphanet.ch>
 <CADHSJjBqUBn7yScdubZkM1v4+WWi3AwegXyjuTJFuT9LjN22XA@mail.gmail.com>
 <559D7FFA.5030301@alphanet.ch>
 <CADHSJjC+cznjPdcX18140ZPEU4wqaiS8J_WF+-=4QTLFuv1aTg@mail.gmail.com>
 <559DF634.5090807@alphanet.ch>
 <CADHSJjD=Sx3BFrKQZ3+PBWB1eG+qE+hnmu3=2EE9L_9voe1wPw@mail.gmail.com>
 <20150710072745.DC6FF1252212@shakotay.alphanet.ch>
Message-ID: <559FD93C.9080106@img-online.de>

Hi Amel,

I followed the discussion between Utkarsh and you on this topic. Could 
you share the rmed file from Code-Aster? The download from your google 
drive seems to be restricted to specific email addresses.

Michael

Am 10.07.2015 um 09:27 schrieb aka at alphanet.ch:
> Utarsh,
> Thank you for your reply, I will try to do what you say this week-end.
> Another fact is a few strange : when I opened my rmed file with Paraview
> (using for this the
> http://www.alneos.com/telechargement/paraview-avec-med software), I
> simply could clic on the "Wrap" button (or a name near that) and, when I
> clic "Play" after I can see the movement...
> This same "Wrap" button is disabled (for this simualtion) in my
> Salome-Meca Paraview module, with which I work, and I don't understand
> why...
> Amel
>
> Utkarsh Ayachit writes:
>> Amel,
>> What's the Result_DEPL array? Is that displacement? Assuming that, I
>> applied two calculators: first to convert the Result_DEPL array to a 3
>> component vector and the second to translate the coordinate positions
>> using
>> the vector computed by the previous one. If the Result_DEPL changes in
>> your
>> dataset over time, you'll see the movement.
>> State file attached.
>> Utarsh
>> On Thu, Jul 9, 2015 at 12:19 AM A. Kapetanovic <aka at alphanet.ch> wrote:
>>> Utkarsh,
>>> I did something on google drive, I shared the file with your e-mail and
>>> here you have the url :
>>> https://drive.google.com/open?id=0B_ag1ge2Wc1nSS10M1JYampTb00
>>> I hope all is OK like this, it's the first time I use google drive. Say
>>> me please if something misses.
>>> Regards   :)
>>>
>>> Le 08. 07. 15 22:47, Utkarsh Ayachit a ?crit :
>>> > Amel,
>>> >
>>> > The dataset didn't come through, I am afraid. Is it may be easier to
>>> > upload it somewhere eg. dropbox/google drive?
>>> >
>>> > Utkarsh
>>> >
>>> > On Wed, Jul 8, 2015 at 3:54 PM A. Kapetanovic <aka at alphanet.ch
>>> > <mailto:aka at alphanet.ch>> wrote:
>>> >
>>> >     WARNING: this mail was modified in transit:
>>> >         defanged (renamed/protected) 07.hdf because file type unknown.
>>> >     Rename defang-0.binary to 07.hdf if you want to access the file
>>> anyway
>>> >
>>> >     More details at:
>>> >     http://www.alphanet.ch/alphanet/anti-spam.html
>>> >     Hi,
>>> >
>>> >     Thanks for your reply.
>>> >
>>> >     Of course I have data to share. The rmed result comressed file
>>> is too
>>> >     big (35 MB), so I send here the hdf and comm files, you only
>>> need to
>>> >     compute the (3) meshes and to run the simulation to have this rmed
>>> file.
>>> >
>>> >     Say me if you need something else, I hope all is clear enough like
>>> >     this   :)
>>> >
>>> >     Amel
>>> >
>>> >
>>> >     Le 08. 07. 15 15:44, Utkarsh Ayachit a ?crit :
>>> >      > Do you have a sample dataset to share? That'll make this
>>> easier.
>>> >      >
>>> >      > Typically, movement comes from one of the following:
>>> >      > 1. Readers: the reader itself translates the points in the grid
>>> >     as time
>>> >      > changes
>>> >      > 2. Filters: if the grid doesn't change but has attributes that
>>> >     indicate
>>> >      > the displacement, one can apply a filter to transform the grid
>>> using
>>> >      > those displacement vectors.
>>> >      >
>>> >      > Utkarsh
>>> >      >
>>> >      > On Wed, Jul 8, 2015 at 3:59 AM <aka at alphanet.ch
>>> >     <mailto:aka at alphanet.ch>
>>> >      > <mailto:aka at alphanet.ch <mailto:aka at alphanet.ch>>> wrote:
>>> >      >
>>> >      >     Hi,
>>> >      >
>>> >      >     I am using Paraview with Salome-Meca + Code_Aster and I
>>> have
>>> >     e little
>>> >      >     problem : impossible to see the movement of a part that is
>>> >     moving.
>>> >      >
>>> >      >     In fact the simulation is very simple : I have 2 cylinders,
>>> >     one is
>>> >      >     fixed by
>>> >      >     one face and the other have a movement on a face. The
>>> simulation
>>> >      >     converges
>>> >      >     and when I open the mmed or rmed file (result) with
>>> Paraview,
>>> >      >     impossible to
>>> >      >     see any movement even if I clic "play".
>>> >      >
>>> >      >     Simply nothing happens.
>>> >      >
>>> >      >     Can please someone help me ?
>>> >      >
>>> >      >     Best regards,
>>> >      >
>>> >      >     Amka
>>> >      >     _______________________________________________
>>> >      >     Powered by www.kitware.com <http://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

-- 
  Michael Grabietz

  IMG - Ingenieurbuero Michael Grabietz
  Stauferring 56
  97941 Tauberbischofsheim
  Germany

  Fon: +49 9341 89 66 70
  Fax: +49 9341 89 66 71

  michael.grabietz at img-online.de
  www.img-online.de



From eric.g.younkin at noaa.gov  Fri Jul 10 11:49:18 2015
From: eric.g.younkin at noaa.gov (Eric Younkin - NOAA Federal)
Date: Fri, 10 Jul 2015 11:49:18 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAOqyOuH60D5LXthUwvSUViCWLqvrTz1z5a9wu-aCX3c4g-GEgQ@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <CAFe6qKgoBR7HU6MHCDTKr_HCxBGu_eU3St2D5+UjQ3zrBwqcbg@mail.gmail.com>
 <CAOqyOuG9-w-TFEXJO1+8EvtAQLK-JJE3Rr8XqVLG=JObe69sNg@mail.gmail.com>
 <CAFe6qKg-_LHR3tHZ10H78PZJcF2rAVV8bEOH_y_Bt0h+C9jMyw@mail.gmail.com>
 <CAFe6qKhUiTADyYM9OTyWZg5RtvctezOxnREXnL40BsR-Ny=EoA@mail.gmail.com>
 <CAOqyOuH60D5LXthUwvSUViCWLqvrTz1z5a9wu-aCX3c4g-GEgQ@mail.gmail.com>
Message-ID: <CAFe6qKhT6PvOoQRdOyAriiLJbc4D-zVJ-TtLgsyitECHCrsz8w@mail.gmail.com>

Thanks Casey.  I'm reading in the Veloview Developer guide (
https://github.com/Kitware/VeloView/tree/master/Documentation) that
Veloview requires VTK6 and Qt 4.8.  I'm currently compiling Paraview from
source using Qt5.5 and VTK libraries that came with Paraview source.  Do I
need to download VTK6 and Qt4.8 and use those?  I've had some issues with
VS2013 and compiling with Qt4.

Also, I'm currently getting the following repeating error upon configuring
in CMake:

CMake Warning (dev) in ThirdParty/QtTesting/vtkqttesting/CMakeLists.txt:
Policy CMP0020 is not set: Automatically link Qt executables to qtmain
target on Windows. Run "cmake --help-policy CMP0020" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.
This warning is for project developers. Use -Wno-dev to suppress it.

I'm seeing some references on the VTK users group (
http://public.kitware.com/pipermail/vtkusers/2013-July/080543.html) that
seem to indicate you can ignore them.  Any reason I shouldn't continue with
Qt5.5?

Thanks,
Eric

On Fri, Jul 10, 2015 at 10:43 AM, Casey Goodlett <casey.goodlett at kitware.com
> wrote:

> Eric,
>
> That paper describes the approach for filter wrapping.  You will also need
> to compile VeloView against your paraview build and then include the
> VeloView plugin alongside the PCL plugin.
>
> Hope that helps.
>
> On Thu, Jul 9, 2015 at 3:00 PM, Eric Younkin - NOAA Federal <
> eric.g.younkin at noaa.gov> wrote:
>
>> I should also mention that I have been reading this paper
>> <http://www.paraview.org/Wiki/images/1/1e/Paper.pdf> and a few other
>> sources.  I think I have a basic idea of the framework.
>>
>> On Thu, Jul 9, 2015 at 11:33 AM, Eric Younkin - NOAA Federal <
>> eric.g.younkin at noaa.gov> wrote:
>>
>>> Thanks Casey.  For someone with only moderate programming experience,
>>> how difficult would you say creating those additional wrappers and building
>>> a VLP-16 paraview plugin would be?  Do you happen to have any resources or
>>> guides for doing so?
>>>
>>> I will continue to look at building from source and check out Project
>>> Tango.  Thanks for the link.
>>>
>>> Thanks,
>>> Eric
>>>
>>> On Thu, Jul 9, 2015 at 11:14 AM, Casey Goodlett <
>>> casey.goodlett at kitware.com> wrote:
>>>
>>>>
>>>> On Thu, Jul 9, 2015 at 10:53 AM, Eric Younkin - NOAA Federal <
>>>> eric.g.younkin at noaa.gov> wrote:
>>>>
>>>>> Casey,
>>>>>
>>>>> I am mostly interested in the feature extraction routines and Paraview
>>>>> integration with the Velodyne VLP-16.  I'd like to experiment with PCL
>>>>> algorithms to try and pick out fixed objects such as buoys or piers from a
>>>>> VLP-16 mounted on our research vessel as we travel up the coast.  I think
>>>>> most of my errors are from attempting to build using Visual Studio 2013 pro
>>>>> and older Qt/PCL versions.  If I can use the most recent versions, that
>>>>> might help things.
>>>>>
>>>>
>>>> Sounds like a cool project.  You may need to add some additional
>>>> wrappers for feature extraction if you are looking for things beyond the
>>>> sample consensus models that we have.  I dont think any of the point
>>>> feature histogram utilities are currently wrapped.
>>>>
>>>> Windows builds of the whole stack are a bit tricky.  Feel free to share
>>>> your error messages, and I'll help where I can.
>>>>
>>>> The plugin does not include support for the VLP-16 in its current
>>>> state.  We have another project VeloView
>>>> <https://github.com/Kitware/VeloView> that builds a paraview plugin
>>>> for VLP-16.  I have used this in combination with the PCL plugin in the
>>>> past, but the build is not straightforward at this time.
>>>>
>>>>
>>>>
>>>>> The binaries you linked to here still require installation of Paraview
>>>>> and PCL correct?
>>>>>
>>>>>
>>>> This binary is ParaView with the pcl plugin built and packaged.  If you
>>>> download this it includes paraview and PCL.
>>>>
>>>> --
>>>> Casey B Goodlett, PhD
>>>> Technical Leader
>>>> Kitware, Inc. - North Carolina Office
>>>> http://www.kitware.com
>>>> (919) 969-6990 x310
>>>>
>>>
>>>
>>>
>>> --
>>> Eric Younkin LTJG/NOAA
>>> HSTP Liaison - East
>>> Marine Operations Center - Atlantic
>>> 439 W York St
>>> Norfolk, VA 23510
>>> Cell: 828-331-8197
>>>
>>
>>
>>
>> --
>> Eric Younkin LTJG/NOAA
>> HSTP Liaison - East
>> Marine Operations Center - Atlantic
>> 439 W York St
>> Norfolk, VA 23510
>> Cell: 828-331-8197
>>
>
>
>
> --
> Casey B Goodlett, PhD
> Technical Leader
> Kitware, Inc. - North Carolina Office
> http://www.kitware.com
> (919) 969-6990 x310
>



-- 
Eric Younkin LTJG/NOAA
HSTP Liaison - East
Marine Operations Center - Atlantic
439 W York St
Norfolk, VA 23510
Cell: 828-331-8197
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150710/9aa27a24/attachment-0001.html>

From berk.geveci at kitware.com  Fri Jul 10 11:55:08 2015
From: berk.geveci at kitware.com (Berk Geveci)
Date: Fri, 10 Jul 2015 11:55:08 -0400
Subject: [Paraview] Molecular dynamics from lammps
In-Reply-To: <1436514441.618845786@f254.i.mail.ru>
References: <1436279999.571994242@f345.i.mail.ru>
 <CAE32kpXt3KL4L5h4qXiCpvqFfAev5N-QJ91nA8Z91uVS2zv3xA@mail.gmail.com>
 <1436514441.618845786@f254.i.mail.ru>
Message-ID: <CAE32kpXwMb6ZWuVZr2AENGQX-Q3Da7uNA+Yj=3CaHQLq1bodyw@mail.gmail.com>

Let's try to refine this. How would you pick which atoms to project to the
plane? Keep the atoms that are under a certain distance to the plane? Also,
once you project the points on the plane, are you looking to interpolate
the values on the plane continuously or simply show the vectors as glyphs?

Best,
-berk


On Fri, Jul 10, 2015 at 3:47 AM, Oksana <oksana_golovnya at mail.ru> wrote:

> Berk, thank you for the reply!
>
> Yes, you are absolutely right, I need to project each closest atom to the
> slice, not the interpolation of several atoms. I do not know how to do it.
> I tried Delaunay, because it was the only solution to use Surface Vectors
> on a PolyData I have found in the mail list archive.
> I want to see projections of displacement vectors of each atom in the
> exact atom position on a slice. On a slice should be atoms belonging to the
> slice and their vectors projections.
> I thought placing each atom in one cell, and according to the output from
> the second case (when I load lammps dump) it is exactly the way paraview
> loads the file. But Surface Vectors are inactive anyway.
>
> Faithfully yours,
> Oksana.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150710/28b60cad/attachment.html>

From casey.goodlett at kitware.com  Fri Jul 10 12:03:06 2015
From: casey.goodlett at kitware.com (Casey Goodlett)
Date: Fri, 10 Jul 2015 12:03:06 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAFe6qKhT6PvOoQRdOyAriiLJbc4D-zVJ-TtLgsyitECHCrsz8w@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <CAFe6qKgoBR7HU6MHCDTKr_HCxBGu_eU3St2D5+UjQ3zrBwqcbg@mail.gmail.com>
 <CAOqyOuG9-w-TFEXJO1+8EvtAQLK-JJE3Rr8XqVLG=JObe69sNg@mail.gmail.com>
 <CAFe6qKg-_LHR3tHZ10H78PZJcF2rAVV8bEOH_y_Bt0h+C9jMyw@mail.gmail.com>
 <CAFe6qKhUiTADyYM9OTyWZg5RtvctezOxnREXnL40BsR-Ny=EoA@mail.gmail.com>
 <CAOqyOuH60D5LXthUwvSUViCWLqvrTz1z5a9wu-aCX3c4g-GEgQ@mail.gmail.com>
 <CAFe6qKhT6PvOoQRdOyAriiLJbc4D-zVJ-TtLgsyitECHCrsz8w@mail.gmail.com>
Message-ID: <CAOqyOuGCULt0Lm4GBzxSLifuv4OoVJ_G-k_rhYMpCG4XE1tPLQ@mail.gmail.com>

You should compile against the VTK of paraview.  I have not tested Qt 5.5.

I have not recently tested building VeloView  against paraview outside of
the VeloView superbuild.  There may be unexpected problems.

On Fri, Jul 10, 2015 at 11:49 AM, Eric Younkin - NOAA Federal <
eric.g.younkin at noaa.gov> wrote:

> Thanks Casey.  I'm reading in the Veloview Developer guide (
> https://github.com/Kitware/VeloView/tree/master/Documentation) that
> Veloview requires VTK6 and Qt 4.8.  I'm currently compiling Paraview from
> source using Qt5.5 and VTK libraries that came with Paraview source.  Do I
> need to download VTK6 and Qt4.8 and use those?  I've had some issues with
> VS2013 and compiling with Qt4.
>
> Also, I'm currently getting the following repeating error upon configuring
> in CMake:
>
> CMake Warning (dev) in ThirdParty/QtTesting/vtkqttesting/CMakeLists.txt:
> Policy CMP0020 is not set: Automatically link Qt executables to qtmain
> target on Windows. Run "cmake --help-policy CMP0020" for policy details.
> Use the cmake_policy command to set the policy and suppress this warning.
> This warning is for project developers. Use -Wno-dev to suppress it.
>
> I'm seeing some references on the VTK users group (
> http://public.kitware.com/pipermail/vtkusers/2013-July/080543.html) that
> seem to indicate you can ignore them.  Any reason I shouldn't continue with
> Qt5.5?
>
> Thanks,
> Eric
>
> On Fri, Jul 10, 2015 at 10:43 AM, Casey Goodlett <
> casey.goodlett at kitware.com> wrote:
>
>> Eric,
>>
>> That paper describes the approach for filter wrapping.  You will also
>> need to compile VeloView against your paraview build and then include the
>> VeloView plugin alongside the PCL plugin.
>>
>> Hope that helps.
>>
>> On Thu, Jul 9, 2015 at 3:00 PM, Eric Younkin - NOAA Federal <
>> eric.g.younkin at noaa.gov> wrote:
>>
>>> I should also mention that I have been reading this paper
>>> <http://www.paraview.org/Wiki/images/1/1e/Paper.pdf> and a few other
>>> sources.  I think I have a basic idea of the framework.
>>>
>>> On Thu, Jul 9, 2015 at 11:33 AM, Eric Younkin - NOAA Federal <
>>> eric.g.younkin at noaa.gov> wrote:
>>>
>>>> Thanks Casey.  For someone with only moderate programming experience,
>>>> how difficult would you say creating those additional wrappers and building
>>>> a VLP-16 paraview plugin would be?  Do you happen to have any resources or
>>>> guides for doing so?
>>>>
>>>> I will continue to look at building from source and check out Project
>>>> Tango.  Thanks for the link.
>>>>
>>>> Thanks,
>>>> Eric
>>>>
>>>> On Thu, Jul 9, 2015 at 11:14 AM, Casey Goodlett <
>>>> casey.goodlett at kitware.com> wrote:
>>>>
>>>>>
>>>>> On Thu, Jul 9, 2015 at 10:53 AM, Eric Younkin - NOAA Federal <
>>>>> eric.g.younkin at noaa.gov> wrote:
>>>>>
>>>>>> Casey,
>>>>>>
>>>>>> I am mostly interested in the feature extraction routines and
>>>>>> Paraview integration with the Velodyne VLP-16.  I'd like to experiment with
>>>>>> PCL algorithms to try and pick out fixed objects such as buoys or piers
>>>>>> from a VLP-16 mounted on our research vessel as we travel up the coast.  I
>>>>>> think most of my errors are from attempting to build using Visual Studio
>>>>>> 2013 pro and older Qt/PCL versions.  If I can use the most recent versions,
>>>>>> that might help things.
>>>>>>
>>>>>
>>>>> Sounds like a cool project.  You may need to add some additional
>>>>> wrappers for feature extraction if you are looking for things beyond the
>>>>> sample consensus models that we have.  I dont think any of the point
>>>>> feature histogram utilities are currently wrapped.
>>>>>
>>>>> Windows builds of the whole stack are a bit tricky.  Feel free to
>>>>> share your error messages, and I'll help where I can.
>>>>>
>>>>> The plugin does not include support for the VLP-16 in its current
>>>>> state.  We have another project VeloView
>>>>> <https://github.com/Kitware/VeloView> that builds a paraview plugin
>>>>> for VLP-16.  I have used this in combination with the PCL plugin in the
>>>>> past, but the build is not straightforward at this time.
>>>>>
>>>>>
>>>>>
>>>>>> The binaries you linked to here still require installation of
>>>>>> Paraview and PCL correct?
>>>>>>
>>>>>>
>>>>> This binary is ParaView with the pcl plugin built and packaged.  If
>>>>> you download this it includes paraview and PCL.
>>>>>
>>>>> --
>>>>> Casey B Goodlett, PhD
>>>>> Technical Leader
>>>>> Kitware, Inc. - North Carolina Office
>>>>> http://www.kitware.com
>>>>> (919) 969-6990 x310
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Eric Younkin LTJG/NOAA
>>>> HSTP Liaison - East
>>>> Marine Operations Center - Atlantic
>>>> 439 W York St
>>>> Norfolk, VA 23510
>>>> Cell: 828-331-8197
>>>>
>>>
>>>
>>>
>>> --
>>> Eric Younkin LTJG/NOAA
>>> HSTP Liaison - East
>>> Marine Operations Center - Atlantic
>>> 439 W York St
>>> Norfolk, VA 23510
>>> Cell: 828-331-8197
>>>
>>
>>
>>
>> --
>> Casey B Goodlett, PhD
>> Technical Leader
>> Kitware, Inc. - North Carolina Office
>> http://www.kitware.com
>> (919) 969-6990 x310
>>
>
>
>
> --
> Eric Younkin LTJG/NOAA
> HSTP Liaison - East
> Marine Operations Center - Atlantic
> 439 W York St
> Norfolk, VA 23510
> Cell: 828-331-8197
>



-- 
Casey B Goodlett, PhD
Technical Leader
Kitware, Inc. - North Carolina Office
http://www.kitware.com
(919) 969-6990 x310
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150710/ca5b36bb/attachment.html>

From aka at alphanet.ch  Fri Jul 10 13:48:02 2015
From: aka at alphanet.ch (A. Kapetanovic)
Date: Fri, 10 Jul 2015 19:48:02 +0200
Subject: [Paraview] Impossible to see a movement.
In-Reply-To: <559FD93C.9080106@img-online.de>
References: <20150708074214.ED383124F2D5@shakotay.alphanet.ch>
 <CADHSJjBqUBn7yScdubZkM1v4+WWi3AwegXyjuTJFuT9LjN22XA@mail.gmail.com>
 <559D7FFA.5030301@alphanet.ch>
 <CADHSJjC+cznjPdcX18140ZPEU4wqaiS8J_WF+-=4QTLFuv1aTg@mail.gmail.com>
 <559DF634.5090807@alphanet.ch>
 <CADHSJjD=Sx3BFrKQZ3+PBWB1eG+qE+hnmu3=2EE9L_9voe1wPw@mail.gmail.com>
 <20150710072745.DC6FF1252212@shakotay.alphanet.ch>
 <559FD93C.9080106@img-online.de>
Message-ID: <55A00552.2090601@alphanet.ch>

Hi Michael,

Here you have the dropbox link for my rmed file :

https://www.dropbox.com/s/e5ub600ygmzyzf6/07b.rmed.zip?dl=0

Amel

Le 10. 07. 15 16:39, Michael Grabietz a ?crit :
> Hi Amel,
>
> I followed the discussion between Utkarsh and you on this topic. Could
> you share the rmed file from Code-Aster? The download from your google
> drive seems to be restricted to specific email addresses.
>
> Michael
>
> Am 10.07.2015 um 09:27 schrieb aka at alphanet.ch:
>> Utarsh,
>> Thank you for your reply, I will try to do what you say this week-end.
>> Another fact is a few strange : when I opened my rmed file with Paraview
>> (using for this the
>> http://www.alneos.com/telechargement/paraview-avec-med software), I
>> simply could clic on the "Wrap" button (or a name near that) and, when I
>> clic "Play" after I can see the movement...
>> This same "Wrap" button is disabled (for this simualtion) in my
>> Salome-Meca Paraview module, with which I work, and I don't understand
>> why...
>> Amel
>>
>> Utkarsh Ayachit writes:
>>> Amel,
>>> What's the Result_DEPL array? Is that displacement? Assuming that, I
>>> applied two calculators: first to convert the Result_DEPL array to a 3
>>> component vector and the second to translate the coordinate positions
>>> using
>>> the vector computed by the previous one. If the Result_DEPL changes in
>>> your
>>> dataset over time, you'll see the movement.
>>> State file attached.
>>> Utarsh
>>> On Thu, Jul 9, 2015 at 12:19 AM A. Kapetanovic <aka at alphanet.ch> wrote:
>>>> Utkarsh,
>>>> I did something on google drive, I shared the file with your e-mail and
>>>> here you have the url :
>>>> https://drive.google.com/open?id=0B_ag1ge2Wc1nSS10M1JYampTb00
>>>> I hope all is OK like this, it's the first time I use google drive. Say
>>>> me please if something misses.
>>>> Regards   :)
>>>>
>>>> Le 08. 07. 15 22:47, Utkarsh Ayachit a ?crit :
>>>> > Amel,
>>>> >
>>>> > The dataset didn't come through, I am afraid. Is it may be easier to
>>>> > upload it somewhere eg. dropbox/google drive?
>>>> >
>>>> > Utkarsh
>>>> >
>>>> > On Wed, Jul 8, 2015 at 3:54 PM A. Kapetanovic <aka at alphanet.ch
>>>> > <mailto:aka at alphanet.ch>> wrote:
>>>> >
>>>> >     WARNING: this mail was modified in transit:
>>>> >         defanged (renamed/protected) 07.hdf because file type
>>>> unknown.
>>>> >     Rename defang-0.binary to 07.hdf if you want to access the file
>>>> anyway
>>>> >
>>>> >     More details at:
>>>> >     http://www.alphanet.ch/alphanet/anti-spam.html
>>>> >     Hi,
>>>> >
>>>> >     Thanks for your reply.
>>>> >
>>>> >     Of course I have data to share. The rmed result comressed file
>>>> is too
>>>> >     big (35 MB), so I send here the hdf and comm files, you only
>>>> need to
>>>> >     compute the (3) meshes and to run the simulation to have this
>>>> rmed
>>>> file.
>>>> >
>>>> >     Say me if you need something else, I hope all is clear enough
>>>> like
>>>> >     this   :)
>>>> >
>>>> >     Amel
>>>> >
>>>> >
>>>> >     Le 08. 07. 15 15:44, Utkarsh Ayachit a ?crit :
>>>> >      > Do you have a sample dataset to share? That'll make this
>>>> easier.
>>>> >      >
>>>> >      > Typically, movement comes from one of the following:
>>>> >      > 1. Readers: the reader itself translates the points in the
>>>> grid
>>>> >     as time
>>>> >      > changes
>>>> >      > 2. Filters: if the grid doesn't change but has attributes that
>>>> >     indicate
>>>> >      > the displacement, one can apply a filter to transform the grid
>>>> using
>>>> >      > those displacement vectors.
>>>> >      >
>>>> >      > Utkarsh
>>>> >      >
>>>> >      > On Wed, Jul 8, 2015 at 3:59 AM <aka at alphanet.ch
>>>> >     <mailto:aka at alphanet.ch>
>>>> >      > <mailto:aka at alphanet.ch <mailto:aka at alphanet.ch>>> wrote:
>>>> >      >
>>>> >      >     Hi,
>>>> >      >
>>>> >      >     I am using Paraview with Salome-Meca + Code_Aster and I
>>>> have
>>>> >     e little
>>>> >      >     problem : impossible to see the movement of a part that is
>>>> >     moving.
>>>> >      >
>>>> >      >     In fact the simulation is very simple : I have 2
>>>> cylinders,
>>>> >     one is
>>>> >      >     fixed by
>>>> >      >     one face and the other have a movement on a face. The
>>>> simulation
>>>> >      >     converges
>>>> >      >     and when I open the mmed or rmed file (result) with
>>>> Paraview,
>>>> >      >     impossible to
>>>> >      >     see any movement even if I clic "play".
>>>> >      >
>>>> >      >     Simply nothing happens.
>>>> >      >
>>>> >      >     Can please someone help me ?
>>>> >      >
>>>> >      >     Best regards,
>>>> >      >
>>>> >      >     Amka
>>>> >      >     _______________________________________________
>>>> >      >     Powered by www.kitware.com <http://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
>

From wascott at sandia.gov  Fri Jul 10 14:12:57 2015
From: wascott at sandia.gov (Scott, W Alan)
Date: Fri, 10 Jul 2015 18:12:57 +0000
Subject: [Paraview] Superbuild
Message-ID: <7d58cb83b51047629cb52a22b8b55a8b@ES01AMSNLNT.srn.sandia.gov>

I created a superbuild yesterday, and now when I run ParaView, I see the following error.  Then, Linux basically locks up.  I also get the second line below in the ParaView Output window.  Has anyone else seen this?

Thanks,

Alan

(<unknown>:19814): Gtk-WARNING **: Attempt to load unknown IM context type 'gtk-im-context-none'
QXcbConnection: XCB error: 177 (Unknown), sequence: 161, resource id: 0, major code: 152 (Unknown), minor code: 20 (:0, )


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

From cory.quammen at kitware.com  Fri Jul 10 17:19:07 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 10 Jul 2015 16:19:07 -0500
Subject: [Paraview] Custom animation help? (Corrected image)
In-Reply-To: <A9BF9A24-AFD8-41DD-8F0C-446AD9B8702C@udel.edu>
References: <A9BF9A24-AFD8-41DD-8F0C-446AD9B8702C@udel.edu>
Message-ID: <CAB5Fpx7yjsZEwk5MtCMVuJ5cVtga=zpfF9rK4S42snNkamAO=A@mail.gmail.com>

Hi Jesse,

It should be possible to do this. See Chapter 7 of the ParaView User Guide
[1] or Section 2.13 or the ParaView Tutorial [2] for more information.

[1] http://www.paraview.org/paraview-guide/
[2] http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf

HTH,
Cory

On Mon, Jul 6, 2015 at 8:56 AM, Jesse Samluk <sevensam at udel.edu> wrote:

> Greetings all,
>
>   I sent this message last week, but errantly sent the .tif image which
> made it a huge file. The JPG is now attached.
>
>    I?m trying to make an animation in Paraview. I took a stab at it before
> with Paraview, but I recall it as being tedious. Maybe I can get some
> pointers from the experts.
>
>   So, the attached imaged is a cube view of the electromagnetic response
> over sea ice. What Im trying to do with this animation is two things:
>
>   1.) Move the horizontal slice and Y-Z vertical slice (the slice without
> the tubes) up and down, and side to side, respectively, such that as if you
> selected the particular slide in the Pipeline browser, you could drag the
> slice in question and move it manually to see the different responses.
> Therefore I?m trying to automate it.
>
>   2.) Rotate it about the z-axis 5 degrees (to about 180) at each
> iteration and return, then rotate it 5 degrees at each iteration about the
> y-axis (till about 45 degrees) and return. These rotations will occur while
> ?action item" 1 is happening.
>
>    Any thoughts/suggestions?
>
>     Thanks!
>     Jesse
>
> _______________________________________________
> 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
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150710/fca2e837/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: YZPlaneInitialForParaview.jpeg
Type: image/jpeg
Size: 27388 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150710/fca2e837/attachment.jpeg>

From dan.lipsa at kitware.com  Fri Jul 10 17:34:48 2015
From: dan.lipsa at kitware.com (Dan Lipsa)
Date: Fri, 10 Jul 2015 21:34:48 +0000
Subject: [Paraview] Custom animation help? (Corrected image)
In-Reply-To: <CAB5Fpx7yjsZEwk5MtCMVuJ5cVtga=zpfF9rK4S42snNkamAO=A@mail.gmail.com>
References: <A9BF9A24-AFD8-41DD-8F0C-446AD9B8702C@udel.edu>
 <CAB5Fpx7yjsZEwk5MtCMVuJ5cVtga=zpfF9rK4S42snNkamAO=A@mail.gmail.com>
Message-ID: <CADwGrVpXTnqgaD_DciowFwe2pc6KC6r332jLwKBnAESWBjkYKQ@mail.gmail.com>

Jesse,
See also the following thread:

http://markmail.org/search/?q=+programmimg+the+camera+position+using+python#query:%20programmimg%20the%20camera%20position%20using%20python+page:1+mid:nkm5rmw2hz52egnk+state:results

On Fri, Jul 10, 2015 at 5:19 PM Cory Quammen <cory.quammen at kitware.com>
wrote:

> Hi Jesse,
>
> It should be possible to do this. See Chapter 7 of the ParaView User Guide
> [1] or Section 2.13 or the ParaView Tutorial [2] for more information.
>
> [1] http://www.paraview.org/paraview-guide/
> [2] http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf
>
> HTH,
> Cory
>
> On Mon, Jul 6, 2015 at 8:56 AM, Jesse Samluk <sevensam at udel.edu> wrote:
>
>> Greetings all,
>>
>>   I sent this message last week, but errantly sent the .tif image which
>> made it a huge file. The JPG is now attached.
>>
>>    I?m trying to make an animation in Paraview. I took a stab at it
>> before with Paraview, but I recall it as being tedious. Maybe I can get
>> some pointers from the experts.
>>
>>   So, the attached imaged is a cube view of the electromagnetic response
>> over sea ice. What Im trying to do with this animation is two things:
>>
>>   1.) Move the horizontal slice and Y-Z vertical slice (the slice without
>> the tubes) up and down, and side to side, respectively, such that as if you
>> selected the particular slide in the Pipeline browser, you could drag the
>> slice in question and move it manually to see the different responses.
>> Therefore I?m trying to automate it.
>>
>>   2.) Rotate it about the z-axis 5 degrees (to about 180) at each
>> iteration and return, then rotate it 5 degrees at each iteration about the
>> y-axis (till about 45 degrees) and return. These rotations will occur while
>> ?action item" 1 is happening.
>>
>>    Any thoughts/suggestions?
>>
>>     Thanks!
>>     Jesse
>>
>> _______________________________________________
>> 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
>>
>>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>  _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150710/04f22149/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: YZPlaneInitialForParaview.jpeg
Type: image/jpeg
Size: 27388 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150710/04f22149/attachment.jpeg>

From wascott at sandia.gov  Fri Jul 10 20:16:19 2015
From: wascott at sandia.gov (Scott, W Alan)
Date: Sat, 11 Jul 2015 00:16:19 +0000
Subject: [Paraview] Qt
Message-ID: <86722d04089940a18075b985091086b1@ES01AMSNLNT.srn.sandia.gov>

I notice that the Superbuild is running Qt 5.4.1.  Any idea where I can find the Windows installer (i.e., I don't want to build from source)?

Thanks!

Alan



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

From eric.g.younkin at noaa.gov  Fri Jul 10 20:32:07 2015
From: eric.g.younkin at noaa.gov (Eric Younkin - NOAA Federal)
Date: Fri, 10 Jul 2015 20:32:07 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAOqyOuGCULt0Lm4GBzxSLifuv4OoVJ_G-k_rhYMpCG4XE1tPLQ@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <CAFe6qKgoBR7HU6MHCDTKr_HCxBGu_eU3St2D5+UjQ3zrBwqcbg@mail.gmail.com>
 <CAOqyOuG9-w-TFEXJO1+8EvtAQLK-JJE3Rr8XqVLG=JObe69sNg@mail.gmail.com>
 <CAFe6qKg-_LHR3tHZ10H78PZJcF2rAVV8bEOH_y_Bt0h+C9jMyw@mail.gmail.com>
 <CAFe6qKhUiTADyYM9OTyWZg5RtvctezOxnREXnL40BsR-Ny=EoA@mail.gmail.com>
 <CAOqyOuH60D5LXthUwvSUViCWLqvrTz1z5a9wu-aCX3c4g-GEgQ@mail.gmail.com>
 <CAFe6qKhT6PvOoQRdOyAriiLJbc4D-zVJ-TtLgsyitECHCrsz8w@mail.gmail.com>
 <CAOqyOuGCULt0Lm4GBzxSLifuv4OoVJ_G-k_rhYMpCG4XE1tPLQ@mail.gmail.com>
Message-ID: <CAFe6qKhhgem8+jPVRyJoaQrY-WJgW3vne7xDFHP41w332FWQPA@mail.gmail.com>

Casey,

When building Paraview 4.3.1 from source with QT5.5 in Visual Studio 2013,
I get 3 failed out of 569.  I pasted in the relevant parts of the VS output
log below (full log too big to attach):

567>  Generating Code...
567>     Creating library
C:/Users/eric.g.younkin/Documents/PCL_ParaView/ParaView-v4.3.1-source/build/lib/Debug/MobileRemoteControl.lib
and object
C:/Users/eric.g.younkin/Documents/PCL_ParaView/ParaView-v4.3.1-source/build/lib/Debug/MobileRemoteControl.exp
567>  MobileRemoteControl.vcxproj ->
C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\bin\Debug\MobileRemoteControl.dll
568>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(607,5):
error MSB6006: "link.exe" exited with code 1120.
568>MSVCRTD.lib(crtexew.obj) : error LNK2019: unresolved external symbol
WinMain referenced in function __tmainCRTStartup
568>C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\bin\Debug\paraview.exe
: fatal error LNK1120: 1 unresolved externals
569>------ Build started: Project: ALL_BUILD, Configuration: Debug x64
------
569>  Building Custom Rule
C:/Users/eric.g.younkin/Documents/PCL_ParaView/ParaView-v4.3.1-source/CMakeLists.txt
569>  CMake does not need to re-run because
C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\CMakeFiles\generate.stamp
is up-to-date.
========== Build: 566 succeeded, 3 failed, 0 up-to-date, 0 skipped
==========

Doing some Google searches seem to indicate that in order to clear the
LNK2019 error, I would need to change the project type
<http://stackoverflow.com/questions/6626397/error-lnk2019-unresolved-external-symbol-winmain16-referenced-in-function>.
And that in order to do that, I would need to change the configuration
type from
utility to something else
<http://gotoanswer.com/?q=No+Linker+option+in+Visual+Studio+Project+Properties>
.

I suspect that I am just missing something obvious, but I'm not sure what
it is.  Can you offer any advice?

Thanks,
Eric

On Fri, Jul 10, 2015 at 12:03 PM, Casey Goodlett <casey.goodlett at kitware.com
> wrote:

> You should compile against the VTK of paraview.  I have not tested Qt 5.5.
>
> I have not recently tested building VeloView  against paraview outside of
> the VeloView superbuild.  There may be unexpected problems.
>
> On Fri, Jul 10, 2015 at 11:49 AM, Eric Younkin - NOAA Federal <
> eric.g.younkin at noaa.gov> wrote:
>
>> Thanks Casey.  I'm reading in the Veloview Developer guide (
>> https://github.com/Kitware/VeloView/tree/master/Documentation) that
>> Veloview requires VTK6 and Qt 4.8.  I'm currently compiling Paraview from
>> source using Qt5.5 and VTK libraries that came with Paraview source.  Do I
>> need to download VTK6 and Qt4.8 and use those?  I've had some issues with
>> VS2013 and compiling with Qt4.
>>
>> Also, I'm currently getting the following repeating error upon
>> configuring in CMake:
>>
>> CMake Warning (dev) in ThirdParty/QtTesting/vtkqttesting/CMakeLists.txt:
>> Policy CMP0020 is not set: Automatically link Qt executables to qtmain
>> target on Windows. Run "cmake --help-policy CMP0020" for policy details.
>> Use the cmake_policy command to set the policy and suppress this warning.
>> This warning is for project developers. Use -Wno-dev to suppress it.
>>
>> I'm seeing some references on the VTK users group (
>> http://public.kitware.com/pipermail/vtkusers/2013-July/080543.html) that
>> seem to indicate you can ignore them.  Any reason I shouldn't continue with
>> Qt5.5?
>>
>> Thanks,
>> Eric
>>
>> On Fri, Jul 10, 2015 at 10:43 AM, Casey Goodlett <
>> casey.goodlett at kitware.com> wrote:
>>
>>> Eric,
>>>
>>> That paper describes the approach for filter wrapping.  You will also
>>> need to compile VeloView against your paraview build and then include the
>>> VeloView plugin alongside the PCL plugin.
>>>
>>> Hope that helps.
>>>
>>> On Thu, Jul 9, 2015 at 3:00 PM, Eric Younkin - NOAA Federal <
>>> eric.g.younkin at noaa.gov> wrote:
>>>
>>>> I should also mention that I have been reading this paper
>>>> <http://www.paraview.org/Wiki/images/1/1e/Paper.pdf> and a few other
>>>> sources.  I think I have a basic idea of the framework.
>>>>
>>>> On Thu, Jul 9, 2015 at 11:33 AM, Eric Younkin - NOAA Federal <
>>>> eric.g.younkin at noaa.gov> wrote:
>>>>
>>>>> Thanks Casey.  For someone with only moderate programming experience,
>>>>> how difficult would you say creating those additional wrappers and building
>>>>> a VLP-16 paraview plugin would be?  Do you happen to have any resources or
>>>>> guides for doing so?
>>>>>
>>>>> I will continue to look at building from source and check out Project
>>>>> Tango.  Thanks for the link.
>>>>>
>>>>> Thanks,
>>>>> Eric
>>>>>
>>>>> On Thu, Jul 9, 2015 at 11:14 AM, Casey Goodlett <
>>>>> casey.goodlett at kitware.com> wrote:
>>>>>
>>>>>>
>>>>>> On Thu, Jul 9, 2015 at 10:53 AM, Eric Younkin - NOAA Federal <
>>>>>> eric.g.younkin at noaa.gov> wrote:
>>>>>>
>>>>>>> Casey,
>>>>>>>
>>>>>>> I am mostly interested in the feature extraction routines and
>>>>>>> Paraview integration with the Velodyne VLP-16.  I'd like to experiment with
>>>>>>> PCL algorithms to try and pick out fixed objects such as buoys or piers
>>>>>>> from a VLP-16 mounted on our research vessel as we travel up the coast.  I
>>>>>>> think most of my errors are from attempting to build using Visual Studio
>>>>>>> 2013 pro and older Qt/PCL versions.  If I can use the most recent versions,
>>>>>>> that might help things.
>>>>>>>
>>>>>>
>>>>>> Sounds like a cool project.  You may need to add some additional
>>>>>> wrappers for feature extraction if you are looking for things beyond the
>>>>>> sample consensus models that we have.  I dont think any of the point
>>>>>> feature histogram utilities are currently wrapped.
>>>>>>
>>>>>> Windows builds of the whole stack are a bit tricky.  Feel free to
>>>>>> share your error messages, and I'll help where I can.
>>>>>>
>>>>>> The plugin does not include support for the VLP-16 in its current
>>>>>> state.  We have another project VeloView
>>>>>> <https://github.com/Kitware/VeloView> that builds a paraview plugin
>>>>>> for VLP-16.  I have used this in combination with the PCL plugin in the
>>>>>> past, but the build is not straightforward at this time.
>>>>>>
>>>>>>
>>>>>>
>>>>>>> The binaries you linked to here still require installation of
>>>>>>> Paraview and PCL correct?
>>>>>>>
>>>>>>>
>>>>>> This binary is ParaView with the pcl plugin built and packaged.  If
>>>>>> you download this it includes paraview and PCL.
>>>>>>
>>>>>> --
>>>>>> Casey B Goodlett, PhD
>>>>>> Technical Leader
>>>>>> Kitware, Inc. - North Carolina Office
>>>>>> http://www.kitware.com
>>>>>> (919) 969-6990 x310
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Eric Younkin LTJG/NOAA
>>>>> HSTP Liaison - East
>>>>> Marine Operations Center - Atlantic
>>>>> 439 W York St
>>>>> Norfolk, VA 23510
>>>>> Cell: 828-331-8197
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Eric Younkin LTJG/NOAA
>>>> HSTP Liaison - East
>>>> Marine Operations Center - Atlantic
>>>> 439 W York St
>>>> Norfolk, VA 23510
>>>> Cell: 828-331-8197
>>>>
>>>
>>>
>>>
>>> --
>>> Casey B Goodlett, PhD
>>> Technical Leader
>>> Kitware, Inc. - North Carolina Office
>>> http://www.kitware.com
>>> (919) 969-6990 x310
>>>
>>
>>
>>
>> --
>> Eric Younkin LTJG/NOAA
>> HSTP Liaison - East
>> Marine Operations Center - Atlantic
>> 439 W York St
>> Norfolk, VA 23510
>> Cell: 828-331-8197
>>
>
>
>
> --
> Casey B Goodlett, PhD
> Technical Leader
> Kitware, Inc. - North Carolina Office
> http://www.kitware.com
> (919) 969-6990 x310
>



-- 
Eric Younkin LTJG/NOAA
HSTP Liaison - East
Marine Operations Center - Atlantic
439 W York St
Norfolk, VA 23510
Cell: 828-331-8197
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150710/d5c5b067/attachment.html>

From aka at alphanet.ch  Sat Jul 11 05:25:39 2015
From: aka at alphanet.ch (A. Kapetanovic)
Date: Sat, 11 Jul 2015 11:25:39 +0200
Subject: [Paraview] Impossible to see a movement.
In-Reply-To: <CADHSJjD=Sx3BFrKQZ3+PBWB1eG+qE+hnmu3=2EE9L_9voe1wPw@mail.gmail.com>
References: <20150708074214.ED383124F2D5@shakotay.alphanet.ch>
 <CADHSJjBqUBn7yScdubZkM1v4+WWi3AwegXyjuTJFuT9LjN22XA@mail.gmail.com>
 <559D7FFA.5030301@alphanet.ch>
 <CADHSJjC+cznjPdcX18140ZPEU4wqaiS8J_WF+-=4QTLFuv1aTg@mail.gmail.com>
 <559DF634.5090807@alphanet.ch>
 <CADHSJjD=Sx3BFrKQZ3+PBWB1eG+qE+hnmu3=2EE9L_9voe1wPw@mail.gmail.com>
Message-ID: <55A0E113.3000207@alphanet.ch>

Utarsh,

Yes, I think that DEPL is "d?placement" in French - that is displacement 
in English.

I tried to do the job. I opened with Paraview my vtm file with all the 
timesteps, I copied pasted the formulas of the two calculators I found 
in your state file in my two calculators, but no movement if I clic play.

Probably I did something wrong...

Amel


Le 09. 07. 15 23:05, Utkarsh Ayachit a ?crit :
> Amel,
>
> What's the Result_DEPL array? Is that displacement? Assuming that, I
> applied two calculators: first to convert the Result_DEPL array to a 3
> component vector and the second to translate the coordinate positions
> using the vector computed by the previous one. If the Result_DEPL
> changes in your dataset over time, you'll see the movement.
>
> State file attached.
>
> Utarsh
>
> On Thu, Jul 9, 2015 at 12:19 AM A. Kapetanovic <aka at alphanet.ch
> <mailto:aka at alphanet.ch>> wrote:
>
>     Utkarsh,
>
>     I did something on google drive, I shared the file with your e-mail and
>     here you have the url :
>
>     https://drive.google.com/open?id=0B_ag1ge2Wc1nSS10M1JYampTb00
>
>     I hope all is OK like this, it's the first time I use google drive. Say
>     me please if something misses.
>
>     Regards   :)
>
>
>     Le 08. 07. 15 22:47, Utkarsh Ayachit a ?crit :
>      > Amel,
>      >
>      > The dataset didn't come through, I am afraid. Is it may be easier to
>      > upload it somewhere eg. dropbox/google drive?
>      >
>      > Utkarsh
>      >
>      > On Wed, Jul 8, 2015 at 3:54 PM A. Kapetanovic <aka at alphanet.ch
>     <mailto:aka at alphanet.ch>
>      > <mailto:aka at alphanet.ch <mailto:aka at alphanet.ch>>> wrote:
>      >
>      >     WARNING: this mail was modified in transit:
>      >         defanged (renamed/protected) 07.hdf because file type
>     unknown.
>      >     Rename defang-0.binary to 07.hdf if you want to access the
>     file anyway
>      >
>      >     More details at:
>      > http://www.alphanet.ch/alphanet/anti-spam.html
>      >     Hi,
>      >
>      >     Thanks for your reply.
>      >
>      >     Of course I have data to share. The rmed result comressed
>     file is too
>      >     big (35 MB), so I send here the hdf and comm files, you only
>     need to
>      >     compute the (3) meshes and to run the simulation to have this
>     rmed file.
>      >
>      >     Say me if you need something else, I hope all is clear enough
>     like
>      >     this   :)
>      >
>      >     Amel
>      >
>      >
>      >     Le 08. 07. 15 15:44, Utkarsh Ayachit a ?crit :
>      >      > Do you have a sample dataset to share? That'll make this
>     easier.
>      >      >
>      >      > Typically, movement comes from one of the following:
>      >      > 1. Readers: the reader itself translates the points in the
>     grid
>      >     as time
>      >      > changes
>      >      > 2. Filters: if the grid doesn't change but has attributes that
>      >     indicate
>      >      > the displacement, one can apply a filter to transform the
>     grid using
>      >      > those displacement vectors.
>      >      >
>      >      > Utkarsh
>      >      >
>      >      > On Wed, Jul 8, 2015 at 3:59 AM <aka at alphanet.ch
>     <mailto:aka at alphanet.ch>
>      >     <mailto:aka at alphanet.ch <mailto:aka at alphanet.ch>>
>      >      > <mailto:aka at alphanet.ch <mailto:aka at alphanet.ch>
>     <mailto:aka at alphanet.ch <mailto:aka at alphanet.ch>>>> wrote:
>      >      >
>      >      >     Hi,
>      >      >
>      >      >     I am using Paraview with Salome-Meca + Code_Aster and
>     I have
>      >     e little
>      >      >     problem : impossible to see the movement of a part that is
>      >     moving.
>      >      >
>      >      >     In fact the simulation is very simple : I have 2
>     cylinders,
>      >     one is
>      >      >     fixed by
>      >      >     one face and the other have a movement on a face. The
>     simulation
>      >      >     converges
>      >      >     and when I open the mmed or rmed file (result) with
>     Paraview,
>      >      >     impossible to
>      >      >     see any movement even if I clic "play".
>      >      >
>      >      >     Simply nothing happens.
>      >      >
>      >      >     Can please someone help me ?
>      >      >
>      >      >     Best regards,
>      >      >
>      >      >     Amka
>      >      >     _______________________________________________
>      >      >     Powered by www.kitware.com <http://www.kitware.com>
>     <http://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
>      >      >
>      >
>

From sergi.mateo.bellido at gmail.com  Sat Jul 11 05:32:30 2015
From: sergi.mateo.bellido at gmail.com (Sergi Mateo Bellido)
Date: Sat, 11 Jul 2015 11:32:30 +0200
Subject: [Paraview] segfault playing a simulation
In-Reply-To: <CAB5Fpx7AdTrtGAsq9OjoW36=-dWFDzUAGrtCF+fqqa4hLenoDg@mail.gmail.com>
References: <55895735.2030202@gmail.com>	<CAB5Fpx4BDY+JDKBbA5Lt02Yt1RLaaZY6TPW9azpZsGf-aWTD7Q@mail.gmail.com>	<559381DE.5030504@gmail.com>	<CAB5Fpx6H7dY-j86vut03OuVr+7smd+1YwGqL2e771tRE0xdkxw@mail.gmail.com>	<559422EF.3070304@gmail.com>
 <CAB5Fpx7AdTrtGAsq9OjoW36=-dWFDzUAGrtCF+fqqa4hLenoDg@mail.gmail.com>
Message-ID: <55A0E2AE.5050101@gmail.com>

Hi Cory,

Thanks for your time. I have been playing a bit with the files too and I 
realized that replacing the whole_extent of each *.vti  by the whole 
dataset everything works.

I would like to generate something like this: 
http://vtk.1045678.n5.nabble.com/Example-vti-file-td3381382.html . In 
this example, each imagedata has whole_extent=whole size but its pieces 
only contain a portion of the whole dataset. Does this configuration 
make sense?

I have been trying to generate something like that but I failed. My code 
looks like this one: 
http://www.vtk.org/Wiki/VTK/Examples/Cxx/IO/WriteVTI but using 
VtkFloatArray as buffers and attaching them to the VtkImageData. I tried 
defining the set of the VtkImageData as the whole dataset and defining 
the VtkFloatArrays of the size of each portion but it didn't work :(

Any clue?

Thanks!
Sergi

On 07/09/2015 05:00 PM, Cory Quamen wrote:
> Hi Sergi,
>
> I played with your data set a little but haven't found what is wrong. 
> I am suspicious of two things in the data file, the extent and the 
> offset in the second data array (it looks too small).
>
> What are the dimensions of your grid? Note that the whole extent upper 
> values need to be the dimension - 1, e.g., for a 300x300x300 grid, the 
> whole extent should be 0 299 0 299 0 299.
>
> Thanks,
> Cory
>
> On Wed, Jul 1, 2015 at 12:27 PM, Sergi Mateo Bellido 
> <sergi.mateo.bellido at gmail.com <mailto:sergi.mateo.bellido at gmail.com>> 
> wrote:
>
>     Hi Cory,
>
>     Thanks for your time. These data files have been produced by a
>     software that I'm developing with some colleagues.
>
>     Best regards,
>
>     Sergi
>
>
>     On 07/01/2015 03:59 PM, Cory Quammen wrote:
>>     Sergi,
>>
>>     I can confirm the crash you are seeing in the same location in
>>     the code. I'm looking for the cause.
>>
>>     What software produced these data files?
>>
>>     Thanks,
>>     Cory
>>
>>     On Wed, Jul 1, 2015 at 1:59 AM, Sergi Mateo Bellido
>>     <sergi.mateo.bellido at gmail.com
>>     <mailto:sergi.mateo.bellido at gmail.com>> wrote:
>>
>>         Hi Cory,
>>
>>         Thanks for your answer. I reproduced the segfault in two
>>         different ways, but it's always after loading a data set:
>>         - After loading a data set, I tried to play the simulation
>>         ->segfault
>>         - After loading a data set, I tried to filter some fields
>>         from the model (Pointer array status). As soon as I clicked
>>         the 'apply' button, paraview crashed with a segfault.
>>
>>         Thanks,
>>         Sergi
>>
>>
>>
>>         On 06/30/2015 06:21 AM, Cory Quammen wrote:
>>>         Hi Sergi,
>>>
>>>         Could you clarify when you are seeing this crash? Is it
>>>         right when starting ParaView or when first loading a data set?
>>>
>>>         Thanks,
>>>         Cory
>>>
>>>         On Tue, Jun 23, 2015 at 8:55 AM, Sergi Mateo Bellido
>>>         <sergi.mateo.bellido at gmail.com
>>>         <mailto:sergi.mateo.bellido at gmail.com>> wrote:
>>>
>>>             Hi,
>>>
>>>             I'm trying to reproduce a simulation with ParaView 4.3.1
>>>             and it always crashes when I start it. You can find the
>>>             backtrace below:
>>>
>>>             =========================================================
>>>             Process id 6681 Caught SIGSEGV at 0x925b124 address not
>>>             mapped to object
>>>             Program Stack:
>>>             WARNING: The stack trace will not use advanced
>>>             capabilities because this is a release build.
>>>             0x7f54ce081d40 : ??? [(???) ???:-1]
>>>             0x7f54ce19caf6 : ??? [(???) ???:-1]
>>>             0x7f54cb123736 :
>>>             vtkXMLPStructuredDataReader::CopySubExtent(int*, int*,
>>>             long long*, int*, int*, long long*, int*, int*,
>>>             vtkDataArray*, vtkDataArray*) [(libvtkIOXML-pv4.3.so.1)
>>>             ???:-1]
>>>             0x7f54cb12389f :
>>>             vtkXMLPStructuredDataReader::CopyArrayForPoints(vtkDataArray*,
>>>             vtkDataArray*) [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>             0x7f54cb11cc1f : vtkXMLPDataReader::ReadPieceData()
>>>             [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>             0x7f54cb11ca14 : vtkXMLPDataReader::ReadPieceData(int)
>>>             [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>             0x7f54cb124d7a :
>>>             vtkXMLPStructuredDataReader::ReadXMLData()
>>>             [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>             0x7f54cb1280eb :
>>>             vtkXMLReader::RequestData(vtkInformation*,
>>>             vtkInformationVector**, vtkInformationVector*)
>>>             [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>             0x7f54cb1273b6 :
>>>             vtkXMLReader::ProcessRequest(vtkInformation*,
>>>             vtkInformationVector**, vtkInformationVector*)
>>>             [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>             0x7f54cd6200f9 :
>>>             vtkFileSeriesReader::RequestData(vtkInformation*,
>>>             vtkInformationVector**, vtkInformationVector*)
>>>             [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1]
>>>             0x7f54cd61f07f :
>>>             vtkFileSeriesReader::ProcessRequest(vtkInformation*,
>>>             vtkInformationVector**, vtkInformationVector*)
>>>             [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1]
>>>             0x7f54d2706204 :
>>>             vtkExecutive::CallAlgorithm(vtkInformation*, int,
>>>             vtkInformationVector**, vtkInformationVector*)
>>>             [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>             0x7f54d27016cc :
>>>             vtkDemandDrivenPipeline::ExecuteData(vtkInformation*,
>>>             vtkInformationVector**, vtkInformationVector*)
>>>             [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>             0x7f54d2700201 :
>>>             vtkCompositeDataPipeline::ExecuteData(vtkInformation*,
>>>             vtkInformationVector**, vtkInformationVector*)
>>>             [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>             0x7f54d2704067 :
>>>             vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>             vtkInformationVector**, vtkInformationVector*)
>>>             [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>             0x7f54d271d959 :
>>>             vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>             vtkInformationVector**, vtkInformationVector*)
>>>             [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>             0x7f54d26fe387 :
>>>             vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*)
>>>             [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>             0x7f54d2704010 :
>>>             vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>             vtkInformationVector**, vtkInformationVector*)
>>>             [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>             0x7f54d271d959 :
>>>             vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>             vtkInformationVector**, vtkInformationVector*)
>>>             [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>             0x7f54d26fe387 :
>>>             vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*)
>>>             [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>             0x7f54d2704010 :
>>>             vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>             vtkInformationVector**, vtkInformationVector*)
>>>             [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>             0x7f54d271d959 :
>>>             vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>             vtkInformationVector**, vtkInformationVector*)
>>>             [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>             0x7f54d27035ae :
>>>             vtkDemandDrivenPipeline::UpdateData(int)
>>>             [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>             0x7f54d271e87f :
>>>             vtkStreamingDemandDrivenPipeline::Update(int)
>>>             [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>             0x7f54cd98fa7f :
>>>             vtkPVDataRepresentation::ProcessViewRequest(vtkInformationRequestKey*,
>>>             vtkInformation*, vtkInformation*)
>>>             [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>             0x7f54cd973d79 :
>>>             vtkGeometryRepresentation::ProcessViewRequest(vtkInformationRequestKey*,
>>>             vtkInformation*, vtkInformation*)
>>>             [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>             0x7f54cd975d71 :
>>>             vtkGeometryRepresentationWithFaces::ProcessViewRequest(vtkInformationRequestKey*,
>>>             vtkInformation*, vtkInformation*)
>>>             [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>             0x7f54cd9bd388 :
>>>             vtkPVView::CallProcessViewRequest(vtkInformationRequestKey*,
>>>             vtkInformation*, vtkInformationVector*)
>>>             [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>             0x7f54cd9bd552 : vtkPVView::Update()
>>>             [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>             0x7f54cd9acb78 : vtkPVRenderView::Update()
>>>             [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>             0x7f54d780ac30 :
>>>             vtkPVRenderViewCommand(vtkClientServerInterpreter*,
>>>             vtkObjectBase*, char const*, vtkClientServerStream
>>>             const&, vtkClientServerStream&, void*)
>>>             [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1]
>>>             0x7f54d4e135e0 :
>>>             vtkClientServerInterpreter::CallCommandFunction(char
>>>             const*, vtkObjectBase*, char const*,
>>>             vtkClientServerStream const&, vtkClientServerStream&)
>>>             [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>             0x7f54d4e18393 :
>>>             vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream
>>>             const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>             0x7f54d4e16832 :
>>>             vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream
>>>             const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>             0x7f54d4e16ced :
>>>             vtkClientServerInterpreter::ProcessStream(vtkClientServerStream
>>>             const&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>             0x7f54d5b26cec :
>>>             vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream
>>>             const&, bool)
>>>             [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>             0x7f54d5b26958 :
>>>             vtkPVSessionCore::ExecuteStream(unsigned int,
>>>             vtkClientServerStream const&, bool)
>>>             [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>             0x7f54d5b25203 :
>>>             vtkPVSessionBase::ExecuteStream(unsigned int,
>>>             vtkClientServerStream const&, bool)
>>>             [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>             0x7f54cdcae44f : vtkSMViewProxy::Update()
>>>             [(libvtkPVServerManagerRendering-pv4.3.so.1) ???:-1]
>>>             0x7f54cdf2f6f7 :
>>>             vtkSMAnimationScene::TickInternal(double, double,
>>>             double) [(libvtkPVAnimation-pv4.3.so.1) ???:-1]
>>>             0x7f54cf415cab : vtkAnimationCue::Tick(double, double,
>>>             double) [(libvtkCommonCore-pv4.3.so.1) ???:-1]
>>>             0x7f54cdf23268 : vtkAnimationPlayer::Play()
>>>             [(libvtkPVAnimation-pv4.3.so.1) ???:-1]
>>>             0x7f54d7851619 :
>>>             vtkSMAnimationSceneCommand(vtkClientServerInterpreter*,
>>>             vtkObjectBase*, char const*, vtkClientServerStream
>>>             const&, vtkClientServerStream&, void*)
>>>             [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1]
>>>             0x7f54d4e135e0 :
>>>             vtkClientServerInterpreter::CallCommandFunction(char
>>>             const*, vtkObjectBase*, char const*,
>>>             vtkClientServerStream const&, vtkClientServerStream&)
>>>             [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>             0x7f54d4e18393 :
>>>             vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream
>>>             const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>             0x7f54d4e16832 :
>>>             vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream
>>>             const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>             0x7f54d4e16ced :
>>>             vtkClientServerInterpreter::ProcessStream(vtkClientServerStream
>>>             const&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>             0x7f54d5b436d4 :
>>>             vtkSIProperty::ProcessMessage(vtkClientServerStream&)
>>>             [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>             0x7f54d5b4377e :
>>>             vtkSIProperty::Push(paraview_protobuf::Message*, int)
>>>             [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>             0x7f54d5b4459e :
>>>             vtkSIProxy::Push(paraview_protobuf::Message*)
>>>             [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>             0x7f54d5b2884a :
>>>             vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*)
>>>             [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>             0x7f54d5b27484 :
>>>             vtkPVSessionCore::PushState(paraview_protobuf::Message*)
>>>             [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>             0x7f54d5b2514d :
>>>             vtkPVSessionBase::PushState(paraview_protobuf::Message*)
>>>             [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>             0x7f54d5d859b7 : vtkSMProxy::UpdateProperty(char const*,
>>>             int) [(libvtkPVServerManagerCore-pv4.3.so.1) ???:-1]
>>>             0x7f54d6d8aa07 : pqVCRController::onPlay()
>>>             [(libvtkpqComponents-pv4.3.so.1) ???:-1]
>>>             0x7f54cfa98258 : QMetaObject::activate(QObject*,
>>>             QMetaObject const*, int, void**) [(libQtCore.so.4) ???:-1]
>>>             0x7f54d01102f2 : QAction::triggered(bool)
>>>             [(libQtGui.so.4) ???:-1]
>>>             0x7f54d0111710 : QAction::activate(QAction::ActionEvent)
>>>             [(libQtGui.so.4) ???:-1]
>>>             0x7f54d04fd514 : ??? [(???) ???:-1]
>>>             0x7f54d04fd7ab :
>>>             QAbstractButton::mouseReleaseEvent(QMouseEvent*)
>>>             [(libQtGui.so.4) ???:-1]
>>>             0x7f54d05d15ea :
>>>             QToolButton::mouseReleaseEvent(QMouseEvent*)
>>>             [(libQtGui.so.4) ???:-1]
>>>             0x7f54d0175ac1 : QWidget::event(QEvent*)
>>>             [(libQtGui.so.4) ???:-1]
>>>             0x7f54d04fca3f : QAbstractButton::event(QEvent*)
>>>             [(libQtGui.so.4) ???:-1]
>>>             0x7f54d05d422d : QToolButton::event(QEvent*)
>>>             [(libQtGui.so.4) ???:-1]
>>>             0x7f54d011759e :
>>>             QApplicationPrivate::notify_helper(QObject*, QEvent*)
>>>             [(libQtGui.so.4) ???:-1]
>>>             0x7f54d011e533 : QApplication::notify(QObject*, QEvent*)
>>>             [(libQtGui.so.4) ???:-1]
>>>             0x7f54cfa802f3 :
>>>             QCoreApplication::notifyInternal(QObject*, QEvent*)
>>>             [(libQtCore.so.4) ???:-1]
>>>             0x7f54d011a656 :
>>>             QApplicationPrivate::sendMouseEvent(QWidget*,
>>>             QMouseEvent*, QWidget*, QWidget*, QWidget**,
>>>             QPointer<QWidget>&, bool) [(libQtGui.so.4) ???:-1]
>>>             0x7f54d019ca94 : ??? [(???) ???:-1]
>>>             0x7f54d019b877 : QApplication::x11ProcessEvent(_XEvent*)
>>>             [(libQtGui.so.4) ???:-1]
>>>             0x7f54d01c4805 : ??? [(???) ???:-1]
>>>             0x7f54cfa7f375 :
>>>             QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
>>>             [(libQtCore.so.4) ???:-1]
>>>             0x7f54cfa7f748 :
>>>             QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
>>>             [(libQtCore.so.4) ???:-1]
>>>             0x7f54cfa8414b : QCoreApplication::exec()
>>>             [(libQtCore.so.4) ???:-1]
>>>             0x407785 : main [(paraview) ???:-1]
>>>             0x7f54ce06cec5 : __libc_start_main [(libc.so.6) ???:-1]
>>>             0x4074da : QMainWindow::event(QEvent*) [(paraview) ???:-1]
>>>             =========================================================
>>>
>>>             Thanks,
>>>
>>>             Sergi Mateo
>>>             sergi.mateo.bellido at gmail.com
>>>             <mailto:sergi.mateo.bellido at gmail.com>
>>>
>>>             _______________________________________________
>>>             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
>>>
>>>
>>>
>>>
>>>         -- 
>>>         Cory Quammen
>>>         R&D Engineer
>>>         Kitware, Inc.
>>
>>
>>
>>
>>     -- 
>>     Cory Quammen
>>     R&D Engineer
>>     Kitware, Inc.
>
>
>
>
> -- 
> Cory Quammen
> R&D Engineer
> Kitware, Inc.

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

From bruce.david.jones at gmail.com  Sat Jul 11 11:14:00 2015
From: bruce.david.jones at gmail.com (Bruce Jones)
Date: Sat, 11 Jul 2015 15:14:00 +0000
Subject: [Paraview] vtkDoubleArray with >3 components
Message-ID: <CAEc4V-bvd0SRk35cuPM7Z9WhoH8WSL=7S_6kr7_Op5aOeoMN6A@mail.gmail.com>

I am creating vtkDoubleArrays based on averaging some input data to a
reduced set of points. The input data includes various vtk arrays which
have 1, 3 and 9 components.

After averaging, I am writing the data to c++ arrays, and creating a new
vtkDoubleArray using the SetArray() function to pass the c++ arrays. This
works fine for 1 and 3 component arrays, however for the 9 component arrays
paraview shows that every element is set to 0.

If I hardcode it so that 9 component arrays become 3 component arrays
(reading only the first 3 components from the input array), then I get the
correct data for the first 3 components, though I obviously need the other
6 components in the end.

Has anyone encountered this before?

Cheers,
Bruce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150711/3d7182fe/attachment.html>

From cory.quammen at kitware.com  Sun Jul 12 21:41:15 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Sun, 12 Jul 2015 21:41:15 -0400
Subject: [Paraview] Can I parallelize different input files?
In-Reply-To: <CANjddW23Bd6DODMSbv9aqrYfipxa5H8gdkvGSu87mjnL39xkfA@mail.gmail.com>
References: <CANjddW23Bd6DODMSbv9aqrYfipxa5H8gdkvGSu87mjnL39xkfA@mail.gmail.com>
Message-ID: <CAB5Fpx4CPu2vAYWqPiEOHOrwLb=hmHn7kCm6h1bCM+wB8s5QoQ@mail.gmail.com>

Hi Adam,

The PVTI file format should work perfectly for this application. The PVTI
file is an XML file that specifies the different pieces in the whole image
and points to the VTI images that contain the pieces. When loaded, each
piece should land on a different CPU - if you are running 12 CPUs. The
extents in your VTI files need to be defined in terms of the overall image
extent - if they aren't you'll need to modify them so that they are.

I have attached an example PVTI file with four associated VTI files that
you can use as a model to define your own PVTI file.

Please let us know if you have any trouble.

Thanks,
Cory


On Fri, Jul 10, 2015 at 9:34 AM, Adam Lyon <lyon at fnal.gov> wrote:

> Hi - I have 12 fairly large vti files (each one is a simulation of part of
> the magnetic field of my particle physics detector). Each file covers a
> distinct part of the total volume, so that all 12 together covers the whole
> thing. This would seem to be a perfect opportunity to try to parallelize
> Paraview's handling of these files - one CPU per vti file.  I have a
> machine with lots of cores at my disposal. Will Paraview recognize by
> itself that it can parallelize its operations, one CPU per vti file, or do
> I need to do something to make that happen? There's no overlap between the
> files - will that be a problem? My plan is to run a pvserver on the
> many-core CPU machine and connect to it via my Mac. Any advice would be
> helpful and appreciated!  Thanks! -- Adam
> *-----*
>
> *Adam L. Lyon*
> *Scientist; Associate Division Head for Systems for Scientific
> Applications*
>
> Scientific Computing Division & Muon g-2 Experiment
> Fermi National Accelerator Laboratory
> 630 840 5522 office
> www.fnal.gov
> lyon at fnal.gov
>
> Connect with us!
> Newsletter <http://www.fnal.gov/pub/today/>  |  Facebook
> <https://www.facebook.com/Fermilab>  |  Twitter
> <https://twitter.com/Fermilab>
>
> _______________________________________________
> 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
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150712/714881ea/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tensors.zip
Type: application/zip
Size: 95168 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150712/714881ea/attachment.zip>

From lyon at fnal.gov  Sun Jul 12 21:49:34 2015
From: lyon at fnal.gov (Adam Lyon)
Date: Sun, 12 Jul 2015 20:49:34 -0500
Subject: [Paraview] Can I parallelize different input files?
In-Reply-To: <cd8c51e054cf43a3bf5c558594540aa9@MAIL03V-CAS01.fnal.gov>
References: <CANjddW23Bd6DODMSbv9aqrYfipxa5H8gdkvGSu87mjnL39xkfA@mail.gmail.com>
 <cd8c51e054cf43a3bf5c558594540aa9@MAIL03V-CAS01.fnal.gov>
Message-ID: <CANjddW2PNFPx9ECq-wRKzr6dzB6iOPewKRsf=M+bX1wQfsRo+A@mail.gmail.com>

Cool! Thanks - I'll try that.  I tried just loading a few vti files anyway
running the pvserver under mpirun on the multi-core machine. This machine
has no GPU and I got a lot of "swrast" errors (one per core). So I think I
don't have a good OpenGL on this machine. I tried building my own Mesa
OpenGL according to
http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D, but got
compilation errors using the newest version of llvm. Then I had to move on
to other things.  Not sure if you've tried this - maybe you have some
ideas. Anyway, I hope to try this again sometime this week.  --- Adam

*------*

*Adam L. Lyon*
*Scientist; Associate Division Head for Systems for Scientific Applications*

Scientific Computing Division & Muon g-2 Experiment
Fermi National Accelerator Laboratory
630 840 5522 office
www.fnal.gov
lyon at fnal.gov

Connect with us!
Newsletter <http://www.fnal.gov/pub/today/>  |  Facebook
<https://www.facebook.com/Fermilab>  |  Twitter
<https://twitter.com/Fermilab>

On Sun, Jul 12, 2015 at 8:41 PM, Cory Quammen <cory.quammen at kitware.com>
wrote:

>  Hi Adam,
>
>  The PVTI file format should work perfectly for this application. The
> PVTI file is an XML file that specifies the different pieces in the whole
> image and points to the VTI images that contain the pieces. When loaded,
> each piece should land on a different CPU - if you are running 12 CPUs. The
> extents in your VTI files need to be defined in terms of the overall image
> extent - if they aren't you'll need to modify them so that they are.
>
>  I have attached an example PVTI file with four associated VTI files that
> you can use as a model to define your own PVTI file.
>
>  Please let us know if you have any trouble.
>
>  Thanks,
> Cory
>
>
> On Fri, Jul 10, 2015 at 9:34 AM, Adam Lyon <lyon at fnal.gov> wrote:
>
>> Hi - I have 12 fairly large vti files (each one is a simulation of part
>> of the magnetic field of my particle physics detector). Each file covers a
>> distinct part of the total volume, so that all 12 together covers the whole
>> thing. This would seem to be a perfect opportunity to try to parallelize
>> Paraview's handling of these files - one CPU per vti file.  I have a
>> machine with lots of cores at my disposal. Will Paraview recognize by
>> itself that it can parallelize its operations, one CPU per vti file, or do
>> I need to do something to make that happen? There's no overlap between the
>> files - will that be a problem? My plan is to run a pvserver on the
>> many-core CPU machine and connect to it via my Mac. Any advice would be
>> helpful and appreciated!  Thanks! -- Adam
>>       *-----*
>>
>>  *Adam L. Lyon*
>> *Scientist; Associate Division Head for Systems for Scientific
>> Applications*
>>
>>  Scientific Computing Division & Muon g-2 Experiment
>> Fermi National Accelerator Laboratory
>> 630 840 5522 office
>> www.fnal.gov
>> lyon at fnal.gov
>>
>>  Connect with us!
>> Newsletter <http://www.fnal.gov/pub/today/>  |  Facebook
>> <https://www.facebook.com/Fermilab>  |  Twitter
>> <https://twitter.com/Fermilab>
>>
>> _______________________________________________
>> 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
>>
>>
>
>
>  --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150712/01b2ced5/attachment.html>

From cory.quammen at kitware.com  Sun Jul 12 21:51:20 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Sun, 12 Jul 2015 21:51:20 -0400
Subject: [Paraview] segfault playing a simulation
In-Reply-To: <55A0E2AE.5050101@gmail.com>
References: <55895735.2030202@gmail.com>
 <CAB5Fpx4BDY+JDKBbA5Lt02Yt1RLaaZY6TPW9azpZsGf-aWTD7Q@mail.gmail.com>
 <559381DE.5030504@gmail.com>
 <CAB5Fpx6H7dY-j86vut03OuVr+7smd+1YwGqL2e771tRE0xdkxw@mail.gmail.com>
 <559422EF.3070304@gmail.com>
 <CAB5Fpx7AdTrtGAsq9OjoW36=-dWFDzUAGrtCF+fqqa4hLenoDg@mail.gmail.com>
 <55A0E2AE.5050101@gmail.com>
Message-ID: <CAB5Fpx7-YAJznWJKT6gk4fAV9_GM_GX2E=0Q9_2YSW4Wt5NO8A@mail.gmail.com>

Sergi,

Your VTI file extents should only describe the region of the whole image
they occupy, so you are on the right track. In situations like these where
it isn't obvious what is wrong, I tend to start from the beginning with a
very small example and build up from there. For example, you could start
with a small image - say 2 x 4 pixels (2D) split into two pieces. Start
with one data array for this example and make sure it works - use ASCII
encoding so that you know for sure what is in the XML file and then switch
to raw binary, then zipped binary. Then add a second data array. When you
are confident that works, change the example to four pieces, then make the
image 3D and so on.

It can take a while to do this, but you'll come out really understanding
the file format and will probably figure out what you had wrong in the
first place.

Thanks,
Cory

On Sat, Jul 11, 2015 at 5:32 AM, Sergi Mateo Bellido <
sergi.mateo.bellido at gmail.com> wrote:

>  Hi Cory,
>
> Thanks for your time. I have been playing a bit with the files too and I
> realized that replacing the whole_extent of each *.vti  by the whole
> dataset everything works.
>
> I would like to generate something like this:
> http://vtk.1045678.n5.nabble.com/Example-vti-file-td3381382.html . In
> this example, each imagedata has whole_extent=whole size but its pieces
> only contain a portion of the whole dataset. Does this configuration make
> sense?
>
> I have been trying to generate something like that but I failed. My code
> looks like this one: http://www.vtk.org/Wiki/VTK/Examples/Cxx/IO/WriteVTI
> but using VtkFloatArray as buffers and attaching them to the VtkImageData.
> I tried defining the set of the VtkImageData as the whole dataset and
> defining the VtkFloatArrays of the size of each portion but it didn't work
> :(
>
> Any clue?
>
> Thanks!
> Sergi
>
>
> On 07/09/2015 05:00 PM, Cory Quamen wrote:
>
> Hi Sergi,
>
>  I played with your data set a little but haven't found what is wrong. I
> am suspicious of two things in the data file, the extent and the offset in
> the second data array (it looks too small).
>
>  What are the dimensions of your grid? Note that the whole extent upper
> values need to be the dimension - 1, e.g., for a 300x300x300 grid, the
> whole extent should be 0 299 0 299 0 299.
>
>  Thanks,
> Cory
>
> On Wed, Jul 1, 2015 at 12:27 PM, Sergi Mateo Bellido <
> sergi.mateo.bellido at gmail.com> wrote:
>
>>  Hi Cory,
>>
>> Thanks for your time. These data files have been produced by a software
>> that I'm developing with some colleagues.
>>
>> Best regards,
>>
>> Sergi
>>
>>
>> On 07/01/2015 03:59 PM, Cory Quammen wrote:
>>
>> Sergi,
>>
>>  I can confirm the crash you are seeing in the same location in the
>> code. I'm looking for the cause.
>>
>>  What software produced these data files?
>>
>>  Thanks,
>> Cory
>>
>> On Wed, Jul 1, 2015 at 1:59 AM, Sergi Mateo Bellido <
>> sergi.mateo.bellido at gmail.com> wrote:
>>
>>>  Hi Cory,
>>>
>>> Thanks for your answer. I reproduced the segfault in two different ways,
>>> but it's always after loading a data set:
>>> - After loading a data set, I tried to play the simulation ->segfault
>>> - After loading a data set, I tried to filter some fields from the model
>>> (Pointer array status). As soon as I clicked the 'apply' button, paraview
>>> crashed with a segfault.
>>>
>>> Thanks,
>>> Sergi
>>>
>>>
>>>
>>> On 06/30/2015 06:21 AM, Cory Quammen wrote:
>>>
>>> Hi Sergi,
>>>
>>>  Could you clarify when you are seeing this crash? Is it right when
>>> starting ParaView or when first loading a data set?
>>>
>>>  Thanks,
>>> Cory
>>>
>>> On Tue, Jun 23, 2015 at 8:55 AM, Sergi Mateo Bellido <
>>> sergi.mateo.bellido at gmail.com> wrote:
>>>
>>>>  Hi,
>>>>
>>>> I'm trying to reproduce a simulation with ParaView 4.3.1 and it always
>>>> crashes when I start it. You can find the backtrace below:
>>>>
>>>> =========================================================
>>>> Process id 6681 Caught SIGSEGV at 0x925b124 address not mapped to object
>>>> Program Stack:
>>>> WARNING: The stack trace will not use advanced capabilities because
>>>> this is a release build.
>>>> 0x7f54ce081d40 : ??? [(???) ???:-1]
>>>> 0x7f54ce19caf6 : ??? [(???) ???:-1]
>>>> 0x7f54cb123736 : vtkXMLPStructuredDataReader::CopySubExtent(int*, int*,
>>>> long long*, int*, int*, long long*, int*, int*, vtkDataArray*,
>>>> vtkDataArray*) [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>> 0x7f54cb12389f :
>>>> vtkXMLPStructuredDataReader::CopyArrayForPoints(vtkDataArray*,
>>>> vtkDataArray*) [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>> 0x7f54cb11cc1f : vtkXMLPDataReader::ReadPieceData()
>>>> [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>> 0x7f54cb11ca14 : vtkXMLPDataReader::ReadPieceData(int)
>>>> [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>> 0x7f54cb124d7a : vtkXMLPStructuredDataReader::ReadXMLData()
>>>> [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>> 0x7f54cb1280eb : vtkXMLReader::RequestData(vtkInformation*,
>>>> vtkInformationVector**, vtkInformationVector*) [(libvtkIOXML-pv4.3.so.1)
>>>> ???:-1]
>>>> 0x7f54cb1273b6 : vtkXMLReader::ProcessRequest(vtkInformation*,
>>>> vtkInformationVector**, vtkInformationVector*) [(libvtkIOXML-pv4.3.so.1)
>>>> ???:-1]
>>>> 0x7f54cd6200f9 : vtkFileSeriesReader::RequestData(vtkInformation*,
>>>> vtkInformationVector**, vtkInformationVector*)
>>>> [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1]
>>>> 0x7f54cd61f07f : vtkFileSeriesReader::ProcessRequest(vtkInformation*,
>>>> vtkInformationVector**, vtkInformationVector*)
>>>> [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1]
>>>> 0x7f54d2706204 : vtkExecutive::CallAlgorithm(vtkInformation*, int,
>>>> vtkInformationVector**, vtkInformationVector*)
>>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>> 0x7f54d27016cc : vtkDemandDrivenPipeline::ExecuteData(vtkInformation*,
>>>> vtkInformationVector**, vtkInformationVector*)
>>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>> 0x7f54d2700201 : vtkCompositeDataPipeline::ExecuteData(vtkInformation*,
>>>> vtkInformationVector**, vtkInformationVector*)
>>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>> 0x7f54d2704067 :
>>>> vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>> vtkInformationVector**, vtkInformationVector*)
>>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>> 0x7f54d271d959 :
>>>> vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>> vtkInformationVector**, vtkInformationVector*)
>>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>> 0x7f54d26fe387 :
>>>> vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*)
>>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>> 0x7f54d2704010 :
>>>> vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>> vtkInformationVector**, vtkInformationVector*)
>>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>> 0x7f54d271d959 :
>>>> vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>> vtkInformationVector**, vtkInformationVector*)
>>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>> 0x7f54d26fe387 :
>>>> vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*)
>>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>> 0x7f54d2704010 :
>>>> vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>> vtkInformationVector**, vtkInformationVector*)
>>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>> 0x7f54d271d959 :
>>>> vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>> vtkInformationVector**, vtkInformationVector*)
>>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>> 0x7f54d27035ae : vtkDemandDrivenPipeline::UpdateData(int)
>>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>> 0x7f54d271e87f : vtkStreamingDemandDrivenPipeline::Update(int)
>>>> [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>> 0x7f54cd98fa7f :
>>>> vtkPVDataRepresentation::ProcessViewRequest(vtkInformationRequestKey*,
>>>> vtkInformation*, vtkInformation*)
>>>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>> 0x7f54cd973d79 :
>>>> vtkGeometryRepresentation::ProcessViewRequest(vtkInformationRequestKey*,
>>>> vtkInformation*, vtkInformation*)
>>>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>> 0x7f54cd975d71 :
>>>> vtkGeometryRepresentationWithFaces::ProcessViewRequest(vtkInformationRequestKey*,
>>>> vtkInformation*, vtkInformation*)
>>>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>> 0x7f54cd9bd388 :
>>>> vtkPVView::CallProcessViewRequest(vtkInformationRequestKey*,
>>>> vtkInformation*, vtkInformationVector*)
>>>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>> 0x7f54cd9bd552 : vtkPVView::Update()
>>>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>> 0x7f54cd9acb78 : vtkPVRenderView::Update()
>>>> [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>> 0x7f54d780ac30 : vtkPVRenderViewCommand(vtkClientServerInterpreter*,
>>>> vtkObjectBase*, char const*, vtkClientServerStream const&,
>>>> vtkClientServerStream&, void*)
>>>> [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1]
>>>> 0x7f54d4e135e0 : vtkClientServerInterpreter::CallCommandFunction(char
>>>> const*, vtkObjectBase*, char const*, vtkClientServerStream const&,
>>>> vtkClientServerStream&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>> 0x7f54d4e18393 :
>>>> vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream
>>>> const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>> 0x7f54d4e16832 :
>>>> vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&,
>>>> int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>> 0x7f54d4e16ced :
>>>> vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&)
>>>> [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>> 0x7f54d5b26cec :
>>>> vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool)
>>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>> 0x7f54d5b26958 : vtkPVSessionCore::ExecuteStream(unsigned int,
>>>> vtkClientServerStream const&, bool)
>>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>> 0x7f54d5b25203 : vtkPVSessionBase::ExecuteStream(unsigned int,
>>>> vtkClientServerStream const&, bool)
>>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>> 0x7f54cdcae44f : vtkSMViewProxy::Update()
>>>> [(libvtkPVServerManagerRendering-pv4.3.so.1) ???:-1]
>>>> 0x7f54cdf2f6f7 : vtkSMAnimationScene::TickInternal(double, double,
>>>> double) [(libvtkPVAnimation-pv4.3.so.1) ???:-1]
>>>> 0x7f54cf415cab : vtkAnimationCue::Tick(double, double, double)
>>>> [(libvtkCommonCore-pv4.3.so.1) ???:-1]
>>>> 0x7f54cdf23268 : vtkAnimationPlayer::Play()
>>>> [(libvtkPVAnimation-pv4.3.so.1) ???:-1]
>>>> 0x7f54d7851619 :
>>>> vtkSMAnimationSceneCommand(vtkClientServerInterpreter*, vtkObjectBase*,
>>>> char const*, vtkClientServerStream const&, vtkClientServerStream&, void*)
>>>> [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1]
>>>> 0x7f54d4e135e0 : vtkClientServerInterpreter::CallCommandFunction(char
>>>> const*, vtkObjectBase*, char const*, vtkClientServerStream const&,
>>>> vtkClientServerStream&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>> 0x7f54d4e18393 :
>>>> vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream
>>>> const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>> 0x7f54d4e16832 :
>>>> vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&,
>>>> int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>> 0x7f54d4e16ced :
>>>> vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&)
>>>> [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>> 0x7f54d5b436d4 : vtkSIProperty::ProcessMessage(vtkClientServerStream&)
>>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>> 0x7f54d5b4377e : vtkSIProperty::Push(paraview_protobuf::Message*, int)
>>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>> 0x7f54d5b4459e : vtkSIProxy::Push(paraview_protobuf::Message*)
>>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>> 0x7f54d5b2884a :
>>>> vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*)
>>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>> 0x7f54d5b27484 :
>>>> vtkPVSessionCore::PushState(paraview_protobuf::Message*)
>>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>> 0x7f54d5b2514d :
>>>> vtkPVSessionBase::PushState(paraview_protobuf::Message*)
>>>> [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>> 0x7f54d5d859b7 : vtkSMProxy::UpdateProperty(char const*, int)
>>>> [(libvtkPVServerManagerCore-pv4.3.so.1) ???:-1]
>>>> 0x7f54d6d8aa07 : pqVCRController::onPlay()
>>>> [(libvtkpqComponents-pv4.3.so.1) ???:-1]
>>>> 0x7f54cfa98258 : QMetaObject::activate(QObject*, QMetaObject const*,
>>>> int, void**) [(libQtCore.so.4) ???:-1]
>>>> 0x7f54d01102f2 : QAction::triggered(bool) [(libQtGui.so.4) ???:-1]
>>>> 0x7f54d0111710 : QAction::activate(QAction::ActionEvent)
>>>> [(libQtGui.so.4) ???:-1]
>>>> 0x7f54d04fd514 : ??? [(???) ???:-1]
>>>> 0x7f54d04fd7ab : QAbstractButton::mouseReleaseEvent(QMouseEvent*)
>>>> [(libQtGui.so.4) ???:-1]
>>>> 0x7f54d05d15ea : QToolButton::mouseReleaseEvent(QMouseEvent*)
>>>> [(libQtGui.so.4) ???:-1]
>>>> 0x7f54d0175ac1 : QWidget::event(QEvent*) [(libQtGui.so.4) ???:-1]
>>>> 0x7f54d04fca3f : QAbstractButton::event(QEvent*) [(libQtGui.so.4)
>>>> ???:-1]
>>>> 0x7f54d05d422d : QToolButton::event(QEvent*) [(libQtGui.so.4) ???:-1]
>>>> 0x7f54d011759e : QApplicationPrivate::notify_helper(QObject*, QEvent*)
>>>> [(libQtGui.so.4) ???:-1]
>>>> 0x7f54d011e533 : QApplication::notify(QObject*, QEvent*)
>>>> [(libQtGui.so.4) ???:-1]
>>>> 0x7f54cfa802f3 : QCoreApplication::notifyInternal(QObject*, QEvent*)
>>>> [(libQtCore.so.4) ???:-1]
>>>> 0x7f54d011a656 : QApplicationPrivate::sendMouseEvent(QWidget*,
>>>> QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool)
>>>> [(libQtGui.so.4) ???:-1]
>>>> 0x7f54d019ca94 : ??? [(???) ???:-1]
>>>> 0x7f54d019b877 : QApplication::x11ProcessEvent(_XEvent*)
>>>> [(libQtGui.so.4) ???:-1]
>>>> 0x7f54d01c4805 : ??? [(???) ???:-1]
>>>> 0x7f54cfa7f375 :
>>>> QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
>>>> [(libQtCore.so.4) ???:-1]
>>>> 0x7f54cfa7f748 :
>>>> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) [(libQtCore.so.4)
>>>> ???:-1]
>>>> 0x7f54cfa8414b : QCoreApplication::exec() [(libQtCore.so.4) ???:-1]
>>>> 0x407785 : main [(paraview) ???:-1]
>>>> 0x7f54ce06cec5 : __libc_start_main [(libc.so.6) ???:-1]
>>>> 0x4074da : QMainWindow::event(QEvent*) [(paraview) ???:-1]
>>>> =========================================================
>>>>
>>>> Thanks,
>>>>
>>>> Sergi Mateo
>>>> sergi.mateo.bellido at 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
>>>>
>>>>
>>>
>>>
>>>  --
>>> Cory Quammen
>>> R&D Engineer
>>> Kitware, Inc.
>>>
>>>
>>>
>>
>>
>>  --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>>
>>
>>
>
>
>  --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150712/3c0e1c2c/attachment.html>

From cory.quammen at kitware.com  Sun Jul 12 23:31:01 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Sun, 12 Jul 2015 23:31:01 -0400
Subject: [Paraview] Fwd: How to plug into paraview his own writer ?
In-Reply-To: <71ceeafa120eedbb8f315f7fac951b49@imap.ipgp.fr>
References: <86347d91c723cd90b081325c08b678ec@imap.ipgp.fr>
 <CAB5Fpx6hLd4Of0iopNU-zEpVV9X=w8-2tPjGChm=sp1OPaM9fA@mail.gmail.com>
 <71ceeafa120eedbb8f315f7fac951b49@imap.ipgp.fr>
Message-ID: <CAB5Fpx53LxNNLYT32J=Y=QQUGQPCUQi5-VmVhqc05y-y5v+W4Q@mail.gmail.com>

Franck,

Thanks for letting us know. I'm glad you figured it out. The client/server
wrapping indeed assumes your class header file is defined in a .h file. You
should, however, have gotten a warning that said something like

Unable to find: myWriter

Cory

On Mon, Jul 6, 2015 at 3:03 AM, houssen <houssen at ipgp.fr> wrote:

> By the way, the crash occured because myWriter.hpp was a .hpp : I moved it
> to myWriter.h and it worked !...
> I guess this should be added in the doc but I don't know who to contact
> for that : I let you forward this if you can.
>
> Franck
>
> Le 2015-06-30 6:08, Cory Quammen a ?crit :
>
>> Hi Franck,
>>
>> It looks like you've been making progress, so I'll answer your
>> questions from your second email.
>>
>>
>>
>>  Question 1 : how to write myWriter.xml ?
>>>
>>> 1.1. seems I must set <InputProperty command="SetInputConnection"
>>> name="Input"> in myWriter.xml. Does this means I will also have to
>>> implement myWriter::SetInputConnection ?
>>>
>>
>> No. Your writer will inherit from subclass of vtkAlgorithm, the class
>> that defines "SetInputConnection", and you should not need to override
>> it. XdmfWriter inherits from vtkDataObjectAlgorithm, which itself
>> inherits vtkAlgorithm.
>>
>>
>>  1.2. seems I must set <StringVectorProperty name="FileName"
>>> command="SetFileName"> in myWriter.xml. Does this means I will also
>>> have to implement myWriter::SetFileName ?
>>>
>>
>> Yes, like vtkXdmfWriter.
>>
>>  2.2 in myWriter.hpp, I need to derive from a vtkObject this way
>> (like XdmfWriter.cpp does)
>>
>>  ew (); // Needed to be plugged into paraview
>>>     vtkTypeMacro ( myWriter, vtkDataObjectAlgorithm ); // Needed
>>> to be plugged into paraview
>>> + suppress copy constructor and operator=
>>>
>>> Am I correct ?
>>>
>>> Yes.
>>>
>>> Question 3 : in myWriter.cpp, on
>>>
>> I am supposed to be called back (to get focus back) when I click the
>> "save data" button ? Here, how can I get data to be saved (data that I
>> can see in paraview viewer befo
>>
>>  n ParaView, when you choose, File -> Save Data, the data from the
>>> selected Pipeline Browser object will be saved. This will have some
>>> kind of data type, e.g., vtkImageData, vtkPolyData, etc. What kind
>>> of data type would you like your writer to support?
>>>
>>> The data should
>>>
>> in the member function myWriter::RequestData(). This is where you
>> should write your data.
>>
>>  Finally, myWriter.xml seems OK. myWriter.*pp compile OK. Paraview
>> finds myWriter.xml at run time (exporting PV_PLUGIN_PATH) and loads
>> libmywriter.so without problem. I see the writer in the "save data"
>> GUI (drop down list with different save formats). I save with
>> myWriter, I get a (basic) GUI with file name only (no extra parameter)
>> : I crash when I click "OK, save" with this error message :
>>  ERROR: In /.../ParaView-v4.3.1-sourc
>>
>>  ailed to create myWriter. Aborting for debugging purposes.
>>>
>>> vtkSIWriterProxy does this at line 303 :
>>> vtkObjectBase* obj = this->Interpreter->NewInstance(className);
>>> but obj is NULL.
>>>
>>> I get obj is NULL because I missed something in myWriter
>>> implementation : what did I miss ?
>>>
>>> Are you running pvserver separately and connecting to it with the
>>> client? If so, make sure PV_PLUGIN_PATH is defined in the
>>> environment in which pvserver is run. Have you tried to load your
>>> plugin through the Tools -> Manage Plugins... dialog?
>>>
>>> I hope that helps get you further in writing your data files.
>>>
>>> Thanks,
>>> Cory
>>>
>>> Can somebody help
>>>
>> t me some clue ?
>>
>>  FH
>>
>>  -------- Message original --------
>>  Objet: How to plug into paraview his own writer ?
>>  Date: 2015-06-12 15:54
>>  De: houssen <houssen at imap.ipgp.fr [6]>
>>  ?: <paraview at paraview.org [7]>
>>
>>  I followed 2 tutorials (
>>
>> Links:
>> ------
>> [1] http://www.kitware.com
>> [2] http://www.kitware.com/opensource/opensource.html
>> [3] http://paraview.org/Wiki/ParaView
>> [4] http://markmail.org/search/?q=ParaView
>> [5] http://public.kitware.com/mailman/listinfo/paraview
>> [6] mailto:houssen at imap.ipgp.fr
>> [7] mailto:paraview at paraview.org
>>
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150712/1b7ceb7c/attachment.html>

From cory.quammen at kitware.com  Sun Jul 12 23:33:58 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Sun, 12 Jul 2015 23:33:58 -0400
Subject: [Paraview] Wrong fetched data
In-Reply-To: <f79e260d16a28fb08f353b8626184dee@fe.up.pt>
References: <5000545d13da0baa4fa1c3d1e3c44423@fe.up.pt>
 <CAB5Fpx5xsoTOeBdtEGLBMEDVG5YonkPb5maRPKVpCbbYCJzeGA@mail.gmail.com>
 <f79e260d16a28fb08f353b8626184dee@fe.up.pt>
Message-ID: <CAB5Fpx4zX0FND+bOdu24oHCnMfzLwgoNbPdp8jQQLhkRw_0UuQ@mail.gmail.com>

Interesting. Is is possible for you to share the data file(s)?

Thanks,
Cory

On Mon, Jul 6, 2015 at 10:23 AM, deq11009 <deq11009 at fe.up.pt> wrote:

> Hi,
>
> Thank you for your reply.
>
> No, the mistake is not there. In the meantime I did realize what is
> exactly happening.
>
> I have, say, 200 timesteps.
> From 0 to 6, data obtained from my code matches the data when I just use
> the GUI.
> Starting in timestep 7 (always) till the end, data (for all timesteps) is
> the data from the last timestep.
> So, when in python shell I go to timestep 6, I see timestep 6. But when I
> go to timestep 7, or 100, or 133, I see timestep 199. At the same time, if
> I go to the GUI, everything is ok.
>
> By coincidence, the ".case" time step data is organized in seven columns.
> Is this related to the problem?
>
> Thank you
> Filipe Direito
>
>
> On 03.07.2015 15:05, Cory Quammen wrote:
>
>> Hi Filipe,
>>
>> Perhaps the array at index 7 is not the array you are expecting? Could
>> you access the array by name instead, .e.g.,
>>
>> dAxis.GetPointData().GetArray(variable_name).GetValue(150)
>>
>> and see if that works better?
>>
>> Thanks,
>> Cory
>>
>> On Wed, Jul 1, 2015 at 1:44 PM, deq11009 <deq11009 at fe.up.pt [6]>
>> wrote:
>>
>>  Hi,
>>>
>>> I am currently using Paraview 4.2, 64, in Windows. (but tried 4.3
>>> and same problem happened)
>>>
>>> My case is Ensight transient. Cylinder with 3.6 million cells,
>>> two-phase flow.
>>>
>>> I created a python code, which I run from the shell in the GUI.
>>>
>>> The main parts of the code are:
>>>
>>> enscase = EnSightReader(CaseFileName = direcp + ensfinal.case)
>>> ...
>>> axis = Line()
>>> ...
>>> rAxis = ResampleWithDataset(Input = enscase , Source = axis)
>>> ...
>>> rAxis.SMProxy.UpdatePipeline(7) # enscase.SMProxy yields same
>>> problem
>>> rAxis.UpdatePipelineInformation()
>>> dAxis = servermanager.Fetch(rAxis)
>>>
>>> Now, for example:
>>> print dAxis.GetPointData().GetArray(7).GetValue(150)
>>> which gives me the value 150 of the phase array.
>>>
>>> This data is wrong. On the other hand, if I go to the GUI Pipeline
>>> and create a Spreadsheet, the values are the real ones (confirmed in
>>> Fluent).
>>>
>>> So, the fetched data in the python shell is, for some reason,
>>> wrong.
>>> What is my mistake?
>>>
>>> Thanks
>>> Filipe Direito
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com [1]
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html [2]
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView [3]
>>>
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>> [4]
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview [5]
>>>
>>
> _______________________________________________
> 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
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150712/d6e0b5eb/attachment.html>

From aymeric.naze at gmail.com  Mon Jul 13 03:41:27 2015
From: aymeric.naze at gmail.com (Aymeric NAZE)
Date: Mon, 13 Jul 2015 09:41:27 +0200
Subject: [Paraview] Orient created vectors
In-Reply-To: <CAM4K3YdQZDhAqAy--jj6bNFy0VYKkwO-=s7Xz-VY7evJJ=DGJw@mail.gmail.com>
References: <CAM4K3YdAJ+XvjbShzT3uJL3ntYwwitjUPdryzrx5pZUOGEa4LQ@mail.gmail.com>
 <CAB5Fpx5ZZb2UQP86on6-YT+Mqx6DfUc3j6K0deo8nTOaY2iHAg@mail.gmail.com>
 <CAM4K3YeSBB+eavXBKA+jUPzTdfASeM-pWRNkOqnBbdD6NcbGow@mail.gmail.com>
 <CAB5Fpx49Pm4tnm_cduJspQXFLzA27R+WXgN8C5XABBsdY3hbfg@mail.gmail.com>
 <CAM4K3YcYe_Eo8jYVWVWuaU3mHssPa=DnSFBjdmK3eyh8tr0RQA@mail.gmail.com>
 <CAB5Fpx5Lgi-yQxwrp43S4goeO40x56P9pFU94OGKWSzN_i+fcw@mail.gmail.com>
 <CAM4K3YdQZDhAqAy--jj6bNFy0VYKkwO-=s7Xz-VY7evJJ=DGJw@mail.gmail.com>
Message-ID: <CAM4K3Yd5ANgvKeSDPG-krMBKsAaiVbHcTsp2qtQsCxgY0ehB4w@mail.gmail.com>

Hi Cory,

Did you have the time to take a look at my dataset ?

2015-07-09 17:03 GMT+02:00 Aymeric NAZE <aymeric.naze at gmail.com>:

> Thank you for your reactivity.
>
> You will find below a dropbox link to 2 files :
>
>    - the dataset : 27.8 Mo
>    - the state file (ontaining the calculators and glyph) : 261 ko
>
>
> https://www.dropbox.com/sh/fu8mji13ov79crb/AAAFcFvCKccEu-qcP5YZtguPa?dl=0
>
>
> 2015-07-09 16:12 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>
>> Hmm, well it does indeed have non-zero Y and Z components. Could you
>> share this dataset?
>>
>> Thanks,
>> Cory
>>
>> On Thu, Jul 9, 2015 at 8:53 AM, Aymeric NAZE <aymeric.naze at gmail.com>
>> wrote:
>>
>>> Information regarding my Result vector field in Data Arrays (under
>>> "Information" tab in the calculator filter) :
>>>
>>>    - *Data Type* : double
>>>    - *Data Ranges* : [-1.26, 0.01], [-0.01, 0.76], [-0.16, 0.27]
>>>
>>>
>>> 2015-07-09 15:03 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>>>
>>>> Can you verify that the second and third components of your Result
>>>> vector field have a range outside [0, 0]? You can get this information
>>>> under the Information tab in the Data Arrays table.
>>>>
>>>> On Thu, Jul 9, 2015 at 7:56 AM, Aymeric NAZE <aymeric.naze at gmail.com>
>>>> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> Thanks for considering my problem.
>>>>>
>>>>> Yes, in the Glyph Filter I have the following *Active Attributes* :
>>>>>
>>>>>    - *Scalars *: FF wich is the magnitude in the (x,y) plane
>>>>>    (calculated with another "calculator" filter : FF=(U^2+V^2)^0.5) : it's the
>>>>>    length of the arrows I want to display.
>>>>>
>>>>>
>>>>>    - *Vectors *: Result (vectors from the previously described
>>>>>    calculator)
>>>>>
>>>>>
>>>>> 2015-07-09 14:29 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>>>>>
>>>>>> Hi Aymeric,
>>>>>>
>>>>>> Did you choose the "Result" array as the "Vectors" property in the
>>>>>> Properties panel of the Glyph filter?
>>>>>>
>>>>>> HTH,
>>>>>> Cory
>>>>>>
>>>>>> On Thu, Jul 9, 2015 at 7:26 AM, Aymeric NAZE <aymeric.naze at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> I'm using Paraview 4.3.1 (64-bit) to display data from a tecplot
>>>>>>> format file.
>>>>>>>
>>>>>>> Data is points coordinates (x,y,z) and vectors coordinates (u,v,w)
>>>>>>> for each point.
>>>>>>>
>>>>>>>
>>>>>>>    - I have created vectors with "Calculator" filter (Result =
>>>>>>>    u*iHat+v*jHat+w*kHat) and it creates vectors with thewanted coordinates (I
>>>>>>>    can see that in the spreadsheet view)
>>>>>>>
>>>>>>>
>>>>>>>    - Then I made a glyph to display these vectors as arrows.
>>>>>>>
>>>>>>> Magnitude is displayed without problem but i did'nt find how to
>>>>>>> orient correctly the vectors.
>>>>>>> Whether i check or not the "Orient" feature it doesn't change
>>>>>>> anything : vectors are always oriented along the x axis...
>>>>>>>
>>>>>>> Does anybody can help me on that issue ?
>>>>>>>
>>>>>>> Thanks so much in advance.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Aymeric
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Cory Quammen
>>>>>> R&D Engineer
>>>>>> Kitware, Inc.
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Cory Quammen
>>>> R&D Engineer
>>>> Kitware, Inc.
>>>>
>>>
>>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150713/ea404e8c/attachment.html>

From asche.j at googlemail.com  Mon Jul 13 07:10:28 2015
From: asche.j at googlemail.com (Jonas Asche)
Date: Mon, 13 Jul 2015 13:10:28 +0200
Subject: [Paraview] Python: Save Screenshot in parallel projection
Message-ID: <CAEqguQY8z8zHaX9ErnnoAxjfWgtA5tSHNCU_P8coyx9DTVtYHA@mail.gmail.com>

Hello, when i try to switch to parallel projection on in my script i can
only save a screenshot with parallel projection disabled:

self.__getView().CameraParallelProjection = 1
self.__getView().CameraParallelScale = 1.0
self.__getView().CameraViewUp = [0.0, 0.0, 1.0]
self.__getView().CameraPosition = camdirection[axis]
self.__getView().CameraFocalPoint = [0.0, 0.0, 33.32500076293945]
self.__getView().CameraClippingRange = [154.56988142373606, 215.9545612783452]

SaveScreenshot(str(self.__getConfig().get("save", "path") + 'img-') +
str(axis) + "-" + str(distribution) + '.png', self.__getView())

When when i print out the parallel scale AFTER savin the screenshot it
is set to 46.6471043813.


is this the same bug like here: http://paraview.org/Bug/view.php?id=7466

?

Is there a workaround or am i doing something wrong?

Thanks,

Jonas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150713/45cc0f0e/attachment.html>

From ben.boeckel at kitware.com  Mon Jul 13 09:04:57 2015
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Mon, 13 Jul 2015 09:04:57 -0400
Subject: [Paraview] Qt
In-Reply-To: <86722d04089940a18075b985091086b1@ES01AMSNLNT.srn.sandia.gov>
References: <86722d04089940a18075b985091086b1@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <20150713130457.GB27674@megas.kitware.com>

On Sat, Jul 11, 2015 at 00:16:19 +0000, Scott, W Alan wrote:
> I notice that the Superbuild is running Qt 5.4.1.  Any idea where I
> can find the Windows installer (i.e., I don't want to build from
> source)?

Downloads are found here:

    http://download.qt.io/archive/qt/5.4/5.4.1/

The superbuild is meant to run with MSVC2013, but I see that only
MSVC2013 has 64 bit and OpenGL support anyways with the prebuilt
binaries.

--Ben

From casey.goodlett at kitware.com  Mon Jul 13 09:48:16 2015
From: casey.goodlett at kitware.com (Casey Goodlett)
Date: Mon, 13 Jul 2015 09:48:16 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAFe6qKhhgem8+jPVRyJoaQrY-WJgW3vne7xDFHP41w332FWQPA@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <CAFe6qKgoBR7HU6MHCDTKr_HCxBGu_eU3St2D5+UjQ3zrBwqcbg@mail.gmail.com>
 <CAOqyOuG9-w-TFEXJO1+8EvtAQLK-JJE3Rr8XqVLG=JObe69sNg@mail.gmail.com>
 <CAFe6qKg-_LHR3tHZ10H78PZJcF2rAVV8bEOH_y_Bt0h+C9jMyw@mail.gmail.com>
 <CAFe6qKhUiTADyYM9OTyWZg5RtvctezOxnREXnL40BsR-Ny=EoA@mail.gmail.com>
 <CAOqyOuH60D5LXthUwvSUViCWLqvrTz1z5a9wu-aCX3c4g-GEgQ@mail.gmail.com>
 <CAFe6qKhT6PvOoQRdOyAriiLJbc4D-zVJ-TtLgsyitECHCrsz8w@mail.gmail.com>
 <CAOqyOuGCULt0Lm4GBzxSLifuv4OoVJ_G-k_rhYMpCG4XE1tPLQ@mail.gmail.com>
 <CAFe6qKhhgem8+jPVRyJoaQrY-WJgW3vne7xDFHP41w332FWQPA@mail.gmail.com>
Message-ID: <CAOqyOuEdwX+2_+7_Q-qfmCHF=oXSgTmJ9U3kEhn8ut+Dc5BEQg@mail.gmail.com>

Eric,

I am not familiar with this problem.

The code for the PCL plugin is now hosted at github here
https://github.com/Kitware/PCLPlugin

Best Regards,

On Fri, Jul 10, 2015 at 8:32 PM, Eric Younkin - NOAA Federal <
eric.g.younkin at noaa.gov> wrote:

> Casey,
>
> When building Paraview 4.3.1 from source with QT5.5 in Visual Studio 2013,
> I get 3 failed out of 569.  I pasted in the relevant parts of the VS output
> log below (full log too big to attach):
>
> 567>  Generating Code...
> 567>     Creating library
> C:/Users/eric.g.younkin/Documents/PCL_ParaView/ParaView-v4.3.1-source/build/lib/Debug/MobileRemoteControl.lib
> and object
> C:/Users/eric.g.younkin/Documents/PCL_ParaView/ParaView-v4.3.1-source/build/lib/Debug/MobileRemoteControl.exp
> 567>  MobileRemoteControl.vcxproj ->
> C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\bin\Debug\MobileRemoteControl.dll
> 568>C:\Program Files
> (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(607,5):
> error MSB6006: "link.exe" exited with code 1120.
> 568>MSVCRTD.lib(crtexew.obj) : error LNK2019: unresolved external symbol
> WinMain referenced in function __tmainCRTStartup
> 568>C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\bin\Debug\paraview.exe
> : fatal error LNK1120: 1 unresolved externals
> 569>------ Build started: Project: ALL_BUILD, Configuration: Debug x64
> ------
> 569>  Building Custom Rule
> C:/Users/eric.g.younkin/Documents/PCL_ParaView/ParaView-v4.3.1-source/CMakeLists.txt
> 569>  CMake does not need to re-run because
> C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\CMakeFiles\generate.stamp
> is up-to-date.
> ========== Build: 566 succeeded, 3 failed, 0 up-to-date, 0 skipped
> ==========
>
> Doing some Google searches seem to indicate that in order to clear the
> LNK2019 error, I would need to change the project type
> <http://stackoverflow.com/questions/6626397/error-lnk2019-unresolved-external-symbol-winmain16-referenced-in-function>.
> And that in order to do that, I would need to change the configuration type from
> utility to something else
> <http://gotoanswer.com/?q=No+Linker+option+in+Visual+Studio+Project+Properties>
> .
>
> I suspect that I am just missing something obvious, but I'm not sure what
> it is.  Can you offer any advice?
>
> Thanks,
> Eric
>
> On Fri, Jul 10, 2015 at 12:03 PM, Casey Goodlett <
> casey.goodlett at kitware.com> wrote:
>
>> You should compile against the VTK of paraview.  I have not tested Qt 5.5.
>>
>> I have not recently tested building VeloView  against paraview outside of
>> the VeloView superbuild.  There may be unexpected problems.
>>
>> On Fri, Jul 10, 2015 at 11:49 AM, Eric Younkin - NOAA Federal <
>> eric.g.younkin at noaa.gov> wrote:
>>
>>> Thanks Casey.  I'm reading in the Veloview Developer guide (
>>> https://github.com/Kitware/VeloView/tree/master/Documentation) that
>>> Veloview requires VTK6 and Qt 4.8.  I'm currently compiling Paraview from
>>> source using Qt5.5 and VTK libraries that came with Paraview source.  Do I
>>> need to download VTK6 and Qt4.8 and use those?  I've had some issues with
>>> VS2013 and compiling with Qt4.
>>>
>>> Also, I'm currently getting the following repeating error upon
>>> configuring in CMake:
>>>
>>> CMake Warning (dev) in ThirdParty/QtTesting/vtkqttesting/CMakeLists.txt:
>>> Policy CMP0020 is not set: Automatically link Qt executables to qtmain
>>> target on Windows. Run "cmake --help-policy CMP0020" for policy details.
>>> Use the cmake_policy command to set the policy and suppress this warning.
>>> This warning is for project developers. Use -Wno-dev to suppress it.
>>>
>>> I'm seeing some references on the VTK users group (
>>> http://public.kitware.com/pipermail/vtkusers/2013-July/080543.html)
>>> that seem to indicate you can ignore them.  Any reason I shouldn't continue
>>> with Qt5.5?
>>>
>>> Thanks,
>>> Eric
>>>
>>> On Fri, Jul 10, 2015 at 10:43 AM, Casey Goodlett <
>>> casey.goodlett at kitware.com> wrote:
>>>
>>>> Eric,
>>>>
>>>> That paper describes the approach for filter wrapping.  You will also
>>>> need to compile VeloView against your paraview build and then include the
>>>> VeloView plugin alongside the PCL plugin.
>>>>
>>>> Hope that helps.
>>>>
>>>> On Thu, Jul 9, 2015 at 3:00 PM, Eric Younkin - NOAA Federal <
>>>> eric.g.younkin at noaa.gov> wrote:
>>>>
>>>>> I should also mention that I have been reading this paper
>>>>> <http://www.paraview.org/Wiki/images/1/1e/Paper.pdf> and a few other
>>>>> sources.  I think I have a basic idea of the framework.
>>>>>
>>>>> On Thu, Jul 9, 2015 at 11:33 AM, Eric Younkin - NOAA Federal <
>>>>> eric.g.younkin at noaa.gov> wrote:
>>>>>
>>>>>> Thanks Casey.  For someone with only moderate programming experience,
>>>>>> how difficult would you say creating those additional wrappers and building
>>>>>> a VLP-16 paraview plugin would be?  Do you happen to have any resources or
>>>>>> guides for doing so?
>>>>>>
>>>>>> I will continue to look at building from source and check out Project
>>>>>> Tango.  Thanks for the link.
>>>>>>
>>>>>> Thanks,
>>>>>> Eric
>>>>>>
>>>>>> On Thu, Jul 9, 2015 at 11:14 AM, Casey Goodlett <
>>>>>> casey.goodlett at kitware.com> wrote:
>>>>>>
>>>>>>>
>>>>>>> On Thu, Jul 9, 2015 at 10:53 AM, Eric Younkin - NOAA Federal <
>>>>>>> eric.g.younkin at noaa.gov> wrote:
>>>>>>>
>>>>>>>> Casey,
>>>>>>>>
>>>>>>>> I am mostly interested in the feature extraction routines and
>>>>>>>> Paraview integration with the Velodyne VLP-16.  I'd like to experiment with
>>>>>>>> PCL algorithms to try and pick out fixed objects such as buoys or piers
>>>>>>>> from a VLP-16 mounted on our research vessel as we travel up the coast.  I
>>>>>>>> think most of my errors are from attempting to build using Visual Studio
>>>>>>>> 2013 pro and older Qt/PCL versions.  If I can use the most recent versions,
>>>>>>>> that might help things.
>>>>>>>>
>>>>>>>
>>>>>>> Sounds like a cool project.  You may need to add some additional
>>>>>>> wrappers for feature extraction if you are looking for things beyond the
>>>>>>> sample consensus models that we have.  I dont think any of the point
>>>>>>> feature histogram utilities are currently wrapped.
>>>>>>>
>>>>>>> Windows builds of the whole stack are a bit tricky.  Feel free to
>>>>>>> share your error messages, and I'll help where I can.
>>>>>>>
>>>>>>> The plugin does not include support for the VLP-16 in its current
>>>>>>> state.  We have another project VeloView
>>>>>>> <https://github.com/Kitware/VeloView> that builds a paraview plugin
>>>>>>> for VLP-16.  I have used this in combination with the PCL plugin in the
>>>>>>> past, but the build is not straightforward at this time.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> The binaries you linked to here still require installation of
>>>>>>>> Paraview and PCL correct?
>>>>>>>>
>>>>>>>>
>>>>>>> This binary is ParaView with the pcl plugin built and packaged.  If
>>>>>>> you download this it includes paraview and PCL.
>>>>>>>
>>>>>>> --
>>>>>>> Casey B Goodlett, PhD
>>>>>>> Technical Leader
>>>>>>> Kitware, Inc. - North Carolina Office
>>>>>>> http://www.kitware.com
>>>>>>> (919) 969-6990 x310
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Eric Younkin LTJG/NOAA
>>>>>> HSTP Liaison - East
>>>>>> Marine Operations Center - Atlantic
>>>>>> 439 W York St
>>>>>> Norfolk, VA 23510
>>>>>> Cell: 828-331-8197
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Eric Younkin LTJG/NOAA
>>>>> HSTP Liaison - East
>>>>> Marine Operations Center - Atlantic
>>>>> 439 W York St
>>>>> Norfolk, VA 23510
>>>>> Cell: 828-331-8197
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Casey B Goodlett, PhD
>>>> Technical Leader
>>>> Kitware, Inc. - North Carolina Office
>>>> http://www.kitware.com
>>>> (919) 969-6990 x310
>>>>
>>>
>>>
>>>
>>> --
>>> Eric Younkin LTJG/NOAA
>>> HSTP Liaison - East
>>> Marine Operations Center - Atlantic
>>> 439 W York St
>>> Norfolk, VA 23510
>>> Cell: 828-331-8197
>>>
>>
>>
>>
>> --
>> Casey B Goodlett, PhD
>> Technical Leader
>> Kitware, Inc. - North Carolina Office
>> http://www.kitware.com
>> (919) 969-6990 x310
>>
>
>
>
> --
> Eric Younkin LTJG/NOAA
> HSTP Liaison - East
> Marine Operations Center - Atlantic
> 439 W York St
> Norfolk, VA 23510
> Cell: 828-331-8197
>



-- 
Casey B Goodlett, PhD
Technical Leader
Kitware, Inc. - North Carolina Office
http://www.kitware.com
(919) 969-6990 x310
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150713/86b86827/attachment.html>

From ben.boeckel at kitware.com  Mon Jul 13 09:49:50 2015
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Mon, 13 Jul 2015 09:49:50 -0400
Subject: [Paraview] Qt
In-Reply-To: <86722d04089940a18075b985091086b1@ES01AMSNLNT.srn.sandia.gov>
References: <86722d04089940a18075b985091086b1@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <20150713134950.GA9629@megas.kitware.com>

On Sat, Jul 11, 2015 at 00:16:19 +0000, Scott, W Alan wrote:
> I notice that the Superbuild is running Qt 5.4.1.  Any idea where I
> can find the Windows installer (i.e., I don't want to build from
> source)?

Also, Qt5 is currently "experimental" in that it is known that there are
issues with it in some places. Qt4 is still the officially supported
version and is still in the superbuild.

--Ben

From eric.g.younkin at noaa.gov  Mon Jul 13 10:04:41 2015
From: eric.g.younkin at noaa.gov (Eric Younkin - NOAA Federal)
Date: Mon, 13 Jul 2015 10:04:41 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAOqyOuEdwX+2_+7_Q-qfmCHF=oXSgTmJ9U3kEhn8ut+Dc5BEQg@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <CAFe6qKgoBR7HU6MHCDTKr_HCxBGu_eU3St2D5+UjQ3zrBwqcbg@mail.gmail.com>
 <CAOqyOuG9-w-TFEXJO1+8EvtAQLK-JJE3Rr8XqVLG=JObe69sNg@mail.gmail.com>
 <CAFe6qKg-_LHR3tHZ10H78PZJcF2rAVV8bEOH_y_Bt0h+C9jMyw@mail.gmail.com>
 <CAFe6qKhUiTADyYM9OTyWZg5RtvctezOxnREXnL40BsR-Ny=EoA@mail.gmail.com>
 <CAOqyOuH60D5LXthUwvSUViCWLqvrTz1z5a9wu-aCX3c4g-GEgQ@mail.gmail.com>
 <CAFe6qKhT6PvOoQRdOyAriiLJbc4D-zVJ-TtLgsyitECHCrsz8w@mail.gmail.com>
 <CAOqyOuGCULt0Lm4GBzxSLifuv4OoVJ_G-k_rhYMpCG4XE1tPLQ@mail.gmail.com>
 <CAFe6qKhhgem8+jPVRyJoaQrY-WJgW3vne7xDFHP41w332FWQPA@mail.gmail.com>
 <CAOqyOuEdwX+2_+7_Q-qfmCHF=oXSgTmJ9U3kEhn8ut+Dc5BEQg@mail.gmail.com>
Message-ID: <CAFe6qKhd060BfDzZV-dA6towMGjTA-hpTpn10XkvtvhviyMgXA@mail.gmail.com>

Casey,

Thanks.  This is just building the latest vanilla Paraview from source.

V/R,
Eric

On Mon, Jul 13, 2015 at 9:48 AM, Casey Goodlett <casey.goodlett at kitware.com>
wrote:

> Eric,
>
> I am not familiar with this problem.
>
> The code for the PCL plugin is now hosted at github here
> https://github.com/Kitware/PCLPlugin
>
> Best Regards,
>
> On Fri, Jul 10, 2015 at 8:32 PM, Eric Younkin - NOAA Federal <
> eric.g.younkin at noaa.gov> wrote:
>
>> Casey,
>>
>> When building Paraview 4.3.1 from source with QT5.5 in Visual Studio
>> 2013, I get 3 failed out of 569.  I pasted in the relevant parts of the VS
>> output log below (full log too big to attach):
>>
>> 567>  Generating Code...
>> 567>     Creating library
>> C:/Users/eric.g.younkin/Documents/PCL_ParaView/ParaView-v4.3.1-source/build/lib/Debug/MobileRemoteControl.lib
>> and object
>> C:/Users/eric.g.younkin/Documents/PCL_ParaView/ParaView-v4.3.1-source/build/lib/Debug/MobileRemoteControl.exp
>> 567>  MobileRemoteControl.vcxproj ->
>> C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\bin\Debug\MobileRemoteControl.dll
>> 568>C:\Program Files
>> (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(607,5):
>> error MSB6006: "link.exe" exited with code 1120.
>> 568>MSVCRTD.lib(crtexew.obj) : error LNK2019: unresolved external symbol
>> WinMain referenced in function __tmainCRTStartup
>> 568>C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\bin\Debug\paraview.exe
>> : fatal error LNK1120: 1 unresolved externals
>> 569>------ Build started: Project: ALL_BUILD, Configuration: Debug x64
>> ------
>> 569>  Building Custom Rule
>> C:/Users/eric.g.younkin/Documents/PCL_ParaView/ParaView-v4.3.1-source/CMakeLists.txt
>> 569>  CMake does not need to re-run because
>> C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\CMakeFiles\generate.stamp
>> is up-to-date.
>> ========== Build: 566 succeeded, 3 failed, 0 up-to-date, 0 skipped
>> ==========
>>
>> Doing some Google searches seem to indicate that in order to clear the
>> LNK2019 error, I would need to change the project type
>> <http://stackoverflow.com/questions/6626397/error-lnk2019-unresolved-external-symbol-winmain16-referenced-in-function>.
>> And that in order to do that, I would need to change the configuration type from
>> utility to something else
>> <http://gotoanswer.com/?q=No+Linker+option+in+Visual+Studio+Project+Properties>
>> .
>>
>> I suspect that I am just missing something obvious, but I'm not sure what
>> it is.  Can you offer any advice?
>>
>> Thanks,
>> Eric
>>
>> On Fri, Jul 10, 2015 at 12:03 PM, Casey Goodlett <
>> casey.goodlett at kitware.com> wrote:
>>
>>> You should compile against the VTK of paraview.  I have not tested Qt
>>> 5.5.
>>>
>>> I have not recently tested building VeloView  against paraview outside
>>> of the VeloView superbuild.  There may be unexpected problems.
>>>
>>> On Fri, Jul 10, 2015 at 11:49 AM, Eric Younkin - NOAA Federal <
>>> eric.g.younkin at noaa.gov> wrote:
>>>
>>>> Thanks Casey.  I'm reading in the Veloview Developer guide (
>>>> https://github.com/Kitware/VeloView/tree/master/Documentation) that
>>>> Veloview requires VTK6 and Qt 4.8.  I'm currently compiling Paraview from
>>>> source using Qt5.5 and VTK libraries that came with Paraview source.  Do I
>>>> need to download VTK6 and Qt4.8 and use those?  I've had some issues with
>>>> VS2013 and compiling with Qt4.
>>>>
>>>> Also, I'm currently getting the following repeating error upon
>>>> configuring in CMake:
>>>>
>>>> CMake Warning (dev) in ThirdParty/QtTesting/vtkqttesting/CMakeLists.txt:
>>>> Policy CMP0020 is not set: Automatically link Qt executables to qtmain
>>>> target on Windows. Run "cmake --help-policy CMP0020" for policy details.
>>>> Use the cmake_policy command to set the policy and suppress this
>>>> warning.
>>>> This warning is for project developers. Use -Wno-dev to suppress it.
>>>>
>>>> I'm seeing some references on the VTK users group (
>>>> http://public.kitware.com/pipermail/vtkusers/2013-July/080543.html)
>>>> that seem to indicate you can ignore them.  Any reason I shouldn't continue
>>>> with Qt5.5?
>>>>
>>>> Thanks,
>>>> Eric
>>>>
>>>> On Fri, Jul 10, 2015 at 10:43 AM, Casey Goodlett <
>>>> casey.goodlett at kitware.com> wrote:
>>>>
>>>>> Eric,
>>>>>
>>>>> That paper describes the approach for filter wrapping.  You will also
>>>>> need to compile VeloView against your paraview build and then include the
>>>>> VeloView plugin alongside the PCL plugin.
>>>>>
>>>>> Hope that helps.
>>>>>
>>>>> On Thu, Jul 9, 2015 at 3:00 PM, Eric Younkin - NOAA Federal <
>>>>> eric.g.younkin at noaa.gov> wrote:
>>>>>
>>>>>> I should also mention that I have been reading this paper
>>>>>> <http://www.paraview.org/Wiki/images/1/1e/Paper.pdf> and a few other
>>>>>> sources.  I think I have a basic idea of the framework.
>>>>>>
>>>>>> On Thu, Jul 9, 2015 at 11:33 AM, Eric Younkin - NOAA Federal <
>>>>>> eric.g.younkin at noaa.gov> wrote:
>>>>>>
>>>>>>> Thanks Casey.  For someone with only moderate programming
>>>>>>> experience, how difficult would you say creating those additional wrappers
>>>>>>> and building a VLP-16 paraview plugin would be?  Do you happen to have any
>>>>>>> resources or guides for doing so?
>>>>>>>
>>>>>>> I will continue to look at building from source and check out
>>>>>>> Project Tango.  Thanks for the link.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Eric
>>>>>>>
>>>>>>> On Thu, Jul 9, 2015 at 11:14 AM, Casey Goodlett <
>>>>>>> casey.goodlett at kitware.com> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Jul 9, 2015 at 10:53 AM, Eric Younkin - NOAA Federal <
>>>>>>>> eric.g.younkin at noaa.gov> wrote:
>>>>>>>>
>>>>>>>>> Casey,
>>>>>>>>>
>>>>>>>>> I am mostly interested in the feature extraction routines and
>>>>>>>>> Paraview integration with the Velodyne VLP-16.  I'd like to experiment with
>>>>>>>>> PCL algorithms to try and pick out fixed objects such as buoys or piers
>>>>>>>>> from a VLP-16 mounted on our research vessel as we travel up the coast.  I
>>>>>>>>> think most of my errors are from attempting to build using Visual Studio
>>>>>>>>> 2013 pro and older Qt/PCL versions.  If I can use the most recent versions,
>>>>>>>>> that might help things.
>>>>>>>>>
>>>>>>>>
>>>>>>>> Sounds like a cool project.  You may need to add some additional
>>>>>>>> wrappers for feature extraction if you are looking for things beyond the
>>>>>>>> sample consensus models that we have.  I dont think any of the point
>>>>>>>> feature histogram utilities are currently wrapped.
>>>>>>>>
>>>>>>>> Windows builds of the whole stack are a bit tricky.  Feel free to
>>>>>>>> share your error messages, and I'll help where I can.
>>>>>>>>
>>>>>>>> The plugin does not include support for the VLP-16 in its current
>>>>>>>> state.  We have another project VeloView
>>>>>>>> <https://github.com/Kitware/VeloView> that builds a paraview
>>>>>>>> plugin for VLP-16.  I have used this in combination with the PCL plugin in
>>>>>>>> the past, but the build is not straightforward at this time.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> The binaries you linked to here still require installation of
>>>>>>>>> Paraview and PCL correct?
>>>>>>>>>
>>>>>>>>>
>>>>>>>> This binary is ParaView with the pcl plugin built and packaged.  If
>>>>>>>> you download this it includes paraview and PCL.
>>>>>>>>
>>>>>>>> --
>>>>>>>> Casey B Goodlett, PhD
>>>>>>>> Technical Leader
>>>>>>>> Kitware, Inc. - North Carolina Office
>>>>>>>> http://www.kitware.com
>>>>>>>> (919) 969-6990 x310
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Eric Younkin LTJG/NOAA
>>>>>>> HSTP Liaison - East
>>>>>>> Marine Operations Center - Atlantic
>>>>>>> 439 W York St
>>>>>>> Norfolk, VA 23510
>>>>>>> Cell: 828-331-8197
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Eric Younkin LTJG/NOAA
>>>>>> HSTP Liaison - East
>>>>>> Marine Operations Center - Atlantic
>>>>>> 439 W York St
>>>>>> Norfolk, VA 23510
>>>>>> Cell: 828-331-8197
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Casey B Goodlett, PhD
>>>>> Technical Leader
>>>>> Kitware, Inc. - North Carolina Office
>>>>> http://www.kitware.com
>>>>> (919) 969-6990 x310
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Eric Younkin LTJG/NOAA
>>>> HSTP Liaison - East
>>>> Marine Operations Center - Atlantic
>>>> 439 W York St
>>>> Norfolk, VA 23510
>>>> Cell: 828-331-8197
>>>>
>>>
>>>
>>>
>>> --
>>> Casey B Goodlett, PhD
>>> Technical Leader
>>> Kitware, Inc. - North Carolina Office
>>> http://www.kitware.com
>>> (919) 969-6990 x310
>>>
>>
>>
>>
>> --
>> Eric Younkin LTJG/NOAA
>> HSTP Liaison - East
>> Marine Operations Center - Atlantic
>> 439 W York St
>> Norfolk, VA 23510
>> Cell: 828-331-8197
>>
>
>
>
> --
> Casey B Goodlett, PhD
> Technical Leader
> Kitware, Inc. - North Carolina Office
> http://www.kitware.com
> (919) 969-6990 x310
>



-- 
Eric Younkin LTJG/NOAA
HSTP Liaison - East
Marine Operations Center - Atlantic
439 W York St
Norfolk, VA 23510
Cell: 828-331-8197
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150713/e4cfb30f/attachment-0001.html>

From berk.geveci at kitware.com  Mon Jul 13 10:26:57 2015
From: berk.geveci at kitware.com (Berk Geveci)
Date: Mon, 13 Jul 2015 10:26:57 -0400
Subject: [Paraview] Fwd: ANNOUNCE: Kitware is hiring
In-Reply-To: <CAE32kpUDB1uOzjKkv8nqNG4nK+YLE9eiz74A4Aejxz2gY7FO-A@mail.gmail.com>
References: <CAE32kpUDB1uOzjKkv8nqNG4nK+YLE9eiz74A4Aejxz2gY7FO-A@mail.gmail.com>
Message-ID: <CAE32kpUKyNkxvd1wZiqLak+idmTB4Dy6b1OQTdEGzKgJzpCWWw@mail.gmail.com>

Hi folks,

We are looking to hire visualization developers to our Scientific Computing
team. If you are a talented visualization researcher and developer with
strong C++ skills, please consider applying.  You will join a great team
and work on many interesting and challenging technical problems - always
aiming to deliver robust and widely used software solutions.

For the full posting see:
http://tinyurl.com/l8sgvzw

JOB DESCRIPTION
Kitware is seeking to hire highly skilled Research and Development
Engineers (R&D Engineers) to join our Scientific Computing team and
contribute to our scientific and information visualization efforts.
Candidates will work to develop and improve leading visualization software
solutions.

Kitware collaborates on a multitude of basic and applied research and
development projects. Our collaborators include the top universities from
around the world, national research labs, medical device manufacturers, car
manufacturers, oil and gas companies, financial institutes, and many
others. The projects range from extending our open source C++ libraries and
applications, such as VTK, ParaView, and CMake, to developing proprietary
domain-specific vertical applications for a wide array of platforms
including web and mobile devices.

By joining our team you will participate in a dynamic work environment with
exceptionally talented and friendly coworkers who are committed to
high-quality development practices.  You will collaborate with esteemed
researchers from around the world by:

* Designing and developing scalable data analysis and visualization tools
for use by  researchers and professionals from various domains;

* Solving a wide array of problems ranging from developing distributed
memory parallel algorithms for data analysis, optimizing distributed
parallel codes to compiling and maintaining software on supercomputers.

* Designing and developing tools to improve scientific data analysis
workflows;

* Contributing to and supporting our dynamic open source communities built
around several of our open source tools.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150713/acfd8c30/attachment.html>

From deq11009 at fe.up.pt  Mon Jul 13 12:40:49 2015
From: deq11009 at fe.up.pt (deq11009)
Date: Mon, 13 Jul 2015 17:40:49 +0100
Subject: [Paraview] Wrong fetched data
In-Reply-To: <CAB5Fpx4zX0FND+bOdu24oHCnMfzLwgoNbPdp8jQQLhkRw_0UuQ@mail.gmail.com>
References: <5000545d13da0baa4fa1c3d1e3c44423@fe.up.pt>
 <CAB5Fpx5xsoTOeBdtEGLBMEDVG5YonkPb5maRPKVpCbbYCJzeGA@mail.gmail.com>
 <f79e260d16a28fb08f353b8626184dee@fe.up.pt>
 <CAB5Fpx4zX0FND+bOdu24oHCnMfzLwgoNbPdp8jQQLhkRw_0UuQ@mail.gmail.com>
Message-ID: <d9d613d6842a39d844e9fc3b6f63369a@fe.up.pt>

Hi,

I can share the following: http://we.tl/3CPwe5y9vA
An easy way to see the problem might be creating a line source in the 
axis of the cylinder, doing Resample and see where interface is located.

Thanks,
Filipe Direito


On 13.07.2015 04:33, Cory Quammen wrote:
> Interesting. Is is possible for you to share the data file(s)?
>
> Thanks,
> Cory
>
> On Mon, Jul 6, 2015 at 10:23 AM, deq11009 <deq11009 at fe.up.pt [12]>
> wrote:
>
>> Hi,
>>
>> Thank you for your reply.
>>
>> No, the mistake is not there. In the meantime I did realize what is
>> exactly happening.
>>
>> I have, say, 200 timesteps.
>> From 0 to 6, data obtained from my code matches the data when I
>> just use the GUI.
>> Starting in timestep 7 (always) till the end, data (for all
>> timesteps) is the data from the last timestep.
>> So, when in python shell I go to timestep 6, I see timestep 6. But
>> when I go to timestep 7, or 100, or 133, I see timestep 199. At the
>> same time, if I go to the GUI, everything is ok.
>>
>> By coincidence, the ".case" time step data is organized in seven
>> columns. Is this related to the problem?
>>
>> Thank you
>> Filipe Direito
>>
>> On 03.07.2015 15:05, Cory Quammen wrote:
>>
>>> Hi Filipe,
>>>
>>> Perhaps the array at index 7 is not the array you are expecting?
>>> Could
>>> you access the array by name instead, .e.g.,
>>>
>>> dAxis.GetPointData().GetArray(variable_name).GetValue(150)
>>>
>>> and see if that works better?
>>>
>>> Thanks,
>>> Cory
>>>
>>> On Wed, Jul 1, 2015 at 1:44 PM, deq11009 <deq11009 at fe.up.pt [6]
>>> [6]>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I am currently using Paraview 4.2, 64, in Windows. (but tried
>>>> 4.3
>>>> and same problem happened)
>>>>
>>>> My case is Ensight transient. Cylinder with 3.6 million cells,
>>>> two-phase flow.
>>>>
>>>> I created a python code, which I run from the shell in the GUI.
>>>>
>>>> The main parts of the code are:
>>>>
>>>> enscase = EnSightReader(CaseFileName = direcp + ensfinal.case)
>>>> ...
>>>> axis = Line()
>>>> ...
>>>> rAxis = ResampleWithDataset(Input = enscase , Source = axis)
>>>> ...
>>>> rAxis.SMProxy.UpdatePipeline(7) # enscase.SMProxy yields same
>>>> problem
>>>> rAxis.UpdatePipelineInformation()
>>>> dAxis = servermanager.Fetch(rAxis)
>>>>
>>>> Now, for example:
>>>> print dAxis.GetPointData().GetArray(7).GetValue(150)
>>>> which gives me the value 150 of the phase array.
>>>>
>>>> This data is wrong. On the other hand, if I go to the GUI
>>>> Pipeline
>>>> and create a Spreadsheet, the values are the real ones
>>>> (confirmed in
>>>> Fluent).
>>>>
>>>> So, the fetched data in the python shell is, for some reason,
>>>> wrong.
>>>> What is my mistake?
>>>>
>>>> Thanks
>>>> Filipe Direito
>>>>
>>>> _______________________________________________
>>>> Powered by www.kitware.com [1] [1]
>>>>
>>>> Visit other Kitware open-source projects at
>>>> http://www.kitware.com/opensource/opensource.html [2] [2]
>>>>
>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>> http://paraview.org/Wiki/ParaView [3] [3]
>>>>
>>>> Search the list archives at:
>>>> http://markmail.org/search/?q=ParaView [4]
>>>> [4]
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://public.kitware.com/mailman/listinfo/paraview [5] [5]
>>
>> _______________________________________________
>> Powered by www.kitware.com [7]
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html [8]
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView [9]
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>> [10]
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview [11]
>
> --
>
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
> Links:
> ------
> [1] http://www.kitware.com
> [2] http://www.kitware.com/opensource/opensource.html
> [3] http://paraview.org/Wiki/ParaView
> [4] http://markmail.org/search/?q=ParaView
> [5] http://public.kitware.com/mailman/listinfo/paraview
> [6] mailto:deq11009 at fe.up.pt
> [7] http://www.kitware.com
> [8] http://www.kitware.com/opensource/opensource.html
> [9] http://paraview.org/Wiki/ParaView
> [10] http://markmail.org/search/?q=ParaView
> [11] http://public.kitware.com/mailman/listinfo/paraview
> [12] mailto:deq11009 at fe.up.pt


From eric.g.younkin at noaa.gov  Mon Jul 13 13:32:39 2015
From: eric.g.younkin at noaa.gov (Eric Younkin - NOAA Federal)
Date: Mon, 13 Jul 2015 13:32:39 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAFe6qKhd060BfDzZV-dA6towMGjTA-hpTpn10XkvtvhviyMgXA@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <CAFe6qKgoBR7HU6MHCDTKr_HCxBGu_eU3St2D5+UjQ3zrBwqcbg@mail.gmail.com>
 <CAOqyOuG9-w-TFEXJO1+8EvtAQLK-JJE3Rr8XqVLG=JObe69sNg@mail.gmail.com>
 <CAFe6qKg-_LHR3tHZ10H78PZJcF2rAVV8bEOH_y_Bt0h+C9jMyw@mail.gmail.com>
 <CAFe6qKhUiTADyYM9OTyWZg5RtvctezOxnREXnL40BsR-Ny=EoA@mail.gmail.com>
 <CAOqyOuH60D5LXthUwvSUViCWLqvrTz1z5a9wu-aCX3c4g-GEgQ@mail.gmail.com>
 <CAFe6qKhT6PvOoQRdOyAriiLJbc4D-zVJ-TtLgsyitECHCrsz8w@mail.gmail.com>
 <CAOqyOuGCULt0Lm4GBzxSLifuv4OoVJ_G-k_rhYMpCG4XE1tPLQ@mail.gmail.com>
 <CAFe6qKhhgem8+jPVRyJoaQrY-WJgW3vne7xDFHP41w332FWQPA@mail.gmail.com>
 <CAOqyOuEdwX+2_+7_Q-qfmCHF=oXSgTmJ9U3kEhn8ut+Dc5BEQg@mail.gmail.com>
 <CAFe6qKhd060BfDzZV-dA6towMGjTA-hpTpn10XkvtvhviyMgXA@mail.gmail.com>
Message-ID: <CAFe6qKjE1cE9uTgKrcci+jAm5uafyHim-3GT0sqSuthf1XYCUA@mail.gmail.com>

Casey,

I don't mean to take up so much of your time, but I've been reviewing the
cmake configuration and I found that there were a number of HDF5 tests that
failed (see below).  Is that significant?

*Found PythonInterp: C:/Program Files/Pydro64/python.exe (found suitable
version "2.7.3", minimum required is "2") *

*Found ZLIB:
C:/Users/eric.g.younkin/Documents/PCL_ParaView/flann-1.8.4/hdf5/lib/zlib.lib
(found version "1.2.8") *

*HDF5: SOVERSION: 8.0.2*

*HDF5: Performing Other Test STDC_HEADERS - Success*

*HDF5: Performing CXX Test OLD_HEADER_FILENAME - Failed*

*HDF5: Performing CXX Test H5_NO_NAMESPACE - Failed*

*HDF5: Performing CXX Test H5_NO_STD - Failed*

*HDF5: Performing CXX Test BOOL_NOTDEFINED - Failed*

*HDF5: Performing CXX Test NO_STATIC_CAST - Failed*

*HDF5: Checking for InitOnceExecuteOnce:*

*HDF5: Performing Test InitOnceExecuteOnce - Success*

*HDF5: Performing Other Test INLINE_TEST_inline - Failed*

*HDF5: Performing Other Test INLINE_TEST___inline__ - Failed*

*HDF5: Performing Other Test INLINE_TEST___inline - Success*

*HDF5: checking IF converting from long double to integers is accurate...
yes*

*HDF5: checking IF accurately converting from integers to long double...
yes*

*HDF5: Checking IF accurately converting unsigned long to float values...
yes*

*HDF5: Checking IF accurately roundup converting floating-point to unsigned
long long values... yes*

*HDF5: Checking IF right maximum converting floating-point to unsigned long
long values... yes*

*HDF5: Checking IF correctly converting long double to unsigned int
values... yes*

*HDF5: Checking IF overflows normally converting floating-point to integer
values... yes*

*HDF5: Checking IF correctly converting long double to (unsigned) long long
values... yes*

*HDF5: Checking IF correctly converting (unsigned) long long to long double
values... yes*

*HDF5: Checking IF alignment restrictions are strictly enforced... yes*

*HDF5: Filter ZLIB is ON*


Also, one of the errors I saw upon rebuilding:


*error C1041: cannot open program database
'c:\users\eric.g.younkin\documents\pcl_paraview\paraview-v4.3.1-source\build\plugins\sciberquesttoolkit\paraviewplugin\sciberquesttoolkit.dir\debug\vc120.pdb';
if multiple CL.EXE write to the same .PDB file, please use /FS
C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\Plugins\SciberQuestToolKit\ParaViewPlugin\moc_pqSQFieldTracerImplementation.cpp)*


Led me to the moc_pqSQFieldTracerImplementation.cpp which had a comment at
the top stating


*"This file was generated using the moc from 5.5.0. It cannot be used with
the include files from this version of Qt. (The moc has changed too much.)"*


So I will try with Qt5.4.1 instead.


Thanks,
Eric


On Mon, Jul 13, 2015 at 10:04 AM, Eric Younkin - NOAA Federal <
eric.g.younkin at noaa.gov> wrote:

> Casey,
>
> Thanks.  This is just building the latest vanilla Paraview from source.
>
> V/R,
> Eric
>
> On Mon, Jul 13, 2015 at 9:48 AM, Casey Goodlett <
> casey.goodlett at kitware.com> wrote:
>
>> Eric,
>>
>> I am not familiar with this problem.
>>
>> The code for the PCL plugin is now hosted at github here
>> https://github.com/Kitware/PCLPlugin
>>
>> Best Regards,
>>
>> On Fri, Jul 10, 2015 at 8:32 PM, Eric Younkin - NOAA Federal <
>> eric.g.younkin at noaa.gov> wrote:
>>
>>> Casey,
>>>
>>> When building Paraview 4.3.1 from source with QT5.5 in Visual Studio
>>> 2013, I get 3 failed out of 569.  I pasted in the relevant parts of the VS
>>> output log below (full log too big to attach):
>>>
>>> 567>  Generating Code...
>>> 567>     Creating library
>>> C:/Users/eric.g.younkin/Documents/PCL_ParaView/ParaView-v4.3.1-source/build/lib/Debug/MobileRemoteControl.lib
>>> and object
>>> C:/Users/eric.g.younkin/Documents/PCL_ParaView/ParaView-v4.3.1-source/build/lib/Debug/MobileRemoteControl.exp
>>> 567>  MobileRemoteControl.vcxproj ->
>>> C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\bin\Debug\MobileRemoteControl.dll
>>> 568>C:\Program Files
>>> (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(607,5):
>>> error MSB6006: "link.exe" exited with code 1120.
>>> 568>MSVCRTD.lib(crtexew.obj) : error LNK2019: unresolved external symbol
>>> WinMain referenced in function __tmainCRTStartup
>>> 568>C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\bin\Debug\paraview.exe
>>> : fatal error LNK1120: 1 unresolved externals
>>> 569>------ Build started: Project: ALL_BUILD, Configuration: Debug x64
>>> ------
>>> 569>  Building Custom Rule
>>> C:/Users/eric.g.younkin/Documents/PCL_ParaView/ParaView-v4.3.1-source/CMakeLists.txt
>>> 569>  CMake does not need to re-run because
>>> C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\CMakeFiles\generate.stamp
>>> is up-to-date.
>>> ========== Build: 566 succeeded, 3 failed, 0 up-to-date, 0 skipped
>>> ==========
>>>
>>> Doing some Google searches seem to indicate that in order to clear the
>>> LNK2019 error, I would need to change the project type
>>> <http://stackoverflow.com/questions/6626397/error-lnk2019-unresolved-external-symbol-winmain16-referenced-in-function>.
>>> And that in order to do that, I would need to change the configuration type from
>>> utility to something else
>>> <http://gotoanswer.com/?q=No+Linker+option+in+Visual+Studio+Project+Properties>
>>> .
>>>
>>> I suspect that I am just missing something obvious, but I'm not sure
>>> what it is.  Can you offer any advice?
>>>
>>> Thanks,
>>> Eric
>>>
>>> On Fri, Jul 10, 2015 at 12:03 PM, Casey Goodlett <
>>> casey.goodlett at kitware.com> wrote:
>>>
>>>> You should compile against the VTK of paraview.  I have not tested Qt
>>>> 5.5.
>>>>
>>>> I have not recently tested building VeloView  against paraview outside
>>>> of the VeloView superbuild.  There may be unexpected problems.
>>>>
>>>> On Fri, Jul 10, 2015 at 11:49 AM, Eric Younkin - NOAA Federal <
>>>> eric.g.younkin at noaa.gov> wrote:
>>>>
>>>>> Thanks Casey.  I'm reading in the Veloview Developer guide (
>>>>> https://github.com/Kitware/VeloView/tree/master/Documentation) that
>>>>> Veloview requires VTK6 and Qt 4.8.  I'm currently compiling Paraview from
>>>>> source using Qt5.5 and VTK libraries that came with Paraview source.  Do I
>>>>> need to download VTK6 and Qt4.8 and use those?  I've had some issues with
>>>>> VS2013 and compiling with Qt4.
>>>>>
>>>>> Also, I'm currently getting the following repeating error upon
>>>>> configuring in CMake:
>>>>>
>>>>> CMake Warning (dev) in
>>>>> ThirdParty/QtTesting/vtkqttesting/CMakeLists.txt:
>>>>> Policy CMP0020 is not set: Automatically link Qt executables to qtmain
>>>>> target on Windows. Run "cmake --help-policy CMP0020" for policy
>>>>> details.
>>>>> Use the cmake_policy command to set the policy and suppress this
>>>>> warning.
>>>>> This warning is for project developers. Use -Wno-dev to suppress it.
>>>>>
>>>>> I'm seeing some references on the VTK users group (
>>>>> http://public.kitware.com/pipermail/vtkusers/2013-July/080543.html)
>>>>> that seem to indicate you can ignore them.  Any reason I shouldn't continue
>>>>> with Qt5.5?
>>>>>
>>>>> Thanks,
>>>>> Eric
>>>>>
>>>>> On Fri, Jul 10, 2015 at 10:43 AM, Casey Goodlett <
>>>>> casey.goodlett at kitware.com> wrote:
>>>>>
>>>>>> Eric,
>>>>>>
>>>>>> That paper describes the approach for filter wrapping.  You will also
>>>>>> need to compile VeloView against your paraview build and then include the
>>>>>> VeloView plugin alongside the PCL plugin.
>>>>>>
>>>>>> Hope that helps.
>>>>>>
>>>>>> On Thu, Jul 9, 2015 at 3:00 PM, Eric Younkin - NOAA Federal <
>>>>>> eric.g.younkin at noaa.gov> wrote:
>>>>>>
>>>>>>> I should also mention that I have been reading this paper
>>>>>>> <http://www.paraview.org/Wiki/images/1/1e/Paper.pdf> and a few
>>>>>>> other sources.  I think I have a basic idea of the framework.
>>>>>>>
>>>>>>> On Thu, Jul 9, 2015 at 11:33 AM, Eric Younkin - NOAA Federal <
>>>>>>> eric.g.younkin at noaa.gov> wrote:
>>>>>>>
>>>>>>>> Thanks Casey.  For someone with only moderate programming
>>>>>>>> experience, how difficult would you say creating those additional wrappers
>>>>>>>> and building a VLP-16 paraview plugin would be?  Do you happen to have any
>>>>>>>> resources or guides for doing so?
>>>>>>>>
>>>>>>>> I will continue to look at building from source and check out
>>>>>>>> Project Tango.  Thanks for the link.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Eric
>>>>>>>>
>>>>>>>> On Thu, Jul 9, 2015 at 11:14 AM, Casey Goodlett <
>>>>>>>> casey.goodlett at kitware.com> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Jul 9, 2015 at 10:53 AM, Eric Younkin - NOAA Federal <
>>>>>>>>> eric.g.younkin at noaa.gov> wrote:
>>>>>>>>>
>>>>>>>>>> Casey,
>>>>>>>>>>
>>>>>>>>>> I am mostly interested in the feature extraction routines and
>>>>>>>>>> Paraview integration with the Velodyne VLP-16.  I'd like to experiment with
>>>>>>>>>> PCL algorithms to try and pick out fixed objects such as buoys or piers
>>>>>>>>>> from a VLP-16 mounted on our research vessel as we travel up the coast.  I
>>>>>>>>>> think most of my errors are from attempting to build using Visual Studio
>>>>>>>>>> 2013 pro and older Qt/PCL versions.  If I can use the most recent versions,
>>>>>>>>>> that might help things.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Sounds like a cool project.  You may need to add some additional
>>>>>>>>> wrappers for feature extraction if you are looking for things beyond the
>>>>>>>>> sample consensus models that we have.  I dont think any of the point
>>>>>>>>> feature histogram utilities are currently wrapped.
>>>>>>>>>
>>>>>>>>> Windows builds of the whole stack are a bit tricky.  Feel free to
>>>>>>>>> share your error messages, and I'll help where I can.
>>>>>>>>>
>>>>>>>>> The plugin does not include support for the VLP-16 in its current
>>>>>>>>> state.  We have another project VeloView
>>>>>>>>> <https://github.com/Kitware/VeloView> that builds a paraview
>>>>>>>>> plugin for VLP-16.  I have used this in combination with the PCL plugin in
>>>>>>>>> the past, but the build is not straightforward at this time.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> The binaries you linked to here still require installation of
>>>>>>>>>> Paraview and PCL correct?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> This binary is ParaView with the pcl plugin built and packaged.
>>>>>>>>> If you download this it includes paraview and PCL.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Casey B Goodlett, PhD
>>>>>>>>> Technical Leader
>>>>>>>>> Kitware, Inc. - North Carolina Office
>>>>>>>>> http://www.kitware.com
>>>>>>>>> (919) 969-6990 x310
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Eric Younkin LTJG/NOAA
>>>>>>>> HSTP Liaison - East
>>>>>>>> Marine Operations Center - Atlantic
>>>>>>>> 439 W York St
>>>>>>>> Norfolk, VA 23510
>>>>>>>> Cell: 828-331-8197
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Eric Younkin LTJG/NOAA
>>>>>>> HSTP Liaison - East
>>>>>>> Marine Operations Center - Atlantic
>>>>>>> 439 W York St
>>>>>>> Norfolk, VA 23510
>>>>>>> Cell: 828-331-8197
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Casey B Goodlett, PhD
>>>>>> Technical Leader
>>>>>> Kitware, Inc. - North Carolina Office
>>>>>> http://www.kitware.com
>>>>>> (919) 969-6990 x310
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Eric Younkin LTJG/NOAA
>>>>> HSTP Liaison - East
>>>>> Marine Operations Center - Atlantic
>>>>> 439 W York St
>>>>> Norfolk, VA 23510
>>>>> Cell: 828-331-8197
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Casey B Goodlett, PhD
>>>> Technical Leader
>>>> Kitware, Inc. - North Carolina Office
>>>> http://www.kitware.com
>>>> (919) 969-6990 x310
>>>>
>>>
>>>
>>>
>>> --
>>> Eric Younkin LTJG/NOAA
>>> HSTP Liaison - East
>>> Marine Operations Center - Atlantic
>>> 439 W York St
>>> Norfolk, VA 23510
>>> Cell: 828-331-8197
>>>
>>
>>
>>
>> --
>> Casey B Goodlett, PhD
>> Technical Leader
>> Kitware, Inc. - North Carolina Office
>> http://www.kitware.com
>> (919) 969-6990 x310
>>
>
>
>
> --
> Eric Younkin LTJG/NOAA
> HSTP Liaison - East
> Marine Operations Center - Atlantic
> 439 W York St
> Norfolk, VA 23510
> Cell: 828-331-8197
>



-- 
Eric Younkin LTJG/NOAA
HSTP Liaison - East
Marine Operations Center - Atlantic
439 W York St
Norfolk, VA 23510
Cell: 828-331-8197
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150713/1bb7ac84/attachment.html>

From casey.goodlett at kitware.com  Mon Jul 13 15:15:45 2015
From: casey.goodlett at kitware.com (Casey Goodlett)
Date: Mon, 13 Jul 2015 15:15:45 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAFe6qKjE1cE9uTgKrcci+jAm5uafyHim-3GT0sqSuthf1XYCUA@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <CAFe6qKgoBR7HU6MHCDTKr_HCxBGu_eU3St2D5+UjQ3zrBwqcbg@mail.gmail.com>
 <CAOqyOuG9-w-TFEXJO1+8EvtAQLK-JJE3Rr8XqVLG=JObe69sNg@mail.gmail.com>
 <CAFe6qKg-_LHR3tHZ10H78PZJcF2rAVV8bEOH_y_Bt0h+C9jMyw@mail.gmail.com>
 <CAFe6qKhUiTADyYM9OTyWZg5RtvctezOxnREXnL40BsR-Ny=EoA@mail.gmail.com>
 <CAOqyOuH60D5LXthUwvSUViCWLqvrTz1z5a9wu-aCX3c4g-GEgQ@mail.gmail.com>
 <CAFe6qKhT6PvOoQRdOyAriiLJbc4D-zVJ-TtLgsyitECHCrsz8w@mail.gmail.com>
 <CAOqyOuGCULt0Lm4GBzxSLifuv4OoVJ_G-k_rhYMpCG4XE1tPLQ@mail.gmail.com>
 <CAFe6qKhhgem8+jPVRyJoaQrY-WJgW3vne7xDFHP41w332FWQPA@mail.gmail.com>
 <CAOqyOuEdwX+2_+7_Q-qfmCHF=oXSgTmJ9U3kEhn8ut+Dc5BEQg@mail.gmail.com>
 <CAFe6qKhd060BfDzZV-dA6towMGjTA-hpTpn10XkvtvhviyMgXA@mail.gmail.com>
 <CAFe6qKjE1cE9uTgKrcci+jAm5uafyHim-3GT0sqSuthf1XYCUA@mail.gmail.com>
Message-ID: <CAOqyOuF_QEFCMBBYgDJNCF8O1gR+77Wwq=g3HEHab-oQ7UJM6w@mail.gmail.com>

On Mon, Jul 13, 2015 at 1:32 PM, Eric Younkin - NOAA Federal <
eric.g.younkin at noaa.gov> wrote:

> Casey,
>
> I don't mean to take up so much of your time, but I've been reviewing the
> cmake configuration and I found that there were a number of HDF5 tests that
> failed (see below).  Is that significant?
>
>
I do not think this is a problem.


> Also, one of the errors I saw upon rebuilding:
>
>
> *error C1041: cannot open program database
> 'c:\users\eric.g.younkin\documents\pcl_paraview\paraview-v4.3.1-source\build\plugins\sciberquesttoolkit\paraviewplugin\sciberquesttoolkit.dir\debug\vc120.pdb';
> if multiple CL.EXE write to the same .PDB file, please use /FS
> C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\Plugins\SciberQuestToolKit\ParaViewPlugin\moc_pqSQFieldTracerImplementation.cpp)*
>
>
> Led me to the moc_pqSQFieldTracerImplementation.cpp which had a comment at
> the top stating
>
>
> *"This file was generated using the moc from 5.5.0. It cannot be used with
> the include files from this version of Qt. (The moc has changed too much.)"*
>
>
> So I will try with Qt5.4.1 instead.
>
>
>
I am not familiar with this problem.  Maybe the filename is getting too
long for windows?  Maybe another developer can help with the Qt issues, I
am not an expert in this area.

Regards,

-- 
Casey B Goodlett, PhD
Technical Leader
Kitware, Inc. - North Carolina Office
http://www.kitware.com
(919) 969-6990 x310
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150713/383101a2/attachment.html>

From oksana_golovnya at mail.ru  Tue Jul 14 01:46:38 2015
From: oksana_golovnya at mail.ru (=?UTF-8?B?T2tzYW5h?=)
Date: Tue, 14 Jul 2015 08:46:38 +0300
Subject: [Paraview] =?utf-8?q?Molecular_dynamics_from_lammps?=
In-Reply-To: <CAE32kpXwMb6ZWuVZr2AENGQX-Q3Da7uNA+Yj=3CaHQLq1bodyw@mail.gmail.com>
References: <1436279999.571994242@f345.i.mail.ru>
 <1436514441.618845786@f254.i.mail.ru>
 <CAE32kpXwMb6ZWuVZr2AENGQX-Q3Da7uNA+Yj=3CaHQLq1bodyw@mail.gmail.com>
Message-ID: <1436852798.517668428@f416.i.mail.ru>

 At best it would be to keep atoms that are under a certain distance to the plane, however to keep only atoms belonging to the plane is also OK. Vectors should be glyphs, one atom with one vector.
May be it woould help if I attach the file?

Faithfully yours,
Oksana

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150714/d7e823b1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: t000.vtk
Type: application/octet-stream
Size: 124405 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150714/d7e823b1/attachment.obj>

From lmorandini at ieee.org  Tue Jul 14 04:09:55 2015
From: lmorandini at ieee.org (Luca Morandini)
Date: Tue, 14 Jul 2015 18:09:55 +1000
Subject: [Paraview] Compilation problem of ParaView 3.14.1 on Ubuntu 14.04
Message-ID: <mo2g4i$4io$1@ger.gmane.org>

I'm trying to compile a rather old version of ParaView (3.14.1) from source, since 
I need it to compile, in turn, the PCL plugin.

However, I was not able to build ParaView after successfully running ccmake to 
configure and generate the makefiles; in fact, when I try make, the result is:

[  0%] Built target vtkWrapHierarchy
[  0%] Built target vtkWrapPython
[  0%] Built target vtkWrapPythonInit
Scanning dependencies of target vtksys
[  0%] Building CXX object 
VTK/Utilities/kwsys/CMakeFiles/vtksys.dir/Directory.cxx.o 

In file included from 
/opt/ParaView-3.14.1-Source/Build/VTK/Utilities/vtksys/stl/string.hxx:29:0,
                  from 
/opt/ParaView-3.14.1-Source/Build/VTK/Utilities/vtksys/stl/string:49,
                  from 
/opt/ParaView-3.14.1-Source/VTK/Utilities/kwsys/Directory.cxx:17:
/opt/ParaView-3.14.1-Source/Build/VTK/Utilities/vtksys/ios/iostream:26:23: fatal 
error: iostream.h: No such file or directory
  # include <iostream.h>
                        ^
compilation terminated.
make[2]: *** [VTK/Utilities/kwsys/CMakeFiles/vtksys.dir/Directory.cxx.o] Error 1
make[1]: *** [VTK/Utilities/kwsys/CMakeFiles/vtksys.dir/all] Error 2
make: *** [all] Error 2


I tried to fiddle around with the CCMKake flags, but, despite my efforts, only a 
few modules compiled, hence I concluded there is something deeper that I am 
missing: could someone shed some light?

Luca Morandini
Data Architect - AURIN project
Melbourne eResearch Group
Department of Computing and Information Systems
University of Melbourne
Tel. +61 03 903 58 380
Skype: lmorandini


From biddisco at cscs.ch  Tue Jul 14 05:03:14 2015
From: biddisco at cscs.ch (Biddiscombe, John A.)
Date: Tue, 14 Jul 2015 09:03:14 +0000
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAOqyOuF_QEFCMBBYgDJNCF8O1gR+77Wwq=g3HEHab-oQ7UJM6w@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <CAFe6qKgoBR7HU6MHCDTKr_HCxBGu_eU3St2D5+UjQ3zrBwqcbg@mail.gmail.com>
 <CAOqyOuG9-w-TFEXJO1+8EvtAQLK-JJE3Rr8XqVLG=JObe69sNg@mail.gmail.com>
 <CAFe6qKg-_LHR3tHZ10H78PZJcF2rAVV8bEOH_y_Bt0h+C9jMyw@mail.gmail.com>
 <CAFe6qKhUiTADyYM9OTyWZg5RtvctezOxnREXnL40BsR-Ny=EoA@mail.gmail.com>
 <CAOqyOuH60D5LXthUwvSUViCWLqvrTz1z5a9wu-aCX3c4g-GEgQ@mail.gmail.com>
 <CAFe6qKhT6PvOoQRdOyAriiLJbc4D-zVJ-TtLgsyitECHCrsz8w@mail.gmail.com>
 <CAOqyOuGCULt0Lm4GBzxSLifuv4OoVJ_G-k_rhYMpCG4XE1tPLQ@mail.gmail.com>
 <CAFe6qKhhgem8+jPVRyJoaQrY-WJgW3vne7xDFHP41w332FWQPA@mail.gmail.com>
 <CAOqyOuEdwX+2_+7_Q-qfmCHF=oXSgTmJ9U3kEhn8ut+Dc5BEQg@mail.gmail.com>
 <CAFe6qKhd060BfDzZV-dA6towMGjTA-hpTpn10XkvtvhviyMgXA@mail.gmail.com>
 <CAFe6qKjE1cE9uTgKrcci+jAm5uafyHim-3GT0sqSuthf1XYCUA@mail.gmail.com>
 <CAOqyOuF_QEFCMBBYgDJNCF8O1gR+77Wwq=g3HEHab-oQ7UJM6w@mail.gmail.com>
Message-ID: <50320452A334BD42A5EC72BAD21450993C691F9C@MBX110.d.ethz.ch>

Casey

I had a look at the PCL plugin and couldn?t help notice that you?ve copied some of my particle partition filtering code into the plugin, though it does not look functional as it?s not enabled in the cmake and does not include the relevant Zoltan sources or the vtkZoltanV1PartitionFilter base class.

The partitioning (both particle and mesh) have been refactored (from the pv-meshles plugin) into their own self contained plugin for some time now and it would be cleaner in my view to have an option in the PCL plugin to enable parallel partitioning and use the pv-zoltan plugin as a submodule where necessary
https://github.com/biddisco/pv-zoltan

(I tend to use GitExternal and SubProject cmake modules rather than a git submodule, I can send links if you?re interested).

The pv-zoltan code is currently under development (and is working with pv-4.4/master) to improve it as part of a GSOC project and should soon be compatible with zoltan2 rather than Zoltan. I can make sure a pv-4.4+zoltan1 compatible branch remains functional should we make major changes.

I might even volunteer to do the clean integration of pv-zoltan with the pcl plugin should you be in need of volunteers.

JB


From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Casey Goodlett
Sent: 13 July 2015 21:16
To: Eric Younkin - NOAA Federal
Cc: paraview
Subject: Re: [Paraview] PCL Plugin



On Mon, Jul 13, 2015 at 1:32 PM, Eric Younkin - NOAA Federal <eric.g.younkin at noaa.gov<mailto:eric.g.younkin at noaa.gov>> wrote:
Casey,

I don't mean to take up so much of your time, but I've been reviewing the cmake configuration and I found that there were a number of HDF5 tests that failed (see below).  Is that significant?


I do not think this is a problem.


Also, one of the errors I saw upon rebuilding:



error C1041: cannot open program database 'c:\users\eric.g.younkin\documents\pcl_paraview\paraview-v4.3.1-source\build\plugins\sciberquesttoolkit\paraviewplugin\sciberquesttoolkit.dir\debug\vc120.pdb'; if multiple CL.EXE write to the same .PDB file, please use /FS C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\Plugins\SciberQuestToolKit\ParaViewPlugin\moc_pqSQFieldTracerImplementation.cpp)



Led me to the moc_pqSQFieldTracerImplementation.cpp which had a comment at the top stating



"This file was generated using the moc from 5.5.0. It cannot be used with the include files from this version of Qt. (The moc has changed too much.)"



So I will try with Qt5.4.1 instead.



I am not familiar with this problem.  Maybe the filename is getting too long for windows?  Maybe another developer can help with the Qt issues, I am not an expert in this area.

Regards,

--
Casey B Goodlett, PhD
Technical Leader
Kitware, Inc. - North Carolina Office
http://www.kitware.com
(919) 969-6990 x310<tel:%28919%29%20969-6990%20x310>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150714/50246907/attachment.html>

From lmorandini at ieee.org  Tue Jul 14 07:00:24 2015
From: lmorandini at ieee.org (Luca Morandini)
Date: Tue, 14 Jul 2015 21:00:24 +1000
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
Message-ID: <mo2q49$4gt$1@ger.gmane.org>

On 10/07/15 00:39, Casey Goodlett wrote:
> Hi Eric,
>
> Thanks for your interest in the PCL plugin, I have used the plugin more recently
> than PCL 1.5.1.  I last tested with ParaView 4.1 and PCL master (from around
> February of this year).

Apologies for the interruption, but I tried to build the PCL plugin following the 
instructions [1] against an old version of ParaView, and run into problems (see my 
other post today),  but then I noticed this thread and realized that I may try to 
build it against a more recent version of ParaView: will it work following the 
dame instructions, as provided by  or some extra care is needed?

Regards,

[1] http://www.paraview.org/Wiki/ParaView/PCL_Plugin/Download_And_Build_Instructions

Luca Morandini
Data Architect - AURIN project
Melbourne eResearch Group
Department of Computing and Information Systems
University of Melbourne
Tel. +61 03 903 58 380
Skype: lmorandini


From lingdeer at gmail.com  Tue Jul 14 13:25:26 2015
From: lingdeer at gmail.com (Elaine Tang)
Date: Tue, 14 Jul 2015 13:25:26 -0400
Subject: [Paraview] Computing displacement
Message-ID: <CAG+yLxmwg6W9mD9NcVYmuopZFqwMh3_cWcC=k_kfZcjGrf07=g@mail.gmail.com>

Hi,

I have a set of data with displacement point data. I want to create a new
variable that:

New_displacement (t) = displacement (t) - displacement (t=0)

Any idea on how to do that? I was trying to use calculator but I don't know
how can I specific displacement for t=0.

Also, is there any easy way in Paraview to find the maximum displacement
throughout all time steps?

Thank you!
-- 
Elaine Tang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150714/0c84701d/attachment.html>

From casey.goodlett at kitware.com  Tue Jul 14 13:32:16 2015
From: casey.goodlett at kitware.com (Casey Goodlett)
Date: Tue, 14 Jul 2015 13:32:16 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <50320452A334BD42A5EC72BAD21450993C691F9C@MBX110.d.ethz.ch>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <CAFe6qKgoBR7HU6MHCDTKr_HCxBGu_eU3St2D5+UjQ3zrBwqcbg@mail.gmail.com>
 <CAOqyOuG9-w-TFEXJO1+8EvtAQLK-JJE3Rr8XqVLG=JObe69sNg@mail.gmail.com>
 <CAFe6qKg-_LHR3tHZ10H78PZJcF2rAVV8bEOH_y_Bt0h+C9jMyw@mail.gmail.com>
 <CAFe6qKhUiTADyYM9OTyWZg5RtvctezOxnREXnL40BsR-Ny=EoA@mail.gmail.com>
 <CAOqyOuH60D5LXthUwvSUViCWLqvrTz1z5a9wu-aCX3c4g-GEgQ@mail.gmail.com>
 <CAFe6qKhT6PvOoQRdOyAriiLJbc4D-zVJ-TtLgsyitECHCrsz8w@mail.gmail.com>
 <CAOqyOuGCULt0Lm4GBzxSLifuv4OoVJ_G-k_rhYMpCG4XE1tPLQ@mail.gmail.com>
 <CAFe6qKhhgem8+jPVRyJoaQrY-WJgW3vne7xDFHP41w332FWQPA@mail.gmail.com>
 <CAOqyOuEdwX+2_+7_Q-qfmCHF=oXSgTmJ9U3kEhn8ut+Dc5BEQg@mail.gmail.com>
 <CAFe6qKhd060BfDzZV-dA6towMGjTA-hpTpn10XkvtvhviyMgXA@mail.gmail.com>
 <CAFe6qKjE1cE9uTgKrcci+jAm5uafyHim-3GT0sqSuthf1XYCUA@mail.gmail.com>
 <CAOqyOuF_QEFCMBBYgDJNCF8O1gR+77Wwq=g3HEHab-oQ7UJM6w@mail.gmail.com>
 <50320452A334BD42A5EC72BAD21450993C691F9C@MBX110.d.ethz.ch>
Message-ID: <CAOqyOuFgq7Zeg44ts=Md9cCFkDGLfVWytina02MUjzOoRJkxqA@mail.gmail.com>

Hi John,

I am trying to remember the history of why that code is there, and the
reason escapes me right now.

Pat Marion: Do you remember this?

I propose that we remove it from the plugin until a time that we can sync
with your latest work.

Does that sound reasonable?


On Tue, Jul 14, 2015 at 5:03 AM, Biddiscombe, John A. <biddisco at cscs.ch>
wrote:

>  Casey
>
>
>
> I had a look at the PCL plugin and couldn?t help notice that you?ve copied
> some of my particle partition filtering code into the plugin, though it
> does not look functional as it?s not enabled in the cmake and does not
> include the relevant Zoltan sources or the vtkZoltanV1PartitionFilter base
> class.
>
>
>
> The partitioning (both particle and mesh) have been refactored (from the
> pv-meshles plugin) into their own self contained plugin for some time now
> and it would be cleaner in my view to have an option in the PCL plugin to
> enable parallel partitioning and use the pv-zoltan plugin as a submodule
> where necessary
>
> https://github.com/biddisco/pv-zoltan
>
>
>
> (I tend to use GitExternal and SubProject cmake modules rather than a git
> submodule, I can send links if you?re interested).
>
>
>
> The pv-zoltan code is currently under development (and is working with
> pv-4.4/master) to improve it as part of a GSOC project and should soon be
> compatible with zoltan2 rather than Zoltan. I can make sure a
> pv-4.4+zoltan1 compatible branch remains functional should we make major
> changes.
>
>
>
> I might even volunteer to do the clean integration of pv-zoltan with the
> pcl plugin should you be in need of volunteers.
>
>
>
> JB
>
>
>
>
>
> *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *Casey
> Goodlett
> *Sent:* 13 July 2015 21:16
> *To:* Eric Younkin - NOAA Federal
> *Cc:* paraview
> *Subject:* Re: [Paraview] PCL Plugin
>
>
>
>
>
>
>
> On Mon, Jul 13, 2015 at 1:32 PM, Eric Younkin - NOAA Federal <
> eric.g.younkin at noaa.gov> wrote:
>
> Casey,
>
>
>
> I don't mean to take up so much of your time, but I've been reviewing the
> cmake configuration and I found that there were a number of HDF5 tests that
> failed (see below).  Is that significant?
>
>
>
>
>
> I do not think this is a problem.
>
>
>
>  Also, one of the errors I saw upon rebuilding:
>
>
>
> *error C1041: cannot open program database
> 'c:\users\eric.g.younkin\documents\pcl_paraview\paraview-v4.3.1-source\build\plugins\sciberquesttoolkit\paraviewplugin\sciberquesttoolkit.dir\debug\vc120.pdb';
> if multiple CL.EXE write to the same .PDB file, please use /FS
> C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\Plugins\SciberQuestToolKit\ParaViewPlugin\moc_pqSQFieldTracerImplementation.cpp)*
>
>
>
> Led me to the moc_pqSQFieldTracerImplementation.cpp which had a comment at
> the top stating
>
>
>
> *"This file was generated using the moc from 5.5.0. It cannot be used with
> the include files from this version of Qt. (The moc has changed too much.)"*
>
>
>
> So I will try with Qt5.4.1 instead.
>
>
>
>
>
> I am not familiar with this problem.  Maybe the filename is getting too
> long for windows?  Maybe another developer can help with the Qt issues, I
> am not an expert in this area.
>
>
>
> Regards,
>
>
>
> --
>
> Casey B Goodlett, PhD
> Technical Leader
> Kitware, Inc. - North Carolina Office
> http://www.kitware.com
> (919) 969-6990 x310
>



-- 
Casey B Goodlett, PhD
Technical Leader
Kitware, Inc. - North Carolina Office
http://www.kitware.com
(919) 969-6990 x310
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150714/92e2ccda/attachment.html>

From casey.goodlett at kitware.com  Tue Jul 14 13:39:05 2015
From: casey.goodlett at kitware.com (Casey Goodlett)
Date: Tue, 14 Jul 2015 13:39:05 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <mo2q49$4gt$1@ger.gmane.org>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <mo2q49$4gt$1@ger.gmane.org>
Message-ID: <CAOqyOuGT2uONXRjPd80bJOBdnhugTMyyUCHGn6s8H4Aw+i1wOg@mail.gmail.com>

Luca,

You should be able to use a more recent ParaView.  If you run across
problems with the build you can ask here.  It should work, but you may
encounter some problems.  I believe I tested as recently as paraview 4.2

On Tue, Jul 14, 2015 at 7:00 AM, Luca Morandini <lmorandini at ieee.org> wrote:

> On 10/07/15 00:39, Casey Goodlett wrote:
>
>> Hi Eric,
>>
>> Thanks for your interest in the PCL plugin, I have used the plugin more
>> recently
>> than PCL 1.5.1.  I last tested with ParaView 4.1 and PCL master (from
>> around
>> February of this year).
>>
>
> Apologies for the interruption, but I tried to build the PCL plugin
> following the instructions [1] against an old version of ParaView, and run
> into problems (see my other post today),  but then I noticed this thread
> and realized that I may try to build it against a more recent version of
> ParaView: will it work following the dame instructions, as provided by  or
> some extra care is needed?
>
> Regards,
>
> [1]
> http://www.paraview.org/Wiki/ParaView/PCL_Plugin/Download_And_Build_Instructions
>
> Luca Morandini
> Data Architect - AURIN project
> Melbourne eResearch Group
> Department of Computing and Information Systems
> University of Melbourne
> Tel. +61 03 903 58 380
> Skype: lmorandini
>
>
> _______________________________________________
> 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
>



-- 
Casey B Goodlett, PhD
Technical Leader
Kitware, Inc. - North Carolina Office
http://www.kitware.com
(919) 969-6990 x310
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150714/7c3de0c5/attachment.html>

From robert.maynard at kitware.com  Tue Jul 14 14:19:59 2015
From: robert.maynard at kitware.com (Robert Maynard)
Date: Tue, 14 Jul 2015 14:19:59 -0400
Subject: [Paraview] Compilation problem of ParaView 3.14.1 on Ubuntu
	14.04
In-Reply-To: <mo2g4i$4io$1@ger.gmane.org>
References: <mo2g4i$4io$1@ger.gmane.org>
Message-ID: <CAFzjYVpax_BsYW3M94FuV+08AaG-Nf3qEW5zdTmOKVYUVTUuFQ@mail.gmail.com>

Hi Luca,

Can you send your CMakeError.log from the build directory? This exact
failure is unexpected.

On Tue, Jul 14, 2015 at 4:09 AM, Luca Morandini <lmorandini at ieee.org> wrote:
> I'm trying to compile a rather old version of ParaView (3.14.1) from source,
> since I need it to compile, in turn, the PCL plugin.
>
> However, I was not able to build ParaView after successfully running ccmake
> to configure and generate the makefiles; in fact, when I try make, the
> result is:
>
> [  0%] Built target vtkWrapHierarchy
> [  0%] Built target vtkWrapPython
> [  0%] Built target vtkWrapPythonInit
> Scanning dependencies of target vtksys
> [  0%] Building CXX object
> VTK/Utilities/kwsys/CMakeFiles/vtksys.dir/Directory.cxx.o
> In file included from
> /opt/ParaView-3.14.1-Source/Build/VTK/Utilities/vtksys/stl/string.hxx:29:0,
>                  from
> /opt/ParaView-3.14.1-Source/Build/VTK/Utilities/vtksys/stl/string:49,
>                  from
> /opt/ParaView-3.14.1-Source/VTK/Utilities/kwsys/Directory.cxx:17:
> /opt/ParaView-3.14.1-Source/Build/VTK/Utilities/vtksys/ios/iostream:26:23:
> fatal error: iostream.h: No such file or directory
>  # include <iostream.h>
>                        ^
> compilation terminated.
> make[2]: *** [VTK/Utilities/kwsys/CMakeFiles/vtksys.dir/Directory.cxx.o]
> Error 1
> make[1]: *** [VTK/Utilities/kwsys/CMakeFiles/vtksys.dir/all] Error 2
> make: *** [all] Error 2
>
>
> I tried to fiddle around with the CCMKake flags, but, despite my efforts,
> only a few modules compiled, hence I concluded there is something deeper
> that I am missing: could someone shed some light?
>
> Luca Morandini
> Data Architect - AURIN project
> Melbourne eResearch Group
> Department of Computing and Information Systems
> University of Melbourne
> Tel. +61 03 903 58 380
> Skype: lmorandini
>
> _______________________________________________
> 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

From andrew.robertson at orbitalatk.com  Tue Jul 14 14:14:21 2015
From: andrew.robertson at orbitalatk.com (Robertson, Andrew)
Date: Tue, 14 Jul 2015 18:14:21 +0000
Subject: [Paraview] Mass weighted, mass flow weighted averages.
Message-ID: <68AC123ECB4AC54DB8876E4D6A3EED966E2DBA44@mn05svcwem002.atk.com>

Folks,
Any add-ons for doing mass weighted and mass flow weighted averages.
Just getting started with paraview, I think I see the path to do this. But am not proud and am sufficiently lazy to use the works of others ;-)
Thanks
-Andy


Andrew Robertson P.E.
CFD Analyst

GASL Operations
Tactical Propulsion and Controls
ATK
77 Raynor Avenue
Ronkokoma NY 11779

Phone:  631-676-8955<tel:631-737-6100%20Ext%20190>  <- NOTE NEW Number
Fax:  631-588-7023<tel:631-588-7023>
www.atk.com<http://www.atk.com/>

 !! Knowledge and Thoroughness Baby !!
       Happiness is conserving mass



------------------------------------------------------------------------------

Notice: This e-mail is intended solely for use of the individual or entity to which it is addressed and may contain information that is proprietary, privileged and exempt from disclosure under applicable law. If the reader is not the intended recipient or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. This communication may also contain data subject to U.S. export laws. If so, that data subject to the International Traffic in Arms Regulation cannot be disseminated, distributed or copied to foreign nationals, residing in the U.S. or abroad, absent the express prior approval of the U.S. Department of State. If you have received this communication in error, please notify the sender by reply e-mail and destroy the e-mail message and any physical copies made of the communication. Thank you. 
********** **********
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150714/61d867fd/attachment.html>

From andy.bauer at kitware.com  Tue Jul 14 14:31:56 2015
From: andy.bauer at kitware.com (Andy Bauer)
Date: Tue, 14 Jul 2015 14:31:56 -0400
Subject: [Paraview] Mass weighted, mass flow weighted averages.
In-Reply-To: <68AC123ECB4AC54DB8876E4D6A3EED966E2DBA44@mn05svcwem002.atk.com>
References: <68AC123ECB4AC54DB8876E4D6A3EED966E2DBA44@mn05svcwem002.atk.com>
Message-ID: <CAMaOp+EgfqgbcDctnJmRNyczTxEvDZJWTacinT-6txyQ0KgAvg@mail.gmail.com>

I think the best way would be to use the Calculator filter to compute your
derived quantities (e.g. whatever field you want mass weighted divided by
density) and then use the Integrate Variables filter to get the integrated
values of the quantities. I'd need to see some equations before giving you
a more precise set of instructions.

By the way, the ParaView User's Guide (
http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.3&type=data&os=all&downloadFile=TheParaViewGuide-v4.3-CC-Edition.pdf)
is a good place to start getting familiar with ParaView. A printed edition
is available but will have to be purchased at
http://www.kitware.com/products/books.php. It has a couple more chapters
that can be helpful to some users.

Regards,
Andy


On Tue, Jul 14, 2015 at 2:14 PM, Robertson, Andrew <
andrew.robertson at orbitalatk.com> wrote:

>  Folks,
>
> Any add-ons for doing mass weighted and mass flow weighted averages.
>
> Just getting started with paraview, I think I see the path to do this. But
> am not proud and am sufficiently lazy to use the works of others ;-)
>
> Thanks
>
> -Andy
>
>
>
>
>
> Andrew Robertson P.E.
>
> CFD Analyst
>
>
>
> GASL Operations
>
> Tactical Propulsion and Controls
>
> ATK
>
> 77 Raynor Avenue
>
> Ronkokoma NY 11779
>
>
>
> Phone:  631-676-8955 <631-737-6100%20Ext%20190>  <- *NOTE NEW Number*
>
> Fax:  631-588-7023
>
> www.atk.com
>
>
>
>  !! Knowledge and Thoroughness Baby !!
>
>        Happiness is conserving mass
>
>
>
> ------------------------------
> Notice: This e-mail is intended solely for use of the individual or entity
> to which it is addressed and may contain information that is proprietary,
> privileged and exempt from disclosure under applicable law. If the reader
> is not the intended recipient or agent responsible for delivering the
> message to the intended recipient, you are hereby notified that any
> dissemination, distribution or copying of this communication is strictly
> prohibited. This communication may also contain data subject to U.S. export
> laws. If so, that data subject to the International Traffic in Arms
> Regulation cannot be disseminated, distributed or copied to foreign
> nationals, residing in the U.S. or abroad, absent the express prior
> approval of the U.S. Department of State. If you have received this
> communication in error, please notify the sender by reply e-mail and
> destroy the e-mail message and any physical copies made of the
> communication. Thank you.
> ********** **********
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150714/5d6effbf/attachment.html>

From andrew.robertson at orbitalatk.com  Tue Jul 14 14:33:37 2015
From: andrew.robertson at orbitalatk.com (Robertson, Andrew)
Date: Tue, 14 Jul 2015 18:33:37 +0000
Subject: [Paraview] Mass weighted, mass flow weighted averages.
In-Reply-To: <CAMaOp+EgfqgbcDctnJmRNyczTxEvDZJWTacinT-6txyQ0KgAvg@mail.gmail.com>
References: <68AC123ECB4AC54DB8876E4D6A3EED966E2DBA44@mn05svcwem002.atk.com>
 <CAMaOp+EgfqgbcDctnJmRNyczTxEvDZJWTacinT-6txyQ0KgAvg@mail.gmail.com>
Message-ID: <68AC123ECB4AC54DB8876E4D6A3EED966E2DBABF@mn05svcwem002.atk.com>

Thanks,
I have worked with the calculator filter and figured out how to use the integraton filter.  Just figured that in the CFD world this is a pretty standard thing to do, and might already exist.
Thanks again
-ANdy

From: Andy Bauer [mailto:andy.bauer at kitware.com]
Sent: Tuesday, July 14, 2015 2:32 PM
To: Robertson, Andrew
Cc: paraview at paraview.org
Subject: Re: [Paraview] Mass weighted, mass flow weighted averages.

I think the best way would be to use the Calculator filter to compute your derived quantities (e.g. whatever field you want mass weighted divided by density) and then use the Integrate Variables filter to get the integrated values of the quantities. I'd need to see some equations before giving you a more precise set of instructions.
By the way, the ParaView User's Guide (http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.3&type=data&os=all&downloadFile=TheParaViewGuide-v4.3-CC-Edition.pdf) is a good place to start getting familiar with ParaView. A printed edition is available but will have to be purchased at http://www.kitware.com/products/books.php. It has a couple more chapters that can be helpful to some users.
Regards,
Andy


On Tue, Jul 14, 2015 at 2:14 PM, Robertson, Andrew <andrew.robertson at orbitalatk.com<mailto:andrew.robertson at orbitalatk.com>> wrote:
Folks,
Any add-ons for doing mass weighted and mass flow weighted averages.
Just getting started with paraview, I think I see the path to do this. But am not proud and am sufficiently lazy to use the works of others ;-)
Thanks
-Andy


Andrew Robertson P.E.
CFD Analyst

GASL Operations
Tactical Propulsion and Controls
ATK
77 Raynor Avenue
Ronkokoma NY 11779

Phone:  631-676-8955<tel:631-737-6100%20Ext%20190>  <- NOTE NEW Number
Fax:  631-588-7023<tel:631-588-7023>
www.atk.com<http://www.atk.com/>

 !! Knowledge and Thoroughness Baby !!
       Happiness is conserving mass


________________________________
Notice: This e-mail is intended solely for use of the individual or entity to which it is addressed and may contain information that is proprietary, privileged and exempt from disclosure under applicable law. If the reader is not the intended recipient or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. This communication may also contain data subject to U.S. export laws. If so, that data subject to the International Traffic in Arms Regulation cannot be disseminated, distributed or copied to foreign nationals, residing in the U.S. or abroad, absent the express prior approval of the U.S. Department of State. If you have received this communication in error, please notify the sender by reply e-mail and destroy the e-mail message and any physical copies made of the communication. Thank you.
********** **********

_______________________________________________
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

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

From andy.bauer at kitware.com  Tue Jul 14 14:45:49 2015
From: andy.bauer at kitware.com (Andy Bauer)
Date: Tue, 14 Jul 2015 14:45:49 -0400
Subject: [Paraview] Mass weighted, mass flow weighted averages.
In-Reply-To: <68AC123ECB4AC54DB8876E4D6A3EED966E2DBABF@mn05svcwem002.atk.com>
References: <68AC123ECB4AC54DB8876E4D6A3EED966E2DBA44@mn05svcwem002.atk.com>
 <CAMaOp+EgfqgbcDctnJmRNyczTxEvDZJWTacinT-6txyQ0KgAvg@mail.gmail.com>
 <68AC123ECB4AC54DB8876E4D6A3EED966E2DBABF@mn05svcwem002.atk.com>
Message-ID: <CAMaOp+Ha+dL7Z_oy5+8ntwfh_9Oxn2_NF2zais6q4GaqY5wtBA@mail.gmail.com>

ParaView was designed as a general viz & analysis tool so it doesn't have a
lot of built-in short cuts for doing complex operations that are tailored
to specific analysis domains (e.g. CFD). This works well when you want to
do something slightly off from "standard" because you can control each step
of a multi-step process. If you have repetitive tasks that you're doing
ParaView has ways to automate them (state files, Python scripts, macros) to
save you time. If you really want to speed up those tasks and make it very
streamlined to your analysis domain, ParaView can be customized for that as
well. It's just a matter of effort for how streamlined you want ParaView to
be for your workflow.

Best,
Andy



On Tue, Jul 14, 2015 at 2:33 PM, Robertson, Andrew <
andrew.robertson at orbitalatk.com> wrote:

>  Thanks,
>
> I have worked with the calculator filter and figured out how to use the
> integraton filter.  Just figured that in the CFD world this is a pretty
> standard thing to do, and might already exist.
>
> Thanks again
>
> -ANdy
>
>
>
> *From:* Andy Bauer [mailto:andy.bauer at kitware.com]
> *Sent:* Tuesday, July 14, 2015 2:32 PM
> *To:* Robertson, Andrew
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] Mass weighted, mass flow weighted averages.
>
>
>
> I think the best way would be to use the Calculator filter to compute your
> derived quantities (e.g. whatever field you want mass weighted divided by
> density) and then use the Integrate Variables filter to get the integrated
> values of the quantities. I'd need to see some equations before giving you
> a more precise set of instructions.
>
> By the way, the ParaView User's Guide (
> http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.3&type=data&os=all&downloadFile=TheParaViewGuide-v4.3-CC-Edition.pdf)
> is a good place to start getting familiar with ParaView. A printed edition
> is available but will have to be purchased at
> http://www.kitware.com/products/books.php. It has a couple more chapters
> that can be helpful to some users.
>
> Regards,
>
> Andy
>
>
>
>
>
> On Tue, Jul 14, 2015 at 2:14 PM, Robertson, Andrew <
> andrew.robertson at orbitalatk.com> wrote:
>
> Folks,
>
> Any add-ons for doing mass weighted and mass flow weighted averages.
>
> Just getting started with paraview, I think I see the path to do this. But
> am not proud and am sufficiently lazy to use the works of others ;-)
>
> Thanks
>
> -Andy
>
>
>
>
>
> Andrew Robertson P.E.
>
> CFD Analyst
>
>
>
> GASL Operations
>
> Tactical Propulsion and Controls
>
> ATK
>
> 77 Raynor Avenue
>
> Ronkokoma NY 11779
>
>
>
> Phone:  631-676-8955 <631-737-6100%20Ext%20190>  <- *NOTE NEW Number*
>
> Fax:  631-588-7023
>
> www.atk.com
>
>
>
>  !! Knowledge and Thoroughness Baby !!
>
>        Happiness is conserving mass
>
>
>
>
>  ------------------------------
>
> Notice: This e-mail is intended solely for use of the individual or entity
> to which it is addressed and may contain information that is proprietary,
> privileged and exempt from disclosure under applicable law. If the reader
> is not the intended recipient or agent responsible for delivering the
> message to the intended recipient, you are hereby notified that any
> dissemination, distribution or copying of this communication is strictly
> prohibited. This communication may also contain data subject to U.S. export
> laws. If so, that data subject to the International Traffic in Arms
> Regulation cannot be disseminated, distributed or copied to foreign
> nationals, residing in the U.S. or abroad, absent the express prior
> approval of the U.S. Department of State. If you have received this
> communication in error, please notify the sender by reply e-mail and
> destroy the e-mail message and any physical copies made of the
> communication. Thank you.
> ********** **********
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150714/827971c8/attachment.html>

From jeffrey.c.becker at nasa.gov  Tue Jul 14 14:59:56 2015
From: jeffrey.c.becker at nasa.gov (Jeff Becker)
Date: Tue, 14 Jul 2015 11:59:56 -0700
Subject: [Paraview] Combining vtk and paraview python scripts
Message-ID: <55A55C2C.2030107@nasa.gov>

Hi.

As a proof of concept, I have a vtk script that reads some binary data, 
and produces a vti file. I then have a second script that I generated 
using ParaView's tracing facility while viewing the data. Now I'd like 
to combine them, so as to eliminate the intermediate file, i.e., go from 
binary data directly to rendering. To be specific, my vtk script ends 
like this:

steinbmag = steinbmag.reshape(nx,ny,nz).T

vtkImporter = vtk.vtkImageImport()
vtkImporter.CopyImportVoidPointer(steinbmag, steinbmag.nbytes)

vtkImporter.SetDataScalarTypeToFloat()
vtkImporter.SetNumberOfScalarComponents(1)
vtkImporter.SetDataExtent(0, nx-1, 0, ny-1, 0, nz-1)
vtkImporter.SetWholeExtent(0, nx-1, 0, ny-1, 0, nz-1)
vtkImporter.SetScalarArrayName('B field magnitude')

writer=vtk.vtkXMLImageDataWriter()
writer.SetFileName(out_fname)
writer.SetInputConnection(vtkImporter.GetOutputPort())
writer.Write()

and the ParaView script starts like this:

from paraview.simple import *

paraview.simple._DisableFirstRenderCameraReset()

filepfx = '/nobackup/jcbecker/steinBmag_0'
infile = filepfx+'.vti'
# create a new 'XML Image Data Reader'
steinBmag_ = XMLImageDataReader(FileName=infile)
steinBmag_.CellArrayStatus = []
steinBmag_.PointArrayStatus = ['B field magnitude']

# get animation scene
animationScene1 = GetAnimationScene()

# update animation scene based on data timesteps
animationScene1.UpdateAnimationUsingDataTimeSteps()

# get active view
renderView1 = GetActiveViewOrCreate('RenderView')
# uncomment following to set a specific view size
renderView1.ViewSize = [1090, 761]

I'm looking at the VTK examples and pvpython documentation, but any help 
is appreciated.

Thanks.

-jeff

From andy.bauer at kitware.com  Tue Jul 14 15:20:08 2015
From: andy.bauer at kitware.com (Andy Bauer)
Date: Tue, 14 Jul 2015 15:20:08 -0400
Subject: [Paraview] Combining vtk and paraview python scripts
In-Reply-To: <55A55C2C.2030107@nasa.gov>
References: <55A55C2C.2030107@nasa.gov>
Message-ID: <CAMaOp+GaBL5wqsU4YiQ5-VpZWqzDjPF8=oc6p950Oums+01+Zg@mail.gmail.com>

ParaView's Python Programmable Filter and Python Programmable Source use
VTK Python wrapping to do the work while making it available in Paraview.
Check out http://www.paraview.org/Wiki/Python_Programmable_Filter.

On Tue, Jul 14, 2015 at 2:59 PM, Jeff Becker <jeffrey.c.becker at nasa.gov>
wrote:

> Hi.
>
> As a proof of concept, I have a vtk script that reads some binary data,
> and produces a vti file. I then have a second script that I generated using
> ParaView's tracing facility while viewing the data. Now I'd like to combine
> them, so as to eliminate the intermediate file, i.e., go from binary data
> directly to rendering. To be specific, my vtk script ends like this:
>
> steinbmag = steinbmag.reshape(nx,ny,nz).T
>
> vtkImporter = vtk.vtkImageImport()
> vtkImporter.CopyImportVoidPointer(steinbmag, steinbmag.nbytes)
>
> vtkImporter.SetDataScalarTypeToFloat()
> vtkImporter.SetNumberOfScalarComponents(1)
> vtkImporter.SetDataExtent(0, nx-1, 0, ny-1, 0, nz-1)
> vtkImporter.SetWholeExtent(0, nx-1, 0, ny-1, 0, nz-1)
> vtkImporter.SetScalarArrayName('B field magnitude')
>
> writer=vtk.vtkXMLImageDataWriter()
> writer.SetFileName(out_fname)
> writer.SetInputConnection(vtkImporter.GetOutputPort())
> writer.Write()
>
> and the ParaView script starts like this:
>
> from paraview.simple import *
>
> paraview.simple._DisableFirstRenderCameraReset()
>
> filepfx = '/nobackup/jcbecker/steinBmag_0'
> infile = filepfx+'.vti'
> # create a new 'XML Image Data Reader'
> steinBmag_ = XMLImageDataReader(FileName=infile)
> steinBmag_.CellArrayStatus = []
> steinBmag_.PointArrayStatus = ['B field magnitude']
>
> # get animation scene
> animationScene1 = GetAnimationScene()
>
> # update animation scene based on data timesteps
> animationScene1.UpdateAnimationUsingDataTimeSteps()
>
> # get active view
> renderView1 = GetActiveViewOrCreate('RenderView')
> # uncomment following to set a specific view size
> renderView1.ViewSize = [1090, 761]
>
> I'm looking at the VTK examples and pvpython documentation, but any help
> is appreciated.
>
> Thanks.
>
> -jeff
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150714/e3cb86d4/attachment.html>

From krishnapai09 at gmail.com  Tue Jul 14 15:26:28 2015
From: krishnapai09 at gmail.com (Krishna Pai)
Date: Tue, 14 Jul 2015 15:26:28 -0400
Subject: [Paraview] How to get pvdataserver/pvrenderserver connected to my
 client using primarily the ParaView GUI?
Message-ID: <CAPHwKk77=h43eS1YfBsGRwUPSWEw2SzxUEnTjYhCESFZd+GWvQ@mail.gmail.com>

Hi all,

I've been trying to run pvdataserver and pvrenderserver on a computer on my
network through a reverse connection back to the client running on my local
machine by establishing an ssh tunnel through the GUI (command startup).

Server name="othermachine2" configuration="" resource="cdsrsrc://
127.0.0.1//127.0.0.1">
    <CommandStartup>
      <Command exec="ssh" delay="0">
        <Arguments>
          <Argument value="-R"/>
          <Argument value="11111:127.0.0.1:11111"/>
          <Argument value="-l"/>
          <Argument value="pai"/>
          <Argument value="othermachine"/>
          <Argument value="/home/pai/pvds.sh"/>
        </Arguments>
      </Command>
      <Command exec="ssh" delay="0">
        <Arguments>
           <Argument value="-R"/>
           <Argument value="22221:127.0.0.1:22221"/>
           <Argument value="-l"/>
           <Argument value="pai"/>
           <Argument value="othermachine"/>
           <Argument value="/home/pai/pvrs.sh"/>
        </Arguments>
      </Command>
    </CommandStartup>
  </Server>

pvdataserver ends up running and connecting to my client. But then the
second command block doesn't appear to run to set up the render server,
maybe because of whatever is making the terminal stop being interactive
after it prints the "client connected" message. I want to be able to create
a second tunnel to run pvrenderserver from a different port, but the above
doesn't work. Suggestions?

Thanks,
Krishna Pai
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150714/d6141db2/attachment.html>

From jeffrey.c.becker at nasa.gov  Tue Jul 14 15:43:46 2015
From: jeffrey.c.becker at nasa.gov (Jeff Becker)
Date: Tue, 14 Jul 2015 12:43:46 -0700
Subject: [Paraview] Combining vtk and paraview python scripts
In-Reply-To: <CAMaOp+GaBL5wqsU4YiQ5-VpZWqzDjPF8=oc6p950Oums+01+Zg@mail.gmail.com>
References: <55A55C2C.2030107@nasa.gov>
 <CAMaOp+GaBL5wqsU4YiQ5-VpZWqzDjPF8=oc6p950Oums+01+Zg@mail.gmail.com>
Message-ID: <55A56672.3040204@nasa.gov>

On 07/14/2015 12:20 PM, Andy Bauer wrote:
> ParaView's Python Programmable Filter and Python Programmable Source 
> use VTK Python wrapping to do the work while making it available in 
> Paraview. Check out 
> http://www.paraview.org/Wiki/Python_Programmable_Filter.

Thanks. That's pretty neat, but what I'd really like is a standalone 
script I can run in batch mode (no interaction) to generate one png file 
per timestep for all the timesteps in the data set. Essentially I'd like 
a way to construct a pipeline between the vtk.vtkImageImport()  object 
and the ParaView renderView1.

-jeff
>
> On Tue, Jul 14, 2015 at 2:59 PM, Jeff Becker 
> <jeffrey.c.becker at nasa.gov <mailto:jeffrey.c.becker at nasa.gov>> wrote:
>
>     Hi.
>
>     As a proof of concept, I have a vtk script that reads some binary
>     data, and produces a vti file. I then have a second script that I
>     generated using ParaView's tracing facility while viewing the
>     data. Now I'd like to combine them, so as to eliminate the
>     intermediate file, i.e., go from binary data directly to
>     rendering. To be specific, my vtk script ends like this:
>
>     steinbmag = steinbmag.reshape(nx,ny,nz).T
>
>     vtkImporter = vtk.vtkImageImport()
>     vtkImporter.CopyImportVoidPointer(steinbmag, steinbmag.nbytes)
>
>     vtkImporter.SetDataScalarTypeToFloat()
>     vtkImporter.SetNumberOfScalarComponents(1)
>     vtkImporter.SetDataExtent(0, nx-1, 0, ny-1, 0, nz-1)
>     vtkImporter.SetWholeExtent(0, nx-1, 0, ny-1, 0, nz-1)
>     vtkImporter.SetScalarArrayName('B field magnitude')
>
>     writer=vtk.vtkXMLImageDataWriter()
>     writer.SetFileName(out_fname)
>     writer.SetInputConnection(vtkImporter.GetOutputPort())
>     writer.Write()
>
>     and the ParaView script starts like this:
>
>     from paraview.simple import *
>
>     paraview.simple._DisableFirstRenderCameraReset()
>
>     filepfx = '/nobackup/jcbecker/steinBmag_0'
>     infile = filepfx+'.vti'
>     # create a new 'XML Image Data Reader'
>     steinBmag_ = XMLImageDataReader(FileName=infile)
>     steinBmag_.CellArrayStatus = []
>     steinBmag_.PointArrayStatus = ['B field magnitude']
>
>     # get animation scene
>     animationScene1 = GetAnimationScene()
>
>     # update animation scene based on data timesteps
>     animationScene1.UpdateAnimationUsingDataTimeSteps()
>
>     # get active view
>     renderView1 = GetActiveViewOrCreate('RenderView')
>     # uncomment following to set a specific view size
>     renderView1.ViewSize = [1090, 761]
>
>     I'm looking at the VTK examples and pvpython documentation, but
>     any help is appreciated.
>
>     Thanks.
>
>     -jeff
>     _______________________________________________
>     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
>
>

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

From andy.bauer at kitware.com  Tue Jul 14 15:53:30 2015
From: andy.bauer at kitware.com (Andy Bauer)
Date: Tue, 14 Jul 2015 15:53:30 -0400
Subject: [Paraview] Combining vtk and paraview python scripts
In-Reply-To: <55A56672.3040204@nasa.gov>
References: <55A55C2C.2030107@nasa.gov>
 <CAMaOp+GaBL5wqsU4YiQ5-VpZWqzDjPF8=oc6p950Oums+01+Zg@mail.gmail.com>
 <55A56672.3040204@nasa.gov>
Message-ID: <CAMaOp+EXhjihx10vBRx-GN_pPKD4ZxGE=1G=YjYku3irAL8Qng@mail.gmail.com>

All of that functionality is available through pvpython, or pvbatch in
parallel. I'd suggest you look into using the GUI's Python trace
functionality to help you make that script. pvpython can also be used as an
interactive Python shell if you want.

On Tue, Jul 14, 2015 at 3:43 PM, Jeff Becker <jeffrey.c.becker at nasa.gov>
wrote:

>  On 07/14/2015 12:20 PM, Andy Bauer wrote:
>
> ParaView's Python Programmable Filter and Python Programmable Source use
> VTK Python wrapping to do the work while making it available in Paraview.
> Check out http://www.paraview.org/Wiki/Python_Programmable_Filter.
>
>
> Thanks. That's pretty neat, but what I'd really like is a standalone
> script I can run in batch mode (no interaction) to generate one png file
> per timestep for all the timesteps in the data set. Essentially I'd like a
> way to construct a pipeline between the vtk.vtkImageImport()  object and
> the ParaView renderView1.
>
> -jeff
>
>
> On Tue, Jul 14, 2015 at 2:59 PM, Jeff Becker <jeffrey.c.becker at nasa.gov>
> wrote:
>
>> Hi.
>>
>> As a proof of concept, I have a vtk script that reads some binary data,
>> and produces a vti file. I then have a second script that I generated using
>> ParaView's tracing facility while viewing the data. Now I'd like to combine
>> them, so as to eliminate the intermediate file, i.e., go from binary data
>> directly to rendering. To be specific, my vtk script ends like this:
>>
>> steinbmag = steinbmag.reshape(nx,ny,nz).T
>>
>> vtkImporter = vtk.vtkImageImport()
>> vtkImporter.CopyImportVoidPointer(steinbmag, steinbmag.nbytes)
>>
>> vtkImporter.SetDataScalarTypeToFloat()
>> vtkImporter.SetNumberOfScalarComponents(1)
>> vtkImporter.SetDataExtent(0, nx-1, 0, ny-1, 0, nz-1)
>> vtkImporter.SetWholeExtent(0, nx-1, 0, ny-1, 0, nz-1)
>> vtkImporter.SetScalarArrayName('B field magnitude')
>>
>> writer=vtk.vtkXMLImageDataWriter()
>> writer.SetFileName(out_fname)
>> writer.SetInputConnection(vtkImporter.GetOutputPort())
>> writer.Write()
>>
>> and the ParaView script starts like this:
>>
>> from paraview.simple import *
>>
>> paraview.simple._DisableFirstRenderCameraReset()
>>
>> filepfx = '/nobackup/jcbecker/steinBmag_0'
>> infile = filepfx+'.vti'
>> # create a new 'XML Image Data Reader'
>> steinBmag_ = XMLImageDataReader(FileName=infile)
>> steinBmag_.CellArrayStatus = []
>> steinBmag_.PointArrayStatus = ['B field magnitude']
>>
>> # get animation scene
>> animationScene1 = GetAnimationScene()
>>
>> # update animation scene based on data timesteps
>> animationScene1.UpdateAnimationUsingDataTimeSteps()
>>
>> # get active view
>> renderView1 = GetActiveViewOrCreate('RenderView')
>> # uncomment following to set a specific view size
>> renderView1.ViewSize = [1090, 761]
>>
>> I'm looking at the VTK examples and pvpython documentation, but any help
>> is appreciated.
>>
>> Thanks.
>>
>> -jeff
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150714/589ca7c6/attachment.html>

From patrick.oleary at kitware.com  Tue Jul 14 16:28:12 2015
From: patrick.oleary at kitware.com (Patrick O'Leary)
Date: Tue, 14 Jul 2015 14:28:12 -0600
Subject: [Paraview] Extended Deadline: ISAV: In Situ Infrastructures for
 Enabling Extreme-Scale Analysis and Visualization an SC15 Workshop
Message-ID: <CAM8hOwbAfj3P+XmoVK8k-n2RQYN=wcQh7TEQ0vAMOdHYG7DnTg@mail.gmail.com>

Extended Deadline (Paper submission deadline: 16 August 2015; other
deadlines: see below)

ISAV: In Situ Infrastructures for Enabling Extreme-Scale Analysis and
Visualization
an SC15 Workshop
Monday afternoon 16 November 2015, Austin, TX, USA

Event web page: http://vis.lbl.gov/Events/ISAV-2015/

== Scope ==
This workshop brings together researchers, developers and practitioners
from industry, academia, and government laboratories who use in situ
methods in extreme-scale, high performance computing. The goal is to
present existing in-situ infrastructures, reference examples in a range of
science and engineering applications, to discuss topics like opportunities
presented by new architectures; existing infrastructure needs,
requirements, and gaps; and experiences to foster and enable in situ
analysis and visualization.

The considerable interest in the HPC community regarding in situ analysis
and visualization is due to several factors. First is an I/O cost savings,
where data is analyzed/visualized while being generated, without first
storing to a filesystem. Second is the potential for increased accuracy,
where fine temporal sampling of transient analysis might expose some
complex behavior missed in coarse temporal sampling. Third is the ability
to use all available resources, CPU?s and accelerators, in the computation
of analysis products.

In Situ processing is still a relatively new idea, and up until recently,
most implementations have been ad hoc, proof-of-concept prototypes.
However, several in situ infrastructure implementations have emerged.
ParaView and VisIt both provide tools for in situ analysis and
visualization. ParaView Catalyst can be  linked to a simulation, allowing
the simulation to share data with Catalyst for visualization. Similar
capabilities are available within VisIt with the libsim library. Both
Catalyst (through Live) and libsim enable the opposite flow of information,
sending data from the client to the simulation, enabling the possibility of
simulation steering. ADIOS and GLEAN allow simulations to adopt in situ
techniques by leveraging their advanced I/O infrastructures that enable
co-analysis pipelines rather than changing the simulator. The non-intrusive
integration provide resilience to third party library bugs and possible
jitter in the simulation.
Participation/Call for Papers
We invite short (4-page) papers that identify opportunities, challenges and
case studies/best practices for in situ analysis and visualization. These
papers could propose actions, or provide position, or experience reports on
in situ analysis and visualization.

Areas of interest for ISAV, include, but are not limited to:
* In situ infrastructures
 - Current Systems: production quality, research prototypes
 - Opportunities
 - Gaps
* System resources, hardware, and emerging architectures
 - Enabling Hardware
 - Hardware and architectures that provide opportunities for In situ
processing, such as burst buffers, staging computations on I/O nodes,
sharing cores within a node for both simulation and in situ processing

* Examples/Case studies
 - Best practices
 - Analysis: feature detection, statistical methods, temporal methods,
geometric methods
 - Visualization: information visualization, scientific visualization,
time-varying methods
 - Data reduction/compression

* Simulation
 - Integration:data modeling, software-engineering
 - Resilience: error detection, fault recovery
 - Workflows for supporting complex in situ processing pipelines

* Requirements
 - Preserve important elements
 - Significantly reduce the data size
 - Flexibility for post-processing exploration

== Submitting Papers ==
Submissions are limited to 4 pages in the ACM format (see
http://www.acm.org/sigs/publications/proceedings-templates). The 4-page
limit includes figures, tables, and appendices, but does not include
references, for which you may use up to one additional page.
Please submit your paper via the ISAV 2015 EasyChair submission page at
https://easychair.org/conferences/?conf=isav2015.

== Timelines/Important Dates: ==
16 August 2015 (was 1 August 2015)        Paper submission deadline
16 September 2015 (was 1 September 2015)  Author notification
30 September 2015 (was 15 September 2015) Camera ready copy due
mid-October 2015                          Final program posted to ISAV web
page
16 November 2015                          ISAV workshop

== Organizers/Program Committee ==

Organizers
 E. Wes Bethel, ewbethel at lbl.gov, Lawrence Berkeley National Laboratory, USA
 Venkatram Vishwanath, venkat at anl.gov, Argonne National Laboratory, USA
 Gunther H. Weber, ghweber at lbl.gov, Lawrence Berkeley National Laboratory,
USA
 Matthew Wolf, mwolf at cc.gatech.edu, Georgia Institute of Technology, USA

Program Committee
 Utkarsh Ayachit, Kitware Inc., USA
 Earl P.N. Duque,  Intelligent Light, USA
 Nicola Ferrier, Argonne National Laboratory, USA
 Burlen Loring, Lawrence Berkeley National Laboratory, USA
 Dmitriy Morozov, Lawrence Berkeley National Laboratory, USA
 Patrick O?Leary, Kitware Inc., USA
 Manish Parashar, Rutgers, USA
 Karsten Schwan, Georgia Institute of Technology, USA
 Alex Sim, Lawrence Berkeley National Laboratory, USA
 Brad Whitlock, Intelligent Light, USA
 Kesheng (John) Wu, Lawrence Berkeley National Laboratory, USA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150714/7ffe1d23/attachment.html>

From sevensam at udel.edu  Tue Jul 14 17:36:16 2015
From: sevensam at udel.edu (Jesse Samluk)
Date: Tue, 14 Jul 2015 17:36:16 -0400
Subject: [Paraview] Custom animation help? (Corrected image)
In-Reply-To: <CADwGrVpXTnqgaD_DciowFwe2pc6KC6r332jLwKBnAESWBjkYKQ@mail.gmail.com>
References: <A9BF9A24-AFD8-41DD-8F0C-446AD9B8702C@udel.edu>
 <CAB5Fpx7yjsZEwk5MtCMVuJ5cVtga=zpfF9rK4S42snNkamAO=A@mail.gmail.com>
 <CADwGrVpXTnqgaD_DciowFwe2pc6KC6r332jLwKBnAESWBjkYKQ@mail.gmail.com>
Message-ID: <D1509E00-6BFE-42F1-8602-ED230B0C5532@udel.edu>

Dan and Cory,

Thanks for the guides. I?m getting a lot better at animations now! Awesome! The guides helped a lot.

  1 more quick question for you.

 I know how to save state files, but is there such a way to save the animation ?state? that I just created in a state file, such that, if I use that state file, the animation scheme will reappear to other data files I?ve created?

   Wasn?t too sure on this.

 Thanks!
  Jesse
  
> On Jul 10, 2015, at 5:34 PM, Dan Lipsa <dan.lipsa at kitware.com> wrote:
> 
> Jesse,
> See also the following thread:
> 
> http://markmail.org/search/?q=+programmimg+the+camera+position+using+python#query:%20programmimg%20the%20camera%20position%20using%20python+page:1+mid:nkm5rmw2hz52egnk+state:results <http://markmail.org/search/?q=+programmimg+the+camera+position+using+python#query:%20programmimg%20the%20camera%20position%20using%20python+page:1+mid:nkm5rmw2hz52egnk+state:results>
> 
> On Fri, Jul 10, 2015 at 5:19 PM Cory Quammen <cory.quammen at kitware.com <mailto:cory.quammen at kitware.com>> wrote:
> Hi Jesse,
> 
> It should be possible to do this. See Chapter 7 of the ParaView User Guide [1] or Section 2.13 or the ParaView Tutorial [2] for more information.
> 
> [1] http://www.paraview.org/paraview-guide/ <http://www.paraview.org/paraview-guide/>
> [2] http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf <http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf>
> 
> HTH,
> Cory
> 
> On Mon, Jul 6, 2015 at 8:56 AM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
> Greetings all,
> 
>   I sent this message last week, but errantly sent the .tif image which made it a huge file. The JPG is now attached.
> 
>    I?m trying to make an animation in Paraview. I took a stab at it before with Paraview, but I recall it as being tedious. Maybe I can get some pointers from the experts.
> 
>   So, the attached imaged is a cube view of the electromagnetic response over sea ice. What Im trying to do with this animation is two things:
> 
>   1.) Move the horizontal slice and Y-Z vertical slice (the slice without the tubes) up and down, and side to side, respectively, such that as if you selected the particular slide in the Pipeline browser, you could drag the slice in question and move it manually to see the different responses. Therefore I?m trying to automate it.
> 
>   2.) Rotate it about the z-axis 5 degrees (to about 180) at each iteration and return, then rotate it 5 degrees at each iteration about the y-axis (till about 45 degrees) and return. These rotations will occur while ?action item" 1 is happening.
> 
>    Any thoughts/suggestions?
> 
>     Thanks!
>     Jesse
> 
> _______________________________________________
> Powered by www.kitware.com <http://www.kitware.com/>
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html <http://www.kitware.com/opensource/opensource.html>
> 
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
> 
> Search the list archives at: http://markmail.org/search/?q=ParaView <http://markmail.org/search/?q=ParaView>
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview <http://public.kitware.com/mailman/listinfo/paraview>
> 
> 
> 
> 
> -- 
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
> _______________________________________________
> Powered by www.kitware.com <http://www.kitware.com/>
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html <http://www.kitware.com/opensource/opensource.html>
> 
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
> 
> Search the list archives at: http://markmail.org/search/?q=ParaView <http://markmail.org/search/?q=ParaView>
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview <http://public.kitware.com/mailman/listinfo/paraview>
> <YZPlaneInitialForParaview.jpeg>

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

From wascott at sandia.gov  Tue Jul 14 19:22:52 2015
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 14 Jul 2015 23:22:52 +0000
Subject: [Paraview] Plot cumulative integral over time of a variable
Message-ID: <f00630c065ee4933aff5a6f5aeee21d7@ES01AMSNLNT.srn.sandia.gov>

Question from a user:

I would like to use paraview to do the following:

1)      Integrate a nodal variable over a volume (IntegrateVariables filter does this)

2)      Then, integrate the result of the volume integral over time (cumulative integral)

The "IntegrateVariables" filter works just fine to integrate over the volume, and I can plot the results of it over time by selecting "RowData" from the "PlotSelectionOverTime" filter.  I just can't figure out how to do #2 - integrate these results over time with something like "numpy.trapz" or "scipy.integrate.cumtrapz".

I feel like this has probably been asked a million times, but I still seem to have trouble with it.  I think I usually fall back to other post processing tools.  Can this be done all in Paraview?



Thanks,

Alan


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

From rajphysics.mon at gmail.com  Wed Jul 15 00:51:56 2015
From: rajphysics.mon at gmail.com (Raj Kumar Manna)
Date: Wed, 15 Jul 2015 10:21:56 +0530
Subject: [Paraview] paraview python script : Delete(renderView1) does not
	free memory
Message-ID: <CANt3wQti+7nAcLhyCaD9yiaNgsAS2cJXOgpBJA5bZ5nhNrniUQ@mail.gmail.com>

Dear All,

I am trying to load multiple state files by running a python script with
python shell. The script is the following

#### import the simple module from the paraview
from paraview.simple import *

for time in range(0,200):
        renderView1 = GetActiveViewOrCreate('RenderView')

        # destroy renderView1
        Delete(renderView1)
        del renderView1

        filename = 'filepath/filename-%s.pvsm' % time
        servermanager.LoadState(filename)
        renderView=SetActiveView(GetRenderView())
        Render()
        # get layout
        viewLayout = GetLayout()

        # save screenshot
        SaveScreenshot('filepath/filename-%s.png' % time,
layout=viewLayout, magnification=3, quality=100)

I was monitoring the memory used by machine, after some time steps the
memory used by the machine is whole RAM. Can anybody tell me what I am
doing wrong here.

I appreciate your time and support.


Thanks
Raj



-- 
##################################################################
Raj Kumar Manna
Complex Fluid & Biological Physics Lab
IIT Madras

Ph. No. 8144637401

alternate email: raj at physics.iitm.ac.in <rajphysics.mon at gmail.com>
####################################################################
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/04f62777/attachment.html>

From andrei.cimpoeru at hotmail.co.uk  Wed Jul 15 04:42:21 2015
From: andrei.cimpoeru at hotmail.co.uk (Ionut Andrei Cimpoeru)
Date: Wed, 15 Jul 2015 09:42:21 +0100
Subject: [Paraview] time average in paraview
Message-ID: <DUB129-W7355D78AA3B5C1BFA154CBB39A0@phx.gbl>

Hi there,

My name is Andrei Cimpoeru and I'm using Paraview 4.2. I came across with a lot of unsteady data from a   CFD simulation and I need time-average it. I used the temporal statistics filter available in Paraview but is very slow. Is there a way to speed up the process? Also I would like to know if there is way of how to time average only for a range of time steps rather than the whole simulation?
I would appreciate your help and many thanks.

Regards

 

Andrei Cimpoeru
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/4c2d9867/attachment.html>

From anny9936 at gmail.com  Wed Jul 15 09:06:19 2015
From: anny9936 at gmail.com (Anny Su)
Date: Wed, 15 Jul 2015 21:06:19 +0800
Subject: [Paraview] Fwd: trouble on merging STL meshes
In-Reply-To: <CAD=-HJMOcE--Bg4dS5ay8XXxVkZd=2dwRLnFvktzcZmNf+5rOg@mail.gmail.com>
References: <CAD=-HJMOcE--Bg4dS5ay8XXxVkZd=2dwRLnFvktzcZmNf+5rOg@mail.gmail.com>
Message-ID: <CAD=-HJP_D3G-BedNMB2nRV7CsEPXH9=uAtKWbO7iN7vvFFnE8Q@mail.gmail.com>

Dear Sir/Ms,

I'm having trouble with ParaView when trying to merge two different STL
mesh into one. I imported these two STL mesh and can find it suitable well
when open the eye on pipeline, but I can't find a way to export these whole
STL mesh. I tried many ways such as click Apply button below the pipeline
browser and changed some parameters; chose all files by pressing ctrl, but
it didn't work when I save it as another file, it often saved as the last
file I chose, not the merged mesh.

Please help me if you know how to merge STL files. By the way, do not
change any of its original settings will be better.

Thanks for your time in advance and looking for your reply!

Anny

7.15
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/6cd7f70c/attachment.html>

From cory.quammen at kitware.com  Wed Jul 15 09:28:44 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 15 Jul 2015 09:28:44 -0400
Subject: [Paraview] Fwd: trouble on merging STL meshes
In-Reply-To: <CAD=-HJP_D3G-BedNMB2nRV7CsEPXH9=uAtKWbO7iN7vvFFnE8Q@mail.gmail.com>
References: <CAD=-HJMOcE--Bg4dS5ay8XXxVkZd=2dwRLnFvktzcZmNf+5rOg@mail.gmail.com>
 <CAD=-HJP_D3G-BedNMB2nRV7CsEPXH9=uAtKWbO7iN7vvFFnE8Q@mail.gmail.com>
Message-ID: <CAB5Fpx5kAmbRbky=Yu2tQjMjqy+m9ma2sgz+gkU45NZ6xHCmBw@mail.gmail.com>

Anny,

You will need to apply an Append Geometry filter to your two STL files. To
use it, control-click on your two STL files in the Pipeline Browser. Then
choose the Filters -> Alphabetical -> Append Geometry filter and click
apply. You should get a new pipeline object named "AppendGeometry1". Click
on this and choose File -> Save Data... Find the STL extension in the
"Files of type" menu save your STL file.

Hope that helps,
Cory



On Wed, Jul 15, 2015 at 9:06 AM, Anny Su <anny9936 at gmail.com> wrote:

> Dear Sir/Ms,
>
> I'm having trouble with ParaView when trying to merge two different STL
> mesh into one. I imported these two STL mesh and can find it suitable well
> when open the eye on pipeline, but I can't find a way to export these whole
> STL mesh. I tried many ways such as click Apply button below the pipeline
> browser and changed some parameters; chose all files by pressing ctrl, but
> it didn't work when I save it as another file, it often saved as the last
> file I chose, not the merged mesh.
>
> Please help me if you know how to merge STL files. By the way, do not
> change any of its original settings will be better.
>
> Thanks for your time in advance and looking for your reply!
>
> Anny
>
> 7.15
>
>
>
> _______________________________________________
> 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
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/f3b157ff/attachment.html>

From albandil at atlas.cz  Wed Jul 15 09:30:28 2015
From: albandil at atlas.cz (=?utf-8?q?Jakub_Benda?=)
Date: Wed, 15 Jul 2015 15:30:28 +0200
Subject: [Paraview] =?utf-8?q?Filter_-_choose_from_multiple_input?=
Message-ID: <20150715153028.2E67C3B7@atlas.cz>

Hello all,
?
I'd like to create a custom filter that accepts arbitrary number of input connections (using InputProperty with multiple_input="1") and fills a CompositeTreeDomain widget (or similar) with those objects, so that the user can select a subset of inputs to work with.
How can this be accomplished?
?
Thanks in advance
?
Jakub Benda

From cory.quammen at kitware.com  Wed Jul 15 09:59:46 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 15 Jul 2015 09:59:46 -0400
Subject: [Paraview] Python: Save Screenshot in parallel projection
In-Reply-To: <CAEqguQY8z8zHaX9ErnnoAxjfWgtA5tSHNCU_P8coyx9DTVtYHA@mail.gmail.com>
References: <CAEqguQY8z8zHaX9ErnnoAxjfWgtA5tSHNCU_P8coyx9DTVtYHA@mail.gmail.com>
Message-ID: <CAB5Fpx60y0Mb0pg3TjD7ZDg=dCd+f33mfWT2KHRWzkEs4kfccg@mail.gmail.com>

Jonas,

What version of ParaView are you using? I am using the latest master branch
and saving a screenshot of with parallel projection seems to work fine on
this version.

Thanks,
Cory

On Mon, Jul 13, 2015 at 7:10 AM, Jonas Asche via ParaView <
paraview at paraview.org> wrote:

> Hello, when i try to switch to parallel projection on in my script i can
> only save a screenshot with parallel projection disabled:
>
> self.__getView().CameraParallelProjection = 1
> self.__getView().CameraParallelScale = 1.0
> self.__getView().CameraViewUp = [0.0, 0.0, 1.0]
> self.__getView().CameraPosition = camdirection[axis]
> self.__getView().CameraFocalPoint = [0.0, 0.0, 33.32500076293945]
> self.__getView().CameraClippingRange = [154.56988142373606, 215.9545612783452]
>
> SaveScreenshot(str(self.__getConfig().get("save", "path") + 'img-') + str(axis) + "-" + str(distribution) + '.png', self.__getView())
>
> When when i print out the parallel scale AFTER savin the screenshot it is set to 46.6471043813.
>
>
> is this the same bug like here: http://paraview.org/Bug/view.php?id=7466
>
> ?
>
> Is there a workaround or am i doing something wrong?
>
> Thanks,
>
> Jonas
>
>
>
>
> _______________________________________________
> 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
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/023b1bac/attachment.html>

From cory.quammen at kitware.com  Wed Jul 15 10:03:56 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 15 Jul 2015 10:03:56 -0400
Subject: [Paraview] Fwd: trouble on merging STL meshes
In-Reply-To: <55a6665f.0e81460a.ce1ea.ffffc8f3@mx.google.com>
References: <55a6665f.0e81460a.ce1ea.ffffc8f3@mx.google.com>
Message-ID: <CAB5Fpx7hQji2H4sLjtsh=u1yvEM19rUcFemdcSEjdiiX-j513w@mail.gmail.com>

Anny,

You are welcome. I hope you find ParaView useful in your work.

The ParaView Guide is a great resource to learn about how to use ParaView.
It is available as a free PDF [1], or you can purchase a paper copy with
extra chapters at [2].

Cheers,
Cory

[1]
http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.3&type=data&os=all&downloadFile=TheParaViewGuide-v4.3-CC-Edition.pdf

[2] http://www.amazon.com/dp/1930934300/ref=cm_sw_su_dp

On Wed, Jul 15, 2015 at 9:55 AM, anny9936 <anny9936 at gmail.com> wrote:

> Dear Cory,
>
> Thank you so much!!! It works! You have really helped me through
> struggling for so long a time!
>
> Thanks again for you are the fastest efficient reply I ever seen! Just
> can't imagine how surprise I am right now!!!
>
> Hope you will get such helps whenever you need:)
>
> Yours Anny
>
> - ?? Smartisan T1 -
> Cory Quammen <cory.quammen at kitware.com> ? 2015?7?15??21:28???
>
> Anny,
>
> You will need to apply an Append Geometry filter to your two STL files. To
> use it, control-click on your two STL files in the Pipeline Browser. Then
> choose the Filters -> Alphabetical -> Append Geometry filter and click
> apply. You should get a new pipeline object named "AppendGeometry1". Click
> on this and choose File -> Save Data... Find the STL extension in the
> "Files of type" menu save your STL file.
>
> Hope that helps,
> Cory
>
>
>
> On Wed, Jul 15, 2015 at 9:06 AM, Anny Su <anny9936 at gmail.com> wrote:
>
>> Dear Sir/Ms,
>>
>> I'm having trouble with ParaView when trying to merge two different STL
>> mesh into one. I imported these two STL mesh and can find it suitable well
>> when open the eye on pipeline, but I can't find a way to export these whole
>> STL mesh. I tried many ways such as click Apply button below the pipeline
>> browser and changed some parameters; chose all files by pressing ctrl, but
>> it didn't work when I save it as another file, it often saved as the last
>> file I chose, not the merged mesh.
>>
>> Please help me if you know how to merge STL files. By the way, do not
>> change any of its original settings will be better.
>>
>> Thanks for your time in advance and looking for your reply!
>>
>> Anny
>>
>> 7.15
>>
>>
>>
>> _______________________________________________
>> 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
>>
>>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/26b69ba3/attachment.html>

From andy.bauer at kitware.com  Wed Jul 15 10:07:49 2015
From: andy.bauer at kitware.com (Andy Bauer)
Date: Wed, 15 Jul 2015 10:07:49 -0400
Subject: [Paraview] time average in paraview
In-Reply-To: <DUB129-W7355D78AA3B5C1BFA154CBB39A0@phx.gbl>
References: <DUB129-W7355D78AA3B5C1BFA154CBB39A0@phx.gbl>
Message-ID: <CAMaOp+E6GAC+99aUd=dpv2CKBg7_TicrH5nw+cUR=o9yTFn6Cg@mail.gmail.com>

Hi,

You may want to look at ParaView's spatio-temporal parallelism tool --
http://www.paraview.org/Wiki/Spatio-Temporal_Parallelism. The bottom line
with respect to performance for temporal statistics is that there's a lot
of file IO involved and usually that's the bottleneck.

As for averaging over only a subset of time steps, the only ways I can
currently think of doing this are:

   - Only read in the time steps you want. This would be dependent on the
   file format and its corresponding reader in PV.
   - Use a Python Programmable Filter to get rid of the time steps you
   don't want.

Cheers,

Andy

On Wed, Jul 15, 2015 at 4:42 AM, Ionut Andrei Cimpoeru <
andrei.cimpoeru at hotmail.co.uk> wrote:

> Hi there,
>
>
> My name is Andrei Cimpoeru and I'm using Paraview 4.2. I came across with
> a lot of unsteady data from a   CFD simulation and I need time-average it.
> I used the temporal statistics filter available in Paraview but is very
> slow. Is there a way to speed up the process?
> Also I would like to know if there is way of how to time average only for
> a range of time steps rather than the whole simulation?
>
> I would appreciate your help and many thanks.
>
>
> Regards
>
> Andrei Cimpoeru
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/d82eb0d2/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Jul 15 10:14:50 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 15 Jul 2015 14:14:50 +0000
Subject: [Paraview] paraview python script : Delete(renderView1) does
 not free memory
In-Reply-To: <CANt3wQti+7nAcLhyCaD9yiaNgsAS2cJXOgpBJA5bZ5nhNrniUQ@mail.gmail.com>
References: <CANt3wQti+7nAcLhyCaD9yiaNgsAS2cJXOgpBJA5bZ5nhNrniUQ@mail.gmail.com>
Message-ID: <CADHSJjCNF2u_3rzrLne0pkt9wpuU_U=RvZa8dyy_vLDKamnBnw@mail.gmail.com>

Delete() will only remove the render view, not all other proxies that were
created as part of the state loading operation. The following script should
do the trick:

--------------------------------------------------------------------------------
from paraview.simple import *

def ResetSession():
    pxm = servermanager.ProxyManager()
    pxm.UnRegisterProxies()
    del pxm
    Disconnect()
    Connect()

for i in range(0, 10):
    ResetSession()
    servermanager.LoadState("/tmp/sample.pvsm")
    renderView=SetActiveView(GetRenderView())
    Render()
--------------------------------------------------------------------------------

Utkarsh


On Wed, Jul 15, 2015 at 12:52 AM Raj Kumar Manna <rajphysics.mon at gmail.com>
wrote:

> Dear All,
>
> I am trying to load multiple state files by running a python script with
> python shell. The script is the following
>
> #### import the simple module from the paraview
> from paraview.simple import *
>
> for time in range(0,200):
>         renderView1 = GetActiveViewOrCreate('RenderView')
>
>         # destroy renderView1
>         Delete(renderView1)
>         del renderView1
>
>         filename = 'filepath/filename-%s.pvsm' % time
>         servermanager.LoadState(filename)
>         renderView=SetActiveView(GetRenderView())
>         Render()
>         # get layout
>         viewLayout = GetLayout()
>
>         # save screenshot
>         SaveScreenshot('filepath/filename-%s.png' % time,
> layout=viewLayout, magnification=3, quality=100)
>
> I was monitoring the memory used by machine, after some time steps the
> memory used by the machine is whole RAM. Can anybody tell me what I am
> doing wrong here.
>
> I appreciate your time and support.
>
>
> Thanks
> Raj
>
>
>
> --
> ##################################################################
> Raj Kumar Manna
> Complex Fluid & Biological Physics Lab
> IIT Madras
>
> Ph. No. 8144637401
>
> alternate email: raj at physics.iitm.ac.in <rajphysics.mon at 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/8e0b6413/attachment.html>

From andy.bauer at kitware.com  Wed Jul 15 10:18:45 2015
From: andy.bauer at kitware.com (Andy Bauer)
Date: Wed, 15 Jul 2015 10:18:45 -0400
Subject: [Paraview] Plot cumulative integral over time of a variable
In-Reply-To: <f00630c065ee4933aff5a6f5aeee21d7@ES01AMSNLNT.srn.sandia.gov>
References: <f00630c065ee4933aff5a6f5aeee21d7@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CAMaOp+H5fn4YfJRbk+thc3kKGiQ1iP-5EjeGY_+P_tNwCqZqcg@mail.gmail.com>

Hi Alan,

For #2, a hacky way would be to use the temporal statistics to get the
average value and then multiply that by the number of time steps. The only
other way I can think of is by using a Python Programmable Filter to
integrate the values over time. The Python Programmable Filter recently was
changed to have access to the pipeline executive so that you can have it
iterate over time steps.

Attached is a state file which I used to iterate over time steps in a
programmable filter. It's not working with PV 4.3.1 but it may help give
you some guidance on how to do it. If it's overly confusing  (which it very
well could be -- I'm too lazy to look at it closely right now) let me know
and I can see if I can update it to work with the latest version of PV.

Best,
Andy

On Tue, Jul 14, 2015 at 7:22 PM, Scott, W Alan <wascott at sandia.gov> wrote:

>  Question from a user:
>
> I would like to use paraview to do the following:
>
> 1)      Integrate a nodal variable over a volume (IntegrateVariables
> filter does this)
>
> 2)      Then, integrate the result of the volume integral over time
> (cumulative integral)
>
> The "IntegrateVariables" filter works just fine to integrate over the
> volume, and I can plot the results of it over time by selecting "RowData"
> from the "PlotSelectionOverTime" filter.  I just can't figure out how to do
> #2 - integrate these results over time with something like "numpy.trapz" or
> "scipy.integrate.cumtrapz".
>
> I feel like this has probably been asked a million times, but I still seem
> to have trouble with it.  I think I usually fall back to other post
> processing tools.  Can this be done all in Paraview?
>
>
>
> Thanks,
>
> Alan
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/59e556e7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: programmablefilteriterateovertime.pvsm
Type: application/octet-stream
Size: 3168 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/59e556e7/attachment.obj>

From cory.quammen at kitware.com  Wed Jul 15 10:23:31 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 15 Jul 2015 10:23:31 -0400
Subject: [Paraview] Computing displacement
In-Reply-To: <CAG+yLxmwg6W9mD9NcVYmuopZFqwMh3_cWcC=k_kfZcjGrf07=g@mail.gmail.com>
References: <CAG+yLxmwg6W9mD9NcVYmuopZFqwMh3_cWcC=k_kfZcjGrf07=g@mail.gmail.com>
Message-ID: <CAB5Fpx4j3CrTonomRd2O7BwUUW1fbVnd7QaVwzTCbU=t1VUZ_Q@mail.gmail.com>

Elaine,

I am assuming that you have time-series data and that your displacement
values are defined in a point data array named "Displacement".

I suggest the following:

- Load your time series data by selecting all the files in the series in
the file dialog (input[0])
- Load just the first time step (input[1])
- Control-click each of the sources in the Pipeline Browser so that they
are selected.
- Use the Python Calculator with an expression like

inputs[0].PointData['Normals'] - inputs[1].PointData['Normals']

You can set the output array name to "New_displacement".

To find the maximum displacement in all the timesteps, you can color your
data set by "New_displacement." In the Color Map Editor, click on the
"Rescale to data range over all timesteps" button. This will compute
New_displacement over all timesteps and the maximum value will be in the
maximum entry of the color map, which can be accessed by clicking on the
"Rescale to custom range" button" and viewing the value in the dialog box
that appears.

Hope that helps,
Cory

On Tue, Jul 14, 2015 at 1:25 PM, Elaine Tang <lingdeer at gmail.com> wrote:

> Hi,
>
> I have a set of data with displacement point data. I want to create a new
> variable that:
>
> New_displacement (t) = displacement (t) - displacement (t=0)
>
> Any idea on how to do that? I was trying to use calculator but I don't
> know how can I specific displacement for t=0.
>
> Also, is there any easy way in Paraview to find the maximum displacement
> throughout all time steps?
>
> Thank you!
> --
> Elaine Tang
>
>
> _______________________________________________
> 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
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/c104a4a7/attachment.html>

From cory.quammen at kitware.com  Wed Jul 15 10:44:14 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 15 Jul 2015 10:44:14 -0400
Subject: [Paraview] Custom animation help? (Corrected image)
In-Reply-To: <D1509E00-6BFE-42F1-8602-ED230B0C5532@udel.edu>
References: <A9BF9A24-AFD8-41DD-8F0C-446AD9B8702C@udel.edu>
 <CAB5Fpx7yjsZEwk5MtCMVuJ5cVtga=zpfF9rK4S42snNkamAO=A@mail.gmail.com>
 <CADwGrVpXTnqgaD_DciowFwe2pc6KC6r332jLwKBnAESWBjkYKQ@mail.gmail.com>
 <D1509E00-6BFE-42F1-8602-ED230B0C5532@udel.edu>
Message-ID: <CAB5Fpx6Uw5WdtPK4Zd+9GqyUoKUQ=0zoXhkybWg6XU51nmRSzw@mail.gmail.com>

Jesse,

When you load a state file, you get the chance to update the data file
paths in the state file. You can use this mechanism to load a different
data file with the same state applied to it.

HTH,
Cory

On Tue, Jul 14, 2015 at 5:36 PM, Jesse Samluk <sevensam at udel.edu> wrote:

> Dan and Cory,
>
> Thanks for the guides. I?m getting a lot better at animations now!
> Awesome! The guides helped a lot.
>
>   1 more quick question for you.
>
>  I know how to save state files, but is there such a way to save the
> animation ?state? that I just created in a state file, such that, if I use
> that state file, the animation scheme will reappear to other data files
> I?ve created?
>
>    Wasn?t too sure on this.
>
>  Thanks!
>   Jesse
>
>
> On Jul 10, 2015, at 5:34 PM, Dan Lipsa <dan.lipsa at kitware.com> wrote:
>
> Jesse,
> See also the following thread:
>
>
> http://markmail.org/search/?q=+programmimg+the+camera+position+using+python#query:%20programmimg%20the%20camera%20position%20using%20python+page:1+mid:nkm5rmw2hz52egnk+state:results
>
> On Fri, Jul 10, 2015 at 5:19 PM Cory Quammen <cory.quammen at kitware.com>
> wrote:
>
>> Hi Jesse,
>>
>> It should be possible to do this. See Chapter 7 of the ParaView User
>> Guide [1] or Section 2.13 or the ParaView Tutorial [2] for more information.
>>
>> [1] http://www.paraview.org/paraview-guide/
>> [2] http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf
>>
>> HTH,
>> Cory
>>
>> On Mon, Jul 6, 2015 at 8:56 AM, Jesse Samluk <sevensam at udel.edu> wrote:
>>
>>> Greetings all,
>>>
>>>   I sent this message last week, but errantly sent the .tif image which
>>> made it a huge file. The JPG is now attached.
>>>
>>>    I?m trying to make an animation in Paraview. I took a stab at it
>>> before with Paraview, but I recall it as being tedious. Maybe I can get
>>> some pointers from the experts.
>>>
>>>   So, the attached imaged is a cube view of the electromagnetic response
>>> over sea ice. What Im trying to do with this animation is two things:
>>>
>>>   1.) Move the horizontal slice and Y-Z vertical slice (the slice
>>> without the tubes) up and down, and side to side, respectively, such that
>>> as if you selected the particular slide in the Pipeline browser, you could
>>> drag the slice in question and move it manually to see the different
>>> responses. Therefore I?m trying to automate it.
>>>
>>>   2.) Rotate it about the z-axis 5 degrees (to about 180) at each
>>> iteration and return, then rotate it 5 degrees at each iteration about the
>>> y-axis (till about 45 degrees) and return. These rotations will occur while
>>> ?action item" 1 is happening.
>>>
>>>    Any thoughts/suggestions?
>>>
>>>     Thanks!
>>>     Jesse
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>>  _______________________________________________
>> 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
>>
> <YZPlaneInitialForParaview.jpeg>
>
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/6855fa4d/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Jul 15 11:05:48 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 15 Jul 2015 15:05:48 +0000
Subject: [Paraview] Plot cumulative integral over time of a variable
In-Reply-To: <f00630c065ee4933aff5a6f5aeee21d7@ES01AMSNLNT.srn.sandia.gov>
References: <f00630c065ee4933aff5a6f5aeee21d7@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjAu=058y7Wj0-CkxMCM3_Y7ngMHV9GEG3eOYyy-Gz_wyQ@mail.gmail.com>

Alan,

Attached is a state file (using can.ex2) which indeed uses numpy.trapz() to
do the work. It needs a small patch to be applied to VTK (attached) to
avoid a segfault.

The Programmable Filter adds a new row-data array named "trapz" which is
the result of the operation (it's repeated so we can add it to RowData
rather than field data.

Utkarsh

On Tue, Jul 14, 2015 at 7:23 PM Scott, W Alan <wascott at sandia.gov> wrote:

>  Question from a user:
>
> I would like to use paraview to do the following:
>
> 1)      Integrate a nodal variable over a volume (IntegrateVariables
> filter does this)
>
> 2)      Then, integrate the result of the volume integral over time
> (cumulative integral)
>
> The "IntegrateVariables" filter works just fine to integrate over the
> volume, and I can plot the results of it over time by selecting "RowData"
> from the "PlotSelectionOverTime" filter.  I just can't figure out how to do
> #2 - integrate these results over time with something like "numpy.trapz" or
> "scipy.integrate.cumtrapz".
>
> I feel like this has probably been asked a million times, but I still seem
> to have trouble with it.  I think I usually fall back to other post
> processing tools.  Can this be done all in Paraview?
>
>
>
> Thanks,
>
> Alan
>
>
>  _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/ee6aa013/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FixSegfault.VTK.patch
Type: text/x-patch
Size: 1328 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/ee6aa013/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: trapz.pvsm
Type: application/octet-stream
Size: 87578 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/ee6aa013/attachment-0001.obj>

From sevensam at udel.edu  Wed Jul 15 11:37:11 2015
From: sevensam at udel.edu (Jesse Samluk)
Date: Wed, 15 Jul 2015 11:37:11 -0400
Subject: [Paraview] Custom animation help? (Corrected image)
In-Reply-To: <CAB5Fpx6Uw5WdtPK4Zd+9GqyUoKUQ=0zoXhkybWg6XU51nmRSzw@mail.gmail.com>
References: <A9BF9A24-AFD8-41DD-8F0C-446AD9B8702C@udel.edu>
 <CAB5Fpx7yjsZEwk5MtCMVuJ5cVtga=zpfF9rK4S42snNkamAO=A@mail.gmail.com>
 <CADwGrVpXTnqgaD_DciowFwe2pc6KC6r332jLwKBnAESWBjkYKQ@mail.gmail.com>
 <D1509E00-6BFE-42F1-8602-ED230B0C5532@udel.edu>
 <CAB5Fpx6Uw5WdtPK4Zd+9GqyUoKUQ=0zoXhkybWg6XU51nmRSzw@mail.gmail.com>
Message-ID: <5E88E865-62F4-4C6D-84C4-97839317CB59@udel.edu>

Cory,

Right, but isn?t that going to ?throw away? the animation ?tracks" I just created?

For instance, I have created an animation with a vtk data set I?m working with. Cool.

But say I close Paraview, I lose the animation tracks I just created. Right.

So how can I save those animation tracks? Is this even possible in Paraview?

Thanks!
Jesse

> On Jul 15, 2015, at 10:44 AM, Cory Quammen <cory.quammen at kitware.com> wrote:
> 
> Jesse,
> 
> When you load a state file, you get the chance to update the data file paths in the state file. You can use this mechanism to load a different data file with the same state applied to it.
> 
> HTH,
> Cory
> 
> On Tue, Jul 14, 2015 at 5:36 PM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
> Dan and Cory,
> 
> Thanks for the guides. I?m getting a lot better at animations now! Awesome! The guides helped a lot.
> 
>   1 more quick question for you.
> 
>  I know how to save state files, but is there such a way to save the animation ?state? that I just created in a state file, such that, if I use that state file, the animation scheme will reappear to other data files I?ve created?
> 
>    Wasn?t too sure on this.
> 
>  Thanks!
>   Jesse
>   
>> On Jul 10, 2015, at 5:34 PM, Dan Lipsa <dan.lipsa at kitware.com <mailto:dan.lipsa at kitware.com>> wrote:
>> 
>> Jesse,
>> See also the following thread:
>> 
>> http://markmail.org/search/?q=+programmimg+the+camera+position+using+python#query:%20programmimg%20the%20camera%20position%20using%20python+page:1+mid:nkm5rmw2hz52egnk+state:results <http://markmail.org/search/?q=+programmimg+the+camera+position+using+python#query:%20programmimg%20the%20camera%20position%20using%20python+page:1+mid:nkm5rmw2hz52egnk+state:results>
>> 
>> On Fri, Jul 10, 2015 at 5:19 PM Cory Quammen <cory.quammen at kitware.com <mailto:cory.quammen at kitware.com>> wrote:
>> Hi Jesse,
>> 
>> It should be possible to do this. See Chapter 7 of the ParaView User Guide [1] or Section 2.13 or the ParaView Tutorial [2] for more information.
>> 
>> [1] http://www.paraview.org/paraview-guide/ <http://www.paraview.org/paraview-guide/>
>> [2] http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf <http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf>
>> 
>> HTH,
>> Cory
>> 
>> On Mon, Jul 6, 2015 at 8:56 AM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
>> Greetings all,
>> 
>>   I sent this message last week, but errantly sent the .tif image which made it a huge file. The JPG is now attached.
>> 
>>    I?m trying to make an animation in Paraview. I took a stab at it before with Paraview, but I recall it as being tedious. Maybe I can get some pointers from the experts.
>> 
>>   So, the attached imaged is a cube view of the electromagnetic response over sea ice. What Im trying to do with this animation is two things:
>> 
>>   1.) Move the horizontal slice and Y-Z vertical slice (the slice without the tubes) up and down, and side to side, respectively, such that as if you selected the particular slide in the Pipeline browser, you could drag the slice in question and move it manually to see the different responses. Therefore I?m trying to automate it.
>> 
>>   2.) Rotate it about the z-axis 5 degrees (to about 180) at each iteration and return, then rotate it 5 degrees at each iteration about the y-axis (till about 45 degrees) and return. These rotations will occur while ?action item" 1 is happening.
>> 
>>    Any thoughts/suggestions?
>> 
>>     Thanks!
>>     Jesse
>> 
>> _______________________________________________
>> Powered by www.kitware.com <http://www.kitware.com/>
>> 
>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html <http://www.kitware.com/opensource/opensource.html>
>> 
>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
>> 
>> Search the list archives at: http://markmail.org/search/?q=ParaView <http://markmail.org/search/?q=ParaView>
>> 
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview <http://public.kitware.com/mailman/listinfo/paraview>
>> 
>> 
>> 
>> 
>> -- 
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>> _______________________________________________
>> Powered by www.kitware.com <http://www.kitware.com/>
>> 
>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html <http://www.kitware.com/opensource/opensource.html>
>> 
>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
>> 
>> Search the list archives at: http://markmail.org/search/?q=ParaView <http://markmail.org/search/?q=ParaView>
>> 
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview <http://public.kitware.com/mailman/listinfo/paraview>
>> <YZPlaneInitialForParaview.jpeg>
> 
> 
> 
> 
> -- 
> Cory Quammen
> R&D Engineer
> Kitware, Inc.

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

From wascott at sandia.gov  Wed Jul 15 12:38:34 2015
From: wascott at sandia.gov (Scott, W Alan)
Date: Wed, 15 Jul 2015 16:38:34 +0000
Subject: [Paraview] [EXTERNAL] Re: Plot cumulative integral over time of
 a variable
In-Reply-To: <CADHSJjAu=058y7Wj0-CkxMCM3_Y7ngMHV9GEG3eOYyy-Gz_wyQ@mail.gmail.com>
References: <f00630c065ee4933aff5a6f5aeee21d7@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjAu=058y7Wj0-CkxMCM3_Y7ngMHV9GEG3eOYyy-Gz_wyQ@mail.gmail.com>
Message-ID: <44ad446b7cb6458ba17586111bca0cd7@ES01AMSNLNT.srn.sandia.gov>

Thanks!

Are you going to get the patch into the next release?

Alan

From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
Sent: Wednesday, July 15, 2015 9:06 AM
To: Scott, W Alan; paraview at paraview.org
Subject: [EXTERNAL] Re: [Paraview] Plot cumulative integral over time of a variable

Alan,

Attached is a state file (using can.ex2) which indeed uses numpy.trapz() to do the work. It needs a small patch to be applied to VTK (attached) to avoid a segfault.

The Programmable Filter adds a new row-data array named "trapz" which is the result of the operation (it's repeated so we can add it to RowData rather than field data.

Utkarsh
On Tue, Jul 14, 2015 at 7:23 PM Scott, W Alan <wascott at sandia.gov<mailto:wascott at sandia.gov>> wrote:
Question from a user:

I would like to use paraview to do the following:

1)      Integrate a nodal variable over a volume (IntegrateVariables filter does this)

2)      Then, integrate the result of the volume integral over time (cumulative integral)

The "IntegrateVariables" filter works just fine to integrate over the volume, and I can plot the results of it over time by selecting "RowData" from the "PlotSelectionOverTime" filter.  I just can't figure out how to do #2 - integrate these results over time with something like "numpy.trapz" or "scipy.integrate.cumtrapz".

I feel like this has probably been asked a million times, but I still seem to have trouble with it.  I think I usually fall back to other post processing tools.  Can this be done all in Paraview?



Thanks,

Alan


_______________________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/35f79c9c/attachment.html>

From cory.quammen at kitware.com  Wed Jul 15 13:08:44 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 15 Jul 2015 13:08:44 -0400
Subject: [Paraview] Custom animation help? (Corrected image)
In-Reply-To: <5E88E865-62F4-4C6D-84C4-97839317CB59@udel.edu>
References: <A9BF9A24-AFD8-41DD-8F0C-446AD9B8702C@udel.edu>
 <CAB5Fpx7yjsZEwk5MtCMVuJ5cVtga=zpfF9rK4S42snNkamAO=A@mail.gmail.com>
 <CADwGrVpXTnqgaD_DciowFwe2pc6KC6r332jLwKBnAESWBjkYKQ@mail.gmail.com>
 <D1509E00-6BFE-42F1-8602-ED230B0C5532@udel.edu>
 <CAB5Fpx6Uw5WdtPK4Zd+9GqyUoKUQ=0zoXhkybWg6XU51nmRSzw@mail.gmail.com>
 <5E88E865-62F4-4C6D-84C4-97839317CB59@udel.edu>
Message-ID: <CAB5Fpx6NP5EKFf4es7mf+2gu0UmfMPBxgexKQmpHOyORznbrZQ@mail.gmail.com>

Jesse,

The animation tracks will be saved in the state file. I just tested
ParaView to see if that is the case, and it is. Let us know if it isn't
working for you.

Thanks,
Cory



On Wed, Jul 15, 2015 at 11:37 AM, Jesse Samluk <sevensam at udel.edu> wrote:

> Cory,
>
> Right, but isn?t that going to ?throw away? the animation ?tracks" I just
> created?
>
> For instance, I have created an animation with a vtk data set I?m working
> with. Cool.
>
> But say I close Paraview, I lose the animation tracks I just created.
> Right.
>
> So how can I save those animation tracks? Is this even possible in
> Paraview?
>
> Thanks!
> Jesse
>
> On Jul 15, 2015, at 10:44 AM, Cory Quammen <cory.quammen at kitware.com>
> wrote:
>
> Jesse,
>
> When you load a state file, you get the chance to update the data file
> paths in the state file. You can use this mechanism to load a different
> data file with the same state applied to it.
>
> HTH,
> Cory
>
> On Tue, Jul 14, 2015 at 5:36 PM, Jesse Samluk <sevensam at udel.edu> wrote:
>
>> Dan and Cory,
>>
>> Thanks for the guides. I?m getting a lot better at animations now!
>> Awesome! The guides helped a lot.
>>
>>   1 more quick question for you.
>>
>>  I know how to save state files, but is there such a way to save the
>> animation ?state? that I just created in a state file, such that, if I use
>> that state file, the animation scheme will reappear to other data files
>> I?ve created?
>>
>>    Wasn?t too sure on this.
>>
>>  Thanks!
>>   Jesse
>>
>>
>> On Jul 10, 2015, at 5:34 PM, Dan Lipsa <dan.lipsa at kitware.com> wrote:
>>
>> Jesse,
>> See also the following thread:
>>
>>
>> http://markmail.org/search/?q=+programmimg+the+camera+position+using+python#query:%20programmimg%20the%20camera%20position%20using%20python+page:1+mid:nkm5rmw2hz52egnk+state:results
>>
>> On Fri, Jul 10, 2015 at 5:19 PM Cory Quammen <cory.quammen at kitware.com>
>> wrote:
>>
>>> Hi Jesse,
>>>
>>> It should be possible to do this. See Chapter 7 of the ParaView User
>>> Guide [1] or Section 2.13 or the ParaView Tutorial [2] for more information.
>>>
>>> [1] http://www.paraview.org/paraview-guide/
>>> [2] http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf
>>>
>>> HTH,
>>> Cory
>>>
>>> On Mon, Jul 6, 2015 at 8:56 AM, Jesse Samluk <sevensam at udel.edu> wrote:
>>>
>>>> Greetings all,
>>>>
>>>>   I sent this message last week, but errantly sent the .tif image which
>>>> made it a huge file. The JPG is now attached.
>>>>
>>>>    I?m trying to make an animation in Paraview. I took a stab at it
>>>> before with Paraview, but I recall it as being tedious. Maybe I can get
>>>> some pointers from the experts.
>>>>
>>>>   So, the attached imaged is a cube view of the electromagnetic
>>>> response over sea ice. What Im trying to do with this animation is two
>>>> things:
>>>>
>>>>   1.) Move the horizontal slice and Y-Z vertical slice (the slice
>>>> without the tubes) up and down, and side to side, respectively, such that
>>>> as if you selected the particular slide in the Pipeline browser, you could
>>>> drag the slice in question and move it manually to see the different
>>>> responses. Therefore I?m trying to automate it.
>>>>
>>>>   2.) Rotate it about the z-axis 5 degrees (to about 180) at each
>>>> iteration and return, then rotate it 5 degrees at each iteration about the
>>>> y-axis (till about 45 degrees) and return. These rotations will occur while
>>>> ?action item" 1 is happening.
>>>>
>>>>    Any thoughts/suggestions?
>>>>
>>>>     Thanks!
>>>>     Jesse
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>>
>>>
>>> --
>>> Cory Quammen
>>> R&D Engineer
>>> Kitware, Inc.
>>>  _______________________________________________
>>> 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
>>>
>> <YZPlaneInitialForParaview.jpeg>
>>
>>
>>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/cf583995/attachment.html>

From psavidge0 at lbl.gov  Wed Jul 15 14:21:35 2015
From: psavidge0 at lbl.gov (Patrick Savidge)
Date: Wed, 15 Jul 2015 11:21:35 -0700
Subject: [Paraview] Output data across all timesteps with Python
Message-ID: <CACPGBqEsuGgRXEFsWmdJPcHV86VbdUQ-AQ-o+QMdmyc6S-t07Q@mail.gmail.com>

Hello Everyone,

I am trying to write a python script to output data for each time step. I
know to use the following script to save data for one time step:

>>> writer = CreateWriter(".../foo.csv", source)>>> writer.FieldAssociation = "Points" # or "Cells">>> writer.UpdatePipeline()>>> del writer


I'm curious how I may do this for every time step?

Thank you for your help,

Patrick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/390f738a/attachment.html>

From andrew.robertson at orbitalatk.com  Wed Jul 15 15:09:55 2015
From: andrew.robertson at orbitalatk.com (Robertson, Andrew)
Date: Wed, 15 Jul 2015 19:09:55 +0000
Subject: [Paraview] Contour Plots
Message-ID: <68AC123ECB4AC54DB8876E4D6A3EED966E2DC003@mn05svcwem002.atk.com>

Folks,
New to paraview, but making some progress.
One thing I have not found a way to make a countour plot where there is a black line separating every Nth contour level.
Manual is not that much help
Can this be done directly with the baseline tool?
Thanks
ANdy


Andrew Robertson P.E.
CFD Analyst

GASL Operations
Tactical Propulsion and Controls
ATK
77 Raynor Avenue
Ronkokoma NY 11779

Phone:  631-676-8955<tel:631-737-6100%20Ext%20190>  <- NOTE NEW Number
Fax:  631-588-7023<tel:631-588-7023>
www.atk.com<http://www.atk.com/>

 !! Knowledge and Thoroughness Baby !!
       Happiness is conserving mass



------------------------------------------------------------------------------

Notice: This e-mail is intended solely for use of the individual or entity to which it is addressed and may contain information that is proprietary, privileged and exempt from disclosure under applicable law. If the reader is not the intended recipient or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. This communication may also contain data subject to U.S. export laws. If so, that data subject to the International Traffic in Arms Regulation cannot be disseminated, distributed or copied to foreign nationals, residing in the U.S. or abroad, absent the express prior approval of the U.S. Department of State. If you have received this communication in error, please notify the sender by reply e-mail and destroy the e-mail message and any physical copies made of the communication. Thank you. 
********** **********
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/00adf605/attachment.html>

From sevensam at udel.edu  Wed Jul 15 15:20:04 2015
From: sevensam at udel.edu (Jesse Samluk)
Date: Wed, 15 Jul 2015 15:20:04 -0400
Subject: [Paraview] Custom animation help? (Corrected image)
In-Reply-To: <CAB5Fpx6NP5EKFf4es7mf+2gu0UmfMPBxgexKQmpHOyORznbrZQ@mail.gmail.com>
References: <A9BF9A24-AFD8-41DD-8F0C-446AD9B8702C@udel.edu>
 <CAB5Fpx7yjsZEwk5MtCMVuJ5cVtga=zpfF9rK4S42snNkamAO=A@mail.gmail.com>
 <CADwGrVpXTnqgaD_DciowFwe2pc6KC6r332jLwKBnAESWBjkYKQ@mail.gmail.com>
 <D1509E00-6BFE-42F1-8602-ED230B0C5532@udel.edu>
 <CAB5Fpx6Uw5WdtPK4Zd+9GqyUoKUQ=0zoXhkybWg6XU51nmRSzw@mail.gmail.com>
 <5E88E865-62F4-4C6D-84C4-97839317CB59@udel.edu>
 <CAB5Fpx6NP5EKFf4es7mf+2gu0UmfMPBxgexKQmpHOyORznbrZQ@mail.gmail.com>
Message-ID: <3654E4A3-D81B-4B91-98A2-CF7BA6210526@udel.edu>

Cory,

  Yes that does the trick, but one more question (and I?ve always wondered this). I had 2 vtk files open in the Pipeline browser when I saved the ?animation track? state file as discussed, but, when I select load state file, it's is now pointing to/asking for two vtk files. 

   Any way to adjust this since I want to open only one vtk file, or am I stuck?

   Thanks again!
    Jesse
> On Jul 15, 2015, at 1:08 PM, Cory Quammen <cory.quammen at kitware.com> wrote:
> 
> Jesse,
> 
> The animation tracks will be saved in the state file. I just tested ParaView to see if that is the case, and it is. Let us know if it isn't working for you.
> 
> Thanks,
> Cory
> 
> 
> 
> On Wed, Jul 15, 2015 at 11:37 AM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
> Cory,
> 
> Right, but isn?t that going to ?throw away? the animation ?tracks" I just created?
> 
> For instance, I have created an animation with a vtk data set I?m working with. Cool.
> 
> But say I close Paraview, I lose the animation tracks I just created. Right.
> 
> So how can I save those animation tracks? Is this even possible in Paraview?
> 
> Thanks!
> Jesse
> 
>> On Jul 15, 2015, at 10:44 AM, Cory Quammen <cory.quammen at kitware.com <mailto:cory.quammen at kitware.com>> wrote:
>> 
>> Jesse,
>> 
>> When you load a state file, you get the chance to update the data file paths in the state file. You can use this mechanism to load a different data file with the same state applied to it.
>> 
>> HTH,
>> Cory
>> 
>> On Tue, Jul 14, 2015 at 5:36 PM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
>> Dan and Cory,
>> 
>> Thanks for the guides. I?m getting a lot better at animations now! Awesome! The guides helped a lot.
>> 
>>   1 more quick question for you.
>> 
>>  I know how to save state files, but is there such a way to save the animation ?state? that I just created in a state file, such that, if I use that state file, the animation scheme will reappear to other data files I?ve created?
>> 
>>    Wasn?t too sure on this.
>> 
>>  Thanks!
>>   Jesse
>>   
>>> On Jul 10, 2015, at 5:34 PM, Dan Lipsa <dan.lipsa at kitware.com <mailto:dan.lipsa at kitware.com>> wrote:
>>> 
>>> Jesse,
>>> See also the following thread:
>>> 
>>> http://markmail.org/search/?q=+programmimg+the+camera+position+using+python#query:%20programmimg%20the%20camera%20position%20using%20python+page:1+mid:nkm5rmw2hz52egnk+state:results <http://markmail.org/search/?q=+programmimg+the+camera+position+using+python#query:%20programmimg%20the%20camera%20position%20using%20python+page:1+mid:nkm5rmw2hz52egnk+state:results>
>>> 
>>> On Fri, Jul 10, 2015 at 5:19 PM Cory Quammen <cory.quammen at kitware.com <mailto:cory.quammen at kitware.com>> wrote:
>>> Hi Jesse,
>>> 
>>> It should be possible to do this. See Chapter 7 of the ParaView User Guide [1] or Section 2.13 or the ParaView Tutorial [2] for more information.
>>> 
>>> [1] http://www.paraview.org/paraview-guide/ <http://www.paraview.org/paraview-guide/>
>>> [2] http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf <http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf>
>>> 
>>> HTH,
>>> Cory
>>> 
>>> On Mon, Jul 6, 2015 at 8:56 AM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
>>> Greetings all,
>>> 
>>>   I sent this message last week, but errantly sent the .tif image which made it a huge file. The JPG is now attached.
>>> 
>>>    I?m trying to make an animation in Paraview. I took a stab at it before with Paraview, but I recall it as being tedious. Maybe I can get some pointers from the experts.
>>> 
>>>   So, the attached imaged is a cube view of the electromagnetic response over sea ice. What Im trying to do with this animation is two things:
>>> 
>>>   1.) Move the horizontal slice and Y-Z vertical slice (the slice without the tubes) up and down, and side to side, respectively, such that as if you selected the particular slide in the Pipeline browser, you could drag the slice in question and move it manually to see the different responses. Therefore I?m trying to automate it.
>>> 
>>>   2.) Rotate it about the z-axis 5 degrees (to about 180) at each iteration and return, then rotate it 5 degrees at each iteration about the y-axis (till about 45 degrees) and return. These rotations will occur while ?action item" 1 is happening.
>>> 
>>>    Any thoughts/suggestions?
>>> 
>>>     Thanks!
>>>     Jesse
>>> 
>>> _______________________________________________
>>> Powered by www.kitware.com <http://www.kitware.com/>
>>> 
>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html <http://www.kitware.com/opensource/opensource.html>
>>> 
>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
>>> 
>>> Search the list archives at: http://markmail.org/search/?q=ParaView <http://markmail.org/search/?q=ParaView>
>>> 
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview <http://public.kitware.com/mailman/listinfo/paraview>
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Cory Quammen
>>> R&D Engineer
>>> Kitware, Inc.
>>> _______________________________________________
>>> Powered by www.kitware.com <http://www.kitware.com/>
>>> 
>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html <http://www.kitware.com/opensource/opensource.html>
>>> 
>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
>>> 
>>> Search the list archives at: http://markmail.org/search/?q=ParaView <http://markmail.org/search/?q=ParaView>
>>> 
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview <http://public.kitware.com/mailman/listinfo/paraview>
>>> <YZPlaneInitialForParaview.jpeg>
>> 
>> 
>> 
>> 
>> -- 
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
> 
> 
> 
> 
> -- 
> Cory Quammen
> R&D Engineer
> Kitware, Inc.

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

From cory.quammen at kitware.com  Wed Jul 15 15:26:13 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 15 Jul 2015 15:26:13 -0400
Subject: [Paraview] Custom animation help? (Corrected image)
In-Reply-To: <3654E4A3-D81B-4B91-98A2-CF7BA6210526@udel.edu>
References: <A9BF9A24-AFD8-41DD-8F0C-446AD9B8702C@udel.edu>
 <CAB5Fpx7yjsZEwk5MtCMVuJ5cVtga=zpfF9rK4S42snNkamAO=A@mail.gmail.com>
 <CADwGrVpXTnqgaD_DciowFwe2pc6KC6r332jLwKBnAESWBjkYKQ@mail.gmail.com>
 <D1509E00-6BFE-42F1-8602-ED230B0C5532@udel.edu>
 <CAB5Fpx6Uw5WdtPK4Zd+9GqyUoKUQ=0zoXhkybWg6XU51nmRSzw@mail.gmail.com>
 <5E88E865-62F4-4C6D-84C4-97839317CB59@udel.edu>
 <CAB5Fpx6NP5EKFf4es7mf+2gu0UmfMPBxgexKQmpHOyORznbrZQ@mail.gmail.com>
 <3654E4A3-D81B-4B91-98A2-CF7BA6210526@udel.edu>
Message-ID: <CAB5Fpx7dyVKZw29-p+bzPig6QcQCGp5+uGBuRdnFQuu=9kxZ4Q@mail.gmail.com>

Jesse,

- Load your state file.
- Delete the second VTK file you don't need.
- Save the state

That should do it.

Cory

On Wed, Jul 15, 2015 at 3:20 PM, Jesse Samluk <sevensam at udel.edu> wrote:

> Cory,
>
>   Yes that does the trick, but one more question (and I?ve always wondered
> this). I had 2 vtk files open in the Pipeline browser when I saved the
> ?animation track? state file as discussed, but, when I select load state
> file, it's is now pointing to/asking for two vtk files.
>
>    Any way to adjust this since I want to open only one vtk file, or am I
> stuck?
>
>    Thanks again!
>     Jesse
>
> On Jul 15, 2015, at 1:08 PM, Cory Quammen <cory.quammen at kitware.com>
> wrote:
>
> Jesse,
>
> The animation tracks will be saved in the state file. I just tested
> ParaView to see if that is the case, and it is. Let us know if it isn't
> working for you.
>
> Thanks,
> Cory
>
>
>
> On Wed, Jul 15, 2015 at 11:37 AM, Jesse Samluk <sevensam at udel.edu> wrote:
>
>> Cory,
>>
>> Right, but isn?t that going to ?throw away? the animation ?tracks" I just
>> created?
>>
>> For instance, I have created an animation with a vtk data set I?m working
>> with. Cool.
>>
>> But say I close Paraview, I lose the animation tracks I just created.
>> Right.
>>
>> So how can I save those animation tracks? Is this even possible in
>> Paraview?
>>
>> Thanks!
>> Jesse
>>
>> On Jul 15, 2015, at 10:44 AM, Cory Quammen <cory.quammen at kitware.com>
>> wrote:
>>
>> Jesse,
>>
>> When you load a state file, you get the chance to update the data file
>> paths in the state file. You can use this mechanism to load a different
>> data file with the same state applied to it.
>>
>> HTH,
>> Cory
>>
>> On Tue, Jul 14, 2015 at 5:36 PM, Jesse Samluk <sevensam at udel.edu> wrote:
>>
>>> Dan and Cory,
>>>
>>> Thanks for the guides. I?m getting a lot better at animations now!
>>> Awesome! The guides helped a lot.
>>>
>>>   1 more quick question for you.
>>>
>>>  I know how to save state files, but is there such a way to save the
>>> animation ?state? that I just created in a state file, such that, if I use
>>> that state file, the animation scheme will reappear to other data files
>>> I?ve created?
>>>
>>>    Wasn?t too sure on this.
>>>
>>>  Thanks!
>>>   Jesse
>>>
>>>
>>> On Jul 10, 2015, at 5:34 PM, Dan Lipsa <dan.lipsa at kitware.com> wrote:
>>>
>>> Jesse,
>>> See also the following thread:
>>>
>>>
>>> http://markmail.org/search/?q=+programmimg+the+camera+position+using+python#query:%20programmimg%20the%20camera%20position%20using%20python+page:1+mid:nkm5rmw2hz52egnk+state:results
>>>
>>> On Fri, Jul 10, 2015 at 5:19 PM Cory Quammen <cory.quammen at kitware.com>
>>> wrote:
>>>
>>>> Hi Jesse,
>>>>
>>>> It should be possible to do this. See Chapter 7 of the ParaView User
>>>> Guide [1] or Section 2.13 or the ParaView Tutorial [2] for more information.
>>>>
>>>> [1] http://www.paraview.org/paraview-guide/
>>>> [2] http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf
>>>>
>>>> HTH,
>>>> Cory
>>>>
>>>> On Mon, Jul 6, 2015 at 8:56 AM, Jesse Samluk <sevensam at udel.edu> wrote:
>>>>
>>>>> Greetings all,
>>>>>
>>>>>   I sent this message last week, but errantly sent the .tif image
>>>>> which made it a huge file. The JPG is now attached.
>>>>>
>>>>>    I?m trying to make an animation in Paraview. I took a stab at it
>>>>> before with Paraview, but I recall it as being tedious. Maybe I can get
>>>>> some pointers from the experts.
>>>>>
>>>>>   So, the attached imaged is a cube view of the electromagnetic
>>>>> response over sea ice. What Im trying to do with this animation is two
>>>>> things:
>>>>>
>>>>>   1.) Move the horizontal slice and Y-Z vertical slice (the slice
>>>>> without the tubes) up and down, and side to side, respectively, such that
>>>>> as if you selected the particular slide in the Pipeline browser, you could
>>>>> drag the slice in question and move it manually to see the different
>>>>> responses. Therefore I?m trying to automate it.
>>>>>
>>>>>   2.) Rotate it about the z-axis 5 degrees (to about 180) at each
>>>>> iteration and return, then rotate it 5 degrees at each iteration about the
>>>>> y-axis (till about 45 degrees) and return. These rotations will occur while
>>>>> ?action item" 1 is happening.
>>>>>
>>>>>    Any thoughts/suggestions?
>>>>>
>>>>>     Thanks!
>>>>>     Jesse
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Cory Quammen
>>>> R&D Engineer
>>>> Kitware, Inc.
>>>>  _______________________________________________
>>>> 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
>>>>
>>> <YZPlaneInitialForParaview.jpeg>
>>>
>>>
>>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>>
>>
>>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/bcb68bee/attachment.html>

From cory.quammen at kitware.com  Wed Jul 15 15:28:46 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 15 Jul 2015 15:28:46 -0400
Subject: [Paraview] Contour Plots
In-Reply-To: <68AC123ECB4AC54DB8876E4D6A3EED966E2DC003@mn05svcwem002.atk.com>
References: <68AC123ECB4AC54DB8876E4D6A3EED966E2DC003@mn05svcwem002.atk.com>
Message-ID: <CAB5Fpx59We8-2W5qjJx16CSG+zC=FCg=SgOeKftKA14c0xrDmg@mail.gmail.com>

Andy,

I don't think there is a way to do this with a single Contour filter. If I
understand what you want correctly, you could do it with two Contour
filters where one has the isovalues for every Nth contour where you want
black lines and another Contour filter for all the other contour values.
Then just change the color in the Display properties for each Contour
filter appropriately.

Cory

On Wed, Jul 15, 2015 at 3:09 PM, Robertson, Andrew <
andrew.robertson at orbitalatk.com> wrote:

>  Folks,
>
> New to paraview, but making some progress.
>
> One thing I have not found a way to make a countour plot where there is a
> black line separating every Nth contour level.
>
> Manual is not that much help
>
> Can this be done directly with the baseline tool?
>
> Thanks
>
> ANdy
>
>
>
>
>
> Andrew Robertson P.E.
>
> CFD Analyst
>
>
>
> GASL Operations
>
> Tactical Propulsion and Controls
>
> ATK
>
> 77 Raynor Avenue
>
> Ronkokoma NY 11779
>
>
>
> Phone:  631-676-8955 <631-737-6100%20Ext%20190>  <- *NOTE NEW Number*
>
> Fax:  631-588-7023
>
> www.atk.com
>
>
>
>  !! Knowledge and Thoroughness Baby !!
>
>        Happiness is conserving mass
>
>
>
> ------------------------------
> Notice: This e-mail is intended solely for use of the individual or entity
> to which it is addressed and may contain information that is proprietary,
> privileged and exempt from disclosure under applicable law. If the reader
> is not the intended recipient or agent responsible for delivering the
> message to the intended recipient, you are hereby notified that any
> dissemination, distribution or copying of this communication is strictly
> prohibited. This communication may also contain data subject to U.S. export
> laws. If so, that data subject to the International Traffic in Arms
> Regulation cannot be disseminated, distributed or copied to foreign
> nationals, residing in the U.S. or abroad, absent the express prior
> approval of the U.S. Department of State. If you have received this
> communication in error, please notify the sender by reply e-mail and
> destroy the e-mail message and any physical copies made of the
> communication. Thank you.
> ********** **********
>
> _______________________________________________
> 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
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/fcdea0ae/attachment.html>

From sevensam at udel.edu  Wed Jul 15 15:31:19 2015
From: sevensam at udel.edu (Jesse Samluk)
Date: Wed, 15 Jul 2015 15:31:19 -0400
Subject: [Paraview] Custom animation help? (Corrected image)
In-Reply-To: <CAB5Fpx7dyVKZw29-p+bzPig6QcQCGp5+uGBuRdnFQuu=9kxZ4Q@mail.gmail.com>
References: <A9BF9A24-AFD8-41DD-8F0C-446AD9B8702C@udel.edu>
 <CAB5Fpx7yjsZEwk5MtCMVuJ5cVtga=zpfF9rK4S42snNkamAO=A@mail.gmail.com>
 <CADwGrVpXTnqgaD_DciowFwe2pc6KC6r332jLwKBnAESWBjkYKQ@mail.gmail.com>
 <D1509E00-6BFE-42F1-8602-ED230B0C5532@udel.edu>
 <CAB5Fpx6Uw5WdtPK4Zd+9GqyUoKUQ=0zoXhkybWg6XU51nmRSzw@mail.gmail.com>
 <5E88E865-62F4-4C6D-84C4-97839317CB59@udel.edu>
 <CAB5Fpx6NP5EKFf4es7mf+2gu0UmfMPBxgexKQmpHOyORznbrZQ@mail.gmail.com>
 <3654E4A3-D81B-4B91-98A2-CF7BA6210526@udel.edu>
 <CAB5Fpx7dyVKZw29-p+bzPig6QcQCGp5+uGBuRdnFQuu=9kxZ4Q@mail.gmail.com>
Message-ID: <A36EE541-B8B0-4BAF-A3DD-2046A86D95B0@udel.edu>

Paraview for Dummies question - it won?t let me delete that other VTK file in the Pipeline browser (grayed out).

There?s only an option for delete all (yikes!). Any other suggestions?
> On Jul 15, 2015, at 3:26 PM, Cory Quammen <cory.quammen at kitware.com> wrote:
> 
> Jesse,
> 
> - Load your state file.
> - Delete the second VTK file you don't need.
> - Save the state
> 
> That should do it.
> 
> Cory
> 
> On Wed, Jul 15, 2015 at 3:20 PM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
> Cory,
> 
>   Yes that does the trick, but one more question (and I?ve always wondered this). I had 2 vtk files open in the Pipeline browser when I saved the ?animation track? state file as discussed, but, when I select load state file, it's is now pointing to/asking for two vtk files. 
> 
>    Any way to adjust this since I want to open only one vtk file, or am I stuck?
> 
>    Thanks again!
>     Jesse
> 
>> On Jul 15, 2015, at 1:08 PM, Cory Quammen <cory.quammen at kitware.com <mailto:cory.quammen at kitware.com>> wrote:
>> 
>> Jesse,
>> 
>> The animation tracks will be saved in the state file. I just tested ParaView to see if that is the case, and it is. Let us know if it isn't working for you.
>> 
>> Thanks,
>> Cory
>> 
>> 
>> 
>> On Wed, Jul 15, 2015 at 11:37 AM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
>> Cory,
>> 
>> Right, but isn?t that going to ?throw away? the animation ?tracks" I just created?
>> 
>> For instance, I have created an animation with a vtk data set I?m working with. Cool.
>> 
>> But say I close Paraview, I lose the animation tracks I just created. Right.
>> 
>> So how can I save those animation tracks? Is this even possible in Paraview?
>> 
>> Thanks!
>> Jesse
>> 
>>> On Jul 15, 2015, at 10:44 AM, Cory Quammen <cory.quammen at kitware.com <mailto:cory.quammen at kitware.com>> wrote:
>>> 
>>> Jesse,
>>> 
>>> When you load a state file, you get the chance to update the data file paths in the state file. You can use this mechanism to load a different data file with the same state applied to it.
>>> 
>>> HTH,
>>> Cory
>>> 
>>> On Tue, Jul 14, 2015 at 5:36 PM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
>>> Dan and Cory,
>>> 
>>> Thanks for the guides. I?m getting a lot better at animations now! Awesome! The guides helped a lot.
>>> 
>>>   1 more quick question for you.
>>> 
>>>  I know how to save state files, but is there such a way to save the animation ?state? that I just created in a state file, such that, if I use that state file, the animation scheme will reappear to other data files I?ve created?
>>> 
>>>    Wasn?t too sure on this.
>>> 
>>>  Thanks!
>>>   Jesse
>>>   
>>>> On Jul 10, 2015, at 5:34 PM, Dan Lipsa <dan.lipsa at kitware.com <mailto:dan.lipsa at kitware.com>> wrote:
>>>> 
>>>> Jesse,
>>>> See also the following thread:
>>>> 
>>>> http://markmail.org/search/?q=+programmimg+the+camera+position+using+python#query:%20programmimg%20the%20camera%20position%20using%20python+page:1+mid:nkm5rmw2hz52egnk+state:results <http://markmail.org/search/?q=+programmimg+the+camera+position+using+python#query:%20programmimg%20the%20camera%20position%20using%20python+page:1+mid:nkm5rmw2hz52egnk+state:results>
>>>> 
>>>> On Fri, Jul 10, 2015 at 5:19 PM Cory Quammen <cory.quammen at kitware.com <mailto:cory.quammen at kitware.com>> wrote:
>>>> Hi Jesse,
>>>> 
>>>> It should be possible to do this. See Chapter 7 of the ParaView User Guide [1] or Section 2.13 or the ParaView Tutorial [2] for more information.
>>>> 
>>>> [1] http://www.paraview.org/paraview-guide/ <http://www.paraview.org/paraview-guide/>
>>>> [2] http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf <http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf>
>>>> 
>>>> HTH,
>>>> Cory
>>>> 
>>>> On Mon, Jul 6, 2015 at 8:56 AM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
>>>> Greetings all,
>>>> 
>>>>   I sent this message last week, but errantly sent the .tif image which made it a huge file. The JPG is now attached.
>>>> 
>>>>    I?m trying to make an animation in Paraview. I took a stab at it before with Paraview, but I recall it as being tedious. Maybe I can get some pointers from the experts.
>>>> 
>>>>   So, the attached imaged is a cube view of the electromagnetic response over sea ice. What Im trying to do with this animation is two things:
>>>> 
>>>>   1.) Move the horizontal slice and Y-Z vertical slice (the slice without the tubes) up and down, and side to side, respectively, such that as if you selected the particular slide in the Pipeline browser, you could drag the slice in question and move it manually to see the different responses. Therefore I?m trying to automate it.
>>>> 
>>>>   2.) Rotate it about the z-axis 5 degrees (to about 180) at each iteration and return, then rotate it 5 degrees at each iteration about the y-axis (till about 45 degrees) and return. These rotations will occur while ?action item" 1 is happening.
>>>> 
>>>>    Any thoughts/suggestions?
>>>> 
>>>>     Thanks!
>>>>     Jesse
>>>> 
>>>> _______________________________________________
>>>> Powered by www.kitware.com <http://www.kitware.com/>
>>>> 
>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html <http://www.kitware.com/opensource/opensource.html>
>>>> 
>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
>>>> 
>>>> Search the list archives at: http://markmail.org/search/?q=ParaView <http://markmail.org/search/?q=ParaView>
>>>> 
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://public.kitware.com/mailman/listinfo/paraview <http://public.kitware.com/mailman/listinfo/paraview>
>>>> 
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> Cory Quammen
>>>> R&D Engineer
>>>> Kitware, Inc.
>>>> _______________________________________________
>>>> Powered by www.kitware.com <http://www.kitware.com/>
>>>> 
>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html <http://www.kitware.com/opensource/opensource.html>
>>>> 
>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
>>>> 
>>>> Search the list archives at: http://markmail.org/search/?q=ParaView <http://markmail.org/search/?q=ParaView>
>>>> 
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://public.kitware.com/mailman/listinfo/paraview <http://public.kitware.com/mailman/listinfo/paraview>
>>>> <YZPlaneInitialForParaview.jpeg>
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Cory Quammen
>>> R&D Engineer
>>> Kitware, Inc.
>> 
>> 
>> 
>> 
>> -- 
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
> 
> 
> 
> 
> -- 
> Cory Quammen
> R&D Engineer
> Kitware, Inc.

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

From psavidge0 at lbl.gov  Wed Jul 15 15:32:28 2015
From: psavidge0 at lbl.gov (Patrick Savidge)
Date: Wed, 15 Jul 2015 12:32:28 -0700
Subject: [Paraview]  Output data across all timesteps with Python
Message-ID: <CACPGBqHm20CiV6MEheDFmA7VYpenJZzgk_B5sXXZx8DnPFi-KQ@mail.gmail.com>

Hello Everyone,

I am trying to write a python script to output data for each time step. I
know to use the following script to save data for one time step:

>>> writer = CreateWriter(".../foo.csv", source)>>> writer.FieldAssociation = "Points" # or "Cells">>> writer.UpdatePipeline()>>> del writer


I'm curious how I may do this for every time step?

Thank you for your help,

Patrick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/3354bf56/attachment.html>

From carlos.gbaena at gmail.com  Wed Jul 15 15:32:47 2015
From: carlos.gbaena at gmail.com (=?utf-8?Q?Carlos_Garc=C3=ADa_Baena?=)
Date: Wed, 15 Jul 2015 21:32:47 +0200
Subject: [Paraview] Pipeline's filters and multiblock order
Message-ID: <7C93ECB5-86A2-463A-988A-BF55929C49F4@gmail.com>

Hello,

I?m working with Fluent and exporting the results like an Ensight case. When I open this case in ParaView, I get all the mesh's zones like blocks and I can hide and show them with the multiblock inspector utility. Later I use a short Python's script that I found in the wiki, which creates a Filter in the pipeline from each block (http://www.paraview.org/Wiki/ParaView/Python/Extracting_Multiple_Blocks <http://www.paraview.org/Wiki/ParaView/Python/Extracting_Multiple_Blocks>).

My problem is that I have a lot of mesh?s zones and ParaView sorts them in some strange manner that I really don?t understand. I want to have them sort by name, alphabetically. Is there any way to do this??

Best regards and thanks for your time.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/b76c4c50/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Jul 15 16:16:36 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 15 Jul 2015 20:16:36 +0000
Subject: [Paraview] Pipeline's filters and multiblock order
In-Reply-To: <7C93ECB5-86A2-463A-988A-BF55929C49F4@gmail.com>
References: <7C93ECB5-86A2-463A-988A-BF55929C49F4@gmail.com>
Message-ID: <CADHSJjBiGhSQzSGDX3+b2jFnvJq0SGioxXMpoPMMMRimMDV2TA@mail.gmail.com>

The "Pipeline Browser" shows the filters in pipeline order (or the order
they are created in). This can't be changed, I am afraid. BTW, rather that
using that script, you can use the "Extract Block" filter to extract blocks
of your choice if you're only interested in a few blocks (or few groups of
blocks). That may make it easier to use. In the "Block Indices" widget for
the Extract Block filter, you can use Ctrl+F (or Cmd+F) to search for a
block by name.

Utkarsh

On Wed, Jul 15, 2015 at 3:33 PM Carlos Garc?a Baena <carlos.gbaena at gmail.com>
wrote:

> Hello,
>
> I?m working with Fluent and exporting the results like an Ensight case.
> When I open this case in ParaView, I get all the mesh's zones like blocks
> and I can hide and show them with the multiblock inspector utility. Later I
> use a short Python's script that I found in the wiki, which creates a
> Filter in the pipeline from each block (
> http://www.paraview.org/Wiki/ParaView/Python/Extracting_Multiple_Blocks).
>
> My problem is that I have a lot of mesh?s zones and ParaView sorts them in
> some strange manner that I really don?t understand. I want to have them
> sort by name, alphabetically. Is there any way to do this??
>
> Best regards and thanks for your time.
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/c657f19e/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Jul 15 16:18:53 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 15 Jul 2015 20:18:53 +0000
Subject: [Paraview] Output data across all timesteps with Python
In-Reply-To: <CACPGBqHm20CiV6MEheDFmA7VYpenJZzgk_B5sXXZx8DnPFi-KQ@mail.gmail.com>
References: <CACPGBqHm20CiV6MEheDFmA7VYpenJZzgk_B5sXXZx8DnPFi-KQ@mail.gmail.com>
Message-ID: <CADHSJjATQOqzcgKYkdoa9DuEH2VsBd6eC8gDWMH3S+vqh1EDnw@mail.gmail.com>

If you know the timestep values you're interested in, you can do the
following:

for t in [0, 0.001, 0.002]:
  writer = CreateWriter(".../foo_%d.csv" % t, source)
  writer.FieldAssociation = "Points" # or "Cells"
  writer.UpdatePipeline(t)
  del writer

On Wed, Jul 15, 2015 at 3:32 PM Patrick Savidge <psavidge0 at lbl.gov> wrote:

> Hello Everyone,
>
> I am trying to write a python script to output data for each time step. I
> know to use the following script to save data for one time step:
>
> >>> writer = CreateWriter(".../foo.csv", source)>>> writer.FieldAssociation = "Points" # or "Cells">>> writer.UpdatePipeline()>>> del writer
>
>
> I'm curious how I may do this for every time step?
>
> Thank you for your help,
>
> Patrick
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/e0908eca/attachment.html>

From marie.kajan at gmail.com  Wed Jul 15 20:03:10 2015
From: marie.kajan at gmail.com (Marie Kajan)
Date: Wed, 15 Jul 2015 20:03:10 -0400
Subject: [Paraview] Transforming a spherical slice into a map projection
Message-ID: <CAK3vnGc2pHaxZXhGtto8JzOo6Nu_UL84+rEMES6z5-x6Ei+=bw@mail.gmail.com>

I'm a new user and am having difficulty navigating Paraview. I would really
appreciate any pointers!

I'm using code called ASPECT (aspect.dealii.org) to generate models of the
Earth's interior. My data are unstructured grids that contain different
data arrays: velocity, temperature, etc. I hope that makes sense. I have a
spherical volume, essentially. I know how to play around with the basic
filters, and I'm able to take spherical slices which represent
velocity/temperature/etc. fields at different depths in the Earth.

But, I'm not sure how to "flatten" these slices into a map projection (for
example, a simple rectangle with latitude-longitude axes). Most tutorials
don't deal with VTK inputs and I'm not familiar enough with Paraview to
figure out my own script.

Thanks!

Marie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/774285a3/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Jul 15 22:41:51 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 15 Jul 2015 22:41:51 -0400
Subject: [Paraview] Transforming a spherical slice into a map projection
In-Reply-To: <CAK3vnGc2pHaxZXhGtto8JzOo6Nu_UL84+rEMES6z5-x6Ei+=bw@mail.gmail.com>
References: <CAK3vnGc2pHaxZXhGtto8JzOo6Nu_UL84+rEMES6z5-x6Ei+=bw@mail.gmail.com>
Message-ID: <CADHSJjAZmDV+7QY7VqAEMxWtumyDK08fGyjpWT8T-JwVY8y4og@mail.gmail.com>

Marie,

Do you have a sample dataset? That'll make it easier to determine the
filters etc. you can apply.

Utkarsh

On Wed, Jul 15, 2015 at 8:03 PM, Marie Kajan <marie.kajan at gmail.com> wrote:
> I'm a new user and am having difficulty navigating Paraview. I would really
> appreciate any pointers!
>
> I'm using code called ASPECT (aspect.dealii.org) to generate models of the
> Earth's interior. My data are unstructured grids that contain different data
> arrays: velocity, temperature, etc. I hope that makes sense. I have a
> spherical volume, essentially. I know how to play around with the basic
> filters, and I'm able to take spherical slices which represent
> velocity/temperature/etc. fields at different depths in the Earth.
>
> But, I'm not sure how to "flatten" these slices into a map projection (for
> example, a simple rectangle with latitude-longitude axes). Most tutorials
> don't deal with VTK inputs and I'm not familiar enough with Paraview to
> figure out my own script.
>
> Thanks!
>
> Marie
>
> _______________________________________________
> 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
>

From eric.g.younkin at noaa.gov  Wed Jul 15 23:02:25 2015
From: eric.g.younkin at noaa.gov (Eric Younkin - NOAA Federal)
Date: Wed, 15 Jul 2015 23:02:25 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAOqyOuGT2uONXRjPd80bJOBdnhugTMyyUCHGn6s8H4Aw+i1wOg@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <mo2q49$4gt$1@ger.gmane.org>
 <CAOqyOuGT2uONXRjPd80bJOBdnhugTMyyUCHGn6s8H4Aw+i1wOg@mail.gmail.com>
Message-ID: <CAFe6qKgK_grq0Vzo0kF8NgiGxU_4T9_6jQrfij3=yZr9y27CEQ@mail.gmail.com>

Casey,

I managed to build from source, Paraview 4.3.1 in VS2013.  It looks like my
problem had to do with ZLIB and how I set the cmake parameters.  Also had
to change the Paraview project subsystem type from windows to console.
This doesn't make a whole lot of sense to me, but it did get it working.

Now when I run Paraview.exe, I get the following output messages on startup:

QWindowsWindow::setGeometryDp: Unable to set geometry 1920x1017+4+23 on
QWidgetWindow/'pqClientMainWindowWindow'. Resulting geometry: 1370x753+4+23
(frame: 4, 23, 4, 4, custom margin: 0, 0, 0, 0, minimum size: 471x407,
maximum size: 16777215x16777215). (qwindowswindow.cpp:1323, void __cdecl
QWindowsWindow::setGeometryDp(const class QRect &))

Is this something I should be concerned about?  Some kind of resolution
issue?  I haven't seen it on the install I have using the binaries from the
Paraview site.

Thanks,
Eric

On Tue, Jul 14, 2015 at 1:39 PM, Casey Goodlett <casey.goodlett at kitware.com>
wrote:

> Luca,
>
> You should be able to use a more recent ParaView.  If you run across
> problems with the build you can ask here.  It should work, but you may
> encounter some problems.  I believe I tested as recently as paraview 4.2
>
> On Tue, Jul 14, 2015 at 7:00 AM, Luca Morandini <lmorandini at ieee.org>
> wrote:
>
>> On 10/07/15 00:39, Casey Goodlett wrote:
>>
>>> Hi Eric,
>>>
>>> Thanks for your interest in the PCL plugin, I have used the plugin more
>>> recently
>>> than PCL 1.5.1.  I last tested with ParaView 4.1 and PCL master (from
>>> around
>>> February of this year).
>>>
>>
>> Apologies for the interruption, but I tried to build the PCL plugin
>> following the instructions [1] against an old version of ParaView, and run
>> into problems (see my other post today),  but then I noticed this thread
>> and realized that I may try to build it against a more recent version of
>> ParaView: will it work following the dame instructions, as provided by  or
>> some extra care is needed?
>>
>> Regards,
>>
>> [1]
>> http://www.paraview.org/Wiki/ParaView/PCL_Plugin/Download_And_Build_Instructions
>>
>> Luca Morandini
>> Data Architect - AURIN project
>> Melbourne eResearch Group
>> Department of Computing and Information Systems
>> University of Melbourne
>> Tel. +61 03 903 58 380
>> Skype: lmorandini
>>
>>
>> _______________________________________________
>> 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
>>
>
>
>
> --
> Casey B Goodlett, PhD
> Technical Leader
> Kitware, Inc. - North Carolina Office
> http://www.kitware.com
> (919) 969-6990 x310
>
> _______________________________________________
> 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
>
>


-- 
Eric Younkin LTJG/NOAA
HSTP Liaison - East
Marine Operations Center - Atlantic
439 W York St
Norfolk, VA 23510
Cell: 828-331-8197
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150715/dd2e9dd9/attachment.html>

From lmorandini at ieee.org  Thu Jul 16 00:31:40 2015
From: lmorandini at ieee.org (Luca Morandini)
Date: Thu, 16 Jul 2015 14:31:40 +1000
Subject: [Paraview] Compilation problem of ParaView 3.14.1 on Ubuntu
	14.04
In-Reply-To: <CAFzjYVpax_BsYW3M94FuV+08AaG-Nf3qEW5zdTmOKVYUVTUuFQ@mail.gmail.com>
References: <mo2g4i$4io$1@ger.gmane.org>
 <CAFzjYVpax_BsYW3M94FuV+08AaG-Nf3qEW5zdTmOKVYUVTUuFQ@mail.gmail.com>
Message-ID: <mo7c3c$ftj$1@ger.gmane.org>

On 15/07/15 04:19, Robert Maynard wrote:
>
> Can you send your CMakeError.log from the build directory? This exact
> failure is unexpected.

Thanks Robert for taking the time to answer my post; however, I've found out, from 
the "PCL Plugin" thread, that a newer version of ParaView can be used to build the 
PCL plugin, and, many hours later, I was able to finally compile ParaView 4 on 
Ubuntu 14.04.

Thanks again,

Luca Morandini
Data Architect - AURIN project
Melbourne eResearch Group
Department of Computing and Information Systems
University of Melbourne
Tel. +61 03 903 58 380
Skype: lmorandini


From rajphysics.mon at gmail.com  Thu Jul 16 00:34:12 2015
From: rajphysics.mon at gmail.com (Raj Kumar Manna)
Date: Thu, 16 Jul 2015 10:04:12 +0530
Subject: [Paraview] paraview python script : Delete(renderView1) does
 not free memory
In-Reply-To: <CADHSJjCNF2u_3rzrLne0pkt9wpuU_U=RvZa8dyy_vLDKamnBnw@mail.gmail.com>
References: <CANt3wQti+7nAcLhyCaD9yiaNgsAS2cJXOgpBJA5bZ5nhNrniUQ@mail.gmail.com>
 <CADHSJjCNF2u_3rzrLne0pkt9wpuU_U=RvZa8dyy_vLDKamnBnw@mail.gmail.com>
Message-ID: <CANt3wQvO38h0pTbDSs4fLyj2hgNrXZbWsiOoCP_3w-gw2nm=0Q@mail.gmail.com>

Thanks Utkarsh. This script solved my problem.

On Wed, Jul 15, 2015 at 7:44 PM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> Delete() will only remove the render view, not all other proxies that were
> created as part of the state loading operation. The following script should
> do the trick:
>
>
> --------------------------------------------------------------------------------
> from paraview.simple import *
>
> def ResetSession():
>     pxm = servermanager.ProxyManager()
>     pxm.UnRegisterProxies()
>     del pxm
>     Disconnect()
>     Connect()
>
> for i in range(0, 10):
>     ResetSession()
>     servermanager.LoadState("/tmp/sample.pvsm")
>     renderView=SetActiveView(GetRenderView())
>     Render()
>
> --------------------------------------------------------------------------------
>
> Utkarsh
>
>
> On Wed, Jul 15, 2015 at 12:52 AM Raj Kumar Manna <rajphysics.mon at gmail.com>
> wrote:
>
>> Dear All,
>>
>> I am trying to load multiple state files by running a python script with
>> python shell. The script is the following
>>
>> #### import the simple module from the paraview
>> from paraview.simple import *
>>
>> for time in range(0,200):
>>         renderView1 = GetActiveViewOrCreate('RenderView')
>>
>>         # destroy renderView1
>>         Delete(renderView1)
>>         del renderView1
>>
>>         filename = 'filepath/filename-%s.pvsm' % time
>>         servermanager.LoadState(filename)
>>         renderView=SetActiveView(GetRenderView())
>>         Render()
>>         # get layout
>>         viewLayout = GetLayout()
>>
>>         # save screenshot
>>         SaveScreenshot('filepath/filename-%s.png' % time,
>> layout=viewLayout, magnification=3, quality=100)
>>
>> I was monitoring the memory used by machine, after some time steps the
>> memory used by the machine is whole RAM. Can anybody tell me what I am
>> doing wrong here.
>>
>> I appreciate your time and support.
>>
>>
>> Thanks
>> Raj
>>
>>
>>
>> --
>> ##################################################################
>> Raj Kumar Manna
>> Complex Fluid & Biological Physics Lab
>> IIT Madras
>>
>> Ph. No. 8144637401
>>
>> alternate email: raj at physics.iitm.ac.in <rajphysics.mon at 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
>>
>


-- 
##################################################################
Raj Kumar Manna
Complex Fluid & Biological Physics Lab
IIT Madras

Ph. No. 8144637401

alternate email: raj at physics.iitm.ac.in <rajphysics.mon at gmail.com>
####################################################################
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/97707299/attachment.html>

From lmorandini at ieee.org  Thu Jul 16 00:46:44 2015
From: lmorandini at ieee.org (Luca Morandini)
Date: Thu, 16 Jul 2015 14:46:44 +1000
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAOqyOuGT2uONXRjPd80bJOBdnhugTMyyUCHGn6s8H4Aw+i1wOg@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <mo2q49$4gt$1@ger.gmane.org>
 <CAOqyOuGT2uONXRjPd80bJOBdnhugTMyyUCHGn6s8H4Aw+i1wOg@mail.gmail.com>
Message-ID: <mo7cvk$ria$1@ger.gmane.org>

On 15/07/15 03:39, Casey Goodlett wrote:
>
> You should be able to use a more recent ParaView.  If you run across problems with
> the build you can ask here.  It should work, but you may encounter some problems.
> I believe I tested as recently as paraview 4.2

Thanks Casey for your answer, which led me to successfully compile, ParaView 4.2 
and PCL 1.7.0. However, it looks the PAraView PCL plugin expects an older version 
of PCL:

[ 27%] Building CXX object CMakeFiles/vtkPCLFilters.dir/qrc_vtkPCLFilters.cxx.o
<command-line>:0:15: warning: missing whitespace after the macro name [enabled by 
default]
[ 28%] Building CXX object 
CMakeFiles/vtkPCLFilters.dir/pqPCLOpenNISourceImplementation.cxx.o
<command-line>:0:15: warning: missing whitespace after the macro name [enabled by 
default]
[ 30%] Building CXX object 
CMakeFiles/vtkPCLFilters.dir/moc_pqPCLOpenNISourceImplementation.cxx.o
<command-line>:0:15: warning: missing whitespace after the macro name [enabled by 
default]
[ 31%] Building CXX object CMakeFiles/vtkPCLFilters.dir/moc_pqPCLOpenNISource.cxx.o
<command-line>:0:15: warning: missing whitespace after the macro name [enabled by 
default]
[ 33%] Building CXX object CMakeFiles/vtkPCLFilters.dir/vtkAnnotateOBBs.cxx.o
<command-line>:0:15: warning: missing whitespace after the macro name [enabled by 
default]
/home/lmorandini/PointCloudLibraryPlugin-v1.0/vtkAnnotateOBBs.cxx: In member 
function ?virtual int vtkAnnotateOBBs::RequestData(vtkInformation*, 
vtkInformationVector**, vtkInformationVector*)?:
/home/lmorandini/PointCloudLibraryPlugin-v1.0/vtkAnnotateOBBs.cxx:126:16: error: 
?class vtkThresholdPoints? has no member named ?SetInput?
      threshold->SetInput(inputCopy);
                 ^
make[2]: *** [CMakeFiles/vtkPCLFilters.dir/vtkAnnotateOBBs.cxx.o] Error 1
make[1]: *** [CMakeFiles/vtkPCLFilters.dir/all] Error 2
make: *** [all] Error 2


Any suggestions on how to fix it (I already tried to build PCL 1.6 on Ubuntu 
14.04, to no avail)?

Regards,

Luca Morandini
Data Architect - AURIN project
Melbourne eResearch Group
Department of Computing and Information Systems
University of Melbourne
Tel. +61 03 903 58 380
Skype: lmorandini


From vishnubabu.c at gmail.com  Thu Jul 16 05:22:44 2015
From: vishnubabu.c at gmail.com (Vishnu)
Date: Thu, 16 Jul 2015 09:22:44 +0000 (UTC)
Subject: [Paraview]
	=?utf-8?q?ParaView_3=2E98_contour_filter_=22Compute_sc?=
	=?utf-8?q?alars=22=09misbehaves?=
References: <50e7469e.8d35320a.3962.1885@mx.google.com>
 <CAMaOp+FeUC0aCm7o_2VykMZt+JJc_wGTOM1n8G4kkEPpV0xDHw@mail.gmail.com>
Message-ID: <loom.20150716T112048-234@post.gmane.org>

Hi Russel,
The link in which you said the file is stored is not valid, did you move to
anywhere? can you provide the link of it?


From ganesh.iitm at gmail.com  Thu Jul 16 09:06:49 2015
From: ganesh.iitm at gmail.com (Ganesh Vijayakumar)
Date: Thu, 16 Jul 2015 13:06:49 +0000
Subject: [Paraview] Paraview server using off-screen rendering
Message-ID: <CAFtK+evM=vwqHoeX4-4hrwzTG3u8wphkheMuiPMzFLiVZ=Ku2g@mail.gmail.com>

Hello,

  I'm trying to install paraview-4.3.1 on a cluster with off-screen
rendering. I'm following instructions on the wiki. I installed mesa-10.6.0
and included that


I get a whole bunch of warnings after i do ccmake like these.

 WARNING: Target "vtkParallelMPI" requests linking to directory
"/opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/lib/".  Targets may link only
 to libraries.  CMake is dropping the item.

Probably about 50 or so of these with various vtk classes saying the same
thing. I'm trying to use the system's cray-mpich2 library. Hence I use the
MPI_CXX_NO_INTERROGATE and  MPI_C_NO_INTERROGATE variables. However, I
realize that MPI_LIBRARY currently points to a directory. I'm not sure if
this is even relevant. If it is, I don't know how to get rid of it. I tried
replacing this variable with a semicolon separated list of individual files
inside the MPI library to link it to. But on performing configure it gives
the same set of warnings and worse.. it reverts back to the original
setting of pointing to a directory.

If I ignore these and continue ahead with the make, this is what I get.

Scanning dependencies of target H5detect
[  3%] Building C object
VTK/ThirdParty/hdf5/vtkhdf5/src/CMakeFiles/H5detect.dir/H5detect.c.o
Linking CXX shared library ../../../../lib/libvtkjsoncpp-pv4.3.so
[  3%] Built target vtkjsoncpp
Linking C executable ../../../../../bin/H5detect
Scanning dependencies of target H5make_libsettings
[  4%] Building C object
VTK/ThirdParty/hdf5/vtkhdf5/src/CMakeFiles/H5make_libsettings.dir/H5make_libsettings.c.o
Linking C executable ../../../../../bin/H5make_libsettings
/usr/lib/../lib64/libpthread.a(lowlevellock.o): In function
`__lll_lock_wait_private':
/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:81:
multiple definition of `__lll_lock
_wait_private'
/usr/lib/../lib64/libc.a(libc-lowlevellock.o):/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowleve
llock.S:81: first defined here
/usr/lib/../lib64/libpthread.a(lowlevellock.o): In function
`__lll_unlock_wake_private':
/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:323:
multiple definition of `__lll_unl
ock_wake_private'
/usr/lib/../lib64/libc.a(libc-lowlevellock.o):/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowleve
llock.S:323: first defined here
/usr/bin/ld: link errors found, deleting executable
`../../../bin/vtkWrapPythonInit-pv4.3'
collect2: error: ld returned 1 exit status
make[2]: *** [bin/vtkWrapPythonInit-pv4.3] Error 1
make[1]: *** [VTK/Wrapping/Tools/CMakeFiles/vtkWrapPythonInit.dir/all]
Error 2
make[1]: *** Waiting for unfinished jobs....
[  4%] Building C object
VTK/ThirdParty/zlib/vtkzlib/CMakeFiles/vtkzlib.dir/zutil.c.o
Linking C shared library ../../../../lib/libvtkzlib-pv4.3.so
/usr/lib/../lib64/libpthread.a(lowlevellock.o): In function
`__lll_lock_wait_private':
/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:81:
multiple definition of `__lll_lock
_wait_private'
/usr/lib/../lib64/libc.a(libc-lowlevellock.o):/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowleve
llock.S:81: first defined here
/usr/lib/../lib64/libpthread.a(lowlevellock.o): In function
`__lll_unlock_wake_private':
/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:323:
multiple definition of `__lll_unl
ock_wake_private'

There's more. But I'm not sure. what exactly the error is. If it's a
problem with HDF5 library, I'm not sure where I need to point to the system
installation. Should I point to a parallel-HDF5 or a serial HDF5? I do need
HDF5 support through XDMF... I guess parallel is better. But I could take
care of that at a later date. I need something (without HDF5 even) working
now.

ganesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/4a5019a8/attachment.html>

From berk.geveci at kitware.com  Thu Jul 16 09:38:58 2015
From: berk.geveci at kitware.com (Berk Geveci)
Date: Thu, 16 Jul 2015 09:38:58 -0400
Subject: [Paraview] Molecular dynamics from lammps
In-Reply-To: <1436852798.517668428@f416.i.mail.ru>
References: <1436279999.571994242@f345.i.mail.ru>
 <1436514441.618845786@f254.i.mail.ru>
 <CAE32kpXwMb6ZWuVZr2AENGQX-Q3Da7uNA+Yj=3CaHQLq1bodyw@mail.gmail.com>
 <1436852798.517668428@f416.i.mail.ru>
Message-ID: <CAE32kpW9hj4bQK6eqvvDT4JDVmhE+naOMs6VyPm7haU2gODZPA@mail.gmail.com>

Sorry Oksana. I have been swamped. I hope to get back to you soon. The
solution will be to use the Python Calculator or Programmable Filter to do
the projection of the points on the plane and threshold based on the
distance. There are instructions on how to use these on the Users' Guide. I
also wrote a number of blogs on this:

http://www.kitware.com/blog/home/user/53

See the earlier blogs on VTK-numpy integration.

Best,
-berk

On Tue, Jul 14, 2015 at 1:46 AM, Oksana <oksana_golovnya at mail.ru> wrote:

> At best it would be to keep atoms that are under a certain distance to the
> plane, however to keep only atoms belonging to the plane is also OK.
> Vectors should be glyphs, one atom with one vector.
> May be it woould help if I attach the file?
>
> Faithfully yours,
> Oksana
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/e7ccd3ba/attachment.html>

From casey.goodlett at kitware.com  Thu Jul 16 10:05:44 2015
From: casey.goodlett at kitware.com (Casey Goodlett)
Date: Thu, 16 Jul 2015 10:05:44 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <mo7cvk$ria$1@ger.gmane.org>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <mo2q49$4gt$1@ger.gmane.org>
 <CAOqyOuGT2uONXRjPd80bJOBdnhugTMyyUCHGn6s8H4Aw+i1wOg@mail.gmail.com>
 <mo7cvk$ria$1@ger.gmane.org>
Message-ID: <CAOqyOuFMFju6ODKyehDU1pDdH1Z=A79wc0iy8KK3m11mziLMPQ@mail.gmail.com>

On Thu, Jul 16, 2015 at 12:46 AM, Luca Morandini <lmorandini at ieee.org>
wrote:

> /home/lmorandini/PointCloudLibraryPlugin-v1.0/vtkAnnotateOBBs.cxx: In
> member function ?virtual int vtkAnnotateOBBs::RequestData(vtkInformation*,
> vtkInformationVector**, vtkInformationVector*)?:
> /home/lmorandini/PointCloudLibraryPlugin-v1.0/vtkAnnotateOBBs.cxx:126:16:
> error: ?class vtkThresholdPoints? has no member named ?SetInput?
>      threshold->SetInput(inputCopy);
>                 ^
> make[2]: *** [CMakeFiles/vtkPCLFilters.dir/vtkAnnotateOBBs.cxx.o] Error 1
> make[1]: *** [CMakeFiles/vtkPCLFilters.dir/all] Error 2
> make: *** [all] Error 2
>

This needs to be updated for VTK 6 and is unrelated to the  PCL version.
You need to checkout the latest version of the plugin from here
https://github.com/Kitware/PCLPlugin where this has been fixed.


-- 
Casey B Goodlett, PhD
Technical Leader
Kitware, Inc. - North Carolina Office
http://www.kitware.com
(919) 969-6990 x310
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/3602cae1/attachment.html>

From cory.quammen at kitware.com  Thu Jul 16 11:14:03 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 16 Jul 2015 11:14:03 -0400
Subject: [Paraview] vtkDoubleArray with >3 components
In-Reply-To: <CAEc4V-bvd0SRk35cuPM7Z9WhoH8WSL=7S_6kr7_Op5aOeoMN6A@mail.gmail.com>
References: <CAEc4V-bvd0SRk35cuPM7Z9WhoH8WSL=7S_6kr7_Op5aOeoMN6A@mail.gmail.com>
Message-ID: <CAB5Fpx6q5_K_ZJNpXtrvNhOYjZQdzGCNxvk8Eo1bvM2tFi0YVQ@mail.gmail.com>

Hi Bruce,

I haven't seen this, but ParaView may be interpreting this array as a
tensor field. Do you have a smallish test data file that you can share that
shows the problem?

Thanks,
Cory

On Sat, Jul 11, 2015 at 11:14 AM, Bruce Jones <bruce.david.jones at gmail.com>
wrote:

> I am creating vtkDoubleArrays based on averaging some input data to a
> reduced set of points. The input data includes various vtk arrays which
> have 1, 3 and 9 components.
>
> After averaging, I am writing the data to c++ arrays, and creating a new
> vtkDoubleArray using the SetArray() function to pass the c++ arrays. This
> works fine for 1 and 3 component arrays, however for the 9 component arrays
> paraview shows that every element is set to 0.
>
> If I hardcode it so that 9 component arrays become 3 component arrays
> (reading only the first 3 components from the input array), then I get the
> correct data for the first 3 components, though I obviously need the other
> 6 components in the end.
>
> Has anyone encountered this before?
>
> Cheers,
> Bruce
>
> _______________________________________________
> 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
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/7c64f75c/attachment.html>

From chuck.atkins at kitware.com  Thu Jul 16 11:23:06 2015
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Thu, 16 Jul 2015 11:23:06 -0400
Subject: [Paraview] Paraview server using off-screen rendering
Message-ID: <CAOXZzG7L4FLP_vsoPY3D1cqUyMdjd-H9T9sK53Teg0yMcpSvGQ@mail.gmail.com>

Hi Ganesh,

WARNING: Target "vtkParallelMPI" requests linking to directory
> "/opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/lib/".  Targets may link only
>  to libraries.  CMake is dropping the item.
>

It looks like you're building with GCC on a Cray.  Are you using gcc
directly or are you using the wrappers provides by the PrgEnv-gnu module?
The CMake FindMPI module should work correctly with the Cray wrappers.  In
that case, cc and CC will work as mpicc and mpiCC, automatically wrapping
the Cray MPI libraries into the compiler args, which the FindMPI module can
detect appropriately.



> If it's a problem with HDF5 library, I'm not sure where I need to point to
> the system installation.
>

If you load the cray-hdf5 module, that will set the HDF5_DIR environment
variable to the correct location.  Unfortunately, CMake uses the HDF5_ROOT
variable instead to look for it so you'll neet to set it accordingly.

If you're using the bash shell, the following sequence should prep your
environment accordingly:

# Start with a pristine environment
module purge
module load modules

# Load the compilers
module load PrgEnv-gnu

# Use the Cray wrappers for the compilers instead of calling gcc and g++
directly
export CC=$(which cc)
export CXX=$(which CC)
export FC=$(which ftn)

# Load the Cray-provided libraries
module load cray-hdf5
module load cray-mpich

# Used by the CMake FindHDF5.cmake module
export HDF5_ROOT=${HDF5_DIR}

Try configuring ParaView starting from that environment.

Out of curiosity, where is the machine located?  We maintain ParaView
installations at many different HPC sites on a range of Cray systems.

- Chuck Atkins
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/1a9edea3/attachment.html>

From ganesh.iitm at gmail.com  Thu Jul 16 12:20:36 2015
From: ganesh.iitm at gmail.com (Ganesh Vijayakumar)
Date: Thu, 16 Jul 2015 16:20:36 +0000
Subject: [Paraview] Paraview server using off-screen rendering
In-Reply-To: <CAOXZzG7L4FLP_vsoPY3D1cqUyMdjd-H9T9sK53Teg0yMcpSvGQ@mail.gmail.com>
References: <CAOXZzG7L4FLP_vsoPY3D1cqUyMdjd-H9T9sK53Teg0yMcpSvGQ@mail.gmail.com>
Message-ID: <CAFtK+evUnwbV_9fC3GwKKx7ss3SQB0QanK4Eygs=NwN6O+JFxg@mail.gmail.com>

Dear Chuck,

  The machine is NICS - Darter -
http://www.nics.tennessee.edu/computing-resources/darter. The last I
checked, there's no paraview module on Darter. Hence my attempt at the
installation.

On Thu, Jul 16, 2015 at 11:23 AM Chuck Atkins <chuck.atkins at kitware.com>
wrote:

> Hi Ganesh,
>
> WARNING: Target "vtkParallelMPI" requests linking to directory
>> "/opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/lib/".  Targets may link only
>>  to libraries.  CMake is dropping the item.
>>
>
> It looks like you're building with GCC on a Cray.  Are you using gcc
> directly or are you using the wrappers provides by the PrgEnv-gnu module?
> The CMake FindMPI module should work correctly with the Cray wrappers.  In
> that case, cc and CC will work as mpicc and mpiCC, automatically wrapping
> the Cray MPI libraries into the compiler args, which the FindMPI module can
> detect appropriately.
>

This is what I have from ccmake window. Does this seem right?

 CMAKE_AR                         /usr/bin/ar
 CMAKE_BUILD_TYPE                 Release
 CMAKE_COLOR_MAKEFILE             ON
 CMAKE_CXX_COMPILER               /opt/cray/craype/2.2.1/bin/CC
 CMAKE_CXX_FLAGS
-L/lustre/medusa/gantech/software/mesa-10.6.0/lib
 CMAKE_CXX_FLAGS_DEBUG            -g
 CMAKE_CXX_FLAGS_MINSIZEREL       -Os -DNDEBUG
 CMAKE_CXX_FLAGS_RELEASE          -O3 -DNDEBUG
 CMAKE_CXX_FLAGS_RELWITHDEBINFO   -O2 -g -DNDEBUG
 CMAKE_C_COMPILER                 /opt/cray/craype/2.2.1/bin/cc
 CMAKE_C_FLAGS
-L/lustre/medusa/gantech/software/mesa-10.6.0/lib
 CMAKE_C_FLAGS_DEBUG              -g
 CMAKE_C_FLAGS_MINSIZEREL         -Os -DNDEBUG
 CMAKE_C_FLAGS_RELEASE            -O3 -DNDEBUG
 CMAKE_C_FLAGS_RELWITHDEBINFO     -O2 -g -DNDEBUG
 CMAKE_EXE_LINKER_FLAGS
-L/lustre/medusa/gantech/software/mesa-10.6.0/lib
 CMAKE_EXE_LINKER_FLAGS_DEBUG
 CMAKE_EXE_LINKER_FLAGS_MINSIZE
 CMAKE_EXE_LINKER_FLAGS_RELEASE
 CMAKE_EXE_LINKER_FLAGS_RELWITH
 CMAKE_EXPORT_COMPILE_COMMANDS    OFF
 CMAKE_Fortran_COMPILER           /opt/gcc/4.9.2/bin/gfortran
 CMAKE_Fortran_FLAGS
 CMAKE_Fortran_FLAGS_DEBUG        -g
 CMAKE_Fortran_FLAGS_MINSIZEREL   -Os
 CMAKE_Fortran_FLAGS_RELEASE      -O3
 CMAKE_Fortran_FLAGS_RELWITHDEB   -O2 -g -DNDEBUG
 CMAKE_HP_PTHREADS                OFF
 CMAKE_INSTALL_PREFIX
/lustre/medusa/gantech/software/Paraview-v4.3.1
 CMAKE_LINKER                     /sw/xc30/xalt/0.5.3-1/sles11.2/bin/ld
 CMAKE_MAKE_PROGRAM               /usr/bin/gmake

 MPIEXEC                          aprun
 MPIEXEC_MAX_NUMPROCS             2
 MPIEXEC_NUMPROC_FLAG             -n
 MPIEXEC_POSTFLAGS
 MPIEXEC_PREFLAGS
 MPI_CXX_COMPILER                 /opt/cray/craype/2.2.1/bin/CC
 MPI_CXX_COMPILE_FLAGS
 MPI_CXX_INCLUDE_PATH
/opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/include
 MPI_CXX_LIBRARIES                /opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/lib/
 MPI_CXX_LINK_FLAGS
 MPI_CXX_NO_INTERROGATE           /opt/cray/craype/2.2.1/bin/CC
 MPI_C_COMPILER                   /opt/cray/craype/2.2.1/bin/cc
 MPI_C_COMPILE_FLAGS
 MPI_C_INCLUDE_PATH
/opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/include
 MPI_C_LIBRARIES                  /opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/lib/
 MPI_C_LINK_FLAGS
 MPI_C_NO_INTERROGATE             /opt/cray/craype/2.2.1/bin/cc
 MPI_EXTRA_LIBRARY                MPI_EXTRA_LIBRARY-NOTFOUND
 MPI_Fortran_COMPILER             /opt/cray/craype/2.2.1/bin/ftn
 MPI_Fortran_COMPILE_FLAGS
 MPI_Fortran_INCLUDE_PATH
 MPI_Fortran_LIBRARIES
 MPI_Fortran_LINK_FLAGS
 MPI_LIBRARY                      /opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/lib



> If it's a problem with HDF5 library, I'm not sure where I need to point to
>> the system installation.
>>
>
> If you load the cray-hdf5 module, that will set the HDF5_DIR environment
> variable to the correct location.  Unfortunately, CMake uses the HDF5_ROOT
> variable instead to look for it so you'll neet to set it accordingly.
>

I don't have much experience with cmake, but can I set additional variables
in the ccmake window? Should this variable show up there asking to be set
if you turn on the advanced mode toggle?


>
> If you're using the bash shell, the following sequence should prep your
> environment accordingly:
>
> # Start with a pristine environment
> module purge
> module load modules
>
> # Load the compilers
> module load PrgEnv-gnu
>
> # Use the Cray wrappers for the compilers instead of calling gcc and g++
> directly
> export CC=$(which cc)
> export CXX=$(which CC)
> export FC=$(which ftn)
>
> # Load the Cray-provided libraries
> module load cray-hdf5
> module load cray-mpich
>
> # Used by the CMake FindHDF5.cmake module
> export HDF5_ROOT=${HDF5_DIR}
>
> Try configuring ParaView starting from that environment.
>

I tried this. I get the same warnings. Any other advice?


>
> Out of curiosity, where is the machine located?  We maintain ParaView
> installations at many different HPC sites on a range of Cray systems.
>
> - Chuck Atkins
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/38a62d42/attachment.html>

From Thomas.Otoole at pinntech.com  Thu Jul 16 12:47:29 2015
From: Thomas.Otoole at pinntech.com (Thomas O'Toole)
Date: Thu, 16 Jul 2015 16:47:29 +0000
Subject: [Paraview] Extract all points inside volume
Message-ID: <4E09FD4309849147BFDAED6FAAC87A956B0D54AF@EP1EXMB004.corp.halliburton.com>

Dear Paraviewers,

I am trying to select and extract all points that lie within a particular volume of my dataset. The volume is irregularly shaped (hence a simple clip is not an option), and created by a 3D Delaunay triangulation. Is there a straightforward way to do this in Paraview? I feel like there must be, but have been drawing a blank so far.

Many thanks,

Tom





----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient.  Any review, use, distribution, or disclosure by others is strictly prohibited.  If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/8c336b4e/attachment.html>

From wascott at sandia.gov  Thu Jul 16 13:14:54 2015
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 16 Jul 2015 17:14:54 +0000
Subject: [Paraview] [EXTERNAL]  Extract all points inside volume
In-Reply-To: <4E09FD4309849147BFDAED6FAAC87A956B0D54AF@EP1EXMB004.corp.halliburton.com>
References: <4E09FD4309849147BFDAED6FAAC87A956B0D54AF@EP1EXMB004.corp.halliburton.com>
Message-ID: <12B8A446-3423-4D7E-8671-55C1D737233D@sandia.gov>

Select points through (i.e., frustum select)?  Then, on the Find Data dialog, Freeze Selection.  Last, Filter/ Extract Selection?

Alan

On Jul 16, 2015, at 10:47 AM, Thomas O'Toole <Thomas.Otoole at pinntech.com<mailto:Thomas.Otoole at pinntech.com>> wrote:

Dear Paraviewers,

I am trying to select and extract all points that lie within a particular volume of my dataset. The volume is irregularly shaped (hence a simple clip is not an option), and created by a 3D Delaunay triangulation. Is there a straightforward way to do this in Paraview? I feel like there must be, but have been drawing a blank so far.

Many thanks,

Tom





________________________________
This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
_______________________________________________
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

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

From cory.quammen at kitware.com  Thu Jul 16 13:38:39 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 16 Jul 2015 13:38:39 -0400
Subject: [Paraview] Orient created vectors
In-Reply-To: <CAM4K3Yd5ANgvKeSDPG-krMBKsAaiVbHcTsp2qtQsCxgY0ehB4w@mail.gmail.com>
References: <CAM4K3YdAJ+XvjbShzT3uJL3ntYwwitjUPdryzrx5pZUOGEa4LQ@mail.gmail.com>
 <CAB5Fpx5ZZb2UQP86on6-YT+Mqx6DfUc3j6K0deo8nTOaY2iHAg@mail.gmail.com>
 <CAM4K3YeSBB+eavXBKA+jUPzTdfASeM-pWRNkOqnBbdD6NcbGow@mail.gmail.com>
 <CAB5Fpx49Pm4tnm_cduJspQXFLzA27R+WXgN8C5XABBsdY3hbfg@mail.gmail.com>
 <CAM4K3YcYe_Eo8jYVWVWuaU3mHssPa=DnSFBjdmK3eyh8tr0RQA@mail.gmail.com>
 <CAB5Fpx5Lgi-yQxwrp43S4goeO40x56P9pFU94OGKWSzN_i+fcw@mail.gmail.com>
 <CAM4K3YdQZDhAqAy--jj6bNFy0VYKkwO-=s7Xz-VY7evJJ=DGJw@mail.gmail.com>
 <CAM4K3Yd5ANgvKeSDPG-krMBKsAaiVbHcTsp2qtQsCxgY0ehB4w@mail.gmail.com>
Message-ID: <CAB5Fpx4rDh4Un-E3BN4wz62AwiEMMNuYoOAxn9CXK+ayoEQQoQ@mail.gmail.com>

Hi Aymeric,

Sorry, I have been swamped.

I just looked at your data. The state file you sent invoked an error in the
Output Window. Indeed, I could see the arrows aligned only with the X axis.

If I load just your data, I have more success. Here's what I did:

- load Test_Set.tp
- Calculator filter
-- Result array name = Velocity
-- express = U*iHat + V*jHat + W*kHat
- Glyph filter
-- Glyph Type = Arrow
-- Vectors = Velocity
-- Glyph Mode = Every Nth Point
-- Stride 300
- color by "GlyphVector"

I get the attached image when doing this.

My suspicion is that an error that occurred somewhere along the way during
your interaction with ParaView, and it has crept into the state file and is
causing a problem with the glyph display. I recommend starting fresh, like
I did, and see if you can get the vectors to point the right way.

Best regards,
Cory

On Mon, Jul 13, 2015 at 3:41 AM, Aymeric NAZE <aymeric.naze at gmail.com>
wrote:

> Hi Cory,
>
> Did you have the time to take a look at my dataset ?
>
> 2015-07-09 17:03 GMT+02:00 Aymeric NAZE <aymeric.naze at gmail.com>:
>
>> Thank you for your reactivity.
>>
>> You will find below a dropbox link to 2 files :
>>
>>    - the dataset : 27.8 Mo
>>    - the state file (ontaining the calculators and glyph) : 261 ko
>>
>>
>> https://www.dropbox.com/sh/fu8mji13ov79crb/AAAFcFvCKccEu-qcP5YZtguPa?dl=0
>>
>>
>> 2015-07-09 16:12 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>>
>>> Hmm, well it does indeed have non-zero Y and Z components. Could you
>>> share this dataset?
>>>
>>> Thanks,
>>> Cory
>>>
>>> On Thu, Jul 9, 2015 at 8:53 AM, Aymeric NAZE <aymeric.naze at gmail.com>
>>> wrote:
>>>
>>>> Information regarding my Result vector field in Data Arrays (under
>>>> "Information" tab in the calculator filter) :
>>>>
>>>>    - *Data Type* : double
>>>>    - *Data Ranges* : [-1.26, 0.01], [-0.01, 0.76], [-0.16, 0.27]
>>>>
>>>>
>>>> 2015-07-09 15:03 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>>>>
>>>>> Can you verify that the second and third components of your Result
>>>>> vector field have a range outside [0, 0]? You can get this information
>>>>> under the Information tab in the Data Arrays table.
>>>>>
>>>>> On Thu, Jul 9, 2015 at 7:56 AM, Aymeric NAZE <aymeric.naze at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Thanks for considering my problem.
>>>>>>
>>>>>> Yes, in the Glyph Filter I have the following *Active Attributes* :
>>>>>>
>>>>>>    - *Scalars *: FF wich is the magnitude in the (x,y) plane
>>>>>>    (calculated with another "calculator" filter : FF=(U^2+V^2)^0.5) : it's the
>>>>>>    length of the arrows I want to display.
>>>>>>
>>>>>>
>>>>>>    - *Vectors *: Result (vectors from the previously described
>>>>>>    calculator)
>>>>>>
>>>>>>
>>>>>> 2015-07-09 14:29 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>>>>>>
>>>>>>> Hi Aymeric,
>>>>>>>
>>>>>>> Did you choose the "Result" array as the "Vectors" property in the
>>>>>>> Properties panel of the Glyph filter?
>>>>>>>
>>>>>>> HTH,
>>>>>>> Cory
>>>>>>>
>>>>>>> On Thu, Jul 9, 2015 at 7:26 AM, Aymeric NAZE <aymeric.naze at gmail.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> I'm using Paraview 4.3.1 (64-bit) to display data from a tecplot
>>>>>>>> format file.
>>>>>>>>
>>>>>>>> Data is points coordinates (x,y,z) and vectors coordinates (u,v,w)
>>>>>>>> for each point.
>>>>>>>>
>>>>>>>>
>>>>>>>>    - I have created vectors with "Calculator" filter (Result =
>>>>>>>>    u*iHat+v*jHat+w*kHat) and it creates vectors with thewanted coordinates (I
>>>>>>>>    can see that in the spreadsheet view)
>>>>>>>>
>>>>>>>>
>>>>>>>>    - Then I made a glyph to display these vectors as arrows.
>>>>>>>>
>>>>>>>> Magnitude is displayed without problem but i did'nt find how to
>>>>>>>> orient correctly the vectors.
>>>>>>>> Whether i check or not the "Orient" feature it doesn't change
>>>>>>>> anything : vectors are always oriented along the x axis...
>>>>>>>>
>>>>>>>> Does anybody can help me on that issue ?
>>>>>>>>
>>>>>>>> Thanks so much in advance.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Aymeric
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Cory Quammen
>>>>>>> R&D Engineer
>>>>>>> Kitware, Inc.
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Cory Quammen
>>>>> R&D Engineer
>>>>> Kitware, Inc.
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Cory Quammen
>>> R&D Engineer
>>> Kitware, Inc.
>>>
>>
>>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/f087033c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Vectors.png
Type: image/png
Size: 116919 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/f087033c/attachment.png>

From chuck.atkins at kitware.com  Thu Jul 16 14:18:38 2015
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Thu, 16 Jul 2015 14:18:38 -0400
Subject: [Paraview] Paraview server using off-screen rendering
In-Reply-To: <CAFtK+evUnwbV_9fC3GwKKx7ss3SQB0QanK4Eygs=NwN6O+JFxg@mail.gmail.com>
References: <CAOXZzG7L4FLP_vsoPY3D1cqUyMdjd-H9T9sK53Teg0yMcpSvGQ@mail.gmail.com>
 <CAFtK+evUnwbV_9fC3GwKKx7ss3SQB0QanK4Eygs=NwN6O+JFxg@mail.gmail.com>
Message-ID: <CAOXZzG7tB=7tC+X0OesEY5yAntYP58y061B9guQkUmz9cnEzZg@mail.gmail.com>

>
> If it's a problem with HDF5 library, I'm not sure where I need to point to
>>> the system installation.
>>>
>> If you load the cray-hdf5 module, that will set the HDF5_DIR environment
>> variable to the correct location.  Unfortunately, CMake uses the HDF5_ROOT
>> variable instead to look for it so you'll neet to set it accordingly.
>>
> I don't have much experience with cmake, but can I set additional
> variables in the ccmake window? Should this variable show up there asking
> to be set if you turn on the advanced mode toggle?
>

Different find modules work differently.  The FindHDF5 module uses the
HDF5_ROOT environment variable (not CMake variable, which is why it won't
show up in the ccmake UI) as a hint for where to search, hence exporting it
as an env var prior to running CMake.  You'll also want to be sure to
specify to use an external HDF5 rather than ParaView building it's own:

  -DVTK_USE_SYSTEM_HDF5:BOOL=ON


 CMAKE_CXX_FLAGS                  -L/lustre/medusa/gantech/
> software/mesa-10.6.0/lib
>
...

>  CMAKE_C_FLAGS                    -L/lustre/medusa/gantech/
> software/mesa-10.6.0/lib
>
...

>  CMAKE_EXE_LINKER_FLAGS           -L/lustre/medusa/gantech/
> software/mesa-10.6.0/lib
>

Instead of setting these in the compiler flags, it's better to tell
ParaView where to explicitly find the libraries and to configure
accordingly for OSMesa.  You can pass these as command line arguments to
cmake or ccmake with -D, or set them in the ccmake UI:

  -DOPENGL_INCLUDE_DIR:PATH=
  -DOPENGL_xmesa_INCLUDE_DIR:PATH=
  -DOPENGL_gl_LIBRARY:FILEPATH=
  -DOPENGL_glu_LIBRARY:FILEPATH=
  -DOSMESA_INCLUDE_DIR:PATH=/lustre/medusa/gantech/
software/mesa-10.6.0/include
  -DOSMESA_LIBRARY:FILEPATH=/lustre/medusa/gantech/
software/mesa-10.6.0/lib/libOSMesa.a
  -DVTK_OPENGL_HAS_OSMESA:BOOL=ON
  -DVTK_USE_X:BOOL=OFF



>  CMAKE_Fortran_COMPILER           /opt/gcc/4.9.2/bin/gfortran
>

Not that it will really matter since we're not compiling Fortran code, but
this should be /opt/cray/craype/2.2.1/bin/ftn


 MPI_CXX_LIBRARIES                /opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/lib/
>
...

>  MPI_C_LIBRARIES                  /opt/cray/mpt/7.1.3/gni/
> mpich2-gnu/49/lib/
>
...

>  MPI_LIBRARY                      /opt/cray/mpt/7.1.3/gni/
> mpich2-gnu/49/lib
>

It does look like the wrappers are correctly getting used for mpicc and
mpiCC and you can see the include dirs getting set accordingly, but these
do not look right.  Which version of CMake are you using?  Here's what I
get using CMake 3.2.3 (current cmake) on a Cray XC30 when not setting any
MPI variables, just letting CMake auto-detect them by enabling
ParaView_USE_MPI=ON:

 MPI_CXX_COMPILER
/opt/cray/craype/2.1.0/bin/CC
 MPI_CXX_COMPILE_FLAGS

 MPI_CXX_INCLUDE_PATH

 MPI_CXX_LIBRARIES

 MPI_CXX_LINK_FLAGS

 MPI_CXX_NO_INTERROGATE
/opt/cray/craype/2.1.0/bin/CC
 MPI_C_COMPILER
/opt/cray/craype/2.1.0/bin/cc
 MPI_C_COMPILE_FLAGS

 MPI_C_INCLUDE_PATH

 MPI_C_LIBRARIES

 MPI_C_LINK_FLAGS

 MPI_C_NO_INTERROGATE
/opt/cray/craype/2.1.0/bin/cc
 MPI_EXTRA_LIBRARY
MPI_EXTRA_LIBRARY-NOTFOUND
 MPI_Fortran_COMPILER
/opt/cray/craype/2.1.0/bin/ftn
 MPI_Fortran_COMPILE_FLAGS

 MPI_Fortran_INCLUDE_PATH

 MPI_Fortran_LIBRARIES

 MPI_Fortran_LINK_FLAGS

 MPI_Fortran_NO_INTERROGATE
/opt/cray/craype/2.1.0/bin/ftn
 MPI_LIBRARY                      MPI_LIBRARY-NOTFOUND

Because the Cray wrappers automatically add the mpi libs and headers
(behaving like mpiCC), then the MPI code should compile without any
additional flags.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/dba8e34f/attachment.html>

From cory.quammen at kitware.com  Thu Jul 16 14:41:13 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 16 Jul 2015 14:41:13 -0400
Subject: [Paraview] vtkDoubleArray with >3 components
In-Reply-To: <CAB5Fpx6q5_K_ZJNpXtrvNhOYjZQdzGCNxvk8Eo1bvM2tFi0YVQ@mail.gmail.com>
References: <CAEc4V-bvd0SRk35cuPM7Z9WhoH8WSL=7S_6kr7_Op5aOeoMN6A@mail.gmail.com>
 <CAB5Fpx6q5_K_ZJNpXtrvNhOYjZQdzGCNxvk8Eo1bvM2tFi0YVQ@mail.gmail.com>
Message-ID: <CAB5Fpx5uVT5qbK7UrXnLiPhYyawDGs8v5Lj41ncEHBy2tfe1XA@mail.gmail.com>

Hi Bruce,

I have attached a ParaView state file with a Programmable Source that
produces a vtkPolyData with 100 random points and a point data array with 9
components. It seems to display the various component ranges just fine.

Best,
Cory

On Thu, Jul 16, 2015 at 11:14 AM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Hi Bruce,
>
> I haven't seen this, but ParaView may be interpreting this array as a
> tensor field. Do you have a smallish test data file that you can share that
> shows the problem?
>
> Thanks,
> Cory
>
> On Sat, Jul 11, 2015 at 11:14 AM, Bruce Jones <bruce.david.jones at gmail.com
> > wrote:
>
>> I am creating vtkDoubleArrays based on averaging some input data to a
>> reduced set of points. The input data includes various vtk arrays which
>> have 1, 3 and 9 components.
>>
>> After averaging, I am writing the data to c++ arrays, and creating a new
>> vtkDoubleArray using the SetArray() function to pass the c++ arrays. This
>> works fine for 1 and 3 component arrays, however for the 9 component arrays
>> paraview shows that every element is set to 0.
>>
>> If I hardcode it so that 9 component arrays become 3 component arrays
>> (reading only the first 3 components from the input array), then I get the
>> correct data for the first 3 components, though I obviously need the other
>> 6 components in the end.
>>
>> Has anyone encountered this before?
>>
>> Cheers,
>> Bruce
>>
>> _______________________________________________
>> 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
>>
>>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/f89adc54/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NoneComponents.pvsm
Type: application/octet-stream
Size: 171587 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/f89adc54/attachment-0001.obj>

From cory.quammen at kitware.com  Thu Jul 16 15:33:35 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 16 Jul 2015 15:33:35 -0400
Subject: [Paraview] Python: Save Screenshot in parallel projection
In-Reply-To: <CAEqguQY0o_g-CjmmocvX9TfChtJ2TCRfJ_NMZ5LM-fhyzSVbfQ@mail.gmail.com>
References: <CAEqguQY8z8zHaX9ErnnoAxjfWgtA5tSHNCU_P8coyx9DTVtYHA@mail.gmail.com>
 <CAB5Fpx60y0Mb0pg3TjD7ZDg=dCd+f33mfWT2KHRWzkEs4kfccg@mail.gmail.com>
 <CAEqguQY0o_g-CjmmocvX9TfChtJ2TCRfJ_NMZ5LM-fhyzSVbfQ@mail.gmail.com>
Message-ID: <CAB5Fpx6gn6u1FGOc7EwUMZMkBwJ21dkxX72p=5GC8vG9y6Y47w@mail.gmail.com>

Hi Jonas,

Please remember to CC the list so that others may benefit from and
contribute to the conversation.

Could you download and try version 4.3.1 and let us know if you have
problems with that version?

Thanks,
Cory

On Thu, Jul 16, 2015 at 3:30 PM, Jonas Asche <asche.j at googlemail.com> wrote:

> Hello Cory,
> I am using Paraview 4.2.0 on a Windows 7 Computer. My question
>  was actually if there is a bug when using it in a Python scipt and how
> you would set up such a script because mine did not work. I realize now
> that i could have put that information in my first mail :P
>
> I tried again after cleaning some code (positions were copied from the
> Trace function etc) but still there is no difference in enabling/disabling
> parallel projection. I do this while setting up the View
> (CreateRenderView()).
>
> Thank you,
>
> Jonas
>
>
> 2015-07-15 15:59 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>
>> Jonas,
>>
>> What version of ParaView are you using? I am using the latest master
>> branch and saving a screenshot of with parallel projection seems to work
>> fine on this version.
>>
>> Thanks,
>> Cory
>>
>> On Mon, Jul 13, 2015 at 7:10 AM, Jonas Asche via ParaView <
>> paraview at paraview.org> wrote:
>>
>>> Hello, when i try to switch to parallel projection on in my script i can
>>> only save a screenshot with parallel projection disabled:
>>>
>>> self.__getView().CameraParallelProjection = 1
>>> self.__getView().CameraParallelScale = 1.0
>>> self.__getView().CameraViewUp = [0.0, 0.0, 1.0]
>>> self.__getView().CameraPosition = camdirection[axis]
>>> self.__getView().CameraFocalPoint = [0.0, 0.0, 33.32500076293945]
>>> self.__getView().CameraClippingRange = [154.56988142373606, 215.9545612783452]
>>>
>>> SaveScreenshot(str(self.__getConfig().get("save", "path") + 'img-') + str(axis) + "-" + str(distribution) + '.png', self.__getView())
>>>
>>> When when i print out the parallel scale AFTER savin the screenshot it is set to 46.6471043813.
>>>
>>>
>>> is this the same bug like here: http://paraview.org/Bug/view.php?id=7466
>>>
>>> ?
>>>
>>> Is there a workaround or am i doing something wrong?
>>>
>>> Thanks,
>>>
>>> Jonas
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>>
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/3b75e8c2/attachment.html>

From Thomas.Otoole at pinntech.com  Thu Jul 16 16:32:48 2015
From: Thomas.Otoole at pinntech.com (Thomas O'Toole)
Date: Thu, 16 Jul 2015 20:32:48 +0000
Subject: [Paraview] [EXTERNAL]  Extract all points inside volume
In-Reply-To: <12B8A446-3423-4D7E-8671-55C1D737233D@sandia.gov>
References: <4E09FD4309849147BFDAED6FAAC87A956B0D54AF@EP1EXMB004.corp.halliburton.com>
 <12B8A446-3423-4D7E-8671-55C1D737233D@sandia.gov>
Message-ID: <4E09FD4309849147BFDAED6FAAC87A956B0D55DA@EP1EXMB004.corp.halliburton.com>

I think the issue is that I want to use a threshold value to define the volume of interest, but then want to extract all of the points within that volume including those that don't satisfy the threshold filter. So far I can only extract the points that satisfy the threshold condition.

From: Scott, W Alan [mailto:wascott at sandia.gov]
Sent: 16 July 2015 18:15
To: Thomas O'Toole
Cc: paraview at paraview.org
Subject: Re: [EXTERNAL] [Paraview] Extract all points inside volume

Select points through (i.e., frustum select)?  Then, on the Find Data dialog, Freeze Selection.  Last, Filter/ Extract Selection?

Alan

On Jul 16, 2015, at 10:47 AM, Thomas O'Toole <Thomas.Otoole at pinntech.com<mailto:Thomas.Otoole at pinntech.com>> wrote:

Dear Paraviewers,

I am trying to select and extract all points that lie within a particular volume of my dataset. The volume is irregularly shaped (hence a simple clip is not an option), and created by a 3D Delaunay triangulation. Is there a straightforward way to do this in Paraview? I feel like there must be, but have been drawing a blank so far.

Many thanks,

Tom





________________________________
This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
_______________________________________________
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

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

From asche.j at googlemail.com  Thu Jul 16 16:41:13 2015
From: asche.j at googlemail.com (Jonas Asche)
Date: Thu, 16 Jul 2015 22:41:13 +0200
Subject: [Paraview] Python: Save Screenshot in parallel projection
In-Reply-To: <CAB5Fpx6gn6u1FGOc7EwUMZMkBwJ21dkxX72p=5GC8vG9y6Y47w@mail.gmail.com>
References: <CAEqguQY8z8zHaX9ErnnoAxjfWgtA5tSHNCU_P8coyx9DTVtYHA@mail.gmail.com>
 <CAB5Fpx60y0Mb0pg3TjD7ZDg=dCd+f33mfWT2KHRWzkEs4kfccg@mail.gmail.com>
 <CAEqguQY0o_g-CjmmocvX9TfChtJ2TCRfJ_NMZ5LM-fhyzSVbfQ@mail.gmail.com>
 <CAB5Fpx6gn6u1FGOc7EwUMZMkBwJ21dkxX72p=5GC8vG9y6Y47w@mail.gmail.com>
Message-ID: <CAEqguQYg+q-PzW725_6qyAX_-ccryGD4Zr8E-5cmkkXGg-JFuQ@mail.gmail.com>

Of course i will CC the list, sorry.
Here is what i wrote in the mail Cory mentioned:

Hello Cory,
> I am using Paraview 4.2.0 on a Windows 7 Computer. My question
>  was actually if there is a bug when using it in a Python scipt and how
> you would set up such a script because mine did not work. I realize now
> that i could have put that information in my first mail :P
>
> I tried again after cleaning some code (positions were copied from the
> Trace function etc) but still there is no difference in enabling/disabling
> parallel projection. I do this while setting up the View
> (CreateRenderView()).
>
> Thank you,
>
> Jonas


I installed version 4.3.1 . My script is working now. I hate to admit it
but from all my testing i forgot to remove one line of code that was
constantly toggling ON parallel projection. So it did not matter if i
toggle it in a function befor because it got resettet al the time...

I also testet it with version 4.2.0 and it does work.

Sorry for wasting some of your time by this mistake of mine. And thank you
for your effort Cory.


Jonas


PS. since i know how helpful these emails can be in the future, here the
code to toggle parallel projection:

(assuming my_view is an object created by 'my_view = CreateRenderView()')

my_view.CameraParallelProjection = 1  # 1 = parallel
my__view.CameraParallelScale = 1.0



2015-07-16 21:33 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:

> Hi Jonas,
>
> Please remember to CC the list so that others may benefit from and
> contribute to the conversation.
>
> Could you download and try version 4.3.1 and let us know if you have
> problems with that version?
>
> Thanks,
> Cory
>
> On Thu, Jul 16, 2015 at 3:30 PM, Jonas Asche <asche.j at googlemail.com>
> wrote:
>
>> Hello Cory,
>> I am using Paraview 4.2.0 on a Windows 7 Computer. My question
>>  was actually if there is a bug when using it in a Python scipt and how
>> you would set up such a script because mine did not work. I realize now
>> that i could have put that information in my first mail :P
>>
>> I tried again after cleaning some code (positions were copied from the
>> Trace function etc) but still there is no difference in enabling/disabling
>> parallel projection. I do this while setting up the View
>> (CreateRenderView()).
>>
>> Thank you,
>>
>> Jonas
>>
>>
>> 2015-07-15 15:59 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>>
>>> Jonas,
>>>
>>> What version of ParaView are you using? I am using the latest master
>>> branch and saving a screenshot of with parallel projection seems to work
>>> fine on this version.
>>>
>>> Thanks,
>>> Cory
>>>
>>> On Mon, Jul 13, 2015 at 7:10 AM, Jonas Asche via ParaView <
>>> paraview at paraview.org> wrote:
>>>
>>>> Hello, when i try to switch to parallel projection on in my script i
>>>> can only save a screenshot with parallel projection disabled:
>>>>
>>>> self.__getView().CameraParallelProjection = 1
>>>> self.__getView().CameraParallelScale = 1.0
>>>> self.__getView().CameraViewUp = [0.0, 0.0, 1.0]
>>>> self.__getView().CameraPosition = camdirection[axis]
>>>> self.__getView().CameraFocalPoint = [0.0, 0.0, 33.32500076293945]
>>>> self.__getView().CameraClippingRange = [154.56988142373606, 215.9545612783452]
>>>>
>>>> SaveScreenshot(str(self.__getConfig().get("save", "path") + 'img-') + str(axis) + "-" + str(distribution) + '.png', self.__getView())
>>>>
>>>> When when i print out the parallel scale AFTER savin the screenshot it is set to 46.6471043813.
>>>>
>>>>
>>>> is this the same bug like here: http://paraview.org/Bug/view.php?id=7466
>>>>
>>>> ?
>>>>
>>>> Is there a workaround or am i doing something wrong?
>>>>
>>>> Thanks,
>>>>
>>>> Jonas
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>>
>>>
>>> --
>>> Cory Quammen
>>> R&D Engineer
>>> Kitware, Inc.
>>>
>>
>>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/9d49732b/attachment.html>

From cory.quammen at kitware.com  Thu Jul 16 16:44:42 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 16 Jul 2015 16:44:42 -0400
Subject: [Paraview] Python: Save Screenshot in parallel projection
In-Reply-To: <CAEqguQYg+q-PzW725_6qyAX_-ccryGD4Zr8E-5cmkkXGg-JFuQ@mail.gmail.com>
References: <CAEqguQY8z8zHaX9ErnnoAxjfWgtA5tSHNCU_P8coyx9DTVtYHA@mail.gmail.com>
 <CAB5Fpx60y0Mb0pg3TjD7ZDg=dCd+f33mfWT2KHRWzkEs4kfccg@mail.gmail.com>
 <CAEqguQY0o_g-CjmmocvX9TfChtJ2TCRfJ_NMZ5LM-fhyzSVbfQ@mail.gmail.com>
 <CAB5Fpx6gn6u1FGOc7EwUMZMkBwJ21dkxX72p=5GC8vG9y6Y47w@mail.gmail.com>
 <CAEqguQYg+q-PzW725_6qyAX_-ccryGD4Zr8E-5cmkkXGg-JFuQ@mail.gmail.com>
Message-ID: <CAB5Fpx78c7Zkx7tjs+w=wDyCfvYaUhcXjK9aJ0MKUDGwCaQ9RA@mail.gmail.com>

No worries, Jonas, it happens to everyone. I'm glad it works.

Cory

On Thu, Jul 16, 2015 at 4:41 PM, Jonas Asche <asche.j at googlemail.com> wrote:

> Of course i will CC the list, sorry.
> Here is what i wrote in the mail Cory mentioned:
>
> Hello Cory,
>> I am using Paraview 4.2.0 on a Windows 7 Computer. My question
>>  was actually if there is a bug when using it in a Python scipt and how
>> you would set up such a script because mine did not work. I realize now
>> that i could have put that information in my first mail :P
>>
>> I tried again after cleaning some code (positions were copied from the
>> Trace function etc) but still there is no difference in enabling/disabling
>> parallel projection. I do this while setting up the View
>> (CreateRenderView()).
>>
>> Thank you,
>>
>> Jonas
>
>
> I installed version 4.3.1 . My script is working now. I hate to admit it
> but from all my testing i forgot to remove one line of code that was
> constantly toggling ON parallel projection. So it did not matter if i
> toggle it in a function befor because it got resettet al the time...
>
> I also testet it with version 4.2.0 and it does work.
>
> Sorry for wasting some of your time by this mistake of mine. And thank you
> for your effort Cory.
>
>
> Jonas
>
>
> PS. since i know how helpful these emails can be in the future, here the
> code to toggle parallel projection:
>
> (assuming my_view is an object created by 'my_view = CreateRenderView()')
>
> my_view.CameraParallelProjection = 1  # 1 = parallel
> my__view.CameraParallelScale = 1.0
>
>
>
> 2015-07-16 21:33 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>
>> Hi Jonas,
>>
>> Please remember to CC the list so that others may benefit from and
>> contribute to the conversation.
>>
>> Could you download and try version 4.3.1 and let us know if you have
>> problems with that version?
>>
>> Thanks,
>> Cory
>>
>> On Thu, Jul 16, 2015 at 3:30 PM, Jonas Asche <asche.j at googlemail.com>
>> wrote:
>>
>>> Hello Cory,
>>> I am using Paraview 4.2.0 on a Windows 7 Computer. My question
>>>  was actually if there is a bug when using it in a Python scipt and how
>>> you would set up such a script because mine did not work. I realize now
>>> that i could have put that information in my first mail :P
>>>
>>> I tried again after cleaning some code (positions were copied from the
>>> Trace function etc) but still there is no difference in enabling/disabling
>>> parallel projection. I do this while setting up the View
>>> (CreateRenderView()).
>>>
>>> Thank you,
>>>
>>> Jonas
>>>
>>>
>>> 2015-07-15 15:59 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>>>
>>>> Jonas,
>>>>
>>>> What version of ParaView are you using? I am using the latest master
>>>> branch and saving a screenshot of with parallel projection seems to work
>>>> fine on this version.
>>>>
>>>> Thanks,
>>>> Cory
>>>>
>>>> On Mon, Jul 13, 2015 at 7:10 AM, Jonas Asche via ParaView <
>>>> paraview at paraview.org> wrote:
>>>>
>>>>> Hello, when i try to switch to parallel projection on in my script i
>>>>> can only save a screenshot with parallel projection disabled:
>>>>>
>>>>> self.__getView().CameraParallelProjection = 1
>>>>> self.__getView().CameraParallelScale = 1.0
>>>>> self.__getView().CameraViewUp = [0.0, 0.0, 1.0]
>>>>> self.__getView().CameraPosition = camdirection[axis]
>>>>> self.__getView().CameraFocalPoint = [0.0, 0.0, 33.32500076293945]
>>>>> self.__getView().CameraClippingRange = [154.56988142373606, 215.9545612783452]
>>>>>
>>>>> SaveScreenshot(str(self.__getConfig().get("save", "path") + 'img-') + str(axis) + "-" + str(distribution) + '.png', self.__getView())
>>>>>
>>>>> When when i print out the parallel scale AFTER savin the screenshot it is set to 46.6471043813.
>>>>>
>>>>>
>>>>> is this the same bug like here: http://paraview.org/Bug/view.php?id=7466
>>>>>
>>>>> ?
>>>>>
>>>>> Is there a workaround or am i doing something wrong?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jonas
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Cory Quammen
>>>> R&D Engineer
>>>> Kitware, Inc.
>>>>
>>>
>>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>>
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/d4100684/attachment.html>

From lmorandini at ieee.org  Fri Jul 17 03:29:26 2015
From: lmorandini at ieee.org (Luca Morandini)
Date: Fri, 17 Jul 2015 17:29:26 +1000
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAOqyOuFMFju6ODKyehDU1pDdH1Z=A79wc0iy8KK3m11mziLMPQ@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <mo2q49$4gt$1@ger.gmane.org>
 <CAOqyOuGT2uONXRjPd80bJOBdnhugTMyyUCHGn6s8H4Aw+i1wOg@mail.gmail.com>
 <mo7cvk$ria$1@ger.gmane.org>
 <CAOqyOuFMFju6ODKyehDU1pDdH1Z=A79wc0iy8KK3m11mziLMPQ@mail.gmail.com>
Message-ID: <moaask$ejm$1@ger.gmane.org>

On 17/07/15 00:05, Casey Goodlett wrote:
>
> This needs to be updated for VTK 6 and is unrelated to the  PCL version.  You need
> to checkout the latest version of the plugin from here
> https://github.com/Kitware/PCLPlugin where this has been fixed.

Thanks Casey, I was finally able to use the plugin :)

May I suggest that an update to the "ParaView/PCL Plugin/Download And Build 
Instructions" page may be helpful?

Thanks again for your help,

Luca Morandini
Data Architect - AURIN project
Melbourne eResearch Group
Department of Computing and Information Systems
University of Melbourne
Tel. +61 03 903 58 380
Skype: lmorandini


From simon.esneault at gmail.com  Fri Jul 17 04:43:11 2015
From: simon.esneault at gmail.com (Simon ESNEAULT)
Date: Fri, 17 Jul 2015 10:43:11 +0200
Subject: [Paraview] GPU volume rendering failure on Intel HD XXXX/Iris,
 Windows and recent drivers
Message-ID: <CAC9gB0ArB3vVBbcQnk-52ymwKYpBuk7ZLRXJD8-RevF7NRGg6w@mail.gmail.com>

Hi All,

We're experiencing GPU volume rendering failure on a lot (maybe all ?)
Intel HD windows system with up to date drivers.

This is reproducible in Paraview or with the GPURenderDemo example from
VTK, just load a volume and try to render the volume... Here is a result
image from paraview on a Dell Latitude E7450 (Intel HD 5500 inside), with
GPU rendering [1] and the same volume with CPU VR rendering [2].
Interestingly, the volume rendering used to work with drivers older or
equal to the version 10.18.10.3496 [3]. As a work around, we ask our
customers to downgrade their driver version to this one, and they're
enjoying smooth GPU rendering. But this driver is quite old and does not
support recent chipset...

I've built and tested the GPURenderDemo with the brand new OpenGL2 backend
on an affected machine and of course it does work out of the box
(congratulations for this amazing work !). But our application is FDA/CE
marked and we need to wait that this new backend is completely ready for
prime time. So for now, we have to stick with VTK 6.1 ...

Anyone has any clue ? They're some warning that pop up from paraview
related to the extension "gl_version_1_2" that could not be loaded, not
sure if that could be related ? Following this thread [4] and the fix
proposed, I've tried to replace
/*****************/
extensions->LoadExtension("GL_VERSION_1_2")
/*****************/
by
/*****************/
extensions->LoadExtension("GL_EXT_texture3D");
extensions->LoadExtension( "GL_ARB_texture_non_power_of_two" );
/*****************/
in the vtkOpenGLGPUVolumeRayCastMapper.cxx, The warning disappears but
there is still no volume rendering (tested with GPURenderDemo). Maybe it
needs some others extensions ?

Should I fill a bug in paraview, vtk ? Are there any plan to maintain and
maybe fix this for the old backend ?

Thanks,
-- 
------------------------------------------------------------------
Simon Esneault
Rennes, France
------------------------------------------------------------------

[1] http://picpaste.com/pics/Paraview-4-3-1-GPU-VR_fail.1437122217.PNG
[2] http://picpaste.com/pics/Paraview-4-3-1-CPU-VR_win.1437122267.PNG
[3] https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23339
[4] http://public.kitware.com/pipermail/vtkusers/2014-April/083584.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150717/cf95ea00/attachment.html>

From dave.demarle at kitware.com  Fri Jul 17 08:52:02 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Fri, 17 Jul 2015 08:52:02 -0400
Subject: [Paraview] Intel Developer Forum, software-defined visualization,
 San Francisco August 18-20
Message-ID: <CANjZAi9OmrUXio85uL15Eff2NWJ1BdtdJX3caNaf=pvCK5i1EA@mail.gmail.com>

Greetings lists,

The vis and rendering folks at Intel will be showing off the things they've
been working on and are bringing to VTK, ParaView and the rest.

See the attached flyer for registration promo-codes if you plan to attend
the conference.

Hope to see you there.

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150717/6796d574/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IDF_wPromoCodes.pdf
Type: application/pdf
Size: 71463 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150717/6796d574/attachment.pdf>

From casey.goodlett at kitware.com  Fri Jul 17 08:54:36 2015
From: casey.goodlett at kitware.com (Casey Goodlett)
Date: Fri, 17 Jul 2015 08:54:36 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <moaask$ejm$1@ger.gmane.org>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <mo2q49$4gt$1@ger.gmane.org>
 <CAOqyOuGT2uONXRjPd80bJOBdnhugTMyyUCHGn6s8H4Aw+i1wOg@mail.gmail.com>
 <mo7cvk$ria$1@ger.gmane.org>
 <CAOqyOuFMFju6ODKyehDU1pDdH1Z=A79wc0iy8KK3m11mziLMPQ@mail.gmail.com>
 <moaask$ejm$1@ger.gmane.org>
Message-ID: <CAOqyOuGFFOHjMazR6EOwixVJ2LbH=5849VVCx2woC1CaJuS4KQ@mail.gmail.com>

Can you request a wiki account and update the page with any instructions
you found helpful?

You could also create a pull request to create an instructions file on the
github page or create a page on the github wiki
https://github.com/Kitware/PCLPlugin/wiki .

Community help in keeping the plugin and documentation up to date would be
greatly appreciated as we have limited resources for maintaining this
plugin at present.

Thank you

-- 
Casey B Goodlett, PhD
Technical Leader
Kitware, Inc. - North Carolina Office
http://www.kitware.com
(919) 969-6990 x310
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150717/c0686cf5/attachment.html>

From sergi.mateo.bellido at gmail.com  Fri Jul 17 09:38:52 2015
From: sergi.mateo.bellido at gmail.com (Sergi Mateo Bellido)
Date: Fri, 17 Jul 2015 15:38:52 +0200
Subject: [Paraview] segfault playing a simulation
In-Reply-To: <CAB5Fpx7-YAJznWJKT6gk4fAV9_GM_GX2E=0Q9_2YSW4Wt5NO8A@mail.gmail.com>
References: <55895735.2030202@gmail.com>	<CAB5Fpx4BDY+JDKBbA5Lt02Yt1RLaaZY6TPW9azpZsGf-aWTD7Q@mail.gmail.com>	<559381DE.5030504@gmail.com>	<CAB5Fpx6H7dY-j86vut03OuVr+7smd+1YwGqL2e771tRE0xdkxw@mail.gmail.com>	<559422EF.3070304@gmail.com>	<CAB5Fpx7AdTrtGAsq9OjoW36=-dWFDzUAGrtCF+fqqa4hLenoDg@mail.gmail.com>	<55A0E2AE.5050101@gmail.com>
 <CAB5Fpx7-YAJznWJKT6gk4fAV9_GM_GX2E=0Q9_2YSW4Wt5NO8A@mail.gmail.com>
Message-ID: <55A9056C.2000101@gmail.com>

Hi Cory,

Your intuition was right: the problem is related in some way with the 
offset. I've changed the DataMote to ASCII and everything worked :)  
Note that in this mode the offset field is not used, instead of that VTK 
generates a DataArray.

I would like to know how the offset is computed since I can't find any 
relation between the  offset value and my data.

Thanks!

Sergi

On 07/13/2015 03:51 AM, Cory Quammen wrote:
> Sergi,
>
> Your VTI file extents should only describe the region of the whole 
> image they occupy, so you are on the right track. In situations like 
> these where it isn't obvious what is wrong, I tend to start from the 
> beginning with a very small example and build up from there. For 
> example, you could start with a small image - say 2 x 4 pixels (2D) 
> split into two pieces. Start with one data array for this example and 
> make sure it works - use ASCII encoding so that you know for sure what 
> is in the XML file and then switch to raw binary, then zipped binary. 
> Then add a second data array. When you are confident that works, 
> change the example to four pieces, then make the image 3D and so on.
>
> It can take a while to do this, but you'll come out really 
> understanding the file format and will probably figure out what you 
> had wrong in the first place.
>
> Thanks,
> Cory
>
> On Sat, Jul 11, 2015 at 5:32 AM, Sergi Mateo Bellido 
> <sergi.mateo.bellido at gmail.com <mailto:sergi.mateo.bellido at gmail.com>> 
> wrote:
>
>     Hi Cory,
>
>     Thanks for your time. I have been playing a bit with the files too
>     and I realized that replacing the whole_extent of each *.vti  by
>     the whole dataset everything works.
>
>     I would like to generate something like this:
>     http://vtk.1045678.n5.nabble.com/Example-vti-file-td3381382.html .
>     In this example, each imagedata has whole_extent=whole size but
>     its pieces only contain a portion of the whole dataset. Does this
>     configuration make sense?
>
>     I have been trying to generate something like that but I failed.
>     My code looks like this one:
>     http://www.vtk.org/Wiki/VTK/Examples/Cxx/IO/WriteVTI but using
>     VtkFloatArray as buffers and attaching them to the VtkImageData. I
>     tried defining the set of the VtkImageData as the whole dataset
>     and defining the VtkFloatArrays of the size of each portion but it
>     didn't work :(
>
>     Any clue?
>
>     Thanks!
>     Sergi
>
>
>     On 07/09/2015 05:00 PM, Cory Quamen wrote:
>>     Hi Sergi,
>>
>>     I played with your data set a little but haven't found what is
>>     wrong. I am suspicious of two things in the data file, the extent
>>     and the offset in the second data array (it looks too small).
>>
>>     What are the dimensions of your grid? Note that the whole extent
>>     upper values need to be the dimension - 1, e.g., for a
>>     300x300x300 grid, the whole extent should be 0 299 0 299 0 299.
>>
>>     Thanks,
>>     Cory
>>
>>     On Wed, Jul 1, 2015 at 12:27 PM, Sergi Mateo Bellido
>>     <sergi.mateo.bellido at gmail.com
>>     <mailto:sergi.mateo.bellido at gmail.com>> wrote:
>>
>>         Hi Cory,
>>
>>         Thanks for your time. These data files have been produced by
>>         a software that I'm developing with some colleagues.
>>
>>         Best regards,
>>
>>         Sergi
>>
>>
>>         On 07/01/2015 03:59 PM, Cory Quammen wrote:
>>>         Sergi,
>>>
>>>         I can confirm the crash you are seeing in the same location
>>>         in the code. I'm looking for the cause.
>>>
>>>         What software produced these data files?
>>>
>>>         Thanks,
>>>         Cory
>>>
>>>         On Wed, Jul 1, 2015 at 1:59 AM, Sergi Mateo Bellido
>>>         <sergi.mateo.bellido at gmail.com
>>>         <mailto:sergi.mateo.bellido at gmail.com>> wrote:
>>>
>>>             Hi Cory,
>>>
>>>             Thanks for your answer. I reproduced the segfault in two
>>>             different ways, but it's always after loading a data set:
>>>             - After loading a data set, I tried to play the
>>>             simulation ->segfault
>>>             - After loading a data set, I tried to filter some
>>>             fields from the model (Pointer array status). As soon as
>>>             I clicked the 'apply' button, paraview crashed with a
>>>             segfault.
>>>
>>>             Thanks,
>>>             Sergi
>>>
>>>
>>>
>>>             On 06/30/2015 06:21 AM, Cory Quammen wrote:
>>>>             Hi Sergi,
>>>>
>>>>             Could you clarify when you are seeing this crash? Is it
>>>>             right when starting ParaView or when first loading a
>>>>             data set?
>>>>
>>>>             Thanks,
>>>>             Cory
>>>>
>>>>             On Tue, Jun 23, 2015 at 8:55 AM, Sergi Mateo Bellido
>>>>             <sergi.mateo.bellido at gmail.com
>>>>             <mailto:sergi.mateo.bellido at gmail.com>> wrote:
>>>>
>>>>                 Hi,
>>>>
>>>>                 I'm trying to reproduce a simulation with ParaView
>>>>                 4.3.1 and it always crashes when I start it. You
>>>>                 can find the backtrace below:
>>>>
>>>>                 =========================================================
>>>>                 Process id 6681 Caught SIGSEGV at 0x925b124 address
>>>>                 not mapped to object
>>>>                 Program Stack:
>>>>                 WARNING: The stack trace will not use advanced
>>>>                 capabilities because this is a release build.
>>>>                 0x7f54ce081d40 : ??? [(???) ???:-1]
>>>>                 0x7f54ce19caf6 : ??? [(???) ???:-1]
>>>>                 0x7f54cb123736 :
>>>>                 vtkXMLPStructuredDataReader::CopySubExtent(int*,
>>>>                 int*, long long*, int*, int*, long long*, int*,
>>>>                 int*, vtkDataArray*, vtkDataArray*)
>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cb12389f :
>>>>                 vtkXMLPStructuredDataReader::CopyArrayForPoints(vtkDataArray*,
>>>>                 vtkDataArray*) [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cb11cc1f : vtkXMLPDataReader::ReadPieceData()
>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cb11ca14 :
>>>>                 vtkXMLPDataReader::ReadPieceData(int)
>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cb124d7a :
>>>>                 vtkXMLPStructuredDataReader::ReadXMLData()
>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cb1280eb :
>>>>                 vtkXMLReader::RequestData(vtkInformation*,
>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cb1273b6 :
>>>>                 vtkXMLReader::ProcessRequest(vtkInformation*,
>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cd6200f9 :
>>>>                 vtkFileSeriesReader::RequestData(vtkInformation*,
>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>                 [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cd61f07f :
>>>>                 vtkFileSeriesReader::ProcessRequest(vtkInformation*, vtkInformationVector**,
>>>>                 vtkInformationVector*)
>>>>                 [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d2706204 :
>>>>                 vtkExecutive::CallAlgorithm(vtkInformation*, int,
>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d27016cc :
>>>>                 vtkDemandDrivenPipeline::ExecuteData(vtkInformation*,
>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d2700201 :
>>>>                 vtkCompositeDataPipeline::ExecuteData(vtkInformation*,
>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d2704067 :
>>>>                 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d271d959 :
>>>>                 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d26fe387 :
>>>>                 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*)
>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d2704010 :
>>>>                 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d271d959 :
>>>>                 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d26fe387 :
>>>>                 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*)
>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d2704010 :
>>>>                 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d271d959 :
>>>>                 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d27035ae :
>>>>                 vtkDemandDrivenPipeline::UpdateData(int)
>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d271e87f :
>>>>                 vtkStreamingDemandDrivenPipeline::Update(int)
>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cd98fa7f :
>>>>                 vtkPVDataRepresentation::ProcessViewRequest(vtkInformationRequestKey*,
>>>>                 vtkInformation*, vtkInformation*)
>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cd973d79 :
>>>>                 vtkGeometryRepresentation::ProcessViewRequest(vtkInformationRequestKey*,
>>>>                 vtkInformation*, vtkInformation*)
>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cd975d71 :
>>>>                 vtkGeometryRepresentationWithFaces::ProcessViewRequest(vtkInformationRequestKey*,
>>>>                 vtkInformation*, vtkInformation*)
>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cd9bd388 :
>>>>                 vtkPVView::CallProcessViewRequest(vtkInformationRequestKey*,
>>>>                 vtkInformation*, vtkInformationVector*)
>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cd9bd552 : vtkPVView::Update()
>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cd9acb78 : vtkPVRenderView::Update()
>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d780ac30 :
>>>>                 vtkPVRenderViewCommand(vtkClientServerInterpreter*,
>>>>                 vtkObjectBase*, char const*, vtkClientServerStream
>>>>                 const&, vtkClientServerStream&, void*)
>>>>                 [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d4e135e0 :
>>>>                 vtkClientServerInterpreter::CallCommandFunction(char const*,
>>>>                 vtkObjectBase*, char const*, vtkClientServerStream
>>>>                 const&, vtkClientServerStream&)
>>>>                 [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d4e18393 :
>>>>                 vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream
>>>>                 const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d4e16832 :
>>>>                 vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream
>>>>                 const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d4e16ced :
>>>>                 vtkClientServerInterpreter::ProcessStream(vtkClientServerStream
>>>>                 const&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d5b26cec :
>>>>                 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream
>>>>                 const&, bool)
>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d5b26958 :
>>>>                 vtkPVSessionCore::ExecuteStream(unsigned int,
>>>>                 vtkClientServerStream const&, bool)
>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d5b25203 :
>>>>                 vtkPVSessionBase::ExecuteStream(unsigned int,
>>>>                 vtkClientServerStream const&, bool)
>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cdcae44f : vtkSMViewProxy::Update()
>>>>                 [(libvtkPVServerManagerRendering-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cdf2f6f7 :
>>>>                 vtkSMAnimationScene::TickInternal(double, double,
>>>>                 double) [(libvtkPVAnimation-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cf415cab : vtkAnimationCue::Tick(double,
>>>>                 double, double) [(libvtkCommonCore-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cdf23268 : vtkAnimationPlayer::Play()
>>>>                 [(libvtkPVAnimation-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d7851619 :
>>>>                 vtkSMAnimationSceneCommand(vtkClientServerInterpreter*,
>>>>                 vtkObjectBase*, char const*, vtkClientServerStream
>>>>                 const&, vtkClientServerStream&, void*)
>>>>                 [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d4e135e0 :
>>>>                 vtkClientServerInterpreter::CallCommandFunction(char const*,
>>>>                 vtkObjectBase*, char const*, vtkClientServerStream
>>>>                 const&, vtkClientServerStream&)
>>>>                 [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d4e18393 :
>>>>                 vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream
>>>>                 const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d4e16832 :
>>>>                 vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream
>>>>                 const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d4e16ced :
>>>>                 vtkClientServerInterpreter::ProcessStream(vtkClientServerStream
>>>>                 const&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d5b436d4 :
>>>>                 vtkSIProperty::ProcessMessage(vtkClientServerStream&)
>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d5b4377e :
>>>>                 vtkSIProperty::Push(paraview_protobuf::Message*,
>>>>                 int) [(libvtkPVServerImplementationCore-pv4.3.so.1)
>>>>                 ???:-1]
>>>>                 0x7f54d5b4459e :
>>>>                 vtkSIProxy::Push(paraview_protobuf::Message*)
>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d5b2884a :
>>>>                 vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*)
>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d5b27484 :
>>>>                 vtkPVSessionCore::PushState(paraview_protobuf::Message*)
>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d5b2514d :
>>>>                 vtkPVSessionBase::PushState(paraview_protobuf::Message*)
>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d5d859b7 : vtkSMProxy::UpdateProperty(char
>>>>                 const*, int)
>>>>                 [(libvtkPVServerManagerCore-pv4.3.so.1) ???:-1]
>>>>                 0x7f54d6d8aa07 : pqVCRController::onPlay()
>>>>                 [(libvtkpqComponents-pv4.3.so.1) ???:-1]
>>>>                 0x7f54cfa98258 : QMetaObject::activate(QObject*,
>>>>                 QMetaObject const*, int, void**) [(libQtCore.so.4)
>>>>                 ???:-1]
>>>>                 0x7f54d01102f2 : QAction::triggered(bool)
>>>>                 [(libQtGui.so.4) ???:-1]
>>>>                 0x7f54d0111710 :
>>>>                 QAction::activate(QAction::ActionEvent)
>>>>                 [(libQtGui.so.4) ???:-1]
>>>>                 0x7f54d04fd514 : ??? [(???) ???:-1]
>>>>                 0x7f54d04fd7ab :
>>>>                 QAbstractButton::mouseReleaseEvent(QMouseEvent*)
>>>>                 [(libQtGui.so.4) ???:-1]
>>>>                 0x7f54d05d15ea :
>>>>                 QToolButton::mouseReleaseEvent(QMouseEvent*)
>>>>                 [(libQtGui.so.4) ???:-1]
>>>>                 0x7f54d0175ac1 : QWidget::event(QEvent*)
>>>>                 [(libQtGui.so.4) ???:-1]
>>>>                 0x7f54d04fca3f : QAbstractButton::event(QEvent*)
>>>>                 [(libQtGui.so.4) ???:-1]
>>>>                 0x7f54d05d422d : QToolButton::event(QEvent*)
>>>>                 [(libQtGui.so.4) ???:-1]
>>>>                 0x7f54d011759e :
>>>>                 QApplicationPrivate::notify_helper(QObject*,
>>>>                 QEvent*) [(libQtGui.so.4) ???:-1]
>>>>                 0x7f54d011e533 : QApplication::notify(QObject*,
>>>>                 QEvent*) [(libQtGui.so.4) ???:-1]
>>>>                 0x7f54cfa802f3 :
>>>>                 QCoreApplication::notifyInternal(QObject*, QEvent*)
>>>>                 [(libQtCore.so.4) ???:-1]
>>>>                 0x7f54d011a656 :
>>>>                 QApplicationPrivate::sendMouseEvent(QWidget*,
>>>>                 QMouseEvent*, QWidget*, QWidget*, QWidget**,
>>>>                 QPointer<QWidget>&, bool) [(libQtGui.so.4) ???:-1]
>>>>                 0x7f54d019ca94 : ??? [(???) ???:-1]
>>>>                 0x7f54d019b877 :
>>>>                 QApplication::x11ProcessEvent(_XEvent*)
>>>>                 [(libQtGui.so.4) ???:-1]
>>>>                 0x7f54d01c4805 : ??? [(???) ???:-1]
>>>>                 0x7f54cfa7f375 :
>>>>                 QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
>>>>                 [(libQtCore.so.4) ???:-1]
>>>>                 0x7f54cfa7f748 :
>>>>                 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
>>>>                 [(libQtCore.so.4) ???:-1]
>>>>                 0x7f54cfa8414b : QCoreApplication::exec()
>>>>                 [(libQtCore.so.4) ???:-1]
>>>>                 0x407785 : main [(paraview) ???:-1]
>>>>                 0x7f54ce06cec5 : __libc_start_main [(libc.so.6) ???:-1]
>>>>                 0x4074da : QMainWindow::event(QEvent*) [(paraview)
>>>>                 ???:-1]
>>>>                 =========================================================
>>>>
>>>>                 Thanks,
>>>>
>>>>                 Sergi Mateo
>>>>                 sergi.mateo.bellido at gmail.com
>>>>                 <mailto:sergi.mateo.bellido at gmail.com>
>>>>
>>>>                 _______________________________________________
>>>>                 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
>>>>
>>>>
>>>>
>>>>
>>>>             -- 
>>>>             Cory Quammen
>>>>             R&D Engineer
>>>>             Kitware, Inc.
>>>
>>>
>>>
>>>
>>>         -- 
>>>         Cory Quammen
>>>         R&D Engineer
>>>         Kitware, Inc.
>>
>>
>>
>>
>>     -- 
>>     Cory Quammen
>>     R&D Engineer
>>     Kitware, Inc.
>
>
>
>
> -- 
> Cory Quammen
> R&D Engineer
> Kitware, Inc.

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

From sergi.mateo.bellido at gmail.com  Fri Jul 17 10:21:42 2015
From: sergi.mateo.bellido at gmail.com (Sergi Mateo Bellido)
Date: Fri, 17 Jul 2015 16:21:42 +0200
Subject: [Paraview] segfault playing a simulation
In-Reply-To: <55A9056C.2000101@gmail.com>
References: <55895735.2030202@gmail.com>	<CAB5Fpx4BDY+JDKBbA5Lt02Yt1RLaaZY6TPW9azpZsGf-aWTD7Q@mail.gmail.com>	<559381DE.5030504@gmail.com>	<CAB5Fpx6H7dY-j86vut03OuVr+7smd+1YwGqL2e771tRE0xdkxw@mail.gmail.com>	<559422EF.3070304@gmail.com>	<CAB5Fpx7AdTrtGAsq9OjoW36=-dWFDzUAGrtCF+fqqa4hLenoDg@mail.gmail.com>	<55A0E2AE.5050101@gmail.com>
 <CAB5Fpx7-YAJznWJKT6gk4fAV9_GM_GX2E=0Q9_2YSW4Wt5NO8A@mail.gmail.com>
 <55A9056C.2000101@gmail.com>
Message-ID: <55A90F76.8000804@gmail.com>

Hi again,

I've just tried storing the data as a binary and It  crashes. In this 
case we are not using the offset field either.

May the problem be related to the data compression?

Best,
Sergi

On 07/17/2015 03:38 PM, Sergi Mateo Bellido wrote:
> Hi Cory,
>
> Your intuition was right: the problem is related in some way with the 
> offset. I've changed the DataMote to ASCII and everything worked :)  
> Note that in this mode the offset field is not used, instead of that 
> VTK generates a DataArray.
>
> I would like to know how the offset is computed since I can't find any 
> relation between the  offset value and my data.
>
> Thanks!
>
> Sergi
>
> On 07/13/2015 03:51 AM, Cory Quammen wrote:
>> Sergi,
>>
>> Your VTI file extents should only describe the region of the whole 
>> image they occupy, so you are on the right track. In situations like 
>> these where it isn't obvious what is wrong, I tend to start from the 
>> beginning with a very small example and build up from there. For 
>> example, you could start with a small image - say 2 x 4 pixels (2D) 
>> split into two pieces. Start with one data array for this example and 
>> make sure it works - use ASCII encoding so that you know for sure 
>> what is in the XML file and then switch to raw binary, then zipped 
>> binary. Then add a second data array. When you are confident that 
>> works, change the example to four pieces, then make the image 3D and 
>> so on.
>>
>> It can take a while to do this, but you'll come out really 
>> understanding the file format and will probably figure out what you 
>> had wrong in the first place.
>>
>> Thanks,
>> Cory
>>
>> On Sat, Jul 11, 2015 at 5:32 AM, Sergi Mateo Bellido 
>> <sergi.mateo.bellido at gmail.com 
>> <mailto:sergi.mateo.bellido at gmail.com>> wrote:
>>
>>     Hi Cory,
>>
>>     Thanks for your time. I have been playing a bit with the files
>>     too and I realized that replacing the whole_extent of each *.vti 
>>     by the whole dataset everything works.
>>
>>     I would like to generate something like this:
>>     http://vtk.1045678.n5.nabble.com/Example-vti-file-td3381382.html
>>     . In this example, each imagedata has whole_extent=whole size but
>>     its pieces only contain a portion of the whole dataset. Does this
>>     configuration make sense?
>>
>>     I have been trying to generate something like that but I failed.
>>     My code looks like this one:
>>     http://www.vtk.org/Wiki/VTK/Examples/Cxx/IO/WriteVTI but using
>>     VtkFloatArray as buffers and attaching them to the VtkImageData.
>>     I tried defining the set of the VtkImageData as the whole dataset
>>     and defining the VtkFloatArrays of the size of each portion but
>>     it didn't work :(
>>
>>     Any clue?
>>
>>     Thanks!
>>     Sergi
>>
>>
>>     On 07/09/2015 05:00 PM, Cory Quamen wrote:
>>>     Hi Sergi,
>>>
>>>     I played with your data set a little but haven't found what is
>>>     wrong. I am suspicious of two things in the data file, the
>>>     extent and the offset in the second data array (it looks too small).
>>>
>>>     What are the dimensions of your grid? Note that the whole extent
>>>     upper values need to be the dimension - 1, e.g., for a
>>>     300x300x300 grid, the whole extent should be 0 299 0 299 0 299.
>>>
>>>     Thanks,
>>>     Cory
>>>
>>>     On Wed, Jul 1, 2015 at 12:27 PM, Sergi Mateo Bellido
>>>     <sergi.mateo.bellido at gmail.com
>>>     <mailto:sergi.mateo.bellido at gmail.com>> wrote:
>>>
>>>         Hi Cory,
>>>
>>>         Thanks for your time. These data files have been produced by
>>>         a software that I'm developing with some colleagues.
>>>
>>>         Best regards,
>>>
>>>         Sergi
>>>
>>>
>>>         On 07/01/2015 03:59 PM, Cory Quammen wrote:
>>>>         Sergi,
>>>>
>>>>         I can confirm the crash you are seeing in the same location
>>>>         in the code. I'm looking for the cause.
>>>>
>>>>         What software produced these data files?
>>>>
>>>>         Thanks,
>>>>         Cory
>>>>
>>>>         On Wed, Jul 1, 2015 at 1:59 AM, Sergi Mateo Bellido
>>>>         <sergi.mateo.bellido at gmail.com
>>>>         <mailto:sergi.mateo.bellido at gmail.com>> wrote:
>>>>
>>>>             Hi Cory,
>>>>
>>>>             Thanks for your answer. I reproduced the segfault in
>>>>             two different ways, but it's always after loading a
>>>>             data set:
>>>>             - After loading a data set, I tried to play the
>>>>             simulation ->segfault
>>>>             - After loading a data set, I tried to filter some
>>>>             fields from the model (Pointer array status). As soon
>>>>             as I clicked the 'apply' button, paraview crashed with
>>>>             a segfault.
>>>>
>>>>             Thanks,
>>>>             Sergi
>>>>
>>>>
>>>>
>>>>             On 06/30/2015 06:21 AM, Cory Quammen wrote:
>>>>>             Hi Sergi,
>>>>>
>>>>>             Could you clarify when you are seeing this crash? Is
>>>>>             it right when starting ParaView or when first loading
>>>>>             a data set?
>>>>>
>>>>>             Thanks,
>>>>>             Cory
>>>>>
>>>>>             On Tue, Jun 23, 2015 at 8:55 AM, Sergi Mateo Bellido
>>>>>             <sergi.mateo.bellido at gmail.com
>>>>>             <mailto:sergi.mateo.bellido at gmail.com>> wrote:
>>>>>
>>>>>                 Hi,
>>>>>
>>>>>                 I'm trying to reproduce a simulation with ParaView
>>>>>                 4.3.1 and it always crashes when I start it. You
>>>>>                 can find the backtrace below:
>>>>>
>>>>>                 =========================================================
>>>>>                 Process id 6681 Caught SIGSEGV at 0x925b124
>>>>>                 address not mapped to object
>>>>>                 Program Stack:
>>>>>                 WARNING: The stack trace will not use advanced
>>>>>                 capabilities because this is a release build.
>>>>>                 0x7f54ce081d40 : ??? [(???) ???:-1]
>>>>>                 0x7f54ce19caf6 : ??? [(???) ???:-1]
>>>>>                 0x7f54cb123736 :
>>>>>                 vtkXMLPStructuredDataReader::CopySubExtent(int*,
>>>>>                 int*, long long*, int*, int*, long long*, int*,
>>>>>                 int*, vtkDataArray*, vtkDataArray*)
>>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54cb12389f :
>>>>>                 vtkXMLPStructuredDataReader::CopyArrayForPoints(vtkDataArray*,
>>>>>                 vtkDataArray*) [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54cb11cc1f :
>>>>>                 vtkXMLPDataReader::ReadPieceData()
>>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54cb11ca14 :
>>>>>                 vtkXMLPDataReader::ReadPieceData(int)
>>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54cb124d7a :
>>>>>                 vtkXMLPStructuredDataReader::ReadXMLData()
>>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54cb1280eb :
>>>>>                 vtkXMLReader::RequestData(vtkInformation*,
>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54cb1273b6 :
>>>>>                 vtkXMLReader::ProcessRequest(vtkInformation*,
>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54cd6200f9 :
>>>>>                 vtkFileSeriesReader::RequestData(vtkInformation*,
>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>                 [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54cd61f07f :
>>>>>                 vtkFileSeriesReader::ProcessRequest(vtkInformation*,
>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>                 [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d2706204 :
>>>>>                 vtkExecutive::CallAlgorithm(vtkInformation*, int,
>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d27016cc :
>>>>>                 vtkDemandDrivenPipeline::ExecuteData(vtkInformation*,
>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d2700201 :
>>>>>                 vtkCompositeDataPipeline::ExecuteData(vtkInformation*,
>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d2704067 :
>>>>>                 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d271d959 :
>>>>>                 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d26fe387 :
>>>>>                 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*)
>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d2704010 :
>>>>>                 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d271d959 :
>>>>>                 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d26fe387 :
>>>>>                 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*)
>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d2704010 :
>>>>>                 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d271d959 :
>>>>>                 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d27035ae :
>>>>>                 vtkDemandDrivenPipeline::UpdateData(int)
>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d271e87f :
>>>>>                 vtkStreamingDemandDrivenPipeline::Update(int)
>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54cd98fa7f :
>>>>>                 vtkPVDataRepresentation::ProcessViewRequest(vtkInformationRequestKey*,
>>>>>                 vtkInformation*, vtkInformation*)
>>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1)
>>>>>                 ???:-1]
>>>>>                 0x7f54cd973d79 :
>>>>>                 vtkGeometryRepresentation::ProcessViewRequest(vtkInformationRequestKey*,
>>>>>                 vtkInformation*, vtkInformation*)
>>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1)
>>>>>                 ???:-1]
>>>>>                 0x7f54cd975d71 :
>>>>>                 vtkGeometryRepresentationWithFaces::ProcessViewRequest(vtkInformationRequestKey*,
>>>>>                 vtkInformation*, vtkInformation*)
>>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1)
>>>>>                 ???:-1]
>>>>>                 0x7f54cd9bd388 :
>>>>>                 vtkPVView::CallProcessViewRequest(vtkInformationRequestKey*,
>>>>>                 vtkInformation*, vtkInformationVector*)
>>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1)
>>>>>                 ???:-1]
>>>>>                 0x7f54cd9bd552 : vtkPVView::Update()
>>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1)
>>>>>                 ???:-1]
>>>>>                 0x7f54cd9acb78 : vtkPVRenderView::Update()
>>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1)
>>>>>                 ???:-1]
>>>>>                 0x7f54d780ac30 :
>>>>>                 vtkPVRenderViewCommand(vtkClientServerInterpreter*, vtkObjectBase*,
>>>>>                 char const*, vtkClientServerStream const&,
>>>>>                 vtkClientServerStream&, void*)
>>>>>                 [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d4e135e0 :
>>>>>                 vtkClientServerInterpreter::CallCommandFunction(char
>>>>>                 const*, vtkObjectBase*, char const*,
>>>>>                 vtkClientServerStream const&,
>>>>>                 vtkClientServerStream&)
>>>>>                 [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d4e18393 :
>>>>>                 vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream
>>>>>                 const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d4e16832 :
>>>>>                 vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream
>>>>>                 const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d4e16ced :
>>>>>                 vtkClientServerInterpreter::ProcessStream(vtkClientServerStream
>>>>>                 const&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d5b26cec :
>>>>>                 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream
>>>>>                 const&, bool)
>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d5b26958 :
>>>>>                 vtkPVSessionCore::ExecuteStream(unsigned int,
>>>>>                 vtkClientServerStream const&, bool)
>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d5b25203 :
>>>>>                 vtkPVSessionBase::ExecuteStream(unsigned int,
>>>>>                 vtkClientServerStream const&, bool)
>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54cdcae44f : vtkSMViewProxy::Update()
>>>>>                 [(libvtkPVServerManagerRendering-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54cdf2f6f7 :
>>>>>                 vtkSMAnimationScene::TickInternal(double, double,
>>>>>                 double) [(libvtkPVAnimation-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54cf415cab : vtkAnimationCue::Tick(double,
>>>>>                 double, double) [(libvtkCommonCore-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54cdf23268 : vtkAnimationPlayer::Play()
>>>>>                 [(libvtkPVAnimation-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d7851619 :
>>>>>                 vtkSMAnimationSceneCommand(vtkClientServerInterpreter*,
>>>>>                 vtkObjectBase*, char const*, vtkClientServerStream
>>>>>                 const&, vtkClientServerStream&, void*)
>>>>>                 [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d4e135e0 :
>>>>>                 vtkClientServerInterpreter::CallCommandFunction(char
>>>>>                 const*, vtkObjectBase*, char const*,
>>>>>                 vtkClientServerStream const&,
>>>>>                 vtkClientServerStream&)
>>>>>                 [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d4e18393 :
>>>>>                 vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream
>>>>>                 const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d4e16832 :
>>>>>                 vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream
>>>>>                 const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d4e16ced :
>>>>>                 vtkClientServerInterpreter::ProcessStream(vtkClientServerStream
>>>>>                 const&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d5b436d4 :
>>>>>                 vtkSIProperty::ProcessMessage(vtkClientServerStream&)
>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d5b4377e :
>>>>>                 vtkSIProperty::Push(paraview_protobuf::Message*,
>>>>>                 int)
>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d5b4459e :
>>>>>                 vtkSIProxy::Push(paraview_protobuf::Message*)
>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d5b2884a :
>>>>>                 vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*)
>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d5b27484 :
>>>>>                 vtkPVSessionCore::PushState(paraview_protobuf::Message*)
>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d5b2514d :
>>>>>                 vtkPVSessionBase::PushState(paraview_protobuf::Message*)
>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d5d859b7 : vtkSMProxy::UpdateProperty(char
>>>>>                 const*, int)
>>>>>                 [(libvtkPVServerManagerCore-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54d6d8aa07 : pqVCRController::onPlay()
>>>>>                 [(libvtkpqComponents-pv4.3.so.1) ???:-1]
>>>>>                 0x7f54cfa98258 : QMetaObject::activate(QObject*,
>>>>>                 QMetaObject const*, int, void**) [(libQtCore.so.4)
>>>>>                 ???:-1]
>>>>>                 0x7f54d01102f2 : QAction::triggered(bool)
>>>>>                 [(libQtGui.so.4) ???:-1]
>>>>>                 0x7f54d0111710 :
>>>>>                 QAction::activate(QAction::ActionEvent)
>>>>>                 [(libQtGui.so.4) ???:-1]
>>>>>                 0x7f54d04fd514 : ??? [(???) ???:-1]
>>>>>                 0x7f54d04fd7ab :
>>>>>                 QAbstractButton::mouseReleaseEvent(QMouseEvent*)
>>>>>                 [(libQtGui.so.4) ???:-1]
>>>>>                 0x7f54d05d15ea :
>>>>>                 QToolButton::mouseReleaseEvent(QMouseEvent*)
>>>>>                 [(libQtGui.so.4) ???:-1]
>>>>>                 0x7f54d0175ac1 : QWidget::event(QEvent*)
>>>>>                 [(libQtGui.so.4) ???:-1]
>>>>>                 0x7f54d04fca3f : QAbstractButton::event(QEvent*)
>>>>>                 [(libQtGui.so.4) ???:-1]
>>>>>                 0x7f54d05d422d : QToolButton::event(QEvent*)
>>>>>                 [(libQtGui.so.4) ???:-1]
>>>>>                 0x7f54d011759e :
>>>>>                 QApplicationPrivate::notify_helper(QObject*,
>>>>>                 QEvent*) [(libQtGui.so.4) ???:-1]
>>>>>                 0x7f54d011e533 : QApplication::notify(QObject*,
>>>>>                 QEvent*) [(libQtGui.so.4) ???:-1]
>>>>>                 0x7f54cfa802f3 :
>>>>>                 QCoreApplication::notifyInternal(QObject*,
>>>>>                 QEvent*) [(libQtCore.so.4) ???:-1]
>>>>>                 0x7f54d011a656 :
>>>>>                 QApplicationPrivate::sendMouseEvent(QWidget*,
>>>>>                 QMouseEvent*, QWidget*, QWidget*, QWidget**,
>>>>>                 QPointer<QWidget>&, bool) [(libQtGui.so.4) ???:-1]
>>>>>                 0x7f54d019ca94 : ??? [(???) ???:-1]
>>>>>                 0x7f54d019b877 :
>>>>>                 QApplication::x11ProcessEvent(_XEvent*)
>>>>>                 [(libQtGui.so.4) ???:-1]
>>>>>                 0x7f54d01c4805 : ??? [(???) ???:-1]
>>>>>                 0x7f54cfa7f375 :
>>>>>                 QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
>>>>>                 [(libQtCore.so.4) ???:-1]
>>>>>                 0x7f54cfa7f748 :
>>>>>                 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
>>>>>                 [(libQtCore.so.4) ???:-1]
>>>>>                 0x7f54cfa8414b : QCoreApplication::exec()
>>>>>                 [(libQtCore.so.4) ???:-1]
>>>>>                 0x407785 : main [(paraview) ???:-1]
>>>>>                 0x7f54ce06cec5 : __libc_start_main [(libc.so.6)
>>>>>                 ???:-1]
>>>>>                 0x4074da : QMainWindow::event(QEvent*) [(paraview)
>>>>>                 ???:-1]
>>>>>                 =========================================================
>>>>>
>>>>>                 Thanks,
>>>>>
>>>>>                 Sergi Mateo
>>>>>                 sergi.mateo.bellido at gmail.com
>>>>>                 <mailto:sergi.mateo.bellido at gmail.com>
>>>>>
>>>>>                 _______________________________________________
>>>>>                 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
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>             -- 
>>>>>             Cory Quammen
>>>>>             R&D Engineer
>>>>>             Kitware, Inc.
>>>>
>>>>
>>>>
>>>>
>>>>         -- 
>>>>         Cory Quammen
>>>>         R&D Engineer
>>>>         Kitware, Inc.
>>>
>>>
>>>
>>>
>>>     -- 
>>>     Cory Quammen
>>>     R&D Engineer
>>>     Kitware, Inc.
>>
>>
>>
>>
>> -- 
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150717/7028f7e3/attachment-0001.html>

From aashish.chaudhary at kitware.com  Fri Jul 17 10:22:14 2015
From: aashish.chaudhary at kitware.com (Aashish Chaudhary)
Date: Fri, 17 Jul 2015 10:22:14 -0400
Subject: [Paraview] GPU volume rendering failure on Intel HD XXXX/Iris,
 Windows and recent drivers
In-Reply-To: <CAC9gB0ArB3vVBbcQnk-52ymwKYpBuk7ZLRXJD8-RevF7NRGg6w@mail.gmail.com>
References: <CAC9gB0ArB3vVBbcQnk-52ymwKYpBuk7ZLRXJD8-RevF7NRGg6w@mail.gmail.com>
Message-ID: <CAEw35Z9KtCZn2MBYaom=8AYocGLJMypMfSf0hZ3m1pUkfhzdXA@mail.gmail.com>

Dear Simon,

On Fri, Jul 17, 2015 at 4:43 AM, Simon ESNEAULT <simon.esneault at gmail.com>
wrote:

> Hi All,
>
> We're experiencing GPU volume rendering failure on a lot (maybe all ?)
> Intel HD windows system with up to date drivers.
>
> This is reproducible in Paraview or with the GPURenderDemo example from
> VTK, just load a volume and try to render the volume... Here is a result
> image from paraview on a Dell Latitude E7450 (Intel HD 5500 inside), with
> GPU rendering [1] and the same volume with CPU VR rendering [2].
> Interestingly, the volume rendering used to work with drivers older or
> equal to the version 10.18.10.3496 [3]. As a work around, we ask our
> customers to downgrade their driver version to this one, and they're
> enjoying smooth GPU rendering. But this driver is quite old and does not
> support recent chipset...
>
> I've built and tested the GPURenderDemo with the brand new OpenGL2 backend
> on an affected machine and of course it does work out of the box
> (congratulations for this amazing work !).
>
Great!


> But our application is FDA/CE marked and we need to wait that this new
> backend is completely ready for prime time. So for now, we have to stick
> with VTK 6.1 ...
>

Most of the tests are passing for OpenGL2 (
https://open.cdash.org/index.php?project=VTK) on most of the dashboards
(various configurations etc) but it is a moving target just like VTK itself
is a moving target. I guess you are waiting for a VTK release that defaults
to OpenGL2 as oppose to OpenGL?

>
> Anyone has any clue ? They're some warning that pop up from paraview
> related to the extension "gl_version_1_2" that could not be loaded, not
> sure if that could be related ? Following this thread [4] and the fix
> proposed, I've tried to replace
> /*****************/
> extensions->LoadExtension("GL_VERSION_1_2")
> /*****************/
> by
> /*****************/
> extensions->LoadExtension("GL_EXT_texture3D");
> extensions->LoadExtension( "GL_ARB_texture_non_power_of_two" );
> /*****************/
> in the vtkOpenGLGPUVolumeRayCastMapper.cxx, The warning disappears but
> there is still no volume rendering (tested with GPURenderDemo). Maybe it
> needs some others extensions ?
>

Yes, there is a patch and I can send it to you. I have to talk to folks
here if we can fix the old mapper with those changes but as of now it is
not in the plan.


>
> Should I fill a bug in paraview, vtk ? Are there any plan to maintain and
> maybe fix this for the old backend ?
>

- Aashish


>
> Thanks,
> --
> ------------------------------------------------------------------
> Simon Esneault
> Rennes, France
> ------------------------------------------------------------------
>
> [1] http://picpaste.com/pics/Paraview-4-3-1-GPU-VR_fail.1437122217.PNG
> [2] http://picpaste.com/pics/Paraview-4-3-1-CPU-VR_win.1437122267.PNG
> [3] https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23339
> [4] http://public.kitware.com/pipermail/vtkusers/2014-April/083584.html
>
> _______________________________________________
> 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
>
>


-- 



*| Aashish Chaudhary | Technical Leader         | Kitware Inc.            *
*| http://www.kitware.com/company/team/chaudhary.html
<http://www.kitware.com/company/team/chaudhary.html>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150717/7fbf8c90/attachment.html>

From simon.esneault at gmail.com  Fri Jul 17 11:34:43 2015
From: simon.esneault at gmail.com (Simon ESNEAULT)
Date: Fri, 17 Jul 2015 17:34:43 +0200
Subject: [Paraview] GPU volume rendering failure on Intel HD XXXX/Iris,
 Windows and recent drivers
In-Reply-To: <CAEw35Z9KtCZn2MBYaom=8AYocGLJMypMfSf0hZ3m1pUkfhzdXA@mail.gmail.com>
References: <CAC9gB0ArB3vVBbcQnk-52ymwKYpBuk7ZLRXJD8-RevF7NRGg6w@mail.gmail.com>
 <CAEw35Z9KtCZn2MBYaom=8AYocGLJMypMfSf0hZ3m1pUkfhzdXA@mail.gmail.com>
Message-ID: <CAC9gB0B=OJ4YBQa=hs=3J=X-4nfEQ3VBqyUSgQG-=LDJSSA6Bg@mail.gmail.com>

Dear Aashish,

Thank you very much for you answer.
Yes you are right, we are waiting for a new VTK release that defaults to
the new OpenGL2 backend, for safety and because a change of VTK version
requires a lot of extra work with our current framework... But the green
dashboard indeed looks really promising, and we will probably make the move
as soon as it's ready !

Meanwhile, I would be really glad if you could send me the patch that
solves this issue with the old backend, or guide me through the needed
modification to make it work.

Thanks again
Simon

2015-07-17 16:22 GMT+02:00 Aashish Chaudhary <aashish.chaudhary at kitware.com>
:

> Dear Simon,
>
> On Fri, Jul 17, 2015 at 4:43 AM, Simon ESNEAULT <simon.esneault at gmail.com>
> wrote:
>
>> Hi All,
>>
>> We're experiencing GPU volume rendering failure on a lot (maybe all ?)
>> Intel HD windows system with up to date drivers.
>>
>> This is reproducible in Paraview or with the GPURenderDemo example from
>> VTK, just load a volume and try to render the volume... Here is a result
>> image from paraview on a Dell Latitude E7450 (Intel HD 5500 inside), with
>> GPU rendering [1] and the same volume with CPU VR rendering [2].
>> Interestingly, the volume rendering used to work with drivers older or
>> equal to the version 10.18.10.3496 [3]. As a work around, we ask our
>> customers to downgrade their driver version to this one, and they're
>> enjoying smooth GPU rendering. But this driver is quite old and does not
>> support recent chipset...
>>
>> I've built and tested the GPURenderDemo with the brand new OpenGL2
>> backend on an affected machine and of course it does work out of the box
>> (congratulations for this amazing work !).
>>
> Great!
>
>
>> But our application is FDA/CE marked and we need to wait that this new
>> backend is completely ready for prime time. So for now, we have to stick
>> with VTK 6.1 ...
>>
>
> Most of the tests are passing for OpenGL2 (
> https://open.cdash.org/index.php?project=VTK) on most of the dashboards
> (various configurations etc) but it is a moving target just like VTK itself
> is a moving target. I guess you are waiting for a VTK release that defaults
> to OpenGL2 as oppose to OpenGL?
>
>>
>> Anyone has any clue ? They're some warning that pop up from paraview
>> related to the extension "gl_version_1_2" that could not be loaded, not
>> sure if that could be related ? Following this thread [4] and the fix
>> proposed, I've tried to replace
>> /*****************/
>> extensions->LoadExtension("GL_VERSION_1_2")
>> /*****************/
>> by
>> /*****************/
>> extensions->LoadExtension("GL_EXT_texture3D");
>> extensions->LoadExtension( "GL_ARB_texture_non_power_of_two" );
>> /*****************/
>> in the vtkOpenGLGPUVolumeRayCastMapper.cxx, The warning disappears but
>> there is still no volume rendering (tested with GPURenderDemo). Maybe it
>> needs some others extensions ?
>>
>
> Yes, there is a patch and I can send it to you. I have to talk to folks
> here if we can fix the old mapper with those changes but as of now it is
> not in the plan.
>
>
>>
>> Should I fill a bug in paraview, vtk ? Are there any plan to maintain and
>> maybe fix this for the old backend ?
>>
>
> - Aashish
>
>
>>
>> Thanks,
>> --
>> ------------------------------------------------------------------
>> Simon Esneault
>> Rennes, France
>> ------------------------------------------------------------------
>>
>> [1] http://picpaste.com/pics/Paraview-4-3-1-GPU-VR_fail.1437122217.PNG
>> [2] http://picpaste.com/pics/Paraview-4-3-1-CPU-VR_win.1437122267.PNG
>> [3] https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23339
>> [4] http://public.kitware.com/pipermail/vtkusers/2014-April/083584.html
>>
>> _______________________________________________
>> 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
>>
>>
>
>
> --
>
>
>
> *| Aashish Chaudhary | Technical Leader         | Kitware Inc.            *
> *| http://www.kitware.com/company/team/chaudhary.html
> <http://www.kitware.com/company/team/chaudhary.html>*
>



-- 
------------------------------------------------------------------
Simon Esneault
Rennes, France
------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150717/4f4a527b/attachment.html>

From utkarsh.ayachit at kitware.com  Fri Jul 17 14:29:43 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 17 Jul 2015 18:29:43 +0000
Subject: [Paraview] Update: Upcoming ParaView Releases (4.4 and 5.0)
Message-ID: <CADHSJjAJS1YR9gHfAte4f5Ga+ij0vGghSQ21Hto+uYX+JbhWiw@mail.gmail.com>

Folks,

Since we're getting close to the next release, I just wanted to send out an
email to let everyone know how we're planning to do the next release.

+ We'll do a ParaView 4.4 release will all features/fixes planned for the
next release. This will use the older rendering code (same as previous
release) that doesn't using OpenGL 2+ features.

+  Following the same pattern as VTK, soon after (at the same time, if
possible), we'll release ParaView 5.0. This will be ParaView 4.4 but with
OpenGL2 backend.

The main reason for this separation would be to have a fallback in case
showstopper issues are noticed with the major rendering changes and for
legacy systems that don't have a newer OpenGL.

Any thoughts? Comments? Suggestions? If things go according to plan,
release candidates should start popping up mid/late August.

Utkarsh

p.s. Originally, we also intended to upgrade ParaView 5.0 to use Qt 5, by
default. However, there are a few outstanding issues with Qt 5 (some in Qt
5 itself, and some in our testing code) and hence the upgrade to Qt 5 has
been tabled for now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150717/2da9dc62/attachment.html>

From berk.geveci at kitware.com  Fri Jul 17 14:38:58 2015
From: berk.geveci at kitware.com (Berk Geveci)
Date: Fri, 17 Jul 2015 14:38:58 -0400
Subject: [Paraview] Open Position Research Programmer
Message-ID: <CAE32kpXu004+DuR4nUnvtBj8PtWYEY=y6RFr3Z-q_3mqcVEN5w@mail.gmail.com>

Hi folks,

This is from our friends at the UIUC Parallel Programming Laboratory:

Now accepting applications for Visiting Research Programmer

Close date: Monday, August 3, 2015 (extended)

The primary functions of the position are to extend the OpenAtom software
and to develop the Argo exascale operating system prototype. Working with
the senior research programmer and research staff, the visiting research
programmer will help improve Charm++ functionalities as necessary for these
and other projects as well as write software for parallel supercomputers
and clusters.

See full description at:

http://charm.cs.illinois.edu/career

Best,
-berk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150717/1614f496/attachment.html>

From arctica1963 at gmail.com  Fri Jul 17 18:50:03 2015
From: arctica1963 at gmail.com (Lester Anderson)
Date: Fri, 17 Jul 2015 23:50:03 +0100
Subject: [Paraview] Update: Upcoming ParaView Releases (4.4 and 5.0)
In-Reply-To: <CADHSJjAJS1YR9gHfAte4f5Ga+ij0vGghSQ21Hto+uYX+JbhWiw@mail.gmail.com>
References: <CADHSJjAJS1YR9gHfAte4f5Ga+ij0vGghSQ21Hto+uYX+JbhWiw@mail.gmail.com>
Message-ID: <CAE3taFDRHUwDY=46R2SLJQLoJd0bMcbvnu9LEF1Pv3NnqyEQkg@mail.gmail.com>

With reference to OpenGL, will the new updates via 4,4 or 5 be compatible
with Windows 7(or 8) or does it expect a newer version of OpenGL on the
target system?
thanks

On 17 July 2015 at 19:29, Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
wrote:

> Folks,
>
> Since we're getting close to the next release, I just wanted to send out
> an email to let everyone know how we're planning to do the next release.
>
> + We'll do a ParaView 4.4 release will all features/fixes planned for the
> next release. This will use the older rendering code (same as previous
> release) that doesn't using OpenGL 2+ features.
>
> +  Following the same pattern as VTK, soon after (at the same time, if
> possible), we'll release ParaView 5.0. This will be ParaView 4.4 but with
> OpenGL2 backend.
>
> The main reason for this separation would be to have a fallback in case
> showstopper issues are noticed with the major rendering changes and for
> legacy systems that don't have a newer OpenGL.
>
> Any thoughts? Comments? Suggestions? If things go according to plan,
> release candidates should start popping up mid/late August.
>
> Utkarsh
>
> p.s. Originally, we also intended to upgrade ParaView 5.0 to use Qt 5, by
> default. However, there are a few outstanding issues with Qt 5 (some in Qt
> 5 itself, and some in our testing code) and hence the upgrade to Qt 5 has
> been tabled for now.
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150717/2b04375f/attachment.html>

From lmorandini at ieee.org  Fri Jul 17 19:26:09 2015
From: lmorandini at ieee.org (Luca Morandini)
Date: Sat, 18 Jul 2015 09:26:09 +1000
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAOqyOuGFFOHjMazR6EOwixVJ2LbH=5849VVCx2woC1CaJuS4KQ@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <mo2q49$4gt$1@ger.gmane.org>
 <CAOqyOuGT2uONXRjPd80bJOBdnhugTMyyUCHGn6s8H4Aw+i1wOg@mail.gmail.com>
 <mo7cvk$ria$1@ger.gmane.org>
 <CAOqyOuFMFju6ODKyehDU1pDdH1Z=A79wc0iy8KK3m11mziLMPQ@mail.gmail.com>
 <moaask$ejm$1@ger.gmane.org>
 <CAOqyOuGFFOHjMazR6EOwixVJ2LbH=5849VVCx2woC1CaJuS4KQ@mail.gmail.com>
Message-ID: <moc2uj$o6b$1@ger.gmane.org>

On 17/07/15 22:54, Casey Goodlett wrote:
> Can you request a wiki account and update the page with any instructions you found
> helpful?
>
> You could also create a pull request to create an instructions file on the github
> page or create a page on the github wiki https://github.com/Kitware/PCLPlugin/wiki .

It would be my pleasure to give something back to the community.

As per the best way to do it, hmm... I'd rather like build documentation to be as 
close to the source code as possible, lest they diverge. Therefore, I would prefer 
updating the readme on the GitHub repo and drop the "Download And Build 
Instructions" wiki page: what do you think?

Regards,

Luca Morandini
Data Architect - AURIN project
Melbourne eResearch Group
Department of Computing and Information Systems
University of Melbourne
Tel. +61 03 903 58 380
Skype: lmorandini


From berk.geveci at kitware.com  Fri Jul 17 19:59:18 2015
From: berk.geveci at kitware.com (Berk Geveci)
Date: Fri, 17 Jul 2015 19:59:18 -0400
Subject: [Paraview] CFP: SC '15 Scientific Visualization Showcase
Message-ID: <CAE32kpVcWLAKqNTH87H+RKe40EYKGy8VT6eL7w4axK3Lk5jw5g@mail.gmail.com>

Hi folks,

Just a reminder that the deadline for the Scientific Visualization Showcase
is near.

Best,
-berk

On Tue, May 26, 2015 at 8:19 AM, Berk Geveci <berk.geveci at kitware.com>
wrote:

> Hi folks,
>
> The Call for Participation for the SC '15 Scientific Visualization
> Showcase is out. This is a great opportunity for the community to highlight
> the wonderful visualization work going on. Please consider submitting an
> entry (or more).
>
> http://sc15.supercomputing.org/program/scientific-visualization-showcase
>
> SC15?s Visualization and Data Analytics Showcase Program provides a forum
> for the year's most instrumental movies in HPC.  Six finalists will compete
> for the Best Visualization Award, and each finalist will present his or her
> movie during a dedicated session at SC15 in a 15-minute presentation.
> Movies are judged based on how their movie illuminates science, by the
> quality of the movie, and for innovations in the process used for creating
> the movie.
>
> Best,
> -berk
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150717/78f3e751/attachment.html>

From marie.kajan at gmail.com  Fri Jul 17 20:49:35 2015
From: marie.kajan at gmail.com (Marie Kajan)
Date: Fri, 17 Jul 2015 20:49:35 -0400
Subject: [Paraview] Transforming a spherical slice into a map projection
In-Reply-To: <CADHSJjAZmDV+7QY7VqAEMxWtumyDK08fGyjpWT8T-JwVY8y4og@mail.gmail.com>
References: <CAK3vnGc2pHaxZXhGtto8JzOo6Nu_UL84+rEMES6z5-x6Ei+=bw@mail.gmail.com>
 <CADHSJjAZmDV+7QY7VqAEMxWtumyDK08fGyjpWT8T-JwVY8y4og@mail.gmail.com>
Message-ID: <CAK3vnGf8e_AHmruBokgujpBCqyA44_A1eX2dwxNSEN0WvkdjUw@mail.gmail.com>

Hi Utkarsh,

Here's a small sample (plus the saved state for a sample slice, if that
helps):

https://www.dropbox.com/s/hpp2y8bbkjn34z3/solution-00000.0000.vtk?dl=0
https://www.dropbox.com/s/94rfo305ljeqtgk/solution-00000.pvsm?dl=0

Thanks a lot!

Marie


On Wed, Jul 15, 2015 at 10:41 PM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> Marie,
>
> Do you have a sample dataset? That'll make it easier to determine the
> filters etc. you can apply.
>
> Utkarsh
>
> On Wed, Jul 15, 2015 at 8:03 PM, Marie Kajan <marie.kajan at gmail.com>
> wrote:
> > I'm a new user and am having difficulty navigating Paraview. I would
> really
> > appreciate any pointers!
> >
> > I'm using code called ASPECT (aspect.dealii.org) to generate models of
> the
> > Earth's interior. My data are unstructured grids that contain different
> data
> > arrays: velocity, temperature, etc. I hope that makes sense. I have a
> > spherical volume, essentially. I know how to play around with the basic
> > filters, and I'm able to take spherical slices which represent
> > velocity/temperature/etc. fields at different depths in the Earth.
> >
> > But, I'm not sure how to "flatten" these slices into a map projection
> (for
> > example, a simple rectangle with latitude-longitude axes). Most tutorials
> > don't deal with VTK inputs and I'm not familiar enough with Paraview to
> > figure out my own script.
> >
> > Thanks!
> >
> > Marie
> >
> > _______________________________________________
> > 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
> >
>



-- 

Centre GEOTOP
Universit? du Qu?bec ? Montr?al
C.P. 8888, succursale Centre-ville
Montr?al, QC  H3C 3P8

+1-514-987-3000 x4600
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150717/1fe4f746/attachment.html>

From lmorandini at ieee.org  Sat Jul 18 03:21:20 2015
From: lmorandini at ieee.org (Luca Morandini)
Date: Sat, 18 Jul 2015 17:21:20 +1000
Subject: [Paraview] Point clouds and computing PCA on voxels
Message-ID: <mocupi$4m1$1@ger.gmane.org>

Folks,

I would like to compute PCA on some LIDAR data in order to tell, say, walls from 
cables. Therefore, it would be useful to know the eigenvectors/eigenvalues of the 
point clouds belonging to voxels of different sizes.

However, I have been unable so far to find a way to achieve this in ParaView, 
possibly using Python: can someone be so benevolent as to show me the way?

Regards,

Luca Morandini
Data Architect - AURIN project
Melbourne eResearch Group
Department of Computing and Information Systems
University of Melbourne
Tel. +61 03 903 58 380
Skype: lmorandini


From S.R.Kharche at exeter.ac.uk  Sat Jul 18 07:04:03 2015
From: S.R.Kharche at exeter.ac.uk (Kharche, Sanjay)
Date: Sat, 18 Jul 2015 11:04:03 +0000
Subject: [Paraview] non-interactive viz on cluster
In-Reply-To: <mocupi$4m1$1@ger.gmane.org>
References: <mocupi$4m1$1@ger.gmane.org>
Message-ID: <VI1PR03MB10718AA847D1243BC64882FD82870@VI1PR03MB1071.eurprd03.prod.outlook.com>


Dear All

I need to non-interactively make png images of a series of sequentially
numbered vts/vtk files. Since this is a large amount of data, I would like
to do this using a cluster. The cluster has paraview and OpenFoam. I am not
very familiar with OpenFoam, and have just started using Paraview in
terms of python scripts. When I submit the job, I get an error. I gather
that the error is because there is always a blank Paraview OpenGL window
that opens when I use the script below. Can someone suggest a solution?

thanks
Sanjay

error from the pbs job:
ERROR: In /home/kitware/Kitware/ParaView-3.10/source/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 541
vtkXOpenGLRenderWindow (0x1ba5ad0): bad X server connection. DISPLAY=ERROR: In /home/kitware/Kitware/ParaView-3.10/source/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 343
vtkXOpenGLRenderWindow (0x1ba5ad0): bad X server connection. DISPLAY=

My python script that I created using the GUI, and then edited for writing the png is below. I run it using the
non screen rendering option:

pvbatch --use-offscreen-rendering mouse2d.py &

mouse2d.py is this:

try: paraview.simple
except: from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()

# this does not make a difference to the viz.
# SetActiveView(GetRenderView())
# GetActiveView().UseOffscreenRenderingForScreenshots = 1

# loop through all files.
for i in range (1,3999):
	mouse2D_SAN1_vts = XMLStructuredGridReader( FileName=['mouse2D_SAN%d.vts' % (i)] )
	mouse2D_SAN1_vts.PointArrayStatus = ['Unnamed0']
	RenderView1 = GetRenderView()
	DataRepresentation1 = Show()
	DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
	RenderView1.CenterOfRotation = [78.0, 58.5, 0.0]
	Transform1 = Transform( Transform="Transform" )
	a1_Unnamed0_PVLookupTable = GetLookupTableForArray( "Unnamed0", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[-0.01, 0.23, 0.299, 0.754, 1.0, 0.706, 0.016, 0.15], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
	a1_Unnamed0_PiecewiseFunction = CreatePiecewiseFunction()
	RenderView1.CameraPosition = [78.0, 58.5, 376.71107225273664]
	RenderView1.CameraFocalPoint = [78.0, 58.5, 0.0]
	RenderView1.CameraClippingRange = [372.94396153020926, 382.3617383365277]
	RenderView1.CameraParallelScale = 97.5
	DataRepresentation1.ColorArrayName = 'Unnamed0'
	DataRepresentation1.LookupTable = a1_Unnamed0_PVLookupTable
	Transform1.Transform = "Transform"
	DataRepresentation2 = Show()
	DataRepresentation2.ColorArrayName = 'Unnamed0'
	DataRepresentation2.LookupTable = a1_Unnamed0_PVLookupTable
	DataRepresentation2.EdgeColor = [0.0, 0.0, 0.5000076295109483]
	DataRepresentation1.Visibility = 0

	Transform1.Transform.Scale = [1.0, -1.0, 0.0]
	RenderView1.CenterAxesVisibility = 0
	RenderView1.CameraPosition = [78.0, -58.5, 376.71107225273664]
	RenderView1.OrientationAxesVisibility = 0
	RenderView1.CameraFocalPoint = [78.0, -58.5, 0.0]
	RenderView1.CenterOfRotation = [78.0, -58.5, 0.0]
#	Render()
	WriteImage("dir_%i.png" % (i))

From dave.demarle at kitware.com  Sat Jul 18 10:08:54 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Sat, 18 Jul 2015 10:08:54 -0400
Subject: [Paraview] non-interactive viz on cluster
In-Reply-To: <VI1PR03MB10718AA847D1243BC64882FD82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
References: <mocupi$4m1$1@ger.gmane.org>
 <VI1PR03MB10718AA847D1243BC64882FD82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
Message-ID: <CANjZAi8Cf76WG94RxsF=BytrX-03xRG70s2-eGpAX0mzAmTHfQ@mail.gmail.com>

The error message indicates that pv batch can not connect the xwindows.
If the cluster is configured to run X for you, ensure that the job has the
correct DISPLAY environment variable.
If not, you should either start X in the job ("xinit pvbatch" or something
like that) or recompile paraview to use offscreen rendering.


On Saturday, July 18, 2015, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk>
wrote:

>
> Dear All
>
> I need to non-interactively make png images of a series of sequentially
> numbered vts/vtk files. Since this is a large amount of data, I would like
> to do this using a cluster. The cluster has paraview and OpenFoam. I am not
> very familiar with OpenFoam, and have just started using Paraview in
> terms of python scripts. When I submit the job, I get an error. I gather
> that the error is because there is always a blank Paraview OpenGL window
> that opens when I use the script below. Can someone suggest a solution?
>
> thanks
> Sanjay
>
> error from the pbs job:
> ERROR: In
> /home/kitware/Kitware/ParaView-3.10/source/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
> line 541
> vtkXOpenGLRenderWindow (0x1ba5ad0): bad X server connection.
> DISPLAY=ERROR: In
> /home/kitware/Kitware/ParaView-3.10/source/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
> line 343
> vtkXOpenGLRenderWindow (0x1ba5ad0): bad X server connection. DISPLAY=
>
> My python script that I created using the GUI, and then edited for writing
> the png is below. I run it using the
> non screen rendering option:
>
> pvbatch --use-offscreen-rendering mouse2d.py &
>
> mouse2d.py is this:
>
> try: paraview.simple
> except: from paraview.simple import *
> paraview.simple._DisableFirstRenderCameraReset()
>
> # this does not make a difference to the viz.
> # SetActiveView(GetRenderView())
> # GetActiveView().UseOffscreenRenderingForScreenshots = 1
>
> # loop through all files.
> for i in range (1,3999):
>         mouse2D_SAN1_vts = XMLStructuredGridReader(
> FileName=['mouse2D_SAN%d.vts' % (i)] )
>         mouse2D_SAN1_vts.PointArrayStatus = ['Unnamed0']
>         RenderView1 = GetRenderView()
>         DataRepresentation1 = Show()
>         DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
>         RenderView1.CenterOfRotation = [78.0, 58.5, 0.0]
>         Transform1 = Transform( Transform="Transform" )
>         a1_Unnamed0_PVLookupTable = GetLookupTableForArray( "Unnamed0", 1,
> NanColor=[0.25, 0.0, 0.0], RGBPoints=[-0.01, 0.23, 0.299, 0.754, 1.0,
> 0.706, 0.016, 0.15], VectorMode='Magnitude', ColorSpace='Diverging',
> LockScalarRange=1 )
>         a1_Unnamed0_PiecewiseFunction = CreatePiecewiseFunction()
>         RenderView1.CameraPosition = [78.0, 58.5, 376.71107225273664]
>         RenderView1.CameraFocalPoint = [78.0, 58.5, 0.0]
>         RenderView1.CameraClippingRange = [372.94396153020926,
> 382.3617383365277]
>         RenderView1.CameraParallelScale = 97.5
>         DataRepresentation1.ColorArrayName = 'Unnamed0'
>         DataRepresentation1.LookupTable = a1_Unnamed0_PVLookupTable
>         Transform1.Transform = "Transform"
>         DataRepresentation2 = Show()
>         DataRepresentation2.ColorArrayName = 'Unnamed0'
>         DataRepresentation2.LookupTable = a1_Unnamed0_PVLookupTable
>         DataRepresentation2.EdgeColor = [0.0, 0.0, 0.5000076295109483]
>         DataRepresentation1.Visibility = 0
>
>         Transform1.Transform.Scale = [1.0, -1.0, 0.0]
>         RenderView1.CenterAxesVisibility = 0
>         RenderView1.CameraPosition = [78.0, -58.5, 376.71107225273664]
>         RenderView1.OrientationAxesVisibility = 0
>         RenderView1.CameraFocalPoint = [78.0, -58.5, 0.0]
>         RenderView1.CenterOfRotation = [78.0, -58.5, 0.0]
> #       Render()
>         WriteImage("dir_%i.png" % (i))
> _______________________________________________
> 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
>


-- 
David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150718/c99d931d/attachment.html>

From S.R.Kharche at exeter.ac.uk  Sat Jul 18 15:26:49 2015
From: S.R.Kharche at exeter.ac.uk (Kharche, Sanjay)
Date: Sat, 18 Jul 2015 19:26:49 +0000
Subject: [Paraview] non-interactive viz on cluster
In-Reply-To: <CANjZAi8Cf76WG94RxsF=BytrX-03xRG70s2-eGpAX0mzAmTHfQ@mail.gmail.com>
References: <mocupi$4m1$1@ger.gmane.org>
 <VI1PR03MB10718AA847D1243BC64882FD82870@VI1PR03MB1071.eurprd03.prod.outlook.com>,
 <CANjZAi8Cf76WG94RxsF=BytrX-03xRG70s2-eGpAX0mzAmTHfQ@mail.gmail.com>
Message-ID: <VI1PR03MB107148468CDDC0E8ABA82C2E82870@VI1PR03MB1071.eurprd03.prod.outlook.com>


Hi


It looks like that my question is more for pbs/torque rather than paraview.

But I will still ask.


I am not wanting to do the visualisation using the PBS -X option, which

will forward the X11 graphics from the compute mnodes to my desktop screen.

I want to do it completely non-interactively. I could not find any other way of

changing the DISPLAY variable. If there is one, please suggest.


In the meantime, I am trying to find out of the paraview on our cluster is

compiled to use off screen rendering. I will also try to have a go at using

some precompiled binaries (pvbatch) if I can find any.


cheers

Sanjay


________________________________
From: David E DeMarle <dave.demarle at kitware.com>
Sent: 18 July 2015 02:08
To: Kharche, Sanjay
Cc: paraview at paraview.org
Subject: Re: [Paraview] non-interactive viz on cluster


The error message indicates that pv batch can not connect the xwindows.
If the cluster is configured to run X for you, ensure that the job has the correct DISPLAY environment variable.
If not, you should either start X in the job ("xinit pvbatch" or something like that) or recompile paraview to use offscreen rendering.


On Saturday, July 18, 2015, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk<mailto:S.R.Kharche at exeter.ac.uk>> wrote:

Dear All

I need to non-interactively make png images of a series of sequentially
numbered vts/vtk files. Since this is a large amount of data, I would like
to do this using a cluster. The cluster has paraview and OpenFoam. I am not
very familiar with OpenFoam, and have just started using Paraview in
terms of python scripts. When I submit the job, I get an error. I gather
that the error is because there is always a blank Paraview OpenGL window
that opens when I use the script below. Can someone suggest a solution?

thanks
Sanjay

error from the pbs job:
ERROR: In /home/kitware/Kitware/ParaView-3.10/source/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 541
vtkXOpenGLRenderWindow (0x1ba5ad0): bad X server connection. DISPLAY=ERROR: In /home/kitware/Kitware/ParaView-3.10/source/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 343
vtkXOpenGLRenderWindow (0x1ba5ad0): bad X server connection. DISPLAY=

My python script that I created using the GUI, and then edited for writing the png is below. I run it using the
non screen rendering option:

pvbatch --use-offscreen-rendering mouse2d.py &

mouse2d.py is this:

try: paraview.simple
except: from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()

# this does not make a difference to the viz.
# SetActiveView(GetRenderView())
# GetActiveView().UseOffscreenRenderingForScreenshots = 1

# loop through all files.
for i in range (1,3999):
        mouse2D_SAN1_vts = XMLStructuredGridReader( FileName=['mouse2D_SAN%d.vts' % (i)] )
        mouse2D_SAN1_vts.PointArrayStatus = ['Unnamed0']
        RenderView1 = GetRenderView()
        DataRepresentation1 = Show()
        DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
        RenderView1.CenterOfRotation = [78.0, 58.5, 0.0]
        Transform1 = Transform( Transform="Transform" )
        a1_Unnamed0_PVLookupTable = GetLookupTableForArray( "Unnamed0", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[-0.01, 0.23, 0.299, 0.754, 1.0, 0.706, 0.016, 0.15], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
        a1_Unnamed0_PiecewiseFunction = CreatePiecewiseFunction()
        RenderView1.CameraPosition = [78.0, 58.5, 376.71107225273664]
        RenderView1.CameraFocalPoint = [78.0, 58.5, 0.0]
        RenderView1.CameraClippingRange = [372.94396153020926, 382.3617383365277]
        RenderView1.CameraParallelScale = 97.5
        DataRepresentation1.ColorArrayName = 'Unnamed0'
        DataRepresentation1.LookupTable = a1_Unnamed0_PVLookupTable
        Transform1.Transform = "Transform"
        DataRepresentation2 = Show()
        DataRepresentation2.ColorArrayName = 'Unnamed0'
        DataRepresentation2.LookupTable = a1_Unnamed0_PVLookupTable
        DataRepresentation2.EdgeColor = [0.0, 0.0, 0.5000076295109483]
        DataRepresentation1.Visibility = 0

        Transform1.Transform.Scale = [1.0, -1.0, 0.0]
        RenderView1.CenterAxesVisibility = 0
        RenderView1.CameraPosition = [78.0, -58.5, 376.71107225273664]
        RenderView1.OrientationAxesVisibility = 0
        RenderView1.CameraFocalPoint = [78.0, -58.5, 0.0]
        RenderView1.CenterOfRotation = [78.0, -58.5, 0.0]
#       Render()
        WriteImage("dir_%i.png" % (i))
_______________________________________________
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


--
David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150718/2c60d32b/attachment.html>

From berk.geveci at kitware.com  Sat Jul 18 20:17:25 2015
From: berk.geveci at kitware.com (Berk Geveci)
Date: Sat, 18 Jul 2015 20:17:25 -0400
Subject: [Paraview] Combining vtk and paraview python scripts
In-Reply-To: <55A56672.3040204@nasa.gov>
References: <55A55C2C.2030107@nasa.gov>
 <CAMaOp+GaBL5wqsU4YiQ5-VpZWqzDjPF8=oc6p950Oums+01+Zg@mail.gmail.com>
 <55A56672.3040204@nasa.gov>
Message-ID: <CAE32kpXDT5cq51PBged+9HF=pFcpEMJeZq9oJGaC6Mmqx2coSA@mail.gmail.com>

To elaborate on what Andy said, you can stick your entire VTK script in
side the programmable source. Which you can use in batch mode as well. If
you want to keep your VTK script as a reusable code, I recommend making it
a module that you import from the programmable source.

Best,
-berk

On Tue, Jul 14, 2015 at 3:43 PM, Jeff Becker <jeffrey.c.becker at nasa.gov>
wrote:

>  On 07/14/2015 12:20 PM, Andy Bauer wrote:
>
> ParaView's Python Programmable Filter and Python Programmable Source use
> VTK Python wrapping to do the work while making it available in Paraview.
> Check out http://www.paraview.org/Wiki/Python_Programmable_Filter.
>
>
> Thanks. That's pretty neat, but what I'd really like is a standalone
> script I can run in batch mode (no interaction) to generate one png file
> per timestep for all the timesteps in the data set. Essentially I'd like a
> way to construct a pipeline between the vtk.vtkImageImport()  object and
> the ParaView renderView1.
>
> -jeff
>
>
> On Tue, Jul 14, 2015 at 2:59 PM, Jeff Becker <jeffrey.c.becker at nasa.gov>
> wrote:
>
>> Hi.
>>
>> As a proof of concept, I have a vtk script that reads some binary data,
>> and produces a vti file. I then have a second script that I generated using
>> ParaView's tracing facility while viewing the data. Now I'd like to combine
>> them, so as to eliminate the intermediate file, i.e., go from binary data
>> directly to rendering. To be specific, my vtk script ends like this:
>>
>> steinbmag = steinbmag.reshape(nx,ny,nz).T
>>
>> vtkImporter = vtk.vtkImageImport()
>> vtkImporter.CopyImportVoidPointer(steinbmag, steinbmag.nbytes)
>>
>> vtkImporter.SetDataScalarTypeToFloat()
>> vtkImporter.SetNumberOfScalarComponents(1)
>> vtkImporter.SetDataExtent(0, nx-1, 0, ny-1, 0, nz-1)
>> vtkImporter.SetWholeExtent(0, nx-1, 0, ny-1, 0, nz-1)
>> vtkImporter.SetScalarArrayName('B field magnitude')
>>
>> writer=vtk.vtkXMLImageDataWriter()
>> writer.SetFileName(out_fname)
>> writer.SetInputConnection(vtkImporter.GetOutputPort())
>> writer.Write()
>>
>> and the ParaView script starts like this:
>>
>> from paraview.simple import *
>>
>> paraview.simple._DisableFirstRenderCameraReset()
>>
>> filepfx = '/nobackup/jcbecker/steinBmag_0'
>> infile = filepfx+'.vti'
>> # create a new 'XML Image Data Reader'
>> steinBmag_ = XMLImageDataReader(FileName=infile)
>> steinBmag_.CellArrayStatus = []
>> steinBmag_.PointArrayStatus = ['B field magnitude']
>>
>> # get animation scene
>> animationScene1 = GetAnimationScene()
>>
>> # update animation scene based on data timesteps
>> animationScene1.UpdateAnimationUsingDataTimeSteps()
>>
>> # get active view
>> renderView1 = GetActiveViewOrCreate('RenderView')
>> # uncomment following to set a specific view size
>> renderView1.ViewSize = [1090, 761]
>>
>> I'm looking at the VTK examples and pvpython documentation, but any help
>> is appreciated.
>>
>> Thanks.
>>
>> -jeff
>> _______________________________________________
>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150718/3dfb5dbf/attachment.html>

From utkarsh.ayachit at kitware.com  Sun Jul 19 16:08:17 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Sun, 19 Jul 2015 20:08:17 +0000
Subject: [Paraview] Update: Upcoming ParaView Releases (4.4 and 5.0)
In-Reply-To: <CAE3taFDRHUwDY=46R2SLJQLoJd0bMcbvnu9LEF1Pv3NnqyEQkg@mail.gmail.com>
References: <CADHSJjAJS1YR9gHfAte4f5Ga+ij0vGghSQ21Hto+uYX+JbhWiw@mail.gmail.com>
 <CAE3taFDRHUwDY=46R2SLJQLoJd0bMcbvnu9LEF1Pv3NnqyEQkg@mail.gmail.com>
Message-ID: <CADHSJjDB8KZNXEowrAHb+Lmem9ah4Xe=0aps93wmLt2nMkw9WA@mail.gmail.com>

Lester,

ParaView 4.4  won't have any major OpenGL related changes so it should work
on platforms ParaView 4.3 or earlier worked. ParaView 5 (with its use of
OpenGL 2.1/3.2 features) should indeed still work on Windows 7/8 with
relatively modern drivers. Note, OpenGL 3.2 is still quite old (~2009). If
you're using remote-desktop, however, you may want to switch to using VNC.
Remote desktop uses a software OpenGL implementation, which (when last I
checked) was only OpenGL 1.1 compatible.

(cc-ing Ken to correct me if I am mistaken)

Utkarsh

On Fri, Jul 17, 2015 at 6:50 PM Lester Anderson <arctica1963 at gmail.com>
wrote:

> With reference to OpenGL, will the new updates via 4,4 or 5 be compatible
> with Windows 7(or 8) or does it expect a newer version of OpenGL on the
> target system?
> thanks
>
> On 17 July 2015 at 19:29, Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> wrote:
>
>> Folks,
>>
>> Since we're getting close to the next release, I just wanted to send out
>> an email to let everyone know how we're planning to do the next release.
>>
>> + We'll do a ParaView 4.4 release will all features/fixes planned for the
>> next release. This will use the older rendering code (same as previous
>> release) that doesn't using OpenGL 2+ features.
>>
>> +  Following the same pattern as VTK, soon after (at the same time, if
>> possible), we'll release ParaView 5.0. This will be ParaView 4.4 but with
>> OpenGL2 backend.
>>
>> The main reason for this separation would be to have a fallback in case
>> showstopper issues are noticed with the major rendering changes and for
>> legacy systems that don't have a newer OpenGL.
>>
>> Any thoughts? Comments? Suggestions? If things go according to plan,
>> release candidates should start popping up mid/late August.
>>
>> Utkarsh
>>
>> p.s. Originally, we also intended to upgrade ParaView 5.0 to use Qt 5,
>> by default. However, there are a few outstanding issues with Qt 5 (some in
>> Qt 5 itself, and some in our testing code) and hence the upgrade to Qt 5
>> has been tabled for now.
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150719/22d94b57/attachment.html>

From dave.demarle at kitware.com  Sun Jul 19 21:46:41 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Sun, 19 Jul 2015 21:46:41 -0400
Subject: [Paraview] non-interactive viz on cluster
In-Reply-To: <VI1PR03MB107148468CDDC0E8ABA82C2E82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
References: <mocupi$4m1$1@ger.gmane.org>
 <VI1PR03MB10718AA847D1243BC64882FD82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi8Cf76WG94RxsF=BytrX-03xRG70s2-eGpAX0mzAmTHfQ@mail.gmail.com>
 <VI1PR03MB107148468CDDC0E8ABA82C2E82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
Message-ID: <CANjZAi-NEtA9gUL-UXGyW87PCWpAFd2qAzhc-2gLDmxBmK+qHA@mail.gmail.com>

I am not wanting to do the visualisation using the PBS -X option, which

> will forward the X11 graphics from the compute mnodes to my desktop screen.
>
> I want to do it completely non-interactively.
>

Agreed. Don't forward X, N compute nodes sending their graphics calls over
the network to your desktop is much worse than N times slower.

I could not find any other way of
>
> changing the DISPLAY variable. If there is one, please suggest.
>
>
> I think it is site specific. Talk with your sys admins about how to submit
a job that has access to X displays on the compute nodes.


>  In the meantime, I am trying to find out of the paraview on our cluster
> is
>
> compiled to use off screen rendering. I will also try to have a go at using
>
> some precompiled binaries (pvbatch) if I can find any.
>
>
> Sounds like a good backup plan. If that fails, you can compile paraview
for offscreen rendering yourself and run your own binary.


>  cheers
>
> Sanjay
>
>
good luck!


>
>  ------------------------------
> *From:* David E DeMarle <dave.demarle at kitware.com>
> *Sent:* 18 July 2015 02:08
> *To:* Kharche, Sanjay
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] non-interactive viz on cluster
>
>
> The error message indicates that pv batch can not connect the xwindows.
> If the cluster is configured to run X for you, ensure that the job has the
> correct DISPLAY environment variable.
> If not, you should either start X in the job ("xinit pvbatch" or something
> like that) or recompile paraview to use offscreen rendering.
>
>
> On Saturday, July 18, 2015, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk>
> wrote:
>
>>
>> Dear All
>>
>> I need to non-interactively make png images of a series of sequentially
>> numbered vts/vtk files. Since this is a large amount of data, I would like
>> to do this using a cluster. The cluster has paraview and OpenFoam. I am
>> not
>> very familiar with OpenFoam, and have just started using Paraview in
>> terms of python scripts. When I submit the job, I get an error. I gather
>> that the error is because there is always a blank Paraview OpenGL window
>> that opens when I use the script below. Can someone suggest a solution?
>>
>> thanks
>> Sanjay
>>
>> error from the pbs job:
>> ERROR: In
>> /home/kitware/Kitware/ParaView-3.10/source/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
>> line 541
>> vtkXOpenGLRenderWindow (0x1ba5ad0): bad X server connection.
>> DISPLAY=ERROR: In
>> /home/kitware/Kitware/ParaView-3.10/source/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
>> line 343
>> vtkXOpenGLRenderWindow (0x1ba5ad0): bad X server connection. DISPLAY=
>>
>> My python script that I created using the GUI, and then edited for
>> writing the png is below. I run it using the
>> non screen rendering option:
>>
>> pvbatch --use-offscreen-rendering mouse2d.py &
>>
>> mouse2d.py is this:
>>
>> try: paraview.simple
>> except: from paraview.simple import *
>> paraview.simple._DisableFirstRenderCameraReset()
>>
>> # this does not make a difference to the viz.
>> # SetActiveView(GetRenderView())
>> # GetActiveView().UseOffscreenRenderingForScreenshots = 1
>>
>> # loop through all files.
>> for i in range (1,3999):
>>         mouse2D_SAN1_vts = XMLStructuredGridReader(
>> FileName=['mouse2D_SAN%d.vts' % (i)] )
>>         mouse2D_SAN1_vts.PointArrayStatus = ['Unnamed0']
>>         RenderView1 = GetRenderView()
>>         DataRepresentation1 = Show()
>>         DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
>>         RenderView1.CenterOfRotation = [78.0, 58.5, 0.0]
>>         Transform1 = Transform( Transform="Transform" )
>>         a1_Unnamed0_PVLookupTable = GetLookupTableForArray( "Unnamed0",
>> 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[-0.01, 0.23, 0.299, 0.754, 1.0,
>> 0.706, 0.016, 0.15], VectorMode='Magnitude', ColorSpace='Diverging',
>> LockScalarRange=1 )
>>         a1_Unnamed0_PiecewiseFunction = CreatePiecewiseFunction()
>>         RenderView1.CameraPosition = [78.0, 58.5, 376.71107225273664]
>>         RenderView1.CameraFocalPoint = [78.0, 58.5, 0.0]
>>         RenderView1.CameraClippingRange = [372.94396153020926,
>> 382.3617383365277]
>>         RenderView1.CameraParallelScale = 97.5
>>         DataRepresentation1.ColorArrayName = 'Unnamed0'
>>         DataRepresentation1.LookupTable = a1_Unnamed0_PVLookupTable
>>         Transform1.Transform = "Transform"
>>         DataRepresentation2 = Show()
>>         DataRepresentation2.ColorArrayName = 'Unnamed0'
>>         DataRepresentation2.LookupTable = a1_Unnamed0_PVLookupTable
>>         DataRepresentation2.EdgeColor = [0.0, 0.0, 0.5000076295109483]
>>         DataRepresentation1.Visibility = 0
>>
>>         Transform1.Transform.Scale = [1.0, -1.0, 0.0]
>>         RenderView1.CenterAxesVisibility = 0
>>         RenderView1.CameraPosition = [78.0, -58.5, 376.71107225273664]
>>         RenderView1.OrientationAxesVisibility = 0
>>         RenderView1.CameraFocalPoint = [78.0, -58.5, 0.0]
>>         RenderView1.CenterOfRotation = [78.0, -58.5, 0.0]
>> #       Render()
>>         WriteImage("dir_%i.png" % (i))
>> _______________________________________________
>> 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
>>
>
>
> --
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150719/24b4a36f/attachment.html>

From aymeric.naze at gmail.com  Mon Jul 20 03:57:36 2015
From: aymeric.naze at gmail.com (Aymeric NAZE)
Date: Mon, 20 Jul 2015 09:57:36 +0200
Subject: [Paraview] Orient created vectors
In-Reply-To: <6265798005891350083@unknownmsgid>
References: <CAM4K3YdAJ+XvjbShzT3uJL3ntYwwitjUPdryzrx5pZUOGEa4LQ@mail.gmail.com>
 <CAB5Fpx5ZZb2UQP86on6-YT+Mqx6DfUc3j6K0deo8nTOaY2iHAg@mail.gmail.com>
 <CAM4K3YeSBB+eavXBKA+jUPzTdfASeM-pWRNkOqnBbdD6NcbGow@mail.gmail.com>
 <CAB5Fpx49Pm4tnm_cduJspQXFLzA27R+WXgN8C5XABBsdY3hbfg@mail.gmail.com>
 <CAM4K3YcYe_Eo8jYVWVWuaU3mHssPa=DnSFBjdmK3eyh8tr0RQA@mail.gmail.com>
 <CAB5Fpx5Lgi-yQxwrp43S4goeO40x56P9pFU94OGKWSzN_i+fcw@mail.gmail.com>
 <CAM4K3YdQZDhAqAy--jj6bNFy0VYKkwO-=s7Xz-VY7evJJ=DGJw@mail.gmail.com>
 <CAM4K3Yd5ANgvKeSDPG-krMBKsAaiVbHcTsp2qtQsCxgY0ehB4w@mail.gmail.com>
 <CAB5Fpx4rDh4Un-E3BN4wz62AwiEMMNuYoOAxn9CXK+ayoEQQoQ@mail.gmail.com>
 <6265798005891350083@unknownmsgid>
Message-ID: <CAM4K3Yerj_YXidn0mYTOCTsUbs7v4cVzzowi8NAQYZ=ybAffZQ@mail.gmail.com>

Hi Cory,

I've tried what you suggested and it works. Something has certainly been
wrong with my state file.

Thank you

Regards,

Aymeric

2015-07-16 20:55 GMT+02:00 Aymeric NAZE <aymeric.naze at gmail.com>:

> Thanks Cory for the time spent on my issue.
>
> I'll try this on monday and post feedback right after.
>
> Regards,
>
> Aymeric
>
> Le 16 juil. 2015 ? 19:38, Cory Quammen <cory.quammen at kitware.com> a
> ?crit :
>
> Hi Aymeric,
>
> Sorry, I have been swamped.
>
> I just looked at your data. The state file you sent invoked an error in
> the Output Window. Indeed, I could see the arrows aligned only with the X
> axis.
>
> If I load just your data, I have more success. Here's what I did:
>
> - load Test_Set.tp
> - Calculator filter
> -- Result array name = Velocity
> -- express = U*iHat + V*jHat + W*kHat
> - Glyph filter
> -- Glyph Type = Arrow
> -- Vectors = Velocity
> -- Glyph Mode = Every Nth Point
> -- Stride 300
> - color by "GlyphVector"
>
> I get the attached image when doing this.
>
> My suspicion is that an error that occurred somewhere along the way during
> your interaction with ParaView, and it has crept into the state file and is
> causing a problem with the glyph display. I recommend starting fresh, like
> I did, and see if you can get the vectors to point the right way.
>
> Best regards,
> Cory
>
> On Mon, Jul 13, 2015 at 3:41 AM, Aymeric NAZE <aymeric.naze at gmail.com>
> wrote:
>
>> Hi Cory,
>>
>> Did you have the time to take a look at my dataset ?
>>
>> 2015-07-09 17:03 GMT+02:00 Aymeric NAZE <aymeric.naze at gmail.com>:
>>
>>> Thank you for your reactivity.
>>>
>>> You will find below a dropbox link to 2 files :
>>>
>>>    - the dataset : 27.8 Mo
>>>    - the state file (ontaining the calculators and glyph) : 261 ko
>>>
>>>
>>> https://www.dropbox.com/sh/fu8mji13ov79crb/AAAFcFvCKccEu-qcP5YZtguPa?dl=0
>>>
>>>
>>> 2015-07-09 16:12 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>>>
>>>> Hmm, well it does indeed have non-zero Y and Z components. Could you
>>>> share this dataset?
>>>>
>>>> Thanks,
>>>> Cory
>>>>
>>>> On Thu, Jul 9, 2015 at 8:53 AM, Aymeric NAZE <aymeric.naze at gmail.com>
>>>> wrote:
>>>>
>>>>> Information regarding my Result vector field in Data Arrays (under
>>>>> "Information" tab in the calculator filter) :
>>>>>
>>>>>    - *Data Type* : double
>>>>>    - *Data Ranges* : [-1.26, 0.01], [-0.01, 0.76], [-0.16, 0.27]
>>>>>
>>>>>
>>>>> 2015-07-09 15:03 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>>>>>
>>>>>> Can you verify that the second and third components of your Result
>>>>>> vector field have a range outside [0, 0]? You can get this information
>>>>>> under the Information tab in the Data Arrays table.
>>>>>>
>>>>>> On Thu, Jul 9, 2015 at 7:56 AM, Aymeric NAZE <aymeric.naze at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> Thanks for considering my problem.
>>>>>>>
>>>>>>> Yes, in the Glyph Filter I have the following *Active Attributes* :
>>>>>>>
>>>>>>>    - *Scalars *: FF wich is the magnitude in the (x,y) plane
>>>>>>>    (calculated with another "calculator" filter : FF=(U^2+V^2)^0.5) : it's the
>>>>>>>    length of the arrows I want to display.
>>>>>>>
>>>>>>>
>>>>>>>    - *Vectors *: Result (vectors from the previously described
>>>>>>>    calculator)
>>>>>>>
>>>>>>>
>>>>>>> 2015-07-09 14:29 GMT+02:00 Cory Quammen <cory.quammen at kitware.com>:
>>>>>>>
>>>>>>>> Hi Aymeric,
>>>>>>>>
>>>>>>>> Did you choose the "Result" array as the "Vectors" property in the
>>>>>>>> Properties panel of the Glyph filter?
>>>>>>>>
>>>>>>>> HTH,
>>>>>>>> Cory
>>>>>>>>
>>>>>>>> On Thu, Jul 9, 2015 at 7:26 AM, Aymeric NAZE <
>>>>>>>> aymeric.naze at gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> I'm using Paraview 4.3.1 (64-bit) to display data from a tecplot
>>>>>>>>> format file.
>>>>>>>>>
>>>>>>>>> Data is points coordinates (x,y,z) and vectors coordinates (u,v,w)
>>>>>>>>> for each point.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>    - I have created vectors with "Calculator" filter (Result =
>>>>>>>>>    u*iHat+v*jHat+w*kHat) and it creates vectors with thewanted coordinates (I
>>>>>>>>>    can see that in the spreadsheet view)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>    - Then I made a glyph to display these vectors as arrows.
>>>>>>>>>
>>>>>>>>> Magnitude is displayed without problem but i did'nt find how to
>>>>>>>>> orient correctly the vectors.
>>>>>>>>> Whether i check or not the "Orient" feature it doesn't change
>>>>>>>>> anything : vectors are always oriented along the x axis...
>>>>>>>>>
>>>>>>>>> Does anybody can help me on that issue ?
>>>>>>>>>
>>>>>>>>> Thanks so much in advance.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Aymeric
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Cory Quammen
>>>>>>>> R&D Engineer
>>>>>>>> Kitware, Inc.
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Cory Quammen
>>>>>> R&D Engineer
>>>>>> Kitware, Inc.
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Cory Quammen
>>>> R&D Engineer
>>>> Kitware, Inc.
>>>>
>>>
>>>
>>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
> <Vectors.png>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/a210404a/attachment.html>

From simon.esneault at gmail.com  Mon Jul 20 05:02:27 2015
From: simon.esneault at gmail.com (Simon ESNEAULT)
Date: Mon, 20 Jul 2015 11:02:27 +0200
Subject: [Paraview] [vtk-developers] GPU volume rendering failure on
 Intel HD XXXX/Iris, Windows and recent drivers
In-Reply-To: <CAEw35Z-3JcFUo8Pd_wSmpBAs+qDnQo-5Nn99wySxCcHYZwMGVQ@mail.gmail.com>
References: <CAC9gB0ArB3vVBbcQnk-52ymwKYpBuk7ZLRXJD8-RevF7NRGg6w@mail.gmail.com>
 <CAEw35Z9KtCZn2MBYaom=8AYocGLJMypMfSf0hZ3m1pUkfhzdXA@mail.gmail.com>
 <CAC9gB0B=OJ4YBQa=hs=3J=X-4nfEQ3VBqyUSgQG-=LDJSSA6Bg@mail.gmail.com>
 <CY1PR0701MB16131DE5669DA94BF51225A1D8980@CY1PR0701MB1613.namprd07.prod.outlook.com>
 <CAEw35Z-3JcFUo8Pd_wSmpBAs+qDnQo-5Nn99wySxCcHYZwMGVQ@mail.gmail.com>
Message-ID: <CAC9gB0DRvEqpzS3zVArYn_K5FUdfP=q_0NALoOUrF4yJm34V1Q@mail.gmail.com>

Hi Aashish,

Thanks for the patchs.
However, I've tried them but without success, the GPU rendering won't show
up on an Intel HD chipset using the GPURenderDemo (the same exe/dll works
fine on a machine with an NVidia/Ati card). The warning disappeared though
...
The proposed patchs seems to affect only the TextureMapper 3D, shouldn't
there be modification to
the vtkOpenGLGPUVolumeRayCastMapper::LoadExtensions method as well?

I've tried to uncomment all added lines in the GL_VERSION_1_2_DEPRECATED
part of vtkgl.cxx, build correctly everything, and on the problematic
machine the checkIfNull() fail for all the lines, the program prints out :
Function pointer vtkgl::ColorTable is invalid
Function pointer vtkgl::.. is invalid
For every one of them.

Also the vtkgl.cxx file is generated by the vtkParseOGLExt exe, shouldn't
there be modification in the headers glext.h/glxext.h/wglext.h instead ?
Maybe this is causing some troubles elsewhere...

If you have some other magical trick to solve this, I would be glad to hear
about it! Also I can provide more informations if you want

Thank You
Simon


2015-07-17 17:48 GMT+02:00 Aashish Chaudhary <aashish.chaudhary at kitware.com>
:

> Hi Andras,
>
> Please find the patchs attached. If you run into issues let me know. I
> should mention that apply these patches at your discretion as I have not
> done enough testing to ensure the quality of the patches but the test
> passed last time I applied them.
>
>
>
> On Fri, Jul 17, 2015 at 11:40 AM, Andras Lasso <lasso at queensu.ca> wrote:
>
>>  Please share the patch publicly, we would need it for some of our
>> projects, too. Thank you!
>>
>>
>>
>> Andras
>>
>>
>>
>> *From:* vtk-developers [mailto:vtk-developers-bounces at vtk.org] *On
>> Behalf Of *Simon ESNEAULT
>> *Sent:* Friday, July 17, 2015 11:35 AM
>> *To:* Aashish Chaudhary
>> *Cc:* VTK Developers; vtkusers at vtk.org; ParaView list
>> *Subject:* Re: [vtk-developers] [Paraview] GPU volume rendering failure
>> on Intel HD XXXX/Iris, Windows and recent drivers
>>
>>
>>
>> Dear Aashish,
>>
>>
>>
>> Thank you very much for you answer.
>>
>> Yes you are right, we are waiting for a new VTK release that defaults to
>> the new OpenGL2 backend, for safety and because a change of VTK version
>> requires a lot of extra work with our current framework... But the green
>> dashboard indeed looks really promising, and we will probably make the move
>> as soon as it's ready !
>>
>> Meanwhile, I would be really glad if you could send me the patch that
>> solves this issue with the old backend, or guide me through the needed
>> modification to make it work.
>>
>> Thanks again
>>
>> Simon
>>
>>
>>
>> 2015-07-17 16:22 GMT+02:00 Aashish Chaudhary <
>> aashish.chaudhary at kitware.com>:
>>
>>  Dear Simon,
>>
>>
>>
>> On Fri, Jul 17, 2015 at 4:43 AM, Simon ESNEAULT <simon.esneault at gmail.com>
>> wrote:
>>
>>  Hi All,
>>
>> We're experiencing GPU volume rendering failure on a lot (maybe all ?)
>> Intel HD windows system with up to date drivers.
>>
>>
>> This is reproducible in Paraview or with the GPURenderDemo example from
>> VTK, just load a volume and try to render the volume... Here is a result
>> image from paraview on a Dell Latitude E7450 (Intel HD 5500 inside), with
>> GPU rendering [1] and the same volume with CPU VR rendering [2].
>> Interestingly, the volume rendering used to work with drivers older or
>> equal to the version 10.18.10.3496 [3]. As a work around, we ask our
>> customers to downgrade their driver version to this one, and they're
>> enjoying smooth GPU rendering. But this driver is quite old and does not
>> support recent chipset...
>>
>> I've built and tested the GPURenderDemo with the brand new OpenGL2
>> backend on an affected machine and of course it does work out of the box
>> (congratulations for this amazing work !).
>>
>>  Great!
>>
>>
>>
>>  But our application is FDA/CE marked and we need to wait that this new
>> backend is completely ready for prime time. So for now, we have to stick
>> with VTK 6.1 ...
>>
>>
>>
>> Most of the tests are passing for OpenGL2 (
>> https://open.cdash.org/index.php?project=VTK) on most of the dashboards
>> (various configurations etc) but it is a moving target just like VTK itself
>> is a moving target. I guess you are waiting for a VTK release that defaults
>> to OpenGL2 as oppose to OpenGL?
>>
>>
>> Anyone has any clue ? They're some warning that pop up from paraview
>> related to the extension "gl_version_1_2" that could not be loaded, not
>> sure if that could be related ? Following this thread [4] and the fix
>> proposed, I've tried to replace
>>
>> /*****************/
>>
>> extensions->LoadExtension("GL_VERSION_1_2")
>>
>> /*****************/
>>
>> by
>>
>> /*****************/
>>
>> extensions->LoadExtension("GL_EXT_texture3D");
>> extensions->LoadExtension( "GL_ARB_texture_non_power_of_two" );
>>
>> /*****************/
>>
>> in the vtkOpenGLGPUVolumeRayCastMapper.cxx, The warning disappears but
>> there is still no volume rendering (tested with GPURenderDemo). Maybe it
>> needs some others extensions ?
>>
>>
>>
>> Yes, there is a patch and I can send it to you. I have to talk to folks
>> here if we can fix the old mapper with those changes but as of now it is
>> not in the plan.
>>
>>
>>
>>
>> Should I fill a bug in paraview, vtk ? Are there any plan to maintain and
>> maybe fix this for the old backend ?
>>
>>
>>
>> - Aashish
>>
>>
>>
>>
>> Thanks,
>> --
>>
>> ------------------------------------------------------------------
>> Simon Esneault
>>
>> Rennes, France
>> ------------------------------------------------------------------
>>
>>
>> [1] http://picpaste.com/pics/Paraview-4-3-1-GPU-VR_fail.1437122217.PNG
>>
>> [2] http://picpaste.com/pics/Paraview-4-3-1-CPU-VR_win.1437122267.PNG
>>
>> [3] https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23339
>> [4] http://public.kitware.com/pipermail/vtkusers/2014-April/083584.html
>>
>>
>> _______________________________________________
>> 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
>>
>>
>>
>>
>>
>> --
>>
>>
>>
>> *| Aashish Chaudhary | Technical Leader          | Kitware Inc.
>>   *
>>
>> *| http://www.kitware.com/company/team/chaudhary.html
>> <http://www.kitware.com/company/team/chaudhary.html>*
>>
>>
>>
>>
>>
>> --
>>
>> ------------------------------------------------------------------
>> Simon Esneault
>>
>> Rennes, France
>> ------------------------------------------------------------------
>>
>
>
>
> --
>
>
>
> *| Aashish Chaudhary | Technical Leader         | Kitware Inc.            *
> *| http://www.kitware.com/company/team/chaudhary.html
> <http://www.kitware.com/company/team/chaudhary.html>*
>



-- 
------------------------------------------------------------------
Simon Esneault
Rennes, France
------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/ce545a23/attachment.html>

From casey.goodlett at kitware.com  Mon Jul 20 07:18:46 2015
From: casey.goodlett at kitware.com (Casey Goodlett)
Date: Mon, 20 Jul 2015 07:18:46 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <moc2uj$o6b$1@ger.gmane.org>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <mo2q49$4gt$1@ger.gmane.org>
 <CAOqyOuGT2uONXRjPd80bJOBdnhugTMyyUCHGn6s8H4Aw+i1wOg@mail.gmail.com>
 <mo7cvk$ria$1@ger.gmane.org>
 <CAOqyOuFMFju6ODKyehDU1pDdH1Z=A79wc0iy8KK3m11mziLMPQ@mail.gmail.com>
 <moaask$ejm$1@ger.gmane.org>
 <CAOqyOuGFFOHjMazR6EOwixVJ2LbH=5849VVCx2woC1CaJuS4KQ@mail.gmail.com>
 <moc2uj$o6b$1@ger.gmane.org>
Message-ID: <CAOqyOuGjOPiyR+R-OLn-W3ecPwb-4HQuh7dkuT0PDNK-3cA8Jw@mail.gmail.com>

On Fri, Jul 17, 2015 at 7:26 PM, Luca Morandini <lmorandini at ieee.org> wrote:

> As per the best way to do it, hmm... I'd rather like build documentation
> to be as close to the source code as possible, lest they diverge.
> Therefore, I would prefer updating the readme on the GitHub repo and drop
> the "Download And Build Instructions" wiki page: what do you think?


This sounds great.  If you create a pull request on github, I will review
and edit the old wiki to point there.


-- 
Casey B Goodlett, PhD
Technical Leader
Kitware, Inc. - North Carolina Office
http://www.kitware.com
(919) 969-6990 x310
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/5f727721/attachment.html>

From silvere.pierre.paraview at gmail.com  Mon Jul 20 08:32:40 2015
From: silvere.pierre.paraview at gmail.com (Silvere Pierre)
Date: Mon, 20 Jul 2015 14:32:40 +0200
Subject: [Paraview] Problem while exporting views in batch
Message-ID: <CAGox_oxa+PdQ2d5OHZR5barjJp2vGaA75p9V_stev4NE1=87Tw@mail.gmail.com>

Hello everyone,

I am used to create vector images (PDF) using the export view tool in the
Paraview 4.3 GUI.
As I wanted to use it in scripts I used Start Trace to get the python
instructions which is :

*ExportView('your_path.pdf', view=your_render_view, Rasterize3DGeometry=0)*

Problem is, the Rasterize3DGeometry option is unknown when you try and use
it in the console (and without it you get a pixeled image).

I looked up old messages and found this piece of code :









*rw = your_render_view.GetRenderWindow()exp =
paraview.vtk.vtkInstantiator.CreateInstance('vtkGL2PSExporter')exp.SetRenderWindow(rw)exp.SetDrawBackground(0)exp.SetSortToSimple()exp.SetFileFormatToPDF()exp.SetFilePrefix("your_path.pdf")exp.Write3DPropsAsRasterImageOff()exp.Write()*

that should take care of it in a less direct way. Unfortunately, the
instanciation fail and the object (named exp here) is undefined.

Is it only an interface problem with python ? Is there any way to get the
correct instance of the renderer ?

Best regards,

Silv?re Pierre
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/f0febf82/attachment.html>

From stefan.otte at gmail.com  Mon Jul 20 08:49:36 2015
From: stefan.otte at gmail.com (Stefan Otte)
Date: Mon, 20 Jul 2015 14:49:36 +0200
Subject: [Paraview] Compilation problem of ParaView 3.14.1 on Ubuntu
	14.04
In-Reply-To: <mo7c3c$ftj$1@ger.gmane.org>
References: <mo2g4i$4io$1@ger.gmane.org>
 <CAFzjYVpax_BsYW3M94FuV+08AaG-Nf3qEW5zdTmOKVYUVTUuFQ@mail.gmail.com>
 <mo7c3c$ftj$1@ger.gmane.org>
Message-ID: <CAFync2juzq+_=74_7BzMbCk9EpWghjg40RsR-gZsXXBVVWj6Mg@mail.gmail.com>

Hey,

I also had problems compiling paraview. There is a pre-build binary
[1] for Mac, Linux, and Windows. However, the OpenNI source is not
included.

Luca, is the OpenNI source available for you after you compiled everything?


Best,
 Stefan

[1] http://www.kitware.com/blog/home/post/650
Beste Gr??e,
 Stefan



On Thu, Jul 16, 2015 at 6:31 AM, Luca Morandini <lmorandini at ieee.org> wrote:
> On 15/07/15 04:19, Robert Maynard wrote:
>>
>>
>> Can you send your CMakeError.log from the build directory? This exact
>> failure is unexpected.
>
>
> Thanks Robert for taking the time to answer my post; however, I've found
> out, from the "PCL Plugin" thread, that a newer version of ParaView can be
> used to build the PCL plugin, and, many hours later, I was able to finally
> compile ParaView 4 on Ubuntu 14.04.
>
> Thanks again,
>
> Luca Morandini
> Data Architect - AURIN project
> Melbourne eResearch Group
> Department of Computing and Information Systems
> University of Melbourne
> Tel. +61 03 903 58 380
> Skype: lmorandini
>
> _______________________________________________
> 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

From aashish.chaudhary at kitware.com  Mon Jul 20 09:21:53 2015
From: aashish.chaudhary at kitware.com (Aashish Chaudhary)
Date: Mon, 20 Jul 2015 09:21:53 -0400
Subject: [Paraview] [vtk-developers] GPU volume rendering failure on
 Intel HD XXXX/Iris, Windows and recent drivers
In-Reply-To: <CAC9gB0DRvEqpzS3zVArYn_K5FUdfP=q_0NALoOUrF4yJm34V1Q@mail.gmail.com>
References: <CAC9gB0ArB3vVBbcQnk-52ymwKYpBuk7ZLRXJD8-RevF7NRGg6w@mail.gmail.com>
 <CAEw35Z9KtCZn2MBYaom=8AYocGLJMypMfSf0hZ3m1pUkfhzdXA@mail.gmail.com>
 <CAC9gB0B=OJ4YBQa=hs=3J=X-4nfEQ3VBqyUSgQG-=LDJSSA6Bg@mail.gmail.com>
 <CY1PR0701MB16131DE5669DA94BF51225A1D8980@CY1PR0701MB1613.namprd07.prod.outlook.com>
 <CAEw35Z-3JcFUo8Pd_wSmpBAs+qDnQo-5Nn99wySxCcHYZwMGVQ@mail.gmail.com>
 <CAC9gB0DRvEqpzS3zVArYn_K5FUdfP=q_0NALoOUrF4yJm34V1Q@mail.gmail.com>
Message-ID: <CAEw35Z9TdUedSHSfd7BEj7b8-O5T5zz5t1M0hPUwA8jXr0khMA@mail.gmail.com>

Hi Simon,

On Mon, Jul 20, 2015 at 5:02 AM, Simon ESNEAULT <simon.esneault at gmail.com>
wrote:

> Hi Aashish,
>
> Thanks for the patchs.
> However, I've tried them but without success, the GPU rendering won't show
> up on an Intel HD chipset using the GPURenderDemo (the same exe/dll works
> fine on a machine with an NVidia/Ati card). The warning disappeared though
> ...
>

The old mapper had issues on some of the ATI cards (specifically on Mac)
and Intel chipset as well. So I am not surprised that it didn't work.


> The proposed patchs seems to affect only the TextureMapper 3D, shouldn't
> there be modification to
> the vtkOpenGLGPUVolumeRayCastMapper::LoadExtensions method as well?
>

That method calls the vtkGL method I believe which I took care of it. I
will have a second look at it today.

>
> I've tried to uncomment all added lines in the GL_VERSION_1_2_DEPRECATED
> part of vtkgl.cxx, build correctly everything, and on the problematic
> machine the checkIfNull() fail for all the lines, the program prints out :
> Function pointer vtkgl::ColorTable is invalid
> Function pointer vtkgl::.. is invalid
> For every one of them.
>
> Also the vtkgl.cxx file is generated by the vtkParseOGLExt exe, shouldn't
> there be modification in the headers glext.h/glxext.h/wglext.h instead ?
> Maybe this is causing some troubles elsewhere...
>

Yes and No. Basically what happened was  that newer drivers stopped
reporting *1_2* variables and that's why you are running into issues. Since
the newer backend uses GLEW, all of this mostly works correctly.

>
> If you have some other magical trick to solve this, I would be glad to
> hear about it! Also I can provide more informations if you want
>

I will have a look at it but even if we can fix all the extension issue,
things may not work on Intel.

- Aashish

>
> Thank You
> Simon
>
>
> 2015-07-17 17:48 GMT+02:00 Aashish Chaudhary <
> aashish.chaudhary at kitware.com>:
>
>> Hi Andras,
>>
>> Please find the patchs attached. If you run into issues let me know. I
>> should mention that apply these patches at your discretion as I have not
>> done enough testing to ensure the quality of the patches but the test
>> passed last time I applied them.
>>
>>
>>
>> On Fri, Jul 17, 2015 at 11:40 AM, Andras Lasso <lasso at queensu.ca> wrote:
>>
>>>  Please share the patch publicly, we would need it for some of our
>>> projects, too. Thank you!
>>>
>>>
>>>
>>> Andras
>>>
>>>
>>>
>>> *From:* vtk-developers [mailto:vtk-developers-bounces at vtk.org] *On
>>> Behalf Of *Simon ESNEAULT
>>> *Sent:* Friday, July 17, 2015 11:35 AM
>>> *To:* Aashish Chaudhary
>>> *Cc:* VTK Developers; vtkusers at vtk.org; ParaView list
>>> *Subject:* Re: [vtk-developers] [Paraview] GPU volume rendering failure
>>> on Intel HD XXXX/Iris, Windows and recent drivers
>>>
>>>
>>>
>>> Dear Aashish,
>>>
>>>
>>>
>>> Thank you very much for you answer.
>>>
>>> Yes you are right, we are waiting for a new VTK release that defaults to
>>> the new OpenGL2 backend, for safety and because a change of VTK version
>>> requires a lot of extra work with our current framework... But the green
>>> dashboard indeed looks really promising, and we will probably make the move
>>> as soon as it's ready !
>>>
>>> Meanwhile, I would be really glad if you could send me the patch that
>>> solves this issue with the old backend, or guide me through the needed
>>> modification to make it work.
>>>
>>> Thanks again
>>>
>>> Simon
>>>
>>>
>>>
>>> 2015-07-17 16:22 GMT+02:00 Aashish Chaudhary <
>>> aashish.chaudhary at kitware.com>:
>>>
>>>  Dear Simon,
>>>
>>>
>>>
>>> On Fri, Jul 17, 2015 at 4:43 AM, Simon ESNEAULT <
>>> simon.esneault at gmail.com> wrote:
>>>
>>>  Hi All,
>>>
>>> We're experiencing GPU volume rendering failure on a lot (maybe all ?)
>>> Intel HD windows system with up to date drivers.
>>>
>>>
>>> This is reproducible in Paraview or with the GPURenderDemo example from
>>> VTK, just load a volume and try to render the volume... Here is a result
>>> image from paraview on a Dell Latitude E7450 (Intel HD 5500 inside), with
>>> GPU rendering [1] and the same volume with CPU VR rendering [2].
>>> Interestingly, the volume rendering used to work with drivers older or
>>> equal to the version 10.18.10.3496 [3]. As a work around, we ask our
>>> customers to downgrade their driver version to this one, and they're
>>> enjoying smooth GPU rendering. But this driver is quite old and does not
>>> support recent chipset...
>>>
>>> I've built and tested the GPURenderDemo with the brand new OpenGL2
>>> backend on an affected machine and of course it does work out of the box
>>> (congratulations for this amazing work !).
>>>
>>>  Great!
>>>
>>>
>>>
>>>  But our application is FDA/CE marked and we need to wait that this new
>>> backend is completely ready for prime time. So for now, we have to stick
>>> with VTK 6.1 ...
>>>
>>>
>>>
>>> Most of the tests are passing for OpenGL2 (
>>> https://open.cdash.org/index.php?project=VTK) on most of the dashboards
>>> (various configurations etc) but it is a moving target just like VTK itself
>>> is a moving target. I guess you are waiting for a VTK release that defaults
>>> to OpenGL2 as oppose to OpenGL?
>>>
>>>
>>> Anyone has any clue ? They're some warning that pop up from paraview
>>> related to the extension "gl_version_1_2" that could not be loaded, not
>>> sure if that could be related ? Following this thread [4] and the fix
>>> proposed, I've tried to replace
>>>
>>> /*****************/
>>>
>>> extensions->LoadExtension("GL_VERSION_1_2")
>>>
>>> /*****************/
>>>
>>> by
>>>
>>> /*****************/
>>>
>>> extensions->LoadExtension("GL_EXT_texture3D");
>>> extensions->LoadExtension( "GL_ARB_texture_non_power_of_two" );
>>>
>>> /*****************/
>>>
>>> in the vtkOpenGLGPUVolumeRayCastMapper.cxx, The warning disappears but
>>> there is still no volume rendering (tested with GPURenderDemo). Maybe it
>>> needs some others extensions ?
>>>
>>>
>>>
>>> Yes, there is a patch and I can send it to you. I have to talk to folks
>>> here if we can fix the old mapper with those changes but as of now it is
>>> not in the plan.
>>>
>>>
>>>
>>>
>>> Should I fill a bug in paraview, vtk ? Are there any plan to maintain
>>> and maybe fix this for the old backend ?
>>>
>>>
>>>
>>> - Aashish
>>>
>>>
>>>
>>>
>>> Thanks,
>>> --
>>>
>>> ------------------------------------------------------------------
>>> Simon Esneault
>>>
>>> Rennes, France
>>> ------------------------------------------------------------------
>>>
>>>
>>> [1] http://picpaste.com/pics/Paraview-4-3-1-GPU-VR_fail.1437122217.PNG
>>>
>>> [2] http://picpaste.com/pics/Paraview-4-3-1-CPU-VR_win.1437122267.PNG
>>>
>>> [3] https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23339
>>> [4] http://public.kitware.com/pipermail/vtkusers/2014-April/083584.html
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>>
>>> *| Aashish Chaudhary | Technical Leader          | Kitware Inc.
>>>   *
>>>
>>> *| http://www.kitware.com/company/team/chaudhary.html
>>> <http://www.kitware.com/company/team/chaudhary.html>*
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> ------------------------------------------------------------------
>>> Simon Esneault
>>>
>>> Rennes, France
>>> ------------------------------------------------------------------
>>>
>>
>>
>>
>> --
>>
>>
>>
>> *| Aashish Chaudhary | Technical Leader         | Kitware Inc.
>> *
>> *| http://www.kitware.com/company/team/chaudhary.html
>> <http://www.kitware.com/company/team/chaudhary.html>*
>>
>
>
>
> --
> ------------------------------------------------------------------
> Simon Esneault
> Rennes, France
> ------------------------------------------------------------------
>



-- 



*| Aashish Chaudhary | Technical Leader         | Kitware Inc.            *
*| http://www.kitware.com/company/team/chaudhary.html
<http://www.kitware.com/company/team/chaudhary.html>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/cccc50b7/attachment.html>

From eric.g.younkin at noaa.gov  Mon Jul 20 09:29:22 2015
From: eric.g.younkin at noaa.gov (Eric Younkin - NOAA Federal)
Date: Mon, 20 Jul 2015 09:29:22 -0400
Subject: [Paraview] Point clouds and computing PCA on voxels
In-Reply-To: <mocupi$4m1$1@ger.gmane.org>
References: <mocupi$4m1$1@ger.gmane.org>
Message-ID: <CAFe6qKifkpvupRtb1EMhYe3+OJEOa58pkp69aFWdKMZzFDOiRg@mail.gmail.com>

Luca,

Have you seen this
<http://pointclouds.org/documentation/tutorials/normal_estimation.php>?
Are you just looking for a more detailed example?  I'm also looking to
eventually do something similar, once I get it all set up in the end.

V/R,
Eric

On Sat, Jul 18, 2015 at 3:21 AM, Luca Morandini <lmorandini at ieee.org> wrote:

> Folks,
>
> I would like to compute PCA on some LIDAR data in order to tell, say,
> walls from cables. Therefore, it would be useful to know the
> eigenvectors/eigenvalues of the point clouds belonging to voxels of
> different sizes.
>
> However, I have been unable so far to find a way to achieve this in
> ParaView, possibly using Python: can someone be so benevolent as to show me
> the way?
>
> Regards,
>
> Luca Morandini
> Data Architect - AURIN project
> Melbourne eResearch Group
> Department of Computing and Information Systems
> University of Melbourne
> Tel. +61 03 903 58 380
> Skype: lmorandini
>
> _______________________________________________
> 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
>



-- 
Eric Younkin LTJG/NOAA
HSTP Liaison - East
Marine Operations Center - Atlantic
439 W York St
Norfolk, VA 23510
Cell: 828-331-8197
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/f9894ba8/attachment.html>

From eric.g.younkin at noaa.gov  Mon Jul 20 09:47:08 2015
From: eric.g.younkin at noaa.gov (Eric Younkin - NOAA Federal)
Date: Mon, 20 Jul 2015 09:47:08 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAFe6qKgK_grq0Vzo0kF8NgiGxU_4T9_6jQrfij3=yZr9y27CEQ@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <mo2q49$4gt$1@ger.gmane.org>
 <CAOqyOuGT2uONXRjPd80bJOBdnhugTMyyUCHGn6s8H4Aw+i1wOg@mail.gmail.com>
 <CAFe6qKgK_grq0Vzo0kF8NgiGxU_4T9_6jQrfij3=yZr9y27CEQ@mail.gmail.com>
Message-ID: <CAFe6qKh_Xs66xKSNX=1Dqz00DBuXk6vOUrDKnxZRcE8_pNkp7A@mail.gmail.com>

Casey,

Did you have a chance to look at this?  What errors would you expect to see
using Paraview and QT5?

Thanks,
Eric

On Wed, Jul 15, 2015 at 11:02 PM, Eric Younkin - NOAA Federal <
eric.g.younkin at noaa.gov> wrote:

> Casey,
>
> I managed to build from source, Paraview 4.3.1 in VS2013.  It looks like
> my problem had to do with ZLIB and how I set the cmake parameters.  Also
> had to change the Paraview project subsystem type from windows to console.
> This doesn't make a whole lot of sense to me, but it did get it working.
>
> Now when I run Paraview.exe, I get the following output messages on
> startup:
>
> QWindowsWindow::setGeometryDp: Unable to set geometry 1920x1017+4+23 on
> QWidgetWindow/'pqClientMainWindowWindow'. Resulting geometry: 1370x753+4+23
> (frame: 4, 23, 4, 4, custom margin: 0, 0, 0, 0, minimum size: 471x407,
> maximum size: 16777215x16777215). (qwindowswindow.cpp:1323, void __cdecl
> QWindowsWindow::setGeometryDp(const class QRect &))
>
> Is this something I should be concerned about?  Some kind of resolution
> issue?  I haven't seen it on the install I have using the binaries from the
> Paraview site.
>
> Thanks,
> Eric
>
> On Tue, Jul 14, 2015 at 1:39 PM, Casey Goodlett <
> casey.goodlett at kitware.com> wrote:
>
>> Luca,
>>
>> You should be able to use a more recent ParaView.  If you run across
>> problems with the build you can ask here.  It should work, but you may
>> encounter some problems.  I believe I tested as recently as paraview 4.2
>>
>> On Tue, Jul 14, 2015 at 7:00 AM, Luca Morandini <lmorandini at ieee.org>
>> wrote:
>>
>>> On 10/07/15 00:39, Casey Goodlett wrote:
>>>
>>>> Hi Eric,
>>>>
>>>> Thanks for your interest in the PCL plugin, I have used the plugin more
>>>> recently
>>>> than PCL 1.5.1.  I last tested with ParaView 4.1 and PCL master (from
>>>> around
>>>> February of this year).
>>>>
>>>
>>> Apologies for the interruption, but I tried to build the PCL plugin
>>> following the instructions [1] against an old version of ParaView, and run
>>> into problems (see my other post today),  but then I noticed this thread
>>> and realized that I may try to build it against a more recent version of
>>> ParaView: will it work following the dame instructions, as provided by  or
>>> some extra care is needed?
>>>
>>> Regards,
>>>
>>> [1]
>>> http://www.paraview.org/Wiki/ParaView/PCL_Plugin/Download_And_Build_Instructions
>>>
>>> Luca Morandini
>>> Data Architect - AURIN project
>>> Melbourne eResearch Group
>>> Department of Computing and Information Systems
>>> University of Melbourne
>>> Tel. +61 03 903 58 380
>>> Skype: lmorandini
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>
>>
>>
>> --
>> Casey B Goodlett, PhD
>> Technical Leader
>> Kitware, Inc. - North Carolina Office
>> http://www.kitware.com
>> (919) 969-6990 x310
>>
>> _______________________________________________
>> 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
>>
>>
>
>
> --
> Eric Younkin LTJG/NOAA
> HSTP Liaison - East
> Marine Operations Center - Atlantic
> 439 W York St
> Norfolk, VA 23510
> Cell: 828-331-8197
>



-- 
Eric Younkin LTJG/NOAA
HSTP Liaison - East
Marine Operations Center - Atlantic
439 W York St
Norfolk, VA 23510
Cell: 828-331-8197
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/ec147e14/attachment.html>

From simon.esneault at gmail.com  Mon Jul 20 10:11:57 2015
From: simon.esneault at gmail.com (Simon ESNEAULT)
Date: Mon, 20 Jul 2015 16:11:57 +0200
Subject: [Paraview] [vtk-developers] GPU volume rendering failure on
 Intel HD XXXX/Iris, Windows and recent drivers
In-Reply-To: <CAEw35Z9TdUedSHSfd7BEj7b8-O5T5zz5t1M0hPUwA8jXr0khMA@mail.gmail.com>
References: <CAC9gB0ArB3vVBbcQnk-52ymwKYpBuk7ZLRXJD8-RevF7NRGg6w@mail.gmail.com>
 <CAEw35Z9KtCZn2MBYaom=8AYocGLJMypMfSf0hZ3m1pUkfhzdXA@mail.gmail.com>
 <CAC9gB0B=OJ4YBQa=hs=3J=X-4nfEQ3VBqyUSgQG-=LDJSSA6Bg@mail.gmail.com>
 <CY1PR0701MB16131DE5669DA94BF51225A1D8980@CY1PR0701MB1613.namprd07.prod.outlook.com>
 <CAEw35Z-3JcFUo8Pd_wSmpBAs+qDnQo-5Nn99wySxCcHYZwMGVQ@mail.gmail.com>
 <CAC9gB0DRvEqpzS3zVArYn_K5FUdfP=q_0NALoOUrF4yJm34V1Q@mail.gmail.com>
 <CAEw35Z9TdUedSHSfd7BEj7b8-O5T5zz5t1M0hPUwA8jXr0khMA@mail.gmail.com>
Message-ID: <CAC9gB0ARxRTDT0z=J37ApkFwm=8O-rO7Fp68GNvNm-s7Xrjtxw@mail.gmail.com>

Hi Aashish,

Thanks you very much for looking into this issue. Our customers (and I
believe the community since the issue is visible in paraview) would really
benefit from such a fix. Quite a lot of new computers just have an intel
chipset nowadays.
This of course until the new OpenGL2 backend is ready !

Please let me know if there is anything I can do to help.

Thanks a lot
Simon

2015-07-20 15:21 GMT+02:00 Aashish Chaudhary <aashish.chaudhary at kitware.com>
:

> Hi Simon,
>
> On Mon, Jul 20, 2015 at 5:02 AM, Simon ESNEAULT <simon.esneault at gmail.com>
> wrote:
>
>> Hi Aashish,
>>
>> Thanks for the patchs.
>> However, I've tried them but without success, the GPU rendering won't
>> show up on an Intel HD chipset using the GPURenderDemo (the same exe/dll
>> works fine on a machine with an NVidia/Ati card). The warning disappeared
>> though ...
>>
>
> The old mapper had issues on some of the ATI cards (specifically on Mac)
> and Intel chipset as well. So I am not surprised that it didn't work.
>
>
>> The proposed patchs seems to affect only the TextureMapper 3D, shouldn't
>> there be modification to
>> the vtkOpenGLGPUVolumeRayCastMapper::LoadExtensions method as well?
>>
>
> That method calls the vtkGL method I believe which I took care of it. I
> will have a second look at it today.
>
>>
>> I've tried to uncomment all added lines in the GL_VERSION_1_2_DEPRECATED
>> part of vtkgl.cxx, build correctly everything, and on the problematic
>> machine the checkIfNull() fail for all the lines, the program prints out :
>> Function pointer vtkgl::ColorTable is invalid
>> Function pointer vtkgl::.. is invalid
>> For every one of them.
>>
>> Also the vtkgl.cxx file is generated by the vtkParseOGLExt exe, shouldn't
>> there be modification in the headers glext.h/glxext.h/wglext.h instead ?
>> Maybe this is causing some troubles elsewhere...
>>
>
> Yes and No. Basically what happened was  that newer drivers stopped
> reporting *1_2* variables and that's why you are running into issues. Since
> the newer backend uses GLEW, all of this mostly works correctly.
>
>>
>> If you have some other magical trick to solve this, I would be glad to
>> hear about it! Also I can provide more informations if you want
>>
>
> I will have a look at it but even if we can fix all the extension issue,
> things may not work on Intel.
>
> - Aashish
>
>>
>> Thank You
>> Simon
>>
>>
>> 2015-07-17 17:48 GMT+02:00 Aashish Chaudhary <
>> aashish.chaudhary at kitware.com>:
>>
>>> Hi Andras,
>>>
>>> Please find the patchs attached. If you run into issues let me know. I
>>> should mention that apply these patches at your discretion as I have not
>>> done enough testing to ensure the quality of the patches but the test
>>> passed last time I applied them.
>>>
>>>
>>>
>>> On Fri, Jul 17, 2015 at 11:40 AM, Andras Lasso <lasso at queensu.ca> wrote:
>>>
>>>>  Please share the patch publicly, we would need it for some of our
>>>> projects, too. Thank you!
>>>>
>>>>
>>>>
>>>> Andras
>>>>
>>>>
>>>>
>>>> *From:* vtk-developers [mailto:vtk-developers-bounces at vtk.org] *On
>>>> Behalf Of *Simon ESNEAULT
>>>> *Sent:* Friday, July 17, 2015 11:35 AM
>>>> *To:* Aashish Chaudhary
>>>> *Cc:* VTK Developers; vtkusers at vtk.org; ParaView list
>>>> *Subject:* Re: [vtk-developers] [Paraview] GPU volume rendering
>>>> failure on Intel HD XXXX/Iris, Windows and recent drivers
>>>>
>>>>
>>>>
>>>> Dear Aashish,
>>>>
>>>>
>>>>
>>>> Thank you very much for you answer.
>>>>
>>>> Yes you are right, we are waiting for a new VTK release that defaults
>>>> to the new OpenGL2 backend, for safety and because a change of VTK version
>>>> requires a lot of extra work with our current framework... But the green
>>>> dashboard indeed looks really promising, and we will probably make the move
>>>> as soon as it's ready !
>>>>
>>>> Meanwhile, I would be really glad if you could send me the patch that
>>>> solves this issue with the old backend, or guide me through the needed
>>>> modification to make it work.
>>>>
>>>> Thanks again
>>>>
>>>> Simon
>>>>
>>>>
>>>>
>>>> 2015-07-17 16:22 GMT+02:00 Aashish Chaudhary <
>>>> aashish.chaudhary at kitware.com>:
>>>>
>>>>  Dear Simon,
>>>>
>>>>
>>>>
>>>> On Fri, Jul 17, 2015 at 4:43 AM, Simon ESNEAULT <
>>>> simon.esneault at gmail.com> wrote:
>>>>
>>>>  Hi All,
>>>>
>>>> We're experiencing GPU volume rendering failure on a lot (maybe all ?)
>>>> Intel HD windows system with up to date drivers.
>>>>
>>>>
>>>> This is reproducible in Paraview or with the GPURenderDemo example from
>>>> VTK, just load a volume and try to render the volume... Here is a result
>>>> image from paraview on a Dell Latitude E7450 (Intel HD 5500 inside), with
>>>> GPU rendering [1] and the same volume with CPU VR rendering [2].
>>>> Interestingly, the volume rendering used to work with drivers older or
>>>> equal to the version 10.18.10.3496 [3]. As a work around, we ask our
>>>> customers to downgrade their driver version to this one, and they're
>>>> enjoying smooth GPU rendering. But this driver is quite old and does not
>>>> support recent chipset...
>>>>
>>>> I've built and tested the GPURenderDemo with the brand new OpenGL2
>>>> backend on an affected machine and of course it does work out of the box
>>>> (congratulations for this amazing work !).
>>>>
>>>>  Great!
>>>>
>>>>
>>>>
>>>>  But our application is FDA/CE marked and we need to wait that this
>>>> new backend is completely ready for prime time. So for now, we have to
>>>> stick with VTK 6.1 ...
>>>>
>>>>
>>>>
>>>> Most of the tests are passing for OpenGL2 (
>>>> https://open.cdash.org/index.php?project=VTK) on most of the
>>>> dashboards (various configurations etc) but it is a moving target just like
>>>> VTK itself is a moving target. I guess you are waiting for a VTK release
>>>> that defaults to OpenGL2 as oppose to OpenGL?
>>>>
>>>>
>>>> Anyone has any clue ? They're some warning that pop up from paraview
>>>> related to the extension "gl_version_1_2" that could not be loaded, not
>>>> sure if that could be related ? Following this thread [4] and the fix
>>>> proposed, I've tried to replace
>>>>
>>>> /*****************/
>>>>
>>>> extensions->LoadExtension("GL_VERSION_1_2")
>>>>
>>>> /*****************/
>>>>
>>>> by
>>>>
>>>> /*****************/
>>>>
>>>> extensions->LoadExtension("GL_EXT_texture3D");
>>>> extensions->LoadExtension( "GL_ARB_texture_non_power_of_two" );
>>>>
>>>> /*****************/
>>>>
>>>> in the vtkOpenGLGPUVolumeRayCastMapper.cxx, The warning disappears but
>>>> there is still no volume rendering (tested with GPURenderDemo). Maybe it
>>>> needs some others extensions ?
>>>>
>>>>
>>>>
>>>> Yes, there is a patch and I can send it to you. I have to talk to folks
>>>> here if we can fix the old mapper with those changes but as of now it is
>>>> not in the plan.
>>>>
>>>>
>>>>
>>>>
>>>> Should I fill a bug in paraview, vtk ? Are there any plan to maintain
>>>> and maybe fix this for the old backend ?
>>>>
>>>>
>>>>
>>>> - Aashish
>>>>
>>>>
>>>>
>>>>
>>>> Thanks,
>>>> --
>>>>
>>>> ------------------------------------------------------------------
>>>> Simon Esneault
>>>>
>>>> Rennes, France
>>>> ------------------------------------------------------------------
>>>>
>>>>
>>>> [1] http://picpaste.com/pics/Paraview-4-3-1-GPU-VR_fail.1437122217.PNG
>>>>
>>>> [2] http://picpaste.com/pics/Paraview-4-3-1-CPU-VR_win.1437122267.PNG
>>>>
>>>> [3] https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23339
>>>> [4] http://public.kitware.com/pipermail/vtkusers/2014-April/083584.html
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>>
>>>> *| Aashish Chaudhary | Technical Leader          | Kitware Inc.
>>>>     *
>>>>
>>>> *| http://www.kitware.com/company/team/chaudhary.html
>>>> <http://www.kitware.com/company/team/chaudhary.html>*
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> ------------------------------------------------------------------
>>>> Simon Esneault
>>>>
>>>> Rennes, France
>>>> ------------------------------------------------------------------
>>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>>
>>> *| Aashish Chaudhary | Technical Leader         | Kitware Inc.
>>>   *
>>> *| http://www.kitware.com/company/team/chaudhary.html
>>> <http://www.kitware.com/company/team/chaudhary.html>*
>>>
>>
>>
>>
>> --
>> ------------------------------------------------------------------
>> Simon Esneault
>> Rennes, France
>> ------------------------------------------------------------------
>>
>
>
>
> --
>
>
>
> *| Aashish Chaudhary | Technical Leader         | Kitware Inc.            *
> *| http://www.kitware.com/company/team/chaudhary.html
> <http://www.kitware.com/company/team/chaudhary.html>*
>



-- 
------------------------------------------------------------------
Simon Esneault
Rennes, France
------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/fd3c41e7/attachment.html>

From aashish.chaudhary at kitware.com  Mon Jul 20 10:14:33 2015
From: aashish.chaudhary at kitware.com (Aashish Chaudhary)
Date: Mon, 20 Jul 2015 10:14:33 -0400
Subject: [Paraview] [vtk-developers] GPU volume rendering failure on
 Intel HD XXXX/Iris, Windows and recent drivers
In-Reply-To: <CAC9gB0ARxRTDT0z=J37ApkFwm=8O-rO7Fp68GNvNm-s7Xrjtxw@mail.gmail.com>
References: <CAC9gB0ArB3vVBbcQnk-52ymwKYpBuk7ZLRXJD8-RevF7NRGg6w@mail.gmail.com>
 <CAEw35Z9KtCZn2MBYaom=8AYocGLJMypMfSf0hZ3m1pUkfhzdXA@mail.gmail.com>
 <CAC9gB0B=OJ4YBQa=hs=3J=X-4nfEQ3VBqyUSgQG-=LDJSSA6Bg@mail.gmail.com>
 <CY1PR0701MB16131DE5669DA94BF51225A1D8980@CY1PR0701MB1613.namprd07.prod.outlook.com>
 <CAEw35Z-3JcFUo8Pd_wSmpBAs+qDnQo-5Nn99wySxCcHYZwMGVQ@mail.gmail.com>
 <CAC9gB0DRvEqpzS3zVArYn_K5FUdfP=q_0NALoOUrF4yJm34V1Q@mail.gmail.com>
 <CAEw35Z9TdUedSHSfd7BEj7b8-O5T5zz5t1M0hPUwA8jXr0khMA@mail.gmail.com>
 <CAC9gB0ARxRTDT0z=J37ApkFwm=8O-rO7Fp68GNvNm-s7Xrjtxw@mail.gmail.com>
Message-ID: <CAEw35Z8YOc6aex6d3iBA7LjMH3P2VN7XbZh0iQS5T72LHAybLw@mail.gmail.com>

The OpenGL2 mapper works on most of the intel chipset. I cannot promise
that we can get the old mapper working on Intel cards unless it can be
fixed by telling it that all the extensions are there.

- Aashish

On Mon, Jul 20, 2015 at 10:11 AM, Simon ESNEAULT <simon.esneault at gmail.com>
wrote:

> Hi Aashish,
>
> Thanks you very much for looking into this issue. Our customers (and I
> believe the community since the issue is visible in paraview) would really
> benefit from such a fix. Quite a lot of new computers just have an intel
> chipset nowadays.
> This of course until the new OpenGL2 backend is ready !
>
> Please let me know if there is anything I can do to help.
>
> Thanks a lot
> Simon
>
> 2015-07-20 15:21 GMT+02:00 Aashish Chaudhary <
> aashish.chaudhary at kitware.com>:
>
>> Hi Simon,
>>
>> On Mon, Jul 20, 2015 at 5:02 AM, Simon ESNEAULT <simon.esneault at gmail.com
>> > wrote:
>>
>>> Hi Aashish,
>>>
>>> Thanks for the patchs.
>>> However, I've tried them but without success, the GPU rendering won't
>>> show up on an Intel HD chipset using the GPURenderDemo (the same exe/dll
>>> works fine on a machine with an NVidia/Ati card). The warning disappeared
>>> though ...
>>>
>>
>> The old mapper had issues on some of the ATI cards (specifically on Mac)
>> and Intel chipset as well. So I am not surprised that it didn't work.
>>
>>
>>> The proposed patchs seems to affect only the TextureMapper 3D, shouldn't
>>> there be modification to
>>> the vtkOpenGLGPUVolumeRayCastMapper::LoadExtensions method as well?
>>>
>>
>> That method calls the vtkGL method I believe which I took care of it. I
>> will have a second look at it today.
>>
>>>
>>> I've tried to uncomment all added lines in the GL_VERSION_1_2_DEPRECATED
>>> part of vtkgl.cxx, build correctly everything, and on the problematic
>>> machine the checkIfNull() fail for all the lines, the program prints out :
>>> Function pointer vtkgl::ColorTable is invalid
>>> Function pointer vtkgl::.. is invalid
>>> For every one of them.
>>>
>>> Also the vtkgl.cxx file is generated by the vtkParseOGLExt exe,
>>> shouldn't there be modification in the headers glext.h/glxext.h/wglext.h
>>> instead ? Maybe this is causing some troubles elsewhere...
>>>
>>
>> Yes and No. Basically what happened was  that newer drivers stopped
>> reporting *1_2* variables and that's why you are running into issues. Since
>> the newer backend uses GLEW, all of this mostly works correctly.
>>
>>>
>>> If you have some other magical trick to solve this, I would be glad to
>>> hear about it! Also I can provide more informations if you want
>>>
>>
>> I will have a look at it but even if we can fix all the extension issue,
>> things may not work on Intel.
>>
>> - Aashish
>>
>>>
>>> Thank You
>>> Simon
>>>
>>>
>>> 2015-07-17 17:48 GMT+02:00 Aashish Chaudhary <
>>> aashish.chaudhary at kitware.com>:
>>>
>>>> Hi Andras,
>>>>
>>>> Please find the patchs attached. If you run into issues let me know. I
>>>> should mention that apply these patches at your discretion as I have not
>>>> done enough testing to ensure the quality of the patches but the test
>>>> passed last time I applied them.
>>>>
>>>>
>>>>
>>>> On Fri, Jul 17, 2015 at 11:40 AM, Andras Lasso <lasso at queensu.ca>
>>>> wrote:
>>>>
>>>>>  Please share the patch publicly, we would need it for some of our
>>>>> projects, too. Thank you!
>>>>>
>>>>>
>>>>>
>>>>> Andras
>>>>>
>>>>>
>>>>>
>>>>> *From:* vtk-developers [mailto:vtk-developers-bounces at vtk.org] *On
>>>>> Behalf Of *Simon ESNEAULT
>>>>> *Sent:* Friday, July 17, 2015 11:35 AM
>>>>> *To:* Aashish Chaudhary
>>>>> *Cc:* VTK Developers; vtkusers at vtk.org; ParaView list
>>>>> *Subject:* Re: [vtk-developers] [Paraview] GPU volume rendering
>>>>> failure on Intel HD XXXX/Iris, Windows and recent drivers
>>>>>
>>>>>
>>>>>
>>>>> Dear Aashish,
>>>>>
>>>>>
>>>>>
>>>>> Thank you very much for you answer.
>>>>>
>>>>> Yes you are right, we are waiting for a new VTK release that defaults
>>>>> to the new OpenGL2 backend, for safety and because a change of VTK version
>>>>> requires a lot of extra work with our current framework... But the green
>>>>> dashboard indeed looks really promising, and we will probably make the move
>>>>> as soon as it's ready !
>>>>>
>>>>> Meanwhile, I would be really glad if you could send me the patch that
>>>>> solves this issue with the old backend, or guide me through the needed
>>>>> modification to make it work.
>>>>>
>>>>> Thanks again
>>>>>
>>>>> Simon
>>>>>
>>>>>
>>>>>
>>>>> 2015-07-17 16:22 GMT+02:00 Aashish Chaudhary <
>>>>> aashish.chaudhary at kitware.com>:
>>>>>
>>>>>  Dear Simon,
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Jul 17, 2015 at 4:43 AM, Simon ESNEAULT <
>>>>> simon.esneault at gmail.com> wrote:
>>>>>
>>>>>  Hi All,
>>>>>
>>>>> We're experiencing GPU volume rendering failure on a lot (maybe all ?)
>>>>> Intel HD windows system with up to date drivers.
>>>>>
>>>>>
>>>>> This is reproducible in Paraview or with the GPURenderDemo example
>>>>> from VTK, just load a volume and try to render the volume... Here is a
>>>>> result image from paraview on a Dell Latitude E7450 (Intel HD 5500 inside),
>>>>> with GPU rendering [1] and the same volume with CPU VR rendering [2].
>>>>> Interestingly, the volume rendering used to work with drivers older or
>>>>> equal to the version 10.18.10.3496 [3]. As a work around, we ask our
>>>>> customers to downgrade their driver version to this one, and they're
>>>>> enjoying smooth GPU rendering. But this driver is quite old and does not
>>>>> support recent chipset...
>>>>>
>>>>> I've built and tested the GPURenderDemo with the brand new OpenGL2
>>>>> backend on an affected machine and of course it does work out of the box
>>>>> (congratulations for this amazing work !).
>>>>>
>>>>>  Great!
>>>>>
>>>>>
>>>>>
>>>>>  But our application is FDA/CE marked and we need to wait that this
>>>>> new backend is completely ready for prime time. So for now, we have to
>>>>> stick with VTK 6.1 ...
>>>>>
>>>>>
>>>>>
>>>>> Most of the tests are passing for OpenGL2 (
>>>>> https://open.cdash.org/index.php?project=VTK) on most of the
>>>>> dashboards (various configurations etc) but it is a moving target just like
>>>>> VTK itself is a moving target. I guess you are waiting for a VTK release
>>>>> that defaults to OpenGL2 as oppose to OpenGL?
>>>>>
>>>>>
>>>>> Anyone has any clue ? They're some warning that pop up from paraview
>>>>> related to the extension "gl_version_1_2" that could not be loaded, not
>>>>> sure if that could be related ? Following this thread [4] and the fix
>>>>> proposed, I've tried to replace
>>>>>
>>>>> /*****************/
>>>>>
>>>>> extensions->LoadExtension("GL_VERSION_1_2")
>>>>>
>>>>> /*****************/
>>>>>
>>>>> by
>>>>>
>>>>> /*****************/
>>>>>
>>>>> extensions->LoadExtension("GL_EXT_texture3D");
>>>>> extensions->LoadExtension( "GL_ARB_texture_non_power_of_two" );
>>>>>
>>>>> /*****************/
>>>>>
>>>>> in the vtkOpenGLGPUVolumeRayCastMapper.cxx, The warning disappears but
>>>>> there is still no volume rendering (tested with GPURenderDemo). Maybe it
>>>>> needs some others extensions ?
>>>>>
>>>>>
>>>>>
>>>>> Yes, there is a patch and I can send it to you. I have to talk to
>>>>> folks here if we can fix the old mapper with those changes but as of now it
>>>>> is not in the plan.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Should I fill a bug in paraview, vtk ? Are there any plan to maintain
>>>>> and maybe fix this for the old backend ?
>>>>>
>>>>>
>>>>>
>>>>> - Aashish
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>> --
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> Simon Esneault
>>>>>
>>>>> Rennes, France
>>>>> ------------------------------------------------------------------
>>>>>
>>>>>
>>>>> [1] http://picpaste.com/pics/Paraview-4-3-1-GPU-VR_fail.1437122217.PNG
>>>>>
>>>>> [2] http://picpaste.com/pics/Paraview-4-3-1-CPU-VR_win.1437122267.PNG
>>>>>
>>>>> [3] https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23339
>>>>> [4]
>>>>> http://public.kitware.com/pipermail/vtkusers/2014-April/083584.html
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>>
>>>>> *| Aashish Chaudhary | Technical Leader          | Kitware Inc.
>>>>>     *
>>>>>
>>>>> *| http://www.kitware.com/company/team/chaudhary.html
>>>>> <http://www.kitware.com/company/team/chaudhary.html>*
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> Simon Esneault
>>>>>
>>>>> Rennes, France
>>>>> ------------------------------------------------------------------
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>>
>>>> *| Aashish Chaudhary | Technical Leader         | Kitware Inc.
>>>>   *
>>>> *| http://www.kitware.com/company/team/chaudhary.html
>>>> <http://www.kitware.com/company/team/chaudhary.html>*
>>>>
>>>
>>>
>>>
>>> --
>>> ------------------------------------------------------------------
>>> Simon Esneault
>>> Rennes, France
>>> ------------------------------------------------------------------
>>>
>>
>>
>>
>> --
>>
>>
>>
>> *| Aashish Chaudhary | Technical Leader         | Kitware Inc.
>> *
>> *| http://www.kitware.com/company/team/chaudhary.html
>> <http://www.kitware.com/company/team/chaudhary.html>*
>>
>
>
>
> --
> ------------------------------------------------------------------
> Simon Esneault
> Rennes, France
> ------------------------------------------------------------------
>



-- 



*| Aashish Chaudhary | Technical Leader         | Kitware Inc.            *
*| http://www.kitware.com/company/team/chaudhary.html
<http://www.kitware.com/company/team/chaudhary.html>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/beb41d02/attachment.html>

From aashish.chaudhary at kitware.com  Mon Jul 20 10:26:30 2015
From: aashish.chaudhary at kitware.com (Aashish Chaudhary)
Date: Mon, 20 Jul 2015 10:26:30 -0400
Subject: [Paraview] Transforming a spherical slice into a map projection
In-Reply-To: <CAK3vnGf8e_AHmruBokgujpBCqyA44_A1eX2dwxNSEN0WvkdjUw@mail.gmail.com>
References: <CAK3vnGc2pHaxZXhGtto8JzOo6Nu_UL84+rEMES6z5-x6Ei+=bw@mail.gmail.com>
 <CADHSJjAZmDV+7QY7VqAEMxWtumyDK08fGyjpWT8T-JwVY8y4og@mail.gmail.com>
 <CAK3vnGf8e_AHmruBokgujpBCqyA44_A1eX2dwxNSEN0WvkdjUw@mail.gmail.com>
Message-ID: <CAEw35Z82=iyeCPOqCgrweS-KK4sznRKFRLt_SFqDMAPe+Fm63A@mail.gmail.com>

Dear Marie,

You can use vtkGeoSphereTransform class to transfrom from Cartesian
(Spherical grid X,Y,Z) to Sphereical (Lat,Lon coordinates). Once you have
Lat-Lon, you can just treat them as in flat projection (Projection 4326).
This class is not exposed in ParaView, so you would have to use Python to
do the job or write a plugin for Paraview. Please let us know if you have
any questions.

Thanks,


On Fri, Jul 17, 2015 at 8:49 PM, Marie Kajan <marie.kajan at gmail.com> wrote:
>
> Hi Utkarsh,
>
> Here's a small sample (plus the saved state for a sample slice, if that
helps):
>
> https://www.dropbox.com/s/hpp2y8bbkjn34z3/solution-00000.0000.vtk?dl=0
> https://www.dropbox.com/s/94rfo305ljeqtgk/solution-00000.pvsm?dl=0
>
> Thanks a lot!
>
> Marie
>
>
> On Wed, Jul 15, 2015 at 10:41 PM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:
>>
>> Marie,
>>
>> Do you have a sample dataset? That'll make it easier to determine the
>> filters etc. you can apply.
>>
>> Utkarsh
>>
>> On Wed, Jul 15, 2015 at 8:03 PM, Marie Kajan <marie.kajan at gmail.com>
wrote:
>> > I'm a new user and am having difficulty navigating Paraview. I would
really
>> > appreciate any pointers!
>> >
>> > I'm using code called ASPECT (aspect.dealii.org) to generate models of
the
>> > Earth's interior. My data are unstructured grids that contain
different data
>> > arrays: velocity, temperature, etc. I hope that makes sense. I have a
>> > spherical volume, essentially. I know how to play around with the basic
>> > filters, and I'm able to take spherical slices which represent
>> > velocity/temperature/etc. fields at different depths in the Earth.
>> >
>> > But, I'm not sure how to "flatten" these slices into a map projection
(for
>> > example, a simple rectangle with latitude-longitude axes). Most
tutorials
>> > don't deal with VTK inputs and I'm not familiar enough with Paraview to
>> > figure out my own script.
>> >
>> > Thanks!
>> >
>> > Marie
>> >
>> > _______________________________________________
>> > 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
>> >
>
>
>
>
> --
>
> Centre GEOTOP
> Universit? du Qu?bec ? Montr?al
> C.P. 8888, succursale Centre-ville
> Montr?al, QC  H3C 3P8
>
> +1-514-987-3000 x4600
>
> _______________________________________________
> 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
>



--
| Aashish Chaudhary
| Technical Leader
| Kitware Inc.
| http://www.kitware.com/company/team/chaudhary.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/92c483bb/attachment.html>

From sevensam at udel.edu  Mon Jul 20 10:42:27 2015
From: sevensam at udel.edu (Jesse Samluk)
Date: Mon, 20 Jul 2015 10:42:27 -0400
Subject: [Paraview] Fwd:  Custom animation help? (Corrected image)
References: <A36EE541-B8B0-4BAF-A3DD-2046A86D95B0@udel.edu>
Message-ID: <F1319BB8-288B-4ADC-A58A-28CD14160358@udel.edu>

Cory,

Just ?bumping? this question:

> Paraview for Dummies question - it won?t let me delete that other VTK file in the Pipeline browser (grayed out).
> 
> There?s only an option for delete all (yikes!). Any other suggestions?

Jesse

> Begin forwarded message:
> 
> From: Jesse Samluk <sevensam at udel.edu>
> Subject: Re: [Paraview] Custom animation help? (Corrected image)
> Date: July 15, 2015 at 3:31:19 PM EDT
> To: Cory Quammen <cory.quammen at kitware.com>
> Cc: Paraview <paraview at paraview.org>
> 
> Paraview for Dummies question - it won?t let me delete that other VTK file in the Pipeline browser (grayed out).
> 
> There?s only an option for delete all (yikes!). Any other suggestions?
>> On Jul 15, 2015, at 3:26 PM, Cory Quammen <cory.quammen at kitware.com <mailto:cory.quammen at kitware.com>> wrote:
>> 
>> Jesse,
>> 
>> - Load your state file.
>> - Delete the second VTK file you don't need.
>> - Save the state
>> 
>> That should do it.
>> 
>> Cory
>> 
>> On Wed, Jul 15, 2015 at 3:20 PM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
>> Cory,
>> 
>>   Yes that does the trick, but one more question (and I?ve always wondered this). I had 2 vtk files open in the Pipeline browser when I saved the ?animation track? state file as discussed, but, when I select load state file, it's is now pointing to/asking for two vtk files. 
>> 
>>    Any way to adjust this since I want to open only one vtk file, or am I stuck?
>> 
>>    Thanks again!
>>     Jesse
>> 
>>> On Jul 15, 2015, at 1:08 PM, Cory Quammen <cory.quammen at kitware.com <mailto:cory.quammen at kitware.com>> wrote:
>>> 
>>> Jesse,
>>> 
>>> The animation tracks will be saved in the state file. I just tested ParaView to see if that is the case, and it is. Let us know if it isn't working for you.
>>> 
>>> Thanks,
>>> Cory
>>> 
>>> 
>>> 
>>> On Wed, Jul 15, 2015 at 11:37 AM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
>>> Cory,
>>> 
>>> Right, but isn?t that going to ?throw away? the animation ?tracks" I just created?
>>> 
>>> For instance, I have created an animation with a vtk data set I?m working with. Cool.
>>> 
>>> But say I close Paraview, I lose the animation tracks I just created. Right.
>>> 
>>> So how can I save those animation tracks? Is this even possible in Paraview?
>>> 
>>> Thanks!
>>> Jesse
>>> 
>>>> On Jul 15, 2015, at 10:44 AM, Cory Quammen <cory.quammen at kitware.com <mailto:cory.quammen at kitware.com>> wrote:
>>>> 
>>>> Jesse,
>>>> 
>>>> When you load a state file, you get the chance to update the data file paths in the state file. You can use this mechanism to load a different data file with the same state applied to it.
>>>> 
>>>> HTH,
>>>> Cory
>>>> 
>>>> On Tue, Jul 14, 2015 at 5:36 PM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
>>>> Dan and Cory,
>>>> 
>>>> Thanks for the guides. I?m getting a lot better at animations now! Awesome! The guides helped a lot.
>>>> 
>>>>   1 more quick question for you.
>>>> 
>>>>  I know how to save state files, but is there such a way to save the animation ?state? that I just created in a state file, such that, if I use that state file, the animation scheme will reappear to other data files I?ve created?
>>>> 
>>>>    Wasn?t too sure on this.
>>>> 
>>>>  Thanks!
>>>>   Jesse
>>>>   
>>>>> On Jul 10, 2015, at 5:34 PM, Dan Lipsa <dan.lipsa at kitware.com <mailto:dan.lipsa at kitware.com>> wrote:
>>>>> 
>>>>> Jesse,
>>>>> See also the following thread:
>>>>> 
>>>>> http://markmail.org/search/?q=+programmimg+the+camera+position+using+python#query:%20programmimg%20the%20camera%20position%20using%20python+page:1+mid:nkm5rmw2hz52egnk+state:results <http://markmail.org/search/?q=+programmimg+the+camera+position+using+python#query:%20programmimg%20the%20camera%20position%20using%20python+page:1+mid:nkm5rmw2hz52egnk+state:results>
>>>>> 
>>>>> On Fri, Jul 10, 2015 at 5:19 PM Cory Quammen <cory.quammen at kitware.com <mailto:cory.quammen at kitware.com>> wrote:
>>>>> Hi Jesse,
>>>>> 
>>>>> It should be possible to do this. See Chapter 7 of the ParaView User Guide [1] or Section 2.13 or the ParaView Tutorial [2] for more information.
>>>>> 
>>>>> [1] http://www.paraview.org/paraview-guide/ <http://www.paraview.org/paraview-guide/>
>>>>> [2] http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf <http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf>
>>>>> 
>>>>> HTH,
>>>>> Cory
>>>>> 
>>>>> On Mon, Jul 6, 2015 at 8:56 AM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
>>>>> Greetings all,
>>>>> 
>>>>>   I sent this message last week, but errantly sent the .tif image which made it a huge file. The JPG is now attached.
>>>>> 
>>>>>    I?m trying to make an animation in Paraview. I took a stab at it before with Paraview, but I recall it as being tedious. Maybe I can get some pointers from the experts.
>>>>> 
>>>>>   So, the attached imaged is a cube view of the electromagnetic response over sea ice. What Im trying to do with this animation is two things:
>>>>> 
>>>>>   1.) Move the horizontal slice and Y-Z vertical slice (the slice without the tubes) up and down, and side to side, respectively, such that as if you selected the particular slide in the Pipeline browser, you could drag the slice in question and move it manually to see the different responses. Therefore I?m trying to automate it.
>>>>> 
>>>>>   2.) Rotate it about the z-axis 5 degrees (to about 180) at each iteration and return, then rotate it 5 degrees at each iteration about the y-axis (till about 45 degrees) and return. These rotations will occur while ?action item" 1 is happening.
>>>>> 
>>>>>    Any thoughts/suggestions?
>>>>> 
>>>>>     Thanks!
>>>>>     Jesse
>>>>> 
>>>>> _______________________________________________
>>>>> Powered by www.kitware.com <http://www.kitware.com/>
>>>>> 
>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html <http://www.kitware.com/opensource/opensource.html>
>>>>> 
>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
>>>>> 
>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView <http://markmail.org/search/?q=ParaView>
>>>>> 
>>>>> Follow this link to subscribe/unsubscribe:
>>>>> http://public.kitware.com/mailman/listinfo/paraview <http://public.kitware.com/mailman/listinfo/paraview>
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> -- 
>>>>> Cory Quammen
>>>>> R&D Engineer
>>>>> Kitware, Inc.
>>>>> _______________________________________________
>>>>> Powered by www.kitware.com <http://www.kitware.com/>
>>>>> 
>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html <http://www.kitware.com/opensource/opensource.html>
>>>>> 
>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
>>>>> 
>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView <http://markmail.org/search/?q=ParaView>
>>>>> 
>>>>> Follow this link to subscribe/unsubscribe:
>>>>> http://public.kitware.com/mailman/listinfo/paraview <http://public.kitware.com/mailman/listinfo/paraview>
>>>>> <YZPlaneInitialForParaview.jpeg>
>>>> 
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> Cory Quammen
>>>> R&D Engineer
>>>> Kitware, Inc.
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Cory Quammen
>>> R&D Engineer
>>> Kitware, Inc.
>> 
>> 
>> 
>> 
>> -- 
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
> 

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

From utkarsh.ayachit at kitware.com  Mon Jul 20 10:46:00 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 20 Jul 2015 14:46:00 +0000
Subject: [Paraview] Fwd: Custom animation help? (Corrected image)
In-Reply-To: <F1319BB8-288B-4ADC-A58A-28CD14160358@udel.edu>
References: <A36EE541-B8B0-4BAF-A3DD-2046A86D95B0@udel.edu>
 <F1319BB8-288B-4ADC-A58A-28CD14160358@udel.edu>
Message-ID: <CADHSJjBFTcGSyX-6sU9twsgrZin=H2nWTtxTqAJRzr5SozdO4w@mail.gmail.com>

Jesse,

Delete is typically greyed out when there's a filter connected to that
particular source/filter. You need to delete all downstream stream filters
before you can delete the active one. In other words, you cannot delete a
filter/source in the middle of a pipeline. You can only delete the "sinks"
or leaves.

Utkarsh

On Mon, Jul 20, 2015 at 10:42 AM Jesse Samluk <sevensam at udel.edu> wrote:

> Cory,
>
> Just ?bumping? this question:
>
> Paraview for Dummies question - it won?t let me delete that other VTK file
> in the Pipeline browser (grayed out).
>
> There?s only an option for delete all (yikes!). Any other suggestions?
>
>
> Jesse
>
> Begin forwarded message:
>
> *From: *Jesse Samluk <sevensam at udel.edu>
> *Subject: **Re: [Paraview] Custom animation help? (Corrected image)*
> *Date: *July 15, 2015 at 3:31:19 PM EDT
> *To: *Cory Quammen <cory.quammen at kitware.com>
> *Cc: *Paraview <paraview at paraview.org>
>
>
> Paraview for Dummies question - it won?t let me delete that other VTK file
> in the Pipeline browser (grayed out).
>
> There?s only an option for delete all (yikes!). Any other suggestions?
>
> On Jul 15, 2015, at 3:26 PM, Cory Quammen <cory.quammen at kitware.com>
> wrote:
>
> Jesse,
>
> - Load your state file.
> - Delete the second VTK file you don't need.
> - Save the state
>
> That should do it.
>
> Cory
>
> On Wed, Jul 15, 2015 at 3:20 PM, Jesse Samluk <sevensam at udel.edu> wrote:
>
>> Cory,
>>
>>   Yes that does the trick, but one more question (and I?ve always
>> wondered this). I had 2 vtk files open in the Pipeline browser when I saved
>> the ?animation track? state file as discussed, but, when I select load
>> state file, it's is now pointing to/asking for two vtk files.
>>
>>    Any way to adjust this since I want to open only one vtk file, or am I
>> stuck?
>>
>>    Thanks again!
>>     Jesse
>>
>> On Jul 15, 2015, at 1:08 PM, Cory Quammen <cory.quammen at kitware.com>
>> wrote:
>>
>> Jesse,
>>
>> The animation tracks will be saved in the state file. I just tested
>> ParaView to see if that is the case, and it is. Let us know if it isn't
>> working for you.
>>
>> Thanks,
>> Cory
>>
>>
>>
>> On Wed, Jul 15, 2015 at 11:37 AM, Jesse Samluk <sevensam at udel.edu> wrote:
>>
>>> Cory,
>>>
>>> Right, but isn?t that going to ?throw away? the animation ?tracks" I
>>> just created?
>>>
>>> For instance, I have created an animation with a vtk data set I?m
>>> working with. Cool.
>>>
>>> But say I close Paraview, I lose the animation tracks I just created.
>>> Right.
>>>
>>> So how can I save those animation tracks? Is this even possible in
>>> Paraview?
>>>
>>> Thanks!
>>> Jesse
>>>
>>> On Jul 15, 2015, at 10:44 AM, Cory Quammen <cory.quammen at kitware.com>
>>> wrote:
>>>
>>> Jesse,
>>>
>>> When you load a state file, you get the chance to update the data file
>>> paths in the state file. You can use this mechanism to load a different
>>> data file with the same state applied to it.
>>>
>>> HTH,
>>> Cory
>>>
>>> On Tue, Jul 14, 2015 at 5:36 PM, Jesse Samluk <sevensam at udel.edu> wrote:
>>>
>>>> Dan and Cory,
>>>>
>>>> Thanks for the guides. I?m getting a lot better at animations now!
>>>> Awesome! The guides helped a lot.
>>>>
>>>>   1 more quick question for you.
>>>>
>>>>  I know how to save state files, but is there such a way to save the
>>>> animation ?state? that I just created in a state file, such that, if I use
>>>> that state file, the animation scheme will reappear to other data files
>>>> I?ve created?
>>>>
>>>>    Wasn?t too sure on this.
>>>>
>>>>  Thanks!
>>>>   Jesse
>>>>
>>>>
>>>> On Jul 10, 2015, at 5:34 PM, Dan Lipsa <dan.lipsa at kitware.com> wrote:
>>>>
>>>> Jesse,
>>>> See also the following thread:
>>>>
>>>>
>>>> http://markmail.org/search/?q=+programmimg+the+camera+position+using+python#query:%20programmimg%20the%20camera%20position%20using%20python+page:1+mid:nkm5rmw2hz52egnk+state:results
>>>>
>>>> On Fri, Jul 10, 2015 at 5:19 PM Cory Quammen <cory.quammen at kitware.com>
>>>> wrote:
>>>>
>>>>> Hi Jesse,
>>>>>
>>>>> It should be possible to do this. See Chapter 7 of the ParaView User
>>>>> Guide [1] or Section 2.13 or the ParaView Tutorial [2] for more information.
>>>>>
>>>>> [1] http://www.paraview.org/paraview-guide/
>>>>> [2] http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf
>>>>>
>>>>> HTH,
>>>>> Cory
>>>>>
>>>>> On Mon, Jul 6, 2015 at 8:56 AM, Jesse Samluk <sevensam at udel.edu>
>>>>> wrote:
>>>>>
>>>>>> Greetings all,
>>>>>>
>>>>>>   I sent this message last week, but errantly sent the .tif image
>>>>>> which made it a huge file. The JPG is now attached.
>>>>>>
>>>>>>    I?m trying to make an animation in Paraview. I took a stab at it
>>>>>> before with Paraview, but I recall it as being tedious. Maybe I can get
>>>>>> some pointers from the experts.
>>>>>>
>>>>>>   So, the attached imaged is a cube view of the electromagnetic
>>>>>> response over sea ice. What Im trying to do with this animation is two
>>>>>> things:
>>>>>>
>>>>>>   1.) Move the horizontal slice and Y-Z vertical slice (the slice
>>>>>> without the tubes) up and down, and side to side, respectively, such that
>>>>>> as if you selected the particular slide in the Pipeline browser, you could
>>>>>> drag the slice in question and move it manually to see the different
>>>>>> responses. Therefore I?m trying to automate it.
>>>>>>
>>>>>>   2.) Rotate it about the z-axis 5 degrees (to about 180) at each
>>>>>> iteration and return, then rotate it 5 degrees at each iteration about the
>>>>>> y-axis (till about 45 degrees) and return. These rotations will occur while
>>>>>> ?action item" 1 is happening.
>>>>>>
>>>>>>    Any thoughts/suggestions?
>>>>>>
>>>>>>     Thanks!
>>>>>>     Jesse
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Cory Quammen
>>>>> R&D Engineer
>>>>> Kitware, Inc.
>>>>>  _______________________________________________
>>>>> 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
>>>>>
>>>> <YZPlaneInitialForParaview.jpeg>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Cory Quammen
>>> R&D Engineer
>>> Kitware, Inc.
>>>
>>>
>>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>>
>>
>>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/2ad378d9/attachment.html>

From casey.goodlett at kitware.com  Mon Jul 20 11:23:48 2015
From: casey.goodlett at kitware.com (Casey Goodlett)
Date: Mon, 20 Jul 2015 11:23:48 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAFe6qKh_Xs66xKSNX=1Dqz00DBuXk6vOUrDKnxZRcE8_pNkp7A@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <mo2q49$4gt$1@ger.gmane.org>
 <CAOqyOuGT2uONXRjPd80bJOBdnhugTMyyUCHGn6s8H4Aw+i1wOg@mail.gmail.com>
 <CAFe6qKgK_grq0Vzo0kF8NgiGxU_4T9_6jQrfij3=yZr9y27CEQ@mail.gmail.com>
 <CAFe6qKh_Xs66xKSNX=1Dqz00DBuXk6vOUrDKnxZRcE8_pNkp7A@mail.gmail.com>
Message-ID: <CAOqyOuES4fYzufraBhnXgpJRQ1RH23FLZgeCOMbzLT=VUjZpSA@mail.gmail.com>

Eric,

I am not familiar with the state of ParaView and Qt5 to be able to help.  I
believe there was a status update on the paraview-developers list recently.

Regards,

-- 
Casey B Goodlett, PhD
Technical Leader
Kitware, Inc. - North Carolina Office
http://www.kitware.com
(919) 969-6990 x310
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/c17140b0/attachment.html>

From sevensam at udel.edu  Mon Jul 20 11:26:08 2015
From: sevensam at udel.edu (Jesse Samluk)
Date: Mon, 20 Jul 2015 11:26:08 -0400
Subject: [Paraview] Custom animation help? (Corrected image)
In-Reply-To: <A36EE541-B8B0-4BAF-A3DD-2046A86D95B0@udel.edu>
References: <A9BF9A24-AFD8-41DD-8F0C-446AD9B8702C@udel.edu>
 <CAB5Fpx7yjsZEwk5MtCMVuJ5cVtga=zpfF9rK4S42snNkamAO=A@mail.gmail.com>
 <CADwGrVpXTnqgaD_DciowFwe2pc6KC6r332jLwKBnAESWBjkYKQ@mail.gmail.com>
 <D1509E00-6BFE-42F1-8602-ED230B0C5532@udel.edu>
 <CAB5Fpx6Uw5WdtPK4Zd+9GqyUoKUQ=0zoXhkybWg6XU51nmRSzw@mail.gmail.com>
 <5E88E865-62F4-4C6D-84C4-97839317CB59@udel.edu>
 <CAB5Fpx6NP5EKFf4es7mf+2gu0UmfMPBxgexKQmpHOyORznbrZQ@mail.gmail.com>
 <3654E4A3-D81B-4B91-98A2-CF7BA6210526@udel.edu>
 <CAB5Fpx7dyVKZw29-p+bzPig6QcQCGp5+uGBuRdnFQuu=9kxZ4Q@mail.gmail.com>
 <A36EE541-B8B0-4BAF-A3DD-2046A86D95B0@udel.edu>
Message-ID: <BC76E4E2-3782-4F10-91C3-06C16B56B39B@udel.edu>

Cool - I got it! 

Thanks guys for all of your help!
Jesse
> On Jul 15, 2015, at 3:31 PM, Jesse Samluk <sevensam at UDel.Edu> wrote:
> 
> Paraview for Dummies question - it won?t let me delete that other VTK file in the Pipeline browser (grayed out).
> 
> There?s only an option for delete all (yikes!). Any other suggestions?
>> On Jul 15, 2015, at 3:26 PM, Cory Quammen <cory.quammen at kitware.com <mailto:cory.quammen at kitware.com>> wrote:
>> 
>> Jesse,
>> 
>> - Load your state file.
>> - Delete the second VTK file you don't need.
>> - Save the state
>> 
>> That should do it.
>> 
>> Cory
>> 
>> On Wed, Jul 15, 2015 at 3:20 PM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
>> Cory,
>> 
>>   Yes that does the trick, but one more question (and I?ve always wondered this). I had 2 vtk files open in the Pipeline browser when I saved the ?animation track? state file as discussed, but, when I select load state file, it's is now pointing to/asking for two vtk files. 
>> 
>>    Any way to adjust this since I want to open only one vtk file, or am I stuck?
>> 
>>    Thanks again!
>>     Jesse
>> 
>>> On Jul 15, 2015, at 1:08 PM, Cory Quammen <cory.quammen at kitware.com <mailto:cory.quammen at kitware.com>> wrote:
>>> 
>>> Jesse,
>>> 
>>> The animation tracks will be saved in the state file. I just tested ParaView to see if that is the case, and it is. Let us know if it isn't working for you.
>>> 
>>> Thanks,
>>> Cory
>>> 
>>> 
>>> 
>>> On Wed, Jul 15, 2015 at 11:37 AM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
>>> Cory,
>>> 
>>> Right, but isn?t that going to ?throw away? the animation ?tracks" I just created?
>>> 
>>> For instance, I have created an animation with a vtk data set I?m working with. Cool.
>>> 
>>> But say I close Paraview, I lose the animation tracks I just created. Right.
>>> 
>>> So how can I save those animation tracks? Is this even possible in Paraview?
>>> 
>>> Thanks!
>>> Jesse
>>> 
>>>> On Jul 15, 2015, at 10:44 AM, Cory Quammen <cory.quammen at kitware.com <mailto:cory.quammen at kitware.com>> wrote:
>>>> 
>>>> Jesse,
>>>> 
>>>> When you load a state file, you get the chance to update the data file paths in the state file. You can use this mechanism to load a different data file with the same state applied to it.
>>>> 
>>>> HTH,
>>>> Cory
>>>> 
>>>> On Tue, Jul 14, 2015 at 5:36 PM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
>>>> Dan and Cory,
>>>> 
>>>> Thanks for the guides. I?m getting a lot better at animations now! Awesome! The guides helped a lot.
>>>> 
>>>>   1 more quick question for you.
>>>> 
>>>>  I know how to save state files, but is there such a way to save the animation ?state? that I just created in a state file, such that, if I use that state file, the animation scheme will reappear to other data files I?ve created?
>>>> 
>>>>    Wasn?t too sure on this.
>>>> 
>>>>  Thanks!
>>>>   Jesse
>>>>   
>>>>> On Jul 10, 2015, at 5:34 PM, Dan Lipsa <dan.lipsa at kitware.com <mailto:dan.lipsa at kitware.com>> wrote:
>>>>> 
>>>>> Jesse,
>>>>> See also the following thread:
>>>>> 
>>>>> http://markmail.org/search/?q=+programmimg+the+camera+position+using+python#query:%20programmimg%20the%20camera%20position%20using%20python+page:1+mid:nkm5rmw2hz52egnk+state:results <http://markmail.org/search/?q=+programmimg+the+camera+position+using+python#query:%20programmimg%20the%20camera%20position%20using%20python+page:1+mid:nkm5rmw2hz52egnk+state:results>
>>>>> 
>>>>> On Fri, Jul 10, 2015 at 5:19 PM Cory Quammen <cory.quammen at kitware.com <mailto:cory.quammen at kitware.com>> wrote:
>>>>> Hi Jesse,
>>>>> 
>>>>> It should be possible to do this. See Chapter 7 of the ParaView User Guide [1] or Section 2.13 or the ParaView Tutorial [2] for more information.
>>>>> 
>>>>> [1] http://www.paraview.org/paraview-guide/ <http://www.paraview.org/paraview-guide/>
>>>>> [2] http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf <http://www.paraview.org/Wiki/images/f/f4/ParaViewTutorial42.pdf>
>>>>> 
>>>>> HTH,
>>>>> Cory
>>>>> 
>>>>> On Mon, Jul 6, 2015 at 8:56 AM, Jesse Samluk <sevensam at udel.edu <mailto:sevensam at udel.edu>> wrote:
>>>>> Greetings all,
>>>>> 
>>>>>   I sent this message last week, but errantly sent the .tif image which made it a huge file. The JPG is now attached.
>>>>> 
>>>>>    I?m trying to make an animation in Paraview. I took a stab at it before with Paraview, but I recall it as being tedious. Maybe I can get some pointers from the experts.
>>>>> 
>>>>>   So, the attached imaged is a cube view of the electromagnetic response over sea ice. What Im trying to do with this animation is two things:
>>>>> 
>>>>>   1.) Move the horizontal slice and Y-Z vertical slice (the slice without the tubes) up and down, and side to side, respectively, such that as if you selected the particular slide in the Pipeline browser, you could drag the slice in question and move it manually to see the different responses. Therefore I?m trying to automate it.
>>>>> 
>>>>>   2.) Rotate it about the z-axis 5 degrees (to about 180) at each iteration and return, then rotate it 5 degrees at each iteration about the y-axis (till about 45 degrees) and return. These rotations will occur while ?action item" 1 is happening.
>>>>> 
>>>>>    Any thoughts/suggestions?
>>>>> 
>>>>>     Thanks!
>>>>>     Jesse
>>>>> 
>>>>> _______________________________________________
>>>>> Powered by www.kitware.com <http://www.kitware.com/>
>>>>> 
>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html <http://www.kitware.com/opensource/opensource.html>
>>>>> 
>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
>>>>> 
>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView <http://markmail.org/search/?q=ParaView>
>>>>> 
>>>>> Follow this link to subscribe/unsubscribe:
>>>>> http://public.kitware.com/mailman/listinfo/paraview <http://public.kitware.com/mailman/listinfo/paraview>
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> -- 
>>>>> Cory Quammen
>>>>> R&D Engineer
>>>>> Kitware, Inc.
>>>>> _______________________________________________
>>>>> Powered by www.kitware.com <http://www.kitware.com/>
>>>>> 
>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html <http://www.kitware.com/opensource/opensource.html>
>>>>> 
>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
>>>>> 
>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView <http://markmail.org/search/?q=ParaView>
>>>>> 
>>>>> Follow this link to subscribe/unsubscribe:
>>>>> http://public.kitware.com/mailman/listinfo/paraview <http://public.kitware.com/mailman/listinfo/paraview>
>>>>> <YZPlaneInitialForParaview.jpeg>
>>>> 
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> Cory Quammen
>>>> R&D Engineer
>>>> Kitware, Inc.
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Cory Quammen
>>> R&D Engineer
>>> Kitware, Inc.
>> 
>> 
>> 
>> 
>> -- 
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
> 

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

From guanw at rhpcs.mcmaster.ca  Mon Jul 20 11:33:12 2015
From: guanw at rhpcs.mcmaster.ca (Weiguang guan)
Date: Mon, 20 Jul 2015 11:33:12 -0400
Subject: [Paraview] number of points in the Information tab
In-Reply-To: <55AD11EF.8040600@sharcnet.ca>
References: <55AD11EF.8040600@sharcnet.ca>
Message-ID: <55AD14B8.1020207@rhpcs.mcmaster.ca>

A naive question: how can a cylinder with resolution=10 have 40 points?

Best,
Weiguang


From cory.quammen at kitware.com  Mon Jul 20 11:56:38 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Mon, 20 Jul 2015 11:56:38 -0400
Subject: [Paraview] number of points in the Information tab
In-Reply-To: <55AD14B8.1020207@rhpcs.mcmaster.ca>
References: <55AD11EF.8040600@sharcnet.ca> <55AD14B8.1020207@rhpcs.mcmaster.ca>
Message-ID: <CAB5Fpx5FHJc5FeHHUe2X6BraBjFuUbyn8+05aq3mFUpMseRfWQ@mail.gmail.com>

Weiguang,

Points are duplicated for the polygons defining the end caps so that a
separate normal for the end cap can be specified - it's a common computer
graphics technique to get sharp edges where desired. Uncheck the "Capping"
property and your source will have 20 points as you probably expected (but
no end caps).

If the point duplicating weren't done, the cylinder would look funny at the
ends. Try running the Clean filter on the cylinder to see what it would
look like. This merges the duplicate points.

Cory

On Mon, Jul 20, 2015 at 11:33 AM, Weiguang guan <guanw at rhpcs.mcmaster.ca>
wrote:

> A naive question: how can a cylinder with resolution=10 have 40 points?
>
> Best,
> Weiguang
>
> _______________________________________________
> 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
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/880bfdc5/attachment-0001.html>

From guanw at rhpcs.mcmaster.ca  Mon Jul 20 12:47:01 2015
From: guanw at rhpcs.mcmaster.ca (Weiguang guan)
Date: Mon, 20 Jul 2015 12:47:01 -0400
Subject: [Paraview] number of points in the Information tab
In-Reply-To: <CAB5Fpx5FHJc5FeHHUe2X6BraBjFuUbyn8+05aq3mFUpMseRfWQ@mail.gmail.com>
References: <55AD11EF.8040600@sharcnet.ca> <55AD14B8.1020207@rhpcs.mcmaster.ca>
 <CAB5Fpx5FHJc5FeHHUe2X6BraBjFuUbyn8+05aq3mFUpMseRfWQ@mail.gmail.com>
Message-ID: <55AD2605.2000306@rhpcs.mcmaster.ca>

Thanks for the answer, Cory.

Weiguang

On 20/07/2015 11:56 AM, Cory Quammen wrote:
> Weiguang,
>
> Points are duplicated for the polygons defining the end caps so that a 
> separate normal for the end cap can be specified - it's a common 
> computer graphics technique to get sharp edges where desired. Uncheck 
> the "Capping" property and your source will have 20 points as you 
> probably expected (but no end caps).
>
> If the point duplicating weren't done, the cylinder would look funny 
> at the ends. Try running the Clean filter on the cylinder to see what 
> it would look like. This merges the duplicate points.
>
> Cory
>
> On Mon, Jul 20, 2015 at 11:33 AM, Weiguang guan 
> <guanw at rhpcs.mcmaster.ca <mailto:guanw at rhpcs.mcmaster.ca>> wrote:
>
>     A naive question: how can a cylinder with resolution=10 have 40
>     points?
>
>     Best,
>     Weiguang
>
>     _______________________________________________
>     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
>
>
>
>
> -- 
> Cory Quammen
> R&D Engineer
> Kitware, Inc.

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

From marie.kajan at gmail.com  Mon Jul 20 13:41:45 2015
From: marie.kajan at gmail.com (Marie Kajan)
Date: Mon, 20 Jul 2015 13:41:45 -0400
Subject: [Paraview] Transforming a spherical slice into a map projection
In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F6841F1E77B@MBX211.d.ethz.ch>
References: <CAK3vnGc2pHaxZXhGtto8JzOo6Nu_UL84+rEMES6z5-x6Ei+=bw@mail.gmail.com>
 <CADHSJjAZmDV+7QY7VqAEMxWtumyDK08fGyjpWT8T-JwVY8y4og@mail.gmail.com>
 <CAK3vnGf8e_AHmruBokgujpBCqyA44_A1eX2dwxNSEN0WvkdjUw@mail.gmail.com>
 <0EB9B6375711A04B820E6B6F5CCA9F6841F1E77B@MBX211.d.ethz.ch>
Message-ID: <CAK3vnGe7qhDN=h25U3gdS=D6+ZhkDb-wPTphJd-2Ua2r1ojZcQ@mail.gmail.com>

This looks beautiful, and exactly what I wanted. Thank you so much! I'll
work with this and let you know if I have any significant difficulties
moving forward (but I'll definitely read that section of the Paraview
manual first).


Marie

On Mon, Jul 20, 2015 at 6:25 AM, Favre Jean <jfavre at cscs.ch> wrote:

>  Here is a state file to try, and the snapshot I created.
>
> The sampling resolution is set to be 128x64. You can change that to
> anything you want, in the ProgrammableSource. Two objects are created (a
> sphere and a plane). The sphere is used to resample the volume. The plane
> is used, to "flatten" the data copied over from the sphere.
>
> Details on how to use the Programmable Sources and Filters are in the PV
> Guide (Chapter 13)
>
> let me know if this works.
>  -----------------
> Jean M. Favre
> Swiss National Supercomputing Center
> CH-6900 Lugano
> Switzerland
>
>


-- 

Centre GEOTOP
Universit? du Qu?bec ? Montr?al
C.P. 8888, succursale Centre-ville
Montr?al, QC  H3C 3P8

+1-514-987-3000 x4600
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/fa6ea56d/attachment.html>

From utkarsh.ayachit at kitware.com  Mon Jul 20 13:47:44 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 20 Jul 2015 17:47:44 +0000
Subject: [Paraview] [EXTERNAL] Re: Plot cumulative integral over time of
	a variable
In-Reply-To: <44ad446b7cb6458ba17586111bca0cd7@ES01AMSNLNT.srn.sandia.gov>
References: <f00630c065ee4933aff5a6f5aeee21d7@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjAu=058y7Wj0-CkxMCM3_Y7ngMHV9GEG3eOYyy-Gz_wyQ@mail.gmail.com>
 <44ad446b7cb6458ba17586111bca0cd7@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjDT_mDxC2stCSAqnnSwK+MgC+7rqiPj4O4kbaQ10texWQ@mail.gmail.com>

Yes, the change is already merged in VTK. It'll make it to ParaView soon.

Utkarsh

On Wed, Jul 15, 2015 at 12:38 PM Scott, W Alan <wascott at sandia.gov> wrote:

>  Thanks!
>
>
>
> Are you going to get the patch into the next release?
>
>
>
> Alan
>
>
>
> *From:* Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> *Sent:* Wednesday, July 15, 2015 9:06 AM
> *To:* Scott, W Alan; paraview at paraview.org
> *Subject:* [EXTERNAL] Re: [Paraview] Plot cumulative integral over time
> of a variable
>
>
>
> Alan,
>
>
> Attached is a state file (using can.ex2) which indeed uses numpy.trapz()
> to do the work. It needs a small patch to be applied to VTK (attached) to
> avoid a segfault.
>
>
>
> The Programmable Filter adds a new row-data array named "trapz" which is
> the result of the operation (it's repeated so we can add it to RowData
> rather than field data.
>
>
>
> Utkarsh
>
> On Tue, Jul 14, 2015 at 7:23 PM Scott, W Alan <wascott at sandia.gov> wrote:
>
>  Question from a user:
>
>
>
> I would like to use paraview to do the following:
>
>
>
> 1)      Integrate a nodal variable over a volume (IntegrateVariables
> filter does this)
>
>
>
> 2)      Then, integrate the result of the volume integral over time
> (cumulative integral)
>
>
>
> The "IntegrateVariables" filter works just fine to integrate over the
> volume, and I can plot the results of it over time by selecting "RowData"
> from the "PlotSelectionOverTime" filter.  I just can't figure out how to do
> #2 - integrate these results over time with something like "numpy.trapz" or
> "scipy.integrate.cumtrapz".
>
>
>
> I feel like this has probably been asked a million times, but I still seem
> to have trouble with it.  I think I usually fall back to other post
> processing tools.  Can this be done all in Paraview?
>
>
>
>
>
>
>
> Thanks,
>
>
>
> Alan
>
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/ea407afc/attachment.html>

From jeffrey.c.becker at nasa.gov  Mon Jul 20 14:08:24 2015
From: jeffrey.c.becker at nasa.gov (Jeff Becker)
Date: Mon, 20 Jul 2015 11:08:24 -0700
Subject: [Paraview] Combining vtk and paraview python scripts
In-Reply-To: <CAE32kpXDT5cq51PBged+9HF=pFcpEMJeZq9oJGaC6Mmqx2coSA@mail.gmail.com>
References: <55A55C2C.2030107@nasa.gov>
 <CAMaOp+GaBL5wqsU4YiQ5-VpZWqzDjPF8=oc6p950Oums+01+Zg@mail.gmail.com>
 <55A56672.3040204@nasa.gov>
 <CAE32kpXDT5cq51PBged+9HF=pFcpEMJeZq9oJGaC6Mmqx2coSA@mail.gmail.com>
Message-ID: <55AD3918.3030808@nasa.gov>

Hi,

On 07/18/2015 05:17 PM, Berk Geveci wrote:
> To elaborate on what Andy said, you can stick your entire VTK script 
> in side the programmable source. Which you can use in batch mode as 
> well. If you want to keep your VTK script as a reusable code, I 
> recommend making it a module that you import from the programmable source.

So if the last thing my VTK script does is set up a vtkImageImport 
object should that work as a programmable source (I tried but ParaView 
didn't get any bounds or scalar field name even though I set them up)? 
If not, what else do I need to do? Thanks.

-jeff

>
> Best,
> -berk
>
> On Tue, Jul 14, 2015 at 3:43 PM, Jeff Becker 
> <jeffrey.c.becker at nasa.gov <mailto:jeffrey.c.becker at nasa.gov>> wrote:
>
>     On 07/14/2015 12:20 PM, Andy Bauer wrote:
>>     ParaView's Python Programmable Filter and Python Programmable
>>     Source use VTK Python wrapping to do the work while making it
>>     available in Paraview. Check out
>>     http://www.paraview.org/Wiki/Python_Programmable_Filter.
>
>     Thanks. That's pretty neat, but what I'd really like is a
>     standalone script I can run in batch mode (no interaction) to
>     generate one png file per timestep for all the timesteps in the
>     data set. Essentially I'd like a way to construct a pipeline
>     between the vtk.vtkImageImport() object and the ParaView renderView1.
>
>     -jeff
>
>>
>>     On Tue, Jul 14, 2015 at 2:59 PM, Jeff Becker
>>     <jeffrey.c.becker at nasa.gov <mailto:jeffrey.c.becker at nasa.gov>> wrote:
>>
>>         Hi.
>>
>>         As a proof of concept, I have a vtk script that reads some
>>         binary data, and produces a vti file. I then have a second
>>         script that I generated using ParaView's tracing facility
>>         while viewing the data. Now I'd like to combine them, so as
>>         to eliminate the intermediate file, i.e., go from binary data
>>         directly to rendering. To be specific, my vtk script ends
>>         like this:
>>
>>         steinbmag = steinbmag.reshape(nx,ny,nz).T
>>
>>         vtkImporter = vtk.vtkImageImport()
>>         vtkImporter.CopyImportVoidPointer(steinbmag, steinbmag.nbytes)
>>
>>         vtkImporter.SetDataScalarTypeToFloat()
>>         vtkImporter.SetNumberOfScalarComponents(1)
>>         vtkImporter.SetDataExtent(0, nx-1, 0, ny-1, 0, nz-1)
>>         vtkImporter.SetWholeExtent(0, nx-1, 0, ny-1, 0, nz-1)
>>         vtkImporter.SetScalarArrayName('B field magnitude')
>>
>>         writer=vtk.vtkXMLImageDataWriter()
>>         writer.SetFileName(out_fname)
>>         writer.SetInputConnection(vtkImporter.GetOutputPort())
>>         writer.Write()
>>
>>         and the ParaView script starts like this:
>>
>>         from paraview.simple import *
>>
>>         paraview.simple._DisableFirstRenderCameraReset()
>>
>>         filepfx = '/nobackup/jcbecker/steinBmag_0'
>>         infile = filepfx+'.vti'
>>         # create a new 'XML Image Data Reader'
>>         steinBmag_ = XMLImageDataReader(FileName=infile)
>>         steinBmag_.CellArrayStatus = []
>>         steinBmag_.PointArrayStatus = ['B field magnitude']
>>
>>         # get animation scene
>>         animationScene1 = GetAnimationScene()
>>
>>         # update animation scene based on data timesteps
>>         animationScene1.UpdateAnimationUsingDataTimeSteps()
>>
>>         # get active view
>>         renderView1 = GetActiveViewOrCreate('RenderView')
>>         # uncomment following to set a specific view size
>>         renderView1.ViewSize = [1090, 761]
>>
>>         I'm looking at the VTK examples and pvpython documentation,
>>         but any help is appreciated.
>>
>>         Thanks.
>>
>>         -jeff
>>         _______________________________________________
>>         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 <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
>
>

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

From berk.geveci at kitware.com  Mon Jul 20 20:43:59 2015
From: berk.geveci at kitware.com (Berk Geveci)
Date: Mon, 20 Jul 2015 20:43:59 -0400
Subject: [Paraview] Combining vtk and paraview python scripts
In-Reply-To: <55AD3918.3030808@nasa.gov>
References: <55A55C2C.2030107@nasa.gov>
 <CAMaOp+GaBL5wqsU4YiQ5-VpZWqzDjPF8=oc6p950Oums+01+Zg@mail.gmail.com>
 <55A56672.3040204@nasa.gov>
 <CAE32kpXDT5cq51PBged+9HF=pFcpEMJeZq9oJGaC6Mmqx2coSA@mail.gmail.com>
 <55AD3918.3030808@nasa.gov>
Message-ID: <CAE32kpW9LoazpP6Xu_3WUmVMqE8FoA0kiw5TRAXrwwms0OBOQg@mail.gmail.com>

You probably need to update vtkImageExport and shallow copy its output to
the programmable source's output. You also need to add something to the
RequestInformation setting the whole extent. You need something like:

from paraview import util

util.SetOutputWholeExtent(self, [0,nx-1,0,ny-1,0,nz-1])

By the way, there are better ways of getting numpy arrays into VTK than the
image import stuff. See some of the earlier blogs here:

http://www.kitware.com/blog/home/user/53/2

Best,
-berk

On Mon, Jul 20, 2015 at 2:08 PM, Jeff Becker <jeffrey.c.becker at nasa.gov>
wrote:

>  Hi,
>
> On 07/18/2015 05:17 PM, Berk Geveci wrote:
>
> To elaborate on what Andy said, you can stick your entire VTK script in
> side the programmable source. Which you can use in batch mode as well. If
> you want to keep your VTK script as a reusable code, I recommend making it
> a module that you import from the programmable source.
>
>
> So if the last thing my VTK script does is set up a vtkImageImport object
> should that work as a programmable source (I tried but ParaView didn't get
> any bounds or scalar field name even though I set them up)? If not, what
> else do I need to do? Thanks.
>
> -jeff
>
>
>
>  Best,
> -berk
>
> On Tue, Jul 14, 2015 at 3:43 PM, Jeff Becker <jeffrey.c.becker at nasa.gov>
> wrote:
>
>>  On 07/14/2015 12:20 PM, Andy Bauer wrote:
>>
>> ParaView's Python Programmable Filter and Python Programmable Source use
>> VTK Python wrapping to do the work while making it available in Paraview.
>> Check out http://www.paraview.org/Wiki/Python_Programmable_Filter.
>>
>>
>>  Thanks. That's pretty neat, but what I'd really like is a standalone
>> script I can run in batch mode (no interaction) to generate one png file
>> per timestep for all the timesteps in the data set. Essentially I'd like a
>> way to construct a pipeline between the vtk.vtkImageImport()  object and
>> the ParaView renderView1.
>>
>> -jeff
>>
>>
>> On Tue, Jul 14, 2015 at 2:59 PM, Jeff Becker <jeffrey.c.becker at nasa.gov>
>> wrote:
>>
>>> Hi.
>>>
>>> As a proof of concept, I have a vtk script that reads some binary data,
>>> and produces a vti file. I then have a second script that I generated using
>>> ParaView's tracing facility while viewing the data. Now I'd like to combine
>>> them, so as to eliminate the intermediate file, i.e., go from binary data
>>> directly to rendering. To be specific, my vtk script ends like this:
>>>
>>> steinbmag = steinbmag.reshape(nx,ny,nz).T
>>>
>>> vtkImporter = vtk.vtkImageImport()
>>> vtkImporter.CopyImportVoidPointer(steinbmag, steinbmag.nbytes)
>>>
>>> vtkImporter.SetDataScalarTypeToFloat()
>>> vtkImporter.SetNumberOfScalarComponents(1)
>>> vtkImporter.SetDataExtent(0, nx-1, 0, ny-1, 0, nz-1)
>>> vtkImporter.SetWholeExtent(0, nx-1, 0, ny-1, 0, nz-1)
>>> vtkImporter.SetScalarArrayName('B field magnitude')
>>>
>>> writer=vtk.vtkXMLImageDataWriter()
>>> writer.SetFileName(out_fname)
>>> writer.SetInputConnection(vtkImporter.GetOutputPort())
>>> writer.Write()
>>>
>>> and the ParaView script starts like this:
>>>
>>> from paraview.simple import *
>>>
>>> paraview.simple._DisableFirstRenderCameraReset()
>>>
>>> filepfx = '/nobackup/jcbecker/steinBmag_0'
>>> infile = filepfx+'.vti'
>>> # create a new 'XML Image Data Reader'
>>> steinBmag_ = XMLImageDataReader(FileName=infile)
>>> steinBmag_.CellArrayStatus = []
>>> steinBmag_.PointArrayStatus = ['B field magnitude']
>>>
>>> # get animation scene
>>> animationScene1 = GetAnimationScene()
>>>
>>> # update animation scene based on data timesteps
>>> animationScene1.UpdateAnimationUsingDataTimeSteps()
>>>
>>> # get active view
>>> renderView1 = GetActiveViewOrCreate('RenderView')
>>> # uncomment following to set a specific view size
>>> renderView1.ViewSize = [1090, 761]
>>>
>>> I'm looking at the VTK examples and pvpython documentation, but any help
>>> is appreciated.
>>>
>>> Thanks.
>>>
>>> -jeff
>>> _______________________________________________
>>> 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
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/10564079/attachment.html>

From lmorandini at ieee.org  Tue Jul 21 03:04:22 2015
From: lmorandini at ieee.org (Luca Morandini)
Date: Tue, 21 Jul 2015 17:04:22 +1000
Subject: [Paraview] Point clouds and computing PCA on voxels
In-Reply-To: <CAFe6qKifkpvupRtb1EMhYe3+OJEOa58pkp69aFWdKMZzFDOiRg@mail.gmail.com>
References: <mocupi$4m1$1@ger.gmane.org>
 <CAFe6qKifkpvupRtb1EMhYe3+OJEOa58pkp69aFWdKMZzFDOiRg@mail.gmail.com>
Message-ID: <mokqtn$k5m$1@ger.gmane.org>

On 20/07/15 23:29, Eric Younkin - NOAA Federal wrote:
> Luca,
>
> Have you seen this
> <http://pointclouds.org/documentation/tutorials/normal_estimation.php>?  Are you
> just looking for a more detailed example?  I'm also looking to eventually do
> something similar, once I get it all set up in the end.

I am not searching for the normal to a surface, but the orientation of a cloud of 
points (in other words, PCA) to tell a wall from a cable (a wall should have big 
first and second eigenvalues and a small third one, while a cable should have a 
big first eigenvalues, and small second and third ones).

Anyway, a fragment of Python calling a vtkPCAStatistics on point data would be 
great (my very first steps in both ParaView and Python, so bear with me).

Cheers,

Luca Morandini
Data Architect - AURIN project
Melbourne eResearch Group
Department of Computing and Information Systems
University of Melbourne
Tel. +61 03 903 58 380
Skype: lmorandini


From lmorandini at ieee.org  Tue Jul 21 03:36:32 2015
From: lmorandini at ieee.org (Luca Morandini)
Date: Tue, 21 Jul 2015 17:36:32 +1000
Subject: [Paraview] Compilation problem of ParaView 3.14.1 on Ubuntu
	14.04
In-Reply-To: <CAFync2juzq+_=74_7BzMbCk9EpWghjg40RsR-gZsXXBVVWj6Mg@mail.gmail.com>
References: <mo2g4i$4io$1@ger.gmane.org>
 <CAFzjYVpax_BsYW3M94FuV+08AaG-Nf3qEW5zdTmOKVYUVTUuFQ@mail.gmail.com>
 <mo7c3c$ftj$1@ger.gmane.org>
 <CAFync2juzq+_=74_7BzMbCk9EpWghjg40RsR-gZsXXBVVWj6Mg@mail.gmail.com>
Message-ID: <moksq2$hdp$1@ger.gmane.org>

On 20/07/15 22:49, Stefan Otte wrote:
> Hey,
>
> I also had problems compiling paraview. There is a pre-build binary
> [1] for Mac, Linux, and Windows. However, the OpenNI source is not
> included.

Thanks, but I tried that out and seemed a bit brittle to me (I managed to crashed 
it while testing a programmable filter); moreover, I would have liked something 
more current.

However, I'm currently using the Project Tango build for Ubuntu, since my static 
build is not terribly stable either (I presume my Ubuntu box has some library 
version inconsistency).


> Luca, is the OpenNI source available for you after you compiled everything?

Hmm... I don;t quite get the question: do you mind elaborating?

Cheers,

Luca Morandini
Data Architect - AURIN project
Melbourne eResearch Group
Department of Computing and Information Systems
University of Melbourne
Tel. +61 03 903 58 380
Skype: lmorandini


From stephen.wornom at inria.fr  Tue Jul 21 04:58:09 2015
From: stephen.wornom at inria.fr (Stephen Wornom)
Date: Tue, 21 Jul 2015 10:58:09 +0200
Subject: [Paraview] PV 4.10 plot over line using mesh coordinates
Message-ID: <55AE09A1.8040504@inria.fr>

One of the inputs to Plot over line  is the number of points (equally 
spaced, I assumed).
The solution is interpolated to the points. This poses a problem for 
highly stretched meshes like the normal coordinate in a boundary layer.

I would like to plot over line using the actual mesh values and NOT the 
interpolated values.
Is this possible in PV?

How do I extract a line using the filters? That would be useful.

Hope my questions are clear,
Stephen


-- 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: stephen_wornom.vcf
Type: text/x-vcard
Size: 109 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150721/666946e2/attachment.vcf>

From oksana_golovnya at mail.ru  Tue Jul 21 09:20:39 2015
From: oksana_golovnya at mail.ru (=?UTF-8?B?T2tzYW5h?=)
Date: Tue, 21 Jul 2015 16:20:39 +0300
Subject: [Paraview] =?utf-8?q?Molecular_dynamics_from_lammps?=
In-Reply-To: <CAE32kpW9hj4bQK6eqvvDT4JDVmhE+naOMs6VyPm7haU2gODZPA@mail.gmail.com>
References: <1436279999.571994242@f345.i.mail.ru>
 <1436852798.517668428@f416.i.mail.ru>
 <CAE32kpW9hj4bQK6eqvvDT4JDVmhE+naOMs6VyPm7haU2gODZPA@mail.gmail.com>
Message-ID: <1437484839.365648603@f303.i.mail.ru>

 Dear Berk,

Thank you for the reply. I was trying to use the Python Calculator.? I created a plane source, but I do not know how to put it into projection calculation. The idea was to use one normal vector to find dislacement vectors projections in a plane. How to create a threshold I have no idea at all. May be you could provide some more reference.

Faithfully yours,
Oksana
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150721/3aa5c1aa/attachment.html>

From jeffrey.c.becker at nasa.gov  Tue Jul 21 12:14:06 2015
From: jeffrey.c.becker at nasa.gov (Jeff Becker)
Date: Tue, 21 Jul 2015 09:14:06 -0700
Subject: [Paraview] Combining vtk and paraview python scripts
In-Reply-To: <CAE32kpW9LoazpP6Xu_3WUmVMqE8FoA0kiw5TRAXrwwms0OBOQg@mail.gmail.com>
References: <55A55C2C.2030107@nasa.gov>
 <CAMaOp+GaBL5wqsU4YiQ5-VpZWqzDjPF8=oc6p950Oums+01+Zg@mail.gmail.com>
 <55A56672.3040204@nasa.gov>
 <CAE32kpXDT5cq51PBged+9HF=pFcpEMJeZq9oJGaC6Mmqx2coSA@mail.gmail.com>
 <55AD3918.3030808@nasa.gov>
 <CAE32kpW9LoazpP6Xu_3WUmVMqE8FoA0kiw5TRAXrwwms0OBOQg@mail.gmail.com>
Message-ID: <55AE6FCE.2010407@nasa.gov>

On 07/20/2015 05:43 PM, Berk Geveci wrote:
> You probably need to update vtkImageExport and shallow copy its output 
> to the programmable source's output. You also need to add something to 
> the RequestInformation setting the whole extent. You need something like:
>
> from paraview import util
> util.SetOutputWholeExtent(self, [0,nx-1,0,ny-1,0,nz-1])
>
> By the way, there are better ways of getting numpy arrays into VTK 
> than the image import stuff. See some of the earlier blogs here:

Right. I found the RequestInformation info above from searching the web. 
Then I was able to follow the instructions in the ParaView Guide section 
13.2.4 Reading binary 2D image. I basically replaced the image import 
stuff with code analogous  to the output assignment,

Thanks for your help.

-jeff

>
> http://www.kitware.com/blog/home/user/53/2
>
> Best,
> -berk
>
> On Mon, Jul 20, 2015 at 2:08 PM, Jeff Becker 
> <jeffrey.c.becker at nasa.gov <mailto:jeffrey.c.becker at nasa.gov>> wrote:
>
>     Hi,
>
>     On 07/18/2015 05:17 PM, Berk Geveci wrote:
>>     To elaborate on what Andy said, you can stick your entire VTK
>>     script in side the programmable source. Which you can use in
>>     batch mode as well. If you want to keep your VTK script as a
>>     reusable code, I recommend making it a module that you import
>>     from the programmable source.
>
>     So if the last thing my VTK script does is set up a vtkImageImport
>     object should that work as a programmable source (I tried but
>     ParaView didn't get any bounds or scalar field name even though I
>     set them up)? If not, what else do I need to do? Thanks.
>
>     -jeff
>
>
>>
>>     Best,
>>     -berk
>>
>>     On Tue, Jul 14, 2015 at 3:43 PM, Jeff Becker
>>     <jeffrey.c.becker at nasa.gov <mailto:jeffrey.c.becker at nasa.gov>> wrote:
>>
>>         On 07/14/2015 12:20 PM, Andy Bauer wrote:
>>>         ParaView's Python Programmable Filter and Python
>>>         Programmable Source use VTK Python wrapping to do the work
>>>         while making it available in Paraview. Check out
>>>         http://www.paraview.org/Wiki/Python_Programmable_Filter.
>>
>>         Thanks. That's pretty neat, but what I'd really like is a
>>         standalone script I can run in batch mode (no interaction) to
>>         generate one png file per timestep for all the timesteps in
>>         the data set. Essentially I'd like a way to construct a
>>         pipeline between the vtk.vtkImageImport()  object and the
>>         ParaView renderView1.
>>
>>         -jeff
>>
>>>
>>>         On Tue, Jul 14, 2015 at 2:59 PM, Jeff Becker
>>>         <jeffrey.c.becker at nasa.gov
>>>         <mailto:jeffrey.c.becker at nasa.gov>> wrote:
>>>
>>>             Hi.
>>>
>>>             As a proof of concept, I have a vtk script that reads
>>>             some binary data, and produces a vti file. I then have a
>>>             second script that I generated using ParaView's tracing
>>>             facility while viewing the data. Now I'd like to combine
>>>             them, so as to eliminate the intermediate file, i.e., go
>>>             from binary data directly to rendering. To be specific,
>>>             my vtk script ends like this:
>>>
>>>             steinbmag = steinbmag.reshape(nx,ny,nz).T
>>>
>>>             vtkImporter = vtk.vtkImageImport()
>>>             vtkImporter.CopyImportVoidPointer(steinbmag,
>>>             steinbmag.nbytes)
>>>
>>>             vtkImporter.SetDataScalarTypeToFloat()
>>>             vtkImporter.SetNumberOfScalarComponents(1)
>>>             vtkImporter.SetDataExtent(0, nx-1, 0, ny-1, 0, nz-1)
>>>             vtkImporter.SetWholeExtent(0, nx-1, 0, ny-1, 0, nz-1)
>>>             vtkImporter.SetScalarArrayName('B field magnitude')
>>>
>>>             writer=vtk.vtkXMLImageDataWriter()
>>>             writer.SetFileName(out_fname)
>>>             writer.SetInputConnection(vtkImporter.GetOutputPort())
>>>             writer.Write()
>>>
>>>             and the ParaView script starts like this:
>>>
>>>             from paraview.simple import *
>>>
>>>             paraview.simple._DisableFirstRenderCameraReset()
>>>
>>>             filepfx = '/nobackup/jcbecker/steinBmag_0'
>>>             infile = filepfx+'.vti'
>>>             # create a new 'XML Image Data Reader'
>>>             steinBmag_ = XMLImageDataReader(FileName=infile)
>>>             steinBmag_.CellArrayStatus = []
>>>             steinBmag_.PointArrayStatus = ['B field magnitude']
>>>
>>>             # get animation scene
>>>             animationScene1 = GetAnimationScene()
>>>
>>>             # update animation scene based on data timesteps
>>>             animationScene1.UpdateAnimationUsingDataTimeSteps()
>>>
>>>             # get active view
>>>             renderView1 = GetActiveViewOrCreate('RenderView')
>>>             # uncomment following to set a specific view size
>>>             renderView1.ViewSize = [1090, 761]
>>>
>>>             I'm looking at the VTK examples and pvpython
>>>             documentation, but any help is appreciated.
>>>
>>>             Thanks.
>>>
>>>             -jeff
>>>             _______________________________________________
>>>             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 <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
>>
>>
>
>

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

From bruce.david.jones at gmail.com  Tue Jul 21 13:37:52 2015
From: bruce.david.jones at gmail.com (Bruce Jones)
Date: Tue, 21 Jul 2015 17:37:52 +0000
Subject: [Paraview] vtkDoubleArray with >3 components
In-Reply-To: <CAB5Fpx5uVT5qbK7UrXnLiPhYyawDGs8v5Lj41ncEHBy2tfe1XA@mail.gmail.com>
References: <CAEc4V-bvd0SRk35cuPM7Z9WhoH8WSL=7S_6kr7_Op5aOeoMN6A@mail.gmail.com>
 <CAB5Fpx6q5_K_ZJNpXtrvNhOYjZQdzGCNxvk8Eo1bvM2tFi0YVQ@mail.gmail.com>
 <CAB5Fpx5uVT5qbK7UrXnLiPhYyawDGs8v5Lj41ncEHBy2tfe1XA@mail.gmail.com>
Message-ID: <CAEc4V-ZO6mB7AJgYG-zRr-kxviiYUyNtcAEsuTuNCU7=uSdfOg@mail.gmail.com>

Hi Cory,

Sorry for the delayed response, I've hit another more serious bug which has
been diverting my attention from this.

Thanks for the state file, I haven't got it to work as I don't have numpy
set up, but I have also got this working with 9 component arrays in
paraview using a python script. However, I am now trying to port my python
plugin to c++ which is where I am seeing the error.

In my plugin I want to output a vtkarray for each vtkarray in the input
dataset. The values in the output vtkarrays are interpolated from those in
the input vtkarrays. Rather than working directly on vtkarray objects, I am
allocating c++ arrays for each vtkarray, performing the interpolation, then
creating vtkDoubleArrays and using SetArray to pass a pointer to my
allocated c++ arrays to the output vtkarrays. The code for setting up the
output vtkarrays is roughly as follows

                vtkPointData *pointData = input->GetPointData();
                vtkDataArray *dArray = pointData->GetArray(i);
vtkDoubleArray *vtkDArrayAve = vtkDoubleArray::New();
vtkDArrayAve->SetName(dArray->GetName());
vtkDArrayAve->SetArray(dArraysAve[i],hgrid->GetTotalCells(),0);
vtkDArrayAve->SetNumberOfComponents(numComponents[i]);
vtkDArrayAve->SetNumberOfTuples(hgrid->GetTotalCells());
output->GetPointData()->AddArray(vtkDArrayAve);

dArraysAve is an array of pointers pointing to my c++ arrays
hgrid->GetTotalCells() returns the number of data points for my output

I also have another mode of operation for this plugin, where I perform the
interpolation differently, in that function, if I make the call to
SetNumberOfComponents() some heap corruption occurs and I get a segfault
when I try to subsequently free my c++ arrays. Commenting out the call to
SetNumberOfComponents avoids the segfault, but then I am limited to single
component arrays. This is the more serious bug I mentioned, initially I
figured they were unrelated, but I can't deny the number of components
coincidence.

Cheers,
Bruce

On Thu, 16 Jul 2015 at 14:41 Cory Quammen <cory.quammen at kitware.com> wrote:

> Hi Bruce,
>
> I have attached a ParaView state file with a Programmable Source that
> produces a vtkPolyData with 100 random points and a point data array with 9
> components. It seems to display the various component ranges just fine.
>
> Best,
> Cory
>
> On Thu, Jul 16, 2015 at 11:14 AM, Cory Quammen <cory.quammen at kitware.com>
> wrote:
>
>> Hi Bruce,
>>
>> I haven't seen this, but ParaView may be interpreting this array as a
>> tensor field. Do you have a smallish test data file that you can share that
>> shows the problem?
>>
>> Thanks,
>> Cory
>>
>> On Sat, Jul 11, 2015 at 11:14 AM, Bruce Jones <
>> bruce.david.jones at gmail.com> wrote:
>>
>>> I am creating vtkDoubleArrays based on averaging some input data to a
>>> reduced set of points. The input data includes various vtk arrays which
>>> have 1, 3 and 9 components.
>>>
>>> After averaging, I am writing the data to c++ arrays, and creating a new
>>> vtkDoubleArray using the SetArray() function to pass the c++ arrays. This
>>> works fine for 1 and 3 component arrays, however for the 9 component arrays
>>> paraview shows that every element is set to 0.
>>>
>>> If I hardcode it so that 9 component arrays become 3 component arrays
>>> (reading only the first 3 components from the input array), then I get the
>>> correct data for the first 3 components, though I obviously need the other
>>> 6 components in the end.
>>>
>>> Has anyone encountered this before?
>>>
>>> Cheers,
>>> Bruce
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>>
>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150721/134d8029/attachment.html>

From rapixxx at abv.bg  Tue Jul 21 22:42:47 2015
From: rapixxx at abv.bg (Petq Stoyanova)
Date: Wed, 22 Jul 2015 05:42:47 +0300 (EEST)
Subject: [Paraview] Newbie in ParaView: Paraview won't run: BadValue and
	GLXBadContext
Message-ID: <705948642.2469781.1437532967881.JavaMail.apache@nm43.abv.bg>

Hello,

I am a total newbie in CFD and ParaView. I was trying to do the OpenFOAM tutorials and running ParaView to view the mesh was one of the first steps, and unfortunately it's where I stumble upon:

X Error: BadValue (integer parameter out of range for operation) 2

 Extension:


 149 (Uknown extension)

 Minor opcode: 3 (Unknown request)

 Resource id:
 0x0
X Error: GLXBadContext 151

 Extension:


 149 (Uknown extension)

 Minor opcode: 5 (Unknown request)

 Resource id:
 0x10002bc

ParaView gives indication of starting then freezes wihout displayng the contents of the opened windows. The version of ParaView I'm using is 3.12.0 for 64-bit systems. I'm using it via the Cygwin Terminal.
To be honest, I have limitted expirience with SSH (I have just started) and everything I read sounds like Chinese to me. If anybody can help and also explain to me what and why I will be extremely grateful. (It may happen that you need to tell me things in a way that a 90-year old grandma who sees computer for the first time would understand :( )

-Petya

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

From shawn.waldon at kitware.com  Wed Jul 22 09:40:37 2015
From: shawn.waldon at kitware.com (Shawn Waldon)
Date: Wed, 22 Jul 2015 09:40:37 -0400
Subject: [Paraview] vtkDoubleArray with >3 components
In-Reply-To: <CAEc4V-ZO6mB7AJgYG-zRr-kxviiYUyNtcAEsuTuNCU7=uSdfOg@mail.gmail.com>
References: <CAEc4V-bvd0SRk35cuPM7Z9WhoH8WSL=7S_6kr7_Op5aOeoMN6A@mail.gmail.com>
 <CAB5Fpx6q5_K_ZJNpXtrvNhOYjZQdzGCNxvk8Eo1bvM2tFi0YVQ@mail.gmail.com>
 <CAB5Fpx5uVT5qbK7UrXnLiPhYyawDGs8v5Lj41ncEHBy2tfe1XA@mail.gmail.com>
 <CAEc4V-ZO6mB7AJgYG-zRr-kxviiYUyNtcAEsuTuNCU7=uSdfOg@mail.gmail.com>
Message-ID: <CALSpCT2tWposY=qgRHzhmE7cw-k=25_2qA6Qu3DYM0sCiYjnkg@mail.gmail.com>

Hi Bruce,

SetNumberOfTuples reallocates the internal datastructure of the data array
to be the new required size based on the new number of components and
number of tuples.  This (combined with trying to clean up the old data from
SetArray) may be causing the heap corruption you are seeing.  Try setting
the number of components and number of tuples before adding the data to the
array.

HTH,
Shawn

On Tue, Jul 21, 2015 at 1:37 PM, Bruce Jones <bruce.david.jones at gmail.com>
wrote:

> Hi Cory,
>
> Sorry for the delayed response, I've hit another more serious bug which
> has been diverting my attention from this.
>
> Thanks for the state file, I haven't got it to work as I don't have numpy
> set up, but I have also got this working with 9 component arrays in
> paraview using a python script. However, I am now trying to port my python
> plugin to c++ which is where I am seeing the error.
>
> In my plugin I want to output a vtkarray for each vtkarray in the input
> dataset. The values in the output vtkarrays are interpolated from those in
> the input vtkarrays. Rather than working directly on vtkarray objects, I am
> allocating c++ arrays for each vtkarray, performing the interpolation, then
> creating vtkDoubleArrays and using SetArray to pass a pointer to my
> allocated c++ arrays to the output vtkarrays. The code for setting up the
> output vtkarrays is roughly as follows
>
>                 vtkPointData *pointData = input->GetPointData();
>                 vtkDataArray *dArray = pointData->GetArray(i);
> vtkDoubleArray *vtkDArrayAve = vtkDoubleArray::New();
> vtkDArrayAve->SetName(dArray->GetName());
> vtkDArrayAve->SetArray(dArraysAve[i],hgrid->GetTotalCells(),0);
> vtkDArrayAve->SetNumberOfComponents(numComponents[i]);
> vtkDArrayAve->SetNumberOfTuples(hgrid->GetTotalCells());
> output->GetPointData()->AddArray(vtkDArrayAve);
>
> dArraysAve is an array of pointers pointing to my c++ arrays
> hgrid->GetTotalCells() returns the number of data points for my output
>
> I also have another mode of operation for this plugin, where I perform the
> interpolation differently, in that function, if I make the call to
> SetNumberOfComponents() some heap corruption occurs and I get a segfault
> when I try to subsequently free my c++ arrays. Commenting out the call to
> SetNumberOfComponents avoids the segfault, but then I am limited to single
> component arrays. This is the more serious bug I mentioned, initially I
> figured they were unrelated, but I can't deny the number of components
> coincidence.
>
> Cheers,
> Bruce
>
> On Thu, 16 Jul 2015 at 14:41 Cory Quammen <cory.quammen at kitware.com>
> wrote:
>
>> Hi Bruce,
>>
>> I have attached a ParaView state file with a Programmable Source that
>> produces a vtkPolyData with 100 random points and a point data array with 9
>> components. It seems to display the various component ranges just fine.
>>
>> Best,
>> Cory
>>
>> On Thu, Jul 16, 2015 at 11:14 AM, Cory Quammen <cory.quammen at kitware.com>
>> wrote:
>>
>>> Hi Bruce,
>>>
>>> I haven't seen this, but ParaView may be interpreting this array as a
>>> tensor field. Do you have a smallish test data file that you can share that
>>> shows the problem?
>>>
>>> Thanks,
>>> Cory
>>>
>>> On Sat, Jul 11, 2015 at 11:14 AM, Bruce Jones <
>>> bruce.david.jones at gmail.com> wrote:
>>>
>>>> I am creating vtkDoubleArrays based on averaging some input data to a
>>>> reduced set of points. The input data includes various vtk arrays which
>>>> have 1, 3 and 9 components.
>>>>
>>>> After averaging, I am writing the data to c++ arrays, and creating a
>>>> new vtkDoubleArray using the SetArray() function to pass the c++ arrays.
>>>> This works fine for 1 and 3 component arrays, however for the 9 component
>>>> arrays paraview shows that every element is set to 0.
>>>>
>>>> If I hardcode it so that 9 component arrays become 3 component arrays
>>>> (reading only the first 3 components from the input array), then I get the
>>>> correct data for the first 3 components, though I obviously need the other
>>>> 6 components in the end.
>>>>
>>>> Has anyone encountered this before?
>>>>
>>>> Cheers,
>>>> Bruce
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>>
>>>
>>> --
>>> Cory Quammen
>>> R&D Engineer
>>> Kitware, Inc.
>>>
>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150722/d0832192/attachment.html>

From berk.geveci at kitware.com  Wed Jul 22 09:44:33 2015
From: berk.geveci at kitware.com (Berk Geveci)
Date: Wed, 22 Jul 2015 09:44:33 -0400
Subject: [Paraview] vtkDoubleArray with >3 components
In-Reply-To: <CALSpCT2tWposY=qgRHzhmE7cw-k=25_2qA6Qu3DYM0sCiYjnkg@mail.gmail.com>
References: <CAEc4V-bvd0SRk35cuPM7Z9WhoH8WSL=7S_6kr7_Op5aOeoMN6A@mail.gmail.com>
 <CAB5Fpx6q5_K_ZJNpXtrvNhOYjZQdzGCNxvk8Eo1bvM2tFi0YVQ@mail.gmail.com>
 <CAB5Fpx5uVT5qbK7UrXnLiPhYyawDGs8v5Lj41ncEHBy2tfe1XA@mail.gmail.com>
 <CAEc4V-ZO6mB7AJgYG-zRr-kxviiYUyNtcAEsuTuNCU7=uSdfOg@mail.gmail.com>
 <CALSpCT2tWposY=qgRHzhmE7cw-k=25_2qA6Qu3DYM0sCiYjnkg@mail.gmail.com>
Message-ID: <CAE32kpXPzntuoXOZRnKt_L4uPUHj9sxUchYdrC-d3OxZOyOh0g@mail.gmail.com>

Actually, don't call SetNumberOfTuples() at all if you are using
SetArray(). It will unnecessarily allocate memory if you call it before
SetArray().

-berk

On Wed, Jul 22, 2015 at 9:40 AM, Shawn Waldon <shawn.waldon at kitware.com>
wrote:

> Hi Bruce,
>
> SetNumberOfTuples reallocates the internal datastructure of the data array
> to be the new required size based on the new number of components and
> number of tuples.  This (combined with trying to clean up the old data from
> SetArray) may be causing the heap corruption you are seeing.  Try setting
> the number of components and number of tuples before adding the data to the
> array.
>
> HTH,
> Shawn
>
> On Tue, Jul 21, 2015 at 1:37 PM, Bruce Jones <bruce.david.jones at gmail.com>
> wrote:
>
>> Hi Cory,
>>
>> Sorry for the delayed response, I've hit another more serious bug which
>> has been diverting my attention from this.
>>
>> Thanks for the state file, I haven't got it to work as I don't have numpy
>> set up, but I have also got this working with 9 component arrays in
>> paraview using a python script. However, I am now trying to port my python
>> plugin to c++ which is where I am seeing the error.
>>
>> In my plugin I want to output a vtkarray for each vtkarray in the input
>> dataset. The values in the output vtkarrays are interpolated from those in
>> the input vtkarrays. Rather than working directly on vtkarray objects, I am
>> allocating c++ arrays for each vtkarray, performing the interpolation, then
>> creating vtkDoubleArrays and using SetArray to pass a pointer to my
>> allocated c++ arrays to the output vtkarrays. The code for setting up the
>> output vtkarrays is roughly as follows
>>
>>                 vtkPointData *pointData = input->GetPointData();
>>                 vtkDataArray *dArray = pointData->GetArray(i);
>> vtkDoubleArray *vtkDArrayAve = vtkDoubleArray::New();
>> vtkDArrayAve->SetName(dArray->GetName());
>> vtkDArrayAve->SetArray(dArraysAve[i],hgrid->GetTotalCells(),0);
>> vtkDArrayAve->SetNumberOfComponents(numComponents[i]);
>> vtkDArrayAve->SetNumberOfTuples(hgrid->GetTotalCells());
>> output->GetPointData()->AddArray(vtkDArrayAve);
>>
>> dArraysAve is an array of pointers pointing to my c++ arrays
>> hgrid->GetTotalCells() returns the number of data points for my output
>>
>> I also have another mode of operation for this plugin, where I perform
>> the interpolation differently, in that function, if I make the call to
>> SetNumberOfComponents() some heap corruption occurs and I get a segfault
>> when I try to subsequently free my c++ arrays. Commenting out the call to
>> SetNumberOfComponents avoids the segfault, but then I am limited to single
>> component arrays. This is the more serious bug I mentioned, initially I
>> figured they were unrelated, but I can't deny the number of components
>> coincidence.
>>
>> Cheers,
>> Bruce
>>
>> On Thu, 16 Jul 2015 at 14:41 Cory Quammen <cory.quammen at kitware.com>
>> wrote:
>>
>>> Hi Bruce,
>>>
>>> I have attached a ParaView state file with a Programmable Source that
>>> produces a vtkPolyData with 100 random points and a point data array with 9
>>> components. It seems to display the various component ranges just fine.
>>>
>>> Best,
>>> Cory
>>>
>>> On Thu, Jul 16, 2015 at 11:14 AM, Cory Quammen <cory.quammen at kitware.com
>>> > wrote:
>>>
>>>> Hi Bruce,
>>>>
>>>> I haven't seen this, but ParaView may be interpreting this array as a
>>>> tensor field. Do you have a smallish test data file that you can share that
>>>> shows the problem?
>>>>
>>>> Thanks,
>>>> Cory
>>>>
>>>> On Sat, Jul 11, 2015 at 11:14 AM, Bruce Jones <
>>>> bruce.david.jones at gmail.com> wrote:
>>>>
>>>>> I am creating vtkDoubleArrays based on averaging some input data to a
>>>>> reduced set of points. The input data includes various vtk arrays which
>>>>> have 1, 3 and 9 components.
>>>>>
>>>>> After averaging, I am writing the data to c++ arrays, and creating a
>>>>> new vtkDoubleArray using the SetArray() function to pass the c++ arrays.
>>>>> This works fine for 1 and 3 component arrays, however for the 9 component
>>>>> arrays paraview shows that every element is set to 0.
>>>>>
>>>>> If I hardcode it so that 9 component arrays become 3 component arrays
>>>>> (reading only the first 3 components from the input array), then I get the
>>>>> correct data for the first 3 components, though I obviously need the other
>>>>> 6 components in the end.
>>>>>
>>>>> Has anyone encountered this before?
>>>>>
>>>>> Cheers,
>>>>> Bruce
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Cory Quammen
>>>> R&D Engineer
>>>> Kitware, Inc.
>>>>
>>>
>>>
>>>
>>> --
>>> Cory Quammen
>>> R&D Engineer
>>> Kitware, Inc.
>>>
>>
>> _______________________________________________
>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150722/b12385b7/attachment.html>

From bruce.david.jones at gmail.com  Wed Jul 22 09:56:21 2015
From: bruce.david.jones at gmail.com (Bruce Jones)
Date: Wed, 22 Jul 2015 13:56:21 +0000
Subject: [Paraview] vtkDoubleArray with >3 components
In-Reply-To: <CAE32kpXPzntuoXOZRnKt_L4uPUHj9sxUchYdrC-d3OxZOyOh0g@mail.gmail.com>
References: <CAEc4V-bvd0SRk35cuPM7Z9WhoH8WSL=7S_6kr7_Op5aOeoMN6A@mail.gmail.com>
 <CAB5Fpx6q5_K_ZJNpXtrvNhOYjZQdzGCNxvk8Eo1bvM2tFi0YVQ@mail.gmail.com>
 <CAB5Fpx5uVT5qbK7UrXnLiPhYyawDGs8v5Lj41ncEHBy2tfe1XA@mail.gmail.com>
 <CAEc4V-ZO6mB7AJgYG-zRr-kxviiYUyNtcAEsuTuNCU7=uSdfOg@mail.gmail.com>
 <CALSpCT2tWposY=qgRHzhmE7cw-k=25_2qA6Qu3DYM0sCiYjnkg@mail.gmail.com>
 <CAE32kpXPzntuoXOZRnKt_L4uPUHj9sxUchYdrC-d3OxZOyOh0g@mail.gmail.com>
Message-ID: <CAEc4V-bN3jDh89hpUJtu8p5VEh8R7wEhCvF=DxPYdSPOoB4DWA@mail.gmail.com>

Hi Guys,

I have just tried it as you suggested, doing SetNumberOfComponents then
SetArray, without doing SetNumberOfTuples. Unfortunately I am still getting
the same behaviour.

Cheers,
Bruce

On Wed, 22 Jul 2015 at 09:44 Berk Geveci <berk.geveci at kitware.com> wrote:

> Actually, don't call SetNumberOfTuples() at all if you are using
> SetArray(). It will unnecessarily allocate memory if you call it before
> SetArray().
>
> -berk
>
> On Wed, Jul 22, 2015 at 9:40 AM, Shawn Waldon <shawn.waldon at kitware.com>
> wrote:
>
>> Hi Bruce,
>>
>> SetNumberOfTuples reallocates the internal datastructure of the data
>> array to be the new required size based on the new number of components and
>> number of tuples.  This (combined with trying to clean up the old data from
>> SetArray) may be causing the heap corruption you are seeing.  Try setting
>> the number of components and number of tuples before adding the data to the
>> array.
>>
>> HTH,
>> Shawn
>>
>> On Tue, Jul 21, 2015 at 1:37 PM, Bruce Jones <bruce.david.jones at gmail.com
>> > wrote:
>>
>>> Hi Cory,
>>>
>>> Sorry for the delayed response, I've hit another more serious bug which
>>> has been diverting my attention from this.
>>>
>>> Thanks for the state file, I haven't got it to work as I don't have
>>> numpy set up, but I have also got this working with 9 component arrays in
>>> paraview using a python script. However, I am now trying to port my python
>>> plugin to c++ which is where I am seeing the error.
>>>
>>> In my plugin I want to output a vtkarray for each vtkarray in the input
>>> dataset. The values in the output vtkarrays are interpolated from those in
>>> the input vtkarrays. Rather than working directly on vtkarray objects, I am
>>> allocating c++ arrays for each vtkarray, performing the interpolation, then
>>> creating vtkDoubleArrays and using SetArray to pass a pointer to my
>>> allocated c++ arrays to the output vtkarrays. The code for setting up the
>>> output vtkarrays is roughly as follows
>>>
>>>                 vtkPointData *pointData = input->GetPointData();
>>>                 vtkDataArray *dArray = pointData->GetArray(i);
>>> vtkDoubleArray *vtkDArrayAve = vtkDoubleArray::New();
>>> vtkDArrayAve->SetName(dArray->GetName());
>>> vtkDArrayAve->SetArray(dArraysAve[i],hgrid->GetTotalCells(),0);
>>> vtkDArrayAve->SetNumberOfComponents(numComponents[i]);
>>> vtkDArrayAve->SetNumberOfTuples(hgrid->GetTotalCells());
>>> output->GetPointData()->AddArray(vtkDArrayAve);
>>>
>>> dArraysAve is an array of pointers pointing to my c++ arrays
>>> hgrid->GetTotalCells() returns the number of data points for my output
>>>
>>> I also have another mode of operation for this plugin, where I perform
>>> the interpolation differently, in that function, if I make the call to
>>> SetNumberOfComponents() some heap corruption occurs and I get a segfault
>>> when I try to subsequently free my c++ arrays. Commenting out the call to
>>> SetNumberOfComponents avoids the segfault, but then I am limited to single
>>> component arrays. This is the more serious bug I mentioned, initially I
>>> figured they were unrelated, but I can't deny the number of components
>>> coincidence.
>>>
>>> Cheers,
>>> Bruce
>>>
>>> On Thu, 16 Jul 2015 at 14:41 Cory Quammen <cory.quammen at kitware.com>
>>> wrote:
>>>
>>>> Hi Bruce,
>>>>
>>>> I have attached a ParaView state file with a Programmable Source that
>>>> produces a vtkPolyData with 100 random points and a point data array with 9
>>>> components. It seems to display the various component ranges just fine.
>>>>
>>>> Best,
>>>> Cory
>>>>
>>>> On Thu, Jul 16, 2015 at 11:14 AM, Cory Quammen <
>>>> cory.quammen at kitware.com> wrote:
>>>>
>>>>> Hi Bruce,
>>>>>
>>>>> I haven't seen this, but ParaView may be interpreting this array as a
>>>>> tensor field. Do you have a smallish test data file that you can share that
>>>>> shows the problem?
>>>>>
>>>>> Thanks,
>>>>> Cory
>>>>>
>>>>> On Sat, Jul 11, 2015 at 11:14 AM, Bruce Jones <
>>>>> bruce.david.jones at gmail.com> wrote:
>>>>>
>>>>>> I am creating vtkDoubleArrays based on averaging some input data to a
>>>>>> reduced set of points. The input data includes various vtk arrays which
>>>>>> have 1, 3 and 9 components.
>>>>>>
>>>>>> After averaging, I am writing the data to c++ arrays, and creating a
>>>>>> new vtkDoubleArray using the SetArray() function to pass the c++ arrays.
>>>>>> This works fine for 1 and 3 component arrays, however for the 9 component
>>>>>> arrays paraview shows that every element is set to 0.
>>>>>>
>>>>>> If I hardcode it so that 9 component arrays become 3 component arrays
>>>>>> (reading only the first 3 components from the input array), then I get the
>>>>>> correct data for the first 3 components, though I obviously need the other
>>>>>> 6 components in the end.
>>>>>>
>>>>>> Has anyone encountered this before?
>>>>>>
>>>>>> Cheers,
>>>>>> Bruce
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Cory Quammen
>>>>> R&D Engineer
>>>>> Kitware, Inc.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Cory Quammen
>>>> R&D Engineer
>>>> Kitware, Inc.
>>>>
>>>
>>> _______________________________________________
>>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150722/b2eb9d04/attachment.html>

From M.Deij at marin.nl  Wed Jul 22 10:45:42 2015
From: M.Deij at marin.nl (Deij-van Rijswijk, Menno)
Date: Wed, 22 Jul 2015 14:45:42 +0000
Subject: [Paraview] [Catalyst] Ghost cells
Message-ID: <9b365a0ae2be4a7e8225e5e218c49da1@MAR190n2.marin.local>

Hi,

I?m slowly getting to grips with PVCatalyst, trying to create an adaptor for our simulation code. Our code is distributed using MPI and has normal and ghost cells for each process. Should I take these ghost cells into account in the adaptor, and if so, how can this be done? There does not seem to be an example for this in the example code repository, but maybe there is an example somewhere else that I can use to understand this?

Thanks and best wishes,


Menno

[cid:image15b291.JPG at 26cf3fbc.42b54f48][cid:imagedfbd55.JPG at b2037a5b.4da2c487]

dr. ir. Menno A. Deij-van Rijswijk


Researcher / Software Engineer


Maritime Simulation & Software Group




MARIN




        2, Haagsteeg

E M.Deij at marin.nl<mailto:M.Deij at marin.nl>       P.O. Box 28     T +31 317 49 39 11
        6700 AA Wageningen      F +31 317 49 32 45
T  +31 317 49 35 06     The Netherlands I  www.marin.nl<http://www.marin.nl>





MARIN news: On the calculation of the flow around 2-D square cylinder with rounded corners<http://www.marin.nl/web/News/News-items/On-the-calculation-of-the-flow-around-2D-square-cylinder-with-rounded-corners-1.htm>

This e-mail may be confidential, privileged and/or protected by copyright. If you are not the intended recipient, you should return it to the sender immediately and delete your copy from your system.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150722/a9f4e497/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image15b291.JPG
Type: image/jpeg
Size: 1069 bytes
Desc: image15b291.JPG
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150722/a9f4e497/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagedfbd55.JPG
Type: image/jpeg
Size: 1622 bytes
Desc: imagedfbd55.JPG
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150722/a9f4e497/attachment-0001.jpe>

From silvere.pierre.paraview at gmail.com  Wed Jul 22 11:04:20 2015
From: silvere.pierre.paraview at gmail.com (Silvere Pierre)
Date: Wed, 22 Jul 2015 17:04:20 +0200
Subject: [Paraview] Bug with the trace tool : Exporting view instruction not
	repeatable
Message-ID: <CAGox_owQwgeuDchfmGgA+SY10on4fXFTmqmX4SHMHvNDBXg_XQ@mail.gmail.com>

Hello everyone,

I am used to create vector images (PDF) using the export view tool in the
Paraview 4.3 GUI.
As I wanted to use it in scripts I used Start Trace to get the python
instructions which is :

ExportView('your_path.pdf', view=your_render_view, Rasterize3DGeometry=0)

Problem is, the Rasterize3DGeometry option is unknown when you try and use
it in the console (and without it you get a pixeled image).

I looked up old messages and found this piece of code :

rw = your_render_view.GetRenderWindow()
exp = paraview.vtk.vtkInstantiator.CreateInstance('vtkGL2PSExporter')
exp.SetRenderWindow(rw)
exp.SetDrawBackground(0)
exp.SetSortToSimple()
exp.SetFileFormatToPDF()
exp.SetFilePrefix("your_path.pdf")
exp.Write3DPropsAsRasterImageOff()
exp.Write()

that should take care of it in a less direct way. Unfortunately, the
instanciation fail and the object (named exp here) is undefined.

Is it only an interface problem with python ? Is there any way to get the
correct instance of the renderer ?

Best regards,

Silv?re Pierre
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150722/fa11eb26/attachment.html>

From andy.bauer at kitware.com  Wed Jul 22 11:09:45 2015
From: andy.bauer at kitware.com (Andy Bauer)
Date: Wed, 22 Jul 2015 11:09:45 -0400
Subject: [Paraview] [Catalyst] Ghost cells
In-Reply-To: <9b365a0ae2be4a7e8225e5e218c49da1@MAR190n2.marin.local>
References: <9b365a0ae2be4a7e8225e5e218c49da1@MAR190n2.marin.local>
Message-ID: <CAMaOp+E_fHh-nx1pYtu9jPOY-dfSftiXnCzHaFeWADmwkxBUDw@mail.gmail.com>

Hi Menno,

Did you look at the http://www.kitware.com/blog/home/post/856 blog about
ghost cells? That has a good explanation of where ParaView is going for
improving ghost cell support in general. I haven't gotten around to making
a Catalyst example yet that uses ghost cells but hopefully someone can find
some time to do that soon with the changes to ghost cell support in
ParaView.

If you try a simple example and notice some unexpected behavior, please let
us know. Also, if you get something working and want to share it in the
Catalyst examples repo (
https://github.com/Kitware/ParaViewCatalystExampleCode) I would appreciate
it.

Best,
Andy


On Wed, Jul 22, 2015 at 10:45 AM, Deij-van Rijswijk, Menno <M.Deij at marin.nl>
wrote:

>   Hi,
>
>
>
> I?m slowly getting to grips with PVCatalyst, trying to create an adaptor
> for our simulation code. Our code is distributed using MPI and has normal
> and ghost cells for each process. Should I take these ghost cells into
> account in the adaptor, and if so, how can this be done? There does not
> seem to be an example for this in the example code repository, but maybe
> there is an example somewhere else that I can use to understand this?
>
>
>
> Thanks and best wishes,
>
>
>
>
>
> Menno
>
>     dr. ir. Menno A. Deij-van Rijswijk
>
> Researcher / Software Engineer
>   Maritime Simulation & Software Group
>
>
>
> *MARIN*
>
>
>   2, Haagsteeg  E M.Deij at marin.nl P.O. Box 28 T +31 317 49 39 11  6700 AA
> Wageningen F +31 317 49 32 45  T  +31 317 49 35 06 The Netherlands I
> www.marin.nl
>
>
>
> MARIN news: On the calculation of the flow around 2-D square cylinder
> with rounded corners
> <http://www.marin.nl/web/News/News-items/On-the-calculation-of-the-flow-around-2D-square-cylinder-with-rounded-corners-1.htm>
>
> This e-mail may be confidential, privileged and/or protected by copyright.
> If you are not the intended recipient, you should return it to the sender
> immediately and delete your copy from 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
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150722/7d82303b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image15b291.JPG
Type: image/jpeg
Size: 1069 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150722/7d82303b/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagedfbd55.JPG
Type: image/jpeg
Size: 1622 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150722/7d82303b/attachment-0001.jpe>

From berk.geveci at kitware.com  Wed Jul 22 11:09:33 2015
From: berk.geveci at kitware.com (Berk Geveci)
Date: Wed, 22 Jul 2015 11:09:33 -0400
Subject: [Paraview] vtkDoubleArray with >3 components
In-Reply-To: <CAEc4V-bN3jDh89hpUJtu8p5VEh8R7wEhCvF=DxPYdSPOoB4DWA@mail.gmail.com>
References: <CAEc4V-bvd0SRk35cuPM7Z9WhoH8WSL=7S_6kr7_Op5aOeoMN6A@mail.gmail.com>
 <CAB5Fpx6q5_K_ZJNpXtrvNhOYjZQdzGCNxvk8Eo1bvM2tFi0YVQ@mail.gmail.com>
 <CAB5Fpx5uVT5qbK7UrXnLiPhYyawDGs8v5Lj41ncEHBy2tfe1XA@mail.gmail.com>
 <CAEc4V-ZO6mB7AJgYG-zRr-kxviiYUyNtcAEsuTuNCU7=uSdfOg@mail.gmail.com>
 <CALSpCT2tWposY=qgRHzhmE7cw-k=25_2qA6Qu3DYM0sCiYjnkg@mail.gmail.com>
 <CAE32kpXPzntuoXOZRnKt_L4uPUHj9sxUchYdrC-d3OxZOyOh0g@mail.gmail.com>
 <CAEc4V-bN3jDh89hpUJtu8p5VEh8R7wEhCvF=DxPYdSPOoB4DWA@mail.gmail.com>
Message-ID: <CAE32kpV=rwYxTeMjh=cme29563uavrkbaQep2QFT+1-nNskOFg@mail.gmail.com>

The solution is in the documentation:

  // This method lets the user specify data to be held by the array.  The
  // array argument is a pointer to the data.  size is the size of the
  // array supplied by the user.  Set save to 1 to keep the class from
  // deleting the array when it cleans up or reallocates memory.  The class
  // uses the actual array provided; it does not copy the data from the
  // suppled array. If specified, the delete method determines how the data
  // array will be deallocated. If the delete method is
  // VTK_DATA_ARRAY_FREE, free() will be used. If the delete method is
  // DELETE, delete[] will be used. The default is FREE.

You are passing 0 for the "save" argument, which means that VTK will delete
the array when the VTK array object is deleted, which would cause a double
delete/free. Use 1 as the second argument of SetArray() if you are managing
the memory. Also, make sure that the VTK array is not used after you free
your array.

Best,
-berk

On Wed, Jul 22, 2015 at 9:56 AM, Bruce Jones <bruce.david.jones at gmail.com>
wrote:

> Hi Guys,
>
> I have just tried it as you suggested, doing SetNumberOfComponents then
> SetArray, without doing SetNumberOfTuples. Unfortunately I am still getting
> the same behaviour.
>
> Cheers,
> Bruce
>
> On Wed, 22 Jul 2015 at 09:44 Berk Geveci <berk.geveci at kitware.com> wrote:
>
>> Actually, don't call SetNumberOfTuples() at all if you are using
>> SetArray(). It will unnecessarily allocate memory if you call it before
>> SetArray().
>>
>> -berk
>>
>> On Wed, Jul 22, 2015 at 9:40 AM, Shawn Waldon <shawn.waldon at kitware.com>
>> wrote:
>>
>>> Hi Bruce,
>>>
>>> SetNumberOfTuples reallocates the internal datastructure of the data
>>> array to be the new required size based on the new number of components and
>>> number of tuples.  This (combined with trying to clean up the old data from
>>> SetArray) may be causing the heap corruption you are seeing.  Try setting
>>> the number of components and number of tuples before adding the data to the
>>> array.
>>>
>>> HTH,
>>> Shawn
>>>
>>> On Tue, Jul 21, 2015 at 1:37 PM, Bruce Jones <
>>> bruce.david.jones at gmail.com> wrote:
>>>
>>>> Hi Cory,
>>>>
>>>> Sorry for the delayed response, I've hit another more serious bug which
>>>> has been diverting my attention from this.
>>>>
>>>> Thanks for the state file, I haven't got it to work as I don't have
>>>> numpy set up, but I have also got this working with 9 component arrays in
>>>> paraview using a python script. However, I am now trying to port my python
>>>> plugin to c++ which is where I am seeing the error.
>>>>
>>>> In my plugin I want to output a vtkarray for each vtkarray in the input
>>>> dataset. The values in the output vtkarrays are interpolated from those in
>>>> the input vtkarrays. Rather than working directly on vtkarray objects, I am
>>>> allocating c++ arrays for each vtkarray, performing the interpolation, then
>>>> creating vtkDoubleArrays and using SetArray to pass a pointer to my
>>>> allocated c++ arrays to the output vtkarrays. The code for setting up the
>>>> output vtkarrays is roughly as follows
>>>>
>>>>                 vtkPointData *pointData = input->GetPointData();
>>>>                 vtkDataArray *dArray = pointData->GetArray(i);
>>>> vtkDoubleArray *vtkDArrayAve = vtkDoubleArray::New();
>>>> vtkDArrayAve->SetName(dArray->GetName());
>>>> vtkDArrayAve->SetArray(dArraysAve[i],hgrid->GetTotalCells(),0);
>>>> vtkDArrayAve->SetNumberOfComponents(numComponents[i]);
>>>> vtkDArrayAve->SetNumberOfTuples(hgrid->GetTotalCells());
>>>> output->GetPointData()->AddArray(vtkDArrayAve);
>>>>
>>>> dArraysAve is an array of pointers pointing to my c++ arrays
>>>> hgrid->GetTotalCells() returns the number of data points for my output
>>>>
>>>> I also have another mode of operation for this plugin, where I perform
>>>> the interpolation differently, in that function, if I make the call to
>>>> SetNumberOfComponents() some heap corruption occurs and I get a segfault
>>>> when I try to subsequently free my c++ arrays. Commenting out the call to
>>>> SetNumberOfComponents avoids the segfault, but then I am limited to single
>>>> component arrays. This is the more serious bug I mentioned, initially I
>>>> figured they were unrelated, but I can't deny the number of components
>>>> coincidence.
>>>>
>>>> Cheers,
>>>> Bruce
>>>>
>>>> On Thu, 16 Jul 2015 at 14:41 Cory Quammen <cory.quammen at kitware.com>
>>>> wrote:
>>>>
>>>>> Hi Bruce,
>>>>>
>>>>> I have attached a ParaView state file with a Programmable Source that
>>>>> produces a vtkPolyData with 100 random points and a point data array with 9
>>>>> components. It seems to display the various component ranges just fine.
>>>>>
>>>>> Best,
>>>>> Cory
>>>>>
>>>>> On Thu, Jul 16, 2015 at 11:14 AM, Cory Quammen <
>>>>> cory.quammen at kitware.com> wrote:
>>>>>
>>>>>> Hi Bruce,
>>>>>>
>>>>>> I haven't seen this, but ParaView may be interpreting this array as a
>>>>>> tensor field. Do you have a smallish test data file that you can share that
>>>>>> shows the problem?
>>>>>>
>>>>>> Thanks,
>>>>>> Cory
>>>>>>
>>>>>> On Sat, Jul 11, 2015 at 11:14 AM, Bruce Jones <
>>>>>> bruce.david.jones at gmail.com> wrote:
>>>>>>
>>>>>>> I am creating vtkDoubleArrays based on averaging some input data to
>>>>>>> a reduced set of points. The input data includes various vtk arrays which
>>>>>>> have 1, 3 and 9 components.
>>>>>>>
>>>>>>> After averaging, I am writing the data to c++ arrays, and creating a
>>>>>>> new vtkDoubleArray using the SetArray() function to pass the c++ arrays.
>>>>>>> This works fine for 1 and 3 component arrays, however for the 9 component
>>>>>>> arrays paraview shows that every element is set to 0.
>>>>>>>
>>>>>>> If I hardcode it so that 9 component arrays become 3 component
>>>>>>> arrays (reading only the first 3 components from the input array), then I
>>>>>>> get the correct data for the first 3 components, though I obviously need
>>>>>>> the other 6 components in the end.
>>>>>>>
>>>>>>> Has anyone encountered this before?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Bruce
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Cory Quammen
>>>>>> R&D Engineer
>>>>>> Kitware, Inc.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Cory Quammen
>>>>> R&D Engineer
>>>>> Kitware, Inc.
>>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150722/73aa60e1/attachment.html>

From bruce.david.jones at gmail.com  Wed Jul 22 11:21:27 2015
From: bruce.david.jones at gmail.com (Bruce Jones)
Date: Wed, 22 Jul 2015 15:21:27 +0000
Subject: [Paraview] vtkDoubleArray with >3 components
In-Reply-To: <CAE32kpV=rwYxTeMjh=cme29563uavrkbaQep2QFT+1-nNskOFg@mail.gmail.com>
References: <CAEc4V-bvd0SRk35cuPM7Z9WhoH8WSL=7S_6kr7_Op5aOeoMN6A@mail.gmail.com>
 <CAB5Fpx6q5_K_ZJNpXtrvNhOYjZQdzGCNxvk8Eo1bvM2tFi0YVQ@mail.gmail.com>
 <CAB5Fpx5uVT5qbK7UrXnLiPhYyawDGs8v5Lj41ncEHBy2tfe1XA@mail.gmail.com>
 <CAEc4V-ZO6mB7AJgYG-zRr-kxviiYUyNtcAEsuTuNCU7=uSdfOg@mail.gmail.com>
 <CALSpCT2tWposY=qgRHzhmE7cw-k=25_2qA6Qu3DYM0sCiYjnkg@mail.gmail.com>
 <CAE32kpXPzntuoXOZRnKt_L4uPUHj9sxUchYdrC-d3OxZOyOh0g@mail.gmail.com>
 <CAEc4V-bN3jDh89hpUJtu8p5VEh8R7wEhCvF=DxPYdSPOoB4DWA@mail.gmail.com>
 <CAE32kpV=rwYxTeMjh=cme29563uavrkbaQep2QFT+1-nNskOFg@mail.gmail.com>
Message-ID: <CAEc4V-bxLtZAcjaMzgHp2ZOQFecmxfC63g2aUaNCDgSi4otOZQ@mail.gmail.com>

Thanks Berk,

I have tried with both zero and 1 as the save argument and am getting the
same behavior. As before, if I comment the SetNumberOfComponents call (or
set number of components to 1) everything works, except I only have single
component arrays in the output.

I'm going to put together a minimum working example with the issue this
afternoon so that I can show you guys in more detail.

Cheers,
Bruce

On Wed, 22 Jul 2015 at 11:09 Berk Geveci <berk.geveci at kitware.com> wrote:

> The solution is in the documentation:
>
>   // This method lets the user specify data to be held by the array.  The
>   // array argument is a pointer to the data.  size is the size of the
>   // array supplied by the user.  Set save to 1 to keep the class from
>   // deleting the array when it cleans up or reallocates memory.  The class
>   // uses the actual array provided; it does not copy the data from the
>   // suppled array. If specified, the delete method determines how the data
>   // array will be deallocated. If the delete method is
>   // VTK_DATA_ARRAY_FREE, free() will be used. If the delete method is
>   // DELETE, delete[] will be used. The default is FREE.
>
> You are passing 0 for the "save" argument, which means that VTK will
> delete the array when the VTK array object is deleted, which would cause a
> double delete/free. Use 1 as the second argument of SetArray() if you are
> managing the memory. Also, make sure that the VTK array is not used after
> you free your array.
>
> Best,
> -berk
>
> On Wed, Jul 22, 2015 at 9:56 AM, Bruce Jones <bruce.david.jones at gmail.com>
> wrote:
>
>> Hi Guys,
>>
>> I have just tried it as you suggested, doing SetNumberOfComponents then
>> SetArray, without doing SetNumberOfTuples. Unfortunately I am still getting
>> the same behaviour.
>>
>> Cheers,
>> Bruce
>>
>> On Wed, 22 Jul 2015 at 09:44 Berk Geveci <berk.geveci at kitware.com> wrote:
>>
>>> Actually, don't call SetNumberOfTuples() at all if you are using
>>> SetArray(). It will unnecessarily allocate memory if you call it before
>>> SetArray().
>>>
>>> -berk
>>>
>>> On Wed, Jul 22, 2015 at 9:40 AM, Shawn Waldon <shawn.waldon at kitware.com>
>>> wrote:
>>>
>>>> Hi Bruce,
>>>>
>>>> SetNumberOfTuples reallocates the internal datastructure of the data
>>>> array to be the new required size based on the new number of components and
>>>> number of tuples.  This (combined with trying to clean up the old data from
>>>> SetArray) may be causing the heap corruption you are seeing.  Try setting
>>>> the number of components and number of tuples before adding the data to the
>>>> array.
>>>>
>>>> HTH,
>>>> Shawn
>>>>
>>>> On Tue, Jul 21, 2015 at 1:37 PM, Bruce Jones <
>>>> bruce.david.jones at gmail.com> wrote:
>>>>
>>>>> Hi Cory,
>>>>>
>>>>> Sorry for the delayed response, I've hit another more serious bug
>>>>> which has been diverting my attention from this.
>>>>>
>>>>> Thanks for the state file, I haven't got it to work as I don't have
>>>>> numpy set up, but I have also got this working with 9 component arrays in
>>>>> paraview using a python script. However, I am now trying to port my python
>>>>> plugin to c++ which is where I am seeing the error.
>>>>>
>>>>> In my plugin I want to output a vtkarray for each vtkarray in the
>>>>> input dataset. The values in the output vtkarrays are interpolated from
>>>>> those in the input vtkarrays. Rather than working directly on vtkarray
>>>>> objects, I am allocating c++ arrays for each vtkarray, performing the
>>>>> interpolation, then creating vtkDoubleArrays and using SetArray to pass a
>>>>> pointer to my allocated c++ arrays to the output vtkarrays. The code for
>>>>> setting up the output vtkarrays is roughly as follows
>>>>>
>>>>>                 vtkPointData *pointData = input->GetPointData();
>>>>>                 vtkDataArray *dArray = pointData->GetArray(i);
>>>>> vtkDoubleArray *vtkDArrayAve = vtkDoubleArray::New();
>>>>> vtkDArrayAve->SetName(dArray->GetName());
>>>>> vtkDArrayAve->SetArray(dArraysAve[i],hgrid->GetTotalCells(),0);
>>>>> vtkDArrayAve->SetNumberOfComponents(numComponents[i]);
>>>>> vtkDArrayAve->SetNumberOfTuples(hgrid->GetTotalCells());
>>>>> output->GetPointData()->AddArray(vtkDArrayAve);
>>>>>
>>>>> dArraysAve is an array of pointers pointing to my c++ arrays
>>>>> hgrid->GetTotalCells() returns the number of data points for my output
>>>>>
>>>>> I also have another mode of operation for this plugin, where I perform
>>>>> the interpolation differently, in that function, if I make the call to
>>>>> SetNumberOfComponents() some heap corruption occurs and I get a segfault
>>>>> when I try to subsequently free my c++ arrays. Commenting out the call to
>>>>> SetNumberOfComponents avoids the segfault, but then I am limited to single
>>>>> component arrays. This is the more serious bug I mentioned, initially I
>>>>> figured they were unrelated, but I can't deny the number of components
>>>>> coincidence.
>>>>>
>>>>> Cheers,
>>>>> Bruce
>>>>>
>>>>> On Thu, 16 Jul 2015 at 14:41 Cory Quammen <cory.quammen at kitware.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Bruce,
>>>>>>
>>>>>> I have attached a ParaView state file with a Programmable Source that
>>>>>> produces a vtkPolyData with 100 random points and a point data array with 9
>>>>>> components. It seems to display the various component ranges just fine.
>>>>>>
>>>>>> Best,
>>>>>> Cory
>>>>>>
>>>>>> On Thu, Jul 16, 2015 at 11:14 AM, Cory Quammen <
>>>>>> cory.quammen at kitware.com> wrote:
>>>>>>
>>>>>>> Hi Bruce,
>>>>>>>
>>>>>>> I haven't seen this, but ParaView may be interpreting this array as
>>>>>>> a tensor field. Do you have a smallish test data file that you can share
>>>>>>> that shows the problem?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Cory
>>>>>>>
>>>>>>> On Sat, Jul 11, 2015 at 11:14 AM, Bruce Jones <
>>>>>>> bruce.david.jones at gmail.com> wrote:
>>>>>>>
>>>>>>>> I am creating vtkDoubleArrays based on averaging some input data to
>>>>>>>> a reduced set of points. The input data includes various vtk arrays which
>>>>>>>> have 1, 3 and 9 components.
>>>>>>>>
>>>>>>>> After averaging, I am writing the data to c++ arrays, and creating
>>>>>>>> a new vtkDoubleArray using the SetArray() function to pass the c++ arrays.
>>>>>>>> This works fine for 1 and 3 component arrays, however for the 9 component
>>>>>>>> arrays paraview shows that every element is set to 0.
>>>>>>>>
>>>>>>>> If I hardcode it so that 9 component arrays become 3 component
>>>>>>>> arrays (reading only the first 3 components from the input array), then I
>>>>>>>> get the correct data for the first 3 components, though I obviously need
>>>>>>>> the other 6 components in the end.
>>>>>>>>
>>>>>>>> Has anyone encountered this before?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Bruce
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Cory Quammen
>>>>>>> R&D Engineer
>>>>>>> Kitware, Inc.
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Cory Quammen
>>>>>> R&D Engineer
>>>>>> Kitware, Inc.
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>
>>>>
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150722/8153320e/attachment.html>

From bruce.david.jones at gmail.com  Wed Jul 22 14:28:43 2015
From: bruce.david.jones at gmail.com (Bruce Jones)
Date: Wed, 22 Jul 2015 18:28:43 +0000
Subject: [Paraview] vtkDoubleArray with >3 components
In-Reply-To: <CAEc4V-bxLtZAcjaMzgHp2ZOQFecmxfC63g2aUaNCDgSi4otOZQ@mail.gmail.com>
References: <CAEc4V-bvd0SRk35cuPM7Z9WhoH8WSL=7S_6kr7_Op5aOeoMN6A@mail.gmail.com>
 <CAB5Fpx6q5_K_ZJNpXtrvNhOYjZQdzGCNxvk8Eo1bvM2tFi0YVQ@mail.gmail.com>
 <CAB5Fpx5uVT5qbK7UrXnLiPhYyawDGs8v5Lj41ncEHBy2tfe1XA@mail.gmail.com>
 <CAEc4V-ZO6mB7AJgYG-zRr-kxviiYUyNtcAEsuTuNCU7=uSdfOg@mail.gmail.com>
 <CALSpCT2tWposY=qgRHzhmE7cw-k=25_2qA6Qu3DYM0sCiYjnkg@mail.gmail.com>
 <CAE32kpXPzntuoXOZRnKt_L4uPUHj9sxUchYdrC-d3OxZOyOh0g@mail.gmail.com>
 <CAEc4V-bN3jDh89hpUJtu8p5VEh8R7wEhCvF=DxPYdSPOoB4DWA@mail.gmail.com>
 <CAE32kpV=rwYxTeMjh=cme29563uavrkbaQep2QFT+1-nNskOFg@mail.gmail.com>
 <CAEc4V-bxLtZAcjaMzgHp2ZOQFecmxfC63g2aUaNCDgSi4otOZQ@mail.gmail.com>
Message-ID: <CAEc4V-Z5A6isVG5oy7AtvxqmjzKr+zN7e+aWC3_Srn3Lf=U7qA@mail.gmail.com>

Hey Guys,

I have created a minimum working example (attached). This example is built
as a paraview plugin, build environment specified below. The plugin takes
point data as input (sample attached), and just does the memory allocation
and creation of output arrays as I have previously described. On my
machine, as soon as I apply the filter, paraview crashes. Commenting line
107 in vtkHeapCorruption.cxx allows the filter to run, but the output is
then limited to single component arrays, where some of the input arrays
have 3 or 9 components.

QT 4.8.6, Visual Studio 2010, Built against Paraview commit SHA1
ID: 70155c17cfe7c2f547bb25ddb859a65518896ee3

On Wed, 22 Jul 2015 at 11:21 Bruce Jones <bruce.david.jones at gmail.com>
wrote:

> Thanks Berk,
>
> I have tried with both zero and 1 as the save argument and am getting the
> same behavior. As before, if I comment the SetNumberOfComponents call (or
> set number of components to 1) everything works, except I only have single
> component arrays in the output.
>
> I'm going to put together a minimum working example with the issue this
> afternoon so that I can show you guys in more detail.
>
> Cheers,
> Bruce
>
> On Wed, 22 Jul 2015 at 11:09 Berk Geveci <berk.geveci at kitware.com> wrote:
>
>> The solution is in the documentation:
>>
>>   // This method lets the user specify data to be held by the array.  The
>>   // array argument is a pointer to the data.  size is the size of the
>>   // array supplied by the user.  Set save to 1 to keep the class from
>>   // deleting the array when it cleans up or reallocates memory.  The
>> class
>>   // uses the actual array provided; it does not copy the data from the
>>   // suppled array. If specified, the delete method determines how the
>> data
>>   // array will be deallocated. If the delete method is
>>   // VTK_DATA_ARRAY_FREE, free() will be used. If the delete method is
>>   // DELETE, delete[] will be used. The default is FREE.
>>
>> You are passing 0 for the "save" argument, which means that VTK will
>> delete the array when the VTK array object is deleted, which would cause a
>> double delete/free. Use 1 as the second argument of SetArray() if you are
>> managing the memory. Also, make sure that the VTK array is not used after
>> you free your array.
>>
>> Best,
>> -berk
>>
>> On Wed, Jul 22, 2015 at 9:56 AM, Bruce Jones <bruce.david.jones at gmail.com
>> > wrote:
>>
>>> Hi Guys,
>>>
>>> I have just tried it as you suggested, doing SetNumberOfComponents then
>>> SetArray, without doing SetNumberOfTuples. Unfortunately I am still getting
>>> the same behaviour.
>>>
>>> Cheers,
>>> Bruce
>>>
>>> On Wed, 22 Jul 2015 at 09:44 Berk Geveci <berk.geveci at kitware.com>
>>> wrote:
>>>
>>>> Actually, don't call SetNumberOfTuples() at all if you are using
>>>> SetArray(). It will unnecessarily allocate memory if you call it before
>>>> SetArray().
>>>>
>>>> -berk
>>>>
>>>> On Wed, Jul 22, 2015 at 9:40 AM, Shawn Waldon <shawn.waldon at kitware.com
>>>> > wrote:
>>>>
>>>>> Hi Bruce,
>>>>>
>>>>> SetNumberOfTuples reallocates the internal datastructure of the data
>>>>> array to be the new required size based on the new number of components and
>>>>> number of tuples.  This (combined with trying to clean up the old data from
>>>>> SetArray) may be causing the heap corruption you are seeing.  Try setting
>>>>> the number of components and number of tuples before adding the data to the
>>>>> array.
>>>>>
>>>>> HTH,
>>>>> Shawn
>>>>>
>>>>> On Tue, Jul 21, 2015 at 1:37 PM, Bruce Jones <
>>>>> bruce.david.jones at gmail.com> wrote:
>>>>>
>>>>>> Hi Cory,
>>>>>>
>>>>>> Sorry for the delayed response, I've hit another more serious bug
>>>>>> which has been diverting my attention from this.
>>>>>>
>>>>>> Thanks for the state file, I haven't got it to work as I don't have
>>>>>> numpy set up, but I have also got this working with 9 component arrays in
>>>>>> paraview using a python script. However, I am now trying to port my python
>>>>>> plugin to c++ which is where I am seeing the error.
>>>>>>
>>>>>> In my plugin I want to output a vtkarray for each vtkarray in the
>>>>>> input dataset. The values in the output vtkarrays are interpolated from
>>>>>> those in the input vtkarrays. Rather than working directly on vtkarray
>>>>>> objects, I am allocating c++ arrays for each vtkarray, performing the
>>>>>> interpolation, then creating vtkDoubleArrays and using SetArray to pass a
>>>>>> pointer to my allocated c++ arrays to the output vtkarrays. The code for
>>>>>> setting up the output vtkarrays is roughly as follows
>>>>>>
>>>>>>                 vtkPointData *pointData = input->GetPointData();
>>>>>>                 vtkDataArray *dArray = pointData->GetArray(i);
>>>>>> vtkDoubleArray *vtkDArrayAve = vtkDoubleArray::New();
>>>>>> vtkDArrayAve->SetName(dArray->GetName());
>>>>>> vtkDArrayAve->SetArray(dArraysAve[i],hgrid->GetTotalCells(),0);
>>>>>> vtkDArrayAve->SetNumberOfComponents(numComponents[i]);
>>>>>> vtkDArrayAve->SetNumberOfTuples(hgrid->GetTotalCells());
>>>>>> output->GetPointData()->AddArray(vtkDArrayAve);
>>>>>>
>>>>>> dArraysAve is an array of pointers pointing to my c++ arrays
>>>>>> hgrid->GetTotalCells() returns the number of data points for my output
>>>>>>
>>>>>> I also have another mode of operation for this plugin, where I
>>>>>> perform the interpolation differently, in that function, if I make the call
>>>>>> to SetNumberOfComponents() some heap corruption occurs and I get a segfault
>>>>>> when I try to subsequently free my c++ arrays. Commenting out the call to
>>>>>> SetNumberOfComponents avoids the segfault, but then I am limited to single
>>>>>> component arrays. This is the more serious bug I mentioned, initially I
>>>>>> figured they were unrelated, but I can't deny the number of components
>>>>>> coincidence.
>>>>>>
>>>>>> Cheers,
>>>>>> Bruce
>>>>>>
>>>>>> On Thu, 16 Jul 2015 at 14:41 Cory Quammen <cory.quammen at kitware.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Bruce,
>>>>>>>
>>>>>>> I have attached a ParaView state file with a Programmable Source
>>>>>>> that produces a vtkPolyData with 100 random points and a point data array
>>>>>>> with 9 components. It seems to display the various component ranges just
>>>>>>> fine.
>>>>>>>
>>>>>>> Best,
>>>>>>> Cory
>>>>>>>
>>>>>>> On Thu, Jul 16, 2015 at 11:14 AM, Cory Quammen <
>>>>>>> cory.quammen at kitware.com> wrote:
>>>>>>>
>>>>>>>> Hi Bruce,
>>>>>>>>
>>>>>>>> I haven't seen this, but ParaView may be interpreting this array as
>>>>>>>> a tensor field. Do you have a smallish test data file that you can share
>>>>>>>> that shows the problem?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Cory
>>>>>>>>
>>>>>>>> On Sat, Jul 11, 2015 at 11:14 AM, Bruce Jones <
>>>>>>>> bruce.david.jones at gmail.com> wrote:
>>>>>>>>
>>>>>>>>> I am creating vtkDoubleArrays based on averaging some input data
>>>>>>>>> to a reduced set of points. The input data includes various vtk arrays
>>>>>>>>> which have 1, 3 and 9 components.
>>>>>>>>>
>>>>>>>>> After averaging, I am writing the data to c++ arrays, and creating
>>>>>>>>> a new vtkDoubleArray using the SetArray() function to pass the c++ arrays.
>>>>>>>>> This works fine for 1 and 3 component arrays, however for the 9 component
>>>>>>>>> arrays paraview shows that every element is set to 0.
>>>>>>>>>
>>>>>>>>> If I hardcode it so that 9 component arrays become 3 component
>>>>>>>>> arrays (reading only the first 3 components from the input array), then I
>>>>>>>>> get the correct data for the first 3 components, though I obviously need
>>>>>>>>> the other 6 components in the end.
>>>>>>>>>
>>>>>>>>> Has anyone encountered this before?
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Bruce
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Cory Quammen
>>>>>>>> R&D Engineer
>>>>>>>> Kitware, Inc.
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Cory Quammen
>>>>>>> R&D Engineer
>>>>>>> Kitware, Inc.
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>
>>>>>
>>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150722/c4973fd2/attachment-0001.html>
-------------- next part --------------
// gridFromSPH code
#include "vtkHeapCorruption.h"

// VTK code
#include "vtkObjectFactory.h"
#include "vtkInformationVector.h"
#include "vtkInformation.h"
#include "vtkImageData.h"
#include "vtkPolyData.h"
#include "vtkPointData.h"
#include "vtkStreamingDemandDrivenPipeline.h"
#include "vtkDoubleArray.h"


vtkStandardNewMacro(vtkHeapCorruption);

//----------------------------------------------------------------------------
vtkHeapCorruption::vtkHeapCorruption()
{
	memPrevAllocated = false;
}

//----------------------------------------------------------------------------
vtkHeapCorruption::~vtkHeapCorruption()
{
	FreeMemory();
}

//----------------------------------------------------------------------------
void vtkHeapCorruption::PrintSelf(ostream& os, vtkIndent indent)
{
	this->Superclass::PrintSelf(os,indent);
}

int vtkHeapCorruption::FillInputPortInformation(
	int vtkNotUsed(port), vtkInformation* info)
{
	info->Set(vtkAlgorithm::INPUT_REQUIRED_DATA_TYPE(), "vtkPolyData");
	return 1;
}

int vtkHeapCorruption::RequestInformation (
	vtkInformation * vtkNotUsed(request),
	vtkInformationVector ** vtkNotUsed( inputVector ),
	vtkInformationVector *outputVector)
{
	vtkInformation* outInfo = outputVector->GetInformationObject(0);

	outInfo->Set(vtkStreamingDemandDrivenPipeline::WHOLE_EXTENT(),
		0, 50,
		0, 50,
		0, 5);

  	double origin[3] = {0.0,0.0,0.0};
	outInfo->Set(vtkDataObject::ORIGIN(),origin,3);

	double spacing[3] = {0.1,0.1,0.1};
	outInfo->Set(vtkDataObject::SPACING(),spacing,3);

	return 1;
}

int vtkHeapCorruption::RequestData(
	vtkInformation*,
	vtkInformationVector** inputVector,
	vtkInformationVector* outputVector)
{
	vtkInformation* inInfo = inputVector[0]->GetInformationObject(0);
	vtkDataSet *input = vtkPolyData::SafeDownCast(
		inInfo->Get(vtkDataObject::DATA_OBJECT()));

	vtkInformation *outInfo = outputVector->GetInformationObject(0);
	vtkImageData *output = vtkImageData::SafeDownCast(
		outInfo->Get(vtkDataObject::DATA_OBJECT()));

	output->SetExtent(
		outInfo->Get(vtkStreamingDemandDrivenPipeline::WHOLE_EXTENT()));

	vtkPointData *pointData = input->GetPointData();

	numArrays = pointData->GetNumberOfArrays();

	// Preform memory allocation
	// Note: Cannot free memory at end of this all to RequestData otherwise
	// we cannot see the result in paraview, so we free this memory on the
	// next timestep and reallocate - could/should be done differently
	if(memPrevAllocated) FreeMemory();
	dArraysAve = (double**)malloc(numArrays*sizeof(double*));
	numComponents = (int*)malloc(numArrays*sizeof(int));
	for(int dataArray = 0; dataArray<numArrays; dataArray++)
	{
		vtkDataArray *dArray = pointData->GetArray(dataArray);
		numComponents[dataArray] = dArray->GetNumberOfComponents();
		dArraysAve[dataArray] = (double*)malloc(numComponents[dataArray]*50*50*5*sizeof(double));
	}
	memPrevAllocated = true;

	// Create an output array for each input array
	for(int dataArray=0; dataArray<numArrays; dataArray++)
	{
		vtkDataArray *dArray = pointData->GetArray(dataArray);

		vtkDoubleArray *vtkDArrayAve = vtkDoubleArray::New();
		vtkDArrayAve->SetName(dArray->GetName());
		// Comment the next line and the code will "work" however we can only have
		// single component arrays in that case
		vtkDArrayAve->SetNumberOfComponents(numComponents[dataArray]);
		vtkDArrayAve->SetArray(dArraysAve[dataArray],50*50*5,1);
		output->GetPointData()->AddArray(vtkDArrayAve);
	}

	return 1;
}

void vtkHeapCorruption::FreeMemory()
{
	for(int i = 0; i<numArrays; i++)
	{
		free(dArraysAve[i]);
	}
	free(dArraysAve);
	free(numComponents);
}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: HeapCorruption.xml
Type: text/xml
Size: 1103 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150722/c4973fd2/attachment-0001.xml>
-------------- next part --------------
cmake_minimum_required(VERSION 2.8.8 FATAL_ERROR)

if (NOT ParaView_BINARY_DIR)
  find_package(ParaView REQUIRED)
  include(${PARAVIEW_USE_FILE})
endif()

# Set a consistent MACOSX_RPATH default across all CMake versions.
# When CMake 2.8.12 is required, change this default to 1.
# When CMake 3.0.0 is required, remove this block (see CMP0042).
if(NOT DEFINED CMAKE_MACOSX_RPATH)
  set(CMAKE_MACOSX_RPATH 0)
endif()

include(ParaViewPlugins)

SET(PLUGIN_NAME HeapCorruption)
SET(PLUGIN_VERSION "1.0")

# create a paraview plugin containing server manager xml and the server
# manager classes to build
# this plugin can be loaded on the server side

ADD_PARAVIEW_PLUGIN(HeapCorruption "1.0"
  SERVER_MANAGER_XML HeapCorruption.xml
  SERVER_MANAGER_SOURCES vtkHeapCorruption.cxx)
-------------- next part --------------
#ifndef __GridFromSPH_h
#define __GridFromSPH_h

#include "vtkImageAlgorithm.h"

class vtkHeapCorruption : public vtkImageAlgorithm
{
public:
	static vtkHeapCorruption* New();
	vtkTypeMacro(vtkHeapCorruption, vtkImageAlgorithm);

	// VTK/Paraview event handlers
	virtual int FillInputPortInformation(int port, vtkInformation* info);

	virtual int RequestInformation (vtkInformation *,
		vtkInformationVector **,
		vtkInformationVector *);

	virtual int RequestData(vtkInformation* request,
		vtkInformationVector** inputVector,
		vtkInformationVector* outputVector);

	void PrintSelf(ostream& os, vtkIndent indent);

protected:
	vtkHeapCorruption();
	~vtkHeapCorruption();

private:
  vtkHeapCorruption(const vtkHeapCorruption&);  // Not implemented.
  void operator=(const vtkHeapCorruption&);  // Not implemented.
  int numArrays;
  double **dArraysAve;
  int *numComponents;
  bool memPrevAllocated;

  // Utility functions
  void FreeMemory();
};

#endif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: solid_ts_00000100.vtp
Type: application/octet-stream
Size: 139238 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150722/c4973fd2/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: solid_ts_00000000.vtp
Type: application/octet-stream
Size: 93072 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150722/c4973fd2/attachment-0003.obj>

From fissell at pitt.edu  Wed Jul 22 15:08:09 2015
From: fissell at pitt.edu (Kate Fissell)
Date: Wed, 22 Jul 2015 15:08:09 -0400
Subject: [Paraview] paraview 4.1 and greater not getting slice
 representation on remote logins
Message-ID: <55AFEA19.5040104@pitt.edu>

Hi,

On Paraview versions 4.1 and greater if I ssh -X from a Centos machine 
into an Ubuntu
graphics server to run Paraview I have a problem with viewing images.

I load the AnalyzeNifTIIO plugin, and load a nifti image, and I believe 
it loads correctly.
I get the wireframe, the Information panel gives the correct 
cells/point.  If I change to
Slice representation the view window stays blank.  Volume representation 
is fine, I get the
3D rendering.
Same thing if I load a vti format of the data, no slice view.

This happens when I ssh from a Centos machine, it does not happen when I 
ssh from
an Ubuntu machine.   In both cases I believe I am using glx to do the 
rendering locally,
not doing a setenv DISPLAY to ship the rendered picture over the net.
It is the same glx version on the Ubuntu and Centos machine, but they 
have different
graphics cards.

Ubuntu server running Paraview (console graphics):
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: Quadro K4000/PCIe/SSE2
OpenGL core profile version string: 4.3.0 NVIDIA 331.113
OpenGL core profile shading language version string: 4.30 NVIDIA via Cg 
compiler
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.4.0 NVIDIA 331.113
OpenGL shading language version string: 4.40 NVIDIA via Cg compiler
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL extensions:


Centos machine ssh'd to Ubuntu server:
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: Quadro FX 580/PCIe/SSE2
OpenGL version string: 2.1.2 NVIDIA 340.76
OpenGL shading language version string: 1.20 NVIDIA via Cg compiler
OpenGL extensions:


Ubuntu machine ssh'd to Ubuntu server:
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: Quadro K4000/PCIe/SSE2
OpenGL version string: 2.1.2 NVIDIA 304.125
OpenGL shading language version string: 1.20 NVIDIA via Cg compiler
OpenGL extensions:


In Paraview ParaView-v4.0.1 I do not have this problem.
I have the problem in Paraview-4.1, 4.2, 4.3.

I am using your pre-compiled binaries as test, but I have the same problem
with my compilation.

Do you know what changed from ParaView-v4.0.1 to ParaView-v4.1 that 
would cause
this or what the workaround is ?

thanks
Kate

From utkarsh.ayachit at kitware.com  Wed Jul 22 15:35:41 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 22 Jul 2015 15:35:41 -0400
Subject: [Paraview] paraview 4.1 and greater not getting slice
 representation on remote logins
In-Reply-To: <55AFEA19.5040104@pitt.edu>
References: <55AFEA19.5040104@pitt.edu>
Message-ID: <CADHSJjBKMu_R=LdmhT9CqioSaU3S6w3+9JUBQCTx2j65V5EQzg@mail.gmail.com>

Kate,

I suspect it's related to this fix:
https://gitlab.kitware.com/paraview/paraview/merge_requests/92

I tested with the latest git/master and it does render correctly in
client-server mode too.

A workaround would be to use the Slice filter instead. It will be a
little slower and more memory intensive than "Slice" representation,
however.

Utkarsh

On Wed, Jul 22, 2015 at 3:08 PM, Kate Fissell <fissell at pitt.edu> wrote:
> Hi,
>
> On Paraview versions 4.1 and greater if I ssh -X from a Centos machine into
> an Ubuntu
> graphics server to run Paraview I have a problem with viewing images.
>
> I load the AnalyzeNifTIIO plugin, and load a nifti image, and I believe it
> loads correctly.
> I get the wireframe, the Information panel gives the correct cells/point.
> If I change to
> Slice representation the view window stays blank.  Volume representation is
> fine, I get the
> 3D rendering.
> Same thing if I load a vti format of the data, no slice view.
>
> This happens when I ssh from a Centos machine, it does not happen when I ssh
> from
> an Ubuntu machine.   In both cases I believe I am using glx to do the
> rendering locally,
> not doing a setenv DISPLAY to ship the rendered picture over the net.
> It is the same glx version on the Ubuntu and Centos machine, but they have
> different
> graphics cards.
>
> Ubuntu server running Paraview (console graphics):
> OpenGL vendor string: NVIDIA Corporation
> OpenGL renderer string: Quadro K4000/PCIe/SSE2
> OpenGL core profile version string: 4.3.0 NVIDIA 331.113
> OpenGL core profile shading language version string: 4.30 NVIDIA via Cg
> compiler
> OpenGL core profile context flags: (none)
> OpenGL core profile profile mask: core profile
> OpenGL core profile extensions:
> OpenGL version string: 4.4.0 NVIDIA 331.113
> OpenGL shading language version string: 4.40 NVIDIA via Cg compiler
> OpenGL context flags: (none)
> OpenGL profile mask: (none)
> OpenGL extensions:
>
>
> Centos machine ssh'd to Ubuntu server:
> OpenGL vendor string: NVIDIA Corporation
> OpenGL renderer string: Quadro FX 580/PCIe/SSE2
> OpenGL version string: 2.1.2 NVIDIA 340.76
> OpenGL shading language version string: 1.20 NVIDIA via Cg compiler
> OpenGL extensions:
>
>
> Ubuntu machine ssh'd to Ubuntu server:
> OpenGL vendor string: NVIDIA Corporation
> OpenGL renderer string: Quadro K4000/PCIe/SSE2
> OpenGL version string: 2.1.2 NVIDIA 304.125
> OpenGL shading language version string: 1.20 NVIDIA via Cg compiler
> OpenGL extensions:
>
>
> In Paraview ParaView-v4.0.1 I do not have this problem.
> I have the problem in Paraview-4.1, 4.2, 4.3.
>
> I am using your pre-compiled binaries as test, but I have the same problem
> with my compilation.
>
> Do you know what changed from ParaView-v4.0.1 to ParaView-v4.1 that would
> cause
> this or what the workaround is ?
>
> thanks
> Kate
> _______________________________________________
> 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

From utkarsh.ayachit at kitware.com  Wed Jul 22 16:06:34 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 22 Jul 2015 16:06:34 -0400
Subject: [Paraview] Bug with the trace tool : Exporting view instruction
 not repeatable
In-Reply-To: <CAGox_owQwgeuDchfmGgA+SY10on4fXFTmqmX4SHMHvNDBXg_XQ@mail.gmail.com>
References: <CAGox_owQwgeuDchfmGgA+SY10on4fXFTmqmX4SHMHvNDBXg_XQ@mail.gmail.com>
Message-ID: <CADHSJjBSy11UgbW_eKUOAO_X4Qoht4=9d9LT2CJnc5+EoUBUPw@mail.gmail.com>

Silv?re,

There was a bug in the code that traced it where it picked up an
incorrect property name. As a workaround, you can change the
"Rasterize3DGeometry" to "Rasterize3Dgeometry" (note the different
case).

e.g.
ExportView('/tmp/sample.pdf', view=renderView1, Rasterize3Dgeometry=0)



On Wed, Jul 22, 2015 at 11:04 AM, Silvere Pierre
<silvere.pierre.paraview at gmail.com> wrote:
> Hello everyone,
>
> I am used to create vector images (PDF) using the export view tool in the
> Paraview 4.3 GUI.
> As I wanted to use it in scripts I used Start Trace to get the python
> instructions which is :
>
> ExportView('your_path.pdf', view=your_render_view, Rasterize3DGeometry=0)
>
> Problem is, the Rasterize3DGeometry option is unknown when you try and use
> it in the console (and without it you get a pixeled image).
>
> I looked up old messages and found this piece of code :
>
> rw = your_render_view.GetRenderWindow()
> exp = paraview.vtk.vtkInstantiator.CreateInstance('vtkGL2PSExporter')
> exp.SetRenderWindow(rw)
> exp.SetDrawBackground(0)
> exp.SetSortToSimple()
> exp.SetFileFormatToPDF()
> exp.SetFilePrefix("your_path.pdf")
> exp.Write3DPropsAsRasterImageOff()
> exp.Write()
>
> that should take care of it in a less direct way. Unfortunately, the
> instanciation fail and the object (named exp here) is undefined.
>
> Is it only an interface problem with python ? Is there any way to get the
> correct instance of the renderer ?
>
> Best regards,
>
> Silv?re Pierre
>
> _______________________________________________
> 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
>

From fissell at pitt.edu  Wed Jul 22 14:43:56 2015
From: fissell at pitt.edu (Kate Fissell)
Date: Wed, 22 Jul 2015 14:43:56 -0400
Subject: [Paraview] disable Ubuntu Unity global menu in ParaView
Message-ID: <55AFE46C.2090702@pitt.edu>

Hi,

When I compiled Paraview-4.3.1 on Ubuntu-14.04 the top menu bar for the 
Paraview window
was no longer on the Paraview window but at the top of the console 
screen.   This "global" or
"single" application menu is an Ubuntu  Unity desktop  thing.
To disable this I edited the source code and added
menubar()->setNativeMenuBar(false);
in the paraview code that initializes the application.
I see in the precompiled paraview binaries that you release that the 
menubar does stay
on the paraview application window.   How did you do that ?
Is there a cmake setting I can use to do this instead of editing source 
code ?

thanks
Kate

From jeffrey.c.becker at nasa.gov  Wed Jul 22 19:15:38 2015
From: jeffrey.c.becker at nasa.gov (Jeff Becker)
Date: Wed, 22 Jul 2015 16:15:38 -0700
Subject: [Paraview] [vtkusers] Combining vtk and paraview python scripts
In-Reply-To: <55AE6FCE.2010407@nasa.gov>
References: <55A55C2C.2030107@nasa.gov>
 <CAMaOp+GaBL5wqsU4YiQ5-VpZWqzDjPF8=oc6p950Oums+01+Zg@mail.gmail.com>
 <55A56672.3040204@nasa.gov>
 <CAE32kpXDT5cq51PBged+9HF=pFcpEMJeZq9oJGaC6Mmqx2coSA@mail.gmail.com>
 <55AD3918.3030808@nasa.gov>
 <CAE32kpW9LoazpP6Xu_3WUmVMqE8FoA0kiw5TRAXrwwms0OBOQg@mail.gmail.com>
 <55AE6FCE.2010407@nasa.gov>
Message-ID: <55B0241A.4050307@nasa.gov>

Now that I can load image (uniform rectilinear grid) data using the 
Python Programmable Source, I'm trying to do this on four gpu nodes 
(using mpirun -np 4 pvserver). Once I load my image, I thought it would 
be automatically distributed (equally) to the four nodes, but coloring 
by process id shows that everything happens on one node. What do I need 
to do (short of writing out four pvti files and reading them back in) to 
automatically distribute my data?

Thanks.

-jeff

On 07/21/2015 09:14 AM, Jeff Becker wrote:
> On 07/20/2015 05:43 PM, Berk Geveci wrote:
>> You probably need to update vtkImageExport and shallow copy its 
>> output to the programmable source's output. You also need to add 
>> something to the RequestInformation setting the whole extent. You 
>> need something like:
>>
>> from paraview import util
>> util.SetOutputWholeExtent(self, [0,nx-1,0,ny-1,0,nz-1])
>>
>> By the way, there are better ways of getting numpy arrays into VTK 
>> than the image import stuff. See some of the earlier blogs here:
>
> Right. I found the RequestInformation info above from searching the 
> web. Then I was able to follow the instructions in the ParaView Guide 
> section 13.2.4 Reading binary 2D image. I basically replaced the image 
> import stuff with code analogous  to the output assignment,
>
> Thanks for your help.
>

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

From ganesh.iitm at gmail.com  Wed Jul 22 22:37:37 2015
From: ganesh.iitm at gmail.com (Ganesh Vijayakumar)
Date: Thu, 23 Jul 2015 02:37:37 +0000
Subject: [Paraview] Paraview server using off-screen rendering
In-Reply-To: <CAOXZzG7tB=7tC+X0OesEY5yAntYP58y061B9guQkUmz9cnEzZg@mail.gmail.com>
References: <CAOXZzG7L4FLP_vsoPY3D1cqUyMdjd-H9T9sK53Teg0yMcpSvGQ@mail.gmail.com>
 <CAFtK+evUnwbV_9fC3GwKKx7ss3SQB0QanK4Eygs=NwN6O+JFxg@mail.gmail.com>
 <CAOXZzG7tB=7tC+X0OesEY5yAntYP58y061B9guQkUmz9cnEzZg@mail.gmail.com>
Message-ID: <CAFtK+etfTwogt=ymfZ1HmJcYB7_=aEYOUWqytANp7iE1ju6M6Q@mail.gmail.com>

Dear Chuck,

   Finally, I got this done. I could get paraview to configure without
giving any errors. I removed the build directory and started afresh.
However, it fails at the same place during the compilation. Could you
advise as to what might be the problem.

Linking C executable ../../../../bin/vtkmkg3states-pv4.3
/usr/lib/../lib64/libpthread.a(lowlevellock.o): In function
`__lll_lock_wait_private':
/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:81:
multiple definition of `__lll_lock
_wait_private'
/usr/lib/../lib64/libc.a(libc-lowlevellock.o):/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowleve
llock.S:81: first defined here
/usr/lib/../lib64/libpthread.a(lowlevellock.o): In function
`__lll_unlock_wake_private':
/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:323:
multiple definition of `__lll_unl
ock_wake_private'
/usr/lib/../lib64/libc.a(libc-lowlevellock.o):/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowleve
llock.S:323: first defined here
/usr/bin/ld: link errors found, deleting executable
`../../../../bin/vtkmkg3states-pv4.3'
collect2: error: ld returned 1 exit status
make[2]: *** [bin/vtkmkg3states-pv4.3] Error 1
make[1]: *** [VTK/ThirdParty/tiff/vtktiff/CMakeFiles/vtkmkg3states.dir/all]
Error 2
make: *** [all] Error 2


ganesh

On Thu, Jul 16, 2015 at 2:19 PM Chuck Atkins <chuck.atkins at kitware.com>
wrote:

> If it's a problem with HDF5 library, I'm not sure where I need to point to
>>>> the system installation.
>>>>
>>> If you load the cray-hdf5 module, that will set the HDF5_DIR environment
>>> variable to the correct location.  Unfortunately, CMake uses the HDF5_ROOT
>>> variable instead to look for it so you'll neet to set it accordingly.
>>>
>> I don't have much experience with cmake, but can I set additional
>> variables in the ccmake window? Should this variable show up there asking
>> to be set if you turn on the advanced mode toggle?
>>
>
> Different find modules work differently.  The FindHDF5 module uses the
> HDF5_ROOT environment variable (not CMake variable, which is why it won't
> show up in the ccmake UI) as a hint for where to search, hence exporting it
> as an env var prior to running CMake.  You'll also want to be sure to
> specify to use an external HDF5 rather than ParaView building it's own:
>
>   -DVTK_USE_SYSTEM_HDF5:BOOL=ON
>
>
>  CMAKE_CXX_FLAGS                  -L/lustre/medusa/gantech/
>> software/mesa-10.6.0/lib
>>
> ...
>
>>  CMAKE_C_FLAGS                    -L/lustre/medusa/gantech/
>> software/mesa-10.6.0/lib
>>
> ...
>
>>  CMAKE_EXE_LINKER_FLAGS           -L/lustre/medusa/gantech/
>> software/mesa-10.6.0/lib
>>
>
> Instead of setting these in the compiler flags, it's better to tell
> ParaView where to explicitly find the libraries and to configure
> accordingly for OSMesa.  You can pass these as command line arguments to
> cmake or ccmake with -D, or set them in the ccmake UI:
>
>   -DOPENGL_INCLUDE_DIR:PATH=
>   -DOPENGL_xmesa_INCLUDE_DIR:PATH=
>   -DOPENGL_gl_LIBRARY:FILEPATH=
>   -DOPENGL_glu_LIBRARY:FILEPATH=
>   -DOSMESA_INCLUDE_DIR:PATH=/lustre/medusa/gantech/
> software/mesa-10.6.0/include
>   -DOSMESA_LIBRARY:FILEPATH=/lustre/medusa/gantech/
> software/mesa-10.6.0/lib/libOSMesa.a
>   -DVTK_OPENGL_HAS_OSMESA:BOOL=ON
>   -DVTK_USE_X:BOOL=OFF
>
>
>
>>  CMAKE_Fortran_COMPILER           /opt/gcc/4.9.2/bin/gfortran
>>
>
> Not that it will really matter since we're not compiling Fortran code, but
> this should be /opt/cray/craype/2.2.1/bin/ftn
>
>
>  MPI_CXX_LIBRARIES                /opt/cray/mpt/7.1.3/gni/
>> mpich2-gnu/49/lib/
>>
> ...
>
>>  MPI_C_LIBRARIES                  /opt/cray/mpt/7.1.3/gni/
>> mpich2-gnu/49/lib/
>>
> ...
>
>>  MPI_LIBRARY                      /opt/cray/mpt/7.1.3/gni/
>> mpich2-gnu/49/lib
>>
>
> It does look like the wrappers are correctly getting used for mpicc and
> mpiCC and you can see the include dirs getting set accordingly, but these
> do not look right.  Which version of CMake are you using?  Here's what I
> get using CMake 3.2.3 (current cmake) on a Cray XC30 when not setting any
> MPI variables, just letting CMake auto-detect them by enabling
> ParaView_USE_MPI=ON:
>
>  MPI_CXX_COMPILER
> /opt/cray/craype/2.1.0/bin/CC
>  MPI_CXX_COMPILE_FLAGS
>
>  MPI_CXX_INCLUDE_PATH
>
>  MPI_CXX_LIBRARIES
>
>  MPI_CXX_LINK_FLAGS
>
>  MPI_CXX_NO_INTERROGATE
> /opt/cray/craype/2.1.0/bin/CC
>  MPI_C_COMPILER
> /opt/cray/craype/2.1.0/bin/cc
>  MPI_C_COMPILE_FLAGS
>
>  MPI_C_INCLUDE_PATH
>
>  MPI_C_LIBRARIES
>
>  MPI_C_LINK_FLAGS
>
>  MPI_C_NO_INTERROGATE
> /opt/cray/craype/2.1.0/bin/cc
>  MPI_EXTRA_LIBRARY
> MPI_EXTRA_LIBRARY-NOTFOUND
>  MPI_Fortran_COMPILER
> /opt/cray/craype/2.1.0/bin/ftn
>  MPI_Fortran_COMPILE_FLAGS
>
>  MPI_Fortran_INCLUDE_PATH
>
>  MPI_Fortran_LIBRARIES
>
>  MPI_Fortran_LINK_FLAGS
>
>  MPI_Fortran_NO_INTERROGATE
> /opt/cray/craype/2.1.0/bin/ftn
>  MPI_LIBRARY                      MPI_LIBRARY-NOTFOUND
>
> Because the Cray wrappers automatically add the mpi libs and headers
> (behaving like mpiCC), then the MPI code should compile without any
> additional flags.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/d79e555b/attachment.html>

From chuck.atkins at kitware.com  Thu Jul 23 08:11:19 2015
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Thu, 23 Jul 2015 08:11:19 -0400
Subject: [Paraview] Paraview server using off-screen rendering
In-Reply-To: <CAFtK+etfTwogt=ymfZ1HmJcYB7_=aEYOUWqytANp7iE1ju6M6Q@mail.gmail.com>
References: <CAOXZzG7L4FLP_vsoPY3D1cqUyMdjd-H9T9sK53Teg0yMcpSvGQ@mail.gmail.com>
 <CAFtK+evUnwbV_9fC3GwKKx7ss3SQB0QanK4Eygs=NwN6O+JFxg@mail.gmail.com>
 <CAOXZzG7tB=7tC+X0OesEY5yAntYP58y061B9guQkUmz9cnEzZg@mail.gmail.com>
 <CAFtK+etfTwogt=ymfZ1HmJcYB7_=aEYOUWqytANp7iE1ju6M6Q@mail.gmail.com>
Message-ID: <CAOXZzG6of-A9+uLUopZpFTmmnwfL6RQBRkUGNW0w3V=xJX9Rog@mail.gmail.com>

Hi Ganesh,

Can you post your CMakeCache.txt?  Also, if you build with "make VERBOSE=1"
that will give the  full command that gets executed for the failing link
step.  Posting both of those will be helpful.

- Chuck

On Wed, Jul 22, 2015 at 10:37 PM, Ganesh Vijayakumar <ganesh.iitm at gmail.com>
wrote:

> Dear Chuck,
>
>    Finally, I got this done. I could get paraview to configure without
> giving any errors. I removed the build directory and started afresh.
> However, it fails at the same place during the compilation. Could you
> advise as to what might be the problem.
>
> Linking C executable ../../../../bin/vtkmkg3states-pv4.3
> /usr/lib/../lib64/libpthread.a(lowlevellock.o): In function
> `__lll_lock_wait_private':
> /usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:81:
> multiple definition of `__lll_lock
> _wait_private'
>
> /usr/lib/../lib64/libc.a(libc-lowlevellock.o):/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowleve
> llock.S:81: first defined here
> /usr/lib/../lib64/libpthread.a(lowlevellock.o): In function
> `__lll_unlock_wake_private':
> /usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:323:
> multiple definition of `__lll_unl
> ock_wake_private'
>
> /usr/lib/../lib64/libc.a(libc-lowlevellock.o):/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowleve
> llock.S:323: first defined here
> /usr/bin/ld: link errors found, deleting executable
> `../../../../bin/vtkmkg3states-pv4.3'
> collect2: error: ld returned 1 exit status
> make[2]: *** [bin/vtkmkg3states-pv4.3] Error 1
> make[1]: ***
> [VTK/ThirdParty/tiff/vtktiff/CMakeFiles/vtkmkg3states.dir/all] Error 2
> make: *** [all] Error 2
>
>
> ganesh
>
> On Thu, Jul 16, 2015 at 2:19 PM Chuck Atkins <chuck.atkins at kitware.com>
> wrote:
>
>> If it's a problem with HDF5 library, I'm not sure where I need to point
>>>>> to the system installation.
>>>>>
>>>> If you load the cray-hdf5 module, that will set the HDF5_DIR
>>>> environment variable to the correct location.  Unfortunately, CMake uses
>>>> the HDF5_ROOT variable instead to look for it so you'll neet to set it
>>>> accordingly.
>>>>
>>> I don't have much experience with cmake, but can I set additional
>>> variables in the ccmake window? Should this variable show up there asking
>>> to be set if you turn on the advanced mode toggle?
>>>
>>
>> Different find modules work differently.  The FindHDF5 module uses the
>> HDF5_ROOT environment variable (not CMake variable, which is why it won't
>> show up in the ccmake UI) as a hint for where to search, hence exporting it
>> as an env var prior to running CMake.  You'll also want to be sure to
>> specify to use an external HDF5 rather than ParaView building it's own:
>>
>>   -DVTK_USE_SYSTEM_HDF5:BOOL=ON
>>
>>
>>  CMAKE_CXX_FLAGS                  -L/lustre/medusa/gantech/
>>> software/mesa-10.6.0/lib
>>>
>> ...
>>
>>>  CMAKE_C_FLAGS                    -L/lustre/medusa/gantech/
>>> software/mesa-10.6.0/lib
>>>
>> ...
>>
>>>  CMAKE_EXE_LINKER_FLAGS           -L/lustre/medusa/gantech/
>>> software/mesa-10.6.0/lib
>>>
>>
>> Instead of setting these in the compiler flags, it's better to tell
>> ParaView where to explicitly find the libraries and to configure
>> accordingly for OSMesa.  You can pass these as command line arguments to
>> cmake or ccmake with -D, or set them in the ccmake UI:
>>
>>   -DOPENGL_INCLUDE_DIR:PATH=
>>   -DOPENGL_xmesa_INCLUDE_DIR:PATH=
>>   -DOPENGL_gl_LIBRARY:FILEPATH=
>>   -DOPENGL_glu_LIBRARY:FILEPATH=
>>   -DOSMESA_INCLUDE_DIR:PATH=/lustre/medusa/gantech/
>> software/mesa-10.6.0/include
>>   -DOSMESA_LIBRARY:FILEPATH=/lustre/medusa/gantech/
>> software/mesa-10.6.0/lib/libOSMesa.a
>>   -DVTK_OPENGL_HAS_OSMESA:BOOL=ON
>>   -DVTK_USE_X:BOOL=OFF
>>
>>
>>
>>>  CMAKE_Fortran_COMPILER           /opt/gcc/4.9.2/bin/gfortran
>>>
>>
>> Not that it will really matter since we're not compiling Fortran code,
>> but this should be /opt/cray/craype/2.2.1/bin/ftn
>>
>>
>>  MPI_CXX_LIBRARIES                /opt/cray/mpt/7.1.3/gni/
>>> mpich2-gnu/49/lib/
>>>
>> ...
>>
>>>  MPI_C_LIBRARIES                  /opt/cray/mpt/7.1.3/gni/
>>> mpich2-gnu/49/lib/
>>>
>> ...
>>
>>>  MPI_LIBRARY                      /opt/cray/mpt/7.1.3/gni/
>>> mpich2-gnu/49/lib
>>>
>>
>> It does look like the wrappers are correctly getting used for mpicc and
>> mpiCC and you can see the include dirs getting set accordingly, but these
>> do not look right.  Which version of CMake are you using?  Here's what I
>> get using CMake 3.2.3 (current cmake) on a Cray XC30 when not setting any
>> MPI variables, just letting CMake auto-detect them by enabling
>> ParaView_USE_MPI=ON:
>>
>>  MPI_CXX_COMPILER
>> /opt/cray/craype/2.1.0/bin/CC
>>  MPI_CXX_COMPILE_FLAGS
>>
>>  MPI_CXX_INCLUDE_PATH
>>
>>  MPI_CXX_LIBRARIES
>>
>>  MPI_CXX_LINK_FLAGS
>>
>>  MPI_CXX_NO_INTERROGATE
>> /opt/cray/craype/2.1.0/bin/CC
>>  MPI_C_COMPILER
>> /opt/cray/craype/2.1.0/bin/cc
>>  MPI_C_COMPILE_FLAGS
>>
>>  MPI_C_INCLUDE_PATH
>>
>>  MPI_C_LIBRARIES
>>
>>  MPI_C_LINK_FLAGS
>>
>>  MPI_C_NO_INTERROGATE
>> /opt/cray/craype/2.1.0/bin/cc
>>  MPI_EXTRA_LIBRARY
>> MPI_EXTRA_LIBRARY-NOTFOUND
>>  MPI_Fortran_COMPILER
>> /opt/cray/craype/2.1.0/bin/ftn
>>  MPI_Fortran_COMPILE_FLAGS
>>
>>  MPI_Fortran_INCLUDE_PATH
>>
>>  MPI_Fortran_LIBRARIES
>>
>>  MPI_Fortran_LINK_FLAGS
>>
>>  MPI_Fortran_NO_INTERROGATE
>> /opt/cray/craype/2.1.0/bin/ftn
>>  MPI_LIBRARY                      MPI_LIBRARY-NOTFOUND
>>
>> Because the Cray wrappers automatically add the mpi libs and headers
>> (behaving like mpiCC), then the MPI code should compile without any
>> additional flags.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/787feb1e/attachment.html>

From cory.quammen at kitware.com  Thu Jul 23 09:51:12 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 23 Jul 2015 09:51:12 -0400
Subject: [Paraview] PV 4.10 plot over line using mesh coordinates
In-Reply-To: <55AE09A1.8040504@inria.fr>
References: <55AE09A1.8040504@inria.fr>
Message-ID: <CAB5Fpx42_RN0LJt=zVHWvSvD3_qXGiCdTHwBLJvdSs9-xS4NDQ@mail.gmail.com>

Hi Stephen,

To my knowledge there is no filter in ParaView to do what you are asking.
For an unstructured grid, it seems to me that no matter where the sample
points are on the line, you are going to need some kind of interpolation at
cell faces and edges where the line intersects the mesh structure to get
the data values to plot. For structured grids, you might be able to plot
values along a 1D subset of the mesh with some work, but not using the Plot
Over Line filter.

Thanks,
Cory

On Tue, Jul 21, 2015 at 4:58 AM, Stephen Wornom <stephen.wornom at inria.fr>
wrote:

> One of the inputs to Plot over line  is the number of points (equally
> spaced, I assumed).
> The solution is interpolated to the points. This poses a problem for
> highly stretched meshes like the normal coordinate in a boundary layer.
>
> I would like to plot over line using the actual mesh values and NOT the
> interpolated values.
> Is this possible in PV?
>
> How do I extract a line using the filters? That would be useful.
>
> Hope my questions are clear,
> Stephen
>
>
> --
>
>
> _______________________________________________
> 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
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/5717f798/attachment.html>

From oksana_golovnya at mail.ru  Thu Jul 23 10:20:42 2015
From: oksana_golovnya at mail.ru (=?UTF-8?B?T2tzYW5h?=)
Date: Thu, 23 Jul 2015 17:20:42 +0300
Subject: [Paraview] =?utf-8?q?Molecular_dynamics_from_lammps?=
In-Reply-To: <CAE32kpW9hj4bQK6eqvvDT4JDVmhE+naOMs6VyPm7haU2gODZPA@mail.gmail.com>
References: <1436279999.571994242@f345.i.mail.ru>
 <1436852798.517668428@f416.i.mail.ru>
 <CAE32kpW9hj4bQK6eqvvDT4JDVmhE+naOMs6VyPm7haU2gODZPA@mail.gmail.com>
Message-ID: <1437661242.850995039@f94.i.mail.ru>

 Berk, thank you for the ideas! I have made the projections using Programmable Filter. It is really very powerful tool.

Oksana
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/17be4b65/attachment.html>

From andy.bauer at kitware.com  Thu Jul 23 10:40:45 2015
From: andy.bauer at kitware.com (Andy Bauer)
Date: Thu, 23 Jul 2015 10:40:45 -0400
Subject: [Paraview] PV 4.10 plot over line using mesh coordinates
In-Reply-To: <CAB5Fpx42_RN0LJt=zVHWvSvD3_qXGiCdTHwBLJvdSs9-xS4NDQ@mail.gmail.com>
References: <55AE09A1.8040504@inria.fr>
 <CAB5Fpx42_RN0LJt=zVHWvSvD3_qXGiCdTHwBLJvdSs9-xS4NDQ@mail.gmail.com>
Message-ID: <CAMaOp+H4SMCmjRU6aKBJ30qErQN5bH9HAHFesb2ib_U7JLx_Dw@mail.gmail.com>

I think you may be able to get what you want if you first do a Slice
through your domain (for 3D only) and then do a Plot on Intersections Curve.

On Thu, Jul 23, 2015 at 9:51 AM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Hi Stephen,
>
> To my knowledge there is no filter in ParaView to do what you are asking.
> For an unstructured grid, it seems to me that no matter where the sample
> points are on the line, you are going to need some kind of interpolation at
> cell faces and edges where the line intersects the mesh structure to get
> the data values to plot. For structured grids, you might be able to plot
> values along a 1D subset of the mesh with some work, but not using the Plot
> Over Line filter.
>
> Thanks,
> Cory
>
> On Tue, Jul 21, 2015 at 4:58 AM, Stephen Wornom <stephen.wornom at inria.fr>
> wrote:
>
>> One of the inputs to Plot over line  is the number of points (equally
>> spaced, I assumed).
>> The solution is interpolated to the points. This poses a problem for
>> highly stretched meshes like the normal coordinate in a boundary layer.
>>
>> I would like to plot over line using the actual mesh values and NOT the
>> interpolated values.
>> Is this possible in PV?
>>
>> How do I extract a line using the filters? That would be useful.
>>
>> Hope my questions are clear,
>> Stephen
>>
>>
>> --
>>
>>
>> _______________________________________________
>> 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
>>
>>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/031b9397/attachment.html>

From cory.quammen at kitware.com  Thu Jul 23 11:05:33 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 23 Jul 2015 11:05:33 -0400
Subject: [Paraview] PV 4.10 plot over line using mesh coordinates
In-Reply-To: <CAMaOp+H4SMCmjRU6aKBJ30qErQN5bH9HAHFesb2ib_U7JLx_Dw@mail.gmail.com>
References: <55AE09A1.8040504@inria.fr>
 <CAB5Fpx42_RN0LJt=zVHWvSvD3_qXGiCdTHwBLJvdSs9-xS4NDQ@mail.gmail.com>
 <CAMaOp+H4SMCmjRU6aKBJ30qErQN5bH9HAHFesb2ib_U7JLx_Dw@mail.gmail.com>
Message-ID: <CAB5Fpx75Acgxh6v_BxD98mNTdU6m1i33-wGFvno4Tr4HNYfOcw@mail.gmail.com>

Stephen,

Andy is right, that should work, but it isn't as straightforward as placing
two end points. Instead, you'll need to define the line as the intersection
of two planes, one of which is the plane used to extract the Slice and the
other is the plane from Plot on Intersections Curve. You'll need to
intersect these planes along the line you want to query.

HTH,
Cory

On Thu, Jul 23, 2015 at 10:40 AM, Andy Bauer <andy.bauer at kitware.com> wrote:

> I think you may be able to get what you want if you first do a Slice
> through your domain (for 3D only) and then do a Plot on Intersections Curve.
>
> On Thu, Jul 23, 2015 at 9:51 AM, Cory Quammen <cory.quammen at kitware.com>
> wrote:
>
>> Hi Stephen,
>>
>> To my knowledge there is no filter in ParaView to do what you are asking.
>> For an unstructured grid, it seems to me that no matter where the sample
>> points are on the line, you are going to need some kind of interpolation at
>> cell faces and edges where the line intersects the mesh structure to get
>> the data values to plot. For structured grids, you might be able to plot
>> values along a 1D subset of the mesh with some work, but not using the Plot
>> Over Line filter.
>>
>> Thanks,
>> Cory
>>
>> On Tue, Jul 21, 2015 at 4:58 AM, Stephen Wornom <stephen.wornom at inria.fr>
>> wrote:
>>
>>> One of the inputs to Plot over line  is the number of points (equally
>>> spaced, I assumed).
>>> The solution is interpolated to the points. This poses a problem for
>>> highly stretched meshes like the normal coordinate in a boundary layer.
>>>
>>> I would like to plot over line using the actual mesh values and NOT the
>>> interpolated values.
>>> Is this possible in PV?
>>>
>>> How do I extract a line using the filters? That would be useful.
>>>
>>> Hope my questions are clear,
>>> Stephen
>>>
>>>
>>> --
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>>
>> _______________________________________________
>> 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
>>
>>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/c1ca288a/attachment.html>

From Patrick.Brockmann at lsce.ipsl.fr  Thu Jul 23 11:19:09 2015
From: Patrick.Brockmann at lsce.ipsl.fr (Patrick Brockmann)
Date: Thu, 23 Jul 2015 17:19:09 +0200
Subject: [Paraview] Translucent Rendering  Options
Message-ID: <55B105ED.7030501@lsce.ipsl.fr>

Hi,

Is it possible to render polydata cells without any depth consideration 
when they are rendered with opacity ?

The attached image shows the problem.
The different cells (made from cap of sphere sources) intersect on some 
planes. That is correct.
But I would like to render the cells without this problem of 
intersection of planes by setting some opacity.
So what ever the position of 2 cells, if one is above or bellow or 
intersect the other one, I will see the overlap
  (the information I am looking for actually) from the "addition" of the 
color.
Is it clear ?

I have tried different settings from the Render View on the Translucent 
Rendring Options but without success.

Any idea ?

You can find the vtk file example from 
http://dods.ipsl.jussieu.fr/brocksce/tmp/disk.vtk

Thanks
Patrick

-- 
LSCE/IPSL, Laboratoire CEA-CNRS-UVSQ
Data Analysis and Visualization Engineer
ICMC - IPSL Climate Modelling Centre
--

-------------- next part --------------
A non-text attachment was scrubbed...
Name: disk_05.png
Type: image/png
Size: 313017 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/ff08b1ff/attachment-0001.png>

From S.R.Kharche at exeter.ac.uk  Thu Jul 23 11:44:07 2015
From: S.R.Kharche at exeter.ac.uk (Kharche, Sanjay)
Date: Thu, 23 Jul 2015 15:44:07 +0000
Subject: [Paraview] non-interactive viz on cluster
In-Reply-To: <CANjZAi-NEtA9gUL-UXGyW87PCWpAFd2qAzhc-2gLDmxBmK+qHA@mail.gmail.com>
References: <mocupi$4m1$1@ger.gmane.org>
 <VI1PR03MB10718AA847D1243BC64882FD82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi8Cf76WG94RxsF=BytrX-03xRG70s2-eGpAX0mzAmTHfQ@mail.gmail.com>
 <VI1PR03MB107148468CDDC0E8ABA82C2E82870@VI1PR03MB1071.eurprd03.prod.outlook.com>,
 <CANjZAi-NEtA9gUL-UXGyW87PCWpAFd2qAzhc-2gLDmxBmK+qHA@mail.gmail.com>
Message-ID: <DB5PR03MB1062F8ED89F963E50A4CD20C82820@DB5PR03MB1062.eurprd03.prod.outlook.com>


Dear All


I found that I can use VNC server (and which is available to me on my current machine) with the offscreen rendering options to paraview.


VNC server seems to be a proprietary software. Are there free options available?


cheers

Sanjay



________________________________
From: David E DeMarle <dave.demarle at kitware.com>
Sent: 19 July 2015 13:46
To: Kharche, Sanjay
Cc: paraview at paraview.org
Subject: Re: [Paraview] non-interactive viz on cluster

I am not wanting to do the visualisation using the PBS -X option, which

will forward the X11 graphics from the compute mnodes to my desktop screen.

I want to do it completely non-interactively.

Agreed. Don't forward X, N compute nodes sending their graphics calls over the network to your desktop is much worse than N times slower.


I could not find any other way of

changing the DISPLAY variable. If there is one, please suggest.


I think it is site specific. Talk with your sys admins about how to submit a job that has access to X displays on the compute nodes.


In the meantime, I am trying to find out of the paraview on our cluster is

compiled to use off screen rendering. I will also try to have a go at using

some precompiled binaries (pvbatch) if I can find any.


Sounds like a good backup plan. If that fails, you can compile paraview for offscreen rendering yourself and run your own binary.


cheers

Sanjay


good luck!


________________________________
From: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>
Sent: 18 July 2015 02:08
To: Kharche, Sanjay
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] non-interactive viz on cluster


The error message indicates that pv batch can not connect the xwindows.
If the cluster is configured to run X for you, ensure that the job has the correct DISPLAY environment variable.
If not, you should either start X in the job ("xinit pvbatch" or something like that) or recompile paraview to use offscreen rendering.


On Saturday, July 18, 2015, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk<mailto:S.R.Kharche at exeter.ac.uk>> wrote:

Dear All

I need to non-interactively make png images of a series of sequentially
numbered vts/vtk files. Since this is a large amount of data, I would like
to do this using a cluster. The cluster has paraview and OpenFoam. I am not
very familiar with OpenFoam, and have just started using Paraview in
terms of python scripts. When I submit the job, I get an error. I gather
that the error is because there is always a blank Paraview OpenGL window
that opens when I use the script below. Can someone suggest a solution?

thanks
Sanjay

error from the pbs job:
ERROR: In /home/kitware/Kitware/ParaView-3.10/source/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 541
vtkXOpenGLRenderWindow (0x1ba5ad0): bad X server connection. DISPLAY=ERROR: In /home/kitware/Kitware/ParaView-3.10/source/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 343
vtkXOpenGLRenderWindow (0x1ba5ad0): bad X server connection. DISPLAY=

My python script that I created using the GUI, and then edited for writing the png is below. I run it using the
non screen rendering option:

pvbatch --use-offscreen-rendering mouse2d.py &

mouse2d.py is this:

try: paraview.simple
except: from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()

# this does not make a difference to the viz.
# SetActiveView(GetRenderView())
# GetActiveView().UseOffscreenRenderingForScreenshots = 1

# loop through all files.
for i in range (1,3999):
        mouse2D_SAN1_vts = XMLStructuredGridReader( FileName=['mouse2D_SAN%d.vts' % (i)] )
        mouse2D_SAN1_vts.PointArrayStatus = ['Unnamed0']
        RenderView1 = GetRenderView()
        DataRepresentation1 = Show()
        DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
        RenderView1.CenterOfRotation = [78.0, 58.5, 0.0]
        Transform1 = Transform( Transform="Transform" )
        a1_Unnamed0_PVLookupTable = GetLookupTableForArray( "Unnamed0", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[-0.01, 0.23, 0.299, 0.754, 1.0, 0.706, 0.016, 0.15], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
        a1_Unnamed0_PiecewiseFunction = CreatePiecewiseFunction()
        RenderView1.CameraPosition = [78.0, 58.5, 376.71107225273664]
        RenderView1.CameraFocalPoint = [78.0, 58.5, 0.0]
        RenderView1.CameraClippingRange = [372.94396153020926, 382.3617383365277]
        RenderView1.CameraParallelScale = 97.5
        DataRepresentation1.ColorArrayName = 'Unnamed0'
        DataRepresentation1.LookupTable = a1_Unnamed0_PVLookupTable
        Transform1.Transform = "Transform"
        DataRepresentation2 = Show()
        DataRepresentation2.ColorArrayName = 'Unnamed0'
        DataRepresentation2.LookupTable = a1_Unnamed0_PVLookupTable
        DataRepresentation2.EdgeColor = [0.0, 0.0, 0.5000076295109483]
        DataRepresentation1.Visibility = 0

        Transform1.Transform.Scale = [1.0, -1.0, 0.0]
        RenderView1.CenterAxesVisibility = 0
        RenderView1.CameraPosition = [78.0, -58.5, 376.71107225273664]
        RenderView1.OrientationAxesVisibility = 0
        RenderView1.CameraFocalPoint = [78.0, -58.5, 0.0]
        RenderView1.CenterOfRotation = [78.0, -58.5, 0.0]
#       Render()
        WriteImage("dir_%i.png" % (i))
_______________________________________________
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


--
David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909<tel:518-881-4909>

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

From yves.rogez at obs.ujf-grenoble.fr  Thu Jul 23 11:55:07 2015
From: yves.rogez at obs.ujf-grenoble.fr (Yves Rogez)
Date: Thu, 23 Jul 2015 17:55:07 +0200
Subject: [Paraview] non-interactive viz on cluster
In-Reply-To: <DB5PR03MB1062F8ED89F963E50A4CD20C82820@DB5PR03MB1062.eurprd03.prod.outlook.com>
References: <mocupi$4m1$1@ger.gmane.org>
 <VI1PR03MB10718AA847D1243BC64882FD82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi8Cf76WG94RxsF=BytrX-03xRG70s2-eGpAX0mzAmTHfQ@mail.gmail.com>
 <VI1PR03MB107148468CDDC0E8ABA82C2E82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi-NEtA9gUL-UXGyW87PCWpAFd2qAzhc-2gLDmxBmK+qHA@mail.gmail.com>
 <DB5PR03MB1062F8ED89F963E50A4CD20C82820@DB5PR03MB1062.eurprd03.prod.outlook.com>
Message-ID: <55B10E5B.7090003@obs.ujf-grenoble.fr>

Hi Patrick,

have you tried to just get rid of the depth peeling ?
(Settings -> Render view tab -> Advanced mode -> Uncheck the depth 
peeling box) and set an opacity < 1.0 on the object.

Cheers,

Yves

Le 23/07/2015 17:44, Kharche, Sanjay a ?crit :
>
>
> Dear All
>
>
> I found that I can use VNC server (and which is available to me on my 
> current machine) with the offscreen rendering options to paraview.
>
>
> VNC server seems to be a proprietary software. Are there free options 
> available?
>
>
> cheers
>
> Sanjay
>
>
>
>
> ------------------------------------------------------------------------
> *From:* David E DeMarle <dave.demarle at kitware.com>
> *Sent:* 19 July 2015 13:46
> *To:* Kharche, Sanjay
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] non-interactive viz on cluster
> I am not wanting to do the visualisation using the PBS -X option, which
>
>     will forward the X11 graphics from the compute mnodes to my
>     desktop screen.
>
>     I want to do it completely non-interactively.
>
>
> Agreed. Don't forward X, N compute nodes sending their graphics calls 
> over the network to your desktop is much worse than N times slower.
>
>     I could not find any other way of
>
>     changing the DISPLAY variable. If there is one, please suggest.
>
>
> I think it is site specific. Talk with your sys admins about how to 
> submit a job that has access to X displays on the compute nodes.
>
>     In the meantime, I am trying to find out of the paraview on our
>     cluster is
>
>     compiled to use off screen rendering. I will also try to have a go
>     at using
>
>     some precompiled binaries (pvbatch) if I can find any.
>
>
> Sounds like a good backup plan. If that fails, you can compile 
> paraview for offscreen rendering yourself and run your own binary.
>
>     cheers
>
>     Sanjay
>
>
>
> good luck!
>
>
>     ------------------------------------------------------------------------
>     *From:* David E DeMarle <dave.demarle at kitware.com
>     <mailto:dave.demarle at kitware.com>>
>     *Sent:* 18 July 2015 02:08
>     *To:* Kharche, Sanjay
>     *Cc:* paraview at paraview.org <mailto:paraview at paraview.org>
>     *Subject:* Re: [Paraview] non-interactive viz on cluster
>
>     The error message indicates that pv batch can not connect the
>     xwindows.
>     If the cluster is configured to run X for you, ensure that the job
>     has the correct DISPLAY environment variable.
>     If not, you should either start X in the job ("xinit pvbatch" or
>     something like that) or recompile paraview to use offscreen rendering.
>
>
>     On Saturday, July 18, 2015, Kharche, Sanjay
>     <S.R.Kharche at exeter.ac.uk <mailto:S.R.Kharche at exeter.ac.uk>> wrote:
>
>
>         Dear All
>
>         I need to non-interactively make png images of a series of
>         sequentially
>         numbered vts/vtk files. Since this is a large amount of data,
>         I would like
>         to do this using a cluster. The cluster has paraview and
>         OpenFoam. I am not
>         very familiar with OpenFoam, and have just started using
>         Paraview in
>         terms of python scripts. When I submit the job, I get an
>         error. I gather
>         that the error is because there is always a blank Paraview
>         OpenGL window
>         that opens when I use the script below. Can someone suggest a
>         solution?
>
>         thanks
>         Sanjay
>
>         error from the pbs job:
>         ERROR: In
>         /home/kitware/Kitware/ParaView-3.10/source/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
>         line 541
>         vtkXOpenGLRenderWindow (0x1ba5ad0): bad X server connection.
>         DISPLAY=ERROR: In
>         /home/kitware/Kitware/ParaView-3.10/source/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
>         line 343
>         vtkXOpenGLRenderWindow (0x1ba5ad0): bad X server connection.
>         DISPLAY=
>
>         My python script that I created using the GUI, and then edited
>         for writing the png is below. I run it using the
>         non screen rendering option:
>
>         pvbatch --use-offscreen-rendering mouse2d.py &
>
>         mouse2d.py is this:
>
>         try: paraview.simple
>         except: from paraview.simple import *
>         paraview.simple._DisableFirstRenderCameraReset()
>
>         # this does not make a difference to the viz.
>         # SetActiveView(GetRenderView())
>         # GetActiveView().UseOffscreenRenderingForScreenshots = 1
>
>         # loop through all files.
>         for i in range (1,3999):
>                 mouse2D_SAN1_vts = XMLStructuredGridReader(
>         FileName=['mouse2D_SAN%d.vts' % (i)] )
>         mouse2D_SAN1_vts.PointArrayStatus = ['Unnamed0']
>                 RenderView1 = GetRenderView()
>                 DataRepresentation1 = Show()
>         DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
>                 RenderView1.CenterOfRotation = [78.0, 58.5, 0.0]
>                 Transform1 = Transform( Transform="Transform" )
>                 a1_Unnamed0_PVLookupTable = GetLookupTableForArray(
>         "Unnamed0", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[-0.01,
>         0.23, 0.299, 0.754, 1.0, 0.706, 0.016, 0.15],
>         VectorMode='Magnitude', ColorSpace='Diverging',
>         LockScalarRange=1 )
>         a1_Unnamed0_PiecewiseFunction = CreatePiecewiseFunction()
>                 RenderView1.CameraPosition = [78.0, 58.5,
>         376.71107225273664]
>                 RenderView1.CameraFocalPoint = [78.0, 58.5, 0.0]
>         RenderView1.CameraClippingRange = [372.94396153020926,
>         382.3617383365277]
>         RenderView1.CameraParallelScale = 97.5
>         DataRepresentation1.ColorArrayName = 'Unnamed0'
>         DataRepresentation1.LookupTable = a1_Unnamed0_PVLookupTable
>                 Transform1.Transform = "Transform"
>                 DataRepresentation2 = Show()
>         DataRepresentation2.ColorArrayName = 'Unnamed0'
>         DataRepresentation2.LookupTable = a1_Unnamed0_PVLookupTable
>         DataRepresentation2.EdgeColor = [0.0, 0.0, 0.5000076295109483]
>         DataRepresentation1.Visibility = 0
>
>                 Transform1.Transform.Scale = [1.0, -1.0, 0.0]
>         RenderView1.CenterAxesVisibility = 0
>                 RenderView1.CameraPosition = [78.0, -58.5,
>         376.71107225273664]
>         RenderView1.OrientationAxesVisibility = 0
>                 RenderView1.CameraFocalPoint = [78.0, -58.5, 0.0]
>                 RenderView1.CenterOfRotation = [78.0, -58.5, 0.0]
>         #       Render()
>                 WriteImage("dir_%i.png" % (i))
>         _______________________________________________
>         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
>         <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
>
>
>
>     -- 
>     David E DeMarle
>     Kitware, Inc.
>     R&D Engineer
>     21 Corporate Drive
>     Clifton Park, NY 12065-8662
>     Phone: 518-881-4909 <tel:518-881-4909>
>
>
>
>
> _______________________________________________
> 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

-- 
Yves Rogez
/CONSERT Operations Engineer/

*IPAG*
/Institut de Plan?tologie et d'Astrophysique de Grenoble /
Bat D de Physique - BP. 53 - 38041 Grenoble - FRANCE

tel : +33 (0)4 76 63 52 80
lab : +33 (0)4 76 63 57 60
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/333b0c8a/attachment.html>

From yves.rogez at obs.ujf-grenoble.fr  Thu Jul 23 11:55:48 2015
From: yves.rogez at obs.ujf-grenoble.fr (Yves Rogez)
Date: Thu, 23 Jul 2015 17:55:48 +0200
Subject: [Paraview] Translucent Rendering Options
In-Reply-To: <55B105ED.7030501@lsce.ipsl.fr>
References: <55B105ED.7030501@lsce.ipsl.fr>
Message-ID: <55B10E84.80405@obs.ujf-grenoble.fr>

Hi Patrick,

have you tried to just get rid of the depth peeling ?
(Settings -> Render view tab -> Advanced mode -> Uncheck the depth 
peeling box) and set an opacity < 1.0 on the object.

Cheers,

Yves

Le 23/07/2015 17:19, Patrick Brockmann a ?crit :
> Hi,
>
> Is it possible to render polydata cells without any depth 
> consideration when they are rendered with opacity ?
>
> The attached image shows the problem.
> The different cells (made from cap of sphere sources) intersect on 
> some planes. That is correct.
> But I would like to render the cells without this problem of 
> intersection of planes by setting some opacity.
> So what ever the position of 2 cells, if one is above or bellow or 
> intersect the other one, I will see the overlap
>  (the information I am looking for actually) from the "addition" of 
> the color.
> Is it clear ?
>
> I have tried different settings from the Render View on the 
> Translucent Rendring Options but without success.
>
> Any idea ?
>
> You can find the vtk file example from 
> http://dods.ipsl.jussieu.fr/brocksce/tmp/disk.vtk
>
> Thanks
> Patrick
>
>
>
> _______________________________________________
> 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

-- 
Yves Rogez
/CONSERT Operations Engineer/

*IPAG*
/Institut de Plan?tologie et d'Astrophysique de Grenoble /
Bat D de Physique - BP. 53 - 38041 Grenoble - FRANCE

tel : +33 (0)4 76 63 52 80
lab : +33 (0)4 76 63 57 60
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/f561172d/attachment.html>

From Patrick.Brockmann at lsce.ipsl.fr  Thu Jul 23 11:57:07 2015
From: Patrick.Brockmann at lsce.ipsl.fr (Patrick Brockmann)
Date: Thu, 23 Jul 2015 17:57:07 +0200
Subject: [Paraview] Translucent Rendering Options
In-Reply-To: <55B10E84.80405@obs.ujf-grenoble.fr>
References: <55B105ED.7030501@lsce.ipsl.fr>
 <55B10E84.80405@obs.ujf-grenoble.fr>
Message-ID: <55B10ED3.20006@lsce.ipsl.fr>

On 23/07/2015 17:55, Yves Rogez wrote:
> Hi Patrick,
>
> have you tried to just get rid of the depth peeling ?
> (Settings -> Render view tab -> Advanced mode -> Uncheck the depth 
> peeling box) and set an opacity < 1.0 on the object.

Hi,
Thank for the suggestion.
Yes, I have tried this but nothing has changed.
Is it the case for you ?

Patrick

-- 
LSCE/IPSL, Laboratoire CEA-CNRS-UVSQ
Data Analysis and Visualization Engineer
ICMC - IPSL Climate Modelling Centre
--

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

From dave.demarle at kitware.com  Thu Jul 23 12:01:33 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 23 Jul 2015 12:01:33 -0400
Subject: [Paraview] non-interactive viz on cluster
In-Reply-To: <DB5PR03MB1062F8ED89F963E50A4CD20C82820@DB5PR03MB1062.eurprd03.prod.outlook.com>
References: <mocupi$4m1$1@ger.gmane.org>
 <VI1PR03MB10718AA847D1243BC64882FD82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi8Cf76WG94RxsF=BytrX-03xRG70s2-eGpAX0mzAmTHfQ@mail.gmail.com>
 <VI1PR03MB107148468CDDC0E8ABA82C2E82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi-NEtA9gUL-UXGyW87PCWpAFd2qAzhc-2gLDmxBmK+qHA@mail.gmail.com>
 <DB5PR03MB1062F8ED89F963E50A4CD20C82820@DB5PR03MB1062.eurprd03.prod.outlook.com>
Message-ID: <CANjZAi_VRp_+_Xe0g9e8X3025HijeEtEWRNgckGmYChzvKnjHg@mail.gmail.com>

There are free and open source VNC servers. Check your system's package
lists first.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Thu, Jul 23, 2015 at 11:44 AM, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk>
wrote:

>
>  Dear All
>
>
>  I found that I can use VNC server (and which is available to me on my
> current machine) with the offscreen rendering options to paraview.
>
>
>  VNC server seems to be a proprietary software. Are there free options
> available?
>
>
>  cheers
>
> Sanjay
>
>
>
>
>  ------------------------------
> *From:* David E DeMarle <dave.demarle at kitware.com>
> *Sent:* 19 July 2015 13:46
>
> *To:* Kharche, Sanjay
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] non-interactive viz on cluster
>
>  I am not wanting to do the visualisation using the PBS -X option, which
>
>>  will forward the X11 graphics from the compute mnodes to my desktop
>> screen.
>>
>> I want to do it completely non-interactively.
>>
>
>  Agreed. Don't forward X, N compute nodes sending their graphics calls
> over the network to your desktop is much worse than N times slower.
>
>   I could not find any other way of
>>
>> changing the DISPLAY variable. If there is one, please suggest.
>>
>>
>>   I think it is site specific. Talk with your sys admins about how to
> submit a job that has access to X displays on the compute nodes.
>
>
>>   In the meantime, I am trying to find out of the paraview on our
>> cluster is
>>
>> compiled to use off screen rendering. I will also try to have a go at
>> using
>>
>> some precompiled binaries (pvbatch) if I can find any.
>>
>>
>>   Sounds like a good backup plan. If that fails, you can compile
> paraview for offscreen rendering yourself and run your own binary.
>
>
>>   cheers
>>
>> Sanjay
>>
>>
>  good luck!
>
>
>>
>>  ------------------------------
>> *From:* David E DeMarle <dave.demarle at kitware.com>
>> *Sent:* 18 July 2015 02:08
>> *To:* Kharche, Sanjay
>> *Cc:* paraview at paraview.org
>> *Subject:* Re: [Paraview] non-interactive viz on cluster
>>
>>
>> The error message indicates that pv batch can not connect the xwindows.
>> If the cluster is configured to run X for you, ensure that the job has
>> the correct DISPLAY environment variable.
>> If not, you should either start X in the job ("xinit pvbatch" or
>> something like that) or recompile paraview to use offscreen rendering.
>>
>>
>> On Saturday, July 18, 2015, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk>
>> wrote:
>>
>>>
>>> Dear All
>>>
>>> I need to non-interactively make png images of a series of sequentially
>>> numbered vts/vtk files. Since this is a large amount of data, I would
>>> like
>>> to do this using a cluster. The cluster has paraview and OpenFoam. I am
>>> not
>>> very familiar with OpenFoam, and have just started using Paraview in
>>> terms of python scripts. When I submit the job, I get an error. I gather
>>> that the error is because there is always a blank Paraview OpenGL window
>>> that opens when I use the script below. Can someone suggest a solution?
>>>
>>> thanks
>>> Sanjay
>>>
>>> error from the pbs job:
>>> ERROR: In
>>> /home/kitware/Kitware/ParaView-3.10/source/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
>>> line 541
>>> vtkXOpenGLRenderWindow (0x1ba5ad0): bad X server connection.
>>> DISPLAY=ERROR: In
>>> /home/kitware/Kitware/ParaView-3.10/source/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
>>> line 343
>>> vtkXOpenGLRenderWindow (0x1ba5ad0): bad X server connection. DISPLAY=
>>>
>>> My python script that I created using the GUI, and then edited for
>>> writing the png is below. I run it using the
>>> non screen rendering option:
>>>
>>> pvbatch --use-offscreen-rendering mouse2d.py &
>>>
>>> mouse2d.py is this:
>>>
>>> try: paraview.simple
>>> except: from paraview.simple import *
>>> paraview.simple._DisableFirstRenderCameraReset()
>>>
>>> # this does not make a difference to the viz.
>>> # SetActiveView(GetRenderView())
>>> # GetActiveView().UseOffscreenRenderingForScreenshots = 1
>>>
>>> # loop through all files.
>>> for i in range (1,3999):
>>>         mouse2D_SAN1_vts = XMLStructuredGridReader(
>>> FileName=['mouse2D_SAN%d.vts' % (i)] )
>>>         mouse2D_SAN1_vts.PointArrayStatus = ['Unnamed0']
>>>         RenderView1 = GetRenderView()
>>>         DataRepresentation1 = Show()
>>>         DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
>>>         RenderView1.CenterOfRotation = [78.0, 58.5, 0.0]
>>>         Transform1 = Transform( Transform="Transform" )
>>>         a1_Unnamed0_PVLookupTable = GetLookupTableForArray( "Unnamed0",
>>> 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[-0.01, 0.23, 0.299, 0.754, 1.0,
>>> 0.706, 0.016, 0.15], VectorMode='Magnitude', ColorSpace='Diverging',
>>> LockScalarRange=1 )
>>>         a1_Unnamed0_PiecewiseFunction = CreatePiecewiseFunction()
>>>         RenderView1.CameraPosition = [78.0, 58.5, 376.71107225273664]
>>>         RenderView1.CameraFocalPoint = [78.0, 58.5, 0.0]
>>>         RenderView1.CameraClippingRange = [372.94396153020926,
>>> 382.3617383365277]
>>>         RenderView1.CameraParallelScale = 97.5
>>>         DataRepresentation1.ColorArrayName = 'Unnamed0'
>>>         DataRepresentation1.LookupTable = a1_Unnamed0_PVLookupTable
>>>         Transform1.Transform = "Transform"
>>>         DataRepresentation2 = Show()
>>>         DataRepresentation2.ColorArrayName = 'Unnamed0'
>>>         DataRepresentation2.LookupTable = a1_Unnamed0_PVLookupTable
>>>         DataRepresentation2.EdgeColor = [0.0, 0.0, 0.5000076295109483]
>>>         DataRepresentation1.Visibility = 0
>>>
>>>         Transform1.Transform.Scale = [1.0, -1.0, 0.0]
>>>         RenderView1.CenterAxesVisibility = 0
>>>         RenderView1.CameraPosition = [78.0, -58.5, 376.71107225273664]
>>>         RenderView1.OrientationAxesVisibility = 0
>>>         RenderView1.CameraFocalPoint = [78.0, -58.5, 0.0]
>>>         RenderView1.CenterOfRotation = [78.0, -58.5, 0.0]
>>> #       Render()
>>>         WriteImage("dir_%i.png" % (i))
>>> _______________________________________________
>>> 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
>>>
>>
>>
>> --
>> David E DeMarle
>> Kitware, Inc.
>> R&D Engineer
>> 21 Corporate Drive
>> Clifton Park, NY 12065-8662
>> Phone: 518-881-4909
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/cd9662e0/attachment.html>

From yves.rogez at obs.ujf-grenoble.fr  Thu Jul 23 12:02:17 2015
From: yves.rogez at obs.ujf-grenoble.fr (Yves Rogez)
Date: Thu, 23 Jul 2015 18:02:17 +0200
Subject: [Paraview] Translucent Rendering Options
In-Reply-To: <55B10ED3.20006@lsce.ipsl.fr>
References: <55B105ED.7030501@lsce.ipsl.fr>
 <55B10E84.80405@obs.ujf-grenoble.fr> <55B10ED3.20006@lsce.ipsl.fr>
Message-ID: <55B11009.9080109@obs.ujf-grenoble.fr>

Yes on paraview 4.3.1 at least:


Le 23/07/2015 17:57, Patrick Brockmann a ?crit :
> On 23/07/2015 17:55, Yves Rogez wrote:
>> Hi Patrick,
>>
>> have you tried to just get rid of the depth peeling ?
>> (Settings -> Render view tab -> Advanced mode -> Uncheck the depth 
>> peeling box) and set an opacity < 1.0 on the object.
>
> Hi,
> Thank for the suggestion.
> Yes, I have tried this but nothing has changed.
> Is it the case for you ?
>
> Patrick
> -- 
> LSCE/IPSL, Laboratoire CEA-CNRS-UVSQ
> Data Analysis and Visualization Engineer
> ICMC - IPSL Climate Modelling Centre
> --

-- 
Yves Rogez
/CONSERT Operations Engineer/

*IPAG*
/Institut de Plan?tologie et d'Astrophysique de Grenoble /
Bat D de Physique - BP. 53 - 38041 Grenoble - FRANCE

tel : +33 (0)4 76 63 52 80
lab : +33 (0)4 76 63 57 60
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/9cb3451d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gijjjchc.png
Type: image/png
Size: 283525 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/9cb3451d/attachment-0001.png>

From deq11009 at fe.up.pt  Thu Jul 23 12:02:25 2015
From: deq11009 at fe.up.pt (deq11009)
Date: Thu, 23 Jul 2015 17:02:25 +0100
Subject: [Paraview] Wrong fetched data
In-Reply-To: <CAB5Fpx6LdnmmsxJ+epj_vSsee7hqQaiais6QHKq9_MP9oiVdpw@mail.gmail.com>
References: <5000545d13da0baa4fa1c3d1e3c44423@fe.up.pt>
 <CAB5Fpx5xsoTOeBdtEGLBMEDVG5YonkPb5maRPKVpCbbYCJzeGA@mail.gmail.com>
 <f79e260d16a28fb08f353b8626184dee@fe.up.pt>
 <CAB5Fpx4zX0FND+bOdu24oHCnMfzLwgoNbPdp8jQQLhkRw_0UuQ@mail.gmail.com>
 <d9d613d6842a39d844e9fc3b6f63369a@fe.up.pt>
 <CAB5Fpx6LdnmmsxJ+epj_vSsee7hqQaiais6QHKq9_MP9oiVdpw@mail.gmail.com>
Message-ID: <39111a445852eb6fd79787826e7b8ad0@fe.up.pt>

Hi Cory,

The new file: http://we.tl/BLMGe1eHKA

Thanks,
Filipe Direito



On 23.07.2015 15:54, Cory Quammen wrote:
> Hi Filipe,
>
> I apologize that I have not had time to look into your data, and now
> the file you posted on wetransfer.com [31] is no longer available.
> Would you be able to post it?
>
> Thanks,
> Cory
>
> On Mon, Jul 13, 2015 at 12:40 PM, deq11009 <deq11009 at fe.up.pt [32]>
> wrote:
>
>> Hi,
>>
>> I can share the following: http://we.tl/3CPwe5y9vA [25]
>> An easy way to see the problem might be creating a line source in
>> the axis of the cylinder, doing Resample and see where interface is
>> located.
>>
>> Thanks,
>> Filipe Direito
>>
>> On 13.07.2015 04:33, Cory Quammen wrote:
>>
>>> Interesting. Is is possible for you to share the data file(s)?
>>>
>>> Thanks,
>>> Cory
>>>
>>> On Mon, Jul 6, 2015 at 10:23 AM, deq11009 <deq11009 at fe.up.pt [12]
>>> [12]>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Thank you for your reply.
>>>>
>>>> No, the mistake is not there. In the meantime I did realize
>>>> what is
>>>> exactly happening.
>>>>
>>>> I have, say, 200 timesteps.
>>>> From 0 to 6, data obtained from my code matches the data when I
>>>> just use the GUI.
>>>> Starting in timestep 7 (always) till the end, data (for all
>>>> timesteps) is the data from the last timestep.
>>>> So, when in python shell I go to timestep 6, I see timestep 6.
>>>> But
>>>> when I go to timestep 7, or 100, or 133, I see timestep 199. At
>>>> the
>>>> same time, if I go to the GUI, everything is ok.
>>>>
>>>> By coincidence, the ".case" time step data is organized in
>>>> seven
>>>> columns. Is this related to the problem?
>>>>
>>>> Thank you
>>>> Filipe Direito
>>>>
>>>> On 03.07.2015 15:05, Cory Quammen wrote:
>>>>
>>>>> Hi Filipe,
>>>>>
>>>>> Perhaps the array at index 7 is not the array you are
>>>>> expecting?
>>>>> Could
>>>>> you access the array by name instead, .e.g.,
>>>>>
>>>>> dAxis.GetPointData().GetArray(variable_name).GetValue(150)
>>>>>
>>>>> and see if that works better?
>>>>>
>>>>> Thanks,
>>>>> Cory
>>>>>
>>>>> On Wed, Jul 1, 2015 at 1:44 PM, deq11009 <deq11009 at fe.up.pt
>>>>> [6] [6]
>>>>> [6]>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I am currently using Paraview 4.2, 64, in Windows. (but
>>>>>> tried
>>>>>> 4.3
>>>>>> and same problem happened)
>>>>>>
>>>>>> My case is Ensight transient. Cylinder with 3.6 million
>>>>>> cells,
>>>>>> two-phase flow.
>>>>>>
>>>>>> I created a python code, which I run from the shell in the
>>>>>> GUI.
>>>>>>
>>>>>> The main parts of the code are:
>>>>>>
>>>>>> enscase = EnSightReader(CaseFileName = direcp +
>>>>>> ensfinal.case)
>>>>>> ...
>>>>>> axis = Line()
>>>>>> ...
>>>>>> rAxis = ResampleWithDataset(Input = enscase , Source =
>>>>>> axis)
>>>>>> ...
>>>>>> rAxis.SMProxy.UpdatePipeline(7) # enscase.SMProxy yields
>>>>>> same
>>>>>> problem
>>>>>> rAxis.UpdatePipelineInformation()
>>>>>> dAxis = servermanager.Fetch(rAxis)
>>>>>>
>>>>>> Now, for example:
>>>>>> print dAxis.GetPointData().GetArray(7).GetValue(150)
>>>>>> which gives me the value 150 of the phase array.
>>>>>>
>>>>>> This data is wrong. On the other hand, if I go to the GUI
>>>>>> Pipeline
>>>>>> and create a Spreadsheet, the values are the real ones
>>>>>> (confirmed in
>>>>>> Fluent).
>>>>>>
>>>>>> So, the fetched data in the python shell is, for some
>>>>>> reason,
>>>>>> wrong.
>>>>>> What is my mistake?
>>>>>>
>>>>>> Thanks
>>>>>> Filipe Direito
>>>>>>
>>>>>> _______________________________________________
>>>>>> Powered by www.kitware.com [1] [1] [1]
>>>>>>
>>>>>> Visit other Kitware open-source projects at
>>>>>> http://www.kitware.com/opensource/opensource.html [2] [2]
>>>>>> [2]
>>>>>>
>>>>>> Please keep messages on-topic and check the ParaView Wiki
>>>>>> at:
>>>>>> http://paraview.org/Wiki/ParaView [3] [3] [3]
>>>>>>
>>>>>> Search the list archives at:
>>>>>> http://markmail.org/search/?q=ParaView [4] [4]
>>>>>> [4]
>>>>>>
>>>>>> Follow this link to subscribe/unsubscribe:
>>>>>> http://public.kitware.com/mailman/listinfo/paraview [5] [5]
>>>>>> [5]
>>>>
>>>> _______________________________________________
>>>> Powered by www.kitware.com [7] [7]
>>>>
>>>> Visit other Kitware open-source projects at
>>>> http://www.kitware.com/opensource/opensource.html [8] [8]
>>>>
>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>> http://paraview.org/Wiki/ParaView [9] [9]
>>>>
>>>> Search the list archives at:
>>>> http://markmail.org/search/?q=ParaView [10]
>>>> [10]
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://public.kitware.com/mailman/listinfo/paraview [11] [11]
>>>
>>> --
>>>
>>> Cory Quammen
>>> R&D Engineer
>>> Kitware, Inc.
>>>
>>> Links:
>>> ------
>>> [1] http://www.kitware.com [13]
>>> [2] http://www.kitware.com/opensource/opensource.html [14]
>>> [3] http://paraview.org/Wiki/ParaView [15]
>>> [4] http://markmail.org/search/?q=ParaView [16]
>>> [5] http://public.kitware.com/mailman/listinfo/paraview [17]
>>> [6] mailto:deq11009 at fe.up.pt [18]
>>> [7] http://www.kitware.com [19]
>>> [8] http://www.kitware.com/opensource/opensource.html [20]
>>> [9] http://paraview.org/Wiki/ParaView [21]
>>> [10] http://markmail.org/search/?q=ParaView [22]
>>> [11] http://public.kitware.com/mailman/listinfo/paraview [23]
>>> [12] mailto:deq11009 at fe.up.pt [24]
>>
>> _______________________________________________
>> Powered by www.kitware.com [26]
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html [27]
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView [28]
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>> [29]
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview [30]
>
> --
>
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
> Links:
> ------
> [1] http://www.kitware.com
> [2] http://www.kitware.com/opensource/opensource.html
> [3] http://paraview.org/Wiki/ParaView
> [4] http://markmail.org/search/?q=ParaView
> [5] http://public.kitware.com/mailman/listinfo/paraview
> [6] mailto:deq11009 at fe.up.pt
> [7] http://www.kitware.com
> [8] http://www.kitware.com/opensource/opensource.html
> [9] http://paraview.org/Wiki/ParaView
> [10] http://markmail.org/search/?q=ParaView
> [11] http://public.kitware.com/mailman/listinfo/paraview
> [12] mailto:deq11009 at fe.up.pt
> [13] http://www.kitware.com
> [14] http://www.kitware.com/opensource/opensource.html
> [15] http://paraview.org/Wiki/ParaView
> [16] http://markmail.org/search/?q=ParaView
> [17] http://public.kitware.com/mailman/listinfo/paraview
> [18] mailto:deq11009 at fe.up.pt
> [19] http://www.kitware.com
> [20] http://www.kitware.com/opensource/opensource.html
> [21] http://paraview.org/Wiki/ParaView
> [22] http://markmail.org/search/?q=ParaView
> [23] http://public.kitware.com/mailman/listinfo/paraview
> [24] mailto:deq11009 at fe.up.pt
> [25] http://we.tl/3CPwe5y9vA
> [26] http://www.kitware.com
> [27] http://www.kitware.com/opensource/opensource.html
> [28] http://paraview.org/Wiki/ParaView
> [29] http://markmail.org/search/?q=ParaView
> [30] http://public.kitware.com/mailman/listinfo/paraview
> [31] http://wetransfer.com
> [32] mailto:deq11009 at fe.up.pt


From bruce.david.jones at gmail.com  Thu Jul 23 13:36:17 2015
From: bruce.david.jones at gmail.com (Bruce Jones)
Date: Thu, 23 Jul 2015 17:36:17 +0000
Subject: [Paraview] vtkDoubleArray with >3 components
In-Reply-To: <CAEc4V-Z5A6isVG5oy7AtvxqmjzKr+zN7e+aWC3_Srn3Lf=U7qA@mail.gmail.com>
References: <CAEc4V-bvd0SRk35cuPM7Z9WhoH8WSL=7S_6kr7_Op5aOeoMN6A@mail.gmail.com>
 <CAB5Fpx6q5_K_ZJNpXtrvNhOYjZQdzGCNxvk8Eo1bvM2tFi0YVQ@mail.gmail.com>
 <CAB5Fpx5uVT5qbK7UrXnLiPhYyawDGs8v5Lj41ncEHBy2tfe1XA@mail.gmail.com>
 <CAEc4V-ZO6mB7AJgYG-zRr-kxviiYUyNtcAEsuTuNCU7=uSdfOg@mail.gmail.com>
 <CALSpCT2tWposY=qgRHzhmE7cw-k=25_2qA6Qu3DYM0sCiYjnkg@mail.gmail.com>
 <CAE32kpXPzntuoXOZRnKt_L4uPUHj9sxUchYdrC-d3OxZOyOh0g@mail.gmail.com>
 <CAEc4V-bN3jDh89hpUJtu8p5VEh8R7wEhCvF=DxPYdSPOoB4DWA@mail.gmail.com>
 <CAE32kpV=rwYxTeMjh=cme29563uavrkbaQep2QFT+1-nNskOFg@mail.gmail.com>
 <CAEc4V-bxLtZAcjaMzgHp2ZOQFecmxfC63g2aUaNCDgSi4otOZQ@mail.gmail.com>
 <CAEc4V-Z5A6isVG5oy7AtvxqmjzKr+zN7e+aWC3_Srn3Lf=U7qA@mail.gmail.com>
Message-ID: <CAEc4V-aAL7gie+6Oc4zLYbUo+Kh6BvX_nf6ME0_XHJb1-d8nTA@mail.gmail.com>

Ok the solution was embarrasingly simple... When specifying the array size
I had specified the number of tuples, where I was supposed to specify
numTuples*numComponents

Thanks for the help anyway.

Bruce

On Wed, 22 Jul 2015 at 14:28 Bruce Jones <bruce.david.jones at gmail.com>
wrote:

> Hey Guys,
>
> I have created a minimum working example (attached). This example is built
> as a paraview plugin, build environment specified below. The plugin takes
> point data as input (sample attached), and just does the memory allocation
> and creation of output arrays as I have previously described. On my
> machine, as soon as I apply the filter, paraview crashes. Commenting line
> 107 in vtkHeapCorruption.cxx allows the filter to run, but the output is
> then limited to single component arrays, where some of the input arrays
> have 3 or 9 components.
>
> QT 4.8.6, Visual Studio 2010, Built against Paraview commit SHA1
> ID: 70155c17cfe7c2f547bb25ddb859a65518896ee3
>
> On Wed, 22 Jul 2015 at 11:21 Bruce Jones <bruce.david.jones at gmail.com>
> wrote:
>
>> Thanks Berk,
>>
>> I have tried with both zero and 1 as the save argument and am getting the
>> same behavior. As before, if I comment the SetNumberOfComponents call (or
>> set number of components to 1) everything works, except I only have single
>> component arrays in the output.
>>
>> I'm going to put together a minimum working example with the issue this
>> afternoon so that I can show you guys in more detail.
>>
>> Cheers,
>> Bruce
>>
>> On Wed, 22 Jul 2015 at 11:09 Berk Geveci <berk.geveci at kitware.com> wrote:
>>
>>> The solution is in the documentation:
>>>
>>>   // This method lets the user specify data to be held by the array.  The
>>>   // array argument is a pointer to the data.  size is the size of the
>>>   // array supplied by the user.  Set save to 1 to keep the class from
>>>   // deleting the array when it cleans up or reallocates memory.  The
>>> class
>>>   // uses the actual array provided; it does not copy the data from the
>>>   // suppled array. If specified, the delete method determines how the
>>> data
>>>   // array will be deallocated. If the delete method is
>>>   // VTK_DATA_ARRAY_FREE, free() will be used. If the delete method is
>>>   // DELETE, delete[] will be used. The default is FREE.
>>>
>>> You are passing 0 for the "save" argument, which means that VTK will
>>> delete the array when the VTK array object is deleted, which would cause a
>>> double delete/free. Use 1 as the second argument of SetArray() if you are
>>> managing the memory. Also, make sure that the VTK array is not used after
>>> you free your array.
>>>
>>> Best,
>>> -berk
>>>
>>> On Wed, Jul 22, 2015 at 9:56 AM, Bruce Jones <
>>> bruce.david.jones at gmail.com> wrote:
>>>
>>>> Hi Guys,
>>>>
>>>> I have just tried it as you suggested, doing SetNumberOfComponents then
>>>> SetArray, without doing SetNumberOfTuples. Unfortunately I am still getting
>>>> the same behaviour.
>>>>
>>>> Cheers,
>>>> Bruce
>>>>
>>>> On Wed, 22 Jul 2015 at 09:44 Berk Geveci <berk.geveci at kitware.com>
>>>> wrote:
>>>>
>>>>> Actually, don't call SetNumberOfTuples() at all if you are using
>>>>> SetArray(). It will unnecessarily allocate memory if you call it before
>>>>> SetArray().
>>>>>
>>>>> -berk
>>>>>
>>>>> On Wed, Jul 22, 2015 at 9:40 AM, Shawn Waldon <
>>>>> shawn.waldon at kitware.com> wrote:
>>>>>
>>>>>> Hi Bruce,
>>>>>>
>>>>>> SetNumberOfTuples reallocates the internal datastructure of the data
>>>>>> array to be the new required size based on the new number of components and
>>>>>> number of tuples.  This (combined with trying to clean up the old data from
>>>>>> SetArray) may be causing the heap corruption you are seeing.  Try setting
>>>>>> the number of components and number of tuples before adding the data to the
>>>>>> array.
>>>>>>
>>>>>> HTH,
>>>>>> Shawn
>>>>>>
>>>>>> On Tue, Jul 21, 2015 at 1:37 PM, Bruce Jones <
>>>>>> bruce.david.jones at gmail.com> wrote:
>>>>>>
>>>>>>> Hi Cory,
>>>>>>>
>>>>>>> Sorry for the delayed response, I've hit another more serious bug
>>>>>>> which has been diverting my attention from this.
>>>>>>>
>>>>>>> Thanks for the state file, I haven't got it to work as I don't have
>>>>>>> numpy set up, but I have also got this working with 9 component arrays in
>>>>>>> paraview using a python script. However, I am now trying to port my python
>>>>>>> plugin to c++ which is where I am seeing the error.
>>>>>>>
>>>>>>> In my plugin I want to output a vtkarray for each vtkarray in the
>>>>>>> input dataset. The values in the output vtkarrays are interpolated from
>>>>>>> those in the input vtkarrays. Rather than working directly on vtkarray
>>>>>>> objects, I am allocating c++ arrays for each vtkarray, performing the
>>>>>>> interpolation, then creating vtkDoubleArrays and using SetArray to pass a
>>>>>>> pointer to my allocated c++ arrays to the output vtkarrays. The code for
>>>>>>> setting up the output vtkarrays is roughly as follows
>>>>>>>
>>>>>>>                 vtkPointData *pointData = input->GetPointData();
>>>>>>>                 vtkDataArray *dArray = pointData->GetArray(i);
>>>>>>> vtkDoubleArray *vtkDArrayAve = vtkDoubleArray::New();
>>>>>>> vtkDArrayAve->SetName(dArray->GetName());
>>>>>>> vtkDArrayAve->SetArray(dArraysAve[i],hgrid->GetTotalCells(),0);
>>>>>>> vtkDArrayAve->SetNumberOfComponents(numComponents[i]);
>>>>>>> vtkDArrayAve->SetNumberOfTuples(hgrid->GetTotalCells());
>>>>>>> output->GetPointData()->AddArray(vtkDArrayAve);
>>>>>>>
>>>>>>> dArraysAve is an array of pointers pointing to my c++ arrays
>>>>>>> hgrid->GetTotalCells() returns the number of data points for my
>>>>>>> output
>>>>>>>
>>>>>>> I also have another mode of operation for this plugin, where I
>>>>>>> perform the interpolation differently, in that function, if I make the call
>>>>>>> to SetNumberOfComponents() some heap corruption occurs and I get a segfault
>>>>>>> when I try to subsequently free my c++ arrays. Commenting out the call to
>>>>>>> SetNumberOfComponents avoids the segfault, but then I am limited to single
>>>>>>> component arrays. This is the more serious bug I mentioned, initially I
>>>>>>> figured they were unrelated, but I can't deny the number of components
>>>>>>> coincidence.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Bruce
>>>>>>>
>>>>>>> On Thu, 16 Jul 2015 at 14:41 Cory Quammen <cory.quammen at kitware.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Bruce,
>>>>>>>>
>>>>>>>> I have attached a ParaView state file with a Programmable Source
>>>>>>>> that produces a vtkPolyData with 100 random points and a point data array
>>>>>>>> with 9 components. It seems to display the various component ranges just
>>>>>>>> fine.
>>>>>>>>
>>>>>>>> Best,
>>>>>>>> Cory
>>>>>>>>
>>>>>>>> On Thu, Jul 16, 2015 at 11:14 AM, Cory Quammen <
>>>>>>>> cory.quammen at kitware.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Bruce,
>>>>>>>>>
>>>>>>>>> I haven't seen this, but ParaView may be interpreting this array
>>>>>>>>> as a tensor field. Do you have a smallish test data file that you can share
>>>>>>>>> that shows the problem?
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Cory
>>>>>>>>>
>>>>>>>>> On Sat, Jul 11, 2015 at 11:14 AM, Bruce Jones <
>>>>>>>>> bruce.david.jones at gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> I am creating vtkDoubleArrays based on averaging some input data
>>>>>>>>>> to a reduced set of points. The input data includes various vtk arrays
>>>>>>>>>> which have 1, 3 and 9 components.
>>>>>>>>>>
>>>>>>>>>> After averaging, I am writing the data to c++ arrays, and
>>>>>>>>>> creating a new vtkDoubleArray using the SetArray() function to pass the c++
>>>>>>>>>> arrays. This works fine for 1 and 3 component arrays, however for the 9
>>>>>>>>>> component arrays paraview shows that every element is set to 0.
>>>>>>>>>>
>>>>>>>>>> If I hardcode it so that 9 component arrays become 3 component
>>>>>>>>>> arrays (reading only the first 3 components from the input array), then I
>>>>>>>>>> get the correct data for the first 3 components, though I obviously need
>>>>>>>>>> the other 6 components in the end.
>>>>>>>>>>
>>>>>>>>>> Has anyone encountered this before?
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>> Bruce
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Cory Quammen
>>>>>>>>> R&D Engineer
>>>>>>>>> Kitware, Inc.
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Cory Quammen
>>>>>>>> R&D Engineer
>>>>>>>> Kitware, Inc.
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>>
>>>>>>
>>>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/4174d864/attachment.html>

From jeffrey.c.becker at nasa.gov  Thu Jul 23 13:53:14 2015
From: jeffrey.c.becker at nasa.gov (Jeff Becker)
Date: Thu, 23 Jul 2015 10:53:14 -0700
Subject: [Paraview] running parallel pvservers
Message-ID: <55B12A0A.6070106@nasa.gov>

Hi. I do "mpirun -np 4 pvserver --client-host=xxx 
--use-offscreen-rendering", and connect a ParaView client viewer. I can 
see 4 nodes in the memory inspector, but when I start a python shell in 
ParaView, and do:

from mpi4py import MPI
print MPI.COMM_WORLD.Get_size()

I get the answer 1. Shouldn't it be 4? Thanks.

-jeff



From dave.demarle at kitware.com  Thu Jul 23 13:57:00 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 23 Jul 2015 13:57:00 -0400
Subject: [Paraview] running parallel pvservers
In-Reply-To: <55B12A0A.6070106@nasa.gov>
References: <55B12A0A.6070106@nasa.gov>
Message-ID: <CANjZAi8TCHjs4dzb7epUKybRu=KjbUheJqKpRYQurqNDcxSeUA@mail.gmail.com>

pyhon shell runs on the client side.

try doing that within the python programmable filter, which runs on the
server side.



David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Thu, Jul 23, 2015 at 1:53 PM, Jeff Becker <jeffrey.c.becker at nasa.gov>
wrote:

> Hi. I do "mpirun -np 4 pvserver --client-host=xxx
> --use-offscreen-rendering", and connect a ParaView client viewer. I can see
> 4 nodes in the memory inspector, but when I start a python shell in
> ParaView, and do:
>
> from mpi4py import MPI
> print MPI.COMM_WORLD.Get_size()
>
> I get the answer 1. Shouldn't it be 4? Thanks.
>
> -jeff
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/88aa9864/attachment.html>

From jeffrey.c.becker at nasa.gov  Thu Jul 23 14:14:29 2015
From: jeffrey.c.becker at nasa.gov (Jeff Becker)
Date: Thu, 23 Jul 2015 11:14:29 -0700
Subject: [Paraview] running parallel pvservers
In-Reply-To: <CANjZAi8TCHjs4dzb7epUKybRu=KjbUheJqKpRYQurqNDcxSeUA@mail.gmail.com>
References: <55B12A0A.6070106@nasa.gov>
 <CANjZAi8TCHjs4dzb7epUKybRu=KjbUheJqKpRYQurqNDcxSeUA@mail.gmail.com>
Message-ID: <55B12F05.6070005@nasa.gov>

Hi David,

On 07/23/2015 10:57 AM, David E DeMarle wrote:
> pyhon shell runs on the client side.
>
> try doing that within the python programmable filter, which runs on 
> the server side.

Yes that works. Thanks. Now I will try to use that and follow

http://www.paraview.org/pipermail/paraview/2011-August/022421.html

to get my existing Image Data producing Python Programmable Source to 
distribute the data across the servers. Any additional advice? Thanks again.

-jeff
>
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Thu, Jul 23, 2015 at 1:53 PM, Jeff Becker 
> <jeffrey.c.becker at nasa.gov <mailto:jeffrey.c.becker at nasa.gov>> wrote:
>
>     Hi. I do "mpirun -np 4 pvserver --client-host=xxx
>     --use-offscreen-rendering", and connect a ParaView client viewer.
>     I can see 4 nodes in the memory inspector, but when I start a
>     python shell in ParaView, and do:
>
>     from mpi4py import MPI
>     print MPI.COMM_WORLD.Get_size()
>
>     I get the answer 1. Shouldn't it be 4? Thanks.
>
>     -jeff
>
>
>     _______________________________________________
>     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
>
>

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

From dave.demarle at kitware.com  Thu Jul 23 14:18:32 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 23 Jul 2015 14:18:32 -0400
Subject: [Paraview] running parallel pvservers
In-Reply-To: <55B12F05.6070005@nasa.gov>
References: <55B12A0A.6070106@nasa.gov>
 <CANjZAi8TCHjs4dzb7epUKybRu=KjbUheJqKpRYQurqNDcxSeUA@mail.gmail.com>
 <55B12F05.6070005@nasa.gov>
Message-ID: <CANjZAi-2kECbCfGX1kYp12Rfa5rH2PYAPyVZy-sEMmJ_KsxAOA@mail.gmail.com>

Excellent.

No advice yet. Anyone have a worked out example ready? If so, post it to
the wiki please.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Thu, Jul 23, 2015 at 2:14 PM, Jeff Becker <jeffrey.c.becker at nasa.gov>
wrote:

>  Hi David,
>
> On 07/23/2015 10:57 AM, David E DeMarle wrote:
>
> pyhon shell runs on the client side.
>
>  try doing that within the python programmable filter, which runs on the
> server side.
>
>
> Yes that works. Thanks. Now I will try to use that and follow
>
> http://www.paraview.org/pipermail/paraview/2011-August/022421.html
>
> to get my existing Image Data producing Python Programmable Source to
> distribute the data across the servers. Any additional advice? Thanks again.
>
> -jeff
>
>
>
>
>  David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Thu, Jul 23, 2015 at 1:53 PM, Jeff Becker <jeffrey.c.becker at nasa.gov>
> wrote:
>
>> Hi. I do "mpirun -np 4 pvserver --client-host=xxx
>> --use-offscreen-rendering", and connect a ParaView client viewer. I can see
>> 4 nodes in the memory inspector, but when I start a python shell in
>> ParaView, and do:
>>
>> from mpi4py import MPI
>> print MPI.COMM_WORLD.Get_size()
>>
>> I get the answer 1. Shouldn't it be 4? Thanks.
>>
>> -jeff
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/74caeb7d/attachment.html>

From jeffrey.c.becker at nasa.gov  Thu Jul 23 17:43:20 2015
From: jeffrey.c.becker at nasa.gov (Jeff Becker)
Date: Thu, 23 Jul 2015 14:43:20 -0700
Subject: [Paraview] running parallel pvservers
In-Reply-To: <CANjZAi-2kECbCfGX1kYp12Rfa5rH2PYAPyVZy-sEMmJ_KsxAOA@mail.gmail.com>
References: <55B12A0A.6070106@nasa.gov>
 <CANjZAi8TCHjs4dzb7epUKybRu=KjbUheJqKpRYQurqNDcxSeUA@mail.gmail.com>
 <55B12F05.6070005@nasa.gov>
 <CANjZAi-2kECbCfGX1kYp12Rfa5rH2PYAPyVZy-sEMmJ_KsxAOA@mail.gmail.com>
Message-ID: <55B15FF8.40306@nasa.gov>

In the e-mail thread quoted below, it says:

>>>/  Note also that there is a "feature" in the python programmable filter
/>>>/  that comes into play with structured data. That feature says that
/>>>/  structured data is not split at all by default. If you want structured
/>>>/  data to actually be parallel you need to put this code in your python
/>>>/  programmable filter.
/>>>/
/>>>/  from paraview import util
/>>>/
/>>>/  self.GetExecutive().SetExtentTranslator(self.GetExecutive().GetOutputInformation(0),
/>>>/  vtk.vtkExtentTranslator())/


Is this still the case, and if so, how does this translate to VTK 6? Thanks.

-jeff


On 07/23/2015 11:18 AM, David E DeMarle wrote:
> Excellent.
>
> No advice yet. Anyone have a worked out example ready? If so, post it 
> to the wiki please.
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Thu, Jul 23, 2015 at 2:14 PM, Jeff Becker 
> <jeffrey.c.becker at nasa.gov <mailto:jeffrey.c.becker at nasa.gov>> wrote:
>
>     Hi David,
>
>     On 07/23/2015 10:57 AM, David E DeMarle wrote:
>>     pyhon shell runs on the client side.
>>
>>     try doing that within the python programmable filter, which runs
>>     on the server side.
>
>     Yes that works. Thanks. Now I will try to use that and follow
>
>     http://www.paraview.org/pipermail/paraview/2011-August/022421.html
>
>     to get my existing Image Data producing Python Programmable Source
>     to distribute the data across the servers. Any additional advice?
>     Thanks again.
>
>     -jeff
>>
>>
>>
>>     David E DeMarle
>>     Kitware, Inc.
>>     R&D Engineer
>>     21 Corporate Drive
>>     Clifton Park, NY 12065-8662
>>     Phone: 518-881-4909 <tel:518-881-4909>
>>
>>     On Thu, Jul 23, 2015 at 1:53 PM, Jeff Becker
>>     <jeffrey.c.becker at nasa.gov <mailto:jeffrey.c.becker at nasa.gov>> wrote:
>>
>>         Hi. I do "mpirun -np 4 pvserver --client-host=xxx
>>         --use-offscreen-rendering", and connect a ParaView client
>>         viewer. I can see 4 nodes in the memory inspector, but when I
>>         start a python shell in ParaView, and do:
>>
>>         from mpi4py import MPI
>>         print MPI.COMM_WORLD.Get_size()
>>
>>         I get the answer 1. Shouldn't it be 4? Thanks.
>>
>>         -jeff
>>
>>
>>         _______________________________________________
>>         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
>>
>>
>
>

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

From fissell at pitt.edu  Thu Jul 23 17:52:00 2015
From: fissell at pitt.edu (Kate Fissell)
Date: Thu, 23 Jul 2015 17:52:00 -0400
Subject: [Paraview] paraview 4.1 and greater not getting slice
 representation on remote logins
In-Reply-To: <CADHSJjBKMu_R=LdmhT9CqioSaU3S6w3+9JUBQCTx2j65V5EQzg@mail.gmail.com>
References: <55AFEA19.5040104@pitt.edu>
 <CADHSJjBKMu_R=LdmhT9CqioSaU3S6w3+9JUBQCTx2j65V5EQzg@mail.gmail.com>
Message-ID: <55B16200.7020307@pitt.edu>

Hi Utkarsh,

Thanks for your super fast response.
Using a  slice filter I also get no slice image.
I downloaded nightly build ParaView-4.3.1-882-gbdceec7-Linux-64bit
and I still have the problem.  Is that the most recent git/master ?

When you say you think the problem is related to the fix you list,
do you mean that the 15457 fix you needed to do for parallel
slice had the side effect of causing this remote connection issue, or,
do you mean that the parallel slice fix would hopefully solve
the remote connection issue ?

I tried to take a look at the code changes in the fix.
I saw some stuff with extents.   Do you think that the
problem is that the extent is computed incorrectly, eg
way too small, eg 0 ?   Why would that happen only
on the Centos->Ubuntu remote connection ?

thanks very much,
Kate

On 07/22/2015 03:35 PM, Utkarsh Ayachit wrote:
> Kate,
>
> I suspect it's related to this fix:
> https://gitlab.kitware.com/paraview/paraview/merge_requests/92
>
> I tested with the latest git/master and it does render correctly in
> client-server mode too.
>
> A workaround would be to use the Slice filter instead. It will be a
> little slower and more memory intensive than "Slice" representation,
> however.
>
> Utkarsh
>
> On Wed, Jul 22, 2015 at 3:08 PM, Kate Fissell <fissell at pitt.edu> wrote:
>> Hi,
>>
>> On Paraview versions 4.1 and greater if I ssh -X from a Centos machine into
>> an Ubuntu
>> graphics server to run Paraview I have a problem with viewing images.
>>
>> I load the AnalyzeNifTIIO plugin, and load a nifti image, and I believe it
>> loads correctly.
>> I get the wireframe, the Information panel gives the correct cells/point.
>> If I change to
>> Slice representation the view window stays blank.  Volume representation is
>> fine, I get the
>> 3D rendering.
>> Same thing if I load a vti format of the data, no slice view.
>>
>> This happens when I ssh from a Centos machine, it does not happen when I ssh
>> from
>> an Ubuntu machine.   In both cases I believe I am using glx to do the
>> rendering locally,
>> not doing a setenv DISPLAY to ship the rendered picture over the net.
>> It is the same glx version on the Ubuntu and Centos machine, but they have
>> different
>> graphics cards.
>>
>> Ubuntu server running Paraview (console graphics):
>> OpenGL vendor string: NVIDIA Corporation
>> OpenGL renderer string: Quadro K4000/PCIe/SSE2
>> OpenGL core profile version string: 4.3.0 NVIDIA 331.113
>> OpenGL core profile shading language version string: 4.30 NVIDIA via Cg
>> compiler
>> OpenGL core profile context flags: (none)
>> OpenGL core profile profile mask: core profile
>> OpenGL core profile extensions:
>> OpenGL version string: 4.4.0 NVIDIA 331.113
>> OpenGL shading language version string: 4.40 NVIDIA via Cg compiler
>> OpenGL context flags: (none)
>> OpenGL profile mask: (none)
>> OpenGL extensions:
>>
>>
>> Centos machine ssh'd to Ubuntu server:
>> OpenGL vendor string: NVIDIA Corporation
>> OpenGL renderer string: Quadro FX 580/PCIe/SSE2
>> OpenGL version string: 2.1.2 NVIDIA 340.76
>> OpenGL shading language version string: 1.20 NVIDIA via Cg compiler
>> OpenGL extensions:
>>
>>
>> Ubuntu machine ssh'd to Ubuntu server:
>> OpenGL vendor string: NVIDIA Corporation
>> OpenGL renderer string: Quadro K4000/PCIe/SSE2
>> OpenGL version string: 2.1.2 NVIDIA 304.125
>> OpenGL shading language version string: 1.20 NVIDIA via Cg compiler
>> OpenGL extensions:
>>
>>
>> In Paraview ParaView-v4.0.1 I do not have this problem.
>> I have the problem in Paraview-4.1, 4.2, 4.3.
>>
>> I am using your pre-compiled binaries as test, but I have the same problem
>> with my compilation.
>>
>> Do you know what changed from ParaView-v4.0.1 to ParaView-v4.1 that would
>> cause
>> this or what the workaround is ?
>>
>> thanks
>> Kate
>> _______________________________________________
>> 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


From kevin.dean at decisionsciencescorp.com  Thu Jul 23 18:56:16 2015
From: kevin.dean at decisionsciencescorp.com (Dean, Kevin)
Date: Thu, 23 Jul 2015 15:56:16 -0700
Subject: [Paraview] Conversions
Message-ID: <CAFvyM3SX+mUcL+2gkWS2NsCOYz_rmO-LheEER2=TRR1VnCSZ=A@mail.gmail.com>

Is there an example for converting an UnstructuredGrid to a StructuredGrid?

Kevin E. Dean

-- 
This email and its contents are confidential. If you are not the intended 
recipient, please do not disclose or use the information within this email 
or its attachments. If you have received this email in error, please report 
the error to the sender by return email and delete this communication from 
your records.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/2bde3429/attachment.html>

From cory.quammen at kitware.com  Thu Jul 23 21:05:02 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 23 Jul 2015 21:05:02 -0400
Subject: [Paraview] Conversions
In-Reply-To: <CAFvyM3SX+mUcL+2gkWS2NsCOYz_rmO-LheEER2=TRR1VnCSZ=A@mail.gmail.com>
References: <CAFvyM3SX+mUcL+2gkWS2NsCOYz_rmO-LheEER2=TRR1VnCSZ=A@mail.gmail.com>
Message-ID: <CAB5Fpx47-uoCoWG0S73_rNqA5OyGP5TdU8dAjKmD=BaPbiVXew@mail.gmail.com>

Hi Kevin,

Here's one way you can get a structured (actually uniform rectilinear) grid
from an unstructured grid:

- start ParaView
- load your unstructured grid
- create a Wavelet source with the extent set to the extent of your desired
structured grid
- Filters -> Resample With Dataset. Set the Input to your unstructured grid
and Source to the Wavelet. Click OK.

HTH,
Cory


On Thu, Jul 23, 2015 at 6:56 PM, Dean, Kevin <
kevin.dean at decisionsciencescorp.com> wrote:

> Is there an example for converting an UnstructuredGrid to a StructuredGrid?
>
> Kevin E. Dean
>
> This email and its contents are confidential. If you are not the intended
> recipient, please do not disclose or use the information within this email
> or its attachments. If you have received this email in error, please report
> the error to the sender by return email and delete this communication from
> your records.
> _______________________________________________
> 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
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/a0185289/attachment.html>

From dave.demarle at kitware.com  Thu Jul 23 21:39:07 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 23 Jul 2015 21:39:07 -0400
Subject: [Paraview] running parallel pvservers
In-Reply-To: <55B15FF8.40306@nasa.gov>
References: <55B12A0A.6070106@nasa.gov>
 <CANjZAi8TCHjs4dzb7epUKybRu=KjbUheJqKpRYQurqNDcxSeUA@mail.gmail.com>
 <55B12F05.6070005@nasa.gov>
 <CANjZAi-2kECbCfGX1kYp12Rfa5rH2PYAPyVZy-sEMmJ_KsxAOA@mail.gmail.com>
 <55B15FF8.40306@nasa.gov>
Message-ID: <CANjZAi_aibkLiBg8J_UedhOP6wvnZonBQY+N=zCcjGMP7vj_pw@mail.gmail.com>

That feature was removed in 4.1 with commit 6ebe5e0f.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Thu, Jul 23, 2015 at 5:43 PM, Jeff Becker <jeffrey.c.becker at nasa.gov>
wrote:

>  In the e-mail thread quoted below, it says:
>
> >>>* Note also that there is a "feature" in the python programmable filter
> *>>>* that comes into play with structured data. That feature says that
> *>>>* structured data is not split at all by default. If you want structured
> *>>>* data to actually be parallel you need to put this code in your python
> *>>>* programmable filter.
> *>>>>>>* from paraview import util
> *>>>>>>* self.GetExecutive().SetExtentTranslator(self.GetExecutive().GetOutputInformation(0),
> *>>>* vtk.vtkExtentTranslator())*
>
>
> Is this still the case, and if so, how does this translate to VTK 6?
> Thanks.
>
> -jeff
>
>
>
> On 07/23/2015 11:18 AM, David E DeMarle wrote:
>
> Excellent.
>
>  No advice yet. Anyone have a worked out example ready? If so, post it to
> the wiki please.
>
>
>  David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Thu, Jul 23, 2015 at 2:14 PM, Jeff Becker <jeffrey.c.becker at nasa.gov>
> wrote:
>
>>  Hi David,
>>
>> On 07/23/2015 10:57 AM, David E DeMarle wrote:
>>
>> pyhon shell runs on the client side.
>>
>>  try doing that within the python programmable filter, which runs on the
>> server side.
>>
>>
>>  Yes that works. Thanks. Now I will try to use that and follow
>>
>> http://www.paraview.org/pipermail/paraview/2011-August/022421.html
>>
>> to get my existing Image Data producing Python Programmable Source to
>> distribute the data across the servers. Any additional advice? Thanks again.
>>
>> -jeff
>>
>>
>>
>>
>>  David E DeMarle
>> Kitware, Inc.
>> R&D Engineer
>> 21 Corporate Drive
>> Clifton Park, NY 12065-8662
>> Phone: 518-881-4909
>>
>> On Thu, Jul 23, 2015 at 1:53 PM, Jeff Becker <jeffrey.c.becker at nasa.gov>
>> wrote:
>>
>>> Hi. I do "mpirun -np 4 pvserver --client-host=xxx
>>> --use-offscreen-rendering", and connect a ParaView client viewer. I can see
>>> 4 nodes in the memory inspector, but when I start a python shell in
>>> ParaView, and do:
>>>
>>> from mpi4py import MPI
>>> print MPI.COMM_WORLD.Get_size()
>>>
>>> I get the answer 1. Shouldn't it be 4? Thanks.
>>>
>>> -jeff
>>>
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview
>>>
>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150723/ecbc7fb1/attachment.html>

From jfavre at cscs.ch  Fri Jul 24 02:28:46 2015
From: jfavre at cscs.ch (Favre  Jean)
Date: Fri, 24 Jul 2015 06:28:46 +0000
Subject: [Paraview] running parallel pvservers
In-Reply-To: <55B15FF8.40306@nasa.gov>
References: <55B12A0A.6070106@nasa.gov>
 <CANjZAi8TCHjs4dzb7epUKybRu=KjbUheJqKpRYQurqNDcxSeUA@mail.gmail.com>
 <55B12F05.6070005@nasa.gov>
 <CANjZAi-2kECbCfGX1kYp12Rfa5rH2PYAPyVZy-sEMmJ_KsxAOA@mail.gmail.com>,
 <55B15FF8.40306@nasa.gov>
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F6841F1FF83@MBX211.d.ethz.ch>

putting the following code in your ScriptRequestInformation should tell ParaView that you can handle sub-divisions:

executive = self.GetExecutive ()
outInfo = executive.GetOutputInformation(0)
outInfo.Set(vtk.vtkAlgorithm.CAN_PRODUCE_SUB_EXTENT(), 1)

it is then up to you, to correctly handle UPDATE_EXTENT() and WHOLE_EXTENT() in your Script.

-----------------
Jean/CSCS
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150724/aceedd8b/attachment.html>

From sergi.mateo.bellido at gmail.com  Fri Jul 24 05:24:21 2015
From: sergi.mateo.bellido at gmail.com (Sergi Mateo Bellido)
Date: Fri, 24 Jul 2015 11:24:21 +0200
Subject: [Paraview] segfault playing a simulation
In-Reply-To: <55A90F76.8000804@gmail.com>
References: <55895735.2030202@gmail.com>	<CAB5Fpx4BDY+JDKBbA5Lt02Yt1RLaaZY6TPW9azpZsGf-aWTD7Q@mail.gmail.com>	<559381DE.5030504@gmail.com>	<CAB5Fpx6H7dY-j86vut03OuVr+7smd+1YwGqL2e771tRE0xdkxw@mail.gmail.com>	<559422EF.3070304@gmail.com>	<CAB5Fpx7AdTrtGAsq9OjoW36=-dWFDzUAGrtCF+fqqa4hLenoDg@mail.gmail.com>	<55A0E2AE.5050101@gmail.com>
 <CAB5Fpx7-YAJznWJKT6gk4fAV9_GM_GX2E=0Q9_2YSW4Wt5NO8A@mail.gmail.com>
 <55A9056C.2000101@gmail.com> <55A90F76.8000804@gmail.com>
Message-ID: <55B20445.7060809@gmail.com>

Hi Cory,

I have been doing some experiments with the encoding formats but I've 
not progressed much.

The elements of my mesh are floats and the mesh dimensions are 
201x201x201 (X,Y,Z). I executed all the experiments with 2 MPI processes 
and the data domain was manually partionated by the Z axis, i.e. each 
process computes half of the cube.

The program basically writes, at each position of the mesh, the 
identifier of the MPI process that computed that position (mpi rank). In 
our case, this means that half of the cube has a '0' whereas the other 
portion has a '1'.

Attached to this email you will  a tarball with 3 outputs, one for each 
different encoding (ASCII, zipped binary, raw binary). The size of the 
mesh is 201x201x201 and the only difference among the executions is the 
encoding format.

I hope you could give me some light.

Thanks!

Sergi

On 07/17/2015 04:21 PM, Sergi Mateo Bellido wrote:
> Hi again,
>
> I've just tried storing the data as a binary and It  crashes. In this 
> case we are not using the offset field either.
>
> May the problem be related to the data compression?
>
> Best,
> Sergi
>
> On 07/17/2015 03:38 PM, Sergi Mateo Bellido wrote:
>> Hi Cory,
>>
>> Your intuition was right: the problem is related in some way with the 
>> offset. I've changed the DataMote to ASCII and everything worked :)  
>> Note that in this mode the offset field is not used, instead of that 
>> VTK generates a DataArray.
>>
>> I would like to know how the offset is computed since I can't find 
>> any relation between the  offset value and my data.
>>
>> Thanks!
>>
>> Sergi
>>
>> On 07/13/2015 03:51 AM, Cory Quammen wrote:
>>> Sergi,
>>>
>>> Your VTI file extents should only describe the region of the whole 
>>> image they occupy, so you are on the right track. In situations like 
>>> these where it isn't obvious what is wrong, I tend to start from the 
>>> beginning with a very small example and build up from there. For 
>>> example, you could start with a small image - say 2 x 4 pixels (2D) 
>>> split into two pieces. Start with one data array for this example 
>>> and make sure it works - use ASCII encoding so that you know for 
>>> sure what is in the XML file and then switch to raw binary, then 
>>> zipped binary. Then add a second data array. When you are confident 
>>> that works, change the example to four pieces, then make the image 
>>> 3D and so on.
>>>
>>> It can take a while to do this, but you'll come out really 
>>> understanding the file format and will probably figure out what you 
>>> had wrong in the first place.
>>>
>>> Thanks,
>>> Cory
>>>
>>> On Sat, Jul 11, 2015 at 5:32 AM, Sergi Mateo Bellido 
>>> <sergi.mateo.bellido at gmail.com 
>>> <mailto:sergi.mateo.bellido at gmail.com>> wrote:
>>>
>>>     Hi Cory,
>>>
>>>     Thanks for your time. I have been playing a bit with the files
>>>     too and I realized that replacing the whole_extent of each
>>>     *.vti  by the whole dataset everything works.
>>>
>>>     I would like to generate something like this:
>>>     http://vtk.1045678.n5.nabble.com/Example-vti-file-td3381382.html
>>>     . In this example, each imagedata has whole_extent=whole size
>>>     but its pieces only contain a portion of the whole dataset. Does
>>>     this configuration make sense?
>>>
>>>     I have been trying to generate something like that but I failed.
>>>     My code looks like this one:
>>>     http://www.vtk.org/Wiki/VTK/Examples/Cxx/IO/WriteVTI but using
>>>     VtkFloatArray as buffers and attaching them to the VtkImageData.
>>>     I tried defining the set of the VtkImageData as the whole
>>>     dataset and defining the VtkFloatArrays of the size of each
>>>     portion but it didn't work :(
>>>
>>>     Any clue?
>>>
>>>     Thanks!
>>>     Sergi
>>>
>>>
>>>     On 07/09/2015 05:00 PM, Cory Quamen wrote:
>>>>     Hi Sergi,
>>>>
>>>>     I played with your data set a little but haven't found what is
>>>>     wrong. I am suspicious of two things in the data file, the
>>>>     extent and the offset in the second data array (it looks too
>>>>     small).
>>>>
>>>>     What are the dimensions of your grid? Note that the whole
>>>>     extent upper values need to be the dimension - 1, e.g., for a
>>>>     300x300x300 grid, the whole extent should be 0 299 0 299 0 299.
>>>>
>>>>     Thanks,
>>>>     Cory
>>>>
>>>>     On Wed, Jul 1, 2015 at 12:27 PM, Sergi Mateo Bellido
>>>>     <sergi.mateo.bellido at gmail.com
>>>>     <mailto:sergi.mateo.bellido at gmail.com>> wrote:
>>>>
>>>>         Hi Cory,
>>>>
>>>>         Thanks for your time. These data files have been produced
>>>>         by a software that I'm developing with some colleagues.
>>>>
>>>>         Best regards,
>>>>
>>>>         Sergi
>>>>
>>>>
>>>>         On 07/01/2015 03:59 PM, Cory Quammen wrote:
>>>>>         Sergi,
>>>>>
>>>>>         I can confirm the crash you are seeing in the same
>>>>>         location in the code. I'm looking for the cause.
>>>>>
>>>>>         What software produced these data files?
>>>>>
>>>>>         Thanks,
>>>>>         Cory
>>>>>
>>>>>         On Wed, Jul 1, 2015 at 1:59 AM, Sergi Mateo Bellido
>>>>>         <sergi.mateo.bellido at gmail.com
>>>>>         <mailto:sergi.mateo.bellido at gmail.com>> wrote:
>>>>>
>>>>>             Hi Cory,
>>>>>
>>>>>             Thanks for your answer. I reproduced the segfault in
>>>>>             two different ways, but it's always after loading a
>>>>>             data set:
>>>>>             - After loading a data set, I tried to play the
>>>>>             simulation ->segfault
>>>>>             - After loading a data set, I tried to filter some
>>>>>             fields from the model (Pointer array status). As soon
>>>>>             as I clicked the 'apply' button, paraview crashed with
>>>>>             a segfault.
>>>>>
>>>>>             Thanks,
>>>>>             Sergi
>>>>>
>>>>>
>>>>>
>>>>>             On 06/30/2015 06:21 AM, Cory Quammen wrote:
>>>>>>             Hi Sergi,
>>>>>>
>>>>>>             Could you clarify when you are seeing this crash? Is
>>>>>>             it right when starting ParaView or when first loading
>>>>>>             a data set?
>>>>>>
>>>>>>             Thanks,
>>>>>>             Cory
>>>>>>
>>>>>>             On Tue, Jun 23, 2015 at 8:55 AM, Sergi Mateo Bellido
>>>>>>             <sergi.mateo.bellido at gmail.com
>>>>>>             <mailto:sergi.mateo.bellido at gmail.com>> wrote:
>>>>>>
>>>>>>                 Hi,
>>>>>>
>>>>>>                 I'm trying to reproduce a simulation with
>>>>>>                 ParaView 4.3.1 and it always crashes when I start
>>>>>>                 it. You can find the backtrace below:
>>>>>>
>>>>>>                 =========================================================
>>>>>>                 Process id 6681 Caught SIGSEGV at 0x925b124
>>>>>>                 address not mapped to object
>>>>>>                 Program Stack:
>>>>>>                 WARNING: The stack trace will not use advanced
>>>>>>                 capabilities because this is a release build.
>>>>>>                 0x7f54ce081d40 : ??? [(???) ???:-1]
>>>>>>                 0x7f54ce19caf6 : ??? [(???) ???:-1]
>>>>>>                 0x7f54cb123736 :
>>>>>>                 vtkXMLPStructuredDataReader::CopySubExtent(int*,
>>>>>>                 int*, long long*, int*, int*, long long*, int*,
>>>>>>                 int*, vtkDataArray*, vtkDataArray*)
>>>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54cb12389f :
>>>>>>                 vtkXMLPStructuredDataReader::CopyArrayForPoints(vtkDataArray*,
>>>>>>                 vtkDataArray*) [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54cb11cc1f :
>>>>>>                 vtkXMLPDataReader::ReadPieceData()
>>>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54cb11ca14 :
>>>>>>                 vtkXMLPDataReader::ReadPieceData(int)
>>>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54cb124d7a :
>>>>>>                 vtkXMLPStructuredDataReader::ReadXMLData()
>>>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54cb1280eb :
>>>>>>                 vtkXMLReader::RequestData(vtkInformation*,
>>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54cb1273b6 :
>>>>>>                 vtkXMLReader::ProcessRequest(vtkInformation*,
>>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>>                 [(libvtkIOXML-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54cd6200f9 :
>>>>>>                 vtkFileSeriesReader::RequestData(vtkInformation*,
>>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>>                 [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54cd61f07f :
>>>>>>                 vtkFileSeriesReader::ProcessRequest(vtkInformation*,
>>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>>                 [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d2706204 :
>>>>>>                 vtkExecutive::CallAlgorithm(vtkInformation*, int,
>>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d27016cc :
>>>>>>                 vtkDemandDrivenPipeline::ExecuteData(vtkInformation*,
>>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d2700201 :
>>>>>>                 vtkCompositeDataPipeline::ExecuteData(vtkInformation*,
>>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d2704067 :
>>>>>>                 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d271d959 :
>>>>>>                 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d26fe387 :
>>>>>>                 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*)
>>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d2704010 :
>>>>>>                 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d271d959 :
>>>>>>                 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d26fe387 :
>>>>>>                 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*)
>>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d2704010 :
>>>>>>                 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d271d959 :
>>>>>>                 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
>>>>>>                 vtkInformationVector**, vtkInformationVector*)
>>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d27035ae :
>>>>>>                 vtkDemandDrivenPipeline::UpdateData(int)
>>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d271e87f :
>>>>>>                 vtkStreamingDemandDrivenPipeline::Update(int)
>>>>>>                 [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54cd98fa7f :
>>>>>>                 vtkPVDataRepresentation::ProcessViewRequest(vtkInformationRequestKey*,
>>>>>>                 vtkInformation*, vtkInformation*)
>>>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54cd973d79 :
>>>>>>                 vtkGeometryRepresentation::ProcessViewRequest(vtkInformationRequestKey*,
>>>>>>                 vtkInformation*, vtkInformation*)
>>>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54cd975d71 :
>>>>>>                 vtkGeometryRepresentationWithFaces::ProcessViewRequest(vtkInformationRequestKey*,
>>>>>>                 vtkInformation*, vtkInformation*)
>>>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54cd9bd388 :
>>>>>>                 vtkPVView::CallProcessViewRequest(vtkInformationRequestKey*,
>>>>>>                 vtkInformation*, vtkInformationVector*)
>>>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54cd9bd552 : vtkPVView::Update()
>>>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54cd9acb78 : vtkPVRenderView::Update()
>>>>>>                 [(libvtkPVClientServerCoreRendering-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54d780ac30 :
>>>>>>                 vtkPVRenderViewCommand(vtkClientServerInterpreter*,
>>>>>>                 vtkObjectBase*, char const*,
>>>>>>                 vtkClientServerStream const&,
>>>>>>                 vtkClientServerStream&, void*)
>>>>>>                 [(libvtkPVServerManagerApplication-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54d4e135e0 :
>>>>>>                 vtkClientServerInterpreter::CallCommandFunction(char
>>>>>>                 const*, vtkObjectBase*, char const*,
>>>>>>                 vtkClientServerStream const&,
>>>>>>                 vtkClientServerStream&)
>>>>>>                 [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d4e18393 :
>>>>>>                 vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream
>>>>>>                 const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d4e16832 :
>>>>>>                 vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream
>>>>>>                 const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d4e16ced :
>>>>>>                 vtkClientServerInterpreter::ProcessStream(vtkClientServerStream
>>>>>>                 const&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d5b26cec :
>>>>>>                 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream
>>>>>>                 const&, bool)
>>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54d5b26958 :
>>>>>>                 vtkPVSessionCore::ExecuteStream(unsigned int,
>>>>>>                 vtkClientServerStream const&, bool)
>>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54d5b25203 :
>>>>>>                 vtkPVSessionBase::ExecuteStream(unsigned int,
>>>>>>                 vtkClientServerStream const&, bool)
>>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54cdcae44f : vtkSMViewProxy::Update()
>>>>>>                 [(libvtkPVServerManagerRendering-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54cdf2f6f7 :
>>>>>>                 vtkSMAnimationScene::TickInternal(double, double,
>>>>>>                 double) [(libvtkPVAnimation-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54cf415cab : vtkAnimationCue::Tick(double,
>>>>>>                 double, double) [(libvtkCommonCore-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54cdf23268 : vtkAnimationPlayer::Play()
>>>>>>                 [(libvtkPVAnimation-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d7851619 :
>>>>>>                 vtkSMAnimationSceneCommand(vtkClientServerInterpreter*,
>>>>>>                 vtkObjectBase*, char const*,
>>>>>>                 vtkClientServerStream const&,
>>>>>>                 vtkClientServerStream&, void*)
>>>>>>                 [(libvtkPVServerManagerApplication-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54d4e135e0 :
>>>>>>                 vtkClientServerInterpreter::CallCommandFunction(char
>>>>>>                 const*, vtkObjectBase*, char const*,
>>>>>>                 vtkClientServerStream const&,
>>>>>>                 vtkClientServerStream&)
>>>>>>                 [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d4e18393 :
>>>>>>                 vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream
>>>>>>                 const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d4e16832 :
>>>>>>                 vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream
>>>>>>                 const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d4e16ced :
>>>>>>                 vtkClientServerInterpreter::ProcessStream(vtkClientServerStream
>>>>>>                 const&) [(libvtkClientServer-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d5b436d4 :
>>>>>>                 vtkSIProperty::ProcessMessage(vtkClientServerStream&)
>>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54d5b4377e :
>>>>>>                 vtkSIProperty::Push(paraview_protobuf::Message*,
>>>>>>                 int)
>>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54d5b4459e :
>>>>>>                 vtkSIProxy::Push(paraview_protobuf::Message*)
>>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54d5b2884a :
>>>>>>                 vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*)
>>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54d5b27484 :
>>>>>>                 vtkPVSessionCore::PushState(paraview_protobuf::Message*)
>>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54d5b2514d :
>>>>>>                 vtkPVSessionBase::PushState(paraview_protobuf::Message*)
>>>>>>                 [(libvtkPVServerImplementationCore-pv4.3.so.1)
>>>>>>                 ???:-1]
>>>>>>                 0x7f54d5d859b7 : vtkSMProxy::UpdateProperty(char
>>>>>>                 const*, int)
>>>>>>                 [(libvtkPVServerManagerCore-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54d6d8aa07 : pqVCRController::onPlay()
>>>>>>                 [(libvtkpqComponents-pv4.3.so.1) ???:-1]
>>>>>>                 0x7f54cfa98258 : QMetaObject::activate(QObject*,
>>>>>>                 QMetaObject const*, int, void**)
>>>>>>                 [(libQtCore.so.4) ???:-1]
>>>>>>                 0x7f54d01102f2 : QAction::triggered(bool)
>>>>>>                 [(libQtGui.so.4) ???:-1]
>>>>>>                 0x7f54d0111710 :
>>>>>>                 QAction::activate(QAction::ActionEvent)
>>>>>>                 [(libQtGui.so.4) ???:-1]
>>>>>>                 0x7f54d04fd514 : ??? [(???) ???:-1]
>>>>>>                 0x7f54d04fd7ab :
>>>>>>                 QAbstractButton::mouseReleaseEvent(QMouseEvent*)
>>>>>>                 [(libQtGui.so.4) ???:-1]
>>>>>>                 0x7f54d05d15ea :
>>>>>>                 QToolButton::mouseReleaseEvent(QMouseEvent*)
>>>>>>                 [(libQtGui.so.4) ???:-1]
>>>>>>                 0x7f54d0175ac1 : QWidget::event(QEvent*)
>>>>>>                 [(libQtGui.so.4) ???:-1]
>>>>>>                 0x7f54d04fca3f : QAbstractButton::event(QEvent*)
>>>>>>                 [(libQtGui.so.4) ???:-1]
>>>>>>                 0x7f54d05d422d : QToolButton::event(QEvent*)
>>>>>>                 [(libQtGui.so.4) ???:-1]
>>>>>>                 0x7f54d011759e :
>>>>>>                 QApplicationPrivate::notify_helper(QObject*,
>>>>>>                 QEvent*) [(libQtGui.so.4) ???:-1]
>>>>>>                 0x7f54d011e533 : QApplication::notify(QObject*,
>>>>>>                 QEvent*) [(libQtGui.so.4) ???:-1]
>>>>>>                 0x7f54cfa802f3 :
>>>>>>                 QCoreApplication::notifyInternal(QObject*,
>>>>>>                 QEvent*) [(libQtCore.so.4) ???:-1]
>>>>>>                 0x7f54d011a656 :
>>>>>>                 QApplicationPrivate::sendMouseEvent(QWidget*,
>>>>>>                 QMouseEvent*, QWidget*, QWidget*, QWidget**,
>>>>>>                 QPointer<QWidget>&, bool) [(libQtGui.so.4) ???:-1]
>>>>>>                 0x7f54d019ca94 : ??? [(???) ???:-1]
>>>>>>                 0x7f54d019b877 :
>>>>>>                 QApplication::x11ProcessEvent(_XEvent*)
>>>>>>                 [(libQtGui.so.4) ???:-1]
>>>>>>                 0x7f54d01c4805 : ??? [(???) ???:-1]
>>>>>>                 0x7f54cfa7f375 :
>>>>>>                 QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
>>>>>>                 [(libQtCore.so.4) ???:-1]
>>>>>>                 0x7f54cfa7f748 :
>>>>>>                 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
>>>>>>                 [(libQtCore.so.4) ???:-1]
>>>>>>                 0x7f54cfa8414b : QCoreApplication::exec()
>>>>>>                 [(libQtCore.so.4) ???:-1]
>>>>>>                 0x407785 : main [(paraview) ???:-1]
>>>>>>                 0x7f54ce06cec5 : __libc_start_main [(libc.so.6)
>>>>>>                 ???:-1]
>>>>>>                 0x4074da : QMainWindow::event(QEvent*)
>>>>>>                 [(paraview) ???:-1]
>>>>>>                 =========================================================
>>>>>>
>>>>>>                 Thanks,
>>>>>>
>>>>>>                 Sergi Mateo
>>>>>>                 sergi.mateo.bellido at gmail.com
>>>>>>                 <mailto:sergi.mateo.bellido at gmail.com>
>>>>>>
>>>>>>                 _______________________________________________
>>>>>>                 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
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>             -- 
>>>>>>             Cory Quammen
>>>>>>             R&D Engineer
>>>>>>             Kitware, Inc.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>         -- 
>>>>>         Cory Quammen
>>>>>         R&D Engineer
>>>>>         Kitware, Inc.
>>>>
>>>>
>>>>
>>>>
>>>>     -- 
>>>>     Cory Quammen
>>>>     R&D Engineer
>>>>     Kitware, Inc.
>>>
>>>
>>>
>>>
>>> -- 
>>> Cory Quammen
>>> R&D Engineer
>>> Kitware, Inc.
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150724/595df898/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mpi_test.tar.gz
Type: application/gzip
Size: 207751 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150724/595df898/attachment-0001.bin>

From utkarsh.ayachit at kitware.com  Fri Jul 24 10:14:38 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 24 Jul 2015 14:14:38 +0000
Subject: [Paraview] paraview 4.1 and greater not getting slice
 representation on remote logins
In-Reply-To: <55B16200.7020307@pitt.edu>
References: <55AFEA19.5040104@pitt.edu>
 <CADHSJjBKMu_R=LdmhT9CqioSaU3S6w3+9JUBQCTx2j65V5EQzg@mail.gmail.com>
 <55B16200.7020307@pitt.edu>
Message-ID: <CADHSJjAeZzoNGGvszfQqFV_ypmPEOWJYgVXAbOWTAnDqus8B7Q@mail.gmail.com>

Ah! I missed the info about ssh -X from different machines. Try doing a
simple Wavelet source and slice that. Does that work?

On Thu, Jul 23, 2015 at 5:52 PM Kate Fissell <fissell at pitt.edu> wrote:

> Hi Utkarsh,
>
> Thanks for your super fast response.
> Using a  slice filter I also get no slice image.
> I downloaded nightly build ParaView-4.3.1-882-gbdceec7-Linux-64bit
> and I still have the problem.  Is that the most recent git/master ?
>
> When you say you think the problem is related to the fix you list,
> do you mean that the 15457 fix you needed to do for parallel
> slice had the side effect of causing this remote connection issue, or,
> do you mean that the parallel slice fix would hopefully solve
> the remote connection issue ?
>
> I tried to take a look at the code changes in the fix.
> I saw some stuff with extents.   Do you think that the
> problem is that the extent is computed incorrectly, eg
> way too small, eg 0 ?   Why would that happen only
> on the Centos->Ubuntu remote connection ?
>
> thanks very much,
> Kate
>
> On 07/22/2015 03:35 PM, Utkarsh Ayachit wrote:
> > Kate,
> >
> > I suspect it's related to this fix:
> > https://gitlab.kitware.com/paraview/paraview/merge_requests/92
> >
> > I tested with the latest git/master and it does render correctly in
> > client-server mode too.
> >
> > A workaround would be to use the Slice filter instead. It will be a
> > little slower and more memory intensive than "Slice" representation,
> > however.
> >
> > Utkarsh
> >
> > On Wed, Jul 22, 2015 at 3:08 PM, Kate Fissell <fissell at pitt.edu> wrote:
> >> Hi,
> >>
> >> On Paraview versions 4.1 and greater if I ssh -X from a Centos machine
> into
> >> an Ubuntu
> >> graphics server to run Paraview I have a problem with viewing images.
> >>
> >> I load the AnalyzeNifTIIO plugin, and load a nifti image, and I believe
> it
> >> loads correctly.
> >> I get the wireframe, the Information panel gives the correct
> cells/point.
> >> If I change to
> >> Slice representation the view window stays blank.  Volume
> representation is
> >> fine, I get the
> >> 3D rendering.
> >> Same thing if I load a vti format of the data, no slice view.
> >>
> >> This happens when I ssh from a Centos machine, it does not happen when
> I ssh
> >> from
> >> an Ubuntu machine.   In both cases I believe I am using glx to do the
> >> rendering locally,
> >> not doing a setenv DISPLAY to ship the rendered picture over the net.
> >> It is the same glx version on the Ubuntu and Centos machine, but they
> have
> >> different
> >> graphics cards.
> >>
> >> Ubuntu server running Paraview (console graphics):
> >> OpenGL vendor string: NVIDIA Corporation
> >> OpenGL renderer string: Quadro K4000/PCIe/SSE2
> >> OpenGL core profile version string: 4.3.0 NVIDIA 331.113
> >> OpenGL core profile shading language version string: 4.30 NVIDIA via Cg
> >> compiler
> >> OpenGL core profile context flags: (none)
> >> OpenGL core profile profile mask: core profile
> >> OpenGL core profile extensions:
> >> OpenGL version string: 4.4.0 NVIDIA 331.113
> >> OpenGL shading language version string: 4.40 NVIDIA via Cg compiler
> >> OpenGL context flags: (none)
> >> OpenGL profile mask: (none)
> >> OpenGL extensions:
> >>
> >>
> >> Centos machine ssh'd to Ubuntu server:
> >> OpenGL vendor string: NVIDIA Corporation
> >> OpenGL renderer string: Quadro FX 580/PCIe/SSE2
> >> OpenGL version string: 2.1.2 NVIDIA 340.76
> >> OpenGL shading language version string: 1.20 NVIDIA via Cg compiler
> >> OpenGL extensions:
> >>
> >>
> >> Ubuntu machine ssh'd to Ubuntu server:
> >> OpenGL vendor string: NVIDIA Corporation
> >> OpenGL renderer string: Quadro K4000/PCIe/SSE2
> >> OpenGL version string: 2.1.2 NVIDIA 304.125
> >> OpenGL shading language version string: 1.20 NVIDIA via Cg compiler
> >> OpenGL extensions:
> >>
> >>
> >> In Paraview ParaView-v4.0.1 I do not have this problem.
> >> I have the problem in Paraview-4.1, 4.2, 4.3.
> >>
> >> I am using your pre-compiled binaries as test, but I have the same
> problem
> >> with my compilation.
> >>
> >> Do you know what changed from ParaView-v4.0.1 to ParaView-v4.1 that
> would
> >> cause
> >> this or what the workaround is ?
> >>
> >> thanks
> >> Kate
> >> _______________________________________________
> >> Powered by www.kitware.com
> >>
> >> Visit other Kitware open-source projects at
> >> http://www.kitware.com/opensource/opensource.html
> >>
> >> Please keep messages on-topic and check the ParaView Wiki at:
> >> http://paraview.org/Wiki/ParaView
> >>
> >> Search the list archives at: http://markmail.org/search/?q=ParaView
> >>
> >> Follow this link to subscribe/unsubscribe:
> >> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150724/78b951d3/attachment.html>

From kevin.dean at decisionsciencescorp.com  Fri Jul 24 12:09:25 2015
From: kevin.dean at decisionsciencescorp.com (Dean, Kevin)
Date: Fri, 24 Jul 2015 09:09:25 -0700
Subject: [Paraview] Conversions
In-Reply-To: <CAB5Fpx47-uoCoWG0S73_rNqA5OyGP5TdU8dAjKmD=BaPbiVXew@mail.gmail.com>
References: <CAFvyM3SX+mUcL+2gkWS2NsCOYz_rmO-LheEER2=TRR1VnCSZ=A@mail.gmail.com>
 <CAB5Fpx47-uoCoWG0S73_rNqA5OyGP5TdU8dAjKmD=BaPbiVXew@mail.gmail.com>
Message-ID: <CAFvyM3QbgPswEtz0j+63qXVs0HTCXZ=7JOUD6O+mmRv41ynD7w@mail.gmail.com>

Thanks Cory, that did get me a little further. However, at the moment, I am
trying to stream (multiple) vtkPolyData Objects. For Some reason, I can't
get them to update by pieces/blocks (i tried referring to
http://www.vtk.org/Wiki/VTK/Streaming &
http://www.kitware.com/blog/home/post/797).

So I ended up converting them to vtkImageData (but could only load one of
the two). I put them into a vtkAppendFilter() and converted them to a
structured grid and Utilized vtkStructuredGridAlgorithm. I can visualize
either the entire block which contains the two separate Objects, or the
points of each object instead of the Surface Representation of each block.
I'll keep trying to figure it out :-), I'm getting closer (and this helped
so thank you).

Thanks,

Kevin

On Thu, Jul 23, 2015 at 6:05 PM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Hi Kevin,
>
> Here's one way you can get a structured (actually uniform rectilinear)
> grid from an unstructured grid:
>
> - start ParaView
> - load your unstructured grid
> - create a Wavelet source with the extent set to the extent of your
> desired structured grid
> - Filters -> Resample With Dataset. Set the Input to your unstructured
> grid and Source to the Wavelet. Click OK.
>
> HTH,
> Cory
>
>
> On Thu, Jul 23, 2015 at 6:56 PM, Dean, Kevin <
> kevin.dean at decisionsciencescorp.com> wrote:
>
>> Is there an example for converting an UnstructuredGrid to a
>> StructuredGrid?
>>
>> Kevin E. Dean
>>
>> This email and its contents are confidential. If you are not the intended
>> recipient, please do not disclose or use the information within this email
>> or its attachments. If you have received this email in error, please report
>> the error to the sender by return email and delete this communication from
>> your records.
>> _______________________________________________
>> 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
>>
>>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>

-- 
This email and its contents are confidential. If you are not the intended 
recipient, please do not disclose or use the information within this email 
or its attachments. If you have received this email in error, please report 
the error to the sender by return email and delete this communication from 
your records.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150724/89e40709/attachment.html>

From pulido at lanl.gov  Fri Jul 24 12:43:44 2015
From: pulido at lanl.gov (Pulido, Jesus)
Date: Fri, 24 Jul 2015 16:43:44 +0000
Subject: [Paraview] Memory seeking problems in using the xdmf2 reader
Message-ID: <E65EBD9CD7A9004A924D2E7C5ED608D58BA250C8@ECS-EXG-P-MB05.win.lanl.gov>

Hello,

I have written a custom xmf file used by the xdmf2 reader to properly read in (raw) binary data into Paraview. This normally works but only for small datasets. The file requires the input of a memory "seek" location to start reading the different scalar components of the data. A problem arises when there is a 512^3 dataset, with 5 scalar components that are required to be read in. The first two scalar components are read in correctly, then the next two components receive the error:


ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/IO/Xdmf2/vtkXdmfHeavyData.cxx, line 1128

vtkXdmfReader (0x7f8614672af0): Failed to read attribute data

The 5th component then becomes a duplicate of the 1st component.
What I believe that's happening is that the "seek" value is only being represented as a signed integer, this would explain the memory location rolling from MAX_INT to -MAX_INT, and failing to read in scalar components 3 and 4. Their seek locations fall within this case. By the time the 5th component is read, the seek value may have rolled over back to positive values (seek > 0) and then duplicates the same data as the 1st component.

Is this assumption correct and intended? Is there fix for this or an alternative way around reading large, raw datasets using this format? I'm attaching a sample xmf file

Thank you,
Jesus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150724/e770550d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rstrt0012.xmf
Type: application/octet-stream
Size: 2149 bytes
Desc: rstrt0012.xmf
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150724/e770550d/attachment.obj>

From patrick.oleary at kitware.com  Fri Jul 24 14:57:29 2015
From: patrick.oleary at kitware.com (Patrick O'Leary)
Date: Fri, 24 Jul 2015 12:57:29 -0600
Subject: [Paraview] Save the Date - 4th Workshop on Next Generation
 Analytics for the Future Power Grid
Message-ID: <CAM8hOwbZdN3BvEwu-J8KqCSmPNZtsHoG+yxJNsPWw8mNw5hfsg@mail.gmail.com>

4th Workshop on Next Generation Analytics for the Future Power
Grid:   http://gridoptics.pnnl.gov/fpgws15/

Energy Day @ PNNL:      http://gridoptics.pnnl.gov/energyday/

More information on logistics for the meeting will be forthcoming, and
will be added to the websites above as it becomes available, but please
contact us at GridOPTICS at pnnl.gov with any questions?.and check your
calendar now to save the date!


Thanks greatly for your consideration,
_________________________________________________
Zhenyu (Henry) Huang, Ph.D., P.E.
Chief Engineer, Team Lead, Workshop Chair
Energy and Environment Directorate
Pacific Northwest National Laboratory
902 Battelle Boulevard
P.O. Box 999, MSIN K1-85
Richland, WA  99352 USA
Tel:  509-372-6781
Fax: 509-372-4353
zhenyu.huang at pnl.gov
www.pnl.gov

__________________________________________________
Tamica Dickenson
Project Coordinator
Energy and Environment Directorate

Pacific Northwest National Laboratory
902 Battelle Boulevard
P.O. Box 999, MSIN J4-90
Richland, WA  99352 USA
Tel:  509-372-6802
Fax: 509-372-4353
Tamica at pnnl.gov
www.pnl.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150724/722b5e3d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Next-Generation Analytics for the Future Power Grid flyer.jpg
Type: image/jpeg
Size: 173744 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150724/722b5e3d/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Save the Date - 4th Workshop on Next-Generation Analytics for the Future Power Grid.ics
Type: text/calendar
Size: 11057 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150724/722b5e3d/attachment.ics>

From fissell at pitt.edu  Fri Jul 24 17:02:48 2015
From: fissell at pitt.edu (Kate Fissell)
Date: Fri, 24 Jul 2015 17:02:48 -0400
Subject: [Paraview] paraview 4.1 and greater not getting slice
 representation on remote logins
In-Reply-To: <CADHSJjAeZzoNGGvszfQqFV_ypmPEOWJYgVXAbOWTAnDqus8B7Q@mail.gmail.com>
References: <55AFEA19.5040104@pitt.edu>
 <CADHSJjBKMu_R=LdmhT9CqioSaU3S6w3+9JUBQCTx2j65V5EQzg@mail.gmail.com>
 <55B16200.7020307@pitt.edu>
 <CADHSJjAeZzoNGGvszfQqFV_ypmPEOWJYgVXAbOWTAnDqus8B7Q@mail.gmail.com>
Message-ID: <55B2A7F8.3040207@pitt.edu>

Hi,

No slice appears with wavelet source.

Kate

On 07/24/2015 10:14 AM, Utkarsh Ayachit wrote:
> Ah! I missed the info about ssh -X from different machines. Try doing 
> a simple Wavelet source and slice that. Does that work?
>
> On Thu, Jul 23, 2015 at 5:52 PM Kate Fissell <fissell at pitt.edu 
> <mailto:fissell at pitt.edu>> wrote:
>
>     Hi Utkarsh,
>
>     Thanks for your super fast response.
>     Using a  slice filter I also get no slice image.
>     I downloaded nightly build ParaView-4.3.1-882-gbdceec7-Linux-64bit
>     and I still have the problem.  Is that the most recent git/master ?
>
>     When you say you think the problem is related to the fix you list,
>     do you mean that the 15457 fix you needed to do for parallel
>     slice had the side effect of causing this remote connection issue, or,
>     do you mean that the parallel slice fix would hopefully solve
>     the remote connection issue ?
>
>     I tried to take a look at the code changes in the fix.
>     I saw some stuff with extents.   Do you think that the
>     problem is that the extent is computed incorrectly, eg
>     way too small, eg 0 ?   Why would that happen only
>     on the Centos->Ubuntu remote connection ?
>
>     thanks very much,
>     Kate
>
>     On 07/22/2015 03:35 PM, Utkarsh Ayachit wrote:
>     > Kate,
>     >
>     > I suspect it's related to this fix:
>     > https://gitlab.kitware.com/paraview/paraview/merge_requests/92
>     >
>     > I tested with the latest git/master and it does render correctly in
>     > client-server mode too.
>     >
>     > A workaround would be to use the Slice filter instead. It will be a
>     > little slower and more memory intensive than "Slice" representation,
>     > however.
>     >
>     > Utkarsh
>     >
>     > On Wed, Jul 22, 2015 at 3:08 PM, Kate Fissell <fissell at pitt.edu
>     <mailto:fissell at pitt.edu>> wrote:
>     >> Hi,
>     >>
>     >> On Paraview versions 4.1 and greater if I ssh -X from a Centos
>     machine into
>     >> an Ubuntu
>     >> graphics server to run Paraview I have a problem with viewing
>     images.
>     >>
>     >> I load the AnalyzeNifTIIO plugin, and load a nifti image, and I
>     believe it
>     >> loads correctly.
>     >> I get the wireframe, the Information panel gives the correct
>     cells/point.
>     >> If I change to
>     >> Slice representation the view window stays blank. Volume
>     representation is
>     >> fine, I get the
>     >> 3D rendering.
>     >> Same thing if I load a vti format of the data, no slice view.
>     >>
>     >> This happens when I ssh from a Centos machine, it does not
>     happen when I ssh
>     >> from
>     >> an Ubuntu machine.   In both cases I believe I am using glx to
>     do the
>     >> rendering locally,
>     >> not doing a setenv DISPLAY to ship the rendered picture over
>     the net.
>     >> It is the same glx version on the Ubuntu and Centos machine,
>     but they have
>     >> different
>     >> graphics cards.
>     >>
>     >> Ubuntu server running Paraview (console graphics):
>     >> OpenGL vendor string: NVIDIA Corporation
>     >> OpenGL renderer string: Quadro K4000/PCIe/SSE2
>     >> OpenGL core profile version string: 4.3.0 NVIDIA 331.113
>     >> OpenGL core profile shading language version string: 4.30
>     NVIDIA via Cg
>     >> compiler
>     >> OpenGL core profile context flags: (none)
>     >> OpenGL core profile profile mask: core profile
>     >> OpenGL core profile extensions:
>     >> OpenGL version string: 4.4.0 NVIDIA 331.113
>     >> OpenGL shading language version string: 4.40 NVIDIA via Cg compiler
>     >> OpenGL context flags: (none)
>     >> OpenGL profile mask: (none)
>     >> OpenGL extensions:
>     >>
>     >>
>     >> Centos machine ssh'd to Ubuntu server:
>     >> OpenGL vendor string: NVIDIA Corporation
>     >> OpenGL renderer string: Quadro FX 580/PCIe/SSE2
>     >> OpenGL version string: 2.1.2 NVIDIA 340.76
>     >> OpenGL shading language version string: 1.20 NVIDIA via Cg compiler
>     >> OpenGL extensions:
>     >>
>     >>
>     >> Ubuntu machine ssh'd to Ubuntu server:
>     >> OpenGL vendor string: NVIDIA Corporation
>     >> OpenGL renderer string: Quadro K4000/PCIe/SSE2
>     >> OpenGL version string: 2.1.2 NVIDIA 304.125
>     >> OpenGL shading language version string: 1.20 NVIDIA via Cg compiler
>     >> OpenGL extensions:
>     >>
>     >>
>     >> In Paraview ParaView-v4.0.1 I do not have this problem.
>     >> I have the problem in Paraview-4.1, 4.2, 4.3.
>     >>
>     >> I am using your pre-compiled binaries as test, but I have the
>     same problem
>     >> with my compilation.
>     >>
>     >> Do you know what changed from ParaView-v4.0.1 to ParaView-v4.1
>     that would
>     >> cause
>     >> this or what the workaround is ?
>     >>
>     >> thanks
>     >> Kate
>     >> _______________________________________________
>     >> 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
>

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

From eric.g.younkin at noaa.gov  Fri Jul 24 22:45:30 2015
From: eric.g.younkin at noaa.gov (Eric Younkin - NOAA Federal)
Date: Fri, 24 Jul 2015 22:45:30 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAOqyOuES4fYzufraBhnXgpJRQ1RH23FLZgeCOMbzLT=VUjZpSA@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <mo2q49$4gt$1@ger.gmane.org>
 <CAOqyOuGT2uONXRjPd80bJOBdnhugTMyyUCHGn6s8H4Aw+i1wOg@mail.gmail.com>
 <CAFe6qKgK_grq0Vzo0kF8NgiGxU_4T9_6jQrfij3=yZr9y27CEQ@mail.gmail.com>
 <CAFe6qKh_Xs66xKSNX=1Dqz00DBuXk6vOUrDKnxZRcE8_pNkp7A@mail.gmail.com>
 <CAOqyOuES4fYzufraBhnXgpJRQ1RH23FLZgeCOMbzLT=VUjZpSA@mail.gmail.com>
Message-ID: <CAFe6qKjn0xwjT8L=Va6_bLx85LmEdTAuV9z0nUMjSmRsnqk2mw@mail.gmail.com>

Casey,

Understood.  I will continue to look into it.

I have run into another roadblock that I was thinking you might
understand.  I have the following VTK libraries linked in all of my PCL
solution projects with the incorrect name:

They show up as:
vtkutilitiespythoninitializer.lib
vtkSciberQuest.lib
vtkQvis.lib
vtkPVPythonCatalyst.lib
vtkPVCatalystTestDriver.lib
vtkPointSpriteRendering.lib
vtkPointSpriteGraphics.lib
vtkeyedomelighting.lib

When they should show up as:
C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\lib\Debug\vtkEyeDomeLighting-pv4.3.lib
C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\lib\Debug\vtkPointSpriteGraphics-pv4.3.lib
C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\lib\Debug\vtkPointSpriteRendering-pv4.3.lib
C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\lib\Debug\vtkPVPythonCatalyst-pv4.3.lib
C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\lib\Debug\vtkQvis-pv4.3.lib
C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\lib\Debug\vtkSciberQuest-pv4.3.lib
C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\lib\Debug\vtkUtilitiesPythonInitializer-pv4.3.lib

I can't seem to find where these libraries are originally linked on
configuration.  Am I missing something in CMake?  Is there a particular
CMake file that addresses all of these?

Thanks,
Eric

On Mon, Jul 20, 2015 at 11:23 AM, Casey Goodlett <casey.goodlett at kitware.com
> wrote:

> Eric,
>
> I am not familiar with the state of ParaView and Qt5 to be able to help.
> I believe there was a status update on the paraview-developers list
> recently.
>
> Regards,
>
> --
> Casey B Goodlett, PhD
> Technical Leader
> Kitware, Inc. - North Carolina Office
> http://www.kitware.com
> (919) 969-6990 x310
>



-- 
Eric Younkin LTJG/NOAA
HSTP Liaison - East
Marine Operations Center - Atlantic
439 W York St
Norfolk, VA 23510
Cell: 828-331-8197
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150724/294e8f05/attachment-0001.html>

From S.R.Kharche at exeter.ac.uk  Sat Jul 25 11:30:40 2015
From: S.R.Kharche at exeter.ac.uk (Kharche, Sanjay)
Date: Sat, 25 Jul 2015 15:30:40 +0000
Subject: [Paraview] non-interactive viz on cluster
In-Reply-To: <CANjZAi_VRp_+_Xe0g9e8X3025HijeEtEWRNgckGmYChzvKnjHg@mail.gmail.com>
References: <mocupi$4m1$1@ger.gmane.org>
 <VI1PR03MB10718AA847D1243BC64882FD82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi8Cf76WG94RxsF=BytrX-03xRG70s2-eGpAX0mzAmTHfQ@mail.gmail.com>
 <VI1PR03MB107148468CDDC0E8ABA82C2E82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi-NEtA9gUL-UXGyW87PCWpAFd2qAzhc-2gLDmxBmK+qHA@mail.gmail.com>
 <DB5PR03MB1062F8ED89F963E50A4CD20C82820@DB5PR03MB1062.eurprd03.prod.outlook.com>,
 <CANjZAi_VRp_+_Xe0g9e8X3025HijeEtEWRNgckGmYChzvKnjHg@mail.gmail.com>
Message-ID: <VI1PR03MB10710503D70C59E000DEFE5782800@VI1PR03MB1071.eurprd03.prod.outlook.com>


Dear David, All

I am now using VNC and got my scripts to do non-interactive viz, i.e.
making of png files using the script below. However, I have a question
regarding efficiency of the run.

As of now, I am doing a serial run. The first several png files are produced
swiftly. However, eventually, the run slows down considerably.
e.g. files 1 to 200 are at a rate of 10 per second
but files 300 to 35 are almost 1 every 2 minutes.#

Any ideas why this is, and how to rectify this? Isthis a memory leak and if so
how not do introduce this when making the .py script using the trace option
in the GUI?

cheers
Sanjay


line in pbs script:

# now any X11 traffic is sent to the VNC server.
pvbatch --use-offscreen-rendering sk3d.py &


my sk3d.py script:

try: paraview.simple
except: from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()

for i in range (415,3998):
    RenderView1 = GetRenderView()
    HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' % (i)] )
    RenderView1.CenterAxesVisibility = 0
    RenderView1.OrientationAxesVisibility = 0
    RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117]
    RenderView1.Background = [1.0, 1.0, 1.0]
    DataRepresentation1 = Show()
    DataRepresentation1.ScalarOpacityUnitDistance = 2.184824466829962
    DataRepresentation1.Representation = 'Outline'
    DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
    RenderView1.CenterOfRotation = [63.5, 63.5, 59.0]
    a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0, 0.7059976962405788, 0.016126465515202103, 0.15000112339188484], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
    a1_voltage_PiecewiseFunction = CreatePiecewiseFunction()
    RenderView1.CameraPosition = [63.5, -351.65487519135064, 59.0]
    RenderView1.CameraViewUp = [0.0, 0.0, 1.0]
    RenderView1.CameraFocalPoint = [63.5, 63.5, 59.0]
    RenderView1.CameraClippingRange = [284.63832643943715, 580.4496983192209]
    RenderView1.CameraParallelScale = 107.44998836668155
    DataRepresentation1.Representation = 'Volume'
    DataRepresentation1.ScalarOpacityFunction = a1_voltage_PiecewiseFunction
    DataRepresentation1.ColorArrayName = 'voltage'
    DataRepresentation1.LookupTable = a1_voltage_PVLookupTable
    Render()
    WriteImage("Endo_dir_%06i.png" % (i))
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150725/c426089b/attachment.html>

From dave.demarle at kitware.com  Sat Jul 25 11:47:40 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Sat, 25 Jul 2015 11:47:40 -0400
Subject: [Paraview] non-interactive viz on cluster
In-Reply-To: <VI1PR03MB10710503D70C59E000DEFE5782800@VI1PR03MB1071.eurprd03.prod.outlook.com>
References: <mocupi$4m1$1@ger.gmane.org>
 <VI1PR03MB10718AA847D1243BC64882FD82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi8Cf76WG94RxsF=BytrX-03xRG70s2-eGpAX0mzAmTHfQ@mail.gmail.com>
 <VI1PR03MB107148468CDDC0E8ABA82C2E82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi-NEtA9gUL-UXGyW87PCWpAFd2qAzhc-2gLDmxBmK+qHA@mail.gmail.com>
 <DB5PR03MB1062F8ED89F963E50A4CD20C82820@DB5PR03MB1062.eurprd03.prod.outlook.com>
 <CANjZAi_VRp_+_Xe0g9e8X3025HijeEtEWRNgckGmYChzvKnjHg@mail.gmail.com>
 <VI1PR03MB10710503D70C59E000DEFE5782800@VI1PR03MB1071.eurprd03.prod.outlook.com>
Message-ID: <CANjZAi__bBiq_DtxzXpHLM4gE5z0gHWzcmkb-tuzf_8bm7rmiA@mail.gmail.com>

I think your memory usage is growing with each iteration, Try moving
everything out of the loop and then just changing what you have to in the
fixed pipeline inside the loop.


i = 415
RenderView1 = GetRenderView()
?
Render()
WriteImage("Endo_dir_%06i.png" % (i))
for i in range(416?):
   HumanSAN000001_vtk.FileName='HumanSAN%06i.vtk' % (i)
   a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1,
NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0,
0.7059976962405788, 0.016126465515202103, 0.15000112339188484],
VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
   Render()
   WriteImage?


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Sat, Jul 25, 2015 at 11:30 AM, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk>
wrote:

>
> Dear David, All
>
> I am now using VNC and got my scripts to do non-interactive viz, i.e.
> making of png files using the script below. However, I have a question
> regarding efficiency of the run.
>
> As of now, I am doing a serial run. The first several png files are
> produced
> swiftly. However, eventually, the run slows down considerably.
> e.g. files 1 to 200 are at a rate of 10 per second
> but files 300 to 35 are almost 1 every 2 minutes.#
>
> Any ideas why this is, and how to rectify this? Isthis a memory leak and
> if so
> how not do introduce this when making the .py script using the trace option
> in the GUI?
>
> cheers
> Sanjay
>
>
> line in pbs script:
>
> # now any X11 traffic is sent to the VNC server.
> pvbatch --use-offscreen-rendering sk3d.py &
>
>
> my sk3d.py script:
>
> try: paraview.simple
> except: from paraview.simple import *
> paraview.simple._DisableFirstRenderCameraReset()
>
> for i in range (415,3998):
>     RenderView1 = GetRenderView()
>     HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' %
> (i)] )
>     RenderView1.CenterAxesVisibility = 0
>     RenderView1.OrientationAxesVisibility = 0
>     RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117]
>     RenderView1.Background = [1.0, 1.0, 1.0]
>     DataRepresentation1 = Show()
>     DataRepresentation1.ScalarOpacityUnitDistance = 2.184824466829962
>     DataRepresentation1.Representation = 'Outline'
>     DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
>     RenderView1.CenterOfRotation = [63.5, 63.5, 59.0]
>     a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1,
> NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0,
> 0.7059976962405788, 0.016126465515202103, 0.15000112339188484],
> VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
>     a1_voltage_PiecewiseFunction = CreatePiecewiseFunction()
>     RenderView1.CameraPosition = [63.5, -351.65487519135064, 59.0]
>     RenderView1.CameraViewUp = [0.0, 0.0, 1.0]
>     RenderView1.CameraFocalPoint = [63.5, 63.5, 59.0]
>     RenderView1.CameraClippingRange = [284.63832643943715,
> 580.4496983192209]
>     RenderView1.CameraParallelScale = 107.44998836668155
>     DataRepresentation1.Representation = 'Volume'
>     DataRepresentation1.ScalarOpacityFunction =
> a1_voltage_PiecewiseFunction
>     DataRepresentation1.ColorArrayName = 'voltage'
>     DataRepresentation1.LookupTable = a1_voltage_PVLookupTable
>     Render()
>     WriteImage("Endo_dir_%06i.png" % (i))
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150725/2bd2db1d/attachment.html>

From S.R.Kharche at exeter.ac.uk  Sat Jul 25 16:02:54 2015
From: S.R.Kharche at exeter.ac.uk (Kharche, Sanjay)
Date: Sat, 25 Jul 2015 20:02:54 +0000
Subject: [Paraview] non-interactive viz on cluster
In-Reply-To: <CANjZAi__bBiq_DtxzXpHLM4gE5z0gHWzcmkb-tuzf_8bm7rmiA@mail.gmail.com>
References: <mocupi$4m1$1@ger.gmane.org>
 <VI1PR03MB10718AA847D1243BC64882FD82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi8Cf76WG94RxsF=BytrX-03xRG70s2-eGpAX0mzAmTHfQ@mail.gmail.com>
 <VI1PR03MB107148468CDDC0E8ABA82C2E82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi-NEtA9gUL-UXGyW87PCWpAFd2qAzhc-2gLDmxBmK+qHA@mail.gmail.com>
 <DB5PR03MB1062F8ED89F963E50A4CD20C82820@DB5PR03MB1062.eurprd03.prod.outlook.com>
 <CANjZAi_VRp_+_Xe0g9e8X3025HijeEtEWRNgckGmYChzvKnjHg@mail.gmail.com>
 <VI1PR03MB10710503D70C59E000DEFE5782800@VI1PR03MB1071.eurprd03.prod.outlook.com>,
 <CANjZAi__bBiq_DtxzXpHLM4gE5z0gHWzcmkb-tuzf_8bm7rmiA@mail.gmail.com>
Message-ID: <VI1PR03MB1071D1C4DD460F63439255DC82800@VI1PR03MB1071.eurprd03.prod.outlook.com>


I just did that, and the 4000 file run finished in 15 minutes!


Just for completeness, I would like to know this: What was the part in my

script that was allocating memory at each call of the iteration, causing

a progressive increase of memory use (and thus time)?


I could take a guess, but that would just be a guess, so any responses

are appreciated.


cheers

Sanjay




________________________________
From: David E DeMarle <dave.demarle at kitware.com>
Sent: 25 July 2015 03:47
To: Kharche, Sanjay
Cc: paraview at paraview.org
Subject: Re: [Paraview] non-interactive viz on cluster

I think your memory usage is growing with each iteration, Try moving everything out of the loop and then just changing what you have to in the fixed pipeline inside the loop.


i = 415
RenderView1 = GetRenderView()
...
Render()
WriteImage("Endo_dir_%06i.png" % (i))
for i in range(416...):
   HumanSAN000001_vtk.FileName='HumanSAN%06i.vtk' % (i)
   a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0, 0.7059976962405788, 0.016126465515202103, 0.15000112339188484], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
   Render()
   WriteImage...


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Sat, Jul 25, 2015 at 11:30 AM, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk<mailto:S.R.Kharche at exeter.ac.uk>> wrote:

Dear David, All

I am now using VNC and got my scripts to do non-interactive viz, i.e.
making of png files using the script below. However, I have a question
regarding efficiency of the run.

As of now, I am doing a serial run. The first several png files are produced
swiftly. However, eventually, the run slows down considerably.
e.g. files 1 to 200 are at a rate of 10 per second
but files 300 to 35 are almost 1 every 2 minutes.#

Any ideas why this is, and how to rectify this? Isthis a memory leak and if so
how not do introduce this when making the .py script using the trace option
in the GUI?

cheers
Sanjay


line in pbs script:

# now any X11 traffic is sent to the VNC server.
pvbatch --use-offscreen-rendering sk3d.py &


my sk3d.py script:

try: paraview.simple
except: from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()

for i in range (415,3998):
    RenderView1 = GetRenderView()
    HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' % (i)] )
    RenderView1.CenterAxesVisibility = 0
    RenderView1.OrientationAxesVisibility = 0
    RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117]
    RenderView1.Background = [1.0, 1.0, 1.0]
    DataRepresentation1 = Show()
    DataRepresentation1.ScalarOpacityUnitDistance = 2.184824466829962
    DataRepresentation1.Representation = 'Outline'
    DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
    RenderView1.CenterOfRotation = [63.5, 63.5, 59.0]
    a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0, 0.7059976962405788, 0.016126465515202103, 0.15000112339188484], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
    a1_voltage_PiecewiseFunction = CreatePiecewiseFunction()
    RenderView1.CameraPosition = [63.5, -351.65487519135064, 59.0]
    RenderView1.CameraViewUp = [0.0, 0.0, 1.0]
    RenderView1.CameraFocalPoint = [63.5, 63.5, 59.0]
    RenderView1.CameraClippingRange = [284.63832643943715, 580.4496983192209]
    RenderView1.CameraParallelScale = 107.44998836668155
    DataRepresentation1.Representation = 'Volume'
    DataRepresentation1.ScalarOpacityFunction = a1_voltage_PiecewiseFunction
    DataRepresentation1.ColorArrayName = 'voltage'
    DataRepresentation1.LookupTable = a1_voltage_PVLookupTable
    Render()
    WriteImage("Endo_dir_%06i.png" % (i))

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

From S.R.Kharche at exeter.ac.uk  Sat Jul 25 16:18:34 2015
From: S.R.Kharche at exeter.ac.uk (Kharche, Sanjay)
Date: Sat, 25 Jul 2015 20:18:34 +0000
Subject: [Paraview] non-interactive viz on cluster
In-Reply-To: <CANjZAi__bBiq_DtxzXpHLM4gE5z0gHWzcmkb-tuzf_8bm7rmiA@mail.gmail.com>
References: <mocupi$4m1$1@ger.gmane.org>
 <VI1PR03MB10718AA847D1243BC64882FD82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi8Cf76WG94RxsF=BytrX-03xRG70s2-eGpAX0mzAmTHfQ@mail.gmail.com>
 <VI1PR03MB107148468CDDC0E8ABA82C2E82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi-NEtA9gUL-UXGyW87PCWpAFd2qAzhc-2gLDmxBmK+qHA@mail.gmail.com>
 <DB5PR03MB1062F8ED89F963E50A4CD20C82820@DB5PR03MB1062.eurprd03.prod.outlook.com>
 <CANjZAi_VRp_+_Xe0g9e8X3025HijeEtEWRNgckGmYChzvKnjHg@mail.gmail.com>
 <VI1PR03MB10710503D70C59E000DEFE5782800@VI1PR03MB1071.eurprd03.prod.outlook.com>,
 <CANjZAi__bBiq_DtxzXpHLM4gE5z0gHWzcmkb-tuzf_8bm7rmiA@mail.gmail.com>
Message-ID: <VI1PR03MB10717FD5A5B11CFA8950FCB882800@VI1PR03MB1071.eurprd03.prod.outlook.com>


I think I started celebrations too soon. The images are identical to the

first image. I have tried a few combinations, but could not find any solution.


The script:


try: paraview.simple
except: from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()

i = 1
RenderView1 = GetRenderView()
HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' % (i)] )
RenderView1.CenterAxesVisibility = 0
RenderView1.OrientationAxesVisibility = 0
RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117]
RenderView1.Background = [1.0, 1.0, 1.0]
DataRepresentation1 = Show()
DataRepresentation1.ScalarOpacityUnitDistance = 2.184824466829962
DataRepresentation1.Representation = 'Outline'
DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
RenderView1.CenterOfRotation = [63.5, 63.5, 59.0]
a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0, 0.7059976962405788, 0.016126465515202103, 0.15000112339188484], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
a1_voltage_PiecewiseFunction = CreatePiecewiseFunction()
RenderView1.CameraPosition = [63.5, -351.65487519135064, 59.0]
RenderView1.CameraViewUp = [0.0, 0.0, 1.0]
RenderView1.CameraFocalPoint = [63.5, 63.5, 59.0]
RenderView1.CameraClippingRange = [284.63832643943715, 580.4496983192209]
RenderView1.CameraParallelScale = 107.44998836668155
DataRepresentation1.Representation = 'Volume'
DataRepresentation1.ScalarOpacityFunction = a1_voltage_PiecewiseFunction
DataRepresentation1.ColorArrayName = 'voltage'
DataRepresentation1.LookupTable = a1_voltage_PVLookupTable
Render()
WriteImage("Endo_dir_%06i.png" % (i))
for j in range (2,3998):
    HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' % (j)] )
    a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0, 0.7059976962405788, 0.016126465515202103, 0.15000112339188484], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
    Render()
    WriteImage("Endo_dir_%06i.png" % (j))



________________________________
From: David E DeMarle <dave.demarle at kitware.com>
Sent: 25 July 2015 03:47
To: Kharche, Sanjay
Cc: paraview at paraview.org
Subject: Re: [Paraview] non-interactive viz on cluster

I think your memory usage is growing with each iteration, Try moving everything out of the loop and then just changing what you have to in the fixed pipeline inside the loop.


i = 415
RenderView1 = GetRenderView()
?
Render()
WriteImage("Endo_dir_%06i.png" % (i))
for i in range(416?):
   HumanSAN000001_vtk.FileName='HumanSAN%06i.vtk' % (i)
   a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0, 0.7059976962405788, 0.016126465515202103, 0.15000112339188484], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
   Render()
   WriteImage?


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Sat, Jul 25, 2015 at 11:30 AM, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk<mailto:S.R.Kharche at exeter.ac.uk>> wrote:

Dear David, All

I am now using VNC and got my scripts to do non-interactive viz, i.e.
making of png files using the script below. However, I have a question
regarding efficiency of the run.

As of now, I am doing a serial run. The first several png files are produced
swiftly. However, eventually, the run slows down considerably.
e.g. files 1 to 200 are at a rate of 10 per second
but files 300 to 35 are almost 1 every 2 minutes.#

Any ideas why this is, and how to rectify this? Isthis a memory leak and if so
how not do introduce this when making the .py script using the trace option
in the GUI?

cheers
Sanjay


line in pbs script:

# now any X11 traffic is sent to the VNC server.
pvbatch --use-offscreen-rendering sk3d.py &


my sk3d.py script:

try: paraview.simple
except: from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()

for i in range (415,3998):
    RenderView1 = GetRenderView()
    HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' % (i)] )
    RenderView1.CenterAxesVisibility = 0
    RenderView1.OrientationAxesVisibility = 0
    RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117]
    RenderView1.Background = [1.0, 1.0, 1.0]
    DataRepresentation1 = Show()
    DataRepresentation1.ScalarOpacityUnitDistance = 2.184824466829962
    DataRepresentation1.Representation = 'Outline'
    DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
    RenderView1.CenterOfRotation = [63.5, 63.5, 59.0]
    a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0, 0.7059976962405788, 0.016126465515202103, 0.15000112339188484], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
    a1_voltage_PiecewiseFunction = CreatePiecewiseFunction()
    RenderView1.CameraPosition = [63.5, -351.65487519135064, 59.0]
    RenderView1.CameraViewUp = [0.0, 0.0, 1.0]
    RenderView1.CameraFocalPoint = [63.5, 63.5, 59.0]
    RenderView1.CameraClippingRange = [284.63832643943715, 580.4496983192209]
    RenderView1.CameraParallelScale = 107.44998836668155
    DataRepresentation1.Representation = 'Volume'
    DataRepresentation1.ScalarOpacityFunction = a1_voltage_PiecewiseFunction
    DataRepresentation1.ColorArrayName = 'voltage'
    DataRepresentation1.LookupTable = a1_voltage_PVLookupTable
    Render()
    WriteImage("Endo_dir_%06i.png" % (i))

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

From dave.demarle at kitware.com  Sat Jul 25 16:22:38 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Sat, 25 Jul 2015 16:22:38 -0400
Subject: [Paraview] non-interactive viz on cluster
In-Reply-To: <VI1PR03MB1071D1C4DD460F63439255DC82800@VI1PR03MB1071.eurprd03.prod.outlook.com>
References: <mocupi$4m1$1@ger.gmane.org>
 <VI1PR03MB10718AA847D1243BC64882FD82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi8Cf76WG94RxsF=BytrX-03xRG70s2-eGpAX0mzAmTHfQ@mail.gmail.com>
 <VI1PR03MB107148468CDDC0E8ABA82C2E82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi-NEtA9gUL-UXGyW87PCWpAFd2qAzhc-2gLDmxBmK+qHA@mail.gmail.com>
 <DB5PR03MB1062F8ED89F963E50A4CD20C82820@DB5PR03MB1062.eurprd03.prod.outlook.com>
 <CANjZAi_VRp_+_Xe0g9e8X3025HijeEtEWRNgckGmYChzvKnjHg@mail.gmail.com>
 <VI1PR03MB10710503D70C59E000DEFE5782800@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi__bBiq_DtxzXpHLM4gE5z0gHWzcmkb-tuzf_8bm7rmiA@mail.gmail.com>
 <VI1PR03MB1071D1C4DD460F63439255DC82800@VI1PR03MB1071.eurprd03.prod.outlook.com>
Message-ID: <CANjZAi-i_61ybu942UnVs1AzPjBtc0zDPmdAhryQObtXx=ZbZg@mail.gmail.com>

I think it was the new reader each iteration, and also possibly the new
representation (output of Show()).
They stick around because of reference counting, even when they go out of
scope the view still has access to them, so they aren't deallocated.

hth and glad to got it working!




David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Sat, Jul 25, 2015 at 4:02 PM, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk>
wrote:

>
>  I just did that, and the 4000 file run finished in 15 minutes!
>
>
>  Just for completeness, I would like to know this: What was the part in my
>
> script that was allocating memory at each call of the iteration, causing
>
> a progressive increase of memory use (and thus time)?
>
>
>  I could take a guess, but that would just be a guess, so any responses
>
> are appreciated.
>
>
>  cheers
>
> Sanjay
>
>
>
>
>
>  ------------------------------
> *From:* David E DeMarle <dave.demarle at kitware.com>
> *Sent:* 25 July 2015 03:47
> *To:* Kharche, Sanjay
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] non-interactive viz on cluster
>
>  I think your memory usage is growing with each iteration, Try moving
> everything out of the loop and then just changing what you have to in the
> fixed pipeline inside the loop.
>
>
> i = 415
> RenderView1 = GetRenderView()
> ?
> Render()
> WriteImage("Endo_dir_%06i.png" % (i))
> for i in range(416?):
>    HumanSAN000001_vtk.FileName='HumanSAN%06i.vtk' % (i)
>    a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1,
> NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0,
> 0.7059976962405788, 0.016126465515202103, 0.15000112339188484],
> VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
>    Render()
>    WriteImage?
>
>
>  David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Sat, Jul 25, 2015 at 11:30 AM, Kharche, Sanjay <
> S.R.Kharche at exeter.ac.uk> wrote:
>
>>
>> Dear David, All
>>
>> I am now using VNC and got my scripts to do non-interactive viz, i.e.
>> making of png files using the script below. However, I have a question
>> regarding efficiency of the run.
>>
>> As of now, I am doing a serial run. The first several png files are
>> produced
>> swiftly. However, eventually, the run slows down considerably.
>> e.g. files 1 to 200 are at a rate of 10 per second
>> but files 300 to 35 are almost 1 every 2 minutes.#
>>
>> Any ideas why this is, and how to rectify this? Isthis a memory leak and
>> if so
>> how not do introduce this when making the .py script using the trace
>> option
>> in the GUI?
>>
>> cheers
>> Sanjay
>>
>>
>> line in pbs script:
>>
>> # now any X11 traffic is sent to the VNC server.
>> pvbatch --use-offscreen-rendering sk3d.py &
>>
>>
>> my sk3d.py script:
>>
>> try: paraview.simple
>> except: from paraview.simple import *
>> paraview.simple._DisableFirstRenderCameraReset()
>>
>> for i in range (415,3998):
>>     RenderView1 = GetRenderView()
>>     HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' %
>> (i)] )
>>     RenderView1.CenterAxesVisibility = 0
>>     RenderView1.OrientationAxesVisibility = 0
>>     RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117]
>>     RenderView1.Background = [1.0, 1.0, 1.0]
>>     DataRepresentation1 = Show()
>>     DataRepresentation1.ScalarOpacityUnitDistance = 2.184824466829962
>>     DataRepresentation1.Representation = 'Outline'
>>     DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
>>     RenderView1.CenterOfRotation = [63.5, 63.5, 59.0]
>>     a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1,
>> NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0,
>> 0.7059976962405788, 0.016126465515202103, 0.15000112339188484],
>> VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
>>     a1_voltage_PiecewiseFunction = CreatePiecewiseFunction()
>>     RenderView1.CameraPosition = [63.5, -351.65487519135064, 59.0]
>>     RenderView1.CameraViewUp = [0.0, 0.0, 1.0]
>>     RenderView1.CameraFocalPoint = [63.5, 63.5, 59.0]
>>     RenderView1.CameraClippingRange = [284.63832643943715,
>> 580.4496983192209]
>>     RenderView1.CameraParallelScale = 107.44998836668155
>>     DataRepresentation1.Representation = 'Volume'
>>     DataRepresentation1.ScalarOpacityFunction =
>> a1_voltage_PiecewiseFunction
>>     DataRepresentation1.ColorArrayName = 'voltage'
>>     DataRepresentation1.LookupTable = a1_voltage_PVLookupTable
>>     Render()
>>     WriteImage("Endo_dir_%06i.png" % (i))
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150725/b7d1c66b/attachment.html>

From dave.demarle at kitware.com  Sat Jul 25 16:24:40 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Sat, 25 Jul 2015 16:24:40 -0400
Subject: [Paraview] non-interactive viz on cluster
In-Reply-To: <VI1PR03MB10717FD5A5B11CFA8950FCB882800@VI1PR03MB1071.eurprd03.prod.outlook.com>
References: <mocupi$4m1$1@ger.gmane.org>
 <VI1PR03MB10718AA847D1243BC64882FD82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi8Cf76WG94RxsF=BytrX-03xRG70s2-eGpAX0mzAmTHfQ@mail.gmail.com>
 <VI1PR03MB107148468CDDC0E8ABA82C2E82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi-NEtA9gUL-UXGyW87PCWpAFd2qAzhc-2gLDmxBmK+qHA@mail.gmail.com>
 <DB5PR03MB1062F8ED89F963E50A4CD20C82820@DB5PR03MB1062.eurprd03.prod.outlook.com>
 <CANjZAi_VRp_+_Xe0g9e8X3025HijeEtEWRNgckGmYChzvKnjHg@mail.gmail.com>
 <VI1PR03MB10710503D70C59E000DEFE5782800@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi__bBiq_DtxzXpHLM4gE5z0gHWzcmkb-tuzf_8bm7rmiA@mail.gmail.com>
 <VI1PR03MB10717FD5A5B11CFA8950FCB882800@VI1PR03MB1071.eurprd03.prod.outlook.com>
Message-ID: <CANjZAi_8VtoYQww3ZBxosCoqLnKONDCx-H02e_WFaf6YeB-A-w@mail.gmail.com>

You are making a new reader, but never connecting it to the View.

not:
  HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' %
(j)] )
rather
  HumanSAN000001_vtk.FileNames=['HumanSAN%06i.vtk' % (j)]

try that



David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Sat, Jul 25, 2015 at 4:18 PM, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk>
wrote:

>
>  I think I started celebrations too soon. The images are identical to the
>
> first image. I have tried a few combinations, but could not find any
> solution.
>
>
>  The script:
>
>
>  try: paraview.simple
> except: from paraview.simple import *
> paraview.simple._DisableFirstRenderCameraReset()
>
> i = 1
> RenderView1 = GetRenderView()
> HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' % (i)]
> )
> RenderView1.CenterAxesVisibility = 0
> RenderView1.OrientationAxesVisibility = 0
> RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117]
> RenderView1.Background = [1.0, 1.0, 1.0]
> DataRepresentation1 = Show()
> DataRepresentation1.ScalarOpacityUnitDistance = 2.184824466829962
> DataRepresentation1.Representation = 'Outline'
> DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
> RenderView1.CenterOfRotation = [63.5, 63.5, 59.0]
> a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1,
> NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0,
> 0.7059976962405788, 0.016126465515202103, 0.15000112339188484],
> VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
> a1_voltage_PiecewiseFunction = CreatePiecewiseFunction()
> RenderView1.CameraPosition = [63.5, -351.65487519135064, 59.0]
> RenderView1.CameraViewUp = [0.0, 0.0, 1.0]
> RenderView1.CameraFocalPoint = [63.5, 63.5, 59.0]
> RenderView1.CameraClippingRange = [284.63832643943715, 580.4496983192209]
> RenderView1.CameraParallelScale = 107.44998836668155
> DataRepresentation1.Representation = 'Volume'
> DataRepresentation1.ScalarOpacityFunction = a1_voltage_PiecewiseFunction
> DataRepresentation1.ColorArrayName = 'voltage'
> DataRepresentation1.LookupTable = a1_voltage_PVLookupTable
> Render()
> WriteImage("Endo_dir_%06i.png" % (i))
> for j in range (2,3998):
>     HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' %
> (j)] )
>     a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1,
> NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0,
> 0.7059976962405788, 0.016126465515202103, 0.15000112339188484],
> VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
>     Render()
>     WriteImage("Endo_dir_%06i.png" % (j))
>
>
>
>  ------------------------------
> *From:* David E DeMarle <dave.demarle at kitware.com>
> *Sent:* 25 July 2015 03:47
> *To:* Kharche, Sanjay
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] non-interactive viz on cluster
>
>  I think your memory usage is growing with each iteration, Try moving
> everything out of the loop and then just changing what you have to in the
> fixed pipeline inside the loop.
>
>
> i = 415
> RenderView1 = GetRenderView()
> ?
> Render()
> WriteImage("Endo_dir_%06i.png" % (i))
> for i in range(416?):
>    HumanSAN000001_vtk.FileName='HumanSAN%06i.vtk' % (i)
>    a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1,
> NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0,
> 0.7059976962405788, 0.016126465515202103, 0.15000112339188484],
> VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
>    Render()
>    WriteImage?
>
>
>  David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Sat, Jul 25, 2015 at 11:30 AM, Kharche, Sanjay <
> S.R.Kharche at exeter.ac.uk> wrote:
>
>>
>> Dear David, All
>>
>> I am now using VNC and got my scripts to do non-interactive viz, i.e.
>> making of png files using the script below. However, I have a question
>> regarding efficiency of the run.
>>
>> As of now, I am doing a serial run. The first several png files are
>> produced
>> swiftly. However, eventually, the run slows down considerably.
>> e.g. files 1 to 200 are at a rate of 10 per second
>> but files 300 to 35 are almost 1 every 2 minutes.#
>>
>> Any ideas why this is, and how to rectify this? Isthis a memory leak and
>> if so
>> how not do introduce this when making the .py script using the trace
>> option
>> in the GUI?
>>
>> cheers
>> Sanjay
>>
>>
>> line in pbs script:
>>
>> # now any X11 traffic is sent to the VNC server.
>> pvbatch --use-offscreen-rendering sk3d.py &
>>
>>
>> my sk3d.py script:
>>
>> try: paraview.simple
>> except: from paraview.simple import *
>> paraview.simple._DisableFirstRenderCameraReset()
>>
>> for i in range (415,3998):
>>     RenderView1 = GetRenderView()
>>     HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' %
>> (i)] )
>>     RenderView1.CenterAxesVisibility = 0
>>     RenderView1.OrientationAxesVisibility = 0
>>     RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117]
>>     RenderView1.Background = [1.0, 1.0, 1.0]
>>     DataRepresentation1 = Show()
>>     DataRepresentation1.ScalarOpacityUnitDistance = 2.184824466829962
>>     DataRepresentation1.Representation = 'Outline'
>>     DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
>>     RenderView1.CenterOfRotation = [63.5, 63.5, 59.0]
>>     a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1,
>> NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0,
>> 0.7059976962405788, 0.016126465515202103, 0.15000112339188484],
>> VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
>>     a1_voltage_PiecewiseFunction = CreatePiecewiseFunction()
>>     RenderView1.CameraPosition = [63.5, -351.65487519135064, 59.0]
>>     RenderView1.CameraViewUp = [0.0, 0.0, 1.0]
>>     RenderView1.CameraFocalPoint = [63.5, 63.5, 59.0]
>>     RenderView1.CameraClippingRange = [284.63832643943715,
>> 580.4496983192209]
>>     RenderView1.CameraParallelScale = 107.44998836668155
>>     DataRepresentation1.Representation = 'Volume'
>>     DataRepresentation1.ScalarOpacityFunction =
>> a1_voltage_PiecewiseFunction
>>     DataRepresentation1.ColorArrayName = 'voltage'
>>     DataRepresentation1.LookupTable = a1_voltage_PVLookupTable
>>     Render()
>>     WriteImage("Endo_dir_%06i.png" % (i))
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150725/ed8e5bf5/attachment.html>

From S.R.Kharche at exeter.ac.uk  Sat Jul 25 16:29:34 2015
From: S.R.Kharche at exeter.ac.uk (Kharche, Sanjay)
Date: Sat, 25 Jul 2015 20:29:34 +0000
Subject: [Paraview] non-interactive viz on cluster
In-Reply-To: <CANjZAi_8VtoYQww3ZBxosCoqLnKONDCx-H02e_WFaf6YeB-A-w@mail.gmail.com>
References: <mocupi$4m1$1@ger.gmane.org>
 <VI1PR03MB10718AA847D1243BC64882FD82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi8Cf76WG94RxsF=BytrX-03xRG70s2-eGpAX0mzAmTHfQ@mail.gmail.com>
 <VI1PR03MB107148468CDDC0E8ABA82C2E82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi-NEtA9gUL-UXGyW87PCWpAFd2qAzhc-2gLDmxBmK+qHA@mail.gmail.com>
 <DB5PR03MB1062F8ED89F963E50A4CD20C82820@DB5PR03MB1062.eurprd03.prod.outlook.com>
 <CANjZAi_VRp_+_Xe0g9e8X3025HijeEtEWRNgckGmYChzvKnjHg@mail.gmail.com>
 <VI1PR03MB10710503D70C59E000DEFE5782800@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi__bBiq_DtxzXpHLM4gE5z0gHWzcmkb-tuzf_8bm7rmiA@mail.gmail.com>
 <VI1PR03MB10717FD5A5B11CFA8950FCB882800@VI1PR03MB1071.eurprd03.prod.outlook.com>,
 <CANjZAi_8VtoYQww3ZBxosCoqLnKONDCx-H02e_WFaf6YeB-A-w@mail.gmail.com>
Message-ID: <VI1PR03MB1071E2F5675A98E8FCECA77F82800@VI1PR03MB1071.eurprd03.prod.outlook.com>

that was one of the combinations I tried, and it didnt work.


I am looking at the ParaView wiki right now. Appareltly there is a Delete(XX)

which should be used to delete objects. I am trying to work out what to

Delete and what not to delete.


________________________________
From: David E DeMarle <dave.demarle at kitware.com>
Sent: 25 July 2015 08:24
To: Kharche, Sanjay
Cc: paraview at paraview.org
Subject: Re: [Paraview] non-interactive viz on cluster

You are making a new reader, but never connecting it to the View.

not:
  HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' % (j)] )
rather
  HumanSAN000001_vtk.FileNames=['HumanSAN%06i.vtk' % (j)]

try that



David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Sat, Jul 25, 2015 at 4:18 PM, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk<mailto:S.R.Kharche at exeter.ac.uk>> wrote:


I think I started celebrations too soon. The images are identical to the

first image. I have tried a few combinations, but could not find any solution.


The script:


try: paraview.simple
except: from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()

i = 1
RenderView1 = GetRenderView()
HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' % (i)] )
RenderView1.CenterAxesVisibility = 0
RenderView1.OrientationAxesVisibility = 0
RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117]
RenderView1.Background = [1.0, 1.0, 1.0]
DataRepresentation1 = Show()
DataRepresentation1.ScalarOpacityUnitDistance = 2.184824466829962
DataRepresentation1.Representation = 'Outline'
DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
RenderView1.CenterOfRotation = [63.5, 63.5, 59.0]
a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0, 0.7059976962405788, 0.016126465515202103, 0.15000112339188484], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
a1_voltage_PiecewiseFunction = CreatePiecewiseFunction()
RenderView1.CameraPosition = [63.5, -351.65487519135064, 59.0]
RenderView1.CameraViewUp = [0.0, 0.0, 1.0]
RenderView1.CameraFocalPoint = [63.5, 63.5, 59.0]
RenderView1.CameraClippingRange = [284.63832643943715, 580.4496983192209]
RenderView1.CameraParallelScale = 107.44998836668155
DataRepresentation1.Representation = 'Volume'
DataRepresentation1.ScalarOpacityFunction = a1_voltage_PiecewiseFunction
DataRepresentation1.ColorArrayName = 'voltage'
DataRepresentation1.LookupTable = a1_voltage_PVLookupTable
Render()
WriteImage("Endo_dir_%06i.png" % (i))
for j in range (2,3998):
    HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' % (j)] )
    a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0, 0.7059976962405788, 0.016126465515202103, 0.15000112339188484], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
    Render()
    WriteImage("Endo_dir_%06i.png" % (j))



________________________________
From: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>
Sent: 25 July 2015 03:47
To: Kharche, Sanjay
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] non-interactive viz on cluster

I think your memory usage is growing with each iteration, Try moving everything out of the loop and then just changing what you have to in the fixed pipeline inside the loop.


i = 415
RenderView1 = GetRenderView()
?
Render()
WriteImage("Endo_dir_%06i.png" % (i))
for i in range(416?):
   HumanSAN000001_vtk.FileName='HumanSAN%06i.vtk' % (i)
   a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0, 0.7059976962405788, 0.016126465515202103, 0.15000112339188484], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
   Render()
   WriteImage?


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909<tel:518-881-4909>

On Sat, Jul 25, 2015 at 11:30 AM, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk<mailto:S.R.Kharche at exeter.ac.uk>> wrote:

Dear David, All

I am now using VNC and got my scripts to do non-interactive viz, i.e.
making of png files using the script below. However, I have a question
regarding efficiency of the run.

As of now, I am doing a serial run. The first several png files are produced
swiftly. However, eventually, the run slows down considerably.
e.g. files 1 to 200 are at a rate of 10 per second
but files 300 to 35 are almost 1 every 2 minutes.#

Any ideas why this is, and how to rectify this? Isthis a memory leak and if so
how not do introduce this when making the .py script using the trace option
in the GUI?

cheers
Sanjay


line in pbs script:

# now any X11 traffic is sent to the VNC server.
pvbatch --use-offscreen-rendering sk3d.py &


my sk3d.py script:

try: paraview.simple
except: from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()

for i in range (415,3998):
    RenderView1 = GetRenderView()
    HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' % (i)] )
    RenderView1.CenterAxesVisibility = 0
    RenderView1.OrientationAxesVisibility = 0
    RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117]
    RenderView1.Background = [1.0, 1.0, 1.0]
    DataRepresentation1 = Show()
    DataRepresentation1.ScalarOpacityUnitDistance = 2.184824466829962
    DataRepresentation1.Representation = 'Outline'
    DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
    RenderView1.CenterOfRotation = [63.5, 63.5, 59.0]
    a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0, 0.7059976962405788, 0.016126465515202103, 0.15000112339188484], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
    a1_voltage_PiecewiseFunction = CreatePiecewiseFunction()
    RenderView1.CameraPosition = [63.5, -351.65487519135064, 59.0]
    RenderView1.CameraViewUp = [0.0, 0.0, 1.0]
    RenderView1.CameraFocalPoint = [63.5, 63.5, 59.0]
    RenderView1.CameraClippingRange = [284.63832643943715, 580.4496983192209]
    RenderView1.CameraParallelScale = 107.44998836668155
    DataRepresentation1.Representation = 'Volume'
    DataRepresentation1.ScalarOpacityFunction = a1_voltage_PiecewiseFunction
    DataRepresentation1.ColorArrayName = 'voltage'
    DataRepresentation1.LookupTable = a1_voltage_PVLookupTable
    Render()
    WriteImage("Endo_dir_%06i.png" % (i))


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

From dave.demarle at kitware.com  Sat Jul 25 16:34:26 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Sat, 25 Jul 2015 16:34:26 -0400
Subject: [Paraview] non-interactive viz on cluster
In-Reply-To: <VI1PR03MB1071E2F5675A98E8FCECA77F82800@VI1PR03MB1071.eurprd03.prod.outlook.com>
References: <mocupi$4m1$1@ger.gmane.org>
 <VI1PR03MB10718AA847D1243BC64882FD82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi8Cf76WG94RxsF=BytrX-03xRG70s2-eGpAX0mzAmTHfQ@mail.gmail.com>
 <VI1PR03MB107148468CDDC0E8ABA82C2E82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi-NEtA9gUL-UXGyW87PCWpAFd2qAzhc-2gLDmxBmK+qHA@mail.gmail.com>
 <DB5PR03MB1062F8ED89F963E50A4CD20C82820@DB5PR03MB1062.eurprd03.prod.outlook.com>
 <CANjZAi_VRp_+_Xe0g9e8X3025HijeEtEWRNgckGmYChzvKnjHg@mail.gmail.com>
 <VI1PR03MB10710503D70C59E000DEFE5782800@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi__bBiq_DtxzXpHLM4gE5z0gHWzcmkb-tuzf_8bm7rmiA@mail.gmail.com>
 <VI1PR03MB10717FD5A5B11CFA8950FCB882800@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi_8VtoYQww3ZBxosCoqLnKONDCx-H02e_WFaf6YeB-A-w@mail.gmail.com>
 <VI1PR03MB1071E2F5675A98E8FCECA77F82800@VI1PR03MB1071.eurprd03.prod.outlook.com>
Message-ID: <CANjZAi-02oK8Lx5xSXix+qMxm0U7R4cXVPK2H7eExNhqK_RTLw@mail.gmail.com>

Try to do this with some similar data in the python GUI's Tools->Python
Shell on your local machine.

That way you get tab completion and can see things happen in the GUI to
help you learn the syntax.




David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Sat, Jul 25, 2015 at 4:29 PM, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk>
wrote:

>  that was one of the combinations I tried, and it didnt work.
>
>
>  I am looking at the ParaView wiki right now. Appareltly there is a
> Delete(XX)
>
> which should be used to delete objects. I am trying to work out what to
>
> Delete and what not to delete.
>
>
>  ------------------------------
> *From:* David E DeMarle <dave.demarle at kitware.com>
> *Sent:* 25 July 2015 08:24
>
> *To:* Kharche, Sanjay
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] non-interactive viz on cluster
>
>  You are making a new reader, but never connecting it to the View.
>
>  not:
>   HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' %
> (j)] )
> rather
>   HumanSAN000001_vtk.FileNames=['HumanSAN%06i.vtk' % (j)]
>
>  try that
>
>
>
>  David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Sat, Jul 25, 2015 at 4:18 PM, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk
> > wrote:
>
>>
>>  I think I started celebrations too soon. The images are identical to the
>>
>> first image. I have tried a few combinations, but could not find any
>> solution.
>>
>>
>>  The script:
>>
>>
>>  try: paraview.simple
>> except: from paraview.simple import *
>> paraview.simple._DisableFirstRenderCameraReset()
>>
>> i = 1
>> RenderView1 = GetRenderView()
>> HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' %
>> (i)] )
>> RenderView1.CenterAxesVisibility = 0
>> RenderView1.OrientationAxesVisibility = 0
>> RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117]
>> RenderView1.Background = [1.0, 1.0, 1.0]
>> DataRepresentation1 = Show()
>> DataRepresentation1.ScalarOpacityUnitDistance = 2.184824466829962
>> DataRepresentation1.Representation = 'Outline'
>> DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
>> RenderView1.CenterOfRotation = [63.5, 63.5, 59.0]
>> a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1,
>> NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0,
>> 0.7059976962405788, 0.016126465515202103, 0.15000112339188484],
>> VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
>> a1_voltage_PiecewiseFunction = CreatePiecewiseFunction()
>> RenderView1.CameraPosition = [63.5, -351.65487519135064, 59.0]
>> RenderView1.CameraViewUp = [0.0, 0.0, 1.0]
>> RenderView1.CameraFocalPoint = [63.5, 63.5, 59.0]
>> RenderView1.CameraClippingRange = [284.63832643943715, 580.4496983192209]
>> RenderView1.CameraParallelScale = 107.44998836668155
>> DataRepresentation1.Representation = 'Volume'
>> DataRepresentation1.ScalarOpacityFunction = a1_voltage_PiecewiseFunction
>> DataRepresentation1.ColorArrayName = 'voltage'
>> DataRepresentation1.LookupTable = a1_voltage_PVLookupTable
>> Render()
>> WriteImage("Endo_dir_%06i.png" % (i))
>> for j in range (2,3998):
>>     HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' %
>> (j)] )
>>     a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1,
>> NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0,
>> 0.7059976962405788, 0.016126465515202103, 0.15000112339188484],
>> VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
>>     Render()
>>     WriteImage("Endo_dir_%06i.png" % (j))
>>
>>
>>
>>  ------------------------------
>> *From:* David E DeMarle <dave.demarle at kitware.com>
>> *Sent:* 25 July 2015 03:47
>> *To:* Kharche, Sanjay
>> *Cc:* paraview at paraview.org
>> *Subject:* Re: [Paraview] non-interactive viz on cluster
>>
>>   I think your memory usage is growing with each iteration, Try moving
>> everything out of the loop and then just changing what you have to in the
>> fixed pipeline inside the loop.
>>
>>
>> i = 415
>> RenderView1 = GetRenderView()
>> ?
>> Render()
>> WriteImage("Endo_dir_%06i.png" % (i))
>> for i in range(416?):
>>    HumanSAN000001_vtk.FileName='HumanSAN%06i.vtk' % (i)
>>    a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1,
>> NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0,
>> 0.7059976962405788, 0.016126465515202103, 0.15000112339188484],
>> VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
>>    Render()
>>    WriteImage?
>>
>>
>>  David E DeMarle
>> Kitware, Inc.
>> R&D Engineer
>> 21 Corporate Drive
>> Clifton Park, NY 12065-8662
>> Phone: 518-881-4909
>>
>> On Sat, Jul 25, 2015 at 11:30 AM, Kharche, Sanjay <
>> S.R.Kharche at exeter.ac.uk> wrote:
>>
>>>
>>> Dear David, All
>>>
>>> I am now using VNC and got my scripts to do non-interactive viz, i.e.
>>> making of png files using the script below. However, I have a question
>>> regarding efficiency of the run.
>>>
>>> As of now, I am doing a serial run. The first several png files are
>>> produced
>>> swiftly. However, eventually, the run slows down considerably.
>>> e.g. files 1 to 200 are at a rate of 10 per second
>>> but files 300 to 35 are almost 1 every 2 minutes.#
>>>
>>> Any ideas why this is, and how to rectify this? Isthis a memory leak and
>>> if so
>>> how not do introduce this when making the .py script using the trace
>>> option
>>> in the GUI?
>>>
>>> cheers
>>> Sanjay
>>>
>>>
>>> line in pbs script:
>>>
>>> # now any X11 traffic is sent to the VNC server.
>>> pvbatch --use-offscreen-rendering sk3d.py &
>>>
>>>
>>> my sk3d.py script:
>>>
>>> try: paraview.simple
>>> except: from paraview.simple import *
>>> paraview.simple._DisableFirstRenderCameraReset()
>>>
>>> for i in range (415,3998):
>>>     RenderView1 = GetRenderView()
>>>     HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk'
>>> % (i)] )
>>>     RenderView1.CenterAxesVisibility = 0
>>>     RenderView1.OrientationAxesVisibility = 0
>>>     RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117]
>>>     RenderView1.Background = [1.0, 1.0, 1.0]
>>>     DataRepresentation1 = Show()
>>>     DataRepresentation1.ScalarOpacityUnitDistance = 2.184824466829962
>>>     DataRepresentation1.Representation = 'Outline'
>>>     DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
>>>     RenderView1.CenterOfRotation = [63.5, 63.5, 59.0]
>>>     a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1,
>>> NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0,
>>> 0.7059976962405788, 0.016126465515202103, 0.15000112339188484],
>>> VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
>>>     a1_voltage_PiecewiseFunction = CreatePiecewiseFunction()
>>>     RenderView1.CameraPosition = [63.5, -351.65487519135064, 59.0]
>>>     RenderView1.CameraViewUp = [0.0, 0.0, 1.0]
>>>     RenderView1.CameraFocalPoint = [63.5, 63.5, 59.0]
>>>     RenderView1.CameraClippingRange = [284.63832643943715,
>>> 580.4496983192209]
>>>     RenderView1.CameraParallelScale = 107.44998836668155
>>>     DataRepresentation1.Representation = 'Volume'
>>>     DataRepresentation1.ScalarOpacityFunction =
>>> a1_voltage_PiecewiseFunction
>>>     DataRepresentation1.ColorArrayName = 'voltage'
>>>     DataRepresentation1.LookupTable = a1_voltage_PVLookupTable
>>>     Render()
>>>     WriteImage("Endo_dir_%06i.png" % (i))
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150725/b05cc0f4/attachment.html>

From ganesh.iitm at gmail.com  Sat Jul 25 19:56:36 2015
From: ganesh.iitm at gmail.com (Ganesh Vijayakumar)
Date: Sat, 25 Jul 2015 19:56:36 -0400
Subject: [Paraview] Paraview server using off-screen rendering
In-Reply-To: <CAOXZzG6of-A9+uLUopZpFTmmnwfL6RQBRkUGNW0w3V=xJX9Rog@mail.gmail.com>
References: <CAOXZzG7L4FLP_vsoPY3D1cqUyMdjd-H9T9sK53Teg0yMcpSvGQ@mail.gmail.com>
 <CAFtK+evUnwbV_9fC3GwKKx7ss3SQB0QanK4Eygs=NwN6O+JFxg@mail.gmail.com>
 <CAOXZzG7tB=7tC+X0OesEY5yAntYP58y061B9guQkUmz9cnEzZg@mail.gmail.com>
 <CAFtK+etfTwogt=ymfZ1HmJcYB7_=aEYOUWqytANp7iE1ju6M6Q@mail.gmail.com>
 <CAOXZzG6of-A9+uLUopZpFTmmnwfL6RQBRkUGNW0w3V=xJX9Rog@mail.gmail.com>
Message-ID: <CAFtK+euhDEFJzNCgh1=MC8NXKQKXehop_ACg=EwFqWK52a-p+Q@mail.gmail.com>

Hello,

  Ooops.. I was trying to see if I did anything wrong and saw that I
addressed my reply to only Chuck. I'm sorry (reply vs. reply all).

I've uploaded the CMakeCache.txt here
https://psu.box.com/s/xsrbpsu73exqmz6v1rsy8jy2mtyzabhk.

This is the error message when using the verbose option.

[  4%] Built target vtkWrappingTools
make -f VTK/Wrapping/Tools/CMakeFiles/vtkWrapHierarchy.dir/build.make
VTK/Wrapping/Tools/CMakeFiles/vtkWrapHierarchy.dir/depend
make[2]: Entering directory
`/lustre/medusa/gantech/software/Paraview-v4.3.1'
cd /lustre/medusa/gantech/software/Paraview-v4.3.1 &&
/nics/e/sw/xc30_cle5.2_pe2014-09/cmake/2.8.12.2/sles11.3_gnu4.3.4/bin/cmake
-E cmake_depends "Unix Makefiles" /nics/d/home/gantech/softw
are/ParaView-v4.3.1-source
/nics/d/home/gantech/software/ParaView-v4.3.1-source/VTK/Wrapping/Tools
/lustre/medusa/gantech/software/Paraview-v4.3.1
/lustre/medusa/gantech/software/Paraview-v4
.3.1/VTK/Wrapping/Tools
/lustre/medusa/gantech/software/Paraview-v4.3.1/VTK/Wrapping/Tools/CMakeFiles/vtkWrapHierarchy.dir/DependInfo.cmake
--color=
make[2]: Leaving directory `/lustre/medusa/gantech/software/Paraview-v4.3.1'
make -f VTK/Wrapping/Tools/CMakeFiles/vtkWrapHierarchy.dir/build.make
VTK/Wrapping/Tools/CMakeFiles/vtkWrapHierarchy.dir/build
make[2]: Entering directory
`/lustre/medusa/gantech/software/Paraview-v4.3.1'
Linking C executable ../../../bin/vtkWrapHierarchy-pv4.3
cd /lustre/medusa/gantech/software/Paraview-v4.3.1/VTK/Wrapping/Tools &&
/nics/e/sw/xc30_cle5.2_pe2014-09/cmake/2.8.12.2/sles11.3_gnu4.3.4/bin/cmake
-E cmake_link_script CMakeFiles/vtkWrapHi
erarchy.dir/link.txt --verbose=1
/opt/cray/craype/2.2.1/bin/cc    -O3 -DNDEBUG  -Wl,--fatal-warnings
-Wl,--no-undefined -lc -Wl,--fatal-warnings -Wl,--no-undefined -lc
CMakeFiles/vtkWrapHierarchy.dir/vtkWrapHierarchy.c.o
  -o ../../../bin/vtkWrapHierarchy-pv4.3 -rdynamic
../../../lib/libvtkWrappingTools-pv4.3.a
/usr/lib/../lib64/libpthread.a(lowlevellock.o): In function
`__lll_lock_wait_private':
/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:81:
multiple definition of `__lll_lock_wait_private'
/usr/lib/../lib64/libc.a(libc-lowlevellock.o):/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:81:
first defined here
/usr/lib/../lib64/libpthread.a(lowlevellock.o): In function
`__lll_unlock_wake_private':
/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:323:
multiple definition of `__lll_unlock_wake_private'
/usr/lib/../lib64/libc.a(libc-lowlevellock.o):/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:323:
first defined here
/usr/bin/ld: link errors found, deleting executable
`../../../bin/vtkWrapHierarchy-pv4.3'
collect2: error: ld returned 1 exit status
make[2]: *** [bin/vtkWrapHierarchy-pv4.3] Error 1
make[2]: Leaving directory `/lustre/medusa/gantech/software/Paraview-v4.3.1'
make[1]: *** [VTK/Wrapping/Tools/CMakeFiles/vtkWrapHierarchy.dir/all] Error
2
make[1]: Leaving directory `/lustre/medusa/gantech/software/Paraview-v4.3.1'
make: *** [all] Error 2



On Thu, Jul 23, 2015 at 8:11 AM, Chuck Atkins <chuck.atkins at kitware.com>
wrote:

> Hi Ganesh,
>
> Can you post your CMakeCache.txt?  Also, if you build with "make
> VERBOSE=1" that will give the  full command that gets executed for the
> failing link step.  Posting both of those will be helpful.
>
> - Chuck
>
> On Wed, Jul 22, 2015 at 10:37 PM, Ganesh Vijayakumar <
> ganesh.iitm at gmail.com> wrote:
>
>> Dear Chuck,
>>
>>    Finally, I got this done. I could get paraview to configure without
>> giving any errors. I removed the build directory and started afresh.
>> However, it fails at the same place during the compilation. Could you
>> advise as to what might be the problem.
>>
>> Linking C executable ../../../../bin/vtkmkg3states-pv4.3
>> /usr/lib/../lib64/libpthread.a(lowlevellock.o): In function
>> `__lll_lock_wait_private':
>> /usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:81:
>> multiple definition of `__lll_lock
>> _wait_private'
>>
>> /usr/lib/../lib64/libc.a(libc-lowlevellock.o):/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowleve
>> llock.S:81: first defined here
>> /usr/lib/../lib64/libpthread.a(lowlevellock.o): In function
>> `__lll_unlock_wake_private':
>> /usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:323:
>> multiple definition of `__lll_unl
>> ock_wake_private'
>>
>> /usr/lib/../lib64/libc.a(libc-lowlevellock.o):/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowleve
>> llock.S:323: first defined here
>> /usr/bin/ld: link errors found, deleting executable
>> `../../../../bin/vtkmkg3states-pv4.3'
>> collect2: error: ld returned 1 exit status
>> make[2]: *** [bin/vtkmkg3states-pv4.3] Error 1
>> make[1]: ***
>> [VTK/ThirdParty/tiff/vtktiff/CMakeFiles/vtkmkg3states.dir/all] Error 2
>> make: *** [all] Error 2
>>
>>
>> ganesh
>>
>> On Thu, Jul 16, 2015 at 2:19 PM Chuck Atkins <chuck.atkins at kitware.com>
>> wrote:
>>
>>> If it's a problem with HDF5 library, I'm not sure where I need to point
>>>>>> to the system installation.
>>>>>>
>>>>> If you load the cray-hdf5 module, that will set the HDF5_DIR
>>>>> environment variable to the correct location.  Unfortunately, CMake uses
>>>>> the HDF5_ROOT variable instead to look for it so you'll neet to set it
>>>>> accordingly.
>>>>>
>>>> I don't have much experience with cmake, but can I set additional
>>>> variables in the ccmake window? Should this variable show up there asking
>>>> to be set if you turn on the advanced mode toggle?
>>>>
>>>
>>> Different find modules work differently.  The FindHDF5 module uses the
>>> HDF5_ROOT environment variable (not CMake variable, which is why it won't
>>> show up in the ccmake UI) as a hint for where to search, hence exporting it
>>> as an env var prior to running CMake.  You'll also want to be sure to
>>> specify to use an external HDF5 rather than ParaView building it's own:
>>>
>>>   -DVTK_USE_SYSTEM_HDF5:BOOL=ON
>>>
>>>
>>>  CMAKE_CXX_FLAGS                  -L/lustre/medusa/gantech/
>>>> software/mesa-10.6.0/lib
>>>>
>>> ...
>>>
>>>>  CMAKE_C_FLAGS                    -L/lustre/medusa/gantech/
>>>> software/mesa-10.6.0/lib
>>>>
>>> ...
>>>
>>>>  CMAKE_EXE_LINKER_FLAGS           -L/lustre/medusa/gantech/
>>>> software/mesa-10.6.0/lib
>>>>
>>>
>>> Instead of setting these in the compiler flags, it's better to tell
>>> ParaView where to explicitly find the libraries and to configure
>>> accordingly for OSMesa.  You can pass these as command line arguments to
>>> cmake or ccmake with -D, or set them in the ccmake UI:
>>>
>>>   -DOPENGL_INCLUDE_DIR:PATH=
>>>   -DOPENGL_xmesa_INCLUDE_DIR:PATH=
>>>   -DOPENGL_gl_LIBRARY:FILEPATH=
>>>   -DOPENGL_glu_LIBRARY:FILEPATH=
>>>   -DOSMESA_INCLUDE_DIR:PATH=/lustre/medusa/gantech/
>>> software/mesa-10.6.0/include
>>>   -DOSMESA_LIBRARY:FILEPATH=/lustre/medusa/gantech/
>>> software/mesa-10.6.0/lib/libOSMesa.a
>>>   -DVTK_OPENGL_HAS_OSMESA:BOOL=ON
>>>   -DVTK_USE_X:BOOL=OFF
>>>
>>>
>>>
>>>>  CMAKE_Fortran_COMPILER           /opt/gcc/4.9.2/bin/gfortran
>>>>
>>>
>>> Not that it will really matter since we're not compiling Fortran code,
>>> but this should be /opt/cray/craype/2.2.1/bin/ftn
>>>
>>>
>>>  MPI_CXX_LIBRARIES                /opt/cray/mpt/7.1.3/gni/
>>>> mpich2-gnu/49/lib/
>>>>
>>> ...
>>>
>>>>  MPI_C_LIBRARIES                  /opt/cray/mpt/7.1.3/gni/
>>>> mpich2-gnu/49/lib/
>>>>
>>> ...
>>>
>>>>  MPI_LIBRARY                      /opt/cray/mpt/7.1.3/gni/
>>>> mpich2-gnu/49/lib
>>>>
>>>
>>> It does look like the wrappers are correctly getting used for mpicc and
>>> mpiCC and you can see the include dirs getting set accordingly, but these
>>> do not look right.  Which version of CMake are you using?  Here's what I
>>> get using CMake 3.2.3 (current cmake) on a Cray XC30 when not setting any
>>> MPI variables, just letting CMake auto-detect them by enabling
>>> ParaView_USE_MPI=ON:
>>>
>>>  MPI_CXX_COMPILER
>>> /opt/cray/craype/2.1.0/bin/CC
>>>  MPI_CXX_COMPILE_FLAGS
>>>
>>>  MPI_CXX_INCLUDE_PATH
>>>
>>>  MPI_CXX_LIBRARIES
>>>
>>>  MPI_CXX_LINK_FLAGS
>>>
>>>  MPI_CXX_NO_INTERROGATE
>>> /opt/cray/craype/2.1.0/bin/CC
>>>  MPI_C_COMPILER
>>> /opt/cray/craype/2.1.0/bin/cc
>>>  MPI_C_COMPILE_FLAGS
>>>
>>>  MPI_C_INCLUDE_PATH
>>>
>>>  MPI_C_LIBRARIES
>>>
>>>  MPI_C_LINK_FLAGS
>>>
>>>  MPI_C_NO_INTERROGATE
>>> /opt/cray/craype/2.1.0/bin/cc
>>>  MPI_EXTRA_LIBRARY
>>> MPI_EXTRA_LIBRARY-NOTFOUND
>>>  MPI_Fortran_COMPILER
>>> /opt/cray/craype/2.1.0/bin/ftn
>>>  MPI_Fortran_COMPILE_FLAGS
>>>
>>>  MPI_Fortran_INCLUDE_PATH
>>>
>>>  MPI_Fortran_LIBRARIES
>>>
>>>  MPI_Fortran_LINK_FLAGS
>>>
>>>  MPI_Fortran_NO_INTERROGATE
>>> /opt/cray/craype/2.1.0/bin/ftn
>>>  MPI_LIBRARY                      MPI_LIBRARY-NOTFOUND
>>>
>>> Because the Cray wrappers automatically add the mpi libs and headers
>>> (behaving like mpiCC), then the MPI code should compile without any
>>> additional flags.
>>>
>>
>


-- 
ganesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150725/637b3aeb/attachment.html>

From eric.g.younkin at noaa.gov  Sun Jul 26 11:29:59 2015
From: eric.g.younkin at noaa.gov (Eric Younkin - NOAA Federal)
Date: Sun, 26 Jul 2015 11:29:59 -0400
Subject: [Paraview] PCL Plugin
In-Reply-To: <CAFe6qKjn0xwjT8L=Va6_bLx85LmEdTAuV9z0nUMjSmRsnqk2mw@mail.gmail.com>
References: <CAFe6qKh9YYANWP94Y5+Vk84NDJEULzm2b21SgX0cWJeNP9b9oQ@mail.gmail.com>
 <CAOqyOuHc=xhtP7uzOk-z9TMkNJ0uhpQfxhosOYJd6JVfLDAO5w@mail.gmail.com>
 <mo2q49$4gt$1@ger.gmane.org>
 <CAOqyOuGT2uONXRjPd80bJOBdnhugTMyyUCHGn6s8H4Aw+i1wOg@mail.gmail.com>
 <CAFe6qKgK_grq0Vzo0kF8NgiGxU_4T9_6jQrfij3=yZr9y27CEQ@mail.gmail.com>
 <CAFe6qKh_Xs66xKSNX=1Dqz00DBuXk6vOUrDKnxZRcE8_pNkp7A@mail.gmail.com>
 <CAOqyOuES4fYzufraBhnXgpJRQ1RH23FLZgeCOMbzLT=VUjZpSA@mail.gmail.com>
 <CAFe6qKjn0xwjT8L=Va6_bLx85LmEdTAuV9z0nUMjSmRsnqk2mw@mail.gmail.com>
Message-ID: <CAFe6qKiT5UHJQ34Vdk75vsGGD3yEquoFgUK8o3nd0WuUBSTaLw@mail.gmail.com>

Casey,

I ended up manually changing the additional dependencies I referenced above
for all projects.  Never figured where they were in the cmake files.  I
think some of them were related to the plugins I had enabled.

I am now configuring the PCL Plugin and I'm finding a few things that I
haven't seen while configuring PCL or Paraview.  CMake output below:

Found unsuitable Qt version "5.4.1" from
C:/Qt/Qt5.4.1/5.4/msvc2013_64/bin/qmake.exe

checking for module 'eigen3'

package 'eigen3' not found

Boost version: 1.58.0

Found the following Boost libraries:

system

filesystem

thread

date_time

iostreams

serialization

checking for module 'libopenni'

package 'libopenni' not found

Could NOT find openni (missing: OPENNI_LIBRARY OPENNI_INCLUDE_DIRS)

** WARNING ** io features related to openni will be disabled

checking for module 'libopenni2'

package 'libopenni2' not found

Could NOT find ensenso (missing: ENSENSO_LIBRARY ENSENSO_INCLUDE_DIR)

** WARNING ** io features related to ensenso will be disabled

Could NOT find DAVIDSDK (missing: DAVIDSDK_LIBRARY DAVIDSDK_INCLUDE_DIR)

** WARNING ** io features related to davidSDK will be disabled

** WARNING ** io features related to pcap will be disabled

** WARNING ** io features related to png will be disabled

checking for module 'flann'

package 'flann' not found

checking for module 'flann'

package 'flann' not found

checking for module 'libopenni'

package 'libopenni' not found

Could NOT find openni (missing: OPENNI_LIBRARY OPENNI_INCLUDE_DIRS)

** WARNING ** visualization features related to openni will be disabled

checking for module 'libopenni2'

package 'libopenni2' not found

Could NOT find ensenso (missing: ENSENSO_LIBRARY ENSENSO_INCLUDE_DIR)

** WARNING ** visualization features related to ensenso will be disabled

Could NOT find DAVIDSDK (missing: DAVIDSDK_LIBRARY DAVIDSDK_INCLUDE_DIR)

** WARNING ** visualization features related to davidSDK will be disabled

checking for module 'libopenni'

package 'libopenni' not found

Could NOT find openni (missing: OPENNI_LIBRARY OPENNI_INCLUDE_DIRS)

** WARNING ** apps features related to openni will be disabled

looking for PCL_COMMON

looking for PCL_OCTREE

looking for PCL_IO

looking for PCL_KDTREE

looking for PCL_SEARCH

looking for PCL_SAMPLE_CONSENSUS

looking for PCL_FILTERS

looking for PCL_2D

looking for PCL_GEOMETRY

looking for PCL_FEATURES

looking for PCL_ML

looking for PCL_SEGMENTATION

looking for PCL_VISUALIZATION

looking for PCL_SURFACE

looking for PCL_REGISTRATION

looking for PCL_KEYPOINTS

looking for PCL_TRACKING

looking for PCL_RECOGNITION

looking for PCL_STEREO

looking for PCL_APPS

looking for PCL_OUTOFCORE

looking for PCL_PEOPLE

Found unsuitable Qt version "5.4.1" from
C:/Qt/Qt5.4.1/5.4/msvc2013_64/bin/qmake.exe

Qt QTGUI library not found.

Qt QTCORE library not found.

CMake Warning at
C:/Users/eric.g.younkin/Documents/PCL_ParaView/ParaView-v4.3.1-source/CMake/ParaViewPlugins.cmake:981
(message):
GUI resource files in plugins are no longer supported. The same
functionality can be obtained using Hints in the Server Manager xml files.
See the Major API Changes document for details.
Call Stack (most recent call first):
CMakeLists.txt:99 (add_paraview_plugin)

Configuring done


Is there something I can change to allow the QT 5.4.1 libraries to be
recognized?  I saw a few references to QT4 in the CMakeLists.  Also,  I
would really like to build with PCAP support.  I have added the library
path in CMake, but it still says it is disabled (see above).  If you have
any ideas, I would welcome your advice.


Thanks,
Eric

On Fri, Jul 24, 2015 at 10:45 PM, Eric Younkin - NOAA Federal <
eric.g.younkin at noaa.gov> wrote:

> Casey,
>
> Understood.  I will continue to look into it.
>
> I have run into another roadblock that I was thinking you might
> understand.  I have the following VTK libraries linked in all of my PCL
> solution projects with the incorrect name:
>
> They show up as:
> vtkutilitiespythoninitializer.lib
> vtkSciberQuest.lib
> vtkQvis.lib
> vtkPVPythonCatalyst.lib
> vtkPVCatalystTestDriver.lib
> vtkPointSpriteRendering.lib
> vtkPointSpriteGraphics.lib
> vtkeyedomelighting.lib
>
> When they should show up as:
>
> C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\lib\Debug\vtkEyeDomeLighting-pv4.3.lib
>
> C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\lib\Debug\vtkPointSpriteGraphics-pv4.3.lib
>
> C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\lib\Debug\vtkPointSpriteRendering-pv4.3.lib
>
> C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\lib\Debug\vtkPVPythonCatalyst-pv4.3.lib
>
> C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\lib\Debug\vtkQvis-pv4.3.lib
>
> C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\lib\Debug\vtkSciberQuest-pv4.3.lib
>
> C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\lib\Debug\vtkUtilitiesPythonInitializer-pv4.3.lib
>
> I can't seem to find where these libraries are originally linked on
> configuration.  Am I missing something in CMake?  Is there a particular
> CMake file that addresses all of these?
>
> Thanks,
> Eric
>
> On Mon, Jul 20, 2015 at 11:23 AM, Casey Goodlett <
> casey.goodlett at kitware.com> wrote:
>
>> Eric,
>>
>> I am not familiar with the state of ParaView and Qt5 to be able to help.
>> I believe there was a status update on the paraview-developers list
>> recently.
>>
>> Regards,
>>
>> --
>> Casey B Goodlett, PhD
>> Technical Leader
>> Kitware, Inc. - North Carolina Office
>> http://www.kitware.com
>> (919) 969-6990 x310
>>
>
>
>
> --
> Eric Younkin LTJG/NOAA
> HSTP Liaison - East
> Marine Operations Center - Atlantic
> 439 W York St
> Norfolk, VA 23510
> Cell: 828-331-8197
>



-- 
Eric Younkin LTJG/NOAA
HSTP Liaison - East
Marine Operations Center - Atlantic
439 W York St
Norfolk, VA 23510
Cell: 828-331-8197
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150726/cf2fb338/attachment.html>

From S.R.Kharche at exeter.ac.uk  Sun Jul 26 11:30:50 2015
From: S.R.Kharche at exeter.ac.uk (Kharche, Sanjay)
Date: Sun, 26 Jul 2015 15:30:50 +0000
Subject: [Paraview] non-interactive viz on cluster
In-Reply-To: <CANjZAi-02oK8Lx5xSXix+qMxm0U7R4cXVPK2H7eExNhqK_RTLw@mail.gmail.com>
References: <mocupi$4m1$1@ger.gmane.org>
 <VI1PR03MB10718AA847D1243BC64882FD82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi8Cf76WG94RxsF=BytrX-03xRG70s2-eGpAX0mzAmTHfQ@mail.gmail.com>
 <VI1PR03MB107148468CDDC0E8ABA82C2E82870@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi-NEtA9gUL-UXGyW87PCWpAFd2qAzhc-2gLDmxBmK+qHA@mail.gmail.com>
 <DB5PR03MB1062F8ED89F963E50A4CD20C82820@DB5PR03MB1062.eurprd03.prod.outlook.com>
 <CANjZAi_VRp_+_Xe0g9e8X3025HijeEtEWRNgckGmYChzvKnjHg@mail.gmail.com>
 <VI1PR03MB10710503D70C59E000DEFE5782800@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi__bBiq_DtxzXpHLM4gE5z0gHWzcmkb-tuzf_8bm7rmiA@mail.gmail.com>
 <VI1PR03MB10717FD5A5B11CFA8950FCB882800@VI1PR03MB1071.eurprd03.prod.outlook.com>
 <CANjZAi_8VtoYQww3ZBxosCoqLnKONDCx-H02e_WFaf6YeB-A-w@mail.gmail.com>
 <VI1PR03MB1071E2F5675A98E8FCECA77F82800@VI1PR03MB1071.eurprd03.prod.outlook.com>,
 <CANjZAi-02oK8Lx5xSXix+qMxm0U7R4cXVPK2H7eExNhqK_RTLw@mail.gmail.com>
Message-ID: <VI1PR03MB107189432705711397683CE9828F0@VI1PR03MB1071.eurprd03.prod.outlook.com>


Hi Dave, All


I will work through the Python shell of the GUI in the next few days, but I need to do a satisfactory viz now.

I may have a working solution which is not perfect.


Looking into the mailing list's archives and doing a general google search, I found that Delete 'ing

the view and the object makes it easier on the memory, and I get a fast viz simulation.

However, the viz does progressively slow down.  Files 1 to 100 come out at 50 per second.

Files 2000 to 2100 come out 10 per second.


cheers

Sanjay


________________________________
From: David E DeMarle <dave.demarle at kitware.com>
Sent: 25 July 2015 08:34
To: Kharche, Sanjay
Cc: paraview at paraview.org
Subject: Re: [Paraview] non-interactive viz on cluster

Try to do this with some similar data in the python GUI's Tools->Python Shell on your local machine.

That way you get tab completion and can see things happen in the GUI to help you learn the syntax.




David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Sat, Jul 25, 2015 at 4:29 PM, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk<mailto:S.R.Kharche at exeter.ac.uk>> wrote:

that was one of the combinations I tried, and it didnt work.


I am looking at the ParaView wiki right now. Appareltly there is a Delete(XX)

which should be used to delete objects. I am trying to work out what to

Delete and what not to delete.


________________________________
From: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>
Sent: 25 July 2015 08:24

To: Kharche, Sanjay
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] non-interactive viz on cluster

You are making a new reader, but never connecting it to the View.

not:
  HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' % (j)] )
rather
  HumanSAN000001_vtk.FileNames=['HumanSAN%06i.vtk' % (j)]

try that



David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909<tel:518-881-4909>

On Sat, Jul 25, 2015 at 4:18 PM, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk<mailto:S.R.Kharche at exeter.ac.uk>> wrote:


I think I started celebrations too soon. The images are identical to the

first image. I have tried a few combinations, but could not find any solution.


The script:


try: paraview.simple
except: from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()

i = 1
RenderView1 = GetRenderView()
HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' % (i)] )
RenderView1.CenterAxesVisibility = 0
RenderView1.OrientationAxesVisibility = 0
RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117]
RenderView1.Background = [1.0, 1.0, 1.0]
DataRepresentation1 = Show()
DataRepresentation1.ScalarOpacityUnitDistance = 2.184824466829962
DataRepresentation1.Representation = 'Outline'
DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
RenderView1.CenterOfRotation = [63.5, 63.5, 59.0]
a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0, 0.7059976962405788, 0.016126465515202103, 0.15000112339188484], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
a1_voltage_PiecewiseFunction = CreatePiecewiseFunction()
RenderView1.CameraPosition = [63.5, -351.65487519135064, 59.0]
RenderView1.CameraViewUp = [0.0, 0.0, 1.0]
RenderView1.CameraFocalPoint = [63.5, 63.5, 59.0]
RenderView1.CameraClippingRange = [284.63832643943715, 580.4496983192209]
RenderView1.CameraParallelScale = 107.44998836668155
DataRepresentation1.Representation = 'Volume'
DataRepresentation1.ScalarOpacityFunction = a1_voltage_PiecewiseFunction
DataRepresentation1.ColorArrayName = 'voltage'
DataRepresentation1.LookupTable = a1_voltage_PVLookupTable
Render()
WriteImage("Endo_dir_%06i.png" % (i))
for j in range (2,3998):
    HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' % (j)] )
    a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0, 0.7059976962405788, 0.016126465515202103, 0.15000112339188484], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
    Render()
    WriteImage("Endo_dir_%06i.png" % (j))



________________________________
From: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>
Sent: 25 July 2015 03:47
To: Kharche, Sanjay
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] non-interactive viz on cluster

I think your memory usage is growing with each iteration, Try moving everything out of the loop and then just changing what you have to in the fixed pipeline inside the loop.


i = 415
RenderView1 = GetRenderView()
...
Render()
WriteImage("Endo_dir_%06i.png" % (i))
for i in range(416...):
   HumanSAN000001_vtk.FileName='HumanSAN%06i.vtk' % (i)
   a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0, 0.7059976962405788, 0.016126465515202103, 0.15000112339188484], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
   Render()
   WriteImage...


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909<tel:518-881-4909>

On Sat, Jul 25, 2015 at 11:30 AM, Kharche, Sanjay <S.R.Kharche at exeter.ac.uk<mailto:S.R.Kharche at exeter.ac.uk>> wrote:

Dear David, All

I am now using VNC and got my scripts to do non-interactive viz, i.e.
making of png files using the script below. However, I have a question
regarding efficiency of the run.

As of now, I am doing a serial run. The first several png files are produced
swiftly. However, eventually, the run slows down considerably.
e.g. files 1 to 200 are at a rate of 10 per second
but files 300 to 35 are almost 1 every 2 minutes.#

Any ideas why this is, and how to rectify this? Isthis a memory leak and if so
how not do introduce this when making the .py script using the trace option
in the GUI?

cheers
Sanjay


line in pbs script:

# now any X11 traffic is sent to the VNC server.
pvbatch --use-offscreen-rendering sk3d.py &


my sk3d.py script:

try: paraview.simple
except: from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()

for i in range (415,3998):
    RenderView1 = GetRenderView()
    HumanSAN000001_vtk = LegacyVTKReader( FileNames=['HumanSAN%06i.vtk' % (i)] )
    RenderView1.CenterAxesVisibility = 0
    RenderView1.OrientationAxesVisibility = 0
    RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117]
    RenderView1.Background = [1.0, 1.0, 1.0]
    DataRepresentation1 = Show()
    DataRepresentation1.ScalarOpacityUnitDistance = 2.184824466829962
    DataRepresentation1.Representation = 'Outline'
    DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
    RenderView1.CenterOfRotation = [63.5, 63.5, 59.0]
    a1_voltage_PVLookupTable = GetLookupTableForArray( "voltage", 1, NanColor=[0.25, 0.0, 0.0], RGBPoints=[0.0, 0.23, 0.299, 0.754, 1.0, 0.7059976962405788, 0.016126465515202103, 0.15000112339188484], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 )
    a1_voltage_PiecewiseFunction = CreatePiecewiseFunction()
    RenderView1.CameraPosition = [63.5, -351.65487519135064, 59.0]
    RenderView1.CameraViewUp = [0.0, 0.0, 1.0]
    RenderView1.CameraFocalPoint = [63.5, 63.5, 59.0]
    RenderView1.CameraClippingRange = [284.63832643943715, 580.4496983192209]
    RenderView1.CameraParallelScale = 107.44998836668155
    DataRepresentation1.Representation = 'Volume'
    DataRepresentation1.ScalarOpacityFunction = a1_voltage_PiecewiseFunction
    DataRepresentation1.ColorArrayName = 'voltage'
    DataRepresentation1.LookupTable = a1_voltage_PVLookupTable
    Render()
    WriteImage("Endo_dir_%06i.png" % (i))



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

From krishnapai09 at gmail.com  Sun Jul 26 13:00:51 2015
From: krishnapai09 at gmail.com (Krishna Pai)
Date: Sun, 26 Jul 2015 13:00:51 -0400
Subject: [Paraview] How to select cells that share the same vtkProcessId
Message-ID: <CAPHwKk7_6tpmjwkLC5CnSm1jx5==HhvMJ=ENJ4T85dS-TmrcEA@mail.gmail.com>

Hi all,

Is there a way to select all the cells that share the same ProcessId (or
other field) without using my mouse to click or drag over every one? My
goal is to use ParaView to visualize the results of several simulations in
parallel, with each process handling the visualization of a single
simulation. Along that same line, is there a way ParaView can make each
process look into a different directory of simulation data so I can
accomplish this?

Thanks,
Krishna Pai
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150726/bdf2220d/attachment.html>

From rccm.kyoshimi at gmail.com  Sun Jul 26 22:58:13 2015
From: rccm.kyoshimi at gmail.com (kenichiro yoshimi)
Date: Mon, 27 Jul 2015 11:58:13 +0900
Subject: [Paraview] Glyph for normalized zero vectors
Message-ID: <CAHDyfPA=P_aa=sYUoxS5ReYPrn-2X0GDYpSvgZ1=f+GjgJaqrQ@mail.gmail.com>

Hi all,

I apply the Glyph filter to the velocity field with zero vectors at the
walls.
At that time, to plot the normalized vectors, I set the "Scale Mode"
property to off. But Glyph filter is drawing arrows oriented along (1, 0,
0) for zero vectors.

Do you have any idea that I could plot normalized zero vectors that have no
length?

Thanks for your helps,
yoshimi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150727/314298f6/attachment.html>

From berk.geveci at kitware.com  Mon Jul 27 11:49:29 2015
From: berk.geveci at kitware.com (Berk Geveci)
Date: Mon, 27 Jul 2015 11:49:29 -0400
Subject: [Paraview] Molecular dynamics from lammps
In-Reply-To: <1437661242.850995039@f94.i.mail.ru>
References: <1436279999.571994242@f345.i.mail.ru>
 <1436852798.517668428@f416.i.mail.ru>
 <CAE32kpW9hj4bQK6eqvvDT4JDVmhE+naOMs6VyPm7haU2gODZPA@mail.gmail.com>
 <1437661242.850995039@f94.i.mail.ru>
Message-ID: <CAE32kpXoLeiBx_TUwKe1gO=+UfVvdbO41i5yuVK3d7mS0PCY4g@mail.gmail.com>

You are welcome :-) Sorry I wasn't able to help a bit more. I was
traveling. Maybe you could share your code with the list? I am sure others
would benefit from this.

Best,
-berk

On Thu, Jul 23, 2015 at 10:20 AM, Oksana <oksana_golovnya at mail.ru> wrote:

> Berk, thank you for the ideas! I have made the projections using
> Programmable Filter. It is really very powerful tool.
>
> Oksana
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150727/05222772/attachment.html>

From kmorel at sandia.gov  Mon Jul 27 11:53:50 2015
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Mon, 27 Jul 2015 15:53:50 +0000
Subject: [Paraview] How to select cells that share the same vtkProcessId
Message-ID: <D1DBAF76.267C9%kmorel@sandia.gov>

You can use the "Find Data" dialog to select all elements with a particular field value as well as many other selection criteria. This feature is documented in the most recent version of both the ParaView Tutorial (http://www.paraview.org/Wiki/The_ParaView_Tutorial) and the ParaView Guide (http://www.paraview.org/paraview-guide/). Both are available for free, and "find data" is referenced in the index of each.

-Ken

From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Krishna Pai <krishnapai09 at gmail.com<mailto:krishnapai09 at gmail.com>>
Date: Sunday, July 26, 2015 at 11:00 AM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] How to select cells that share the same vtkProcessId

Hi all,

Is there a way to select all the cells that share the same ProcessId (or other field) without using my mouse to click or drag over every one? My goal is to use ParaView to visualize the results of several simulations in parallel, with each process handling the visualization of a single simulation. Along that same line, is there a way ParaView can make each process look into a different directory of simulation data so I can accomplish this?

Thanks,
Krishna Pai
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150727/c399b52c/attachment.html>

From krishnapai09 at gmail.com  Mon Jul 27 12:02:38 2015
From: krishnapai09 at gmail.com (Krishna Pai)
Date: Mon, 27 Jul 2015 12:02:38 -0400
Subject: [Paraview] How to select cells that share the same vtkProcessId
In-Reply-To: <D1DBAF76.267C9%kmorel@sandia.gov>
References: <D1DBAF76.267C9%kmorel@sandia.gov>
Message-ID: <CAPHwKk5TNTJd=giuVRV8DfoCvqzQGS8HMdpL2wQ3+MOVJAPKBA@mail.gmail.com>

Thanks Ken,

For some reason, I wasn't finding success with Find Data (every query I
tried resulted in an empty table), but I was able to use a combination of
the ProcessIdScalars and the Threshold filters to do what I wanted, shortly
before you replied.

Krishna

On Mon, Jul 27, 2015 at 11:53 AM, Moreland, Kenneth <kmorel at sandia.gov>
wrote:

>   You can use the "Find Data" dialog to select all elements with a
> particular field value as well as many other selection criteria. This
> feature is documented in the most recent version of both the *ParaView
> Tutorial* (http://www.paraview.org/Wiki/The_ParaView_Tutorial) and the *ParaView
> Guide* (http://www.paraview.org/paraview-guide/). Both are available for
> free, and "find data" is referenced in the index of each.
>
>  -Ken
>
>   From: ParaView <paraview-bounces at paraview.org> on behalf of Krishna Pai
> <krishnapai09 at gmail.com>
> Date: Sunday, July 26, 2015 at 11:00 AM
> To: "paraview at paraview.org" <paraview at paraview.org>
> Subject: [EXTERNAL] [Paraview] How to select cells that share the same
> vtkProcessId
>
>    Hi all,
>
>  Is there a way to select all the cells that share the same ProcessId (or
> other field) without using my mouse to click or drag over every one? My
> goal is to use ParaView to visualize the results of several simulations in
> parallel, with each process handling the visualization of a single
> simulation. Along that same line, is there a way ParaView can make each
> process look into a different directory of simulation data so I can
> accomplish this?
>
>  Thanks,
>  Krishna Pai
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150727/9931045c/attachment.html>

From sevensam at udel.edu  Mon Jul 27 14:26:53 2015
From: sevensam at udel.edu (Jesse Samluk)
Date: Mon, 27 Jul 2015 14:26:53 -0400
Subject: [Paraview] Automatic translation with Tube?
Message-ID: <A26AAC9B-7CB6-4DFB-B5ED-048B995AE55E@udel.edu>

Greetings all,

  Attached is a rendering I constructed with Paraview. I turned the StreamTracer on so you can see the purpose behind my question.

 The StreamTracer (thin blue lines) is in the correct position, however the yellow Tube is not (it?s translated by 5 units on the y-axis as I soon discovered).

  My question is - is there some type of automatic setting with Tubes in Paraview? I didn?t touch the translation at all, so I?m curious why the Tubes are pushed out a bit.

Thanks!
  Jesse
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150727/11fd9b9b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Question for Paraview.jpeg
Type: image/jpeg
Size: 31001 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150727/11fd9b9b/attachment.jpeg>

From jfavre at cscs.ch  Mon Jul 27 16:17:09 2015
From: jfavre at cscs.ch (Favre  Jean)
Date: Mon, 27 Jul 2015 20:17:09 +0000
Subject: [Paraview] CFP: SC '15 Scientific Visualization Showcase
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F6841F212D9@MBX211.d.ethz.ch>


Folks

We have some great news. The deadline for submission has been pushed back to August 7. Take advantage of the extra time to submit the best visualizations ever.

Jean,
SC15,  Scientific Visualization Showcase Chair

________________________________
From: ParaView [paraview-bounces at paraview.org] on behalf of Berk Geveci [berk.geveci at kitware.com]
Sent: Saturday, July 18, 2015 1:59 AM
To: ParaView Developers; ParaView Mailing List
Subject: [Paraview] CFP: SC '15 Scientific Visualization Showcase

Hi folks,

Just a reminder that the deadline for the Scientific Visualization Showcase is near.

Best,
-berk

On Tue, May 26, 2015 at 8:19 AM, Berk Geveci <berk.geveci at kitware.com<mailto:berk.geveci at kitware.com>> wrote:
Hi folks,

The Call for Participation for the SC '15 Scientific Visualization Showcase is out. This is a great opportunity for the community to highlight the wonderful visualization work going on. Please consider submitting an entry (or more).

http://sc15.supercomputing.org/program/scientific-visualization-showcase

SC15?s Visualization and Data Analytics Showcase Program provides a forum for the year's most instrumental movies in HPC.  Six finalists will compete for the Best Visualization Award, and each finalist will present his or her movie during a dedicated session at SC15 in a 15-minute presentation. Movies are judged based on how their movie illuminates science, by the quality of the movie, and for innovations in the process used for creating the movie.

Best,
-berk


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

From kevin.dean at decisionsciencescorp.com  Mon Jul 27 16:35:23 2015
From: kevin.dean at decisionsciencescorp.com (Dean, Kevin)
Date: Mon, 27 Jul 2015 13:35:23 -0700
Subject: [Paraview] MultiBlockDataSet Won't render while streaming
Message-ID: <CAFvyM3Rsc94DSCwqVFmu5g+GO56HP+db0iinqAbK2u62V4XGUQ@mail.gmail.com>

So I am streaming data and putting it into and mutliblockdataset, however,
It won't render after going through request data. I have a similar script
that works with imagedata, but for some reason it will not work with
mutliblocks.  Here is what the output I am getting... (also, I threw a
writer into the RequestData function and the data is being written out...
provided a picture for comparison). Do you have any suggestions on where to
go from here?

Thanks,

Kevin E. Dean

-- 
This email and its contents are confidential. If you are not the intended 
recipient, please do not disclose or use the information within this email 
or its attachments. If you have received this email in error, please report 
the error to the sender by return email and delete this communication from 
your records.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150727/8fcc1eae/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OutputFromStreaming.png
Type: image/png
Size: 267225 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150727/8fcc1eae/attachment-0001.png>

From krishnapai09 at gmail.com  Mon Jul 27 17:26:53 2015
From: krishnapai09 at gmail.com (Krishna Pai)
Date: Mon, 27 Jul 2015 17:26:53 -0400
Subject: [Paraview] How to assign separate parallel pvserver processes to
 separate independent datasets?
Message-ID: <CAPHwKk48ggjkoDaJ+1Tfaez7ASgz3cFXKgosWMzYUx+ZEXzy6Q@mail.gmail.com>

Hi all,

I know that, normally, ParaView works with one large dataset and partitions
it based on the number of processes, then renders and merges the results,
which I can then view on my ParaView GUI locally. What I want to do is take
a bunch of independent datasets and make each parallel process render them
without partitioning them further. In other words, I want a one-to-one
correspondence between a parallel process and a dataset with the ability to
view them separately locally (which I can do by filtering by Process ID).
So far, I've tried opening a couple of datasets separately and
simultaneously (using ctrl to select them both), and combined them with
AppendDatasets to see if they would separate out in the way I want. That
didn't work. In both instances, ParaView partitioned each dataset and
rendered a part of them in each process. I would appreciate any tips.

Thanks,
Krishna Pai
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150727/de357968/attachment.html>

From rccm.kyoshimi at gmail.com  Mon Jul 27 22:06:47 2015
From: rccm.kyoshimi at gmail.com (kenichiro yoshimi)
Date: Tue, 28 Jul 2015 11:06:47 +0900
Subject: [Paraview] Glyph for normalized zero vectors
In-Reply-To: <CAHDyfPA=P_aa=sYUoxS5ReYPrn-2X0GDYpSvgZ1=f+GjgJaqrQ@mail.gmail.com>
References: <CAHDyfPA=P_aa=sYUoxS5ReYPrn-2X0GDYpSvgZ1=f+GjgJaqrQ@mail.gmail.com>
Message-ID: <CAHDyfPDjK3cnvTTpBu_RTNuEyVg-oa2OjzL5XpL4oDcCXvOwAg@mail.gmail.com>

I attach an image that shows unnatural arrows generated from zero vectors.

Thanks,
yoshimi

2015-07-27 11:58 GMT+09:00 kenichiro yoshimi <rccm.kyoshimi at gmail.com>:

> Hi all,
>
> I apply the Glyph filter to the velocity field with zero vectors at the
> walls.
> At that time, to plot the normalized vectors, I set the "Scale Mode"
> property to off. But Glyph filter is drawing arrows oriented along (1, 0,
> 0) for zero vectors.
>
> Do you have any idea that I could plot normalized zero vectors that have
> no length?
>
> Thanks for your helps,
> yoshimi
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150728/553de76d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: zero_vector_arrow.png
Type: image/png
Size: 229184 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150728/553de76d/attachment-0001.png>

From eric.g.younkin at noaa.gov  Mon Jul 27 23:30:11 2015
From: eric.g.younkin at noaa.gov (Eric Younkin - NOAA Federal)
Date: Mon, 27 Jul 2015 23:30:11 -0400
Subject: [Paraview] PythonQT Plugin build in VS2013
Message-ID: <CAFe6qKhZR_39j9nXH7JFzsA9ErgY-QfRBc0tB4dodcsW0yQMXg@mail.gmail.com>

Hello,

I've compiled and built the latest PythonQT from this source
<https://github.com/Orochimarufan/PythonQt> in VS2013 with Python 2.7.3 and
QT 5.4.1. Working towards compiling Veloview from source.  I've had to do a
few things to get it to build including:

   - Comment out the '#ifdef PY3K' clause in PythonQT.cpp, line 835
   - Add /bigobj to the project properties in Visual Studio

Now I am trying to compile the Paraview PythonQT Plugin and I get the
following linker error:

3>pqPythonQtPlugin.obj : error LNK2019: unresolved external symbol "void
__cdecl PythonQt_init_QtBindings(void)" (?PythonQt_init_QtBindings@@YAXXZ)
referenced in function "protected: void __cdecl
pqPythonQtPlugin::initialize(void)" (?initialize at pqPythonQtPlugin@@IEAAXXZ)
3>C:\Users\eric.g.younkin\Documents\PCL_ParaView\ParaView-v4.3.1-source\build\bin\Debug\PythonQtPlugin.dll
: fatal error LNK1120: 1 unresolved externals

Anyone have any idea what that is from?  I know this is generally because
an library file isn't properly linked, but I have no idea which one or how
to tell.


Thanks,
Eric

-- 
Eric Younkin LTJG/NOAA
HSTP Liaison - East
Marine Operations Center - Atlantic
439 W York St
Norfolk, VA 23510
Cell: 828-331-8197
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150727/7d39c2c6/attachment.html>

From gaspare.argento at gmail.com  Tue Jul 28 08:46:59 2015
From: gaspare.argento at gmail.com (Gaspare Argento)
Date: Tue, 28 Jul 2015 14:46:59 +0200
Subject: [Paraview] Glyph for normalized zero vectors
In-Reply-To: <CAHDyfPDjK3cnvTTpBu_RTNuEyVg-oa2OjzL5XpL4oDcCXvOwAg@mail.gmail.com>
References: <CAHDyfPA=P_aa=sYUoxS5ReYPrn-2X0GDYpSvgZ1=f+GjgJaqrQ@mail.gmail.com>
 <CAHDyfPDjK3cnvTTpBu_RTNuEyVg-oa2OjzL5XpL4oDcCXvOwAg@mail.gmail.com>
Message-ID: <CADvG_es=nfFb4qJg=U=djHii8-5DzB2YhqBhBuNqrPyEHcfyLA@mail.gmail.com>

Hi all,

I have the same problem. Any tips could help.

Thanks,

Gaspare

2015-07-28 4:06 GMT+02:00 kenichiro yoshimi <rccm.kyoshimi at gmail.com>:
> I attach an image that shows unnatural arrows generated from zero vectors.
>
> Thanks,
> yoshimi
>
> 2015-07-27 11:58 GMT+09:00 kenichiro yoshimi <rccm.kyoshimi at gmail.com>:
>>
>> Hi all,
>>
>> I apply the Glyph filter to the velocity field with zero vectors at the
>> walls.
>> At that time, to plot the normalized vectors, I set the "Scale Mode"
>> property to off. But Glyph filter is drawing arrows oriented along (1, 0, 0)
>> for zero vectors.
>>
>> Do you have any idea that I could plot normalized zero vectors that have
>> no length?
>>
>> Thanks for your helps,
>> yoshimi
>
>
>
> _______________________________________________
> 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
>

From berk.geveci at kitware.com  Tue Jul 28 08:53:38 2015
From: berk.geveci at kitware.com (Berk Geveci)
Date: Tue, 28 Jul 2015 08:53:38 -0400
Subject: [Paraview] CFP: SC '15 Scientific Visualization Showcase
In-Reply-To: <CAE32kpVHFU4qMnTj508FT25Di9gp7c68JmOBy90LjzGPv8cE_A@mail.gmail.com>
References: <CAE32kpVHFU4qMnTj508FT25Di9gp7c68JmOBy90LjzGPv8cE_A@mail.gmail.com>
Message-ID: <CAE32kpWinJkXA=RUjyM9uqH3uvdU4Km4-ZPvbGCWGGCaor8yoQ@mail.gmail.com>

Update!

The deadline for submission of your best scientific visualizations to the
Supercomputing 2015 Showcase has been pushed back to August 7.

hxxp://sc15.supercomputing.org/program/scientific-visualization-showcase

Best,
-berk

On Tue, May 26, 2015 at 8:19 AM, Berk Geveci <berk.geveci at kitware.com>
wrote:

> Hi folks,
>
> The Call for Participation for the SC '15 Scientific Visualization
> Showcase is out. This is a great opportunity for the community to highlight
> the wonderful visualization work going on. Please consider submitting an
> entry (or more).
>
> http://sc15.supercomputing.org/program/scientific-visualization-showcase
>
> SC15?s Visualization and Data Analytics Showcase Program provides a forum
> for the year's most instrumental movies in HPC.  Six finalists will compete
> for the Best Visualization Award, and each finalist will present his or her
> movie during a dedicated session at SC15 in a 15-minute presentation.
> Movies are judged based on how their movie illuminates science, by the
> quality of the movie, and for innovations in the process used for creating
> the movie.
>
> Best,
> -berk
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150728/d5744695/attachment.html>

From cory.quammen at kitware.com  Tue Jul 28 08:55:22 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 28 Jul 2015 08:55:22 -0400
Subject: [Paraview] Glyph for normalized zero vectors
In-Reply-To: <CADvG_es=nfFb4qJg=U=djHii8-5DzB2YhqBhBuNqrPyEHcfyLA@mail.gmail.com>
References: <CAHDyfPA=P_aa=sYUoxS5ReYPrn-2X0GDYpSvgZ1=f+GjgJaqrQ@mail.gmail.com>
 <CAHDyfPDjK3cnvTTpBu_RTNuEyVg-oa2OjzL5XpL4oDcCXvOwAg@mail.gmail.com>
 <CADvG_es=nfFb4qJg=U=djHii8-5DzB2YhqBhBuNqrPyEHcfyLA@mail.gmail.com>
Message-ID: <CAB5Fpx6kvzd+ZhGaKrwvqeOJiWwCjusFD8awGC+8w7FZrKWoSg@mail.gmail.com>

Yoshimi and Gaspare,

Try Thresholding the glyph filter to get rid of the zero-magnitude glyphs.

HTH,
Cory

On Tue, Jul 28, 2015 at 8:46 AM, Gaspare Argento <gaspare.argento at gmail.com>
wrote:

> Hi all,
>
> I have the same problem. Any tips could help.
>
> Thanks,
>
> Gaspare
>
> 2015-07-28 4:06 GMT+02:00 kenichiro yoshimi <rccm.kyoshimi at gmail.com>:
> > I attach an image that shows unnatural arrows generated from zero
> vectors.
> >
> > Thanks,
> > yoshimi
> >
> > 2015-07-27 11:58 GMT+09:00 kenichiro yoshimi <rccm.kyoshimi at gmail.com>:
> >>
> >> Hi all,
> >>
> >> I apply the Glyph filter to the velocity field with zero vectors at the
> >> walls.
> >> At that time, to plot the normalized vectors, I set the "Scale Mode"
> >> property to off. But Glyph filter is drawing arrows oriented along (1,
> 0, 0)
> >> for zero vectors.
> >>
> >> Do you have any idea that I could plot normalized zero vectors that have
> >> no length?
> >>
> >> Thanks for your helps,
> >> yoshimi
> >
> >
> >
> > _______________________________________________
> > 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
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150728/e915349e/attachment.html>

From bruce.david.jones at gmail.com  Tue Jul 28 10:54:19 2015
From: bruce.david.jones at gmail.com (Bruce Jones)
Date: Tue, 28 Jul 2015 14:54:19 +0000
Subject: [Paraview] Compiling ParaView 4.3.1 release
Message-ID: <CAEc4V-YVpruZRpkGQU4bwiDt2ZBRu=_uU+z=23eiQWZaKvYe+w@mail.gmail.com>

Hey Guys,

I have successfully built a recent commit in the paraview repository. I
would like to do some testing against the most recent paraview release
(4.3.1), however when I check out the release branch and try to configure
with cmake I get the error below. I am building on windows with visual
studio 2010. Can anyone explain this error?

Cheers,
Bruce

CMake Error at VTK/CMake/vtkModuleTop.cmake:53 (message):
No such module "vtkRenderingFreeTypeOpenGL" needed by
"vtkPVVTKExtensionsRendering"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150728/a2b9531b/attachment.html>

From cory.quammen at kitware.com  Tue Jul 28 11:01:17 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 28 Jul 2015 11:01:17 -0400
Subject: [Paraview] Compiling ParaView 4.3.1 release
In-Reply-To: <CAEc4V-YVpruZRpkGQU4bwiDt2ZBRu=_uU+z=23eiQWZaKvYe+w@mail.gmail.com>
References: <CAEc4V-YVpruZRpkGQU4bwiDt2ZBRu=_uU+z=23eiQWZaKvYe+w@mail.gmail.com>
Message-ID: <CAB5Fpx7gR5Mfaywd7e1zXvsR11Vf5Bq_7jsbQ6tkBeni22NXXw@mail.gmail.com>

Did you run

git submodule update

after checking out the commit of ParaView you want to build? It looks like
your VTK may not be the right one.

Thanks,
Cory

On Tue, Jul 28, 2015 at 10:54 AM, Bruce Jones <bruce.david.jones at gmail.com>
wrote:

> Hey Guys,
>
> I have successfully built a recent commit in the paraview repository. I
> would like to do some testing against the most recent paraview release
> (4.3.1), however when I check out the release branch and try to configure
> with cmake I get the error below. I am building on windows with visual
> studio 2010. Can anyone explain this error?
>
> Cheers,
> Bruce
>
> CMake Error at VTK/CMake/vtkModuleTop.cmake:53 (message):
> No such module "vtkRenderingFreeTypeOpenGL" needed by
> "vtkPVVTKExtensionsRendering"
>
>
>
> _______________________________________________
> 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
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150728/35ce1746/attachment.html>

From bruce.david.jones at gmail.com  Tue Jul 28 11:05:52 2015
From: bruce.david.jones at gmail.com (Bruce Jones)
Date: Tue, 28 Jul 2015 15:05:52 +0000
Subject: [Paraview] Compiling ParaView 4.3.1 release
In-Reply-To: <CAB5Fpx7gR5Mfaywd7e1zXvsR11Vf5Bq_7jsbQ6tkBeni22NXXw@mail.gmail.com>
References: <CAEc4V-YVpruZRpkGQU4bwiDt2ZBRu=_uU+z=23eiQWZaKvYe+w@mail.gmail.com>
 <CAB5Fpx7gR5Mfaywd7e1zXvsR11Vf5Bq_7jsbQ6tkBeni22NXXw@mail.gmail.com>
Message-ID: <CAEc4V-Zcht7xvuP8KRa2MYM7W9BLEtH5TVLDQhmxqbfTQSuGoQ@mail.gmail.com>

Whoops, no I hadn't. Thanks Cory.

Bruce

On Tue, 28 Jul 2015 at 11:01 Cory Quammen <cory.quammen at kitware.com> wrote:

> Did you run
>
> git submodule update
>
> after checking out the commit of ParaView you want to build? It looks like
> your VTK may not be the right one.
>
> Thanks,
> Cory
>
> On Tue, Jul 28, 2015 at 10:54 AM, Bruce Jones <bruce.david.jones at gmail.com
> > wrote:
>
>> Hey Guys,
>>
>> I have successfully built a recent commit in the paraview repository. I
>> would like to do some testing against the most recent paraview release
>> (4.3.1), however when I check out the release branch and try to configure
>> with cmake I get the error below. I am building on windows with visual
>> studio 2010. Can anyone explain this error?
>>
>> Cheers,
>> Bruce
>>
>> CMake Error at VTK/CMake/vtkModuleTop.cmake:53 (message):
>> No such module "vtkRenderingFreeTypeOpenGL" needed by
>> "vtkPVVTKExtensionsRendering"
>>
>>
>>
>> _______________________________________________
>> 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
>>
>>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150728/c0c1ecea/attachment.html>

From cory.quammen at kitware.com  Tue Jul 28 11:08:28 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 28 Jul 2015 11:08:28 -0400
Subject: [Paraview] Automatic translation with Tube?
In-Reply-To: <A26AAC9B-7CB6-4DFB-B5ED-048B995AE55E@udel.edu>
References: <A26AAC9B-7CB6-4DFB-B5ED-048B995AE55E@udel.edu>
Message-ID: <CAB5Fpx6fqik2LxJ6S94LX2_mZ9CiTM=UWo0Gmp+kUmBWWtzg0g@mail.gmail.com>

Hi Jesse,

Do you have a data set and state file you can share that shows this
behavior?

Thanks,
Cory

On Mon, Jul 27, 2015 at 2:26 PM, Jesse Samluk <sevensam at udel.edu> wrote:

> Greetings all,
>
>   Attached is a rendering I constructed with Paraview. I turned the
> StreamTracer on so you can see the purpose behind my question.
>
>  The StreamTracer (thin blue lines) is in the correct position, however
> the yellow Tube is not (it?s translated by 5 units on the y-axis as I soon
> discovered).
>
>   My question is - is there some type of automatic setting with Tubes in
> Paraview? I didn?t touch the translation at all, so I?m curious why the
> Tubes are pushed out a bit.
>
> Thanks!
>   Jesse
>
> _______________________________________________
> 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
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150728/f9858916/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Question for Paraview.jpeg
Type: image/jpeg
Size: 31001 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150728/f9858916/attachment.jpeg>

From bak at lanl.gov  Tue Jul 28 16:55:36 2015
From: bak at lanl.gov (Kashiwa, Bucky)
Date: Tue, 28 Jul 2015 20:55:36 +0000
Subject: [Paraview] how to build 4.3.1 with CosmoTools
Message-ID: <D1DD4866.318C4%bak@lanl.gov>

I?m trying to build the ParaView-v4.3.1-source standard release, with
cosmotools enabled.  The directory is present at

ParaView-v4.3.1/ParaViewCore/VTKExtensions/CosmoTools

and useful looking source code, but it seems to be unrecognized.  Below is
pasted my ccmake command, and after that is the ccmake error message.  Any
help would be very welcome.  Thanks much, b.


ccmake2.8 \
-D BUILD_SHARED_LIBS:BOOL=ON \
-D BUILD_TESTING:BOOL=OFF \
-D CMAKE_BUILD_TYPE:STRING=Release \
-D 
CMAKE_C_COMPILER:FILEPATH=/usr/projects/hpcsoft/toss2/common/gcc/4.7.2/bin/
gcc \
-D 
CMAKE_CXX_COMPILER:FILEPATH=/usr/projects/hpcsoft/toss2/common/gcc/4.7.2/bi
n/g++ \
-D CMAKE_C_FLAGS:STRING=-fPIC \
-D CMAKE_CXX_FLAGS:STRING=-fPIC \
-D 
CMAKE_Fortran_COMPILER:FILEPATH=/usr/projects/hpcsoft/toss2/common/gcc/4.7.
2/bin/gfortran \
-D 
COSMOTOOLS_INCLUDE_DIR:PATH=../ParaView-v4.3.1-source/ParaViewCore/VTKExten
sions/CosmoTools \
-D FFMPEG_INCLUDE_DIR:PATH=/usr/projects/pv_dev/FFmpeg-1.2/include \
-D 
FFMPEG_avcodec_LIBRARY:FILEPATH=/usr/projects/pv_dev/FFmpeg-1.2/lib/libavco
dec.so \
-D 
FFMPEG_avformat_LIBRARY:FILEPATH=/usr/projects/pv_dev/FFmpeg-1.2/lib/libavf
ormat.so \
-D 
FFMPEG_avutil_LIBRARY:FILEPATH=/usr/projects/pv_dev/FFmpeg-1.2/lib/libavuti
l.so \
-D 
FFMPEG_dc1394_LIBRARY:FILEPATH=/usr/projects/pv_dev/FFmpeg-1.2/lib/libavdev
ice.so \
-D 
FFMPEG_dts_LIBRARY:FILEPATH=/usr/projects/pv_dev/FFmpeg-1.2/lib/libavformat
.so \
-D 
FFMPEG_gsm_LIBRARY:FILEPATH=/usr/projects/pv_dev/FFmpeg-1.2/lib/libavcodec.
so \
-D 
FFMPEG_swscale_LIBRARY:FILEPATH=/usr/projects/pv_dev/FFmpeg-1.2/lib/libswsc
ale.so \
-D GENERIC_IO_INCLUDE_DIR:PATH=/usr/include/gio-unix-2.0 \
-D GENERIC_IO_LIBRARIES:FILEPATH=/usr/lib64/libgio-2.0.so \
-D 
OPENGL_gl_LIBRARY:FILEPATH=/usr/projects/pv_dev/OSMesa-9.0.1/lib/libGL.so \
-D OPENGL_glu_LIBRARY:FILEPATH= \
-D OPENGL_INCLUDE_DIR:PATH=/usr/projects/pv_dev/OSMesa-9.0.1/include \
-D OSMESA_INCLUDE_DIR:PATH=/usr/projects/pv_dev/OSMesa-9.0.1/include \
-D 
OSMESA_LIBRARY:FILEPATH=/usr/projects/pv_dev/OSMesa-9.0.1/lib/libOSMesa.so
\
-D PARAVIEW_BUILD_QT_GUI:BOOL=ON \
-D PARAVIEW_BUILD_CATALYST_ADAPTORS:BOOL=ON \
-D PARAVIEW_ENABLE_COPROCESSING:BOOL=ON \
-D PARAVIEW_ENABLE_COSMOTOOLS:BOOL=ON \
-D PARAVIEW_ENABLE_FFMPEG:BOOL=ON \
-D PARAVIEW_ENABLE_PYTHON:BOOL=ON \
-D PARAVIEW_USE_MPI:BOOL=ON \
-D PYTHON_EXECUTABLE:FILEPATH=/usr/projects/pv_dev/Python-2.7.4/bin/python
\
-D 
PYTHON_INCLUDE_DIR:PATH=/usr/projects/pv_dev/Python-2.7.4/include/python2.7
 \
-D 
PYTHON_LIBRARY:FILEPATH=/usr/projects/pv_dev/Python-2.7.4/lib/libpython2.7.
so \
-D QT_QMAKE_EXECUTABLE:FILEPATH=/usr/projects/pv_dev/Qt-4.8.4/bin/qmake \
-D 
VTK_MPIRUN_EXE:FILEPATH=/usr/projects/hpcsoft/lightshow/openmpi/1.6.5-gcc-4
.7/bin/mpiexec \
-D VTK_OPENGL_HAS_OSMESA:BOOL=ON \
-D VTK_USE_X:BOOL=ON \
-D CMAKE_INSTALL_PREFIX:PATH=/usr/projects/pv_dev/PV-4.3.1-FX \
 ../ParaView-v4.3.1-source







 CMake Error at VTK/CMake/FindPackageHandleStandardArgs.cmake:97 (MESSAGE):
   Could NOT find CosmoTools (missing: COSMOTOOLS_LIBRARIES)
 Call Stack (most recent call first):
   VTK/CMake/FindPackageHandleStandardArgs.cmake:288
(_FPHSA_FAILURE_MESSAGE)
   CMake/FindCosmoTools.cmake:21 (find_package_handle_standard_args)
   ParaViewCore/VTKExtensions/CosmoTools/CMakeLists.txt:6 (find_package)









=======================================================================73
<>Bucky Kashiwa PhD, PE  <> Post: MS B216, Los Alamos, NM  87545       <>
<>  Ofc: TA3-SM123-RM276 <>Email: bak at lanl.gov, kashiwa at qwest.net      <>
<>Voice: 505-667-8812    <>  Fax: 505-665-5926  <>
                         <> Home: 505-988-7332  <> Cell: 505-795-5581  <>
=======================================================================73



From shawn.waldon at kitware.com  Tue Jul 28 17:24:17 2015
From: shawn.waldon at kitware.com (Shawn Waldon)
Date: Tue, 28 Jul 2015 17:24:17 -0400
Subject: [Paraview] how to build 4.3.1 with CosmoTools
In-Reply-To: <D1DD4866.318C4%bak@lanl.gov>
References: <D1DD4866.318C4%bak@lanl.gov>
Message-ID: <CALSpCT249DTH7EvWLZ1Oua0iOZ+jf1dYiz5Zo=85FYWTyfp_2g@mail.gmail.com>

CosmoTools is part of a closed-source project at ANL.  The
COSMOTOOLS_INCLUDE_DIR is incorrect and you need to provide the
COSMOTOOLS_LIBRARIES variable with the external library to link against.
The small part of it that the ParaView module depends on was added to
ParaView so that we wouldn't have the closed-source dependency.
Unfortunately, that change didn't make it into 4.3.1, but if you build
against ParaView's master branch, you will no longer need the closed source
cosmotools package and will still have most of the features in the
CosmoTools module.

HTH,
Shawn

On Tue, Jul 28, 2015 at 4:55 PM, Kashiwa, Bucky <bak at lanl.gov> wrote:

> I?m trying to build the ParaView-v4.3.1-source standard release, with
> cosmotools enabled.  The directory is present at
>
> ParaView-v4.3.1/ParaViewCore/VTKExtensions/CosmoTools
>
> and useful looking source code, but it seems to be unrecognized.  Below is
> pasted my ccmake command, and after that is the ccmake error message.  Any
> help would be very welcome.  Thanks much, b.
>
>
> ccmake2.8 \
> -D BUILD_SHARED_LIBS:BOOL=ON \
> -D BUILD_TESTING:BOOL=OFF \
> -D CMAKE_BUILD_TYPE:STRING=Release \
> -D
> CMAKE_C_COMPILER:FILEPATH=/usr/projects/hpcsoft/toss2/common/gcc/4.7.2/bin/
> gcc \
> -D
> CMAKE_CXX_COMPILER:FILEPATH=/usr/projects/hpcsoft/toss2/common/gcc/4.7.2/bi
> n/g++ \
> -D CMAKE_C_FLAGS:STRING=-fPIC \
> -D CMAKE_CXX_FLAGS:STRING=-fPIC \
> -D
> CMAKE_Fortran_COMPILER:FILEPATH=/usr/projects/hpcsoft/toss2/common/gcc/4.7.
> 2/bin/gfortran \
> -D
> COSMOTOOLS_INCLUDE_DIR:PATH=../ParaView-v4.3.1-source/ParaViewCore/VTKExten
> sions/CosmoTools \
> -D FFMPEG_INCLUDE_DIR:PATH=/usr/projects/pv_dev/FFmpeg-1.2/include \
> -D
> FFMPEG_avcodec_LIBRARY:FILEPATH=/usr/projects/pv_dev/FFmpeg-1.2/lib/libavco
> dec.so \
> -D
> FFMPEG_avformat_LIBRARY:FILEPATH=/usr/projects/pv_dev/FFmpeg-1.2/lib/libavf
> ormat.so \
> -D
> FFMPEG_avutil_LIBRARY:FILEPATH=/usr/projects/pv_dev/FFmpeg-1.2/lib/libavuti
> l.so \
> -D
> FFMPEG_dc1394_LIBRARY:FILEPATH=/usr/projects/pv_dev/FFmpeg-1.2/lib/libavdev
> ice.so \
> -D
> FFMPEG_dts_LIBRARY:FILEPATH=/usr/projects/pv_dev/FFmpeg-1.2/lib/libavformat
> .so \
> -D
> FFMPEG_gsm_LIBRARY:FILEPATH=/usr/projects/pv_dev/FFmpeg-1.2/lib/libavcodec.
> so \
> -D
> FFMPEG_swscale_LIBRARY:FILEPATH=/usr/projects/pv_dev/FFmpeg-1.2/lib/libswsc
> ale.so \
> -D GENERIC_IO_INCLUDE_DIR:PATH=/usr/include/gio-unix-2.0 \
> -D GENERIC_IO_LIBRARIES:FILEPATH=/usr/lib64/libgio-2.0.so \
> -D
> OPENGL_gl_LIBRARY:FILEPATH=/usr/projects/pv_dev/OSMesa-9.0.1/lib/libGL.so \
> -D OPENGL_glu_LIBRARY:FILEPATH= \
> -D OPENGL_INCLUDE_DIR:PATH=/usr/projects/pv_dev/OSMesa-9.0.1/include \
> -D OSMESA_INCLUDE_DIR:PATH=/usr/projects/pv_dev/OSMesa-9.0.1/include \
> -D
> OSMESA_LIBRARY:FILEPATH=/usr/projects/pv_dev/OSMesa-9.0.1/lib/libOSMesa.so
> \
> -D PARAVIEW_BUILD_QT_GUI:BOOL=ON \
> -D PARAVIEW_BUILD_CATALYST_ADAPTORS:BOOL=ON \
> -D PARAVIEW_ENABLE_COPROCESSING:BOOL=ON \
> -D PARAVIEW_ENABLE_COSMOTOOLS:BOOL=ON \
> -D PARAVIEW_ENABLE_FFMPEG:BOOL=ON \
> -D PARAVIEW_ENABLE_PYTHON:BOOL=ON \
> -D PARAVIEW_USE_MPI:BOOL=ON \
> -D PYTHON_EXECUTABLE:FILEPATH=/usr/projects/pv_dev/Python-2.7.4/bin/python
> \
> -D
> PYTHON_INCLUDE_DIR:PATH=/usr/projects/pv_dev/Python-2.7.4/include/python2.7
>  \
> -D
> PYTHON_LIBRARY:FILEPATH=/usr/projects/pv_dev/Python-2.7.4/lib/libpython2.7.
> so \
> -D QT_QMAKE_EXECUTABLE:FILEPATH=/usr/projects/pv_dev/Qt-4.8.4/bin/qmake \
> -D
> VTK_MPIRUN_EXE:FILEPATH=/usr/projects/hpcsoft/lightshow/openmpi/1.6.5-gcc-4
> .7/bin/mpiexec \
> -D VTK_OPENGL_HAS_OSMESA:BOOL=ON \
> -D VTK_USE_X:BOOL=ON \
> -D CMAKE_INSTALL_PREFIX:PATH=/usr/projects/pv_dev/PV-4.3.1-FX \
>  ../ParaView-v4.3.1-source
>
>
>
>
>
>
>
>  CMake Error at VTK/CMake/FindPackageHandleStandardArgs.cmake:97 (MESSAGE):
>    Could NOT find CosmoTools (missing: COSMOTOOLS_LIBRARIES)
>  Call Stack (most recent call first):
>    VTK/CMake/FindPackageHandleStandardArgs.cmake:288
> (_FPHSA_FAILURE_MESSAGE)
>    CMake/FindCosmoTools.cmake:21 (find_package_handle_standard_args)
>    ParaViewCore/VTKExtensions/CosmoTools/CMakeLists.txt:6 (find_package)
>
>
>
>
>
>
>
>
>
> =======================================================================73
> <>Bucky Kashiwa PhD, PE  <> Post: MS B216, Los Alamos, NM  87545       <>
> <>  Ofc: TA3-SM123-RM276 <>Email: bak at lanl.gov, kashiwa at qwest.net      <>
> <>Voice: 505-667-8812    <>  Fax: 505-665-5926  <>
>                          <> Home: 505-988-7332  <> Cell: 505-795-5581  <>
> =======================================================================73
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150728/3ad02883/attachment.html>

From rccm.kyoshimi at gmail.com  Tue Jul 28 19:49:39 2015
From: rccm.kyoshimi at gmail.com (kenichiro yoshimi)
Date: Wed, 29 Jul 2015 08:49:39 +0900
Subject: [Paraview] Glyph for normalized zero vectors
In-Reply-To: <CAB5Fpx6kvzd+ZhGaKrwvqeOJiWwCjusFD8awGC+8w7FZrKWoSg@mail.gmail.com>
References: <CAHDyfPA=P_aa=sYUoxS5ReYPrn-2X0GDYpSvgZ1=f+GjgJaqrQ@mail.gmail.com>
 <CAHDyfPDjK3cnvTTpBu_RTNuEyVg-oa2OjzL5XpL4oDcCXvOwAg@mail.gmail.com>
 <CADvG_es=nfFb4qJg=U=djHii8-5DzB2YhqBhBuNqrPyEHcfyLA@mail.gmail.com>
 <CAB5Fpx6kvzd+ZhGaKrwvqeOJiWwCjusFD8awGC+8w7FZrKWoSg@mail.gmail.com>
Message-ID: <CAHDyfPCQ3agTY0giYgZqeAKTGgSsPBvrNBLX3B-4uDcPC_JdaA@mail.gmail.com>

Cory,

Thank you for your response. This works fine.
I hope that Glyph filter has the feature to always remove glyphs for zero
vectors.
Thank you again for your help.

Best,
yoshimi

2015-07-28 21:55 GMT+09:00 Cory Quammen <cory.quammen at kitware.com>:

> Yoshimi and Gaspare,
>
> Try Thresholding the glyph filter to get rid of the zero-magnitude glyphs.
>
> HTH,
> Cory
>
> On Tue, Jul 28, 2015 at 8:46 AM, Gaspare Argento <
> gaspare.argento at gmail.com> wrote:
>
>> Hi all,
>>
>> I have the same problem. Any tips could help.
>>
>> Thanks,
>>
>> Gaspare
>>
>> 2015-07-28 4:06 GMT+02:00 kenichiro yoshimi <rccm.kyoshimi at gmail.com>:
>> > I attach an image that shows unnatural arrows generated from zero
>> vectors.
>> >
>> > Thanks,
>> > yoshimi
>> >
>> > 2015-07-27 11:58 GMT+09:00 kenichiro yoshimi <rccm.kyoshimi at gmail.com>:
>> >>
>> >> Hi all,
>> >>
>> >> I apply the Glyph filter to the velocity field with zero vectors at the
>> >> walls.
>> >> At that time, to plot the normalized vectors, I set the "Scale Mode"
>> >> property to off. But Glyph filter is drawing arrows oriented along (1,
>> 0, 0)
>> >> for zero vectors.
>> >>
>> >> Do you have any idea that I could plot normalized zero vectors that
>> have
>> >> no length?
>> >>
>> >> Thanks for your helps,
>> >> yoshimi
>> >
>> >
>> >
>> > _______________________________________________
>> > 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
>>
>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150729/33e765e4/attachment.html>

From ganesh.iitm at gmail.com  Tue Jul 28 23:39:53 2015
From: ganesh.iitm at gmail.com (Ganesh Vijayakumar)
Date: Wed, 29 Jul 2015 03:39:53 +0000
Subject: [Paraview] Reg. paraview using off
Message-ID: <CAFtK+eubFC-2qodP-4sA66uvknW5d5tbSA7PApWmXypG-joseg@mail.gmail.com>

Hello,

  I'm trying to install paraview using off-screen rendering on a cluster. I
attached my CMakeCache. It configures just fine. However, I'm unable to
progress beyond this error during the compile. Could anyone please help?
I load the required modules first

module load gcc/4.9.2
module load cmake/3.1.0
module load python/2.7.9
module load hdf5/1.8.14
export HDF5_ROOT=/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/
export PYTHON_INCLUDE_DIRS=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/include/
export PYTHON_LIBRARY=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/lib/
libpython2.7.so
export PYTHON_EXECUTABLE=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/bin/python

Then, I configured as

ccmake ~/software/ParaView-v4.3.1-source
-DOSMESA_INCLUDE_DIR:PATH=/storage/home/guv106/software/mesa-10.5.4/include
-DOSMESA_LIBRARY:FILEPATH=/storage/home/guv106/software/mesa-10.5.4/lib/gallium/libOSMesa.so
-DVTK_USE_X:BOOL=OFF  -DVTK_USE_SYSTEM_HDF5:BOOL=ON
-DPYTHON_INCLUDE_DIRS=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/include/python2.7/

The error during the make process is

[ 11%] Building CXX object
VTK/Rendering/OpenGL/CMakeFiles/vtkRenderingOpenGL.dir/vtkOSOpenGLRenderWindow.cxx.o
cd /storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Rendering/OpenGL
&& /usr/bin/c++   -DVTK_IN_VTK -DvtkRenderingO
penGL_EXPORTS -O3 -DNDEBUG -fPIC
-I/storage/home/guv106/software/ParaView-v4.3.1-build
-I/storage/home/guv106/software/mes
a-10.5.4/include
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Imaging/Hybrid
-I/storage/home/guv106/software/
ParaView-v4.3.1-source/VTK/Imaging/Hybrid
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/IO/Image
-I/storage/ho
me/guv106/software/ParaView-v4.3.1-source/VTK/IO/Image
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/Da
taModel
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/DataModel
-I/storage/home/guv106/software/ParaVi
ew-v4.3.1-build/VTK/Common/Math
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/Math
-I/storage/home/guv
106/software/ParaView-v4.3.1-build/VTK/Common/Core
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/Core
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/KWSys
-I/storage/home/guv106/software/ParaView-v4.3.1-
source/VTK/Utilities/KWSys
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/Misc
-I/storage/home/guv106/so
ftware/ParaView-v4.3.1-source/VTK/Common/Misc
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/System -I/s
torage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/System
-I/storage/home/guv106/software/ParaView-v4.3.1-build
/VTK/Common/Transforms
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/Transforms
-I/storage/home/guv106
/software/ParaView-v4.3.1-build/VTK/Common/ExecutionModel
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Commo
n/ExecutionModel
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/DICOMParser
-I/storage/home/guv106/so
ftware/ParaView-v4.3.1-source/VTK/Utilities/DICOMParser
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/IO/Core
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/IO/Core
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/zlib
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/zlib
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/MetaIO/vtkmetaio
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/MetaIO
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/MetaIO
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/jpeg
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/jpeg
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/png
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/png
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/tiff
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/tiff
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Imaging/Core
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Imaging/Core
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/ParseOGLExt
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/ParseOGLExt
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Rendering/Core
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/Core
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/Color
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/Color
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Extraction
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Extraction
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Core
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Core
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/General
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/General
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/ComputationalGeometry
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/ComputationalGeometry
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Statistics
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Statistics
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Imaging/Fourier
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Imaging/Fourier
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/alglib
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/alglib
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Geometry
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Geometry
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Sources
-I/storage/ home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Sources
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/EncodeString
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/EncodeString
-I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Rendering/OpenGL
-I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL
-fvisibility=hidden -fvisibility-inlines-hidden -o
CMakeFiles/vtkRenderingOpenGL.dir/vtkOSOpenGLRenderWindow.cxx.o -c
/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx
/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:52:
error: ?OSMesaContext? does not name a type
/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:
In constructor
?vtkOSOpenGLRenderWindowInternal::vtkOSOpenGLRenderWindowInternal(vtkRenderWindow*)?:
/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:64:
error: ?class vtkOSOpenGLRenderWindowInternal? has no member named
?OffScreenContextId?
/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:
In member function ?virtual void
vtkOSOpenGLRenderWindow::SetStereoCapableWindow(int)?:
/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:128:
error: ?class vtkOSOpenGLRenderWindowInternal? has no member named
?OffScreenContextId?
/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:
In member function ?void
vtkOSOpenGLRenderWindow::CreateOffScreenWindow(int, int)?:
/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:185:
error: ?class vtkOSOpenGLRenderWindowInternal? has no member named
?OffScreenContextId?
/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:187:
error: ?class vtkOSOpenGLRenderWindowInternal? has no member named
?OffScreenContextId?
/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:187:
error: ?OSMesaCreateContext? was not declared in this scope
/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:
In member function ?void vtkOSOpenGLRenderWindow::DestroyOffScreenWindow()?:


ganesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150729/2df4a027/attachment-0001.html>
-------------- next part --------------
# This is the CMakeCache file.
# For build in directory: /storage/home/guv106/software/ParaView-v4.3.1-build
# It was generated by CMake: /opt/aci/sw/cmake/3.1.0_gcc-4.9.2-1/bin/cmake
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=VALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.

########################
# EXTERNAL cache entries
########################

//Dependencies for the target
AnalyzeNIfTIIO_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkzlib;

//Dependencies for the target
ArrowGlyph_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Build the VTK documentation
BUILD_DOCUMENTATION:BOOL=OFF

BUILD_EXAMPLES:BOOL=FALSE

//Build shared protobuf library
BUILD_SHARED_LIBS:BOOL=ON

//Build the testing tree.
BUILD_TESTING:BOOL=ON

//Path to a program.
BZRCOMMAND:FILEPATH=BZRCOMMAND-NOTFOUND

//Path to a program.
CMAKE_AR:FILEPATH=/usr/bin/ar

//Choose the type of build.
CMAKE_BUILD_TYPE:STRING=Release

//Enable/Disable color output during build.
CMAKE_COLOR_MAKEFILE:BOOL=ON

//CXX compiler
CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++

//Flags used by the compiler during all build types.
CMAKE_CXX_FLAGS:STRING=

//Flags used by the compiler during debug builds.
CMAKE_CXX_FLAGS_DEBUG:STRING=-g

//Flags used by the compiler during release builds for minimum
// size.
CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG

//Flags used by the compiler during release builds.
CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG

//Flags used by the compiler during release builds with debug info.
CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG

//C compiler
CMAKE_C_COMPILER:FILEPATH=/usr/bin/cc

//Flags used by the compiler during all build types.
CMAKE_C_FLAGS:STRING=

//Flags used by the compiler during debug builds.
CMAKE_C_FLAGS_DEBUG:STRING=-g

//Flags used by the compiler during release builds for minimum
// size.
CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG

//Flags used by the compiler during release builds.
CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG

//Flags used by the compiler during release builds with debug info.
CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG

//Flags used by the linker.
CMAKE_EXE_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Enable/Disable output of compile commands during generation.
CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=OFF

//Fortran compiler
CMAKE_Fortran_COMPILER:FILEPATH=/usr/bin/f95

//Fortran flags
CMAKE_Fortran_FLAGS:STRING=

//Flags used by the compiler during debug builds.
CMAKE_Fortran_FLAGS_DEBUG:STRING=-g

//Flags used by the compiler during release builds for minimum
// size.
CMAKE_Fortran_FLAGS_MINSIZEREL:STRING=-Os

//Flags used by the compiler during release builds.
CMAKE_Fortran_FLAGS_RELEASE:STRING=-O3

//Flags used by the compiler during release builds with debug info.
CMAKE_Fortran_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG

//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=/storage/home/guv106/software/Paraview

//Path to a program.
CMAKE_LINKER:FILEPATH=/usr/bin/ld

//Path to a program.
CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/gmake

//Flags used by the linker during the creation of modules.
CMAKE_MODULE_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Path to a program.
CMAKE_NM:FILEPATH=/usr/bin/nm

//Path to a program.
CMAKE_OBJCOPY:FILEPATH=/usr/bin/objcopy

//Path to a program.
CMAKE_OBJDUMP:FILEPATH=/usr/bin/objdump

//Value Computed by CMake
CMAKE_PROJECT_NAME:STATIC=ParaView

//Path to a program.
CMAKE_RANLIB:FILEPATH=/usr/bin/ranlib

//Flags used by the linker during the creation of dll's.
CMAKE_SHARED_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//If set, runtime paths are not added when installing shared libraries,
// but are added when building.
CMAKE_SKIP_INSTALL_RPATH:BOOL=NO

//If set, runtime paths are not added when using shared libraries.
CMAKE_SKIP_RPATH:BOOL=NO

//Flags used by the linker during the creation of static libraries.
CMAKE_STATIC_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Path to a program.
CMAKE_STRIP:FILEPATH=/usr/bin/strip

//Thread library used.
CMAKE_THREAD_LIBS:STRING=-lpthread

//If true, cmake will use relative paths in makefiles and projects.
CMAKE_USE_RELATIVE_PATHS:BOOL=OFF

//If this value is on, makefiles will be generated without the
// .SILENT directive, and all commands will be echoed to the console
// during the make.  This is useful for debugging only. With Visual
// Studio IDE projects all commands are done without /nologo.
CMAKE_VERBOSE_MAKEFILE:BOOL=FALSE

//Path to the coverage program that CTest uses for performing coverage
// inspection
COVERAGE_COMMAND:FILEPATH=/opt/aci/sw/gcc/4.9.2_gcc-4.9.1-10/bin/gcov

//Extra command line flags to pass to the coverage tool
COVERAGE_EXTRA_FLAGS:STRING=-l

//How many times to retry timed-out CTest submissions.
CTEST_SUBMIT_RETRY_COUNT:STRING=3

//How long to wait between timed-out CTest submissions.
CTEST_SUBMIT_RETRY_DELAY:STRING=5

//Path to a program.
CVSCOMMAND:FILEPATH=/usr/bin/cvs

//Options passed to the cvs update command.
CVS_UPDATE_OPTIONS:STRING=-d -A -P

//Maximum time allowed before CTest will kill the test.
DART_TESTING_TIMEOUT:STRING=1500

//Value Computed by CMake
DICOMParser_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/DICOMParser

//Value Computed by CMake
DICOMParser_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/DICOMParser

//Path to a library.
EXECINFO_LIB:FILEPATH=EXECINFO_LIB-NOTFOUND

//Disable compiler warnings
EXODUSII_DISABLE_COMPILER_WARNINGS:BOOL=ON

//Path to Eigen install.
Eigen_DIR:FILEPATH=/storage/home/guv106/software/ParaView-v4.3.1-source/Plugins/SciberQuestToolKit/eigen-3.0.3/eigen-eigen-3.0.3

//Additional URL templates for the ExternalData CMake script to
// look for testing data. E.g.
//\nfile:///var/bigharddrive/%(algo)/%(hash)
ExternalData_URL_TEMPLATES:STRING=

//Dependencies for the target
EyeDomeLightingView_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkEyeDomeLighting;general;vtkEyeDomeLightingCS;general;vtkEyeDomeLighting;

//Value Computed by CMake
EyeDomeLighting_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/Plugins/EyeDomeLighting

//Value Computed by CMake
EyeDomeLighting_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/Plugins/EyeDomeLighting

//Path to a program.
GITCOMMAND:FILEPATH=/usr/bin/git

//git command line client
GIT_EXECUTABLE:FILEPATH=/usr/bin/git

//The directory containing gmvread.c, gmvread.h and gmvrayread.h
GMVReader_GMVREAD_LIB_DIR:PATH=/storage/home/guv106/software/ParaView-v4.3.1-source/Utilities/VisItBridge/databases/GMV

//Dependencies for the target
GMVReader_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Calculate minimum and maximum of data arrays in RequestInformation
// calls.
//\n   A feature inherited from AVSucdReader, but it seems this
// information is
//\n   never queried by ParaView.
GMVReader_SKIP_DATARANGE_CALCULATIONS_IN_REQUEST_INFORMATION_CALLS:BOOL=OFF

//Dependencies for the target
H5PartReader_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/lib/libhdf5.so;general;/usr/lib64/libsz.so;general;/usr/lib64/libz.so;general;/usr/lib64/librt.so;general;/usr/lib64/libdl.so;general;/usr/lib64/libm.so;general;/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/lib/libhdf5_hl.so;general;/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/lib/libhdf5.so;general;vtksys;

//HDF5 C++ Wrapper compiler.  Used only to detect HDF5 compile
// flags.
HDF5_CXX_COMPILER_EXECUTABLE:FILEPATH=/usr/bin/h5c++

//HDF5 Wrapper compiler.  Used only to detect HDF5 compile flags.
HDF5_C_COMPILER_EXECUTABLE:FILEPATH=/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/bin/h5cc

//Path to a file.
HDF5_C_INCLUDE_DIR:PATH=/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/include

//HDF5 file differencing tool.
HDF5_DIFF_EXECUTABLE:FILEPATH=/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/bin/h5diff

//The directory containing a CMake configuration file for HDF5.
HDF5_DIR:PATH=HDF5_DIR-NOTFOUND

//HDF5 Fortran Wrapper compiler.  Used only to detect HDF5 compile
// flags.
HDF5_Fortran_COMPILER_EXECUTABLE:FILEPATH=/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/bin/h5fc

//Path to a file.
HDF5_HL_INCLUDE_DIR:PATH=/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/include

//HDF5 library compiled with parallel IO support
HDF5_IS_PARALLEL:BOOL=FALSE

//Path to a library.
HDF5_dl_LIBRARY_DEBUG:FILEPATH=HDF5_dl_LIBRARY_DEBUG-NOTFOUND

//Path to a library.
HDF5_dl_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libdl.so

//Path to a library.
HDF5_hdf5_LIBRARY_DEBUG:FILEPATH=HDF5_hdf5_LIBRARY_DEBUG-NOTFOUND

//Path to a library.
HDF5_hdf5_LIBRARY_RELEASE:FILEPATH=/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/lib/libhdf5.so

//Path to a library.
HDF5_hdf5_hl_LIBRARY_DEBUG:FILEPATH=HDF5_hdf5_hl_LIBRARY_DEBUG-NOTFOUND

//Path to a library.
HDF5_hdf5_hl_LIBRARY_RELEASE:FILEPATH=/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/lib/libhdf5_hl.so

//Path to a library.
HDF5_m_LIBRARY_DEBUG:FILEPATH=HDF5_m_LIBRARY_DEBUG-NOTFOUND

//Path to a library.
HDF5_m_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libm.so

//Path to a library.
HDF5_rt_LIBRARY_DEBUG:FILEPATH=HDF5_rt_LIBRARY_DEBUG-NOTFOUND

//Path to a library.
HDF5_rt_LIBRARY_RELEASE:FILEPATH=/usr/lib64/librt.so

//Path to a library.
HDF5_sz_LIBRARY_DEBUG:FILEPATH=HDF5_sz_LIBRARY_DEBUG-NOTFOUND

//Path to a library.
HDF5_sz_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libsz.so

//Path to a library.
HDF5_z_LIBRARY_DEBUG:FILEPATH=HDF5_z_LIBRARY_DEBUG-NOTFOUND

//Path to a library.
HDF5_z_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libz.so

//Path to a program.
HGCOMMAND:FILEPATH=HGCOMMAND-NOTFOUND

//Value Computed by CMake
JsonCpp_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/jsoncpp/vtkjsoncpp

//Value Computed by CMake
JsonCpp_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/jsoncpp/vtkjsoncpp

//Command to build the project
MAKECOMMAND:STRING=/opt/aci/sw/cmake/3.1.0_gcc-4.9.2-1/bin/cmake --build . --config "${CTEST_CONFIGURATION_TYPE}" -- -i

//Path to the memory checking command, used for memory error detection.
MEMORYCHECK_COMMAND:FILEPATH=/usr/bin/valgrind

//File that contains suppressions for the memory checker
MEMORYCHECK_SUPPRESSIONS_FILE:FILEPATH=

//Request building Pygments
Module_Pygments:BOOL=OFF

//Request building VisItLib
Module_VisItLib:BOOL=OFF

//Request building pqApplicationComponents
Module_pqApplicationComponents:BOOL=OFF

//Request building pqComponents
Module_pqComponents:BOOL=OFF

//Request building pqCore
Module_pqCore:BOOL=OFF

//Request building pqDeprecated
Module_pqDeprecated:BOOL=OFF

//Request building pqPython
Module_pqPython:BOOL=OFF

//Request building pqWidgets
Module_pqWidgets:BOOL=OFF

//Request building vtkAcceleratorsDax
Module_vtkAcceleratorsDax:BOOL=OFF

//Request building vtkAcceleratorsPiston
Module_vtkAcceleratorsPiston:BOOL=OFF

//Request building vtkDomainsChemistryOpenGL2
Module_vtkDomainsChemistryOpenGL2:BOOL=OFF

//Request building vtkFiltersImaging
Module_vtkFiltersImaging:BOOL=OFF

//Request building vtkFiltersMatlab
Module_vtkFiltersMatlab:BOOL=OFF

//Request building vtkFiltersParallelFlowPaths
Module_vtkFiltersParallelFlowPaths:BOOL=OFF

//Request building vtkFiltersParallelGeometry
Module_vtkFiltersParallelGeometry:BOOL=OFF

//Request building vtkFiltersParallelImaging
Module_vtkFiltersParallelImaging:BOOL=OFF

//Request building vtkFiltersParallelMPI
Module_vtkFiltersParallelMPI:BOOL=OFF

//Request building vtkFiltersReebGraph
Module_vtkFiltersReebGraph:BOOL=OFF

//Request building vtkFiltersSMP
Module_vtkFiltersSMP:BOOL=OFF

//Request building vtkFiltersSelection
Module_vtkFiltersSelection:BOOL=OFF

//Request building vtkFiltersStatisticsGnuR
Module_vtkFiltersStatisticsGnuR:BOOL=OFF

//Request building vtkGUISupportQt
Module_vtkGUISupportQt:BOOL=OFF

//Request building vtkGUISupportQtOpenGL
Module_vtkGUISupportQtOpenGL:BOOL=OFF

//Request building vtkGUISupportQtSQL
Module_vtkGUISupportQtSQL:BOOL=OFF

//Request building vtkGUISupportQtWebkit
Module_vtkGUISupportQtWebkit:BOOL=OFF

//Request building vtkGeovisCore
Module_vtkGeovisCore:BOOL=OFF

//Request building vtkIOADIOS
Module_vtkIOADIOS:BOOL=OFF

//Request building vtkIOFFMPEG
Module_vtkIOFFMPEG:BOOL=OFF

//Request building vtkIOGDAL
Module_vtkIOGDAL:BOOL=OFF

//Request building vtkIOGeoJSON
Module_vtkIOGeoJSON:BOOL=OFF

//Request building vtkIOMINC
Module_vtkIOMINC:BOOL=OFF

//Request building vtkIOMPIImage
Module_vtkIOMPIImage:BOOL=OFF

//Request building vtkIOMPIParallel
Module_vtkIOMPIParallel:BOOL=OFF

//Request building vtkIOMySQL
Module_vtkIOMySQL:BOOL=OFF

//Request building vtkIOODBC
Module_vtkIOODBC:BOOL=OFF

//Request building vtkIOParallelNetCDF
Module_vtkIOParallelNetCDF:BOOL=OFF

//Request building vtkIOPostgreSQL
Module_vtkIOPostgreSQL:BOOL=OFF

//Request building vtkIOSQL
Module_vtkIOSQL:BOOL=OFF

//Request building vtkIOVideo
Module_vtkIOVideo:BOOL=OFF

//Request building vtkIOVisItBridge
Module_vtkIOVisItBridge:BOOL=OFF

//Request building vtkIOXdmf3
Module_vtkIOXdmf3:BOOL=OFF

//Request building vtkImagingMath
Module_vtkImagingMath:BOOL=OFF

//Request building vtkImagingStatistics
Module_vtkImagingStatistics:BOOL=OFF

//Request building vtkImagingStencil
Module_vtkImagingStencil:BOOL=OFF

//Request building vtkInfovisBoost
Module_vtkInfovisBoost:BOOL=OFF

//Request building vtkInfovisBoostGraphAlgorithms
Module_vtkInfovisBoostGraphAlgorithms:BOOL=OFF

//Request building vtkInfovisLayout
Module_vtkInfovisLayout:BOOL=OFF

//Request building vtkInfovisParallel
Module_vtkInfovisParallel:BOOL=OFF

//Request building vtkPVVTKExtensionsCosmoTools
Module_vtkPVVTKExtensionsCosmoTools:BOOL=OFF

//Request building vtkParaViewWebDocumentation
Module_vtkParaViewWebDocumentation:BOOL=OFF

//Request building vtkParallelMPI
Module_vtkParallelMPI:BOOL=OFF

//Request building vtkParallelMPI4Py
Module_vtkParallelMPI4Py:BOOL=OFF

//Request building vtkRenderingContextOpenGL2
Module_vtkRenderingContextOpenGL2:BOOL=OFF

//Request building vtkRenderingFreeTypeFontConfig
Module_vtkRenderingFreeTypeFontConfig:BOOL=OFF

//Request building vtkRenderingFreeTypeOpenGL2
Module_vtkRenderingFreeTypeOpenGL2:BOOL=OFF

//Request building vtkRenderingImage
Module_vtkRenderingImage:BOOL=OFF

//Request building vtkRenderingOpenGL2
Module_vtkRenderingOpenGL2:BOOL=OFF

//Request building vtkRenderingParallelLIC
Module_vtkRenderingParallelLIC:BOOL=OFF

//Request building vtkRenderingQt
Module_vtkRenderingQt:BOOL=OFF

//Request building vtkRenderingTk
Module_vtkRenderingTk:BOOL=OFF

//Request building vtkRenderingVolumeOpenGL2
Module_vtkRenderingVolumeOpenGL2:BOOL=OFF

//Request building vtkRenderingVolumeOpenGLNew
Module_vtkRenderingVolumeOpenGLNew:BOOL=OFF

//Request building vtkTclTk
Module_vtkTclTk:BOOL=OFF

//Request building vtkTestingIOSQL
Module_vtkTestingIOSQL:BOOL=OFF

//Request building vtkUtilitiesColorSeriesToXML
Module_vtkUtilitiesColorSeriesToXML:BOOL=OFF

//Request building vtkViewsGeovis
Module_vtkViewsGeovis:BOOL=OFF

//Request building vtkViewsInfovis
Module_vtkViewsInfovis:BOOL=OFF

//Request building vtkViewsQt
Module_vtkViewsQt:BOOL=OFF

//Request building vtkWebApplications
Module_vtkWebApplications:BOOL=OFF

//Request building vtkWebInstall
Module_vtkWebInstall:BOOL=OFF

//Request building vtkWrappingJava
Module_vtkWrappingJava:BOOL=OFF

//Request building vtkWrappingPythonCore
Module_vtkWrappingPythonCore:BOOL=ON

//Request building vtkWrappingTcl
Module_vtkWrappingTcl:BOOL=OFF

//Request building vtkglew
Module_vtkglew:BOOL=OFF

//Request building vtkicet
Module_vtkicet:BOOL=OFF

//Request building vtklibproj4
Module_vtklibproj4:BOOL=OFF

//Request building vtkmpi4py
Module_vtkmpi4py:BOOL=OFF

//Request building vtkqttesting
Module_vtkqttesting:BOOL=OFF

//Request building vtksqlite
Module_vtksqlite:BOOL=OFF

//Request building vtkxdmf3
Module_vtkxdmf3:BOOL=OFF

//Dependencies for the target
Moments_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Disable compiler warnings
NETCDF_DISABLE_COMPILER_WARNINGS:BOOL=ON

//Build netcdf C++ API
NETCDF_ENABLE_CXX:BOOL=ON

//Dependencies for the target
NonOrthogonalSource_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Path to a file.
OPENGL_INCLUDE_DIR:PATH=/usr/include

//Path to a library.
OPENGL_gl_LIBRARY:FILEPATH=/usr/lib64/libGL.so

//Path to a library.
OPENGL_glu_LIBRARY:FILEPATH=/usr/lib64/libGLU.so

//Path to a file.
OPENGL_xmesa_INCLUDE_DIR:PATH=OPENGL_xmesa_INCLUDE_DIR-NOTFOUND

//No help, variable specified on the command line.
OSMESA_INCLUDE_DIR:PATH=/storage/home/guv106/software/mesa-10.5.4/include

//No help, variable specified on the command line.
OSMESA_LIBRARY:FILEPATH=/storage/home/guv106/software/mesa-10.5.4/lib/gallium/libOSMesa.so

//Path to a program.
P4COMMAND:FILEPATH=P4COMMAND-NOTFOUND

//Build Adaptors for various simulation codes
PARAVIEW_BUILD_CATALYST_ADAPTORS:BOOL=OFF

//Build AdiosReader Plugin
PARAVIEW_BUILD_PLUGIN_AdiosReader:BOOL=FALSE

//Build AnalyzeNIfTIIO Plugin
PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO:BOOL=TRUE

//Build ArrowGlyph Plugin
PARAVIEW_BUILD_PLUGIN_ArrowGlyph:BOOL=TRUE

//Build CGNSReader Plugin
PARAVIEW_BUILD_PLUGIN_CGNSReader:BOOL=FALSE

//Build EyeDomeLighting Plugin
PARAVIEW_BUILD_PLUGIN_EyeDomeLighting:BOOL=TRUE

//Build ForceTime Plugin
PARAVIEW_BUILD_PLUGIN_ForceTime:BOOL=FALSE

//Build GMVReader Plugin
PARAVIEW_BUILD_PLUGIN_GMVReader:BOOL=TRUE

//Build H5PartReader Plugin
PARAVIEW_BUILD_PLUGIN_H5PartReader:BOOL=TRUE

//Build InSituExodus Plugin
PARAVIEW_BUILD_PLUGIN_InSituExodus:BOOL=FALSE

//Build MantaView Plugin
PARAVIEW_BUILD_PLUGIN_MantaView:BOOL=FALSE

//Build Moments Plugin
PARAVIEW_BUILD_PLUGIN_Moments:BOOL=TRUE

//Build NonOrthogonalSource Plugin
PARAVIEW_BUILD_PLUGIN_NonOrthogonalSource:BOOL=TRUE

//Build PacMan Plugin
PARAVIEW_BUILD_PLUGIN_PacMan:BOOL=TRUE

//Build PointSprite Plugin
PARAVIEW_BUILD_PLUGIN_PointSprite:BOOL=TRUE

//Build RGBZView Plugin
PARAVIEW_BUILD_PLUGIN_RGBZView:BOOL=TRUE

//Build SLACTools Plugin
PARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=TRUE

//Build SciberQuestToolKit Plugin
PARAVIEW_BUILD_PLUGIN_SciberQuestToolKit:BOOL=TRUE

//Build SierraPlotTools Plugin
PARAVIEW_BUILD_PLUGIN_SierraPlotTools:BOOL=TRUE

//Build StreamingParticles Plugin
PARAVIEW_BUILD_PLUGIN_StreamingParticles:BOOL=TRUE

//Build SurfaceLIC Plugin
PARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=TRUE

//Build UncertaintyRendering Plugin
PARAVIEW_BUILD_PLUGIN_UncertaintyRendering:BOOL=TRUE

//Build VaporPlugin Plugin
PARAVIEW_BUILD_PLUGIN_VaporPlugin:BOOL=FALSE

//Enable ParaView Qt-based client
PARAVIEW_BUILD_QT_GUI:BOOL=OFF

//Enable/Disable web documentation
PARAVIEW_BUILD_WEB_DOCUMENTATION:BOOL=OFF

//Exclude test data download from default 'all' target.
PARAVIEW_DATA_EXCLUDE_FROM_ALL:BOOL=OFF

//Local directory holding ExternalData objects in the layout %(algo)/%(hash).
PARAVIEW_DATA_STORE:PATH=

//Enable Catalyst CoProcessing modules
PARAVIEW_ENABLE_CATALYST:BOOL=ON

//Build ParaView command-line tools
PARAVIEW_ENABLE_COMMANDLINE_TOOLS:BOOL=ON

//Enable FFMPEG Support.
PARAVIEW_ENABLE_FFMPEG:BOOL=OFF

//Enable/Disable Python scripting support
PARAVIEW_ENABLE_MATPLOTLIB:BOOL=ON

//Enable/Disable Python scripting support
PARAVIEW_ENABLE_PYTHON:BOOL=ON

//Build ParaView with Qt support (without GUI)
PARAVIEW_ENABLE_QT_SUPPORT:BOOL=OFF

//Enables markers in the spyplot reader
PARAVIEW_ENABLE_SPYPLOT_MARKERS:BOOL=ON

//Turn off to avoid ParaView depending on all used VTK modules.
PARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE

//Enable/Disable web support
PARAVIEW_ENABLE_WEB:BOOL=ON

//Semi-colon seperated paths to extrenal plugin directories.
PARAVIEW_EXTERNAL_PLUGIN_DIRS:STRING=

//Freeze Python packages/modules into the application.
PARAVIEW_FREEZE_PYTHON:BOOL=OFF

//When enabled, "make install" will install development files
PARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=OFF

//Expected Qt version
PARAVIEW_QT_VERSION:STRING=4

//Build ParaView with Dax many-core filters
PARAVIEW_USE_DAX:BOOL=OFF

//Enable MPI support for parallel computing
PARAVIEW_USE_MPI:BOOL=OFF

//Build ParaView with Piston GPGPU filters
PARAVIEW_USE_PISTON:BOOL=OFF

//If enabled, Python bindings will back the ClientServer wrapping
// implementation
PARAVIEW_USE_UNIFIED_BINDINGS:BOOL=OFF

//Build ParaView with VisIt readers.
PARAVIEW_USE_VISITBRIDGE:BOOL=OFF

//Disable compiler warnings
PROTOBUF_DISABLE_COMPILER_WARNINGS:BOOL=ON

//Command to run after a failed test to cleanup processes.  Example:
// "killall -9 rsh paraview"
PV_TEST_CLEAN_COMMAND:STRING=

//Node which serves as the client node, used to connect from the
// server side in reverse connection mode.
PV_TEST_CLIENT:STRING=localhost

//Command to run before a test begins. Multiple commands are separated
// by ';'.
PV_TEST_INIT_COMMAND:STRING=

//Use random port numbers when testing client-server configurations.
PV_TEST_USE_RANDOM_PORTS:BOOL=ON

//Path to a program.
PYTHON_EXECUTABLE:FILEPATH=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/bin/python2

//Extra libraries to link when linking to python (such as "z" for
// zlib).  Separate multiple libraries with semicolons.
PYTHON_EXTRA_LIBS:STRING=

//Path to a file.
PYTHON_INCLUDE_DIR:PATH=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/include/python2.7/

//No help, variable specified on the command line.
PYTHON_INCLUDE_DIRS:UNINITIALIZED=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/include/python2.7/

//Path to a library.
PYTHON_LIBRARY:FILEPATH=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/lib/libpython2.7.so

//Utility library needed for vtkpython
PYTHON_UTIL_LIBRARY:FILEPATH=/usr/lib64/libutil.so

//Dependencies for the target
PacMan_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Value Computed by CMake
ParaView_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build

//Value Computed by CMake
ParaView_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source

//Value Computed by CMake
PointSpritePlugin_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/Plugins/PointSprite

//Value Computed by CMake
PointSpritePlugin_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/Plugins/PointSprite

//Dependencies for the target
PointSprite_Plugin_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkPointSpriteRendering;general;vtkPointSpriteRenderingCS;general;vtkPointSpriteGraphics;general;vtkPointSpriteGraphicsCS;general;vtkPointSpriteGraphics;general;vtkPointSpriteRendering;

//Path to a library.
QT_ARTHURPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_ARTHURPLUGIN_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_ARTHURPLUGIN_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/designer/libarthurplugin.so

//Path to a library.
QT_CONTAINEREXTENSION_PLUGIN_DEBUG:FILEPATH=QT_CONTAINEREXTENSION_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_CONTAINEREXTENSION_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/designer/libcontainerextension.so

//Path to a library.
QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/designer/libcustomwidgetplugin.so

//Path to a program.
QT_DBUSCPP2XML_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/qdbuscpp2xml

//Path to a program.
QT_DBUSXML2CPP_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/qdbusxml2cpp

//Path to a program.
QT_DESIGNER_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/designer-qt4

//The location of the Qt docs
QT_DOC_DIR:PATH=/usr/share/doc/qt4

//Path to a program.
QT_LINGUIST_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/linguist-qt4

//Path to a program.
QT_LRELEASE_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/lrelease-qt4

//Path to a program.
QT_LUPDATE_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/lupdate-qt4

//The location of the Qt mkspecs containing qconfig.pri
QT_MKSPECS_DIR:PATH=/usr/lib64/qt4/mkspecs

//Path to a program.
QT_MOC_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/moc-qt4

//Path to a library.
QT_PHONONWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_PHONONWIDGETS_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_PHONONWIDGETS_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/designer/libphononwidgets.so

//Path to a file.
QT_PHONON_INCLUDE_DIR:PATH=/usr/include/phonon

//The Qt PHONON library
QT_PHONON_LIBRARY:STRING=optimized;/usr/lib64/libphonon.so;debug;/usr/lib64/libphonon.so

//Path to a library.
QT_PHONON_LIBRARY_DEBUG:FILEPATH=QT_PHONON_LIBRARY_DEBUG-NOTFOUND

//Path to a library.
QT_PHONON_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libphonon.so

//The location of the Qt plugins
QT_PLUGINS_DIR:PATH=/usr/lib64/qt4/plugins

//Path to a library.
QT_QCNCODECS_PLUGIN_DEBUG:FILEPATH=QT_QCNCODECS_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QCNCODECS_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/codecs/libqcncodecs.so

//Path to a program.
QT_QCOLLECTIONGENERATOR_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/qcollectiongenerator

//Path to a library.
QT_QCOREWLANBEARER_PLUGIN_DEBUG:FILEPATH=QT_QCOREWLANBEARER_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QCOREWLANBEARER_PLUGIN_RELEASE:FILEPATH=QT_QCOREWLANBEARER_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QDECLARATIVEVIEW_PLUGIN_DEBUG:FILEPATH=QT_QDECLARATIVEVIEW_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QDECLARATIVEVIEW_PLUGIN_RELEASE:FILEPATH=QT_QDECLARATIVEVIEW_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QDECORATIONDEFAULT_PLUGIN_DEBUG:FILEPATH=QT_QDECORATIONDEFAULT_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QDECORATIONDEFAULT_PLUGIN_RELEASE:FILEPATH=QT_QDECORATIONDEFAULT_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QDECORATIONWINDOWS_PLUGIN_DEBUG:FILEPATH=QT_QDECORATIONWINDOWS_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QDECORATIONWINDOWS_PLUGIN_RELEASE:FILEPATH=QT_QDECORATIONWINDOWS_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QGENERICBEARER_PLUGIN_DEBUG:FILEPATH=QT_QGENERICBEARER_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QGENERICBEARER_PLUGIN_RELEASE:FILEPATH=QT_QGENERICBEARER_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QGIF_PLUGIN_DEBUG:FILEPATH=QT_QGIF_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QGIF_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/imageformats/libqgif.so

//Path to a library.
QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG:FILEPATH=QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/graphicssystems/libqglgraphicssystem.so

//Path to a library.
QT_QICO_PLUGIN_DEBUG:FILEPATH=QT_QICO_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QICO_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/imageformats/libqico.so

//Path to a library.
QT_QIMSW_MULTI_PLUGIN_DEBUG:FILEPATH=QT_QIMSW_MULTI_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QIMSW_MULTI_PLUGIN_RELEASE:FILEPATH=QT_QIMSW_MULTI_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QJPCODECS_PLUGIN_DEBUG:FILEPATH=QT_QJPCODECS_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QJPCODECS_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/codecs/libqjpcodecs.so

//Path to a library.
QT_QJPEG_PLUGIN_DEBUG:FILEPATH=QT_QJPEG_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QJPEG_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/imageformats/libqjpeg.so

//Path to a library.
QT_QKRCODECS_PLUGIN_DEBUG:FILEPATH=QT_QKRCODECS_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QKRCODECS_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/codecs/libqkrcodecs.so

//Where can the qmake-qt4 library be found
QT_QMAKE_EXECUTABLE:FILEPATH=/usr/bin/qmake-qt4

//Path to a library.
QT_QMNG_PLUGIN_DEBUG:FILEPATH=QT_QMNG_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QMNG_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/imageformats/libqmng.so

//Path to a library.
QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG:FILEPATH=QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE:FILEPATH=QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QSQLDB2_PLUGIN_DEBUG:FILEPATH=QT_QSQLDB2_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QSQLDB2_PLUGIN_RELEASE:FILEPATH=QT_QSQLDB2_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QSQLIBASE_PLUGIN_DEBUG:FILEPATH=QT_QSQLIBASE_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QSQLIBASE_PLUGIN_RELEASE:FILEPATH=QT_QSQLIBASE_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QSQLITE2_PLUGIN_DEBUG:FILEPATH=QT_QSQLITE2_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QSQLITE2_PLUGIN_RELEASE:FILEPATH=QT_QSQLITE2_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QSQLITE_PLUGIN_DEBUG:FILEPATH=QT_QSQLITE_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QSQLITE_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so

//Path to a library.
QT_QSQLMYSQL_PLUGIN_DEBUG:FILEPATH=QT_QSQLMYSQL_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QSQLMYSQL_PLUGIN_RELEASE:FILEPATH=QT_QSQLMYSQL_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QSQLOCI_PLUGIN_DEBUG:FILEPATH=QT_QSQLOCI_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QSQLOCI_PLUGIN_RELEASE:FILEPATH=QT_QSQLOCI_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QSQLODBC_PLUGIN_DEBUG:FILEPATH=QT_QSQLODBC_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QSQLODBC_PLUGIN_RELEASE:FILEPATH=QT_QSQLODBC_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QSQLPSQL_PLUGIN_DEBUG:FILEPATH=QT_QSQLPSQL_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QSQLPSQL_PLUGIN_RELEASE:FILEPATH=QT_QSQLPSQL_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QSQLTDS_PLUGIN_DEBUG:FILEPATH=QT_QSQLTDS_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QSQLTDS_PLUGIN_RELEASE:FILEPATH=QT_QSQLTDS_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QSVGICON_PLUGIN_DEBUG:FILEPATH=QT_QSVGICON_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QSVGICON_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/iconengines/libqsvgicon.so

//Path to a library.
QT_QSVG_PLUGIN_DEBUG:FILEPATH=QT_QSVG_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QSVG_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/imageformats/libqsvg.so

//Path to a library.
QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/designer/libqt3supportwidgets.so

//Path to a file.
QT_QT3SUPPORT_INCLUDE_DIR:PATH=/usr/include/Qt3Support

//The Qt QT3SUPPORT library
QT_QT3SUPPORT_LIBRARY:STRING=optimized;/usr/lib64/libQt3Support.so;debug;/usr/lib64/libQt3Support_debug.so

//Path to a library.
QT_QT3SUPPORT_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQt3Support_debug.so

//Path to a library.
QT_QT3SUPPORT_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQt3Support.so

//Path to a library.
QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/accessible/libqtaccessiblecompatwidgets.so

//Path to a library.
QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/accessible/libqtaccessiblewidgets.so

//Path to a file.
QT_QTASSISTANTCLIENT_INCLUDE_DIR:PATH=/usr/include/QtAssistant

//The Qt QTASSISTANTCLIENT library
QT_QTASSISTANTCLIENT_LIBRARY:STRING=optimized;/usr/lib64/libQtAssistantClient.so;debug;/usr/lib64/libQtAssistantClient_debug.so

//Path to a library.
QT_QTASSISTANTCLIENT_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtAssistantClient_debug.so

//Path to a library.
QT_QTASSISTANTCLIENT_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtAssistantClient.so

//Path to a file.
QT_QTASSISTANT_INCLUDE_DIR:PATH=/usr/include/QtAssistant

//The Qt QTASSISTANT library
QT_QTASSISTANT_LIBRARY:STRING=optimized;/usr/lib64/libQtAssistantClient.so;debug;/usr/lib64/libQtAssistantClient_debug.so

//Path to a library.
QT_QTASSISTANT_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtAssistantClient_debug.so

//Path to a library.
QT_QTASSISTANT_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtAssistantClient.so

//The Qt QTCLUCENE library
QT_QTCLUCENE_LIBRARY:STRING=optimized;/usr/lib64/libQtCLucene.so;debug;/usr/lib64/libQtCLucene_debug.so

//Path to a library.
QT_QTCLUCENE_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtCLucene_debug.so

//Path to a library.
QT_QTCLUCENE_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtCLucene.so

//Path to a file.
QT_QTCORE_INCLUDE_DIR:PATH=/usr/include/QtCore

//The Qt QTCORE library
QT_QTCORE_LIBRARY:STRING=optimized;/usr/lib64/libQtCore.so;debug;/usr/lib64/libQtCore_debug.so

//Path to a library.
QT_QTCORE_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtCore_debug.so

//Path to a library.
QT_QTCORE_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtCore.so

//Path to a file.
QT_QTDBUS_INCLUDE_DIR:PATH=/usr/include/QtDBus

//The Qt QTDBUS library
QT_QTDBUS_LIBRARY:STRING=optimized;/usr/lib64/libQtDBus.so;debug;/usr/lib64/libQtDBus_debug.so

//Path to a library.
QT_QTDBUS_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtDBus_debug.so

//Path to a library.
QT_QTDBUS_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtDBus.so

//Path to a file.
QT_QTDECLARATIVE_INCLUDE_DIR:PATH=QT_QTDECLARATIVE_INCLUDE_DIR-NOTFOUND

//The Qt QTDECLARATIVE library
QT_QTDECLARATIVE_LIBRARY:STRING=

//Path to a library.
QT_QTDECLARATIVE_LIBRARY_DEBUG:FILEPATH=QT_QTDECLARATIVE_LIBRARY_DEBUG-NOTFOUND

//Path to a library.
QT_QTDECLARATIVE_LIBRARY_RELEASE:FILEPATH=QT_QTDECLARATIVE_LIBRARY_RELEASE-NOTFOUND

//Path to a file.
QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR:PATH=/usr/include/QtDesigner

//The Qt QTDESIGNERCOMPONENTS library
QT_QTDESIGNERCOMPONENTS_LIBRARY:STRING=optimized;/usr/lib64/libQtDesignerComponents.so;debug;/usr/lib64/libQtDesignerComponents_debug.so

//Path to a library.
QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtDesignerComponents_debug.so

//Path to a library.
QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtDesignerComponents.so

//Path to a file.
QT_QTDESIGNER_INCLUDE_DIR:PATH=/usr/include/QtDesigner

//The Qt QTDESIGNER library
QT_QTDESIGNER_LIBRARY:STRING=optimized;/usr/lib64/libQtDesigner.so;debug;/usr/lib64/libQtDesigner_debug.so

//Path to a library.
QT_QTDESIGNER_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtDesigner_debug.so

//Path to a library.
QT_QTDESIGNER_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtDesigner.so

//Path to a library.
QT_QTGA_PLUGIN_DEBUG:FILEPATH=QT_QTGA_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QTGA_PLUGIN_RELEASE:FILEPATH=QT_QTGA_PLUGIN_RELEASE-NOTFOUND

//Path to a file.
QT_QTGUI_INCLUDE_DIR:PATH=/usr/include/QtGui

//The Qt QTGUI library
QT_QTGUI_LIBRARY:STRING=optimized;/usr/lib64/libQtGui.so;debug;/usr/lib64/libQtGui_debug.so

//Path to a library.
QT_QTGUI_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtGui_debug.so

//Path to a library.
QT_QTGUI_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtGui.so

//Path to a file.
QT_QTHELP_INCLUDE_DIR:PATH=/usr/include/QtHelp

//The Qt QTHELP library
QT_QTHELP_LIBRARY:STRING=optimized;/usr/lib64/libQtHelp.so;debug;/usr/lib64/libQtHelp_debug.so

//Path to a library.
QT_QTHELP_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtHelp_debug.so

//Path to a library.
QT_QTHELP_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtHelp.so

//Path to a library.
QT_QTIFF_PLUGIN_DEBUG:FILEPATH=QT_QTIFF_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QTIFF_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/imageformats/libqtiff.so

//Path to a file.
QT_QTMOTIF_INCLUDE_DIR:PATH=QT_QTMOTIF_INCLUDE_DIR-NOTFOUND

//The Qt QTMOTIF library
QT_QTMOTIF_LIBRARY:STRING=

//Path to a library.
QT_QTMOTIF_LIBRARY_DEBUG:FILEPATH=QT_QTMOTIF_LIBRARY_DEBUG-NOTFOUND

//Path to a library.
QT_QTMOTIF_LIBRARY_RELEASE:FILEPATH=QT_QTMOTIF_LIBRARY_RELEASE-NOTFOUND

//Path to a file.
QT_QTMULTIMEDIA_INCLUDE_DIR:PATH=/usr/include/QtMultimedia

//The Qt QTMULTIMEDIA library
QT_QTMULTIMEDIA_LIBRARY:STRING=optimized;/usr/lib64/libQtMultimedia.so;debug;/usr/lib64/libQtMultimedia_debug.so

//Path to a library.
QT_QTMULTIMEDIA_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtMultimedia_debug.so

//Path to a library.
QT_QTMULTIMEDIA_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtMultimedia.so

//Path to a file.
QT_QTNETWORK_INCLUDE_DIR:PATH=/usr/include/QtNetwork

//The Qt QTNETWORK library
QT_QTNETWORK_LIBRARY:STRING=optimized;/usr/lib64/libQtNetwork.so;debug;/usr/lib64/libQtNetwork_debug.so

//Path to a library.
QT_QTNETWORK_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtNetwork_debug.so

//Path to a library.
QT_QTNETWORK_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtNetwork.so

//Path to a file.
QT_QTNSPLUGIN_INCLUDE_DIR:PATH=QT_QTNSPLUGIN_INCLUDE_DIR-NOTFOUND

//The Qt QTNSPLUGIN library
QT_QTNSPLUGIN_LIBRARY:STRING=

//Path to a library.
QT_QTNSPLUGIN_LIBRARY_DEBUG:FILEPATH=QT_QTNSPLUGIN_LIBRARY_DEBUG-NOTFOUND

//Path to a library.
QT_QTNSPLUGIN_LIBRARY_RELEASE:FILEPATH=QT_QTNSPLUGIN_LIBRARY_RELEASE-NOTFOUND

//Path to a file.
QT_QTOPENGL_INCLUDE_DIR:PATH=/usr/include/QtOpenGL

//The Qt QTOPENGL library
QT_QTOPENGL_LIBRARY:STRING=optimized;/usr/lib64/libQtOpenGL.so;debug;/usr/lib64/libQtOpenGL_debug.so

//Path to a library.
QT_QTOPENGL_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtOpenGL_debug.so

//Path to a library.
QT_QTOPENGL_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtOpenGL.so

//Path to a library.
QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG:FILEPATH=QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/graphicssystems/libqtracegraphicssystem.so

//Path to a library.
QT_QTSCRIPTDBUS_PLUGIN_DEBUG:FILEPATH=QT_QTSCRIPTDBUS_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QTSCRIPTDBUS_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/script/libqtscriptdbus.so

//Path to a file.
QT_QTSCRIPTTOOLS_INCLUDE_DIR:PATH=/usr/include/QtScriptTools

//The Qt QTSCRIPTTOOLS library
QT_QTSCRIPTTOOLS_LIBRARY:STRING=optimized;/usr/lib64/libQtScriptTools.so;debug;/usr/lib64/libQtScriptTools_debug.so

//Path to a library.
QT_QTSCRIPTTOOLS_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtScriptTools_debug.so

//Path to a library.
QT_QTSCRIPTTOOLS_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtScriptTools.so

//Path to a file.
QT_QTSCRIPT_INCLUDE_DIR:PATH=/usr/include/QtScript

//The Qt QTSCRIPT library
QT_QTSCRIPT_LIBRARY:STRING=optimized;/usr/lib64/libQtScript.so;debug;/usr/lib64/libQtScript_debug.so

//Path to a library.
QT_QTSCRIPT_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtScript_debug.so

//Path to a library.
QT_QTSCRIPT_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtScript.so

//Path to a file.
QT_QTSQL_INCLUDE_DIR:PATH=/usr/include/QtSql

//The Qt QTSQL library
QT_QTSQL_LIBRARY:STRING=optimized;/usr/lib64/libQtSql.so;debug;/usr/lib64/libQtSql_debug.so

//Path to a library.
QT_QTSQL_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtSql_debug.so

//Path to a library.
QT_QTSQL_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtSql.so

//Path to a file.
QT_QTSVG_INCLUDE_DIR:PATH=/usr/include/QtSvg

//The Qt QTSVG library
QT_QTSVG_LIBRARY:STRING=optimized;/usr/lib64/libQtSvg.so;debug;/usr/lib64/libQtSvg_debug.so

//Path to a library.
QT_QTSVG_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtSvg_debug.so

//Path to a library.
QT_QTSVG_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtSvg.so

//Path to a file.
QT_QTTEST_INCLUDE_DIR:PATH=/usr/include/QtTest

//The Qt QTTEST library
QT_QTTEST_LIBRARY:STRING=optimized;/usr/lib64/libQtTest.so;debug;/usr/lib64/libQtTest_debug.so

//Path to a library.
QT_QTTEST_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtTest_debug.so

//Path to a library.
QT_QTTEST_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtTest.so

//Path to a file.
QT_QTUITOOLS_INCLUDE_DIR:PATH=/usr/include/QtUiTools

//The Qt QTUITOOLS library
QT_QTUITOOLS_LIBRARY:STRING=optimized;/usr/lib64/libQtUiTools.a;debug;/usr/lib64/libQtUiTools_debug.a

//Path to a library.
QT_QTUITOOLS_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtUiTools_debug.a

//Path to a library.
QT_QTUITOOLS_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtUiTools.a

//Path to a library.
QT_QTWCODECS_PLUGIN_DEBUG:FILEPATH=QT_QTWCODECS_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QTWCODECS_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/codecs/libqtwcodecs.so

//Path to a file.
QT_QTWEBKIT_INCLUDE_DIR:PATH=/usr/include/QtWebKit

//The Qt QTWEBKIT library
QT_QTWEBKIT_LIBRARY:STRING=optimized;/usr/lib64/libQtWebKit.so;debug;/usr/lib64/libQtWebKit.so

//Path to a library.
QT_QTWEBKIT_LIBRARY_DEBUG:FILEPATH=QT_QTWEBKIT_LIBRARY_DEBUG-NOTFOUND

//Path to a library.
QT_QTWEBKIT_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtWebKit.so

//Path to a file.
QT_QTXMLPATTERNS_INCLUDE_DIR:PATH=/usr/include/QtXmlPatterns

//The Qt QTXMLPATTERNS library
QT_QTXMLPATTERNS_LIBRARY:STRING=optimized;/usr/lib64/libQtXmlPatterns.so;debug;/usr/lib64/libQtXmlPatterns_debug.so

//Path to a library.
QT_QTXMLPATTERNS_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtXmlPatterns_debug.so

//Path to a library.
QT_QTXMLPATTERNS_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtXmlPatterns.so

//Path to a file.
QT_QTXML_INCLUDE_DIR:PATH=/usr/include/QtXml

//The Qt QTXML library
QT_QTXML_LIBRARY:STRING=optimized;/usr/lib64/libQtXml.so;debug;/usr/lib64/libQtXml_debug.so

//Path to a library.
QT_QTXML_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtXml_debug.so

//Path to a library.
QT_QTXML_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtXml.so

//Path to a library.
QT_QWEBVIEW_PLUGIN_DEBUG:FILEPATH=QT_QWEBVIEW_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QWEBVIEW_PLUGIN_RELEASE:FILEPATH=QT_QWEBVIEW_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG:FILEPATH=QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE:FILEPATH=QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE-NOTFOUND

//Path to a program.
QT_RCC_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/rcc

//Path to a library.
QT_TASKMENUEXTENSION_PLUGIN_DEBUG:FILEPATH=QT_TASKMENUEXTENSION_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_TASKMENUEXTENSION_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/designer/libtaskmenuextension.so

//The location of the Qt translations
QT_TRANSLATIONS_DIR:PATH=/usr/share/qt4/translations

//Path to a program.
QT_UIC3_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/uic3

//Path to a program.
QT_UIC_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/uic-qt4

//Path to a library.
QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/designer/libworldtimeclockplugin.so

//Value Computed by CMake
RGBZView_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/Plugins/RGBZView

//Dependencies for the target
RGBZView_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Value Computed by CMake
RGBZView_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/Plugins/RGBZView

//Path to scp command, used by CTest for submitting results to
// a Dart server
SCPCOMMAND:FILEPATH=/usr/bin/scp

//Name of the computer/site where compile is being run
SITE:STRING=aci-b.lnx.int.aci.ics.psu.edu

//Dependencies for the target
SLACTools_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Path to the SLURM sbatch executable
SLURM_SBATCH_COMMAND:FILEPATH=SLURM_SBATCH_COMMAND-NOTFOUND

//Path to the SLURM srun executable
SLURM_SRUN_COMMAND:FILEPATH=SLURM_SRUN_COMMAND-NOTFOUND

//Enable CUDA accelerated filters.
SQTK_CUDA:BOOL=OFF

//Enable debug output to stderr.
SQTK_DEBUG:BOOL=OFF

//Explicitly disable SurfaceLIC plugin ctests
SURFACELIC_PLUGIN_TESTING:BOOL=ON

//Path to a program.
SVNCOMMAND:FILEPATH=/usr/bin/svn

//Value Computed by CMake
SciberQuestToolKit_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/Plugins/SciberQuestToolKit

//Dependencies for the target
SciberQuestToolKit_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkSciberQuest;general;vtkSciberQuestCS;general;vtkFiltersFlowPaths;general;vtkSciberQuest;general;vtkPVServerManagerDefault;general;vtksys;

//Value Computed by CMake
SciberQuestToolKit_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/Plugins/SciberQuestToolKit

//Dependencies for the target
StreamingParticles_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Dependencies for the target
SurfaceLIC_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkRenderingLIC;

//Use HIDDEN visibility support if available.
USE_COMPILER_HIDDEN_VISIBILITY:BOOL=ON

//Value Computed by CMake
VPIC_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/VPIC

//Dependencies for the target
VPIC_LIB_DEPENDS:STATIC=general;vtksys;

//Value Computed by CMake
VPIC_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/VPIC

//Value Computed by CMake
VTKEXPAT_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/expat/vtkexpat

//Value Computed by CMake
VTKEXPAT_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/expat/vtkexpat

//Value Computed by CMake
VTKFREETYPE_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/freetype/vtkfreetype

//Value Computed by CMake
VTKFREETYPE_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/freetype/vtkfreetype

//Value Computed by CMake
VTKFTGL_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/ftgl

//Value Computed by CMake
VTKFTGL_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/ftgl

//Value Computed by CMake
VTKGL2PS_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/gl2ps/vtkgl2ps

//Value Computed by CMake
VTKGL2PS_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/gl2ps/vtkgl2ps

//Value Computed by CMake
VTKJPEG_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/jpeg/vtkjpeg

//Value Computed by CMake
VTKJPEG_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/jpeg/vtkjpeg

//Value Computed by CMake
VTKNETCDF_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/netcdf/vtknetcdf

//Value Computed by CMake
VTKNETCDF_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/netcdf/vtknetcdf

//Value Computed by CMake
VTKOGGTHEORA_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/oggtheora/vtkoggtheora

//Disable assemby optimizations
VTKOGGTHEORA_DISABLE_ASM:BOOL=OFF

//Disable the use of floating point code in theora
VTKOGGTHEORA_DISABLE_FLOAT:BOOL=OFF

//Additional linker flags for vtkoggtheora when building as a shared
// library
VTKOGGTHEORA_SHARED_LINKER_FLAGS:STRING=-Wl,--version-script="/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/oggtheora/vtkoggtheora/vtkoggtheora.vscript"

//Value Computed by CMake
VTKOGGTHEORA_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/oggtheora/vtkoggtheora

//Value Computed by CMake
VTKPNG_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/png/vtkpng

//Value Computed by CMake
VTKPNG_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/png/vtkpng

//Value Computed by CMake
VTKTIFF_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/tiff/vtktiff

//Value Computed by CMake
VTKTIFF_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/tiff/vtktiff

//Value Computed by CMake
VTKZLIB_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/zlib/vtkzlib

//Value Computed by CMake
VTKZLIB_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/zlib/vtkzlib

//Build all vtkObject derived classes with object factory new methods.
VTK_ALL_NEW_OBJECT_FACTORY:BOOL=OFF

//Value Computed by CMake
VTK_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK

//Request to build all modules
VTK_BUILD_ALL_MODULES:BOOL=OFF

//Enable modules as needed for testing all the enabled modules
VTK_BUILD_ALL_MODULES_FOR_TESTS:BOOL=OFF

//Build a BenchmarkFreeTypeRendering test that benchmarks freetype
// rendering performance.
VTK_BUILD_FREETYPE_BENCHMARK:BOOL=OFF

//Local directory holding ExternalData objects in the layout %(algo)/%(hash).
VTK_DATA_STORE:PATH=

//Build leak checking support into VTK.
VTK_DEBUG_LEAKS:BOOL=OFF

//Build VTK using kits instead of modules.
VTK_ENABLE_KITS:BOOL=OFF

//Enable vtkpython and pvtkpython binaries
VTK_ENABLE_VTKPYTHON:BOOL=ON

//Add compiler flags to do stricter checking when building debug.
VTK_EXTRA_COMPILER_WARNINGS:BOOL=OFF

//Path to a program.
VTK_GHOSTSCRIPT_EXECUTABLE:FILEPATH=/usr/bin/gs

//Location of the OpenGL extensions header file (glext.h).
VTK_GLEXT_FILE:FILEPATH=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/ParseOGLExt/headers/glext.h

//Location of the GLX extensions header file (glxext.h).
VTK_GLXEXT_FILE:FILEPATH=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/ParseOGLExt/headers/glxext.h

//Request building Imaging modules
VTK_Group_Imaging:BOOL=OFF

//Request building MPI modules
VTK_Group_MPI:BOOL=OFF

//Request building ParaViewCore modules
VTK_Group_ParaViewCore:BOOL=ON

//Request building ParaViewQt modules
VTK_Group_ParaViewQt:BOOL=OFF

//Request building ParaViewRendering modules
VTK_Group_ParaViewRendering:BOOL=ON

//Request building Qt modules
VTK_Group_Qt:BOOL=OFF

//Request building Rendering modules
VTK_Group_Rendering:BOOL=OFF

//Request building of all stand alone modules (no external dependencies
// required)
VTK_Group_StandAlone:BOOL=OFF

//Request building Tk modules
VTK_Group_Tk:BOOL=OFF

//Request building Views modules
VTK_Group_Views:BOOL=OFF

//Request building Web modules
VTK_Group_Web:BOOL=OFF

//Enable buggy OpenGL drivers for testing.
VTK_IGNORE_GLDRIVER_BUGS:BOOL=OFF

//Remove all legacy code completely.
VTK_LEGACY_REMOVE:BOOL=OFF

//Silence all legacy code messages.
VTK_LEGACY_SILENT:BOOL=OFF

//Should all modules build instantiators
VTK_MAKE_INSTANTIATORS:BOOL=OFF

//Max number of threads vktMultiThreader will allocate.
VTK_MAX_THREADS:STRING=64

//The OpenGL library being used supports off screen Mesa calls
VTK_OPENGL_HAS_OSMESA:BOOL=OFF

//Python version to use: 2, 2.x, or empty
VTK_PYTHON_VERSION:STRING=2

VTK_QT_VERSION:STRING=4

//Choose the rendering backend.
VTK_RENDERING_BACKEND:STRING=OpenGL

//Enable OpenGL error check and report
VTK_REPORT_OPENGL_ERRORS:BOOL=ON

//Which multi-threaded parallelism implementation to use. Options
// are Sequential, Simple, Kaapi or TBB
VTK_SMP_IMPLEMENTATION_TYPE:STRING=Sequential

//Value Computed by CMake
VTK_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK

//Build VTK with 64 bit ids
VTK_USE_64BIT_IDS:BOOL=ON

//Use GCC visibility support if available.
VTK_USE_GCC_VISIBILITY:BOOL=OFF

//Enable tests requiring "large" data
VTK_USE_LARGE_DATA:BOOL=OFF

//Use off screen calls by default
VTK_USE_OFFSCREEN:BOOL=OFF

//Use system 'autobahn' Python package
VTK_USE_SYSTEM_AUTOBAHN:BOOL=OFF

//Use system-installed EXPAT
VTK_USE_SYSTEM_EXPAT:BOOL=OFF

//Use system-installed Freetype
VTK_USE_SYSTEM_FREETYPE:BOOL=OFF

//Use system-installed GL2PS
VTK_USE_SYSTEM_GL2PS:BOOL=OFF

//Use system-installed HDF5
VTK_USE_SYSTEM_HDF5:BOOL=ON

//Use system-installed JPEG
VTK_USE_SYSTEM_JPEG:BOOL=OFF

//Use system-installed JsonCpp
VTK_USE_SYSTEM_JSONCPP:BOOL=OFF

//Use the system's libraries by default.
VTK_USE_SYSTEM_LIBRARIES:BOOL=OFF

//Use system-installed LibXml2
VTK_USE_SYSTEM_LIBXML2:BOOL=OFF

//Use system-installed NetCDF
VTK_USE_SYSTEM_NETCDF:BOOL=OFF

//Use system-installed OGGTHEORA
VTK_USE_SYSTEM_OGGTHEORA:BOOL=OFF

//Use system-installed PNG
VTK_USE_SYSTEM_PNG:BOOL=OFF

//Use system-installed Protobuf
VTK_USE_SYSTEM_PROTOBUF:BOOL=OFF

//Use system-installed pugixml
VTK_USE_SYSTEM_PUGIXML:BOOL=OFF

//Use system 'pygments' Python package
VTK_USE_SYSTEM_PYGMENTS:BOOL=OFF

//Use system 'six' Python Module
VTK_USE_SYSTEM_SIX:BOOL=OFF

//Use system-installed TIFF
VTK_USE_SYSTEM_TIFF:BOOL=OFF

//Use system 'twisted' Python package
VTK_USE_SYSTEM_TWISTED:BOOL=OFF

//Use system-installed xdmf2
VTK_USE_SYSTEM_XDMF2:BOOL=OFF

//Use system-installed ZLIB
VTK_USE_SYSTEM_ZLIB:BOOL=OFF

//Use system 'zope' Python package
VTK_USE_SYSTEM_ZOPE:BOOL=OFF

//Use TDx interaction devices
VTK_USE_TDX:BOOL=OFF

//Build VTK with Tk support
VTK_USE_TK:BOOL=OFF

//Use X for VTK render windows
VTK_USE_X:BOOL=OFF

//Build VPIC with MPI
VTK_VPIC_USE_MPI:BOOL=OFF

//Location of the WGL extensions header file (wglext.h).
VTK_WGLEXT_FILE:FILEPATH=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/ParseOGLExt/headers/wglext.h

//Path to a file.
VTK_WRAP_HINTS:FILEPATH=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Wrapping/Tools/hints

//Should VTK Java wrapping be built?
VTK_WRAP_JAVA:BOOL=OFF

//Should VTK Tcl wrapping be built?
VTK_WRAP_TCL:BOOL=OFF

//Build Xdmf with MPI
VTK_XDMF_USE_MPI:BOOL=OFF

//Path to a file.
X11_ICE_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_ICE_LIB:FILEPATH=/usr/lib64/libICE.so

//Path to a file.
X11_SM_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_SM_LIB:FILEPATH=/usr/lib64/libSM.so

//Path to a file.
X11_X11_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_X11_LIB:FILEPATH=/usr/lib64/libX11.so

//Path to a file.
X11_XRes_INCLUDE_PATH:PATH=X11_XRes_INCLUDE_PATH-NOTFOUND

//Path to a library.
X11_XRes_LIB:FILEPATH=X11_XRes_LIB-NOTFOUND

//Path to a file.
X11_XShm_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_XSync_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_XTest_INCLUDE_PATH:PATH=X11_XTest_INCLUDE_PATH-NOTFOUND

//Path to a library.
X11_XTest_LIB:FILEPATH=X11_XTest_LIB-NOTFOUND

//Path to a file.
X11_Xaccessrules_INCLUDE_PATH:PATH=X11_Xaccessrules_INCLUDE_PATH-NOTFOUND

//Path to a file.
X11_Xaccessstr_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xau_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xau_LIB:FILEPATH=/usr/lib64/libXau.so

//Path to a file.
X11_Xcomposite_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xcomposite_LIB:FILEPATH=/usr/lib64/libXcomposite.so

//Path to a file.
X11_Xcursor_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xcursor_LIB:FILEPATH=/usr/lib64/libXcursor.so

//Path to a file.
X11_Xdamage_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xdamage_LIB:FILEPATH=/usr/lib64/libXdamage.so

//Path to a file.
X11_Xdmcp_INCLUDE_PATH:PATH=X11_Xdmcp_INCLUDE_PATH-NOTFOUND

//Path to a library.
X11_Xdmcp_LIB:FILEPATH=X11_Xdmcp_LIB-NOTFOUND

//Path to a library.
X11_Xext_LIB:FILEPATH=/usr/lib64/libXext.so

//Path to a file.
X11_Xfixes_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xfixes_LIB:FILEPATH=/usr/lib64/libXfixes.so

//Path to a file.
X11_Xft_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xft_LIB:FILEPATH=/usr/lib64/libXft.so

//Path to a file.
X11_Xi_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xi_LIB:FILEPATH=/usr/lib64/libXi.so

//Path to a file.
X11_Xinerama_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xinerama_LIB:FILEPATH=/usr/lib64/libXinerama.so

//Path to a file.
X11_Xinput_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xinput_LIB:FILEPATH=/usr/lib64/libXi.so

//Path to a file.
X11_Xkb_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xkbfile_INCLUDE_PATH:PATH=X11_Xkbfile_INCLUDE_PATH-NOTFOUND

//Path to a library.
X11_Xkbfile_LIB:FILEPATH=X11_Xkbfile_LIB-NOTFOUND

//Path to a file.
X11_Xkblib_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xlib_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xmu_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xmu_LIB:FILEPATH=/usr/lib64/libXmu.so

//Path to a file.
X11_Xpm_INCLUDE_PATH:PATH=X11_Xpm_INCLUDE_PATH-NOTFOUND

//Path to a library.
X11_Xpm_LIB:FILEPATH=X11_Xpm_LIB-NOTFOUND

//Path to a file.
X11_Xrandr_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xrandr_LIB:FILEPATH=/usr/lib64/libXrandr.so

//Path to a file.
X11_Xrender_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xrender_LIB:FILEPATH=/usr/lib64/libXrender.so

//Path to a file.
X11_Xscreensaver_INCLUDE_PATH:PATH=X11_Xscreensaver_INCLUDE_PATH-NOTFOUND

//Path to a library.
X11_Xscreensaver_LIB:FILEPATH=X11_Xscreensaver_LIB-NOTFOUND

//Path to a file.
X11_Xshape_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xt_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xt_LIB:FILEPATH=/usr/lib64/libXt.so

//Path to a file.
X11_Xutil_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xv_INCLUDE_PATH:PATH=X11_Xv_INCLUDE_PATH-NOTFOUND

//Path to a library.
X11_Xv_LIB:FILEPATH=X11_Xv_LIB-NOTFOUND

//Path to a library.
X11_Xxf86misc_LIB:FILEPATH=X11_Xxf86misc_LIB-NOTFOUND

//Path to a library.
X11_Xxf86vm_LIB:FILEPATH=/usr/lib64/libXxf86vm.so

//Path to a file.
X11_dpms_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_xf86misc_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_xf86vmode_INCLUDE_PATH:PATH=/usr/include

//XDMF should use MPI
XDMF_BUILD_MPI:BOOL=OFF

//XDMF has Network Distributed Global Memory (NDGM)
XDMF_HAS_NDGM:BOOL=OFF

//Path to a file.
XDMF_HAVE_FCNTL:PATH=/usr/include

//Path to a file.
XDMF_HAVE_MMAN:PATH=/usr/include/sys

//Path to a file.
XDMF_HAVE_NETINET:PATH=/usr/include/netinet

//Use bzip2
XDMF_USE_BZIP2:BOOL=OFF

//Build GZip Compression
XDMF_USE_GZIP:BOOL=OFF

//Build Support for MySQL DataItems
XDMF_USE_MYSQL:BOOL=OFF

//Path to a file.
ZLIB_INCLUDE_DIR:PATH=/usr/include

//Path to a library.
ZLIB_LIBRARY:FILEPATH=/usr/lib64/libz.so

//Value Computed by CMake
alglib_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/alglib

//Value Computed by CMake
alglib_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/alglib

//Value Computed by CMake
netcdf_cxx_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/netcdf/vtknetcdf/cxx

//Value Computed by CMake
netcdf_cxx_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/netcdf/vtknetcdf/cxx

//Value Computed by CMake
netcdf_libdispatch_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch

//Value Computed by CMake
netcdf_libdispatch_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch

//Value Computed by CMake
netcdf_liblib_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/netcdf/vtknetcdf/liblib

//Value Computed by CMake
netcdf_liblib_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/netcdf/vtknetcdf/liblib

//Value Computed by CMake
netcdf_libsrc_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/netcdf/vtknetcdf/libsrc

//Value Computed by CMake
netcdf_libsrc_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/netcdf/vtknetcdf/libsrc

//Dependencies for the target
protobuf-lite_LIB_DEPENDS:STATIC=general;-lpthread;

//Value Computed by CMake
protobuf_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/ThirdParty/protobuf/vtkprotobuf

//Dependencies for the target
protobuf_LIB_DEPENDS:STATIC=general;-lpthread;general;/usr/lib64/libz.so;

//Value Computed by CMake
protobuf_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/ThirdParty/protobuf/vtkprotobuf

//Path to smooth.flash data file.
smooth_flash:FILEPATH=smooth_flash-NOTFOUND

//Value Computed by CMake
verdict_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/verdict/vtkverdict

//Dependencies for target
verdict_LIB_DEPENDS:STATIC=

//Value Computed by CMake
verdict_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/verdict/vtkverdict

//Dependencies for the target
vtkChartsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkChartsCore;

//Dependencies for the target
vtkChartsCorePythonD_LIB_DEPENDS:STATIC=general;vtkChartsCore;general;vtkWrappingPythonCore;general;vtkCommonColorPythonD;general;vtkInfovisCorePythonD;general;vtkRenderingContext2DPythonD;

//Dependencies for the target
vtkChartsCorePython_LIB_DEPENDS:STATIC=general;vtkChartsCorePythonD;

//Dependencies for the target
vtkChartsCore_LIB_DEPENDS:STATIC=general;vtkRenderingContext2D;general;vtkCommonColor;general;vtkInfovisCore;

//Dependencies for the target
vtkClientServer_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/lib/libpython2.7.so;general;vtkPythonInterpreter;general;vtkWrappingPythonCore;

//Dependencies for the target
vtkCommonColorCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonColor;

//Dependencies for the target
vtkCommonColorPythonD_LIB_DEPENDS:STATIC=general;vtkCommonColor;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;

//Dependencies for the target
vtkCommonColorPython_LIB_DEPENDS:STATIC=general;vtkCommonColorPythonD;

//Dependencies for the target
vtkCommonColor_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;

//Dependencies for the target
vtkCommonComputationalGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonComputationalGeometry;

//Dependencies for the target
vtkCommonComputationalGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkCommonComputationalGeometry;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;

//Dependencies for the target
vtkCommonComputationalGeometryPython_LIB_DEPENDS:STATIC=general;vtkCommonComputationalGeometryPythonD;

//Dependencies for the target
vtkCommonComputationalGeometry_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonSystem;

//Dependencies for the target
vtkCommonCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonCore;

//Dependencies for the target
vtkCommonCorePythonD_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkWrappingPythonCore;

//Dependencies for the target
vtkCommonCorePython_LIB_DEPENDS:STATIC=general;vtkCommonCorePythonD;

//Dependencies for the target
vtkCommonCore_LIB_DEPENDS:STATIC=general;vtksys;general;-lpthread;

//Dependencies for the target
vtkCommonDataModelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonDataModel;

//Dependencies for the target
vtkCommonDataModelPythonD_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkWrappingPythonCore;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;

//Dependencies for the target
vtkCommonDataModelPython_LIB_DEPENDS:STATIC=general;vtkCommonDataModelPythonD;

//Dependencies for the target
vtkCommonDataModel_LIB_DEPENDS:STATIC=general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtksys;

//Dependencies for the target
vtkCommonExecutionModelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonExecutionModel;

//Dependencies for the target
vtkCommonExecutionModelPythonD_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;

//Dependencies for the target
vtkCommonExecutionModelPython_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModelPythonD;

//Dependencies for the target
vtkCommonExecutionModel_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;

//Dependencies for the target
vtkCommonMathCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonMath;

//Dependencies for the target
vtkCommonMathPythonD_LIB_DEPENDS:STATIC=general;vtkCommonMath;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;

//Dependencies for the target
vtkCommonMathPython_LIB_DEPENDS:STATIC=general;vtkCommonMathPythonD;

//Dependencies for the target
vtkCommonMath_LIB_DEPENDS:STATIC=general;vtkCommonCore;

//Dependencies for the target
vtkCommonMiscCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonMisc;

//Dependencies for the target
vtkCommonMiscPythonD_LIB_DEPENDS:STATIC=general;vtkCommonMisc;general;vtkWrappingPythonCore;general;vtkCommonMathPythonD;

//Dependencies for the target
vtkCommonMiscPython_LIB_DEPENDS:STATIC=general;vtkCommonMiscPythonD;

//Dependencies for the target
vtkCommonMisc_LIB_DEPENDS:STATIC=general;vtkCommonMath;

//Dependencies for the target
vtkCommonSystemCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonSystem;

//Dependencies for the target
vtkCommonSystemPythonD_LIB_DEPENDS:STATIC=general;vtkCommonSystem;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;

//Dependencies for the target
vtkCommonSystemPython_LIB_DEPENDS:STATIC=general;vtkCommonSystemPythonD;

//Dependencies for the target
vtkCommonSystem_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtksys;general;-lpthread;

//Dependencies for the target
vtkCommonTransformsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonTransforms;

//Dependencies for the target
vtkCommonTransformsPythonD_LIB_DEPENDS:STATIC=general;vtkCommonTransforms;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonMathPythonD;

//Dependencies for the target
vtkCommonTransformsPython_LIB_DEPENDS:STATIC=general;vtkCommonTransformsPythonD;

//Dependencies for the target
vtkCommonTransforms_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonMath;

//Dependencies for target
vtkDICOMParser_LIB_DEPENDS:STATIC=

//Dependencies for the target
vtkDomainsChemistryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkDomainsChemistry;

//Dependencies for the target
vtkDomainsChemistryPythonD_LIB_DEPENDS:STATIC=general;vtkDomainsChemistry;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkFiltersSourcesPythonD;general;vtkIOXMLPythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkDomainsChemistryPython_LIB_DEPENDS:STATIC=general;vtkDomainsChemistryPythonD;

//Dependencies for the target
vtkDomainsChemistry_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkRenderingCore;general;vtkIOXML;general;vtkFiltersSources;

//Value Computed by CMake
vtkExodus2_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/exodusII/vtkexodusII

//Value Computed by CMake
vtkExodus2_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/exodusII/vtkexodusII

//Dependencies for the target
vtkEyeDomeLightingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkEyeDomeLighting;

//Dependencies for the target
vtkEyeDomeLighting_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGL;

//Dependencies for the target
vtkFiltersAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersAMR;

//Dependencies for the target
vtkFiltersAMRPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkFiltersAMRPython_LIB_DEPENDS:STATIC=general;vtkFiltersAMRPythonD;

//Dependencies for the target
vtkFiltersAMR_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;general;vtkParallelCore;

//Dependencies for the target
vtkFiltersCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersCore;

//Dependencies for the target
vtkFiltersCorePythonD_LIB_DEPENDS:STATIC=general;vtkFiltersCore;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;

//Dependencies for the target
vtkFiltersCorePython_LIB_DEPENDS:STATIC=general;vtkFiltersCorePythonD;

//Dependencies for the target
vtkFiltersCore_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;

//Dependencies for the target
vtkFiltersExtractionCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersExtraction;

//Dependencies for the target
vtkFiltersExtractionPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersExtraction;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersStatisticsPythonD;

//Dependencies for the target
vtkFiltersExtractionPython_LIB_DEPENDS:STATIC=general;vtkFiltersExtractionPythonD;

//Dependencies for the target
vtkFiltersExtraction_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkFiltersStatistics;

//Dependencies for the target
vtkFiltersFlowPathsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersFlowPaths;

//Dependencies for the target
vtkFiltersFlowPathsPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersFlowPaths;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkIOCorePythonD;

//Dependencies for the target
vtkFiltersFlowPathsPython_LIB_DEPENDS:STATIC=general;vtkFiltersFlowPathsPythonD;

//Dependencies for the target
vtkFiltersFlowPaths_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtkIOCore;

//Dependencies for the target
vtkFiltersGeneralCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersGeneral;

//Dependencies for the target
vtkFiltersGeneralPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;general;vtkWrappingPythonCore;general;vtkCommonComputationalGeometryPythonD;general;vtkFiltersCorePythonD;

//Dependencies for the target
vtkFiltersGeneralPython_LIB_DEPENDS:STATIC=general;vtkFiltersGeneralPythonD;

//Dependencies for the target
vtkFiltersGeneral_LIB_DEPENDS:STATIC=general;vtkCommonComputationalGeometry;general;vtkFiltersCore;

//Dependencies for the target
vtkFiltersGenericCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersGeneric;

//Dependencies for the target
vtkFiltersGenericPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersGeneric;general;vtkWrappingPythonCore;general;vtkFiltersCorePythonD;general;vtkFiltersSourcesPythonD;

//Dependencies for the target
vtkFiltersGenericPython_LIB_DEPENDS:STATIC=general;vtkFiltersGenericPythonD;

//Dependencies for the target
vtkFiltersGeneric_LIB_DEPENDS:STATIC=general;vtkFiltersCore;general;vtkFiltersSources;

//Dependencies for the target
vtkFiltersGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersGeometry;

//Dependencies for the target
vtkFiltersGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersGeometry;general;vtkWrappingPythonCore;general;vtkFiltersCorePythonD;

//Dependencies for the target
vtkFiltersGeometryPython_LIB_DEPENDS:STATIC=general;vtkFiltersGeometryPythonD;

//Dependencies for the target
vtkFiltersGeometry_LIB_DEPENDS:STATIC=general;vtkFiltersCore;

//Dependencies for the target
vtkFiltersHybridCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersHybrid;

//Dependencies for the target
vtkFiltersHybridPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersHybrid;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkImagingSourcesPythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkFiltersHybridPython_LIB_DEPENDS:STATIC=general;vtkFiltersHybridPythonD;

//Dependencies for the target
vtkFiltersHybrid_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;general;vtkImagingSources;general;vtkRenderingCore;

//Dependencies for the target
vtkFiltersHyperTreeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersHyperTree;

//Dependencies for the target
vtkFiltersHyperTreePythonD_LIB_DEPENDS:STATIC=general;vtkFiltersHyperTree;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;

//Dependencies for the target
vtkFiltersHyperTreePython_LIB_DEPENDS:STATIC=general;vtkFiltersHyperTreePythonD;

//Dependencies for the target
vtkFiltersHyperTree_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;

//Dependencies for the target
vtkFiltersModelingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersModeling;

//Dependencies for the target
vtkFiltersModelingPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersModeling;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;

//Dependencies for the target
vtkFiltersModelingPython_LIB_DEPENDS:STATIC=general;vtkFiltersModelingPythonD;

//Dependencies for the target
vtkFiltersModeling_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;general;vtkFiltersSources;

//Dependencies for the target
vtkFiltersParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallel;

//Dependencies for the target
vtkFiltersParallelPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersParallel;general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersModelingPythonD;general;vtkParallelCorePythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkFiltersParallelPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelPythonD;

//Dependencies for the target
vtkFiltersParallelStatisticsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelStatistics;

//Dependencies for the target
vtkFiltersParallelStatisticsPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersParallelStatistics;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersStatisticsPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkFiltersParallelStatisticsPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelStatisticsPythonD;

//Dependencies for the target
vtkFiltersParallelStatistics_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersStatistics;general;vtkParallelCore;general;vtkalglib;

//Dependencies for the target
vtkFiltersParallel_LIB_DEPENDS:STATIC=general;vtkFiltersExtraction;general;vtkFiltersGeometry;general;vtkFiltersModeling;general;vtkParallelCore;general;vtkRenderingCore;

//Dependencies for the target
vtkFiltersProgrammableCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersProgrammable;

//Dependencies for the target
vtkFiltersProgrammablePythonD_LIB_DEPENDS:STATIC=general;vtkFiltersProgrammable;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;

//Dependencies for the target
vtkFiltersProgrammablePython_LIB_DEPENDS:STATIC=general;vtkFiltersProgrammablePythonD;

//Dependencies for the target
vtkFiltersProgrammable_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;

//Dependencies for the target
vtkFiltersPythonCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersPython;

//Dependencies for the target
vtkFiltersPythonPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersPython;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;

//Dependencies for the target
vtkFiltersPythonPython_LIB_DEPENDS:STATIC=general;vtkFiltersPythonPythonD;

//Dependencies for the target
vtkFiltersPython_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/lib/libpython2.7.so;general;vtkWrappingPythonCore;

//Dependencies for the target
vtkFiltersSourcesCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersSources;

//Dependencies for the target
vtkFiltersSourcesPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersSources;general;vtkWrappingPythonCore;general;vtkCommonComputationalGeometryPythonD;general;vtkFiltersGeneralPythonD;

//Dependencies for the target
vtkFiltersSourcesPython_LIB_DEPENDS:STATIC=general;vtkFiltersSourcesPythonD;

//Dependencies for the target
vtkFiltersSources_LIB_DEPENDS:STATIC=general;vtkCommonComputationalGeometry;general;vtkFiltersGeneral;

//Dependencies for the target
vtkFiltersStatisticsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersStatistics;

//Dependencies for the target
vtkFiltersStatisticsPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersStatistics;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonTransformsPythonD;general;vtkImagingFourierPythonD;

//Dependencies for the target
vtkFiltersStatisticsPython_LIB_DEPENDS:STATIC=general;vtkFiltersStatisticsPythonD;

//Dependencies for the target
vtkFiltersStatistics_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonTransforms;general;vtkImagingFourier;general;vtkalglib;

//Dependencies for the target
vtkFiltersTextureCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersTexture;

//Dependencies for the target
vtkFiltersTexturePythonD_LIB_DEPENDS:STATIC=general;vtkFiltersTexture;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;

//Dependencies for the target
vtkFiltersTexturePython_LIB_DEPENDS:STATIC=general;vtkFiltersTexturePythonD;

//Dependencies for the target
vtkFiltersTexture_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;

//Dependencies for the target
vtkFiltersVerdictCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersVerdict;

//Dependencies for the target
vtkFiltersVerdictPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersVerdict;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;

//Dependencies for the target
vtkFiltersVerdictPython_LIB_DEPENDS:STATIC=general;vtkFiltersVerdictPythonD;

//Dependencies for the target
vtkFiltersVerdict_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;verdict;

//Dependencies for the target
vtkIOAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOAMR;

//Dependencies for the target
vtkIOAMRPythonD_LIB_DEPENDS:STATIC=general;vtkIOAMR;general;vtkWrappingPythonCore;general;vtkFiltersAMRPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkIOAMRPython_LIB_DEPENDS:STATIC=general;vtkIOAMRPythonD;

//Dependencies for the target
vtkIOAMR_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkParallelCore;general;/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/lib/libhdf5.so;general;/usr/lib64/libsz.so;general;/usr/lib64/libz.so;general;/usr/lib64/librt.so;general;/usr/lib64/libdl.so;general;/usr/lib64/libm.so;general;/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/lib/libhdf5_hl.so;general;/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/lib/libhdf5.so;general;vtksys;

//Dependencies for the target
vtkIOCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOCore;

//Dependencies for the target
vtkIOCorePythonD_LIB_DEPENDS:STATIC=general;vtkIOCore;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;

//Dependencies for the target
vtkIOCorePython_LIB_DEPENDS:STATIC=general;vtkIOCorePythonD;

//Dependencies for the target
vtkIOCore_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkzlib;general;vtksys;

//Dependencies for the target
vtkIOEnSightCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOEnSight;

//Dependencies for the target
vtkIOEnSightPythonD_LIB_DEPENDS:STATIC=general;vtkIOEnSight;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;

//Dependencies for the target
vtkIOEnSightPython_LIB_DEPENDS:STATIC=general;vtkIOEnSightPythonD;

//Dependencies for the target
vtkIOEnSight_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;

//Dependencies for the target
vtkIOExodusCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExodus;

//Dependencies for the target
vtkIOExodusPythonD_LIB_DEPENDS:STATIC=general;vtkIOExodus;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkIOXMLPythonD;

//Dependencies for the target
vtkIOExodusPython_LIB_DEPENDS:STATIC=general;vtkIOExodusPythonD;

//Dependencies for the target
vtkIOExodus_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;general;vtkIOXML;general;vtkexoIIc;general;vtksys;

//Dependencies for the target
vtkIOExportCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExport;

//Dependencies for the target
vtkIOExportPythonD_LIB_DEPENDS:STATIC=general;vtkIOExport;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkFiltersGeometryPythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingGL2PSPythonD;general;vtkRenderingLabelPythonD;general;vtkRenderingOpenGLPythonD;

//Dependencies for the target
vtkIOExportPython_LIB_DEPENDS:STATIC=general;vtkIOExportPythonD;

//Dependencies for the target
vtkIOExport_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkImagingCore;general;vtkRenderingAnnotation;general;vtkRenderingContext2D;general;vtkRenderingCore;general;vtkRenderingFreeType;general;vtkRenderingGL2PS;general;vtkRenderingLabel;general;vtkRenderingOpenGL;general;vtkIOImage;general;vtkFiltersGeometry;general;vtkgl2ps;

//Dependencies for the target
vtkIOGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOGeometry;

//Dependencies for the target
vtkIOGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkIOGeometry;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;

//Dependencies for the target
vtkIOGeometryPython_LIB_DEPENDS:STATIC=general;vtkIOGeometryPythonD;

//Dependencies for the target
vtkIOGeometry_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkIOCore;general;vtkzlib;general;vtkjsoncpp;general;vtksys;

//Dependencies for the target
vtkIOImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOImage;

//Dependencies for the target
vtkIOImagePythonD_LIB_DEPENDS:STATIC=general;vtkIOImage;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOCorePythonD;

//Dependencies for the target
vtkIOImagePython_LIB_DEPENDS:STATIC=general;vtkIOImagePythonD;

//Dependencies for the target
vtkIOImage_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkIOCore;general;vtkjpeg;general;vtkpng;general;vtktiff;general;vtkmetaio;general;vtkDICOMParser;general;vtkzlib;general;vtksys;

//Dependencies for the target
vtkIOImportCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOImport;

//Dependencies for the target
vtkIOImportPythonD_LIB_DEPENDS:STATIC=general;vtkIOImport;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkIOImportPython_LIB_DEPENDS:STATIC=general;vtkIOImportPythonD;

//Dependencies for the target
vtkIOImport_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkFiltersSources;

//Dependencies for the target
vtkIOInfovisCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOInfovis;

//Dependencies for the target
vtkIOInfovisPythonD_LIB_DEPENDS:STATIC=general;vtkIOInfovis;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;general;vtkInfovisCorePythonD;

//Dependencies for the target
vtkIOInfovisPython_LIB_DEPENDS:STATIC=general;vtkIOInfovisPythonD;

//Dependencies for the target
vtkIOInfovis_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkIOCore;general;vtkIOLegacy;general;vtkIOXML;general;vtkInfovisCore;general;vtklibxml2;general;vtksys;

//Dependencies for the target
vtkIOLSDynaCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOLSDyna;

//Dependencies for the target
vtkIOLSDynaPythonD_LIB_DEPENDS:STATIC=general;vtkIOLSDyna;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkIOXMLPythonD;

//Dependencies for the target
vtkIOLSDynaPython_LIB_DEPENDS:STATIC=general;vtkIOLSDynaPythonD;

//Dependencies for the target
vtkIOLSDyna_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkIOXML;general;vtksys;

//Dependencies for the target
vtkIOLegacyCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOLegacy;

//Dependencies for the target
vtkIOLegacyPythonD_LIB_DEPENDS:STATIC=general;vtkIOLegacy;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;

//Dependencies for the target
vtkIOLegacyPython_LIB_DEPENDS:STATIC=general;vtkIOLegacyPythonD;

//Dependencies for the target
vtkIOLegacy_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkIOCore;general;vtksys;

//Dependencies for the target
vtkIOMovieCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMovie;

//Dependencies for the target
vtkIOMoviePythonD_LIB_DEPENDS:STATIC=general;vtkIOMovie;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;

//Dependencies for the target
vtkIOMoviePython_LIB_DEPENDS:STATIC=general;vtkIOMoviePythonD;

//Dependencies for the target
vtkIOMovie_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonSystem;general;vtkIOCore;general;vtkoggtheora;

//Dependencies for the target
vtkIONetCDFCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIONetCDF;

//Dependencies for the target
vtkIONetCDFPythonD_LIB_DEPENDS:STATIC=general;vtkIONetCDF;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;

//Dependencies for the target
vtkIONetCDFPython_LIB_DEPENDS:STATIC=general;vtkIONetCDFPythonD;

//Dependencies for the target
vtkIONetCDF_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkIOCore;general;vtksys;general;vtkNetCDF;general;vtkNetCDF_cxx;

//Dependencies for the target
vtkIOPLYCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOPLY;

//Dependencies for the target
vtkIOPLYPythonD_LIB_DEPENDS:STATIC=general;vtkIOPLY;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkIOGeometryPythonD;

//Dependencies for the target
vtkIOPLYPython_LIB_DEPENDS:STATIC=general;vtkIOPLYPythonD;

//Dependencies for the target
vtkIOPLY_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkIOGeometry;

//Dependencies for the target
vtkIOParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallel;

//Dependencies for the target
vtkIOParallelExodusCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelExodus;

//Dependencies for the target
vtkIOParallelExodusPythonD_LIB_DEPENDS:STATIC=general;vtkIOParallelExodus;general;vtkWrappingPythonCore;general;vtkIOExodusPythonD;general;vtkIOExodusPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkIOParallelExodusPython_LIB_DEPENDS:STATIC=general;vtkIOParallelExodusPythonD;

//Dependencies for the target
vtkIOParallelExodus_LIB_DEPENDS:STATIC=general;vtkIOExodus;general;vtkIOExodus;general;vtkParallelCore;general;vtksys;general;vtkexoIIc;

//Dependencies for the target
vtkIOParallelLSDynaCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelLSDyna;

//Dependencies for the target
vtkIOParallelLSDynaPythonD_LIB_DEPENDS:STATIC=general;vtkIOParallelLSDyna;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkIOLSDynaPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkIOParallelLSDynaPython_LIB_DEPENDS:STATIC=general;vtkIOParallelLSDynaPythonD;

//Dependencies for the target
vtkIOParallelLSDyna_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkIOLSDyna;general;vtkParallelCore;

//Dependencies for the target
vtkIOParallelPythonD_LIB_DEPENDS:STATIC=general;vtkIOParallel;general;vtkWrappingPythonCore;general;vtkFiltersParallelPythonD;general;vtkIOImagePythonD;general;vtkIONetCDFPythonD;general;vtkIOXMLPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkIOParallelPython_LIB_DEPENDS:STATIC=general;vtkIOParallelPythonD;

//Dependencies for the target
vtkIOParallelXMLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelXML;

//Dependencies for the target
vtkIOParallelXMLPythonD_LIB_DEPENDS:STATIC=general;vtkIOParallelXML;general;vtkWrappingPythonCore;general;vtkIOXMLPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkIOParallelXMLPython_LIB_DEPENDS:STATIC=general;vtkIOParallelXMLPythonD;

//Dependencies for the target
vtkIOParallelXML_LIB_DEPENDS:STATIC=general;vtkIOXML;general;vtkParallelCore;general;vtksys;

//Dependencies for the target
vtkIOParallel_LIB_DEPENDS:STATIC=general;vtkFiltersParallel;general;vtkIOImage;general;vtkIONetCDF;general;vtkIOXML;general;vtkParallelCore;general;vtkexoIIc;general;vtkNetCDF;general;vtkNetCDF_cxx;

//Dependencies for the target
vtkIOVPICCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOVPIC;

//Dependencies for the target
vtkIOVPICPythonD_LIB_DEPENDS:STATIC=general;vtkIOVPIC;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkIOVPICPython_LIB_DEPENDS:STATIC=general;vtkIOVPICPythonD;

//Dependencies for the target
vtkIOVPIC_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkParallelCore;general;VPIC;

//Dependencies for the target
vtkIOXMLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOXML;

//Dependencies for the target
vtkIOXMLParserCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOXMLParser;

//Dependencies for the target
vtkIOXMLParserPythonD_LIB_DEPENDS:STATIC=general;vtkIOXMLParser;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;

//Dependencies for the target
vtkIOXMLParserPython_LIB_DEPENDS:STATIC=general;vtkIOXMLParserPythonD;

//Dependencies for the target
vtkIOXMLParser_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkIOCore;general;vtkexpat;

//Dependencies for the target
vtkIOXMLPythonD_LIB_DEPENDS:STATIC=general;vtkIOXML;general;vtkWrappingPythonCore;general;vtkIOGeometryPythonD;general;vtkIOXMLParserPythonD;

//Dependencies for the target
vtkIOXMLPython_LIB_DEPENDS:STATIC=general;vtkIOXMLPythonD;

//Dependencies for the target
vtkIOXML_LIB_DEPENDS:STATIC=general;vtkIOGeometry;general;vtkIOXMLParser;general;vtksys;

//Dependencies for the target
vtkIOXdmf2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOXdmf2;

//Dependencies for the target
vtkIOXdmf2PythonD_LIB_DEPENDS:STATIC=general;vtkIOXdmf2;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersExtractionPythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;

//Dependencies for the target
vtkIOXdmf2Python_LIB_DEPENDS:STATIC=general;vtkIOXdmf2PythonD;

//Dependencies for the target
vtkIOXdmf2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersExtraction;general;vtkIOLegacy;general;vtkIOXML;general;vtksys;general;vtkxdmf2;

//Dependencies for the target
vtkImagingColorCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingColor;

//Dependencies for the target
vtkImagingColorPythonD_LIB_DEPENDS:STATIC=general;vtkImagingColor;general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;

//Dependencies for the target
vtkImagingColorPython_LIB_DEPENDS:STATIC=general;vtkImagingColorPythonD;

//Dependencies for the target
vtkImagingColor_LIB_DEPENDS:STATIC=general;vtkImagingCore;

//Dependencies for the target
vtkImagingCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingCore;

//Dependencies for the target
vtkImagingCorePythonD_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;

//Dependencies for the target
vtkImagingCorePython_LIB_DEPENDS:STATIC=general;vtkImagingCorePythonD;

//Dependencies for the target
vtkImagingCore_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;

//Dependencies for the target
vtkImagingFourierCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingFourier;

//Dependencies for the target
vtkImagingFourierPythonD_LIB_DEPENDS:STATIC=general;vtkImagingFourier;general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;

//Dependencies for the target
vtkImagingFourierPython_LIB_DEPENDS:STATIC=general;vtkImagingFourierPythonD;

//Dependencies for the target
vtkImagingFourier_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtksys;

//Dependencies for the target
vtkImagingGeneralCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingGeneral;

//Dependencies for the target
vtkImagingGeneralPythonD_LIB_DEPENDS:STATIC=general;vtkImagingGeneral;general;vtkWrappingPythonCore;general;vtkImagingSourcesPythonD;

//Dependencies for the target
vtkImagingGeneralPython_LIB_DEPENDS:STATIC=general;vtkImagingGeneralPythonD;

//Dependencies for the target
vtkImagingGeneral_LIB_DEPENDS:STATIC=general;vtkImagingSources;

//Dependencies for the target
vtkImagingHybridCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingHybrid;

//Dependencies for the target
vtkImagingHybridPythonD_LIB_DEPENDS:STATIC=general;vtkImagingHybrid;general;vtkWrappingPythonCore;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;

//Dependencies for the target
vtkImagingHybridPython_LIB_DEPENDS:STATIC=general;vtkImagingHybridPythonD;

//Dependencies for the target
vtkImagingHybrid_LIB_DEPENDS:STATIC=general;vtkIOImage;general;vtkImagingCore;

//Dependencies for the target
vtkImagingMorphologicalCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingMorphological;

//Dependencies for the target
vtkImagingMorphologicalPythonD_LIB_DEPENDS:STATIC=general;vtkImagingMorphological;general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;general;vtkImagingGeneralPythonD;

//Dependencies for the target
vtkImagingMorphologicalPython_LIB_DEPENDS:STATIC=general;vtkImagingMorphologicalPythonD;

//Dependencies for the target
vtkImagingMorphological_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtkImagingGeneral;

//Dependencies for the target
vtkImagingSourcesCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingSources;

//Dependencies for the target
vtkImagingSourcesPythonD_LIB_DEPENDS:STATIC=general;vtkImagingSources;general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;

//Dependencies for the target
vtkImagingSourcesPython_LIB_DEPENDS:STATIC=general;vtkImagingSourcesPythonD;

//Dependencies for the target
vtkImagingSources_LIB_DEPENDS:STATIC=general;vtkImagingCore;

//Dependencies for the target
vtkInfovisCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInfovisCore;

//Dependencies for the target
vtkInfovisCorePythonD_LIB_DEPENDS:STATIC=general;vtkInfovisCore;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;

//Dependencies for the target
vtkInfovisCorePython_LIB_DEPENDS:STATIC=general;vtkInfovisCorePythonD;

//Dependencies for the target
vtkInfovisCore_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkFiltersExtraction;general;vtkFiltersGeneral;

//Dependencies for the target
vtkInteractionImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionImage;

//Dependencies for the target
vtkInteractionImagePythonD_LIB_DEPENDS:STATIC=general;vtkInteractionImage;general;vtkWrappingPythonCore;general;vtkImagingColorPythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;

//Dependencies for the target
vtkInteractionImagePython_LIB_DEPENDS:STATIC=general;vtkInteractionImagePythonD;

//Dependencies for the target
vtkInteractionImage_LIB_DEPENDS:STATIC=general;vtkImagingColor;general;vtkInteractionStyle;general;vtkInteractionWidgets;general;vtkRenderingCore;general;vtkRenderingFreeType;

//Dependencies for the target
vtkInteractionStyleCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionStyle;

//Dependencies for the target
vtkInteractionStylePythonD_LIB_DEPENDS:STATIC=general;vtkInteractionStyle;general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkInteractionStylePython_LIB_DEPENDS:STATIC=general;vtkInteractionStylePythonD;

//Dependencies for the target
vtkInteractionStyle_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkFiltersSources;general;vtkFiltersExtraction;

//Dependencies for the target
vtkInteractionWidgetsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionWidgets;

//Dependencies for the target
vtkInteractionWidgetsPythonD_LIB_DEPENDS:STATIC=general;vtkInteractionWidgets;general;vtkWrappingPythonCore;general;vtkFiltersHybridPythonD;general;vtkFiltersModelingPythonD;general;vtkImagingGeneralPythonD;general;vtkImagingHybridPythonD;general;vtkInteractionStylePythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingVolumePythonD;

//Dependencies for the target
vtkInteractionWidgetsPython_LIB_DEPENDS:STATIC=general;vtkInteractionWidgetsPythonD;

//Dependencies for the target
vtkInteractionWidgets_LIB_DEPENDS:STATIC=general;vtkFiltersHybrid;general;vtkFiltersModeling;general;vtkImagingGeneral;general;vtkImagingHybrid;general;vtkInteractionStyle;general;vtkRenderingAnnotation;general;vtkRenderingFreeType;general;vtkRenderingVolume;

//Dependencies for the target
vtkNetCDF_LIB_DEPENDS:STATIC=general;/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/lib/libhdf5.so;general;/usr/lib64/libsz.so;general;/usr/lib64/libz.so;general;/usr/lib64/librt.so;general;/usr/lib64/libdl.so;general;/usr/lib64/libm.so;general;/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/lib/libhdf5_hl.so;general;/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/lib/libhdf5.so;general;m;

//Dependencies for the target
vtkNetCDF_cxx_LIB_DEPENDS:STATIC=general;vtkNetCDF;

//Dependencies for the target
vtkPVAnimationCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVAnimation;

//Dependencies for the target
vtkPVAnimationPythonD_LIB_DEPENDS:STATIC=general;vtkPVAnimation;general;vtkWrappingPythonCore;general;vtkIOMoviePythonD;general;vtkPVServerManagerCorePythonD;general;vtkPVServerManagerDefaultPythonD;general;vtkPVVTKExtensionsDefaultPythonD;

//Dependencies for the target
vtkPVAnimationPython_LIB_DEPENDS:STATIC=general;vtkPVAnimationPythonD;

//Dependencies for the target
vtkPVAnimation_LIB_DEPENDS:STATIC=general;vtkPVServerManagerCore;general;vtkPVVTKExtensionsDefault;general;vtksys;general;vtkIOMovie;general;vtkPVServerManagerDefault;

//Dependencies for the target
vtkPVCatalystCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVCatalyst;

//Dependencies for the target
vtkPVCatalystPythonD_LIB_DEPENDS:STATIC=general;vtkPVCatalyst;general;vtkWrappingPythonCore;general;vtkPVServerManagerApplicationPythonD;

//Dependencies for the target
vtkPVCatalystPython_LIB_DEPENDS:STATIC=general;vtkPVCatalystPythonD;

//Dependencies for the target
vtkPVCatalystTestDriverCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVCatalystTestDriver;

//Dependencies for the target
vtkPVCatalystTestDriverPythonD_LIB_DEPENDS:STATIC=general;vtkPVCatalystTestDriver;general;vtkWrappingPythonCore;general;vtkPVCatalystPythonD;

//Dependencies for the target
vtkPVCatalystTestDriverPython_LIB_DEPENDS:STATIC=general;vtkPVCatalystTestDriverPythonD;

//Dependencies for the target
vtkPVCatalystTestDriver_LIB_DEPENDS:STATIC=general;vtkPVCatalyst;

//Dependencies for the target
vtkPVCatalyst_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtksys;

//Dependencies for the target
vtkPVClientServerCoreCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreCore;

//Dependencies for the target
vtkPVClientServerCoreCorePythonD_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreCore;general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersProgrammablePythonD;general;vtkPVCommonPythonD;general;vtkPVCommonPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkPythonInterpreterPythonD;

//Dependencies for the target
vtkPVClientServerCoreCorePython_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreCorePythonD;

//Dependencies for the target
vtkPVClientServerCoreCore_LIB_DEPENDS:STATIC=general;vtkFiltersExtraction;general;vtkFiltersParallel;general;vtkFiltersProgrammable;general;vtkPVCommon;general;vtkPVCommon;general;vtkPVVTKExtensionsCore;general;vtkPythonInterpreter;general;vtksys;

//Dependencies for the target
vtkPVClientServerCoreDefaultCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreDefault;

//Dependencies for the target
vtkPVClientServerCoreDefaultPythonD_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreDefault;general;vtkWrappingPythonCore;general;vtkPVClientServerCoreRenderingPythonD;general;vtkPVVTKExtensionsDefaultPythonD;

//Dependencies for the target
vtkPVClientServerCoreDefaultPython_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreDefaultPythonD;

//Dependencies for the target
vtkPVClientServerCoreDefault_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRendering;general;vtkPVVTKExtensionsDefault;general;vtksys;

//Dependencies for the target
vtkPVClientServerCoreRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreRendering;

//Dependencies for the target
vtkPVClientServerCoreRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRendering;general;vtkWrappingPythonCore;general;vtkDomainsChemistryPythonD;general;vtkFiltersAMRPythonD;general;vtkPVClientServerCoreCorePythonD;general;vtkPVVTKExtensionsDefaultPythonD;general;vtkPVVTKExtensionsRenderingPythonD;general;vtkRenderingLabelPythonD;general;vtkRenderingVolumeAMRPythonD;general;vtkRenderingVolumeOpenGLPythonD;general;vtkViewsContext2DPythonD;general;vtkViewsCorePythonD;general;vtkWebGLExporterPythonD;

//Dependencies for the target
vtkPVClientServerCoreRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRenderingPythonD;

//Dependencies for the target
vtkPVClientServerCoreRendering_LIB_DEPENDS:STATIC=general;vtkDomainsChemistry;general;vtkFiltersAMR;general;vtkPVClientServerCoreCore;general;vtkPVVTKExtensionsDefault;general;vtkPVVTKExtensionsRendering;general;vtkRenderingLabel;general;vtkRenderingVolumeAMR;general;vtkRenderingVolumeOpenGL;general;vtkViewsContext2D;general;vtkViewsCore;general;vtkWebGLExporter;general;vtksys;general;vtkzlib;

//Dependencies for the target
vtkPVCommonCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVCommon;

//Dependencies for the target
vtkPVCommonPythonD_LIB_DEPENDS:STATIC=general;vtkPVCommon;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOXMLParserPythonD;

//Dependencies for the target
vtkPVCommonPython_LIB_DEPENDS:STATIC=general;vtkPVCommonPythonD;

//Dependencies for the target
vtkPVCommon_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonCore;general;vtkIOXMLParser;general;vtksys;

//Dependencies for the target
vtkPVPythonCatalystPythonD_LIB_DEPENDS:STATIC=general;vtkPVPythonCatalyst;general;vtkWrappingPythonCore;general;vtkPVCatalystPythonD;general;vtkPythonInterpreterPythonD;

//Dependencies for the target
vtkPVPythonCatalystPython_LIB_DEPENDS:STATIC=general;vtkPVPythonCatalystPythonD;

//Dependencies for the target
vtkPVPythonCatalyst_LIB_DEPENDS:STATIC=general;vtkPVCatalyst;general;vtkPythonInterpreter;general;vtkUtilitiesPythonInitializer;

//Dependencies for the target
vtkPVServerImplementationCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerImplementationCore;

//Dependencies for the target
vtkPVServerImplementationCorePythonD_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationCore;general;vtkWrappingPythonCore;general;vtkPVClientServerCoreCorePythonD;

//Dependencies for the target
vtkPVServerImplementationCorePython_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationCorePythonD;

//Dependencies for the target
vtkPVServerImplementationCore_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreCore;general;protobuf;general;vtksys;

//Dependencies for the target
vtkPVServerImplementationRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerImplementationRendering;

//Dependencies for the target
vtkPVServerImplementationRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationRendering;general;vtkWrappingPythonCore;general;vtkPVClientServerCoreRenderingPythonD;general;vtkPVServerImplementationCorePythonD;

//Dependencies for the target
vtkPVServerImplementationRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationRenderingPythonD;

//Dependencies for the target
vtkPVServerImplementationRendering_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRendering;general;vtkPVServerImplementationCore;

//Dependencies for the target
vtkPVServerManagerApplicationCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerApplication;

//Dependencies for the target
vtkPVServerManagerApplicationPythonD_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkWrappingPythonCore;general;vtkChartsCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkDomainsChemistryPythonD;general;vtkFiltersAMRPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersFlowPathsPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersGenericPythonD;general;vtkFiltersGenericPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersHybridPythonD;general;vtkFiltersHyperTreePythonD;general;vtkFiltersModelingPythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersParallelStatisticsPythonD;general;vtkFiltersProgrammablePythonD;general;vtkFiltersPythonPythonD;general;vtkFiltersSourcesPythonD;general;vtkFiltersStatisticsPythonD;general;vtkFiltersTexturePythonD;general;vtkFiltersVerdictPythonD;general;vtkIOAMRPythonD;general;vtkIOEnSightPythonD;general;vtkIOExodusPythonD;general;vtkIOExportPythonD;general;vtkIOGeometryPythonD;general;vtkIOGeometryPythonD;general;vtkIOImagePythonD;general;vtkIOImagePythonD;general;vtkIOImportPythonD;general;vtkIOInfovisPythonD;general;vtkIOLegacyPythonD;general;vtkIOMoviePythonD;general;vtkIONetCDFPythonD;general;vtkIOPLYPythonD;general;vtkIOParallelPythonD;general;vtkIOParallelPythonD;general;vtkIOParallelExodusPythonD;general;vtkIOParallelLSDynaPythonD;general;vtkIOVPICPythonD;general;vtkIOXMLPythonD;general;vtkIOXMLPythonD;general;vtkIOXdmf2PythonD;general;vtkImagingCorePythonD;general;vtkImagingFourierPythonD;general;vtkImagingHybridPythonD;general;vtkImagingMorphologicalPythonD;general;vtkImagingSourcesPythonD;general;vtkInteractionImagePythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVAnimationPythonD;general;vtkPVServerManagerCorePythonD;general;vtkPVServerManagerDefaultPythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingFreeTypeOpenGLPythonD;general;vtkRenderingLICPythonD;general;vtkRenderingLODPythonD;general;vtkRenderingLabelPythonD;general;vtkRenderingMatplotlibPythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingParallelPythonD;general;vtkRenderingVolumePythonD;general;vtkRenderingVolumeOpenGLPythonD;general;vtkTestingRenderingPythonD;general;vtkViewsContext2DPythonD;

//Dependencies for the target
vtkPVServerManagerApplicationPython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplicationPythonD;

//Dependencies for the target
vtkPVServerManagerApplication_LIB_DEPENDS:STATIC=general;vtkPVServerManagerCore;general;vtksys;general;vtkCommonCoreCS;general;vtkCommonMathCS;general;vtkCommonMiscCS;general;vtkCommonSystemCS;general;vtkCommonTransformsCS;general;vtkCommonDataModelCS;general;vtkCommonColorCS;general;vtkCommonExecutionModelCS;general;vtkFiltersCoreCS;general;vtkCommonComputationalGeometryCS;general;vtkFiltersGeneralCS;general;vtkImagingCoreCS;general;vtkImagingFourierCS;general;vtkFiltersStatisticsCS;general;vtkFiltersExtractionCS;general;vtkInfovisCoreCS;general;vtkFiltersGeometryCS;general;vtkFiltersSourcesCS;general;vtkRenderingCoreCS;general;vtkRenderingFreeTypeCS;general;vtkRenderingContext2DCS;general;vtkChartsCoreCS;general;vtkIOCoreCS;general;vtkIOLegacyCS;general;vtkIOGeometryCS;general;vtkIOXMLParserCS;general;vtkIOXMLCS;general;vtkIOInfovisCS;general;vtkIOImageCS;general;vtkImagingHybridCS;general;vtkRenderingOpenGLCS;general;vtkRenderingContextOpenGLCS;general;vtkTestingRenderingCS;general;vtkImagingSourcesCS;general;vtkFiltersHybridCS;general;vtkFiltersModelingCS;general;vtkImagingGeneralCS;general;vtkInteractionStyleCS;general;vtkImagingColorCS;general;vtkRenderingAnnotationCS;general;vtkRenderingVolumeCS;general;vtkInteractionWidgetsCS;general;vtkViewsCoreCS;general;vtkViewsContext2DCS;general;vtkPythonInterpreterCS;general;vtkDomainsChemistryCS;general;vtkParallelCoreCS;general;vtkFiltersAMRCS;general;vtkIOAMRCS;general;vtkFiltersFlowPathsCS;general;vtkFiltersGenericCS;general;vtkRenderingFreeTypeOpenGLCS;general;vtkRenderingLabelCS;general;vtkFiltersHyperTreeCS;general;vtkFiltersParallelCS;general;vtkFiltersParallelStatisticsCS;general;vtkFiltersProgrammableCS;general;vtkFiltersPythonCS;general;vtkFiltersTextureCS;general;vtkFiltersVerdictCS;general;vtkIOEnSightCS;general;vtkIOExodusCS;general;vtkRenderingGL2PSCS;general;vtkIOExportCS;general;vtkInteractionImageCS;general;vtkRenderingVolumeOpenGLCS;general;vtkIOImportCS;general;vtkIOLSDynaCS;general;vtkIOMovieCS;general;vtkIONetCDFCS;general;vtkIOPLYCS;general;vtkIOParallelCS;general;vtkIOParallelExodusCS;general;vtkIOParallelLSDynaCS;general;vtkIOParallelXMLCS;general;vtkIOVPICCS;general;vtkIOXdmf2CS;general;vtkImagingMorphologicalCS;general;vtkPVCommonCS;general;vtkPVVTKExtensionsCoreCS;general;vtkPVClientServerCoreCoreCS;general;vtkPVServerImplementationCoreCS;general;vtkPVServerManagerCoreCS;general;vtkRenderingLICCS;general;vtkRenderingMatplotlibCS;general;vtkRenderingParallelCS;general;vtkPVVTKExtensionsRenderingCS;general;vtkPVVTKExtensionsDefaultCS;general;vtkRenderingVolumeAMRCS;general;vtkWebGLExporterCS;general;vtkPVClientServerCoreRenderingCS;general;vtkPVClientServerCoreDefaultCS;general;vtkPVServerImplementationRenderingCS;general;vtkPVServerManagerRenderingCS;general;vtkPVServerManagerDefaultCS;general;vtkPVAnimationCS;general;vtkRenderingLODCS;general;vtkWebCoreCS;general;vtkParaViewWebCoreCS;general;vtkPVServerManagerCore;

//Dependencies for the target
vtkPVServerManagerCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerCore;

//Dependencies for the target
vtkPVServerManagerCorePythonD_LIB_DEPENDS:STATIC=general;vtkPVServerManagerCore;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkPVServerImplementationCorePythonD;general;vtkPythonInterpreterPythonD;

//Dependencies for the target
vtkPVServerManagerCorePython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerCorePythonD;

//Dependencies for the target
vtkPVServerManagerCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkPVServerImplementationCore;general;vtksys;general;vtkjsoncpp;general;vtkpugixml;general;vtkPythonInterpreter;

//Dependencies for the target
vtkPVServerManagerDefaultCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerDefault;

//Dependencies for the target
vtkPVServerManagerDefaultPythonD_LIB_DEPENDS:STATIC=general;vtkPVServerManagerDefault;general;vtkWrappingPythonCore;general;vtkPVClientServerCoreDefaultPythonD;general;vtkPVServerManagerRenderingPythonD;general;vtkRenderingVolumeOpenGLPythonD;general;vtkTestingRenderingPythonD;

//Dependencies for the target
vtkPVServerManagerDefaultPython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerDefaultPythonD;

//Dependencies for the target
vtkPVServerManagerDefault_LIB_DEPENDS:STATIC=general;vtkPVServerManagerRendering;general;vtksys;general;vtkRenderingVolumeOpenGL;general;vtkTestingRendering;general;vtkPVClientServerCoreDefault;

//Dependencies for the target
vtkPVServerManagerRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerRendering;

//Dependencies for the target
vtkPVServerManagerRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkPVServerManagerRendering;general;vtkWrappingPythonCore;general;vtkCommonColorPythonD;general;vtkPVServerImplementationRenderingPythonD;general;vtkPVServerManagerCorePythonD;general;vtkPVServerManagerCorePythonD;

//Dependencies for the target
vtkPVServerManagerRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerRenderingPythonD;

//Dependencies for the target
vtkPVServerManagerRendering_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationRendering;general;vtkPVServerManagerCore;general;vtkPVServerManagerCore;general;vtksys;general;vtkCommonColor;

//Dependencies for the target
vtkPVVTKExtensionsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsCore;

//Dependencies for the target
vtkPVVTKExtensionsCorePythonD_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsCore;general;vtkWrappingPythonCore;general;vtkFiltersCorePythonD;general;vtkPVCommonPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkPVVTKExtensionsCorePython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsCorePythonD;

//Dependencies for the target
vtkPVVTKExtensionsCore_LIB_DEPENDS:STATIC=general;vtkFiltersCore;general;vtkPVCommon;general;vtkParallelCore;general;vtksys;

//Dependencies for the target
vtkPVVTKExtensionsDefaultCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsDefault;

//Dependencies for the target
vtkPVVTKExtensionsDefaultPythonD_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsDefault;general;vtkWrappingPythonCore;general;vtkFiltersAMRPythonD;general;vtkFiltersParallelStatisticsPythonD;general;vtkIOEnSightPythonD;general;vtkIOImportPythonD;general;vtkIOInfovisPythonD;general;vtkIOParallelPythonD;general;vtkIOParallelExodusPythonD;general;vtkIOParallelXMLPythonD;general;vtkImagingFourierPythonD;general;vtkImagingSourcesPythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkPVVTKExtensionsRenderingPythonD;

//Dependencies for the target
vtkPVVTKExtensionsDefaultPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsDefaultPythonD;

//Dependencies for the target
vtkPVVTKExtensionsDefault_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkFiltersParallelStatistics;general;vtkIOEnSight;general;vtkIOImport;general;vtkIOParallel;general;vtkIOParallelExodus;general;vtkIOParallelXML;general;vtkImagingFourier;general;vtkImagingSources;general;vtkInteractionWidgets;general;vtkPVVTKExtensionsCore;general;vtkPVVTKExtensionsRendering;general;vtkIOInfovis;general;vtkNetCDF;general;vtkNetCDF_cxx;general;vtksys;

//Dependencies for the target
vtkPVVTKExtensionsRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsRendering;

//Dependencies for the target
vtkPVVTKExtensionsRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsRendering;general;vtkWrappingPythonCore;general;vtkChartsCorePythonD;general;vtkCommonColorPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGenericPythonD;general;vtkFiltersHyperTreePythonD;general;vtkFiltersParallelPythonD;general;vtkIOExportPythonD;general;vtkIOXMLPythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingFreeTypeOpenGLPythonD;general;vtkRenderingLICPythonD;general;vtkRenderingMatplotlibPythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingParallelPythonD;

//Dependencies for the target
vtkPVVTKExtensionsRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsRenderingPythonD;

//Dependencies for the target
vtkPVVTKExtensionsRendering_LIB_DEPENDS:STATIC=general;vtkChartsCore;general;vtkFiltersExtraction;general;vtkFiltersGeneric;general;vtkFiltersHyperTree;general;vtkFiltersParallel;general;vtkIOExport;general;vtkIOXML;general;vtkInteractionStyle;general;vtkInteractionWidgets;general;vtkPVVTKExtensionsCore;general;vtkRenderingAnnotation;general;vtkRenderingFreeTypeOpenGL;general;vtkRenderingLIC;general;vtkRenderingMatplotlib;general;vtkRenderingOpenGL;general;vtkRenderingParallel;general;vtkCommonColor;general;vtkzlib;

//Dependencies for the target
vtkParaViewWebCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParaViewWebCore;

//Dependencies for the target
vtkParaViewWebCorePythonD_LIB_DEPENDS:STATIC=general;vtkParaViewWebCore;general;vtkWrappingPythonCore;general;vtkPVServerManagerDefaultPythonD;general;vtkWebCorePythonD;general;vtkWebGLExporterPythonD;

//Dependencies for the target
vtkParaViewWebCorePython_LIB_DEPENDS:STATIC=general;vtkParaViewWebCorePythonD;

//Dependencies for the target
vtkParaViewWebCore_LIB_DEPENDS:STATIC=general;vtkPVServerManagerDefault;general;vtkWebCore;general;vtkWebGLExporter;

//Dependencies for the target
vtkParallelCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallelCore;

//Dependencies for the target
vtkParallelCorePythonD_LIB_DEPENDS:STATIC=general;vtkParallelCore;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOLegacyPythonD;

//Dependencies for the target
vtkParallelCorePython_LIB_DEPENDS:STATIC=general;vtkParallelCorePythonD;

//Dependencies for the target
vtkParallelCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkIOLegacy;general;vtksys;

//Dependencies for the target
vtkPointSpriteGraphicsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPointSpriteGraphics;

//Dependencies for the target
vtkPointSpriteGraphics_LIB_DEPENDS:STATIC=general;vtkFiltersCore;

//Dependencies for the target
vtkPointSpriteRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPointSpriteRendering;

//Dependencies for the target
vtkPointSpriteRendering_LIB_DEPENDS:STATIC=general;vtkFiltersHybrid;general;vtkImagingCore;general;vtkInteractionStyle;general;vtkRenderingFreeTypeOpenGL;general;vtkRenderingOpenGL;

//Dependencies for the target
vtkPythonInterpreterCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPythonInterpreter;

//Dependencies for the target
vtkPythonInterpreterPythonD_LIB_DEPENDS:STATIC=general;vtkPythonInterpreter;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;

//Dependencies for the target
vtkPythonInterpreterPython_LIB_DEPENDS:STATIC=general;vtkPythonInterpreterPythonD;

//Dependencies for the target
vtkPythonInterpreter_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/lib/libpython2.7.so;general;vtksys;

//Dependencies for the target
vtkRenderingAnnotationCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingAnnotation;

//Dependencies for the target
vtkRenderingAnnotationPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingAnnotation;general;vtkWrappingPythonCore;general;vtkFiltersSourcesPythonD;general;vtkImagingColorPythonD;general;vtkRenderingFreeTypePythonD;

//Dependencies for the target
vtkRenderingAnnotationPython_LIB_DEPENDS:STATIC=general;vtkRenderingAnnotationPythonD;

//Dependencies for the target
vtkRenderingAnnotation_LIB_DEPENDS:STATIC=general;vtkImagingColor;general;vtkRenderingFreeType;general;vtkFiltersSources;

//Dependencies for the target
vtkRenderingContext2DCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingContext2D;

//Dependencies for the target
vtkRenderingContext2DPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingContext2D;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;

//Dependencies for the target
vtkRenderingContext2DPython_LIB_DEPENDS:STATIC=general;vtkRenderingContext2DPythonD;

//Dependencies for the target
vtkRenderingContext2D_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkRenderingFreeType;

//Dependencies for the target
vtkRenderingContextOpenGLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingContextOpenGL;

//Dependencies for the target
vtkRenderingContextOpenGLPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingContextOpenGL;general;vtkWrappingPythonCore;general;vtkRenderingContext2DPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingOpenGLPythonD;

//Dependencies for the target
vtkRenderingContextOpenGLPython_LIB_DEPENDS:STATIC=general;vtkRenderingContextOpenGLPythonD;

//Dependencies for the target
vtkRenderingContextOpenGL_LIB_DEPENDS:STATIC=general;vtkRenderingContext2D;general;vtkRenderingOpenGL;general;vtkRenderingFreeType;

//Dependencies for the target
vtkRenderingCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingCore;

//Dependencies for the target
vtkRenderingCorePythonD_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkWrappingPythonCore;general;vtkCommonColorPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersSourcesPythonD;

//Dependencies for the target
vtkRenderingCorePython_LIB_DEPENDS:STATIC=general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkRenderingCore_LIB_DEPENDS:STATIC=general;vtkCommonColor;general;vtkCommonExecutionModel;general;vtkCommonTransforms;general;vtkFiltersSources;general;vtkFiltersGeometry;general;vtkFiltersExtraction;general;vtksys;

//Dependencies for the target
vtkRenderingFreeTypeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingFreeType;

//Dependencies for the target
vtkRenderingFreeTypeOpenGLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingFreeTypeOpenGL;

//Dependencies for the target
vtkRenderingFreeTypeOpenGLPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingFreeTypeOpenGL;general;vtkWrappingPythonCore;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingOpenGLPythonD;

//Dependencies for the target
vtkRenderingFreeTypeOpenGLPython_LIB_DEPENDS:STATIC=general;vtkRenderingFreeTypeOpenGLPythonD;

//Dependencies for the target
vtkRenderingFreeTypeOpenGL_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkRenderingFreeType;general;vtkRenderingOpenGL;

//Dependencies for the target
vtkRenderingFreeTypePythonD_LIB_DEPENDS:STATIC=general;vtkRenderingFreeType;general;vtkWrappingPythonCore;general;vtkRenderingCorePythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkRenderingFreeTypePython_LIB_DEPENDS:STATIC=general;vtkRenderingFreeTypePythonD;

//Dependencies for the target
vtkRenderingFreeType_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkRenderingCore;general;vtkfreetype;general;vtkftgl;

//Dependencies for the target
vtkRenderingGL2PSCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingGL2PS;

//Dependencies for the target
vtkRenderingGL2PSPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingGL2PS;general;vtkWrappingPythonCore;general;vtkRenderingContextOpenGLPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingOpenGLPythonD;

//Dependencies for the target
vtkRenderingGL2PSPython_LIB_DEPENDS:STATIC=general;vtkRenderingGL2PSPythonD;

//Dependencies for the target
vtkRenderingGL2PS_LIB_DEPENDS:STATIC=general;vtkRenderingContextOpenGL;general;vtkRenderingOpenGL;general;vtkRenderingFreeType;general;vtkgl2ps;

//Dependencies for the target
vtkRenderingLICCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLIC;

//Dependencies for the target
vtkRenderingLICPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingLIC;general;vtkWrappingPythonCore;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;general;vtkImagingSourcesPythonD;general;vtkRenderingOpenGLPythonD;

//Dependencies for the target
vtkRenderingLICPython_LIB_DEPENDS:STATIC=general;vtkRenderingLICPythonD;

//Dependencies for the target
vtkRenderingLIC_LIB_DEPENDS:STATIC=general;vtkIOLegacy;general;vtkIOXML;general;vtkImagingSources;general;vtkRenderingOpenGL;general;vtksys;

//Dependencies for the target
vtkRenderingLODCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLOD;

//Dependencies for the target
vtkRenderingLODPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingLOD;general;vtkWrappingPythonCore;general;vtkFiltersModelingPythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkRenderingLODPython_LIB_DEPENDS:STATIC=general;vtkRenderingLODPythonD;

//Dependencies for the target
vtkRenderingLOD_LIB_DEPENDS:STATIC=general;vtkFiltersModeling;general;vtkRenderingCore;

//Dependencies for the target
vtkRenderingLabelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLabel;

//Dependencies for the target
vtkRenderingLabelPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingLabel;general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkRenderingFreeTypePythonD;

//Dependencies for the target
vtkRenderingLabelPython_LIB_DEPENDS:STATIC=general;vtkRenderingLabelPythonD;

//Dependencies for the target
vtkRenderingLabel_LIB_DEPENDS:STATIC=general;vtkRenderingFreeType;general;vtkFiltersExtraction;

//Dependencies for the target
vtkRenderingMatplotlibCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingMatplotlib;

//Dependencies for the target
vtkRenderingMatplotlibPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingMatplotlib;general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;general;vtkPythonInterpreterPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;

//Dependencies for the target
vtkRenderingMatplotlibPython_LIB_DEPENDS:STATIC=general;vtkRenderingMatplotlibPythonD;

//Dependencies for the target
vtkRenderingMatplotlib_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtkPythonInterpreter;general;vtkRenderingCore;general;vtkRenderingFreeType;general;vtkWrappingPythonCore;

//Dependencies for the target
vtkRenderingOpenGLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingOpenGL;

//Dependencies for the target
vtkRenderingOpenGLPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGL;general;vtkWrappingPythonCore;general;vtkImagingHybridPythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkRenderingOpenGLPython_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGLPythonD;

//Dependencies for the target
vtkRenderingOpenGL_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkImagingHybrid;general;vtksys;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so;general;/usr/lib64/libSM.so;general;/usr/lib64/libICE.so;general;/usr/lib64/libX11.so;general;/usr/lib64/libXext.so;

//Dependencies for the target
vtkRenderingParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingParallel;

//Dependencies for the target
vtkRenderingParallelPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingParallel;general;vtkWrappingPythonCore;general;vtkFiltersParallelPythonD;general;vtkIOImagePythonD;general;vtkParallelCorePythonD;general;vtkRenderingOpenGLPythonD;

//Dependencies for the target
vtkRenderingParallelPython_LIB_DEPENDS:STATIC=general;vtkRenderingParallelPythonD;

//Dependencies for the target
vtkRenderingParallel_LIB_DEPENDS:STATIC=general;vtkFiltersParallel;general;vtkParallelCore;general;vtkRenderingOpenGL;general;vtkIOImage;

//Dependencies for the target
vtkRenderingVolumeAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolumeAMR;

//Dependencies for the target
vtkRenderingVolumeAMRPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeAMR;general;vtkWrappingPythonCore;general;vtkFiltersAMRPythonD;general;vtkParallelCorePythonD;general;vtkRenderingVolumeOpenGLPythonD;

//Dependencies for the target
vtkRenderingVolumeAMRPython_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeAMRPythonD;

//Dependencies for the target
vtkRenderingVolumeAMR_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkParallelCore;general;vtkRenderingVolumeOpenGL;

//Dependencies for the target
vtkRenderingVolumeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolume;

//Dependencies for the target
vtkRenderingVolumeOpenGLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolumeOpenGL;

//Dependencies for the target
vtkRenderingVolumeOpenGLPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeOpenGL;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingVolumePythonD;

//Dependencies for the target
vtkRenderingVolumeOpenGLPython_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeOpenGLPythonD;

//Dependencies for the target
vtkRenderingVolumeOpenGL_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGL;general;vtkRenderingVolume;general;vtksys;general;vtkFiltersGeneral;general;vtkFiltersSources;

//Dependencies for the target
vtkRenderingVolumePythonD_LIB_DEPENDS:STATIC=general;vtkRenderingVolume;general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkRenderingVolumePython_LIB_DEPENDS:STATIC=general;vtkRenderingVolumePythonD;

//Dependencies for the target
vtkRenderingVolume_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtkRenderingCore;

//Dependencies for the target
vtkSciberQuestCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkSciberQuest;

//Dependencies for the target
vtkSciberQuest_LIB_DEPENDS:STATIC=general;vtkFiltersFlowPaths;general;vtkIOLegacy;general;vtkPVCommon;general;vtkPVVTKExtensionsCore;general;vtkParallelCore;general;vtksys;

//Dependencies for the target
vtkTestingGenericBridge_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;

//Dependencies for the target
vtkTestingRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkTestingRendering;

//Dependencies for the target
vtkTestingRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkTestingRendering;general;vtkWrappingPythonCore;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkTestingRenderingPython_LIB_DEPENDS:STATIC=general;vtkTestingRenderingPythonD;

//Dependencies for the target
vtkTestingRendering_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtkRenderingCore;general;vtksys;general;vtkIOImage;

//Dependencies for the target
vtkUtilitiesPythonInitializer_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkWrappingPythonCore;general;vtkWrappingPythonCore;general;vtkCommonCore;

//Dependencies for the target
vtkViewsContext2DCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkViewsContext2D;

//Dependencies for the target
vtkViewsContext2DPythonD_LIB_DEPENDS:STATIC=general;vtkViewsContext2D;general;vtkWrappingPythonCore;general;vtkRenderingContext2DPythonD;general;vtkViewsCorePythonD;

//Dependencies for the target
vtkViewsContext2DPython_LIB_DEPENDS:STATIC=general;vtkViewsContext2DPythonD;

//Dependencies for the target
vtkViewsContext2D_LIB_DEPENDS:STATIC=general;vtkRenderingContext2D;general;vtkViewsCore;

//Dependencies for the target
vtkViewsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkViewsCore;

//Dependencies for the target
vtkViewsCorePythonD_LIB_DEPENDS:STATIC=general;vtkViewsCore;general;vtkWrappingPythonCore;general;vtkInteractionWidgetsPythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkViewsCorePython_LIB_DEPENDS:STATIC=general;vtkViewsCorePythonD;

//Dependencies for the target
vtkViewsCore_LIB_DEPENDS:STATIC=general;vtkInteractionWidgets;general;vtkRenderingCore;

//Dependencies for the target
vtkWebCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkWebCore;

//Dependencies for the target
vtkWebCorePythonD_LIB_DEPENDS:STATIC=general;vtkWebCore;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkIOCorePythonD;general;vtkIOImagePythonD;general;vtkParallelCorePythonD;general;vtkRenderingCorePythonD;general;vtkWebGLExporterPythonD;

//Dependencies for the target
vtkWebCorePython_LIB_DEPENDS:STATIC=general;vtkWebCorePythonD;

//Dependencies for the target
vtkWebCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtksys;general;vtkFiltersGeneral;general;/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/lib/libpython2.7.so;general;vtkIOCore;general;vtkIOImage;general;vtkRenderingCore;general;vtkParallelCore;general;vtkWebGLExporter;

//Dependencies for the target
vtkWebGLExporterCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkWebGLExporter;

//Dependencies for the target
vtkWebGLExporterPythonD_LIB_DEPENDS:STATIC=general;vtkWebGLExporter;general;vtkWrappingPythonCore;general;vtkFiltersGeometryPythonD;general;vtkIOExportPythonD;general;vtkInteractionWidgetsPythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkWebGLExporterPython_LIB_DEPENDS:STATIC=general;vtkWebGLExporterPythonD;

//Dependencies for the target
vtkWebGLExporter_LIB_DEPENDS:STATIC=general;vtkIOExport;general;vtksys;general;vtkFiltersGeometry;general;vtkInteractionWidgets;general;vtkRenderingCore;

//Dependencies for the target
vtkWrappingPythonCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/lib/libpython2.7.so;general;vtksys;

//Dependencies for target
vtkWrappingTools_LIB_DEPENDS:STATIC=

//Dependencies for target
vtkalglib_LIB_DEPENDS:STATIC=

//Dependencies for the target
vtkexoIIc_LIB_DEPENDS:STATIC=general;vtkNetCDF;general;vtkNetCDF_cxx;

//Dependencies for target
vtkexpat_LIB_DEPENDS:STATIC=

//Dependencies for the target
vtkfreetype_LIB_DEPENDS:STATIC=general;vtkzlib;

//Dependencies for the target
vtkftgl_LIB_DEPENDS:STATIC=general;/usr/lib64/libGL.so;general;vtkfreetype;

//Dependencies for the target
vtkgl2ps_LIB_DEPENDS:STATIC=general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so;general;/usr/lib64/libSM.so;general;/usr/lib64/libICE.so;general;/usr/lib64/libX11.so;general;/usr/lib64/libXext.so;general;m;general;vtkzlib;general;vtkpng;general;m;

//Dependencies for target
vtkjpeg_LIB_DEPENDS:STATIC=

//Dependencies for target
vtkjsoncpp_LIB_DEPENDS:STATIC=

//Value Computed by CMake
vtklibxml2_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/libxml2/vtklibxml2

//Dependencies for the target
vtklibxml2_LIB_DEPENDS:STATIC=general;vtkzlib;general;dl;general;-lpthread;general;dl;general;m;

//Value Computed by CMake
vtklibxml2_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/libxml2/vtklibxml2

//Value Computed by CMake
vtkmetaio_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/MetaIO/vtkmetaio

//Dependencies for the target
vtkmetaio_LIB_DEPENDS:STATIC=general;vtkzlib;

//Value Computed by CMake
vtkmetaio_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/MetaIO/vtkmetaio

//Dependencies for target
vtkoggtheora_LIB_DEPENDS:STATIC=

//Dependencies for the target
vtkpng_LIB_DEPENDS:STATIC=general;vtkzlib;general;-lm;

//Dependencies for target
vtkpugixml_LIB_DEPENDS:STATIC=

//Value Computed by CMake
vtksys_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/KWSys/vtksys

//Dependencies for the target
vtksys_LIB_DEPENDS:STATIC=general;dl;general;dl;

//Value Computed by CMake
vtksys_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/KWSys/vtksys

//Dependencies for the target
vtktiff_LIB_DEPENDS:STATIC=general;vtkzlib;general;vtkjpeg;general;-lm;

//Dependencies for the target
vtkxdmf2_LIB_DEPENDS:STATIC=general;vtklibxml2;general;/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/lib/libhdf5.so;general;/usr/lib64/libsz.so;general;/usr/lib64/libz.so;general;/usr/lib64/librt.so;general;/usr/lib64/libdl.so;general;/usr/lib64/libm.so;general;/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/lib/libhdf5_hl.so;general;/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/lib/libhdf5.so;

//Dependencies for target
vtkzlib_LIB_DEPENDS:STATIC=

//Value Computed by CMake
xdmf2_BINARY_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/xdmf2/vtkxdmf2

//Value Computed by CMake
xdmf2_SOURCE_DIR:STATIC=/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/xdmf2/vtkxdmf2


########################
# INTERNAL cache entries
########################

ALGLIB_SHARED_LIB:INTERNAL=ON
//Host Arcitecture : Linux IRIXN32 IRIX64 AIX CYGWIN
ARCH_TO_BUILD:INTERNAL=Linux
//ADVANCED property for variable: BZRCOMMAND
BZRCOMMAND-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
CMAKE_ANSI_FOR_SCOPE:INTERNAL=TRUE
//Have include iostream
CMAKE_ANSI_STREAM_HEADERS:INTERNAL=1
//ADVANCED property for variable: CMAKE_AR
CMAKE_AR-ADVANCED:INTERNAL=1
//MODIFIED property for variable: CMAKE_BUILD_TYPE
CMAKE_BUILD_TYPE-MODIFIED:INTERNAL=ON
//STRINGS property for variable: CMAKE_BUILD_TYPE
CMAKE_BUILD_TYPE-STRINGS:INTERNAL=Debug;Release;MinSizeRel;RelWithDebInfo
//This is the directory where this CMakeCache.txt was created
CMAKE_CACHEFILE_DIR:INTERNAL=/storage/home/guv106/software/ParaView-v4.3.1-build
//Major version of cmake used to create the current loaded cache
CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3
//Minor version of cmake used to create the current loaded cache
CMAKE_CACHE_MINOR_VERSION:INTERNAL=1
//Patch version of cmake used to create the current loaded cache
CMAKE_CACHE_PATCH_VERSION:INTERNAL=0
//ADVANCED property for variable: CMAKE_COLOR_MAKEFILE
CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=/opt/aci/sw/cmake/3.1.0_gcc-4.9.2-1/bin/cmake
//Path to cpack program executable.
CMAKE_CPACK_COMMAND:INTERNAL=/opt/aci/sw/cmake/3.1.0_gcc-4.9.2-1/bin/cpack
//ADVANCED property for variable: CMAKE_CTEST_COMMAND
CMAKE_CTEST_COMMAND-ADVANCED:INTERNAL=1
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=/opt/aci/sw/cmake/3.1.0_gcc-4.9.2-1/bin/ctest
//ADVANCED property for variable: CMAKE_CXX_COMPILER
CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS
CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG
CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL
CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE
CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO
CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_COMPILER
CMAKE_C_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS
CMAKE_C_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG
CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL
CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE
CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO
CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Path to cache edit program executable.
CMAKE_EDIT_COMMAND:INTERNAL=/opt/aci/sw/cmake/3.1.0_gcc-4.9.2-1/bin/ccmake
//Executable file format
CMAKE_EXECUTABLE_FORMAT:INTERNAL=ELF
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS
CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG
CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE
CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS
CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1
//Name of external makefile project generator.
CMAKE_EXTRA_GENERATOR:INTERNAL=
//ADVANCED property for variable: CMAKE_Fortran_COMPILER
CMAKE_Fortran_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_Fortran_FLAGS
CMAKE_Fortran_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_Fortran_FLAGS_DEBUG
CMAKE_Fortran_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_Fortran_FLAGS_MINSIZEREL
CMAKE_Fortran_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_Fortran_FLAGS_RELEASE
CMAKE_Fortran_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_Fortran_FLAGS_RELWITHDEBINFO
CMAKE_Fortran_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Name of generator.
CMAKE_GENERATOR:INTERNAL=Unix Makefiles
//Name of generator platform.
CMAKE_GENERATOR_PLATFORM:INTERNAL=
//Name of generator toolset.
CMAKE_GENERATOR_TOOLSET:INTERNAL=
//Result of TRY_COMPILE
CMAKE_HAS_ANSI_STRING_STREAM:INTERNAL=TRUE
//Have function connect
CMAKE_HAVE_CONNECT:INTERNAL=1
//Have function gethostbyname
CMAKE_HAVE_GETHOSTBYNAME:INTERNAL=1
//Have symbol pthread_create
CMAKE_HAVE_LIBC_CREATE:INTERNAL=
//Have library pthreads
CMAKE_HAVE_PTHREADS_CREATE:INTERNAL=
//Have library pthread
CMAKE_HAVE_PTHREAD_CREATE:INTERNAL=1
//Have include pthread.h
CMAKE_HAVE_PTHREAD_H:INTERNAL=1
//Have function remove
CMAKE_HAVE_REMOVE:INTERNAL=1
//Have function shmat
CMAKE_HAVE_SHMAT:INTERNAL=1
//Start directory with the top level CMakeLists.txt file for this
// project
CMAKE_HOME_DIRECTORY:INTERNAL=/storage/home/guv106/software/ParaView-v4.3.1-source
//MODIFIED property for variable: CMAKE_INSTALL_PREFIX
CMAKE_INSTALL_PREFIX-MODIFIED:INTERNAL=ON
//Install .so files without execute permission.
CMAKE_INSTALL_SO_NO_EXE:INTERNAL=0
//Have library ICE
CMAKE_LIB_ICE_HAS_ICECONNECTIONNUMBER:INTERNAL=1
//ADVANCED property for variable: CMAKE_LINKER
CMAKE_LINKER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MAKE_PROGRAM
CMAKE_MAKE_PROGRAM-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS
CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG
CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE
CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_NM
CMAKE_NM-ADVANCED:INTERNAL=1
//Does the compiler support ansi for scope.
CMAKE_NO_ANSI_FOR_SCOPE:INTERNAL=0
//ADVANCED property for variable: CMAKE_NO_ANSI_STREAM_HEADERS
CMAKE_NO_ANSI_STREAM_HEADERS-ADVANCED:INTERNAL=1
//Does the compiler support headers like iostream.
CMAKE_NO_ANSI_STREAM_HEADERS:INTERNAL=0
//Does the compiler support sstream
CMAKE_NO_ANSI_STRING_STREAM:INTERNAL=0
//Does the compiler support std::.
CMAKE_NO_STD_NAMESPACE:INTERNAL=0
//number of local generators
CMAKE_NUMBER_OF_LOCAL_GENERATORS:INTERNAL=306
//ADVANCED property for variable: CMAKE_OBJCOPY
CMAKE_OBJCOPY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_OBJDUMP
CMAKE_OBJDUMP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RANLIB
CMAKE_RANLIB-ADVANCED:INTERNAL=1
//Test Support for 64 bit file systems
CMAKE_REQUIRE_LARGE_FILE_SUPPORT:INTERNAL=1
//Path to CMake installation.
CMAKE_ROOT:INTERNAL=/opt/aci/sw/cmake/3.1.0_gcc-4.9.2-1/share/cmake-3.1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG
CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE
CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(unsigned short)
CMAKE_SIZEOF_UNSIGNED_SHORT:INTERNAL=2
//ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH
CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS
CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG
CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE
CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
CMAKE_STD_NAMESPACE:INTERNAL=TRUE
//ADVANCED property for variable: CMAKE_STRIP
CMAKE_STRIP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_THREAD_LIBS
CMAKE_THREAD_LIBS-ADVANCED:INTERNAL=1
//uname command
CMAKE_UNAME:INTERNAL=/bin/uname
//ADVANCED property for variable: CMAKE_USE_RELATIVE_PATHS
CMAKE_USE_RELATIVE_PATHS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1
//Result of TEST_BIG_ENDIAN
CMAKE_WORDS_BIGENDIAN:INTERNAL=0
//Compiler support for a deprecated attribute
COMPILER_HAS_DEPRECATED:INTERNAL=1
//Test COMPILER_HAS_DEPRECATED_ATTR
COMPILER_HAS_DEPRECATED_ATTR:INTERNAL=1
//Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY
COMPILER_HAS_HIDDEN_INLINE_VISIBILITY:INTERNAL=1
//Test COMPILER_HAS_HIDDEN_VISIBILITY
COMPILER_HAS_HIDDEN_VISIBILITY:INTERNAL=1
//ADVANCED property for variable: COVERAGE_COMMAND
COVERAGE_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: COVERAGE_EXTRA_FLAGS
COVERAGE_EXTRA_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CTEST_SUBMIT_RETRY_COUNT
CTEST_SUBMIT_RETRY_COUNT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CTEST_SUBMIT_RETRY_DELAY
CTEST_SUBMIT_RETRY_DELAY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CVSCOMMAND
CVSCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CVS_UPDATE_OPTIONS
CVS_UPDATE_OPTIONS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DART_TESTING_TIMEOUT
DART_TESTING_TIMEOUT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: EXECINFO_LIB
EXECINFO_LIB-ADVANCED:INTERNAL=1
EXECUTABLE_OUTPUT_PATH:INTERNAL=/storage/home/guv106/software/ParaView-v4.3.1-build/ThirdParty/protobuf/vtkprotobuf/bin
//ADVANCED property for variable: EXODUSII_DISABLE_COMPILER_WARNINGS
EXODUSII_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1
//Have include malloc.h
EX_HAVE_MALLOC_H:INTERNAL=1
//ADVANCED property for variable: Eigen_DIR
Eigen_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ExternalData_URL_TEMPLATES
ExternalData_URL_TEMPLATES-ADVANCED:INTERNAL=1
//Details about finding Git
FIND_PACKAGE_MESSAGE_DETAILS_Git:INTERNAL=[/usr/bin/git][v1.7.1()]
//Details about finding HDF5
FIND_PACKAGE_MESSAGE_DETAILS_HDF5:INTERNAL=[/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/lib/libhdf5.so;/usr/lib64/libsz.so;/usr/lib64/libz.so;/usr/lib64/librt.so;/usr/lib64/libdl.so;/usr/lib64/libm.so;/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/lib/libhdf5_hl.so;/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/lib/libhdf5.so][/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/include][v()]
//Details about finding OSMesa
FIND_PACKAGE_MESSAGE_DETAILS_OSMesa:INTERNAL=[/storage/home/guv106/software/mesa-10.5.4/lib/gallium/libOSMesa.so][/storage/home/guv106/software/mesa-10.5.4/include][v()]
//Details about finding OpenGL
FIND_PACKAGE_MESSAGE_DETAILS_OpenGL:INTERNAL=[/usr/lib64/libGL.so][/usr/include][v()]
//Details about finding PythonInterp
FIND_PACKAGE_MESSAGE_DETAILS_PythonInterp:INTERNAL=[/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/bin/python2][v2.7.9()]
//Details about finding PythonLibs
FIND_PACKAGE_MESSAGE_DETAILS_PythonLibs:INTERNAL=[/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/lib/libpython2.7.so][/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/include/python2.7/][v()]
//Details about finding Threads
FIND_PACKAGE_MESSAGE_DETAILS_Threads:INTERNAL=[TRUE][v()]
//Details about finding X11
FIND_PACKAGE_MESSAGE_DETAILS_X11:INTERNAL=[/usr/lib64/libX11.so][/usr/include]
//Details about finding ZLIB
FIND_PACKAGE_MESSAGE_DETAILS_ZLIB:INTERNAL=[/usr/lib64/libz.so][/usr/include][v1.2.3()]
//ADVANCED property for variable: GITCOMMAND
GITCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GIT_EXECUTABLE
GIT_EXECUTABLE-ADVANCED:INTERNAL=1
HASH_MAP_CLASS:INTERNAL=unordered_map
HASH_MAP_H:INTERNAL=tr1/unordered_map
HASH_NAMESPACE:INTERNAL=std::tr1
HASH_SET_CLASS:INTERNAL=unordered_set
HASH_SET_H:INTERNAL=tr1/unordered_set
//Have symbol alloca
HAVE_ALLOCA:INTERNAL=1
//Have include ;alloca.h
HAVE_ALLOCA_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h
HAVE_ANSIDECL_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h
HAVE_ARPA_INET_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h
HAVE_ARPA_NAMESER_H:INTERNAL=1
//Have include assert.h
HAVE_ASSERT_H:INTERNAL=1
//Result of TRY_COMPILE
HAVE_CMAKE_REQUIRE_LARGE_FILE_SUPPORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_UNSIGNED_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_WORDS_BIGENDIAN:INTERNAL=TRUE
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h
HAVE_CTYPE_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h
HAVE_DIRENT_H:INTERNAL=1
//Have include dlfcn.h
HAVE_DLFCN_H:INTERNAL=1
//Have library dl;-lpthread;dl;m
HAVE_DLOPEN:INTERNAL=1
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;dl.h
HAVE_DL_H:INTERNAL=
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h
HAVE_ERRNO_H:INTERNAL=1
//Have include fcntl.h
HAVE_FCNTL_H:INTERNAL=1
//Have include fenv.h
HAVE_FENV_H:INTERNAL=1
//Have symbol finite
HAVE_FINITE:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h
HAVE_FLOAT_H:INTERNAL=1
//Have function floor
HAVE_FLOOR:INTERNAL=
//Have symbol fpclass
HAVE_FPCLASS:INTERNAL=
//Have symbol fprintf
HAVE_FPRINTF:INTERNAL=1
//Have symbol fp_class
HAVE_FP_CLASS:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;fp_class.h
HAVE_FP_CLASS_H:INTERNAL=
//Have symbol ftime
HAVE_FTIME:INTERNAL=1
//NetCDF test 
HAVE_FTRUNCATE:INTERNAL=1
//Test HAVE_GCC_ERROR_RETURN_TYPE
HAVE_GCC_ERROR_RETURN_TYPE:INTERNAL=1
//Test HAVE_GCC_VISIBILITY
HAVE_GCC_VISIBILITY:INTERNAL=1
//Result of TRY_COMPILE
HAVE_GETADDRINFO_COMPILED:INTERNAL=TRUE
//Have function getopt
HAVE_GETOPT:INTERNAL=1
//Have symbol gettimeofday
HAVE_GETTIMEOFDAY:INTERNAL=1
HAVE_HASH_MAP:INTERNAL=1
HAVE_HASH_SET:INTERNAL=1
//Have includes ieeefp.h
HAVE_IEEEFP_H:INTERNAL=
//Have include inttypes.h
HAVE_INTTYPES_H:INTERNAL=1
//Have function isascii
HAVE_ISASCII:INTERNAL=1
//Result of TRY_COMPILE
HAVE_KWSYS_SIZEOF_CHAR:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_KWSYS_SIZEOF___INT64:INTERNAL=FALSE
//Have library dl;
HAVE_LIBDL:INTERNAL=1
//Have include limits.h
HAVE_LIMITS_H:INTERNAL=1
//Have symbol localtime
HAVE_LOCALTIME:INTERNAL=1
//Have include malloc.h
HAVE_MALLOC_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h
HAVE_MATH_H:INTERNAL=1
//Have function memmove
HAVE_MEMMOVE:INTERNAL=1
//Have include memory.h
HAVE_MEMORY_H:INTERNAL=1
//Have function memset
HAVE_MEMSET:INTERNAL=1
//Have function mmap
HAVE_MMAP:INTERNAL=1
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;nan.h
HAVE_NAN_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;ndir.h
HAVE_NDIR_H:INTERNAL=
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h
HAVE_NETDB_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h
HAVE_NETINET_IN_H:INTERNAL=1
//Have function pow
HAVE_POW:INTERNAL=
//Have symbol printf
HAVE_PRINTF:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h
HAVE_PTHREAD_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h;resolv.h
HAVE_RESOLV_H:INTERNAL=1
//Have library dld;dl
HAVE_SHLLOAD:INTERNAL=
//Have symbol signal
HAVE_SIGNAL:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h
HAVE_SIGNAL_H:INTERNAL=1
//Result of TRY_COMPILE
HAVE_SIZEOF_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_FLOAT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_OFF_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_PTRDIFF_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_SIZE_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_SSIZE_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_UCHAR:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_SIZEOF__BOOL:INTERNAL=TRUE
//Have symbol snprintf
HAVE_SNPRINTF:INTERNAL=1
//Result of TRY_COMPILE
HAVE_SOCKLEN_T_COMPILED:INTERNAL=TRUE
//Have symbol sprintf
HAVE_SPRINTF:INTERNAL=1
//Have function sqrt
HAVE_SQRT:INTERNAL=
//Have symbol sscanf
HAVE_SSCANF:INTERNAL=1
//Have symbol stat
HAVE_STAT:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h;resolv.h;stdarg.h
HAVE_STDARG_H:INTERNAL=1
//Have include alloca.h;stdlib.h;sys/types.h;sys/stat.h;unistd.h;fcntl.h;stdio.h;string.h;stddef.h;stdint.h;inttypes.h;stdbool.h
HAVE_STDBOOL_H:INTERNAL=1
//Have include stddef.h
HAVE_STDDEF_H:INTERNAL=1
//Have include stdint.h
HAVE_STDINT_H:INTERNAL=1
//Have include ;stdio.h
HAVE_STDIO_H:INTERNAL=1
//Have include stdlib.h
HAVE_STDLIB_H:INTERNAL=1
//Have function strcasecmp
HAVE_STRCASECMP:INTERNAL=1
//Have function strchr
HAVE_STRCHR:INTERNAL=1
//Have symbol strdup
HAVE_STRDUP:INTERNAL=1
//Have symbol strerror
HAVE_STRERROR:INTERNAL=1
//Have symbol strftime
HAVE_STRFTIME:INTERNAL=1
//Have include strings.h
HAVE_STRINGS_H:INTERNAL=1
//Have include string.h
HAVE_STRING_H:INTERNAL=1
//Have symbol strndup
HAVE_STRNDUP:INTERNAL=1
//Have function strrchr
HAVE_STRRCHR:INTERNAL=1
//Have function strstr
HAVE_STRSTR:INTERNAL=1
//Have function strtol
HAVE_STRTOL:INTERNAL=1
//Have function strtoll
HAVE_STRTOLL:INTERNAL=1
//Have function strtoul
HAVE_STRTOUL:INTERNAL=1
//NetCDF test 
HAVE_ST_BLKSIZE:INTERNAL=1
//Result of TRY_COMPILE
HAVE_SYS_DIR_H_COMPILED:INTERNAL=TRUE
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h;resolv.h;stdarg.h;sys/mman.h
HAVE_SYS_MMAN_H:INTERNAL=1
//Result of TRY_COMPILE
HAVE_SYS_NDIR_H_COMPILED:INTERNAL=FALSE
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h
HAVE_SYS_SELECT_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h
HAVE_SYS_SOCKET_H:INTERNAL=1
//Have include sys/stat.h
HAVE_SYS_STAT_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h;resolv.h;stdarg.h;sys/mman.h;sys/timeb.h
HAVE_SYS_TIMEB_H:INTERNAL=1
//Have include sys/time.h
HAVE_SYS_TIME_H:INTERNAL=1
//Have include sys/types.h
HAVE_SYS_TYPES_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h
HAVE_TIME_H:INTERNAL=1
//Have include unistd.h
HAVE_UNISTD_H:INTERNAL=1
//Result of TRY_COMPILE
HAVE_VA_COPY_COMPILED:INTERNAL=TRUE
//Have symbol vfprintf
HAVE_VFPRINTF:INTERNAL=1
//Have symbol vsnprintf
HAVE_VSNPRINTF:INTERNAL=1
//Have symbol vsprintf
HAVE_VSPRINTF:INTERNAL=1
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_INT16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_INT32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_INT64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_UINT16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_UINT32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_U_INT16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_U_INT32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF_CHAR:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF_FLOAT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF___INT64:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_VTK_UINTPTR_T:INTERNAL=TRUE
//Have includes windows.h
HAVE_WINDOWS_H:INTERNAL=
//Have symbol _stat
HAVE__STAT:INTERNAL=
//Result of TRY_COMPILE
HAVE___VA_COPY_COMPILED:INTERNAL=TRUE
//ADVANCED property for variable: HDF5_CXX_COMPILER_EXECUTABLE
HDF5_CXX_COMPILER_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_C_COMPILER_EXECUTABLE
HDF5_C_COMPILER_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_C_INCLUDE_DIR
HDF5_C_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_DIFF_EXECUTABLE
HDF5_DIFF_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_Fortran_COMPILER_EXECUTABLE
HDF5_Fortran_COMPILER_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_HL_INCLUDE_DIR
HDF5_HL_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_IS_PARALLEL
HDF5_IS_PARALLEL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_dl_LIBRARY_DEBUG
HDF5_dl_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_dl_LIBRARY_RELEASE
HDF5_dl_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_hdf5_LIBRARY_DEBUG
HDF5_hdf5_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_hdf5_LIBRARY_RELEASE
HDF5_hdf5_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_hdf5_hl_LIBRARY_DEBUG
HDF5_hdf5_hl_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_hdf5_hl_LIBRARY_RELEASE
HDF5_hdf5_hl_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_m_LIBRARY_DEBUG
HDF5_m_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_m_LIBRARY_RELEASE
HDF5_m_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_rt_LIBRARY_DEBUG
HDF5_rt_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_rt_LIBRARY_RELEASE
HDF5_rt_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_sz_LIBRARY_DEBUG
HDF5_sz_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_sz_LIBRARY_RELEASE
HDF5_sz_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_z_LIBRARY_DEBUG
HDF5_z_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_z_LIBRARY_RELEASE
HDF5_z_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HGCOMMAND
HGCOMMAND-ADVANCED:INTERNAL=1
//Result of TRY_RUN
KWSYS_CHAR_IS_SIGNED:INTERNAL=0
//Result of TRY_COMPILE
KWSYS_CHAR_IS_SIGNED_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_ARGUMENT_DEPENDENT_LOOKUP_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_ATOLL_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_ATOL_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_BACKTRACE_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_CSTDDEF_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_CSTDIO_COMPILED:INTERNAL=TRUE
//Have include cxxabi.h
KWSYS_CXX_HAS_CXXABIH:INTERNAL=1
//Result of TRY_COMPILE
KWSYS_CXX_HAS_CXXABI_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_DLADDR_COMPILED:INTERNAL=TRUE
//Have include dlfcn.h
KWSYS_CXX_HAS_DLFCNH:INTERNAL=1
//Result of TRY_COMPILE
KWSYS_CXX_HAS_ENVIRON_IN_STDLIB_H_COMPILED:INTERNAL=FALSE
//Have include execinfo.h
KWSYS_CXX_HAS_EXECINFOH:INTERNAL=1
//Result of TRY_COMPILE
KWSYS_CXX_HAS_FULL_SPECIALIZATION_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_LONG_LONG_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_MEMBER_TEMPLATES_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_NULL_TEMPLATE_ARGS_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_RLIMIT64_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_SETENV_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_UNSETENV_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_UTIMENSAT_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_UTIMES_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS__ATOI64_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_HAS___INT64_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_C_HAS_PTRDIFF_T_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_C_HAS_SSIZE_T_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_C_TYPE_MACROS_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_IOS_HAVE_BINARY_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_IOS_HAVE_STD_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_IOS_USE_ANSI_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_IOS_USE_SSTREAM_COMPILED:INTERNAL=TRUE
//Result of TRY_RUN
KWSYS_LFS_WORKS:INTERNAL=0
//Result of TRY_COMPILE
KWSYS_LFS_WORKS_COMPILED:INTERNAL=TRUE
//CHECK_TYPE_SIZE: sizeof(char)
KWSYS_SIZEOF_CHAR:INTERNAL=1
//CHECK_TYPE_SIZE: __int64 unknown
KWSYS_SIZEOF___INT64:INTERNAL=
//Result of TRY_COMPILE
KWSYS_STAT_HAS_ST_MTIM_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_HAS_ALLOCATOR_MAX_SIZE_ARGUMENT_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_STL_HAS_ALLOCATOR_OBJECTS_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_HAS_ALLOCATOR_REBIND_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_HAS_ALLOCATOR_TEMPLATE_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_HAS_ITERATOR_TRAITS_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_HAS_WSTRING_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_HAVE_STD_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_STRING_HAVE_NEQ_CHAR_COMPILED:INTERNAL=TRUE
//Have include sys/types.h;ifaddrs.h
KWSYS_SYS_HAS_IFADDRS_H:INTERNAL=1
LIBRARY_OUTPUT_PATH:INTERNAL=/storage/home/guv106/software/ParaView-v4.3.1-build/ThirdParty/protobuf/vtkprotobuf/bin
//ADVANCED property for variable: MAKECOMMAND
MAKECOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MEMORYCHECK_COMMAND
MEMORYCHECK_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MEMORYCHECK_SUPPRESSIONS_FILE
MEMORYCHECK_SUPPRESSIONS_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_AutobahnPython
Module_AutobahnPython-ADVANCED:INTERNAL=1
//Request building AutobahnPython
Module_AutobahnPython:INTERNAL=OFF
//ADVANCED property for variable: Module_Pygments
Module_Pygments-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_SixPython
Module_SixPython-ADVANCED:INTERNAL=1
//Request building SixPython
Module_SixPython:INTERNAL=OFF
//ADVANCED property for variable: Module_Twisted
Module_Twisted-ADVANCED:INTERNAL=1
//Request building Twisted
Module_Twisted:INTERNAL=OFF
//ADVANCED property for variable: Module_VisItLib
Module_VisItLib-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_ZopeInterface
Module_ZopeInterface-ADVANCED:INTERNAL=1
//Request building ZopeInterface
Module_ZopeInterface:INTERNAL=OFF
//ADVANCED property for variable: Module_pqApplicationComponents
Module_pqApplicationComponents-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_pqComponents
Module_pqComponents-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_pqCore
Module_pqCore-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_pqDeprecated
Module_pqDeprecated-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_pqPython
Module_pqPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_pqWidgets
Module_pqWidgets-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_smTestDriver
Module_smTestDriver-ADVANCED:INTERNAL=1
//Request building smTestDriver
Module_smTestDriver:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkAcceleratorsDax
Module_vtkAcceleratorsDax-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkAcceleratorsPiston
Module_vtkAcceleratorsPiston-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkChartsCore
Module_vtkChartsCore-ADVANCED:INTERNAL=1
//Request building vtkChartsCore
Module_vtkChartsCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkClientServer
Module_vtkClientServer-ADVANCED:INTERNAL=1
//Request building vtkClientServer
Module_vtkClientServer:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonColor
Module_vtkCommonColor-ADVANCED:INTERNAL=1
//Request building vtkCommonColor
Module_vtkCommonColor:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonComputationalGeometry
Module_vtkCommonComputationalGeometry-ADVANCED:INTERNAL=1
//Request building vtkCommonComputationalGeometry
Module_vtkCommonComputationalGeometry:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonCore
Module_vtkCommonCore-ADVANCED:INTERNAL=1
//Request building vtkCommonCore
Module_vtkCommonCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonDataModel
Module_vtkCommonDataModel-ADVANCED:INTERNAL=1
//Request building vtkCommonDataModel
Module_vtkCommonDataModel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonExecutionModel
Module_vtkCommonExecutionModel-ADVANCED:INTERNAL=1
//Request building vtkCommonExecutionModel
Module_vtkCommonExecutionModel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonMath
Module_vtkCommonMath-ADVANCED:INTERNAL=1
//Request building vtkCommonMath
Module_vtkCommonMath:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonMisc
Module_vtkCommonMisc-ADVANCED:INTERNAL=1
//Request building vtkCommonMisc
Module_vtkCommonMisc:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonSystem
Module_vtkCommonSystem-ADVANCED:INTERNAL=1
//Request building vtkCommonSystem
Module_vtkCommonSystem:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonTransforms
Module_vtkCommonTransforms-ADVANCED:INTERNAL=1
//Request building vtkCommonTransforms
Module_vtkCommonTransforms:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkDICOMParser
Module_vtkDICOMParser-ADVANCED:INTERNAL=1
//Request building vtkDICOMParser
Module_vtkDICOMParser:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkDomainsChemistry
Module_vtkDomainsChemistry-ADVANCED:INTERNAL=1
//Request building vtkDomainsChemistry
Module_vtkDomainsChemistry:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkDomainsChemistryOpenGL2
Module_vtkDomainsChemistryOpenGL2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersAMR
Module_vtkFiltersAMR-ADVANCED:INTERNAL=1
//Request building vtkFiltersAMR
Module_vtkFiltersAMR:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersCore
Module_vtkFiltersCore-ADVANCED:INTERNAL=1
//Request building vtkFiltersCore
Module_vtkFiltersCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersExtraction
Module_vtkFiltersExtraction-ADVANCED:INTERNAL=1
//Request building vtkFiltersExtraction
Module_vtkFiltersExtraction:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersFlowPaths
Module_vtkFiltersFlowPaths-ADVANCED:INTERNAL=1
//Request building vtkFiltersFlowPaths
Module_vtkFiltersFlowPaths:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersGeneral
Module_vtkFiltersGeneral-ADVANCED:INTERNAL=1
//Request building vtkFiltersGeneral
Module_vtkFiltersGeneral:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersGeneric
Module_vtkFiltersGeneric-ADVANCED:INTERNAL=1
//Request building vtkFiltersGeneric
Module_vtkFiltersGeneric:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersGeometry
Module_vtkFiltersGeometry-ADVANCED:INTERNAL=1
//Request building vtkFiltersGeometry
Module_vtkFiltersGeometry:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersHybrid
Module_vtkFiltersHybrid-ADVANCED:INTERNAL=1
//Request building vtkFiltersHybrid
Module_vtkFiltersHybrid:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersHyperTree
Module_vtkFiltersHyperTree-ADVANCED:INTERNAL=1
//Request building vtkFiltersHyperTree
Module_vtkFiltersHyperTree:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersImaging
Module_vtkFiltersImaging-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersMatlab
Module_vtkFiltersMatlab-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersModeling
Module_vtkFiltersModeling-ADVANCED:INTERNAL=1
//Request building vtkFiltersModeling
Module_vtkFiltersModeling:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersParallel
Module_vtkFiltersParallel-ADVANCED:INTERNAL=1
//Request building vtkFiltersParallel
Module_vtkFiltersParallel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersParallelFlowPaths
Module_vtkFiltersParallelFlowPaths-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersParallelGeometry
Module_vtkFiltersParallelGeometry-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersParallelImaging
Module_vtkFiltersParallelImaging-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersParallelMPI
Module_vtkFiltersParallelMPI-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersParallelStatistics
Module_vtkFiltersParallelStatistics-ADVANCED:INTERNAL=1
//Request building vtkFiltersParallelStatistics
Module_vtkFiltersParallelStatistics:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersProgrammable
Module_vtkFiltersProgrammable-ADVANCED:INTERNAL=1
//Request building vtkFiltersProgrammable
Module_vtkFiltersProgrammable:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersPython
Module_vtkFiltersPython-ADVANCED:INTERNAL=1
//Request building vtkFiltersPython
Module_vtkFiltersPython:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersReebGraph
Module_vtkFiltersReebGraph-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersSMP
Module_vtkFiltersSMP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersSelection
Module_vtkFiltersSelection-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersSources
Module_vtkFiltersSources-ADVANCED:INTERNAL=1
//Request building vtkFiltersSources
Module_vtkFiltersSources:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersStatistics
Module_vtkFiltersStatistics-ADVANCED:INTERNAL=1
//Request building vtkFiltersStatistics
Module_vtkFiltersStatistics:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersStatisticsGnuR
Module_vtkFiltersStatisticsGnuR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersTexture
Module_vtkFiltersTexture-ADVANCED:INTERNAL=1
//Request building vtkFiltersTexture
Module_vtkFiltersTexture:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersVerdict
Module_vtkFiltersVerdict-ADVANCED:INTERNAL=1
//Request building vtkFiltersVerdict
Module_vtkFiltersVerdict:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkGUISupportQt
Module_vtkGUISupportQt-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkGUISupportQtOpenGL
Module_vtkGUISupportQtOpenGL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkGUISupportQtSQL
Module_vtkGUISupportQtSQL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkGUISupportQtWebkit
Module_vtkGUISupportQtWebkit-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkGeovisCore
Module_vtkGeovisCore-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOADIOS
Module_vtkIOADIOS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOAMR
Module_vtkIOAMR-ADVANCED:INTERNAL=1
//Request building vtkIOAMR
Module_vtkIOAMR:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOCore
Module_vtkIOCore-ADVANCED:INTERNAL=1
//Request building vtkIOCore
Module_vtkIOCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOEnSight
Module_vtkIOEnSight-ADVANCED:INTERNAL=1
//Request building vtkIOEnSight
Module_vtkIOEnSight:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOExodus
Module_vtkIOExodus-ADVANCED:INTERNAL=1
//Request building vtkIOExodus
Module_vtkIOExodus:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOExport
Module_vtkIOExport-ADVANCED:INTERNAL=1
//Request building vtkIOExport
Module_vtkIOExport:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOFFMPEG
Module_vtkIOFFMPEG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOGDAL
Module_vtkIOGDAL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOGeoJSON
Module_vtkIOGeoJSON-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOGeometry
Module_vtkIOGeometry-ADVANCED:INTERNAL=1
//Request building vtkIOGeometry
Module_vtkIOGeometry:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOImage
Module_vtkIOImage-ADVANCED:INTERNAL=1
//Request building vtkIOImage
Module_vtkIOImage:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOImport
Module_vtkIOImport-ADVANCED:INTERNAL=1
//Request building vtkIOImport
Module_vtkIOImport:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOInfovis
Module_vtkIOInfovis-ADVANCED:INTERNAL=1
//Request building vtkIOInfovis
Module_vtkIOInfovis:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOLSDyna
Module_vtkIOLSDyna-ADVANCED:INTERNAL=1
//Request building vtkIOLSDyna
Module_vtkIOLSDyna:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOLegacy
Module_vtkIOLegacy-ADVANCED:INTERNAL=1
//Request building vtkIOLegacy
Module_vtkIOLegacy:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOMINC
Module_vtkIOMINC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOMPIImage
Module_vtkIOMPIImage-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOMPIParallel
Module_vtkIOMPIParallel-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOMovie
Module_vtkIOMovie-ADVANCED:INTERNAL=1
//Request building vtkIOMovie
Module_vtkIOMovie:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOMySQL
Module_vtkIOMySQL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIONetCDF
Module_vtkIONetCDF-ADVANCED:INTERNAL=1
//Request building vtkIONetCDF
Module_vtkIONetCDF:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOODBC
Module_vtkIOODBC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOPLY
Module_vtkIOPLY-ADVANCED:INTERNAL=1
//Request building vtkIOPLY
Module_vtkIOPLY:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOParallel
Module_vtkIOParallel-ADVANCED:INTERNAL=1
//Request building vtkIOParallel
Module_vtkIOParallel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOParallelExodus
Module_vtkIOParallelExodus-ADVANCED:INTERNAL=1
//Request building vtkIOParallelExodus
Module_vtkIOParallelExodus:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOParallelLSDyna
Module_vtkIOParallelLSDyna-ADVANCED:INTERNAL=1
//Request building vtkIOParallelLSDyna
Module_vtkIOParallelLSDyna:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOParallelNetCDF
Module_vtkIOParallelNetCDF-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOParallelXML
Module_vtkIOParallelXML-ADVANCED:INTERNAL=1
//Request building vtkIOParallelXML
Module_vtkIOParallelXML:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOPostgreSQL
Module_vtkIOPostgreSQL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOSQL
Module_vtkIOSQL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOVPIC
Module_vtkIOVPIC-ADVANCED:INTERNAL=1
//Request building vtkIOVPIC
Module_vtkIOVPIC:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOVideo
Module_vtkIOVideo-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOVisItBridge
Module_vtkIOVisItBridge-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOXML
Module_vtkIOXML-ADVANCED:INTERNAL=1
//Request building vtkIOXML
Module_vtkIOXML:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOXMLParser
Module_vtkIOXMLParser-ADVANCED:INTERNAL=1
//Request building vtkIOXMLParser
Module_vtkIOXMLParser:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOXdmf2
Module_vtkIOXdmf2-ADVANCED:INTERNAL=1
//Request building vtkIOXdmf2
Module_vtkIOXdmf2:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOXdmf3
Module_vtkIOXdmf3-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkImagingColor
Module_vtkImagingColor-ADVANCED:INTERNAL=1
//Request building vtkImagingColor
Module_vtkImagingColor:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingCore
Module_vtkImagingCore-ADVANCED:INTERNAL=1
//Request building vtkImagingCore
Module_vtkImagingCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingFourier
Module_vtkImagingFourier-ADVANCED:INTERNAL=1
//Request building vtkImagingFourier
Module_vtkImagingFourier:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingGeneral
Module_vtkImagingGeneral-ADVANCED:INTERNAL=1
//Request building vtkImagingGeneral
Module_vtkImagingGeneral:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingHybrid
Module_vtkImagingHybrid-ADVANCED:INTERNAL=1
//Request building vtkImagingHybrid
Module_vtkImagingHybrid:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingMath
Module_vtkImagingMath-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkImagingMorphological
Module_vtkImagingMorphological-ADVANCED:INTERNAL=1
//Request building vtkImagingMorphological
Module_vtkImagingMorphological:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingSources
Module_vtkImagingSources-ADVANCED:INTERNAL=1
//Request building vtkImagingSources
Module_vtkImagingSources:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingStatistics
Module_vtkImagingStatistics-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkImagingStencil
Module_vtkImagingStencil-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkInfovisBoost
Module_vtkInfovisBoost-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkInfovisBoostGraphAlgorithms
Module_vtkInfovisBoostGraphAlgorithms-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkInfovisCore
Module_vtkInfovisCore-ADVANCED:INTERNAL=1
//Request building vtkInfovisCore
Module_vtkInfovisCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkInfovisLayout
Module_vtkInfovisLayout-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkInfovisParallel
Module_vtkInfovisParallel-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkInteractionImage
Module_vtkInteractionImage-ADVANCED:INTERNAL=1
//Request building vtkInteractionImage
Module_vtkInteractionImage:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkInteractionStyle
Module_vtkInteractionStyle-ADVANCED:INTERNAL=1
//Request building vtkInteractionStyle
Module_vtkInteractionStyle:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkInteractionWidgets
Module_vtkInteractionWidgets-ADVANCED:INTERNAL=1
//Request building vtkInteractionWidgets
Module_vtkInteractionWidgets:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkMetaIO
Module_vtkMetaIO-ADVANCED:INTERNAL=1
//Request building vtkMetaIO
Module_vtkMetaIO:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVAnimation
Module_vtkPVAnimation-ADVANCED:INTERNAL=1
//Request building vtkPVAnimation
Module_vtkPVAnimation:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVCatalyst
Module_vtkPVCatalyst-ADVANCED:INTERNAL=1
//Request building vtkPVCatalyst
Module_vtkPVCatalyst:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVCatalystTestDriver
Module_vtkPVCatalystTestDriver-ADVANCED:INTERNAL=1
//Request building vtkPVCatalystTestDriver
Module_vtkPVCatalystTestDriver:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVClientServerCoreCore
Module_vtkPVClientServerCoreCore-ADVANCED:INTERNAL=1
//Request building vtkPVClientServerCoreCore
Module_vtkPVClientServerCoreCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVClientServerCoreDefault
Module_vtkPVClientServerCoreDefault-ADVANCED:INTERNAL=1
//Request building vtkPVClientServerCoreDefault
Module_vtkPVClientServerCoreDefault:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVClientServerCoreRendering
Module_vtkPVClientServerCoreRendering-ADVANCED:INTERNAL=1
//Request building vtkPVClientServerCoreRendering
Module_vtkPVClientServerCoreRendering:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVCommon
Module_vtkPVCommon-ADVANCED:INTERNAL=1
//Request building vtkPVCommon
Module_vtkPVCommon:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerImplementationCore
Module_vtkPVServerImplementationCore-ADVANCED:INTERNAL=1
//Request building vtkPVServerImplementationCore
Module_vtkPVServerImplementationCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerImplementationRendering
Module_vtkPVServerImplementationRendering-ADVANCED:INTERNAL=1
//Request building vtkPVServerImplementationRendering
Module_vtkPVServerImplementationRendering:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerManagerApplication
Module_vtkPVServerManagerApplication-ADVANCED:INTERNAL=1
//Request building vtkPVServerManagerApplication
Module_vtkPVServerManagerApplication:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerManagerCore
Module_vtkPVServerManagerCore-ADVANCED:INTERNAL=1
//Request building vtkPVServerManagerCore
Module_vtkPVServerManagerCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerManagerDefault
Module_vtkPVServerManagerDefault-ADVANCED:INTERNAL=1
//Request building vtkPVServerManagerDefault
Module_vtkPVServerManagerDefault:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerManagerRendering
Module_vtkPVServerManagerRendering-ADVANCED:INTERNAL=1
//Request building vtkPVServerManagerRendering
Module_vtkPVServerManagerRendering:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVVTKExtensionsCore
Module_vtkPVVTKExtensionsCore-ADVANCED:INTERNAL=1
//Request building vtkPVVTKExtensionsCore
Module_vtkPVVTKExtensionsCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVVTKExtensionsCosmoTools
Module_vtkPVVTKExtensionsCosmoTools-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkPVVTKExtensionsDefault
Module_vtkPVVTKExtensionsDefault-ADVANCED:INTERNAL=1
//Request building vtkPVVTKExtensionsDefault
Module_vtkPVVTKExtensionsDefault:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVVTKExtensionsRendering
Module_vtkPVVTKExtensionsRendering-ADVANCED:INTERNAL=1
//Request building vtkPVVTKExtensionsRendering
Module_vtkPVVTKExtensionsRendering:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkParaViewWeb
Module_vtkParaViewWeb-ADVANCED:INTERNAL=1
//Request building vtkParaViewWeb
Module_vtkParaViewWeb:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkParaViewWebApplications
Module_vtkParaViewWebApplications-ADVANCED:INTERNAL=1
//Request building vtkParaViewWebApplications
Module_vtkParaViewWebApplications:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkParaViewWebCore
Module_vtkParaViewWebCore-ADVANCED:INTERNAL=1
//Request building vtkParaViewWebCore
Module_vtkParaViewWebCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkParaViewWebDocumentation
Module_vtkParaViewWebDocumentation-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkParaViewWebPython
Module_vtkParaViewWebPython-ADVANCED:INTERNAL=1
//Request building vtkParaViewWebPython
Module_vtkParaViewWebPython:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkParaViewWebWidgets
Module_vtkParaViewWebWidgets-ADVANCED:INTERNAL=1
//Request building vtkParaViewWebWidgets
Module_vtkParaViewWebWidgets:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkParallelCore
Module_vtkParallelCore-ADVANCED:INTERNAL=1
//Request building vtkParallelCore
Module_vtkParallelCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkParallelMPI
Module_vtkParallelMPI-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkParallelMPI4Py
Module_vtkParallelMPI4Py-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkParseOGLExt
Module_vtkParseOGLExt-ADVANCED:INTERNAL=1
//Request building vtkParseOGLExt
Module_vtkParseOGLExt:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPython
Module_vtkPython-ADVANCED:INTERNAL=1
//Request building vtkPython
Module_vtkPython:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPythonInterpreter
Module_vtkPythonInterpreter-ADVANCED:INTERNAL=1
//Request building vtkPythonInterpreter
Module_vtkPythonInterpreter:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingAnnotation
Module_vtkRenderingAnnotation-ADVANCED:INTERNAL=1
//Request building vtkRenderingAnnotation
Module_vtkRenderingAnnotation:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingContext2D
Module_vtkRenderingContext2D-ADVANCED:INTERNAL=1
//Request building vtkRenderingContext2D
Module_vtkRenderingContext2D:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingContextOpenGL
Module_vtkRenderingContextOpenGL-ADVANCED:INTERNAL=1
//Request building vtkRenderingContextOpenGL
Module_vtkRenderingContextOpenGL:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingContextOpenGL2
Module_vtkRenderingContextOpenGL2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingCore
Module_vtkRenderingCore-ADVANCED:INTERNAL=1
//Request building vtkRenderingCore
Module_vtkRenderingCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingFreeType
Module_vtkRenderingFreeType-ADVANCED:INTERNAL=1
//Request building vtkRenderingFreeType
Module_vtkRenderingFreeType:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingFreeTypeFontConfig
Module_vtkRenderingFreeTypeFontConfig-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingFreeTypeOpenGL
Module_vtkRenderingFreeTypeOpenGL-ADVANCED:INTERNAL=1
//Request building vtkRenderingFreeTypeOpenGL
Module_vtkRenderingFreeTypeOpenGL:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingFreeTypeOpenGL2
Module_vtkRenderingFreeTypeOpenGL2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingGL2PS
Module_vtkRenderingGL2PS-ADVANCED:INTERNAL=1
//Request building vtkRenderingGL2PS
Module_vtkRenderingGL2PS:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingImage
Module_vtkRenderingImage-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingLIC
Module_vtkRenderingLIC-ADVANCED:INTERNAL=1
//Request building vtkRenderingLIC
Module_vtkRenderingLIC:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingLOD
Module_vtkRenderingLOD-ADVANCED:INTERNAL=1
//Request building vtkRenderingLOD
Module_vtkRenderingLOD:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingLabel
Module_vtkRenderingLabel-ADVANCED:INTERNAL=1
//Request building vtkRenderingLabel
Module_vtkRenderingLabel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingMatplotlib
Module_vtkRenderingMatplotlib-ADVANCED:INTERNAL=1
//Request building vtkRenderingMatplotlib
Module_vtkRenderingMatplotlib:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingOpenGL
Module_vtkRenderingOpenGL-ADVANCED:INTERNAL=1
//Request building vtkRenderingOpenGL
Module_vtkRenderingOpenGL:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingOpenGL2
Module_vtkRenderingOpenGL2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingParallel
Module_vtkRenderingParallel-ADVANCED:INTERNAL=1
//Request building vtkRenderingParallel
Module_vtkRenderingParallel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingParallelLIC
Module_vtkRenderingParallelLIC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingQt
Module_vtkRenderingQt-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingTk
Module_vtkRenderingTk-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingVolume
Module_vtkRenderingVolume-ADVANCED:INTERNAL=1
//Request building vtkRenderingVolume
Module_vtkRenderingVolume:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingVolumeAMR
Module_vtkRenderingVolumeAMR-ADVANCED:INTERNAL=1
//Request building vtkRenderingVolumeAMR
Module_vtkRenderingVolumeAMR:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingVolumeOpenGL
Module_vtkRenderingVolumeOpenGL-ADVANCED:INTERNAL=1
//Request building vtkRenderingVolumeOpenGL
Module_vtkRenderingVolumeOpenGL:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingVolumeOpenGL2
Module_vtkRenderingVolumeOpenGL2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingVolumeOpenGLNew
Module_vtkRenderingVolumeOpenGLNew-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkTclTk
Module_vtkTclTk-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkTestingCore
Module_vtkTestingCore-ADVANCED:INTERNAL=1
//Request building vtkTestingCore
Module_vtkTestingCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkTestingGenericBridge
Module_vtkTestingGenericBridge-ADVANCED:INTERNAL=1
//Request building vtkTestingGenericBridge
Module_vtkTestingGenericBridge:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkTestingIOSQL
Module_vtkTestingIOSQL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkTestingRendering
Module_vtkTestingRendering-ADVANCED:INTERNAL=1
//Request building vtkTestingRendering
Module_vtkTestingRendering:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkUtilitiesColorSeriesToXML
Module_vtkUtilitiesColorSeriesToXML-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkUtilitiesEncodeString
Module_vtkUtilitiesEncodeString-ADVANCED:INTERNAL=1
//Request building vtkUtilitiesEncodeString
Module_vtkUtilitiesEncodeString:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkUtilitiesHashSource
Module_vtkUtilitiesHashSource-ADVANCED:INTERNAL=1
//Request building vtkUtilitiesHashSource
Module_vtkUtilitiesHashSource:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkUtilitiesProcessXML
Module_vtkUtilitiesProcessXML-ADVANCED:INTERNAL=1
//Request building vtkUtilitiesProcessXML
Module_vtkUtilitiesProcessXML:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkUtilitiesWrapClientServer
Module_vtkUtilitiesWrapClientServer-ADVANCED:INTERNAL=1
//Request building vtkUtilitiesWrapClientServer
Module_vtkUtilitiesWrapClientServer:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkVPIC
Module_vtkVPIC-ADVANCED:INTERNAL=1
//Request building vtkVPIC
Module_vtkVPIC:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkViewsContext2D
Module_vtkViewsContext2D-ADVANCED:INTERNAL=1
//Request building vtkViewsContext2D
Module_vtkViewsContext2D:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkViewsCore
Module_vtkViewsCore-ADVANCED:INTERNAL=1
//Request building vtkViewsCore
Module_vtkViewsCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkViewsGeovis
Module_vtkViewsGeovis-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkViewsInfovis
Module_vtkViewsInfovis-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkViewsQt
Module_vtkViewsQt-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWebApplications
Module_vtkWebApplications-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWebCore
Module_vtkWebCore-ADVANCED:INTERNAL=1
//Request building vtkWebCore
Module_vtkWebCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkWebGLExporter
Module_vtkWebGLExporter-ADVANCED:INTERNAL=1
//Request building vtkWebGLExporter
Module_vtkWebGLExporter:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkWebInstall
Module_vtkWebInstall-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWebJavaScript
Module_vtkWebJavaScript-ADVANCED:INTERNAL=1
//Request building vtkWebJavaScript
Module_vtkWebJavaScript:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkWebPython
Module_vtkWebPython-ADVANCED:INTERNAL=1
//Request building vtkWebPython
Module_vtkWebPython:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkWrappingJava
Module_vtkWrappingJava-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWrappingPythonCore
Module_vtkWrappingPythonCore-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWrappingTcl
Module_vtkWrappingTcl-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWrappingTools
Module_vtkWrappingTools-ADVANCED:INTERNAL=1
//Request building vtkWrappingTools
Module_vtkWrappingTools:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkalglib
Module_vtkalglib-ADVANCED:INTERNAL=1
//Request building vtkalglib
Module_vtkalglib:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkexodusII
Module_vtkexodusII-ADVANCED:INTERNAL=1
//Request building vtkexodusII
Module_vtkexodusII:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkexpat
Module_vtkexpat-ADVANCED:INTERNAL=1
//Request building vtkexpat
Module_vtkexpat:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkfreetype
Module_vtkfreetype-ADVANCED:INTERNAL=1
//Request building vtkfreetype
Module_vtkfreetype:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkftgl
Module_vtkftgl-ADVANCED:INTERNAL=1
//Request building vtkftgl
Module_vtkftgl:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkgl2ps
Module_vtkgl2ps-ADVANCED:INTERNAL=1
//Request building vtkgl2ps
Module_vtkgl2ps:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkglew
Module_vtkglew-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkhdf5
Module_vtkhdf5-ADVANCED:INTERNAL=1
//Request building vtkhdf5
Module_vtkhdf5:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkicet
Module_vtkicet-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkjpeg
Module_vtkjpeg-ADVANCED:INTERNAL=1
//Request building vtkjpeg
Module_vtkjpeg:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkjsoncpp
Module_vtkjsoncpp-ADVANCED:INTERNAL=1
//Request building vtkjsoncpp
Module_vtkjsoncpp:INTERNAL=OFF
//ADVANCED property for variable: Module_vtklibproj4
Module_vtklibproj4-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtklibxml2
Module_vtklibxml2-ADVANCED:INTERNAL=1
//Request building vtklibxml2
Module_vtklibxml2:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkmpi4py
Module_vtkmpi4py-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtknetcdf
Module_vtknetcdf-ADVANCED:INTERNAL=1
//Request building vtknetcdf
Module_vtknetcdf:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkoggtheora
Module_vtkoggtheora-ADVANCED:INTERNAL=1
//Request building vtkoggtheora
Module_vtkoggtheora:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkpng
Module_vtkpng-ADVANCED:INTERNAL=1
//Request building vtkpng
Module_vtkpng:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkprotobuf
Module_vtkprotobuf-ADVANCED:INTERNAL=1
//Request building vtkprotobuf
Module_vtkprotobuf:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkpugixml
Module_vtkpugixml-ADVANCED:INTERNAL=1
//Request building vtkpugixml
Module_vtkpugixml:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkqttesting
Module_vtkqttesting-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtksqlite
Module_vtksqlite-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtksys
Module_vtksys-ADVANCED:INTERNAL=1
//Request building vtksys
Module_vtksys:INTERNAL=OFF
//ADVANCED property for variable: Module_vtktiff
Module_vtktiff-ADVANCED:INTERNAL=1
//Request building vtktiff
Module_vtktiff:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkverdict
Module_vtkverdict-ADVANCED:INTERNAL=1
//Request building vtkverdict
Module_vtkverdict:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkxdmf2
Module_vtkxdmf2-ADVANCED:INTERNAL=1
//Request building vtkxdmf2
Module_vtkxdmf2:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkxdmf3
Module_vtkxdmf3-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkzlib
Module_vtkzlib-ADVANCED:INTERNAL=1
//Request building vtkzlib
Module_vtkzlib:INTERNAL=OFF
//ADVANCED property for variable: NETCDF_DISABLE_COMPILER_WARNINGS
NETCDF_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: NETCDF_ENABLE_CXX
NETCDF_ENABLE_CXX-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENGL_INCLUDE_DIR
OPENGL_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENGL_gl_LIBRARY
OPENGL_gl_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENGL_glu_LIBRARY
OPENGL_glu_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENGL_xmesa_INCLUDE_DIR
OPENGL_xmesa_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OSMESA_INCLUDE_DIR
OSMESA_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OSMESA_LIBRARY
OSMESA_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: P4COMMAND
P4COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_CATALYST_ADAPTORS
PARAVIEW_BUILD_CATALYST_ADAPTORS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_AdiosReader
PARAVIEW_BUILD_PLUGIN_AdiosReader-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO
PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_ArrowGlyph
PARAVIEW_BUILD_PLUGIN_ArrowGlyph-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_CGNSReader
PARAVIEW_BUILD_PLUGIN_CGNSReader-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_EyeDomeLighting
PARAVIEW_BUILD_PLUGIN_EyeDomeLighting-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_ForceTime
PARAVIEW_BUILD_PLUGIN_ForceTime-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_GMVReader
PARAVIEW_BUILD_PLUGIN_GMVReader-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_H5PartReader
PARAVIEW_BUILD_PLUGIN_H5PartReader-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_InSituExodus
PARAVIEW_BUILD_PLUGIN_InSituExodus-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_MantaView
PARAVIEW_BUILD_PLUGIN_MantaView-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_Moments
PARAVIEW_BUILD_PLUGIN_Moments-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_NonOrthogonalSource
PARAVIEW_BUILD_PLUGIN_NonOrthogonalSource-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_PacMan
PARAVIEW_BUILD_PLUGIN_PacMan-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_PointSprite
PARAVIEW_BUILD_PLUGIN_PointSprite-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_RGBZView
PARAVIEW_BUILD_PLUGIN_RGBZView-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SLACTools
PARAVIEW_BUILD_PLUGIN_SLACTools-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SciberQuestToolKit
PARAVIEW_BUILD_PLUGIN_SciberQuestToolKit-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SierraPlotTools
PARAVIEW_BUILD_PLUGIN_SierraPlotTools-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_StreamingParticles
PARAVIEW_BUILD_PLUGIN_StreamingParticles-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SurfaceLIC
PARAVIEW_BUILD_PLUGIN_SurfaceLIC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_UncertaintyRendering
PARAVIEW_BUILD_PLUGIN_UncertaintyRendering-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_VaporPlugin
PARAVIEW_BUILD_PLUGIN_VaporPlugin-ADVANCED:INTERNAL=1
//MODIFIED property for variable: PARAVIEW_BUILD_QT_GUI
PARAVIEW_BUILD_QT_GUI-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: PARAVIEW_BUILD_WEB_DOCUMENTATION
PARAVIEW_BUILD_WEB_DOCUMENTATION-ADVANCED:INTERNAL=1
//List of modules to CS wrap
PARAVIEW_CURRENT_CS_MODULES:INTERNAL=vtkCommonCore;vtkCommonMath;vtkCommonMisc;vtkCommonSystem;vtkCommonTransforms;vtkCommonDataModel;vtkCommonColor;vtkCommonExecutionModel;vtkFiltersCore;vtkCommonComputationalGeometry;vtkFiltersGeneral;vtkImagingCore;vtkImagingFourier;vtkFiltersStatistics;vtkFiltersExtraction;vtkInfovisCore;vtkFiltersGeometry;vtkFiltersSources;vtkRenderingCore;vtkRenderingFreeType;vtkRenderingContext2D;vtkChartsCore;vtkIOCore;vtkIOLegacy;vtkIOGeometry;vtkIOXMLParser;vtkIOXML;vtkIOInfovis;vtkIOImage;vtkImagingHybrid;vtkRenderingOpenGL;vtkRenderingContextOpenGL;vtkTestingRendering;vtkImagingSources;vtkFiltersHybrid;vtkFiltersModeling;vtkImagingGeneral;vtkInteractionStyle;vtkImagingColor;vtkRenderingAnnotation;vtkRenderingVolume;vtkInteractionWidgets;vtkViewsCore;vtkViewsContext2D;vtkPythonInterpreter;vtkDomainsChemistry;vtkParallelCore;vtkFiltersAMR;vtkIOAMR;vtkFiltersFlowPaths;vtkFiltersGeneric;vtkRenderingFreeTypeOpenGL;vtkRenderingLabel;vtkFiltersHyperTree;vtkFiltersParallel;vtkFiltersParallelStatistics;vtkFiltersProgrammable;vtkFiltersPython;vtkFiltersTexture;vtkFiltersVerdict;vtkIOEnSight;vtkIOExodus;vtkRenderingGL2PS;vtkIOExport;vtkInteractionImage;vtkRenderingVolumeOpenGL;vtkIOImport;vtkIOLSDyna;vtkIOMovie;vtkIONetCDF;vtkIOPLY;vtkIOParallel;vtkIOParallelExodus;vtkIOParallelLSDyna;vtkIOParallelXML;vtkIOVPIC;vtkIOXdmf2;vtkImagingMorphological;vtkPVCommon;vtkPVVTKExtensionsCore;vtkPVClientServerCoreCore;vtkPVServerImplementationCore;vtkPVServerManagerCore;vtkRenderingLIC;vtkRenderingMatplotlib;vtkRenderingParallel;vtkPVVTKExtensionsRendering;vtkPVVTKExtensionsDefault;vtkRenderingVolumeAMR;vtkWebGLExporter;vtkPVClientServerCoreRendering;vtkPVClientServerCoreDefault;vtkPVServerImplementationRendering;vtkPVServerManagerRendering;vtkPVServerManagerDefault;vtkPVAnimation;vtkRenderingLOD;vtkPVServerManagerApplication;vtkPVCatalyst;vtkPVCatalystTestDriver;vtkWebCore;vtkParaViewWebCore
//ADVANCED property for variable: PARAVIEW_DATA_EXCLUDE_FROM_ALL
PARAVIEW_DATA_EXCLUDE_FROM_ALL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_DATA_STORE
PARAVIEW_DATA_STORE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_ENABLE_MATPLOTLIB
PARAVIEW_ENABLE_MATPLOTLIB-ADVANCED:INTERNAL=1
//MODIFIED property for variable: PARAVIEW_ENABLE_PYTHON
PARAVIEW_ENABLE_PYTHON-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: PARAVIEW_ENABLE_SPYPLOT_MARKERS
PARAVIEW_ENABLE_SPYPLOT_MARKERS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED
PARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_ENABLE_WEB
PARAVIEW_ENABLE_WEB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_EXTERNAL_PLUGIN_DIRS
PARAVIEW_EXTERNAL_PLUGIN_DIRS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_FREEZE_PYTHON
PARAVIEW_FREEZE_PYTHON-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_QT_VERSION
PARAVIEW_QT_VERSION-ADVANCED:INTERNAL=1
//STRINGS property for variable: PARAVIEW_QT_VERSION
PARAVIEW_QT_VERSION-STRINGS:INTERNAL=4;5
//Server Manager XMLs
PARAVIEW_SERVERMANAGER_XMLS:INTERNAL=/storage/home/guv106/software/ParaView-v4.3.1-source/ParaViewCore/ServerManager/SMApplication/Resources/3d_widgets.xml;/storage/home/guv106/software/ParaView-v4.3.1-source/ParaViewCore/ServerManager/SMApplication/Resources/filters.xml;/storage/home/guv106/software/ParaView-v4.3.1-source/ParaViewCore/ServerManager/SMApplication/Resources/internal_writers.xml;/storage/home/guv106/software/ParaView-v4.3.1-source/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml;/storage/home/guv106/software/ParaView-v4.3.1-source/ParaViewCore/ServerManager/SMApplication/Resources/rendering.xml;/storage/home/guv106/software/ParaView-v4.3.1-source/ParaViewCore/ServerManager/SMApplication/Resources/sources.xml;/storage/home/guv106/software/ParaView-v4.3.1-source/ParaViewCore/ServerManager/SMApplication/Resources/utilities.xml;/storage/home/guv106/software/ParaView-v4.3.1-source/ParaViewCore/ServerManager/SMApplication/Resources/views_and_representations.xml;/storage/home/guv106/software/ParaView-v4.3.1-source/ParaViewCore/ServerManager/SMApplication/Resources/writers.xml;/storage/home/guv106/software/ParaView-v4.3.1-source/ParaViewCore/ServerManager/Default/settings.xml;/storage/home/guv106/software/ParaView-v4.3.1-source/ParaViewCore/Animation/animation.xml;/storage/home/guv106/software/ParaView-v4.3.1-source/ParaViewCore/ServerManager/SMApplication/Resources/pythonfilter.xml
//ADVANCED property for variable: PROTOBUF_DISABLE_COMPILER_WARNINGS
PROTOBUF_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PV_TEST_CLEAN_COMMAND
PV_TEST_CLEAN_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PV_TEST_CLIENT
PV_TEST_CLIENT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PV_TEST_INIT_COMMAND
PV_TEST_INIT_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PV_TEST_USE_RANDOM_PORTS
PV_TEST_USE_RANDOM_PORTS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_EXECUTABLE
PYTHON_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_EXTRA_LIBS
PYTHON_EXTRA_LIBS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_INCLUDE_DIR
PYTHON_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_LIBRARY
PYTHON_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_UTIL_LIBRARY
PYTHON_UTIL_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_ARTHURPLUGIN_PLUGIN_DEBUG
QT_ARTHURPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_ARTHURPLUGIN_PLUGIN_RELEASE
QT_ARTHURPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
QT_BINARY_DIR:INTERNAL=/usr/lib64/qt4/bin
//ADVANCED property for variable: QT_CONTAINEREXTENSION_PLUGIN_DEBUG
QT_CONTAINEREXTENSION_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_CONTAINEREXTENSION_PLUGIN_RELEASE
QT_CONTAINEREXTENSION_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG
QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE
QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_DBUSCPP2XML_EXECUTABLE
QT_DBUSCPP2XML_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_DBUSXML2CPP_EXECUTABLE
QT_DBUSXML2CPP_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_DESIGNER_EXECUTABLE
QT_DESIGNER_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_DOC_DIR
QT_DOC_DIR-ADVANCED:INTERNAL=1
QT_HEADERS_DIR:INTERNAL=/usr/include
//Qt library dir
QT_LIBRARY_DIR:INTERNAL=/usr/lib64
//ADVANCED property for variable: QT_LINGUIST_EXECUTABLE
QT_LINGUIST_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_LRELEASE_EXECUTABLE
QT_LRELEASE_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_LUPDATE_EXECUTABLE
QT_LUPDATE_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_MKSPECS_DIR
QT_MKSPECS_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_MOC_EXECUTABLE
QT_MOC_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_PHONONWIDGETS_PLUGIN_DEBUG
QT_PHONONWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_PHONONWIDGETS_PLUGIN_RELEASE
QT_PHONONWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_PHONON_INCLUDE_DIR
QT_PHONON_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_PHONON_LIBRARY
QT_PHONON_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_PHONON_LIBRARY_DEBUG
QT_PHONON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_PHONON_LIBRARY_RELEASE
QT_PHONON_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_PLUGINS_DIR
QT_PLUGINS_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QCNCODECS_PLUGIN_DEBUG
QT_QCNCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QCNCODECS_PLUGIN_RELEASE
QT_QCNCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QCOLLECTIONGENERATOR_EXECUTABLE
QT_QCOLLECTIONGENERATOR_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QCOREWLANBEARER_PLUGIN_DEBUG
QT_QCOREWLANBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QCOREWLANBEARER_PLUGIN_RELEASE
QT_QCOREWLANBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QDECLARATIVEVIEW_PLUGIN_DEBUG
QT_QDECLARATIVEVIEW_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QDECLARATIVEVIEW_PLUGIN_RELEASE
QT_QDECLARATIVEVIEW_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QDECORATIONDEFAULT_PLUGIN_DEBUG
QT_QDECORATIONDEFAULT_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QDECORATIONDEFAULT_PLUGIN_RELEASE
QT_QDECORATIONDEFAULT_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QDECORATIONWINDOWS_PLUGIN_DEBUG
QT_QDECORATIONWINDOWS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QDECORATIONWINDOWS_PLUGIN_RELEASE
QT_QDECORATIONWINDOWS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QGENERICBEARER_PLUGIN_DEBUG
QT_QGENERICBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QGENERICBEARER_PLUGIN_RELEASE
QT_QGENERICBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QGIF_PLUGIN_DEBUG
QT_QGIF_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QGIF_PLUGIN_RELEASE
QT_QGIF_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG
QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE
QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QICO_PLUGIN_DEBUG
QT_QICO_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QICO_PLUGIN_RELEASE
QT_QICO_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QIMSW_MULTI_PLUGIN_DEBUG
QT_QIMSW_MULTI_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QIMSW_MULTI_PLUGIN_RELEASE
QT_QIMSW_MULTI_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QJPCODECS_PLUGIN_DEBUG
QT_QJPCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QJPCODECS_PLUGIN_RELEASE
QT_QJPCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QJPEG_PLUGIN_DEBUG
QT_QJPEG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QJPEG_PLUGIN_RELEASE
QT_QJPEG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QKRCODECS_PLUGIN_DEBUG
QT_QKRCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QKRCODECS_PLUGIN_RELEASE
QT_QKRCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
QT_QMAKE_EXECUTABLE_LAST:INTERNAL=/usr/bin/qmake-qt4
//ADVANCED property for variable: QT_QMNG_PLUGIN_DEBUG
QT_QMNG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QMNG_PLUGIN_RELEASE
QT_QMNG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG
QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE
QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLDB2_PLUGIN_DEBUG
QT_QSQLDB2_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLDB2_PLUGIN_RELEASE
QT_QSQLDB2_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLIBASE_PLUGIN_DEBUG
QT_QSQLIBASE_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLIBASE_PLUGIN_RELEASE
QT_QSQLIBASE_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLITE2_PLUGIN_DEBUG
QT_QSQLITE2_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLITE2_PLUGIN_RELEASE
QT_QSQLITE2_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLITE_PLUGIN_DEBUG
QT_QSQLITE_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLITE_PLUGIN_RELEASE
QT_QSQLITE_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLMYSQL_PLUGIN_DEBUG
QT_QSQLMYSQL_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLMYSQL_PLUGIN_RELEASE
QT_QSQLMYSQL_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLOCI_PLUGIN_DEBUG
QT_QSQLOCI_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLOCI_PLUGIN_RELEASE
QT_QSQLOCI_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLODBC_PLUGIN_DEBUG
QT_QSQLODBC_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLODBC_PLUGIN_RELEASE
QT_QSQLODBC_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLPSQL_PLUGIN_DEBUG
QT_QSQLPSQL_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLPSQL_PLUGIN_RELEASE
QT_QSQLPSQL_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLTDS_PLUGIN_DEBUG
QT_QSQLTDS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLTDS_PLUGIN_RELEASE
QT_QSQLTDS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSVGICON_PLUGIN_DEBUG
QT_QSVGICON_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSVGICON_PLUGIN_RELEASE
QT_QSVGICON_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSVG_PLUGIN_DEBUG
QT_QSVG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSVG_PLUGIN_RELEASE
QT_QSVG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG
QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE
QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QT3SUPPORT_INCLUDE_DIR
QT_QT3SUPPORT_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY
QT_QT3SUPPORT_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY_DEBUG
QT_QT3SUPPORT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY_RELEASE
QT_QT3SUPPORT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG
QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE
QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG
QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE
QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTASSISTANTCLIENT_INCLUDE_DIR
QT_QTASSISTANTCLIENT_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY
QT_QTASSISTANTCLIENT_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY_DEBUG
QT_QTASSISTANTCLIENT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY_RELEASE
QT_QTASSISTANTCLIENT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTASSISTANT_INCLUDE_DIR
QT_QTASSISTANT_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTASSISTANT_LIBRARY
QT_QTASSISTANT_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTASSISTANT_LIBRARY_DEBUG
QT_QTASSISTANT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTASSISTANT_LIBRARY_RELEASE
QT_QTASSISTANT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTCLUCENE_LIBRARY
QT_QTCLUCENE_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTCLUCENE_LIBRARY_DEBUG
QT_QTCLUCENE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTCLUCENE_LIBRARY_RELEASE
QT_QTCLUCENE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTCORE_INCLUDE_DIR
QT_QTCORE_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTCORE_LIBRARY
QT_QTCORE_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTCORE_LIBRARY_DEBUG
QT_QTCORE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTCORE_LIBRARY_RELEASE
QT_QTCORE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDBUS_INCLUDE_DIR
QT_QTDBUS_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDBUS_LIBRARY
QT_QTDBUS_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDBUS_LIBRARY_DEBUG
QT_QTDBUS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDBUS_LIBRARY_RELEASE
QT_QTDBUS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDECLARATIVE_INCLUDE_DIR
QT_QTDECLARATIVE_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY
QT_QTDECLARATIVE_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY_DEBUG
QT_QTDECLARATIVE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY_RELEASE
QT_QTDECLARATIVE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR
QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY
QT_QTDESIGNERCOMPONENTS_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG
QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE
QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDESIGNER_INCLUDE_DIR
QT_QTDESIGNER_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDESIGNER_LIBRARY
QT_QTDESIGNER_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDESIGNER_LIBRARY_DEBUG
QT_QTDESIGNER_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDESIGNER_LIBRARY_RELEASE
QT_QTDESIGNER_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTGA_PLUGIN_DEBUG
QT_QTGA_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTGA_PLUGIN_RELEASE
QT_QTGA_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTGUI_INCLUDE_DIR
QT_QTGUI_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTGUI_LIBRARY
QT_QTGUI_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTGUI_LIBRARY_DEBUG
QT_QTGUI_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTGUI_LIBRARY_RELEASE
QT_QTGUI_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTHELP_INCLUDE_DIR
QT_QTHELP_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTHELP_LIBRARY
QT_QTHELP_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTHELP_LIBRARY_DEBUG
QT_QTHELP_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTHELP_LIBRARY_RELEASE
QT_QTHELP_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTIFF_PLUGIN_DEBUG
QT_QTIFF_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTIFF_PLUGIN_RELEASE
QT_QTIFF_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTMOTIF_INCLUDE_DIR
QT_QTMOTIF_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTMOTIF_LIBRARY
QT_QTMOTIF_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTMOTIF_LIBRARY_DEBUG
QT_QTMOTIF_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTMOTIF_LIBRARY_RELEASE
QT_QTMOTIF_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTMULTIMEDIA_INCLUDE_DIR
QT_QTMULTIMEDIA_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY
QT_QTMULTIMEDIA_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY_DEBUG
QT_QTMULTIMEDIA_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY_RELEASE
QT_QTMULTIMEDIA_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTNETWORK_INCLUDE_DIR
QT_QTNETWORK_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTNETWORK_LIBRARY
QT_QTNETWORK_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTNETWORK_LIBRARY_DEBUG
QT_QTNETWORK_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTNETWORK_LIBRARY_RELEASE
QT_QTNETWORK_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTNSPLUGIN_INCLUDE_DIR
QT_QTNSPLUGIN_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY
QT_QTNSPLUGIN_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY_DEBUG
QT_QTNSPLUGIN_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY_RELEASE
QT_QTNSPLUGIN_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTOPENGL_INCLUDE_DIR
QT_QTOPENGL_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTOPENGL_LIBRARY
QT_QTOPENGL_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTOPENGL_LIBRARY_DEBUG
QT_QTOPENGL_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTOPENGL_LIBRARY_RELEASE
QT_QTOPENGL_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG
QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE
QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPTDBUS_PLUGIN_DEBUG
QT_QTSCRIPTDBUS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPTDBUS_PLUGIN_RELEASE
QT_QTSCRIPTDBUS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPTTOOLS_INCLUDE_DIR
QT_QTSCRIPTTOOLS_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY
QT_QTSCRIPTTOOLS_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY_DEBUG
QT_QTSCRIPTTOOLS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY_RELEASE
QT_QTSCRIPTTOOLS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPT_INCLUDE_DIR
QT_QTSCRIPT_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPT_LIBRARY
QT_QTSCRIPT_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPT_LIBRARY_DEBUG
QT_QTSCRIPT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPT_LIBRARY_RELEASE
QT_QTSCRIPT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSQL_INCLUDE_DIR
QT_QTSQL_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSQL_LIBRARY
QT_QTSQL_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSQL_LIBRARY_DEBUG
QT_QTSQL_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSQL_LIBRARY_RELEASE
QT_QTSQL_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSVG_INCLUDE_DIR
QT_QTSVG_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSVG_LIBRARY
QT_QTSVG_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSVG_LIBRARY_DEBUG
QT_QTSVG_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSVG_LIBRARY_RELEASE
QT_QTSVG_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTTEST_INCLUDE_DIR
QT_QTTEST_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTTEST_LIBRARY
QT_QTTEST_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTTEST_LIBRARY_DEBUG
QT_QTTEST_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTTEST_LIBRARY_RELEASE
QT_QTTEST_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTUITOOLS_INCLUDE_DIR
QT_QTUITOOLS_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTUITOOLS_LIBRARY
QT_QTUITOOLS_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTUITOOLS_LIBRARY_DEBUG
QT_QTUITOOLS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTUITOOLS_LIBRARY_RELEASE
QT_QTUITOOLS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTWCODECS_PLUGIN_DEBUG
QT_QTWCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTWCODECS_PLUGIN_RELEASE
QT_QTWCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTWEBKIT_INCLUDE_DIR
QT_QTWEBKIT_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTWEBKIT_LIBRARY
QT_QTWEBKIT_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTWEBKIT_LIBRARY_DEBUG
QT_QTWEBKIT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTWEBKIT_LIBRARY_RELEASE
QT_QTWEBKIT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTXMLPATTERNS_INCLUDE_DIR
QT_QTXMLPATTERNS_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY
QT_QTXMLPATTERNS_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY_DEBUG
QT_QTXMLPATTERNS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY_RELEASE
QT_QTXMLPATTERNS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTXML_INCLUDE_DIR
QT_QTXML_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTXML_LIBRARY
QT_QTXML_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTXML_LIBRARY_DEBUG
QT_QTXML_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTXML_LIBRARY_RELEASE
QT_QTXML_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QWEBVIEW_PLUGIN_DEBUG
QT_QWEBVIEW_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QWEBVIEW_PLUGIN_RELEASE
QT_QWEBVIEW_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG
QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE
QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_RCC_EXECUTABLE
QT_RCC_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_TASKMENUEXTENSION_PLUGIN_DEBUG
QT_TASKMENUEXTENSION_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_TASKMENUEXTENSION_PLUGIN_RELEASE
QT_TASKMENUEXTENSION_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_TRANSLATIONS_DIR
QT_TRANSLATIONS_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_UIC3_EXECUTABLE
QT_UIC3_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_UIC_EXECUTABLE
QT_UIC_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG
QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE
QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//Have symbol Q_WS_MAC
Q_WS_MAC:INTERNAL=
//Have symbol Q_WS_QWS
Q_WS_QWS:INTERNAL=
//Have symbol Q_WS_WIN
Q_WS_WIN:INTERNAL=
//Have symbol Q_WS_X11
Q_WS_X11:INTERNAL=1
//ADVANCED property for variable: SCPCOMMAND
SCPCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: SITE
SITE-ADVANCED:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(double)
SIZEOF_DOUBLE:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(float)
SIZEOF_FLOAT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int)
SIZEOF_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long)
SIZEOF_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(long long)
SIZEOF_LONG_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(off_t)
SIZEOF_OFF_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(ptrdiff_t)
SIZEOF_PTRDIFF_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(short)
SIZEOF_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(size_t)
SIZEOF_SIZE_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(ssize_t)
SIZEOF_SSIZE_T:INTERNAL=8
//CHECK_TYPE_SIZE: uchar unknown
SIZEOF_UCHAR:INTERNAL=
//CHECK_TYPE_SIZE: sizeof(_Bool)
SIZEOF__BOOL:INTERNAL=1
//ADVANCED property for variable: SLURM_SBATCH_COMMAND
SLURM_SBATCH_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: SLURM_SRUN_COMMAND
SLURM_SRUN_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: SQTK_CUDA
SQTK_CUDA-ADVANCED:INTERNAL=1
//ADVANCED property for variable: SQTK_DEBUG
SQTK_DEBUG-ADVANCED:INTERNAL=1
//Have include stdlib.h;stdarg.h;string.h;float.h
STDC_HEADERS:INTERNAL=1
//Result of TRY_COMPILE
SUCCEED:INTERNAL=TRUE
//Result of TRY_COMPILE
SUCCEED_MAP:INTERNAL=TRUE
//Result of TRY_COMPILE
SUCCEED_SET:INTERNAL=TRUE
//Result of TRY_COMPILE
SUPPORT_IP6_COMPILED:INTERNAL=TRUE
//ADVANCED property for variable: SVNCOMMAND
SVNCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: USE_COMPILER_HIDDEN_VISIBILITY
USE_COMPILER_HIDDEN_VISIBILITY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VERDICT_BUILD_DOC
VERDICT_BUILD_DOC-ADVANCED:INTERNAL=1
//Build the 2007 Verdict User Manual
VERDICT_BUILD_DOC:INTERNAL=OFF
//ADVANCED property for variable: VERDICT_ENABLE_TESTING
VERDICT_ENABLE_TESTING-ADVANCED:INTERNAL=1
//Should tests of the VERDICT library be built?
VERDICT_ENABLE_TESTING:INTERNAL=OFF
//ADVANCED property for variable: VERDICT_MANGLE
VERDICT_MANGLE-ADVANCED:INTERNAL=1
//Mangle verdict names for inclusion in a larger library?
VERDICT_MANGLE:INTERNAL=OFF
//A string to prepend to all verdict function names and classes.
VERDICT_MANGLE_PREFIX:INTERNAL=
//ADVANCED property for variable: VTKOGGTHEORA_DISABLE_ASM
VTKOGGTHEORA_DISABLE_ASM-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTKOGGTHEORA_DISABLE_FLOAT
VTKOGGTHEORA_DISABLE_FLOAT-ADVANCED:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(int)
VTKOGGTHEORA_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int16_t)
VTKOGGTHEORA_INT16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(int32_t)
VTKOGGTHEORA_INT32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int64_t)
VTKOGGTHEORA_INT64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(long)
VTKOGGTHEORA_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(long long)
VTKOGGTHEORA_LONG_LONG:INTERNAL=8
//ADVANCED property for variable: VTKOGGTHEORA_SHARED_LINKER_FLAGS
VTKOGGTHEORA_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(short)
VTKOGGTHEORA_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(uint16_t)
VTKOGGTHEORA_UINT16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(uint32_t)
VTKOGGTHEORA_UINT32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(u_int16_t)
VTKOGGTHEORA_U_INT16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(u_int32_t)
VTKOGGTHEORA_U_INT32_T:INTERNAL=4
//ADVANCED property for variable: VTK_ALL_NEW_OBJECT_FACTORY
VTK_ALL_NEW_OBJECT_FACTORY-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
VTK_ANSI_STREAM_EOF_COMPILED:INTERNAL=TRUE
//Result of TRY_RUN
VTK_ANSI_STREAM_EOF_RESULT:INTERNAL=1
//ADVANCED property for variable: VTK_BUILD_ALL_MODULES
VTK_BUILD_ALL_MODULES-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_BUILD_ALL_MODULES_FOR_TESTS
VTK_BUILD_ALL_MODULES_FOR_TESTS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_BUILD_FREETYPE_BENCHMARK
VTK_BUILD_FREETYPE_BENCHMARK-ADVANCED:INTERNAL=1
//Directory where python modules will be built
VTK_BUILD_PYTHON_MODULE_DIR:INTERNAL=/storage/home/guv106/software/ParaView-v4.3.1-build/lib/site-packages
//Support for full template specialization syntax
VTK_COMPILER_HAS_FULL_SPECIALIZATION:INTERNAL=1
//Test VTK_CONST_REVERSE_ITERATOR_COMPARISON
VTK_CONST_REVERSE_ITERATOR_COMPARISON:INTERNAL=1
//ADVANCED property for variable: VTK_DATA_STORE
VTK_DATA_STORE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_DEBUG_LEAKS
VTK_DEBUG_LEAKS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_ENABLE_KITS
VTK_ENABLE_KITS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_ENABLE_VTKPYTHON
VTK_ENABLE_VTKPYTHON-ADVANCED:INTERNAL=1
//Support for C++ explict templates
VTK_EXPLICIT_TEMPLATES:INTERNAL=1
//ADVANCED property for variable: VTK_EXTRA_COMPILER_WARNINGS
VTK_EXTRA_COMPILER_WARNINGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_GHOSTSCRIPT_EXECUTABLE
VTK_GHOSTSCRIPT_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_GLEXT_FILE
VTK_GLEXT_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_GLXEXT_FILE
VTK_GLXEXT_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Imaging
VTK_Group_Imaging-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_MPI
VTK_Group_MPI-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_ParaViewCore
VTK_Group_ParaViewCore-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_ParaViewQt
VTK_Group_ParaViewQt-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_ParaViewRendering
VTK_Group_ParaViewRendering-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Qt
VTK_Group_Qt-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Rendering
VTK_Group_Rendering-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_StandAlone
VTK_Group_StandAlone-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Tk
VTK_Group_Tk-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Views
VTK_Group_Views-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Web
VTK_Group_Web-ADVANCED:INTERNAL=1
//Have symbol feenableexcept
VTK_HAS_FEENABLEEXCEPT:INTERNAL=1
//Have symbol finite
VTK_HAS_FINITE:INTERNAL=1
//Have symbol isfinite
VTK_HAS_ISFINITE:INTERNAL=1
//Have symbol isinf
VTK_HAS_ISINF:INTERNAL=1
//Have symbol isnan
VTK_HAS_ISNAN:INTERNAL=1
//Test VTK_HAS_STD_ISFINITE
VTK_HAS_STD_ISFINITE:INTERNAL=1
//Test VTK_HAS_STD_ISINF
VTK_HAS_STD_ISINF:INTERNAL=1
//Test VTK_HAS_STD_ISNAN
VTK_HAS_STD_ISNAN:INTERNAL=1
//Support for getsockname with socklen_t
VTK_HAVE_GETSOCKNAME_WITH_SOCKLEN_T:INTERNAL=1
//Have library socket
VTK_HAVE_LIBSOCKET:INTERNAL=
//Have symbol SO_REUSEADDR
VTK_HAVE_SO_REUSEADDR:INTERNAL=1
//For __sync atomic builtins.
VTK_HAVE_SYNC_BUILTINS:INTERNAL=1
//VTK modular always ignores BTX
VTK_IGNORE_BTX:INTERNAL=ON
//ADVANCED property for variable: VTK_IGNORE_GLDRIVER_BUGS
VTK_IGNORE_GLDRIVER_BUGS-ADVANCED:INTERNAL=1
//Directory where python modules will be installed
VTK_INSTALL_PYTHON_MODULE_DIR:INTERNAL=lib/paraview-4.3/site-packages
//Whether istream supports long long
VTK_ISTREAM_SUPPORTS_LONG_LONG:INTERNAL=1
//ADVANCED property for variable: VTK_LEGACY_REMOVE
VTK_LEGACY_REMOVE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_LEGACY_SILENT
VTK_LEGACY_SILENT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MAKE_INSTANTIATORS
VTK_MAKE_INSTANTIATORS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MAX_THREADS
VTK_MAX_THREADS-ADVANCED:INTERNAL=1
//Disable Python Threads support
VTK_NO_PYTHON_THREADS:INTERNAL=1
//ADVANCED property for variable: VTK_OPENGL_HAS_OSMESA
VTK_OPENGL_HAS_OSMESA-ADVANCED:INTERNAL=1
//Whether ostream supports long long
VTK_OSTREAM_SUPPORTS_LONG_LONG:INTERNAL=1
//ADVANCED property for variable: VTK_QT_VERSION
VTK_QT_VERSION-ADVANCED:INTERNAL=1
//STRINGS property for variable: VTK_QT_VERSION
VTK_QT_VERSION-STRINGS:INTERNAL=4;5
//STRINGS property for variable: VTK_RENDERING_BACKEND
VTK_RENDERING_BACKEND-STRINGS:INTERNAL=OpenGL;OpenGL2;None
//ADVANCED property for variable: VTK_REPORT_OPENGL_ERRORS
VTK_REPORT_OPENGL_ERRORS-ADVANCED:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(char)
VTK_SIZEOF_CHAR:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(double)
VTK_SIZEOF_DOUBLE:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(float)
VTK_SIZEOF_FLOAT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int)
VTK_SIZEOF_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long)
VTK_SIZEOF_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(long long)
VTK_SIZEOF_LONG_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(short)
VTK_SIZEOF_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: __int64 unknown
VTK_SIZEOF___INT64:INTERNAL=
//STRINGS property for variable: VTK_SMP_IMPLEMENTATION_TYPE
VTK_SMP_IMPLEMENTATION_TYPE-STRINGS:INTERNAL=Sequential;Simple;Kaapi;TBB
//Result of TRY_COMPILE
VTK_TEST_SYNC_BUILTINS_COMPILED:INTERNAL=TRUE
//Whether char is signed.
VTK_TYPE_CHAR_IS_SIGNED:INTERNAL=1
//Result of TRY_COMPILE
VTK_TYPE_CHAR_IS_SIGNED_COMPILED:INTERNAL=TRUE
//CHECK_TYPE_SIZE: sizeof(uintptr_t)
VTK_UINTPTR_T:INTERNAL=8
//ADVANCED property for variable: VTK_USE_64BIT_IDS
VTK_USE_64BIT_IDS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_GCC_VISIBILITY
VTK_USE_GCC_VISIBILITY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_OFFSCREEN
VTK_USE_OFFSCREEN-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_AUTOBAHN
VTK_USE_SYSTEM_AUTOBAHN-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_EXPAT
VTK_USE_SYSTEM_EXPAT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_FREETYPE
VTK_USE_SYSTEM_FREETYPE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_GL2PS
VTK_USE_SYSTEM_GL2PS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_HDF5
VTK_USE_SYSTEM_HDF5-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_JPEG
VTK_USE_SYSTEM_JPEG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_JSONCPP
VTK_USE_SYSTEM_JSONCPP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_LIBRARIES
VTK_USE_SYSTEM_LIBRARIES-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_LIBXML2
VTK_USE_SYSTEM_LIBXML2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_NETCDF
VTK_USE_SYSTEM_NETCDF-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_OGGTHEORA
VTK_USE_SYSTEM_OGGTHEORA-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_PNG
VTK_USE_SYSTEM_PNG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_PROTOBUF
VTK_USE_SYSTEM_PROTOBUF-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_PUGIXML
VTK_USE_SYSTEM_PUGIXML-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_PYGMENTS
VTK_USE_SYSTEM_PYGMENTS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_SIX
VTK_USE_SYSTEM_SIX-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_TIFF
VTK_USE_SYSTEM_TIFF-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_TWISTED
VTK_USE_SYSTEM_TWISTED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_XDMF2
VTK_USE_SYSTEM_XDMF2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_ZLIB
VTK_USE_SYSTEM_ZLIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_ZOPE
VTK_USE_SYSTEM_ZOPE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_TDX
VTK_USE_TDX-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_TK
VTK_USE_TK-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_X
VTK_USE_X-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_VPIC_USE_MPI
VTK_VPIC_USE_MPI-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_WGLEXT_FILE
VTK_WGLEXT_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_WRAP_HINTS
VTK_WRAP_HINTS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_WRAP_JAVA
VTK_WRAP_JAVA-ADVANCED:INTERNAL=1
//Should VTK Python wrapping be built?
VTK_WRAP_PYTHON:INTERNAL=ON
//ADVANCED property for variable: VTK_WRAP_TCL
VTK_WRAP_TCL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_XDMF_USE_MPI
VTK_XDMF_USE_MPI-ADVANCED:INTERNAL=1
//Test Wno-unused-result
Wno-unused-result:INTERNAL=1
//ADVANCED property for variable: X11_ICE_INCLUDE_PATH
X11_ICE_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_ICE_LIB
X11_ICE_LIB-ADVANCED:INTERNAL=1
//Have library /usr/lib64/libX11.so;/usr/lib64/libXext.so
X11_LIB_X11_SOLO:INTERNAL=1
//ADVANCED property for variable: X11_SM_INCLUDE_PATH
X11_SM_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_SM_LIB
X11_SM_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_X11_INCLUDE_PATH
X11_X11_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_X11_LIB
X11_X11_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_XRes_INCLUDE_PATH
X11_XRes_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_XRes_LIB
X11_XRes_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_XShm_INCLUDE_PATH
X11_XShm_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_XSync_INCLUDE_PATH
X11_XSync_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_XTest_INCLUDE_PATH
X11_XTest_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_XTest_LIB
X11_XTest_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xaccessrules_INCLUDE_PATH
X11_Xaccessrules_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xaccessstr_INCLUDE_PATH
X11_Xaccessstr_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xau_INCLUDE_PATH
X11_Xau_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xau_LIB
X11_Xau_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xcomposite_INCLUDE_PATH
X11_Xcomposite_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xcomposite_LIB
X11_Xcomposite_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xcursor_INCLUDE_PATH
X11_Xcursor_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xcursor_LIB
X11_Xcursor_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xdamage_INCLUDE_PATH
X11_Xdamage_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xdamage_LIB
X11_Xdamage_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xdmcp_INCLUDE_PATH
X11_Xdmcp_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xdmcp_LIB
X11_Xdmcp_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xext_LIB
X11_Xext_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xfixes_INCLUDE_PATH
X11_Xfixes_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xfixes_LIB
X11_Xfixes_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xft_INCLUDE_PATH
X11_Xft_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xft_LIB
X11_Xft_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xi_INCLUDE_PATH
X11_Xi_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xi_LIB
X11_Xi_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xinerama_INCLUDE_PATH
X11_Xinerama_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xinerama_LIB
X11_Xinerama_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xinput_INCLUDE_PATH
X11_Xinput_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xinput_LIB
X11_Xinput_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xkb_INCLUDE_PATH
X11_Xkb_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xkbfile_INCLUDE_PATH
X11_Xkbfile_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xkbfile_LIB
X11_Xkbfile_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xkblib_INCLUDE_PATH
X11_Xkblib_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xlib_INCLUDE_PATH
X11_Xlib_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xmu_INCLUDE_PATH
X11_Xmu_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xmu_LIB
X11_Xmu_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xpm_INCLUDE_PATH
X11_Xpm_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xpm_LIB
X11_Xpm_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xrandr_INCLUDE_PATH
X11_Xrandr_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xrandr_LIB
X11_Xrandr_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xrender_INCLUDE_PATH
X11_Xrender_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xrender_LIB
X11_Xrender_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xscreensaver_INCLUDE_PATH
X11_Xscreensaver_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xscreensaver_LIB
X11_Xscreensaver_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xshape_INCLUDE_PATH
X11_Xshape_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xt_INCLUDE_PATH
X11_Xt_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xt_LIB
X11_Xt_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xutil_INCLUDE_PATH
X11_Xutil_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xv_INCLUDE_PATH
X11_Xv_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xv_LIB
X11_Xv_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xxf86misc_LIB
X11_Xxf86misc_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xxf86vm_LIB
X11_Xxf86vm_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_dpms_INCLUDE_PATH
X11_dpms_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_xf86misc_INCLUDE_PATH
X11_xf86misc_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_xf86vmode_INCLUDE_PATH
X11_xf86vmode_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_BUILD_MPI
XDMF_BUILD_MPI-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_HAS_NDGM
XDMF_HAS_NDGM-ADVANCED:INTERNAL=1
//Whether streams support 64-bit types
XDMF_HAVE_64BIT_STREAMS:INTERNAL=1
//ADVANCED property for variable: XDMF_HAVE_FCNTL
XDMF_HAVE_FCNTL-ADVANCED:INTERNAL=1
//Have include malloc.h
XDMF_HAVE_MALLOC_H:INTERNAL=1
//ADVANCED property for variable: XDMF_HAVE_MMAN
XDMF_HAVE_MMAN-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_HAVE_NETINET
XDMF_HAVE_NETINET-ADVANCED:INTERNAL=1
XDMF_REGENERATE_WRAPPERS:INTERNAL=OFF
XDMF_REGENERATE_YACCLEX:INTERNAL=OFF
//ADVANCED property for variable: XDMF_USE_MYSQL
XDMF_USE_MYSQL-ADVANCED:INTERNAL=1
XDMF_WRAP_CSHARP:INTERNAL=OFF
XDMF_WRAP_PYTHON:INTERNAL=OFF
XDMF_WRAP_TCL:INTERNAL=OFF
//ADVANCED property for variable: ZLIB_INCLUDE_DIR
ZLIB_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ZLIB_LIBRARY
ZLIB_LIBRARY-ADVANCED:INTERNAL=1
//ParaView has been configured
__paraview_configured:INTERNAL=TRUE
protobut_determine_hash_namespace_done:INTERNAL=TRUE
protobut_pthread_test_done:INTERNAL=TRUE
pthread_test_result:INTERNAL=PTHREAD_CREATE_JOINABLE
//ADVANCED property for variable: smooth_flash
smooth_flash-ADVANCED:INTERNAL=1


From andy.bauer at kitware.com  Wed Jul 29 00:48:17 2015
From: andy.bauer at kitware.com (Andy Bauer)
Date: Wed, 29 Jul 2015 00:48:17 -0400
Subject: [Paraview] How to assign separate parallel pvserver processes
 to separate independent datasets?
In-Reply-To: <CAPHwKk48ggjkoDaJ+1Tfaez7ASgz3cFXKgosWMzYUx+ZEXzy6Q@mail.gmail.com>
References: <CAPHwKk48ggjkoDaJ+1Tfaez7ASgz3cFXKgosWMzYUx+ZEXzy6Q@mail.gmail.com>
Message-ID: <CAMaOp+GLqzc=vheCrKHGbmTNTz2gPkSH4hh=FwPEtkuAHQKTHg@mail.gmail.com>

The closest thing I can think of is doing this in batch. Information on
that is available at
http://www.paraview.org/Wiki/Spatio-Temporal_Parallelism. It's probably
doable in ParaView but would likely take significant amount of
modification.

On Mon, Jul 27, 2015 at 5:26 PM, Krishna Pai <krishnapai09 at gmail.com> wrote:

> Hi all,
>
> I know that, normally, ParaView works with one large dataset and
> partitions it based on the number of processes, then renders and merges the
> results, which I can then view on my ParaView GUI locally. What I want to
> do is take a bunch of independent datasets and make each parallel process
> render them without partitioning them further. In other words, I want a
> one-to-one correspondence between a parallel process and a dataset with the
> ability to view them separately locally (which I can do by filtering by
> Process ID). So far, I've tried opening a couple of datasets separately and
> simultaneously (using ctrl to select them both), and combined them with
> AppendDatasets to see if they would separate out in the way I want. That
> didn't work. In both instances, ParaView partitioned each dataset and
> rendered a part of them in each process. I would appreciate any tips.
>
> Thanks,
> Krishna Pai
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150729/964fa2e5/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Jul 29 12:00:03 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 29 Jul 2015 12:00:03 -0400
Subject: [Paraview] Reg. paraview using off
In-Reply-To: <CAFtK+eubFC-2qodP-4sA66uvknW5d5tbSA7PApWmXypG-joseg@mail.gmail.com>
References: <CAFtK+eubFC-2qodP-4sA66uvknW5d5tbSA7PApWmXypG-joseg@mail.gmail.com>
Message-ID: <CADHSJjB-cAmvTGoFfjR49y0c0WfbCQsw4YTW2Tiehg5reqyg2g@mail.gmail.com>

Check this out:
http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D#Configuring_ParaView_for_use_with_OSMesa

You're missing several other flags needed for ParaView to use OSMesa
e.g. VTK_OPENGL_HAS_OSMESA. Also, your CMakeCache.txt shows that
OPENGL_gl_LIBRARY, OPENGL_glu_LIBRARY, OPENGL_INCLUDE_DIR are set to
use system OpenGL. That will cause runtime issues. The Wiki indicates
the values that these should be set to.

On Tue, Jul 28, 2015 at 11:39 PM, Ganesh Vijayakumar
<ganesh.iitm at gmail.com> wrote:
> Hello,
>
>   I'm trying to install paraview using off-screen rendering on a cluster. I
> attached my CMakeCache. It configures just fine. However, I'm unable to
> progress beyond this error during the compile. Could anyone please help?
> I load the required modules first
>
> module load gcc/4.9.2
> module load cmake/3.1.0
> module load python/2.7.9
> module load hdf5/1.8.14
> export HDF5_ROOT=/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/
> export PYTHON_INCLUDE_DIRS=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/include/
> export
> PYTHON_LIBRARY=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/lib/libpython2.7.so
> export PYTHON_EXECUTABLE=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/bin/python
>
> Then, I configured as
>
> ccmake ~/software/ParaView-v4.3.1-source
> -DOSMESA_INCLUDE_DIR:PATH=/storage/home/guv106/software/mesa-10.5.4/include
> -DOSMESA_LIBRARY:FILEPATH=/storage/home/guv106/software/mesa-10.5.4/lib/gallium/libOSMesa.so
> -DVTK_USE_X:BOOL=OFF  -DVTK_USE_SYSTEM_HDF5:BOOL=ON
> -DPYTHON_INCLUDE_DIRS=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/include/python2.7/
>
> The error during the make process is
>
> [ 11%] Building CXX object
> VTK/Rendering/OpenGL/CMakeFiles/vtkRenderingOpenGL.dir/vtkOSOpenGLRenderWindow.cxx.o
> cd /storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Rendering/OpenGL
> && /usr/bin/c++   -DVTK_IN_VTK -DvtkRenderingO
> penGL_EXPORTS -O3 -DNDEBUG -fPIC
> -I/storage/home/guv106/software/ParaView-v4.3.1-build
> -I/storage/home/guv106/software/mes
> a-10.5.4/include
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Imaging/Hybrid
> -I/storage/home/guv106/software/
> ParaView-v4.3.1-source/VTK/Imaging/Hybrid
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/IO/Image
> -I/storage/ho
> me/guv106/software/ParaView-v4.3.1-source/VTK/IO/Image
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/Da
> taModel
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/DataModel
> -I/storage/home/guv106/software/ParaVi
> ew-v4.3.1-build/VTK/Common/Math
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/Math
> -I/storage/home/guv
> 106/software/ParaView-v4.3.1-build/VTK/Common/Core
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/Core
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/KWSys
> -I/storage/home/guv106/software/ParaView-v4.3.1-
> source/VTK/Utilities/KWSys
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/Misc
> -I/storage/home/guv106/so
> ftware/ParaView-v4.3.1-source/VTK/Common/Misc
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/System -I/s
> torage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/System
> -I/storage/home/guv106/software/ParaView-v4.3.1-build
> /VTK/Common/Transforms
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/Transforms
> -I/storage/home/guv106
> /software/ParaView-v4.3.1-build/VTK/Common/ExecutionModel
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Commo
> n/ExecutionModel
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/DICOMParser
> -I/storage/home/guv106/so
> ftware/ParaView-v4.3.1-source/VTK/Utilities/DICOMParser
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/IO/Core
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/IO/Core
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/zlib
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/zlib
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/MetaIO/vtkmetaio
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/MetaIO
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/MetaIO
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/jpeg
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/jpeg
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/png
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/png
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/tiff
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/tiff
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Imaging/Core
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Imaging/Core
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/ParseOGLExt
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/ParseOGLExt
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Rendering/Core
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/Core
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/Color
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/Color
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Extraction
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Extraction
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Core
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Core
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/General
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/General
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/ComputationalGeometry
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/ComputationalGeometry
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Statistics
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Statistics
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Imaging/Fourier
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Imaging/Fourier
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/alglib
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/alglib
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Geometry
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Geometry
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Sources
> -I/storage/ home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Sources
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/EncodeString
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/EncodeString
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Rendering/OpenGL
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL
> -fvisibility=hidden -fvisibility-inlines-hidden -o
> CMakeFiles/vtkRenderingOpenGL.dir/vtkOSOpenGLRenderWindow.cxx.o -c
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:52:
> error: ?OSMesaContext? does not name a type
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:
> In constructor
> ?vtkOSOpenGLRenderWindowInternal::vtkOSOpenGLRenderWindowInternal(vtkRenderWindow*)?:
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:64:
> error: ?class vtkOSOpenGLRenderWindowInternal? has no member named
> ?OffScreenContextId?
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:
> In member function ?virtual void
> vtkOSOpenGLRenderWindow::SetStereoCapableWindow(int)?:
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:128:
> error: ?class vtkOSOpenGLRenderWindowInternal? has no member named
> ?OffScreenContextId?
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:
> In member function ?void vtkOSOpenGLRenderWindow::CreateOffScreenWindow(int,
> int)?:
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:185:
> error: ?class vtkOSOpenGLRenderWindowInternal? has no member named
> ?OffScreenContextId?
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:187:
> error: ?class vtkOSOpenGLRenderWindowInternal? has no member named
> ?OffScreenContextId?
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:187:
> error: ?OSMesaCreateContext? was not declared in this scope
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:
> In member function ?void vtkOSOpenGLRenderWindow::DestroyOffScreenWindow()?:
>
>
> ganesh
>
> _______________________________________________
> 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
>

From krishnapai09 at gmail.com  Wed Jul 29 17:32:11 2015
From: krishnapai09 at gmail.com (Krishna Pai)
Date: Wed, 29 Jul 2015 17:32:11 -0400
Subject: [Paraview] How to assign separate parallel pvserver processes
 to separate independent datasets?
In-Reply-To: <CAMaOp+GLqzc=vheCrKHGbmTNTz2gPkSH4hh=FwPEtkuAHQKTHg@mail.gmail.com>
References: <CAPHwKk48ggjkoDaJ+1Tfaez7ASgz3cFXKgosWMzYUx+ZEXzy6Q@mail.gmail.com>
 <CAMaOp+GLqzc=vheCrKHGbmTNTz2gPkSH4hh=FwPEtkuAHQKTHg@mail.gmail.com>
Message-ID: <CAPHwKk55H1HJ1v+ROPjJ28wq3LO_p3KpuY3CJed5wVaNApkQCw@mail.gmail.com>

Thanks for the recommendation, Andy. I've decided to use the
spatio-temporal parallelism plugin for a different application: I've found
that D3 re-partitions my data every time step, and I think this plugin
might be a better way to handle my spatio-temporal data. However, the
instructions on the wiki say to run it using pvbatch, which, as far as I
know, doesn't allow for interactive visualizations. Is there a way to
somehow run the python script it generates through the ParaView GUI instead
of by mpirunning pvbatch to allow for interactivity?

On Wed, Jul 29, 2015 at 12:48 AM, Andy Bauer <andy.bauer at kitware.com> wrote:

> The closest thing I can think of is doing this in batch. Information on
> that is available at
> http://www.paraview.org/Wiki/Spatio-Temporal_Parallelism. It's probably
> doable in ParaView but would likely take significant amount of
> modification.
>
> On Mon, Jul 27, 2015 at 5:26 PM, Krishna Pai <krishnapai09 at gmail.com>
> wrote:
>
>> Hi all,
>>
>> I know that, normally, ParaView works with one large dataset and
>> partitions it based on the number of processes, then renders and merges the
>> results, which I can then view on my ParaView GUI locally. What I want to
>> do is take a bunch of independent datasets and make each parallel process
>> render them without partitioning them further. In other words, I want a
>> one-to-one correspondence between a parallel process and a dataset with the
>> ability to view them separately locally (which I can do by filtering by
>> Process ID). So far, I've tried opening a couple of datasets separately and
>> simultaneously (using ctrl to select them both), and combined them with
>> AppendDatasets to see if they would separate out in the way I want. That
>> didn't work. In both instances, ParaView partitioned each dataset and
>> rendered a part of them in each process. I would appreciate any tips.
>>
>> Thanks,
>> Krishna Pai
>>
>> _______________________________________________
>> 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
>>
>>
>


-- 
          1   1
          1   /
          1 1                     1
          1 1      _    0   _   1 _       _      _
          1   \   1  1  1  (     1   7   1  7    _)
          1    !  1      1   )    1   1   1  1   {_}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150729/9fcbc24d/attachment.html>

From dave.demarle at kitware.com  Thu Jul 30 00:36:07 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 30 Jul 2015 00:36:07 -0400
Subject: [Paraview] Memory seeking problems in using the xdmf2 reader
In-Reply-To: <E65EBD9CD7A9004A924D2E7C5ED608D58BA250C8@ECS-EXG-P-MB05.win.lanl.gov>
References: <E65EBD9CD7A9004A924D2E7C5ED608D58BA250C8@ECS-EXG-P-MB05.win.lanl.gov>
Message-ID: <CANjZAi8SGrHo32CL4smp30apVXONv9Yy3Pb6g3nfNogy5TuhhQ@mail.gmail.com>

Would you mind trying this Jesus?

diff --git a/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfValuesBinary.cxx
b/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfValuesBinary.cxx
index 04ea0a7..6fe37d0 100644
--- a/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfValuesBinary.cxx
+++ b/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfValuesBinary.cxx
@@ -187,7 +187,7 @@ public:

 size_t XdmfValuesBinary::getSeek(){
     if(this->Seek==NULL)return 0;
-    return static_cast<size_t>(atoi(this->Seek));
+    return static_cast<size_t>(atol(this->Seek));
 }

Once you confirm it fixes it for you too I'll check it in.

Thanks,


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Fri, Jul 24, 2015 at 12:43 PM, Pulido, Jesus <pulido at lanl.gov> wrote:

>  Hello,
>
> I have written a custom xmf file used by the xdmf2 reader to properly read
> in (raw) binary data into Paraview. This normally works but only for small
> datasets. The file requires the input of a memory "seek" location to start
> reading the different scalar components of the data. A problem arises when
> there is a 512^3 dataset, with 5 scalar components that are required to be
> read in. The first two scalar components are read in correctly, then the
> next two components receive the error:
>
>  ERROR: In
> /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/IO/Xdmf2/vtkXdmfHeavyData.cxx,
> line 1128
>
> vtkXdmfReader (0x7f8614672af0): Failed to read attribute data
>
> The 5th component then becomes a duplicate of the 1st component.
> What I believe that's happening is that the "seek" value is only being
> represented as a signed integer, this would explain the memory location
> rolling from MAX_INT to -MAX_INT, and failing to read in scalar components
> 3 and 4. Their seek locations fall within this case. By the time the 5th
> component is read, the seek value may have rolled over back to positive
> values (seek > 0) and then duplicates the same data as the 1st component.
>
> Is this assumption correct and intended? Is there fix for this or an
> alternative way around reading large, raw datasets using this format? I'm
> attaching a sample xmf file
>
> Thank you,
> Jesus
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150730/e9493db8/attachment.html>

From aeatmon at lanl.gov  Thu Jul 30 09:52:50 2015
From: aeatmon at lanl.gov (Eatmon Jr., Arnold)
Date: Thu, 30 Jul 2015 13:52:50 +0000
Subject: [Paraview] adjusting vertical level setting via paraview python
	script
Message-ID: <D1DF8851.718%aeatmon@lanl.gov>

I?m one of the DSS interns working under Jim Ahrens for the summer. I am using paraviews python script in the HPC and I?m having an issue adjusting an attribute of paraview.simple.netcdfmpasreader ?VerticalLevel?.

I want to adjust it from the default to one and attempted:

paraview.simple.NetCDFMPASreader.VerticalLevel = 1
paraview.simple.NetCDFMPASreader.VerticalLevel = ?1'
And
paraview.simple.GetActiveSource().VerticalLevel = 1

The first two operate with no errors doing nothing in the program and the last returns an error that the class bars adding attributes to prevent errors due to spelling.

How do I adjust the vertical level setting?

Thank you in advance for your assistance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150730/60bc32cb/attachment.html>

From dave.demarle at kitware.com  Thu Jul 30 14:32:03 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 30 Jul 2015 14:32:03 -0400
Subject: [Paraview] adjusting vertical level setting via paraview python
	script
In-Reply-To: <D1DF8851.718%aeatmon@lanl.gov>
References: <D1DF8851.718%aeatmon@lanl.gov>
Message-ID: <CANjZAi8UrrgPa-2SOVz3EdKfzK6+8g40rMru528MO-XPvYUu=w@mail.gmail.com>

Regarding the adding attributes error message, it is likely that the
ActiveSource is not an MPAS reader at that point in time.
?GetActiveSource().__class__ should tell your what it is.

Regarding the level setting - what is yourReader.ShowMultilayerView?
The docs indicated a value of 1 makes VerticalLayer immaterial.



David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Thu, Jul 30, 2015 at 9:52 AM, Eatmon Jr., Arnold <aeatmon at lanl.gov>
wrote:

> I?m one of the DSS interns working under Jim Ahrens for the summer. I am
> using paraviews python script in the HPC and I?m having an issue adjusting
> an attribute of paraview.simple.netcdfmpasreader ?VerticalLevel?.
>
> I want to adjust it from the default to one and attempted:
>
> paraview.simple.NetCDFMPASreader.VerticalLevel = 1
> paraview.simple.NetCDFMPASreader.VerticalLevel = ?1'
> And
> paraview.simple.GetActiveSource().VerticalLevel = 1
>
> The first two operate with no errors doing nothing in the program and the
> last returns an error that the class bars adding attributes to prevent
> errors due to spelling.
>
> How do I adjust the vertical level setting?
>
> Thank you in advance for your assistance.
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150730/6959dff2/attachment.html>

From aeatmon at lanl.gov  Thu Jul 30 15:18:49 2015
From: aeatmon at lanl.gov (Eatmon Jr., Arnold)
Date: Thu, 30 Jul 2015 19:18:49 +0000
Subject: [Paraview] FW: adjusting vertical level setting via paraview python
 script
In-Reply-To: <D1DFCF4C.72E%aeatmon@lanl.gov>
References: <D1DF8851.718%aeatmon@lanl.gov>
 <CANjZAi8UrrgPa-2SOVz3EdKfzK6+8g40rMru528MO-XPvYUu=w@mail.gmail.com>
 <D1DFCF4C.72E%aeatmon@lanl.gov>
Message-ID: <D1DFD4AF.74B%aeatmon@lanl.gov>



From: "<Eatmon Jr.>", First name Last name <aeatmon at lanl.gov<mailto:aeatmon at lanl.gov>>
Date: Thursday, July 30, 2015 at 1:00 PM
To: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>
Subject: Re: [Paraview] adjusting vertical level setting via paraview python script

I added a line to the code to explicitly set the value to 0 and ran the script again, however it still does not adjust the vertical level.

I added paraview.simple.NetCDFMPASreader.ShowMultilayerView = 0
And then set vertical level to two different values and saw no change in the output.

Is my syntax correct? Should the values be defined in the above way or as  ?ShowMultilayerView = ?1? ?

From: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>
Date: Thursday, July 30, 2015 at 12:32 PM
To: First name Last name <aeatmon at lanl.gov<mailto:aeatmon at lanl.gov>>
Cc: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: Re: [Paraview] adjusting vertical level setting via paraview python script

Regarding the adding attributes error message, it is likely that the ActiveSource is not an MPAS reader at that point in time.
?GetActiveSource().__class__ should tell your what it is.

Regarding the level setting - what is yourReader.ShowMultilayerView?
The docs indicated a value of 1 makes VerticalLayer immaterial.



David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Thu, Jul 30, 2015 at 9:52 AM, Eatmon Jr., Arnold <aeatmon at lanl.gov<mailto:aeatmon at lanl.gov>> wrote:
I?m one of the DSS interns working under Jim Ahrens for the summer. I am using paraviews python script in the HPC and I?m having an issue adjusting an attribute of paraview.simple.netcdfmpasreader ?VerticalLevel?.

I want to adjust it from the default to one and attempted:

paraview.simple.NetCDFMPASreader.VerticalLevel = 1
paraview.simple.NetCDFMPASreader.VerticalLevel = ?1'
And
paraview.simple.GetActiveSource().VerticalLevel = 1

The first two operate with no errors doing nothing in the program and the last returns an error that the class bars adding attributes to prevent errors due to spelling.

How do I adjust the vertical level setting?

Thank you in advance for your assistance.

_______________________________________________
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


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

From aeatmon at lanl.gov  Thu Jul 30 15:19:07 2015
From: aeatmon at lanl.gov (Eatmon Jr., Arnold)
Date: Thu, 30 Jul 2015 19:19:07 +0000
Subject: [Paraview] FW: adjusting vertical level setting via paraview python
 script
In-Reply-To: <D1DFD169.73B%aeatmon@lanl.gov>
References: <D1DF8851.718%aeatmon@lanl.gov>
 <CANjZAi8UrrgPa-2SOVz3EdKfzK6+8g40rMru528MO-XPvYUu=w@mail.gmail.com>
 <D1DFD169.73B%aeatmon@lanl.gov>
Message-ID: <D1DFD4C0.74D%aeatmon@lanl.gov>



From: "<Eatmon Jr.>", First name Last name <aeatmon at lanl.gov<mailto:aeatmon at lanl.gov>>
Date: Thursday, July 30, 2015 at 1:12 PM
To: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>
Subject: Re: [Paraview] adjusting vertical level setting via paraview python script

As a followup to my last reply, I?m pasting the script below for reference because there may be a problem within of which I am not aware. The script is not too clean, though.

Also attached is an image of the output where I see the vertical level still needs to be turned down.

??????????????????????????????????????????????????

from paraview import coprocessing



#--------------------------------------------------------------

# Code generated from cpstate.py to create the CoProcessor.

# ParaView 4.3.1 64 bits



# ----------------------- CoProcessor definition -----------------------


def CreateCoProcessor():

  def _CreatePipeline(coprocessor, datadescription):

    class Pipeline:

      # state file generated using paraview version 4.3.1


      # ----------------------------------------------------------------

      # setup views used in the visualization

      # ----------------------------------------------------------------


      #### disable automatic camera reset on 'Show'

      paraview.simple._DisableFirstRenderCameraReset()


      # Create a new 'Render View'

      renderView1 = CreateView('RenderView')

      renderView1.ViewSize = [1811, 837]

      renderView1.CenterOfRotation = [0.0, 0.0, 69503.75]

      renderView1.StereoType = 0

      renderView1.CameraPosition = [-41129254.56226203, -8828710.007515563, 6001602.840730475]

      renderView1.CameraFocalPoint = [0.0, 0.0, 69503.75]

      renderView1.CameraViewUp = [0.06821863148547692, 0.3176561586160046, 0.9457487949828816]

      renderView1.CameraParallelScale = 10995245.645232411

      renderView1.Background = [0.37254901960784315, 0.36470588235294116, 0.3411764705882353]


      # register the view with coprocessor

      # and provide it with information such as the filename to use,

      # how frequently to write the images, etc.

      coprocessor.RegisterView(renderView1,

          filename='image_%t.png', freq=1, fittoscreen=0, magnification=1, width=1811, height=837, cinema={"camera":"Spherical", "phi":[-180,-162,-144,-126,-108,-90,-72,-54,-36,-18,0,18,36,54,72,90,108,126,144,162], "theta":[-180,-162,-144,-126,-108,-90,-72,-54,-36,-18,0,18,36,54,72,90,108,126,144,162] })


      # ----------------------------------------------------------------

      # setup the data processing pipelines

      # ---------------------------------------------------------------


      # create a new 'NetCDF MPAS reader'

      # create a producer from a simulation input

      output00240101_000000nc = coprocessor.CreateProducer(datadescription, 'X_Y_Z_1LAYER-primal')


      # ----------------------------------------------------------------

      # setup color maps and opacity mapes used in the visualization

      # note: the Get..() functions create a new object, if needed

      # ----------------------------------------------------------------



      # reset view to fit data

      renderView1.ResetCamera()


      # show data in view

      output00240101_000000ncDisplay = Show(output00240101_000000nc, renderView1)


      # Properties modified on output00240101_000000nc

      paraview.simple.NetCDFMPASreader.PointArrayStatus = ['temperature']

      paraview.simple.NetCDFMPASreader.ShowMultilayerView = 0

      paraview.simple.NetCDFMPASreader.VerticalLevel = '1'


      # Level1 = paraview.simple.ColorByArray()

      # Level1.ColorBy(mpas_data_1pvtuDisplay, ('CELLS', 'temperature'))


      # set scalar coloring

      ColorBy(output00240101_000000ncDisplay, ('CELLS', 'temperature'))


      # rescale color and/or opacity maps used to include current data range

      output00240101_000000ncDisplay.RescaleTransferFunctionToDataRange(True)



      # get color transfer function/color map for 'temperature'

      temperatureLUT = GetColorTransferFunction('temperature')

      temperatureLUT.InterpretValuesAsCategories = 0

      temperatureLUT.Discretize = 0

      temperatureLUT.MapControlPointsToLinearSpace()

      temperatureLUT.UseLogScale = 0

      temperatureLUT.RGBPoints = [-2.0, 0.105882, 0.2, 0.14902, -1.25, 0.141176, 0.25098, 0.180392, -0.5, 0.172549, 0.301961, 0.211765, 0.25, 0.211765, 0.34902, 0.243137, 1.0, 0.227451, 0.388235, 0.254902, 1.75, 0.239216, 0.431373, 0.258824, 2.5, 0.25098, 0.470588, 0.262745, 3.25, 0.258824, 0.509804, 0.258824, 4.0, 0.294118, 0.54902, 0.27451, 4.75, 0.333333, 0.580392, 0.294118, 5.5, 0.380392, 0.619608, 0.321569, 6.250000000000002, 0.431373, 0.658824, 0.34902, 7.0, 0.482353, 0.690196, 0.380392, 7.750000000000002, 0.52549, 0.729412, 0.388235, 8.5, 0.564706, 0.760784, 0.380392, 9.250000000000002, 0.631373, 0.788235, 0.411765, 10.0, 0.694118, 0.819608, 0.443137, 10.75, 0.745098, 0.85098, 0.458824, 11.5, 0.803922, 0.878431, 0.494118, 12.25, 0.843137, 0.901961, 0.521569, 13.0, 0.894118, 0.929412, 0.556863, 14.500000000000004, 0.94902, 0.94902, 0.647059, 16.0, 0.968627, 0.968627, 0.796078, 17.05, 1.0, 0.996078, 0.901961, 17.2, 0.968627, 1.0, 0.996078, 17.35, 0.901961, 1.0, 0.984314, 18.1, 0.831373, 0.988235, 0.972549, 19.0, 0.721569, 0.94902, 0.945098, 19.75, 0.639216, 0.882353, 0.901961, 20.500000000000004, 0.568627, 0.807843, 0.85098, 21.25, 0.513725, 0.717647, 0.788235, 22.0, 0.447059, 0.627451, 0.721569, 22.75, 0.388235, 0.541176, 0.65098, 23.5, 0.337255, 0.462745, 0.580392, 24.25, 0.286275, 0.388235, 0.521569, 25.0, 0.25098, 0.333333, 0.478431, 25.750000000000004, 0.219608, 0.290196, 0.45098, 26.5, 0.196078, 0.247059, 0.419608, 27.25, 0.152941, 0.188235, 0.34902, 28.0, 0.113725, 0.113725, 0.278431]

      temperatureLUT.ColorSpace = 'Lab'

      temperatureLUT.LockScalarRange = 0

      temperatureLUT.NanColor = [0.250004, 0.0, 0.0]

      temperatureLUT.ScalarRangeInitialized = 1.0



      # get opacity transfer function/opacity map for 'temperature'

      temperaturePWF = GetOpacityTransferFunction('temperature')

      temperaturePWF.Points = [-2.0, 0.0, 0.5, 0.0, 28.0, 1.0, 0.5, 0.0]

      temperaturePWF.ScalarRangeInitialized = 1


      # Properties modified on temperatureLUT

      # temperatureLUT.InterpretValuesAsCategories = 0



      # paraview.simple.NetCDFMPASreader.ShowMultilayerView = 0

      paraview.simple.NetCDFMPASreader.VerticalLevel = 1


      # renderView1.ResetCamera()


      # get active source.

      # Level2 = paraview.simple.GetActiveSource()

      # Level2.VerticalLevel = 1



      # ----------------------------------------------------------------

      # setup the visualization in view 'renderView1'

      # ----------------------------------------------------------------


      # show data from output00240101_000000nc

      output00240101_000000ncDisplay = Show(output00240101_000000nc, renderView1)

      # trace defaults for the display properties. 356617.92693278694

      output00240101_000000ncDisplay.ColorArrayName = ['CELLS', 'temperature']

      output00240101_000000ncDisplay.LookupTable = temperatureLUT

      output00240101_000000ncDisplay.ScalarOpacityUnitDistance = 1469170.6394257464


      # show color legend

      output00240101_000000ncDisplay.SetScalarBarVisibility(renderView1, True)


      # setup the color legend parameters for each legend in this view



      # get color legend/bar for temperatureLUT in view renderView1

      temperatureLUTColorBar = GetScalarBar(temperatureLUT, renderView1)

      temperatureLUTColorBar.Title = 'temperature'

      temperatureLUTColorBar.ComponentTitle = ''

    return Pipeline()


  class CoProcessor(coprocessing.CoProcessor):

    def CreatePipeline(self, datadescription):

      self.Pipeline = _CreatePipeline(self, datadescription)


  coprocessor = CoProcessor()

  # these are the frequencies at which the coprocessor updates.

  freqs = {'X_Y_Z_1LAYER-primal': [1]}

  coprocessor.SetUpdateFrequencies(freqs)

  return coprocessor


#--------------------------------------------------------------

# Global variables that will hold the pipeline for each timestep

# Creating the CoProcessor object, doesn't actually create the ParaView pipeline.

# It will be automatically setup when coprocessor.UpdateProducers() is called the

# first time.

coprocessor = CreateCoProcessor()


#--------------------------------------------------------------

# Enable Live-Visualizaton with ParaView

coprocessor.EnableLiveVisualization(False, 1)



# ---------------------- Data Selection method ----------------------


def RequestDataDescription(datadescription):

    "Callback to populate the request for current timestep"

    global coprocessor

    if datadescription.GetForceOutput() == True:

        # We are just going to request all fields and meshes from the simulation

        # code/adaptor.

        for i in range(datadescription.GetNumberOfInputDescriptions()):

            datadescription.GetInputDescription(i).AllFieldsOn()

            datadescription.GetInputDescription(i).GenerateMeshOn()

        return


    # setup requests for all inputs based on the requirements of the

    # pipeline.

    coprocessor.LoadRequestedData(datadescription)


# ------------------------ Processing method ------------------------


def DoCoProcessing(datadescription):

    "Callback to do co-processing for current timestep"

    global coprocessor


    # Update the coprocessor by providing it the newly generated simulation data.

    # If the pipeline hasn't been setup yet, this will setup the pipeline.

    coprocessor.UpdateProducers(datadescription)


    # Write output data, if appropriate.

    coprocessor.WriteData(datadescription);




    # Write image capture (Last arg: rescale lookup table), if appropriate.

    coprocessor.WriteImages(datadescription, rescale_lookuptable=False)


    # Live Visualization, if enabled.

    coprocessor.DoLiveVisualization(datadescription, "localhost", 22222)



From: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>
Date: Thursday, July 30, 2015 at 12:32 PM
To: First name Last name <aeatmon at lanl.gov<mailto:aeatmon at lanl.gov>>
Cc: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: Re: [Paraview] adjusting vertical level setting via paraview python script

Regarding the adding attributes error message, it is likely that the ActiveSource is not an MPAS reader at that point in time.
?GetActiveSource().__class__ should tell your what it is.

Regarding the level setting - what is yourReader.ShowMultilayerView?
The docs indicated a value of 1 makes VerticalLayer immaterial.



David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Thu, Jul 30, 2015 at 9:52 AM, Eatmon Jr., Arnold <aeatmon at lanl.gov<mailto:aeatmon at lanl.gov>> wrote:
I?m one of the DSS interns working under Jim Ahrens for the summer. I am using paraviews python script in the HPC and I?m having an issue adjusting an attribute of paraview.simple.netcdfmpasreader ?VerticalLevel?.

I want to adjust it from the default to one and attempted:

paraview.simple.NetCDFMPASreader.VerticalLevel = 1
paraview.simple.NetCDFMPASreader.VerticalLevel = ?1'
And
paraview.simple.GetActiveSource().VerticalLevel = 1

The first two operate with no errors doing nothing in the program and the last returns an error that the class bars adding attributes to prevent errors due to spelling.

How do I adjust the vertical level setting?

Thank you in advance for your assistance.

_______________________________________________
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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150730/6cf3d941/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2015-07-30 at 1.03.54 PM.png
Type: image/png
Size: 244567 bytes
Desc: Screen Shot 2015-07-30 at 1.03.54 PM.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150730/6cf3d941/attachment-0001.png>

From krishnapai09 at gmail.com  Thu Jul 30 15:20:07 2015
From: krishnapai09 at gmail.com (Krishna Pai)
Date: Thu, 30 Jul 2015 15:20:07 -0400
Subject: [Paraview] Using SpatioTemporalParallelism plugin in ParaView
Message-ID: <CAPHwKk6esyqjhDVVjiQ9+4BDrPjicDs-mjuj4VxOfm_risekTQ@mail.gmail.com>

Hi all,

I've been working with spatio-temporal data stored in an xdmf file. I found
that ParaView doesn't handle parallel processing of this file well, so I
thought I would use the SpatioTemporalParallelism plugin to partition the
data better. I chose the Parallel Image Data Writer to write to a .pvti
before using the plugin to export state. Once the python script was
generated, and I tried running it with pvbatch, I got the following error
message:

Traceback (most recent call last):
  File "./yoda.py", line 26, in <module>
    xdmf_test_v01xdmf = STP.CreateReader(XDMFReader,
fileinfo='/lustre/cmf/scratch/k/kpai/projects/NeptuneData_2015-07-28/xdmf_test_v01.xdmf')
TypeError: CreateReader() takes exactly 2 non-keyword arguments (1 given)

The file path above is to the xdmf file on a remote machine.
I'm not sure what other arguments need to be given, considering the script
was generated by ParaView (maybe I exported state incorrectly?). I would
appreciate any help.

Thanks,
Krishna Pai
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150730/60c740a9/attachment.html>

From dave.demarle at kitware.com  Thu Jul 30 15:46:09 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 30 Jul 2015 15:46:09 -0400
Subject: [Paraview] FW: adjusting vertical level setting via paraview
 python script
In-Reply-To: <D1DFD4C0.74D%aeatmon@lanl.gov>
References: <D1DF8851.718%aeatmon@lanl.gov>
 <CANjZAi8UrrgPa-2SOVz3EdKfzK6+8g40rMru528MO-XPvYUu=w@mail.gmail.com>
 <D1DFD169.73B%aeatmon@lanl.gov> <D1DFD4C0.74D%aeatmon@lanl.gov>
Message-ID: <CANjZAi8=FQriZ7+szc7HbYAak6K4VpdnQ2geBj8deOKeFxm=FQ@mail.gmail.com>

I verified in the GUI that I can change the level and see it take effect,
so it should work in principle. You might want to open that file in the
paraView GUI and do the same exercise.

In your script a couple of bits looks fishy to me and might cause the
problem.

paraview.simple.NetCDFMPASreader.PointArrayStatus = ['temperature']
paraview.simple.NetCDFMPASreader.ShowMultilayerView = 0
paraview.simple.NetCDFMPASreader.VerticalLevel = '1' *#use = 1 not = '1'*

later

paraview.simple.NetCDFMPASreader.VerticalLevel = 1

just do it one time


I think the above all do something like set propeties of the global
netcdmfmpasreader class, not the one specific instance of that class that
you care about.

# get active source.
# Level2 = paraview.simple.GetActiveSource()
# Level2.VerticalLevel = 1

this is closer, try
level2=paraview.simple.FindSource('X_Y_Z_1LAYER-primal')

or better yet, since it is defined early on just

Layer2 = output00240101_000000nc

Either should give you the specific instance and then you can call
Layer2.VerticalLevel
= 1 on it.

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Thu, Jul 30, 2015 at 3:19 PM, Eatmon Jr., Arnold <aeatmon at lanl.gov>
wrote:

>
>
> From: "<Eatmon Jr.>", First name Last name <aeatmon at lanl.gov>
> Date: Thursday, July 30, 2015 at 1:12 PM
> To: David E DeMarle <dave.demarle at kitware.com>
> Subject: Re: [Paraview] adjusting vertical level setting via paraview
> python script
>
> As a followup to my last reply, I?m pasting the script below for reference
> because there may be a problem within of which I am not aware. The script
> is not too clean, though.
>
> Also attached is an image of the output where I see the vertical level
> still needs to be turned down.
>
> ??????????????????????????????????????????????????
>
> from paraview import coprocessing
>
>
>
> #--------------------------------------------------------------
>
> # Code generated from cpstate.py to create the CoProcessor.
>
> # ParaView 4.3.1 64 bits
>
>
>
> # ----------------------- CoProcessor definition -----------------------
>
>
> def CreateCoProcessor():
>
>   def _CreatePipeline(coprocessor, datadescription):
>
>     class Pipeline:
>
>       # state file generated using paraview version 4.3.1
>
>
>       # ----------------------------------------------------------------
>
>       # setup views used in the visualization
>
>       # ----------------------------------------------------------------
>
>
>       #### disable automatic camera reset on 'Show'
>
>       paraview.simple._DisableFirstRenderCameraReset()
>
>
>       # Create a new 'Render View'
>
>       renderView1 = CreateView('RenderView')
>
>       renderView1.ViewSize = [1811, 837]
>
>       renderView1.CenterOfRotation = [0.0, 0.0, 69503.75]
>
>       renderView1.StereoType = 0
>
>       renderView1.CameraPosition = [-41129254.56226203,
> -8828710.007515563, 6001602.840730475]
>
>       renderView1.CameraFocalPoint = [0.0, 0.0, 69503.75]
>
>       renderView1.CameraViewUp = [0.06821863148547692, 0.3176561586160046,
> 0.9457487949828816]
>
>       renderView1.CameraParallelScale = 10995245.645232411
>
>       renderView1.Background = [0.37254901960784315, 0.36470588235294116,
> 0.3411764705882353]
>
>
>       # register the view with coprocessor
>
>       # and provide it with information such as the filename to use,
>
>       # how frequently to write the images, etc.
>
>       coprocessor.RegisterView(renderView1,
>
>           filename='image_%t.png', freq=1, fittoscreen=0, magnification=1,
> width=1811, height=837, cinema={"camera":"Spherical",
> "phi":[-180,-162,-144,-126,-108,-90,-72,-54,-36,-18,0,18,36,54,72,90,108,126,144,162],
> "theta":[-180,-162,-144,-126,-108,-90,-72,-54,-36,-18,0,18,36,54,72,90,108,126,144,162]
> })
>
>
>       # ----------------------------------------------------------------
>
>       # setup the data processing pipelines
>
>       # ---------------------------------------------------------------
>
>
>       # create a new 'NetCDF MPAS reader'
>
>       # create a producer from a simulation input
>
>       output00240101_000000nc =
> coprocessor.CreateProducer(datadescription, 'X_Y_Z_1LAYER-primal')
>
>
>       # ----------------------------------------------------------------
>
>       # setup color maps and opacity mapes used in the visualization
>
>       # note: the Get..() functions create a new object, if needed
>
>       # ----------------------------------------------------------------
>
>
>
>       # reset view to fit data
>
>       renderView1.ResetCamera()
>
>
>       # show data in view
>
>       output00240101_000000ncDisplay = Show(output00240101_000000nc,
> renderView1)
>
>
>       # Properties modified on output00240101_000000nc
>
>       paraview.simple.NetCDFMPASreader.PointArrayStatus = ['temperature']
>
>       paraview.simple.NetCDFMPASreader.ShowMultilayerView = 0
>
>       paraview.simple.NetCDFMPASreader.VerticalLevel = '1'
>
>
>       # Level1 = paraview.simple.ColorByArray()
>
>       # Level1.ColorBy(mpas_data_1pvtuDisplay, ('CELLS', 'temperature'))
>
>
>       # set scalar coloring
>
>       ColorBy(output00240101_000000ncDisplay, ('CELLS', 'temperature'))
>
>
>       # rescale color and/or opacity maps used to include current data
> range
>
>
> output00240101_000000ncDisplay.RescaleTransferFunctionToDataRange(True)
>
>
>
>       # get color transfer function/color map for 'temperature'
>
>       temperatureLUT = GetColorTransferFunction('temperature')
>
>       temperatureLUT.InterpretValuesAsCategories = 0
>
>       temperatureLUT.Discretize = 0
>
>       temperatureLUT.MapControlPointsToLinearSpace()
>
>       temperatureLUT.UseLogScale = 0
>
>       temperatureLUT.RGBPoints = [-2.0, 0.105882, 0.2, 0.14902, -1.25,
> 0.141176, 0.25098, 0.180392, -0.5, 0.172549, 0.301961, 0.211765, 0.25,
> 0.211765, 0.34902, 0.243137, 1.0, 0.227451, 0.388235, 0.254902, 1.75,
> 0.239216, 0.431373, 0.258824, 2.5, 0.25098, 0.470588, 0.262745, 3.25,
> 0.258824, 0.509804, 0.258824, 4.0, 0.294118, 0.54902, 0.27451, 4.75,
> 0.333333, 0.580392, 0.294118, 5.5, 0.380392, 0.619608, 0.321569,
> 6.250000000000002, 0.431373, 0.658824, 0.34902, 7.0, 0.482353, 0.690196,
> 0.380392, 7.750000000000002, 0.52549, 0.729412, 0.388235, 8.5, 0.564706,
> 0.760784, 0.380392, 9.250000000000002, 0.631373, 0.788235, 0.411765, 10.0,
> 0.694118, 0.819608, 0.443137, 10.75, 0.745098, 0.85098, 0.458824, 11.5,
> 0.803922, 0.878431, 0.494118, 12.25, 0.843137, 0.901961, 0.521569, 13.0,
> 0.894118, 0.929412, 0.556863, 14.500000000000004, 0.94902, 0.94902,
> 0.647059, 16.0, 0.968627, 0.968627, 0.796078, 17.05, 1.0, 0.996078,
> 0.901961, 17.2, 0.968627, 1.0, 0.996078, 17.35, 0.901961, 1.0, 0.984314,
> 18.1, 0.831373, 0.988235, 0.972549, 19.0, 0.721569, 0.94902, 0.945098,
> 19.75, 0.639216, 0.882353, 0.901961, 20.500000000000004, 0.568627,
> 0.807843, 0.85098, 21.25, 0.513725, 0.717647, 0.788235, 22.0, 0.447059,
> 0.627451, 0.721569, 22.75, 0.388235, 0.541176, 0.65098, 23.5, 0.337255,
> 0.462745, 0.580392, 24.25, 0.286275, 0.388235, 0.521569, 25.0, 0.25098,
> 0.333333, 0.478431, 25.750000000000004, 0.219608, 0.290196, 0.45098, 26.5,
> 0.196078, 0.247059, 0.419608, 27.25, 0.152941, 0.188235, 0.34902, 28.0,
> 0.113725, 0.113725, 0.278431]
>
>       temperatureLUT.ColorSpace = 'Lab'
>
>       temperatureLUT.LockScalarRange = 0
>
>       temperatureLUT.NanColor = [0.250004, 0.0, 0.0]
>
>       temperatureLUT.ScalarRangeInitialized = 1.0
>
>
>
>       # get opacity transfer function/opacity map for 'temperature'
>
>       temperaturePWF = GetOpacityTransferFunction('temperature')
>
>       temperaturePWF.Points = [-2.0, 0.0, 0.5, 0.0, 28.0, 1.0, 0.5, 0.0]
>
>       temperaturePWF.ScalarRangeInitialized = 1
>
>
>       # Properties modified on temperatureLUT
>
>       # temperatureLUT.InterpretValuesAsCategories = 0
>
>
>
>       # paraview.simple.NetCDFMPASreader.ShowMultilayerView = 0
>
>       paraview.simple.NetCDFMPASreader.VerticalLevel = 1
>
>
>       # renderView1.ResetCamera()
>
>
>       # get active source.
>
>       # Level2 = paraview.simple.GetActiveSource()
>
>       # Level2.VerticalLevel = 1
>
>
>
>       # ----------------------------------------------------------------
>
>       # setup the visualization in view 'renderView1'
>
>       # ----------------------------------------------------------------
>
>
>       # show data from output00240101_000000nc
>
>       output00240101_000000ncDisplay = Show(output00240101_000000nc,
> renderView1)
>
>       # trace defaults for the display properties. 356617.92693278694
>
>       output00240101_000000ncDisplay.ColorArrayName = ['CELLS',
> 'temperature']
>
>       output00240101_000000ncDisplay.LookupTable = temperatureLUT
>
>       output00240101_000000ncDisplay.ScalarOpacityUnitDistance = 1469170.
> 6394257464
>
>
>       # show color legend
>
>       output00240101_000000ncDisplay.SetScalarBarVisibility(renderView1,
> True)
>
>
>       # setup the color legend parameters for each legend in this view
>
>
>
>       # get color legend/bar for temperatureLUT in view renderView1
>
>       temperatureLUTColorBar = GetScalarBar(temperatureLUT, renderView1)
>
>       temperatureLUTColorBar.Title = 'temperature'
>
>       temperatureLUTColorBar.ComponentTitle = ''
>
>     return Pipeline()
>
>
>   class CoProcessor(coprocessing.CoProcessor):
>
>     def CreatePipeline(self, datadescription):
>
>       self.Pipeline = _CreatePipeline(self, datadescription)
>
>
>   coprocessor = CoProcessor()
>
>   # these are the frequencies at which the coprocessor updates.
>
>   freqs = {'X_Y_Z_1LAYER-primal': [1]}
>
>   coprocessor.SetUpdateFrequencies(freqs)
>
>   return coprocessor
>
>
> #--------------------------------------------------------------
>
> # Global variables that will hold the pipeline for each timestep
>
> # Creating the CoProcessor object, doesn't actually create the ParaView
> pipeline.
>
> # It will be automatically setup when coprocessor.UpdateProducers() is
> called the
>
> # first time.
>
> coprocessor = CreateCoProcessor()
>
>
> #--------------------------------------------------------------
>
> # Enable Live-Visualizaton with ParaView
>
> coprocessor.EnableLiveVisualization(False, 1)
>
>
>
> # ---------------------- Data Selection method ----------------------
>
>
> def RequestDataDescription(datadescription):
>
>     "Callback to populate the request for current timestep"
>
>     global coprocessor
>
>     if datadescription.GetForceOutput() == True:
>
>         # We are just going to request all fields and meshes from the
> simulation
>
>         # code/adaptor.
>
>         for i in range(datadescription.GetNumberOfInputDescriptions()):
>
>             datadescription.GetInputDescription(i).AllFieldsOn()
>
>             datadescription.GetInputDescription(i).GenerateMeshOn()
>
>         return
>
>
>     # setup requests for all inputs based on the requirements of the
>
>     # pipeline.
>
>     coprocessor.LoadRequestedData(datadescription)
>
>
> # ------------------------ Processing method ------------------------
>
>
> def DoCoProcessing(datadescription):
>
>     "Callback to do co-processing for current timestep"
>
>     global coprocessor
>
>
>     # Update the coprocessor by providing it the newly generated
> simulation data.
>
>     # If the pipeline hasn't been setup yet, this will setup the pipeline.
>
>     coprocessor.UpdateProducers(datadescription)
>
>
>     # Write output data, if appropriate.
>
>     coprocessor.WriteData(datadescription);
>
>
>
>
>     # Write image capture (Last arg: rescale lookup table), if appropriate.
>
>     coprocessor.WriteImages(datadescription, rescale_lookuptable=False)
>
>
>     # Live Visualization, if enabled.
>
>     coprocessor.DoLiveVisualization(datadescription, "localhost", 22222)
>
>
>
>
> From: David E DeMarle <dave.demarle at kitware.com>
> Date: Thursday, July 30, 2015 at 12:32 PM
> To: First name Last name <aeatmon at lanl.gov>
> Cc: "paraview at paraview.org" <paraview at paraview.org>
> Subject: Re: [Paraview] adjusting vertical level setting via paraview
> python script
>
> Regarding the adding attributes error message, it is likely that the
> ActiveSource is not an MPAS reader at that point in time.
> ?GetActiveSource().__class__ should tell your what it is.
>
> Regarding the level setting - what is yourReader.ShowMultilayerView?
> The docs indicated a value of 1 makes VerticalLayer immaterial.
>
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Thu, Jul 30, 2015 at 9:52 AM, Eatmon Jr., Arnold <aeatmon at lanl.gov>
> wrote:
>
>> I?m one of the DSS interns working under Jim Ahrens for the summer. I am
>> using paraviews python script in the HPC and I?m having an issue adjusting
>> an attribute of paraview.simple.netcdfmpasreader ?VerticalLevel?.
>>
>> I want to adjust it from the default to one and attempted:
>>
>> paraview.simple.NetCDFMPASreader.VerticalLevel = 1
>> paraview.simple.NetCDFMPASreader.VerticalLevel = ?1'
>> And
>> paraview.simple.GetActiveSource().VerticalLevel = 1
>>
>> The first two operate with no errors doing nothing in the program and the
>> last returns an error that the class bars adding attributes to prevent
>> errors due to spelling.
>>
>> How do I adjust the vertical level setting?
>>
>> Thank you in advance for your assistance.
>>
>> _______________________________________________
>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150730/10a87ad5/attachment.html>

From aeatmon at lanl.gov  Thu Jul 30 15:59:19 2015
From: aeatmon at lanl.gov (Eatmon Jr., Arnold)
Date: Thu, 30 Jul 2015 19:59:19 +0000
Subject: [Paraview] adjusting vertical level setting via paraview python
 script
In-Reply-To: <CANjZAi9jsg=wgZLdCr-vE_sP0mgWryg5X9NCAmR0Na=DbP_u0A@mail.gmail.com>
References: <D1DF8851.718%aeatmon@lanl.gov>
 <CANjZAi8UrrgPa-2SOVz3EdKfzK6+8g40rMru528MO-XPvYUu=w@mail.gmail.com>
 <D1DFD169.73B%aeatmon@lanl.gov>
 <CANjZAi9jsg=wgZLdCr-vE_sP0mgWryg5X9NCAmR0Na=DbP_u0A@mail.gmail.com>
Message-ID: <D1DFDC91.756%aeatmon@lanl.gov>

I noticed when pasting into the email and tried to change them, but the problem still persists even when adjusting them as you stated


  # Properties modified on output00240101_000000nc

      paraview.simple.NetCDFMPASreader.PointArrayStatus = ['temperature']

      paraview.simple.NetCDFMPASreader.ShowMultilayerView = 0

      paraview.simple.NetCDFMPASreader.VerticalLevel = 32



And I commented the repeating lines out




      # paraview.simple.NetCDFMPASreader.ShowMultilayerView = 0

      # paraview.simple.NetCDFMPASreader.VerticalLevel = 1


 However output remains exactly the same even adjusting the vertical level to something like 33 that would return an extremely noticeable difference.



I do see it is possible in the GUI however, it works exactly as it should there.
On a wing of faith, I also tried formatting as = [?1?] and that did not work either.

Thank you for your continuing assistance by the way, I asked around and it does seem to be a difficult issue to remedy.
From: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>
Date: Thursday, July 30, 2015 at 1:45 PM
To: First name Last name <aeatmon at lanl.gov<mailto:aeatmon at lanl.gov>>
Subject: Re: [Paraview] adjusting vertical level setting via paraview python script


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

From lyon at fnal.gov  Thu Jul 30 16:19:18 2015
From: lyon at fnal.gov (Adam Lyon)
Date: Thu, 30 Jul 2015 15:19:18 -0500
Subject: [Paraview] Differences between OpenGL and OpenGL2 versions of
	ParaView
Message-ID: <CANjddW2ooLsY9yo+7+-ON9-uRftDmvc0CiMNS1qCy_6bb2-bOw@mail.gmail.com>

Hi,  I'm trying to use ParaView built with OpenGL2, hoping to see some
speed improvement when I interact with my visualization. Indeed for a
complicated geometry I see significant speed up (e.g. ~25 fps with OpenGL2
vs. 5 fps with regular ParaView). But I also see serious errors in the
display. I've attached two images of our "g-2 muon storage ring" (never
mind what it actually is, though it is very cool :-) ..

[image: Inline image 1]

The first, mostly blue image, is from regular ParaView (downloaded Mac
binary 4.3.1 64 bit)  and is what the ring is supposed to look like. There
is a color vector selected and I've unchecked "Map scalars" so that the
colors are "true". And indeed the RGB color values in the vector are what
is shown on the display.


[image: Inline image 2]
The next image, with a chunk on the left side missing, is from the OpenGL2
ParaView (Mac built from source 4.3.1-882-gbdceec7 64 bit) configured
identically as the other ParaView. So it should look identical to the
mostly blue picture. Along with the missing chunk, you see the colors look
very wrong. What's even stranger is that the missing chunk is really
missing - not invisible - the visualization is made of multiblock datasets,
and right clicking where a structure should be only brings up the link
camera option.

You can try this yourself -- see
https://www.dropbox.com/sh/900ocfc90v0w3r6/AACmqz8kVrGPUMnJbpxAFOzBa?dl=0 .
The "gm2ring.zip" file has gm2ring.vtm (with the corresponding gm2ring
directory) and gm2ring.pvsm to restore my configuration.

I'm looking forward to using the OpenGL2 version when it works better. I
hope this helps in working out its kinks (or hoping to find out I've built
or configured something incorrectly). Let me know how I can help!  Thanks!
-- Adam
*------*

*Adam L. Lyon*
*Scientist; Associate Division Head for Systems for Scientific Applications*

Scientific Computing Division & Muon g-2 Experiment
Fermi National Accelerator Laboratory
630 840 5522 office
www.fnal.gov
lyon at fnal.gov

Connect with us!
Newsletter <http://www.fnal.gov/pub/today/>  |  Facebook
<https://www.facebook.com/Fermilab>  |  Twitter
<https://twitter.com/Fermilab>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150730/95883e1a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gm2ringsim_opengl_good.png
Type: image/png
Size: 19431 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150730/95883e1a/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gm2ringsim_opengl2_bad.png
Type: image/png
Size: 16709 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150730/95883e1a/attachment-0001.png>

From aeatmon at lanl.gov  Thu Jul 30 16:20:46 2015
From: aeatmon at lanl.gov (Eatmon Jr., Arnold)
Date: Thu, 30 Jul 2015 20:20:46 +0000
Subject: [Paraview] adjusting vertical level setting via paraview python
 script
In-Reply-To: <CANjZAi9jsg=wgZLdCr-vE_sP0mgWryg5X9NCAmR0Na=DbP_u0A@mail.gmail.com>
References: <D1DF8851.718%aeatmon@lanl.gov>
 <CANjZAi8UrrgPa-2SOVz3EdKfzK6+8g40rMru528MO-XPvYUu=w@mail.gmail.com>
 <D1DFD169.73B%aeatmon@lanl.gov>
 <CANjZAi9jsg=wgZLdCr-vE_sP0mgWryg5X9NCAmR0Na=DbP_u0A@mail.gmail.com>
Message-ID: <D1DFE283.768%aeatmon@lanl.gov>

      # Level2 = paraview.simple.FindSource('X_Y_Z_1LAYER-primal')

      # Level2.VerticalLevel = 32


      Layer2 = output00240101_000000nc

      Layer2.VerticalLevel = 32


Also,

I tried both of the above both individually with the other commented out and running at the same time, they both return that the attribute VerticalLevel does not exist in that class. It seems to solely exist in paraview.simple.NetCDFreader.


From: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>
Date: Thursday, July 30, 2015 at 1:45 PM
To: First name Last name <aeatmon at lanl.gov<mailto:aeatmon at lanl.gov>>
Subject: Re: [Paraview] adjusting vertical level setting via paraview python script

I verified in the GUI that I can change the level and see it take effect, so it should work in principle. You might want to open that file in the paraView GUI and do the same exercise.

In your script a couple of bits looks fishy to me and might cause the problem.

paraview.simple.NetCDFMPASreader.PointArrayStatus = ['temperature']
paraview.simple.NetCDFMPASreader.ShowMultilayerView = 0
paraview.simple.NetCDFMPASreader.VerticalLevel = '1' #use = 1 not = '1'

later

paraview.simple.NetCDFMPASreader.VerticalLevel = 1

just do it one time


I think the above all do something like set propeties of the global netcdmfmpasreader class, not the one specific instance of that class that you care about.

# get active source.
# Level2 = paraview.simple.GetActiveSource()
# Level2.VerticalLevel = 1

this is closer, try
level2=paraview.simple.FindSource('X_Y_Z_1LAYER-primal')

or better yet, since it is defined early on just

Layer2 = output00240101_000000nc

Either should give you the specific instance and then you can call Layer2.VerticalLevel = 1 on it.



David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Thu, Jul 30, 2015 at 3:12 PM, Eatmon Jr., Arnold <aeatmon at lanl.gov<mailto:aeatmon at lanl.gov>> wrote:
As a followup to my last reply, I?m pasting the script below for reference because there may be a problem within of which I am not aware. The script is not too clean, though.

Also attached is an image of the output where I see the vertical level still needs to be turned down.

??????????????????????????????????????????????????

from paraview import coprocessing



#--------------------------------------------------------------

# Code generated from cpstate.py to create the CoProcessor.

# ParaView 4.3.1 64 bits



# ----------------------- CoProcessor definition -----------------------


def CreateCoProcessor():

  def _CreatePipeline(coprocessor, datadescription):

    class Pipeline:

      # state file generated using paraview version 4.3.1


      # ----------------------------------------------------------------

      # setup views used in the visualization

      # ----------------------------------------------------------------


      #### disable automatic camera reset on 'Show'

      paraview.simple._DisableFirstRenderCameraReset()


      # Create a new 'Render View'

      renderView1 = CreateView('RenderView')

      renderView1.ViewSize = [1811, 837]

      renderView1.CenterOfRotation = [0.0, 0.0, 69503.75]

      renderView1.StereoType = 0

      renderView1.CameraPosition = [-41129254.56226203, -8828710.007515563, 6001602.840730475]

      renderView1.CameraFocalPoint = [0.0, 0.0, 69503.75]

      renderView1.CameraViewUp = [0.06821863148547692, 0.3176561586160046, 0.9457487949828816]

      renderView1.CameraParallelScale = 10995245.645232411

      renderView1.Background = [0.37254901960784315, 0.36470588235294116, 0.3411764705882353]


      # register the view with coprocessor

      # and provide it with information such as the filename to use,

      # how frequently to write the images, etc.

      coprocessor.RegisterView(renderView1,

          filename='image_%t.png', freq=1, fittoscreen=0, magnification=1, width=1811, height=837, cinema={"camera":"Spherical", "phi":[-180,-162,-144,-126,-108,-90,-72,-54,-36,-18,0,18,36,54,72,90,108,126,144,162], "theta":[-180,-162,-144,-126,-108,-90,-72,-54,-36,-18,0,18,36,54,72,90,108,126,144,162] })


      # ----------------------------------------------------------------

      # setup the data processing pipelines

      # ---------------------------------------------------------------


      # create a new 'NetCDF MPAS reader'

      # create a producer from a simulation input

      output00240101_000000nc = coprocessor.CreateProducer(datadescription, 'X_Y_Z_1LAYER-primal')


      # ----------------------------------------------------------------

      # setup color maps and opacity mapes used in the visualization

      # note: the Get..() functions create a new object, if needed

      # ----------------------------------------------------------------



      # reset view to fit data

      renderView1.ResetCamera()


      # show data in view

      output00240101_000000ncDisplay = Show(output00240101_000000nc, renderView1)


      # Properties modified on output00240101_000000nc

      paraview.simple.NetCDFMPASreader.PointArrayStatus = ['temperature']

      paraview.simple.NetCDFMPASreader.ShowMultilayerView = 0

      paraview.simple.NetCDFMPASreader.VerticalLevel = '1'


      # Level1 = paraview.simple.ColorByArray()

      # Level1.ColorBy(mpas_data_1pvtuDisplay, ('CELLS', 'temperature'))


      # set scalar coloring

      ColorBy(output00240101_000000ncDisplay, ('CELLS', 'temperature'))


      # rescale color and/or opacity maps used to include current data range

      output00240101_000000ncDisplay.RescaleTransferFunctionToDataRange(True)



      # get color transfer function/color map for 'temperature'

      temperatureLUT = GetColorTransferFunction('temperature')

      temperatureLUT.InterpretValuesAsCategories = 0

      temperatureLUT.Discretize = 0

      temperatureLUT.MapControlPointsToLinearSpace()

      temperatureLUT.UseLogScale = 0

      temperatureLUT.RGBPoints = [-2.0, 0.105882, 0.2, 0.14902, -1.25, 0.141176, 0.25098, 0.180392, -0.5, 0.172549, 0.301961, 0.211765, 0.25, 0.211765, 0.34902, 0.243137, 1.0, 0.227451, 0.388235, 0.254902, 1.75, 0.239216, 0.431373, 0.258824, 2.5, 0.25098, 0.470588, 0.262745, 3.25, 0.258824, 0.509804, 0.258824, 4.0, 0.294118, 0.54902, 0.27451, 4.75, 0.333333, 0.580392, 0.294118, 5.5, 0.380392, 0.619608, 0.321569, 6.250000000000002, 0.431373, 0.658824, 0.34902, 7.0, 0.482353, 0.690196, 0.380392, 7.750000000000002, 0.52549, 0.729412, 0.388235, 8.5, 0.564706, 0.760784, 0.380392, 9.250000000000002, 0.631373, 0.788235, 0.411765, 10.0, 0.694118, 0.819608, 0.443137, 10.75, 0.745098, 0.85098, 0.458824, 11.5, 0.803922, 0.878431, 0.494118, 12.25, 0.843137, 0.901961, 0.521569, 13.0, 0.894118, 0.929412, 0.556863, 14.500000000000004, 0.94902, 0.94902, 0.647059, 16.0, 0.968627, 0.968627, 0.796078, 17.05, 1.0, 0.996078, 0.901961, 17.2, 0.968627, 1.0, 0.996078, 17.35, 0.901961, 1.0, 0.984314, 18.1, 0.831373, 0.988235, 0.972549, 19.0, 0.721569, 0.94902, 0.945098, 19.75, 0.639216, 0.882353, 0.901961, 20.500000000000004, 0.568627, 0.807843, 0.85098, 21.25, 0.513725, 0.717647, 0.788235, 22.0, 0.447059, 0.627451, 0.721569, 22.75, 0.388235, 0.541176, 0.65098, 23.5, 0.337255, 0.462745, 0.580392, 24.25, 0.286275, 0.388235, 0.521569, 25.0, 0.25098, 0.333333, 0.478431, 25.750000000000004, 0.219608, 0.290196, 0.45098, 26.5, 0.196078, 0.247059, 0.419608, 27.25, 0.152941, 0.188235, 0.34902, 28.0, 0.113725, 0.113725, 0.278431]

      temperatureLUT.ColorSpace = 'Lab'

      temperatureLUT.LockScalarRange = 0

      temperatureLUT.NanColor = [0.250004, 0.0, 0.0]

      temperatureLUT.ScalarRangeInitialized = 1.0



      # get opacity transfer function/opacity map for 'temperature'

      temperaturePWF = GetOpacityTransferFunction('temperature')

      temperaturePWF.Points = [-2.0, 0.0, 0.5, 0.0, 28.0, 1.0, 0.5, 0.0]

      temperaturePWF.ScalarRangeInitialized = 1


      # Properties modified on temperatureLUT

      # temperatureLUT.InterpretValuesAsCategories = 0



      # paraview.simple.NetCDFMPASreader.ShowMultilayerView = 0

      paraview.simple.NetCDFMPASreader.VerticalLevel = 1


      # renderView1.ResetCamera()


      # get active source.

      # Level2 = paraview.simple.GetActiveSource()

      # Level2.VerticalLevel = 1



      # ----------------------------------------------------------------

      # setup the visualization in view 'renderView1'

      # ----------------------------------------------------------------


      # show data from output00240101_000000nc

      output00240101_000000ncDisplay = Show(output00240101_000000nc, renderView1)

      # trace defaults for the display properties. 356617.92693278694

      output00240101_000000ncDisplay.ColorArrayName = ['CELLS', 'temperature']

      output00240101_000000ncDisplay.LookupTable = temperatureLUT

      output00240101_000000ncDisplay.ScalarOpacityUnitDistance = 1469170.6394257464<tel:6394257464>


      # show color legend

      output00240101_000000ncDisplay.SetScalarBarVisibility(renderView1, True)


      # setup the color legend parameters for each legend in this view



      # get color legend/bar for temperatureLUT in view renderView1

      temperatureLUTColorBar = GetScalarBar(temperatureLUT, renderView1)

      temperatureLUTColorBar.Title = 'temperature'

      temperatureLUTColorBar.ComponentTitle = ''

    return Pipeline()


  class CoProcessor(coprocessing.CoProcessor):

    def CreatePipeline(self, datadescription):

      self.Pipeline = _CreatePipeline(self, datadescription)


  coprocessor = CoProcessor()

  # these are the frequencies at which the coprocessor updates.

  freqs = {'X_Y_Z_1LAYER-primal': [1]}

  coprocessor.SetUpdateFrequencies(freqs)

  return coprocessor


#--------------------------------------------------------------

# Global variables that will hold the pipeline for each timestep

# Creating the CoProcessor object, doesn't actually create the ParaView pipeline.

# It will be automatically setup when coprocessor.UpdateProducers() is called the

# first time.

coprocessor = CreateCoProcessor()


#--------------------------------------------------------------

# Enable Live-Visualizaton with ParaView

coprocessor.EnableLiveVisualization(False, 1)



# ---------------------- Data Selection method ----------------------


def RequestDataDescription(datadescription):

    "Callback to populate the request for current timestep"

    global coprocessor

    if datadescription.GetForceOutput() == True:

        # We are just going to request all fields and meshes from the simulation

        # code/adaptor.

        for i in range(datadescription.GetNumberOfInputDescriptions()):

            datadescription.GetInputDescription(i).AllFieldsOn()

            datadescription.GetInputDescription(i).GenerateMeshOn()

        return


    # setup requests for all inputs based on the requirements of the

    # pipeline.

    coprocessor.LoadRequestedData(datadescription)


# ------------------------ Processing method ------------------------


def DoCoProcessing(datadescription):

    "Callback to do co-processing for current timestep"

    global coprocessor


    # Update the coprocessor by providing it the newly generated simulation data.

    # If the pipeline hasn't been setup yet, this will setup the pipeline.

    coprocessor.UpdateProducers(datadescription)


    # Write output data, if appropriate.

    coprocessor.WriteData(datadescription);




    # Write image capture (Last arg: rescale lookup table), if appropriate.

    coprocessor.WriteImages(datadescription, rescale_lookuptable=False)


    # Live Visualization, if enabled.

    coprocessor.DoLiveVisualization(datadescription, "localhost", 22222)



From: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>
Date: Thursday, July 30, 2015 at 12:32 PM
To: First name Last name <aeatmon at lanl.gov<mailto:aeatmon at lanl.gov>>
Cc: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: Re: [Paraview] adjusting vertical level setting via paraview python script

Regarding the adding attributes error message, it is likely that the ActiveSource is not an MPAS reader at that point in time.
?GetActiveSource().__class__ should tell your what it is.

Regarding the level setting - what is yourReader.ShowMultilayerView?
The docs indicated a value of 1 makes VerticalLayer immaterial.



David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909<tel:518-881-4909>

On Thu, Jul 30, 2015 at 9:52 AM, Eatmon Jr., Arnold <aeatmon at lanl.gov<mailto:aeatmon at lanl.gov>> wrote:
I?m one of the DSS interns working under Jim Ahrens for the summer. I am using paraviews python script in the HPC and I?m having an issue adjusting an attribute of paraview.simple.netcdfmpasreader ?VerticalLevel?.

I want to adjust it from the default to one and attempted:

paraview.simple.NetCDFMPASreader.VerticalLevel = 1
paraview.simple.NetCDFMPASreader.VerticalLevel = ?1'
And
paraview.simple.GetActiveSource().VerticalLevel = 1

The first two operate with no errors doing nothing in the program and the last returns an error that the class bars adding attributes to prevent errors due to spelling.

How do I adjust the vertical level setting?

Thank you in advance for your assistance.

_______________________________________________
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



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

From ganesh.iitm at gmail.com  Thu Jul 30 17:01:25 2015
From: ganesh.iitm at gmail.com (Ganesh Vijayakumar)
Date: Thu, 30 Jul 2015 21:01:25 +0000
Subject: [Paraview] Reg. paraview using off
In-Reply-To: <CADHSJjB-cAmvTGoFfjR49y0c0WfbCQsw4YTW2Tiehg5reqyg2g@mail.gmail.com>
References: <CAFtK+eubFC-2qodP-4sA66uvknW5d5tbSA7PApWmXypG-joseg@mail.gmail.com>
 <CADHSJjB-cAmvTGoFfjR49y0c0WfbCQsw4YTW2Tiehg5reqyg2g@mail.gmail.com>
Message-ID: <CAFtK+evtZpHF3+sX9=CGDADAFf8b+HZJnVq-8oH+=eEYN7FvOQ@mail.gmail.com>

Thanks all. This is super awesome and now allows me to get real time
updates on the status of simulations instead of wheeling the data out to
some other place.. tarring, scping, untarring.... phew!

ganesh

On Wed, Jul 29, 2015 at 12:00 PM Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> Check this out:
>
> http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D#Configuring_ParaView_for_use_with_OSMesa
>
> You're missing several other flags needed for ParaView to use OSMesa
> e.g. VTK_OPENGL_HAS_OSMESA. Also, your CMakeCache.txt shows that
> OPENGL_gl_LIBRARY, OPENGL_glu_LIBRARY, OPENGL_INCLUDE_DIR are set to
> use system OpenGL. That will cause runtime issues. The Wiki indicates
> the values that these should be set to.
>
> On Tue, Jul 28, 2015 at 11:39 PM, Ganesh Vijayakumar
> <ganesh.iitm at gmail.com> wrote:
> > Hello,
> >
> >   I'm trying to install paraview using off-screen rendering on a
> cluster. I
> > attached my CMakeCache. It configures just fine. However, I'm unable to
> > progress beyond this error during the compile. Could anyone please help?
> > I load the required modules first
> >
> > module load gcc/4.9.2
> > module load cmake/3.1.0
> > module load python/2.7.9
> > module load hdf5/1.8.14
> > export HDF5_ROOT=/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/
> > export
> PYTHON_INCLUDE_DIRS=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/include/
> > export
> > PYTHON_LIBRARY=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/lib/
> libpython2.7.so
> > export
> PYTHON_EXECUTABLE=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/bin/python
> >
> > Then, I configured as
> >
> > ccmake ~/software/ParaView-v4.3.1-source
> >
> -DOSMESA_INCLUDE_DIR:PATH=/storage/home/guv106/software/mesa-10.5.4/include
> >
> -DOSMESA_LIBRARY:FILEPATH=/storage/home/guv106/software/mesa-10.5.4/lib/gallium/libOSMesa.so
> > -DVTK_USE_X:BOOL=OFF  -DVTK_USE_SYSTEM_HDF5:BOOL=ON
> >
> -DPYTHON_INCLUDE_DIRS=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/include/python2.7/
> >
> > The error during the make process is
> >
> > [ 11%] Building CXX object
> >
> VTK/Rendering/OpenGL/CMakeFiles/vtkRenderingOpenGL.dir/vtkOSOpenGLRenderWindow.cxx.o
> > cd
> /storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Rendering/OpenGL
> > && /usr/bin/c++   -DVTK_IN_VTK -DvtkRenderingO
> > penGL_EXPORTS -O3 -DNDEBUG -fPIC
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build
> > -I/storage/home/guv106/software/mes
> > a-10.5.4/include
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Imaging/Hybrid
> > -I/storage/home/guv106/software/
> > ParaView-v4.3.1-source/VTK/Imaging/Hybrid
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/IO/Image
> > -I/storage/ho
> > me/guv106/software/ParaView-v4.3.1-source/VTK/IO/Image
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/Da
> > taModel
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/DataModel
> > -I/storage/home/guv106/software/ParaVi
> > ew-v4.3.1-build/VTK/Common/Math
> > -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/Math
> > -I/storage/home/guv
> > 106/software/ParaView-v4.3.1-build/VTK/Common/Core
> > -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/Core
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/KWSys
> > -I/storage/home/guv106/software/ParaView-v4.3.1-
> > source/VTK/Utilities/KWSys
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/Misc
> > -I/storage/home/guv106/so
> > ftware/ParaView-v4.3.1-source/VTK/Common/Misc
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/System
> -I/s
> > torage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/System
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build
> > /VTK/Common/Transforms
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/Transforms
> > -I/storage/home/guv106
> > /software/ParaView-v4.3.1-build/VTK/Common/ExecutionModel
> > -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Commo
> > n/ExecutionModel
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/DICOMParser
> > -I/storage/home/guv106/so
> > ftware/ParaView-v4.3.1-source/VTK/Utilities/DICOMParser
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/IO/Core
> > -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/IO/Core
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/zlib
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/zlib
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/MetaIO/vtkmetaio
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/MetaIO
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/MetaIO
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/jpeg
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/jpeg
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/png
> > -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/png
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/tiff
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/tiff
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Imaging/Core
> > -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Imaging/Core
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/ParseOGLExt
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/ParseOGLExt
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Rendering/Core
> > -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/Core
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/Color
> > -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/Color
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Extraction
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Extraction
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Core
> > -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Core
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/General
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/General
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/ComputationalGeometry
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/ComputationalGeometry
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Statistics
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Statistics
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Imaging/Fourier
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Imaging/Fourier
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/alglib
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/alglib
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Geometry
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Geometry
> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Sources
> > -I/storage/
> home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Sources
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/EncodeString
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/EncodeString
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Rendering/OpenGL
> >
> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL
> > -fvisibility=hidden -fvisibility-inlines-hidden -o
> > CMakeFiles/vtkRenderingOpenGL.dir/vtkOSOpenGLRenderWindow.cxx.o -c
> >
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx
> >
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:52:
> > error: ?OSMesaContext? does not name a type
> >
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:
> > In constructor
> >
> ?vtkOSOpenGLRenderWindowInternal::vtkOSOpenGLRenderWindowInternal(vtkRenderWindow*)?:
> >
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:64:
> > error: ?class vtkOSOpenGLRenderWindowInternal? has no member named
> > ?OffScreenContextId?
> >
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:
> > In member function ?virtual void
> > vtkOSOpenGLRenderWindow::SetStereoCapableWindow(int)?:
> >
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:128:
> > error: ?class vtkOSOpenGLRenderWindowInternal? has no member named
> > ?OffScreenContextId?
> >
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:
> > In member function ?void
> vtkOSOpenGLRenderWindow::CreateOffScreenWindow(int,
> > int)?:
> >
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:185:
> > error: ?class vtkOSOpenGLRenderWindowInternal? has no member named
> > ?OffScreenContextId?
> >
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:187:
> > error: ?class vtkOSOpenGLRenderWindowInternal? has no member named
> > ?OffScreenContextId?
> >
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:187:
> > error: ?OSMesaCreateContext? was not declared in this scope
> >
> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:
> > In member function ?void
> vtkOSOpenGLRenderWindow::DestroyOffScreenWindow()?:
> >
> >
> > ganesh
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150730/26638eb0/attachment.html>

From dennis_conklin at goodyear.com  Thu Jul 30 14:38:10 2015
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Thu, 30 Jul 2015 18:38:10 +0000
Subject: [Paraview] Is there a way to make Spreadsheet view Text larger?
Message-ID: <SN1PR0701MB2029182F856F62E15E1F70EB9F8B0@SN1PR0701MB2029.namprd07.prod.outlook.com>

Is there a Geezer mode for Spreadsheet view.    I can find no way to zoom or to change font size in Spreadsheet, and these old eyes aren't what they used to be.

Thanks

Dennis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150730/01d4b1f5/attachment.html>

From wascott at sandia.gov  Thu Jul 30 17:13:47 2015
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 30 Jul 2015 21:13:47 +0000
Subject: [Paraview] Geezer mode for Spreadsheet?
Message-ID: <32cb553a799a4aa1971c89539de8a479@ES01AMSNLNT.srn.sandia.gov>

Is there a Geezer mode for the spreadsheet view?  I.e., larger fonts, bold fonts?

Thanks,

Alan

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

From pulido at lanl.gov  Thu Jul 30 17:55:54 2015
From: pulido at lanl.gov (Pulido, Jesus)
Date: Thu, 30 Jul 2015 21:55:54 +0000
Subject: [Paraview] Memory seeking problems in using the xdmf2 reader
In-Reply-To: <CANjZAi8SGrHo32CL4smp30apVXONv9Yy3Pb6g3nfNogy5TuhhQ@mail.gmail.com>
References: <E65EBD9CD7A9004A924D2E7C5ED608D58BA250C8@ECS-EXG-P-MB05.win.lanl.gov>,
 <CANjZAi8SGrHo32CL4smp30apVXONv9Yy3Pb6g3nfNogy5TuhhQ@mail.gmail.com>
Message-ID: <E65EBD9CD7A9004A924D2E7C5ED608D58BA26324@ECS-EXG-P-MB05.win.lanl.gov>

Hi David,

The patch did not work, the file is still not read correctly after the second scalar component.

After applying your patch, I did a bit of debugging myself. I enabled XDMF Debug in the code and found that the seek values are incorrect for scalar fields 3, 4, and 6.
They seem to be stuck at the value 2147483647. On the plus side, it looks like the array size (array size in bytes) is being computed correctly.

Please take a look at the parsed debug log file that I've attached. Maybe the seek value is being malformed somewhere before it reaches XdmfValuesBinary.cxx?

Thanks,
Jesus


________________________________
From: David E DeMarle [dave.demarle at kitware.com]
Sent: Wednesday, July 29, 2015 10:36 PM
To: Pulido, Jesus
Cc: paraview at paraview.org
Subject: Re: [Paraview] Memory seeking problems in using the xdmf2 reader

Would you mind trying this Jesus?

diff --git a/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfValuesBinary.cxx b/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfValuesBinary.cxx
index 04ea0a7..6fe37d0 100644
--- a/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfValuesBinary.cxx
+++ b/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfValuesBinary.cxx
@@ -187,7 +187,7 @@ public:

 size_t XdmfValuesBinary::getSeek(){
     if(this->Seek==NULL)return 0;
-    return static_cast<size_t>(atoi(this->Seek));
+    return static_cast<size_t>(atol(this->Seek));
 }

Once you confirm it fixes it for you too I'll check it in.

Thanks,


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Fri, Jul 24, 2015 at 12:43 PM, Pulido, Jesus <pulido at lanl.gov<mailto:pulido at lanl.gov>> wrote:
Hello,

I have written a custom xmf file used by the xdmf2 reader to properly read in (raw) binary data into Paraview. This normally works but only for small datasets. The file requires the input of a memory "seek" location to start reading the different scalar components of the data. A problem arises when there is a 512^3 dataset, with 5 scalar components that are required to be read in. The first two scalar components are read in correctly, then the next two components receive the error:


ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/IO/Xdmf2/vtkXdmfHeavyData.cxx, line 1128

vtkXdmfReader (0x7f8614672af0): Failed to read attribute data

The 5th component then becomes a duplicate of the 1st component.
What I believe that's happening is that the "seek" value is only being represented as a signed integer, this would explain the memory location rolling from MAX_INT to -MAX_INT, and failing to read in scalar components 3 and 4. Their seek locations fall within this case. By the time the 5th component is read, the seek value may have rolled over back to positive values (seek > 0) and then duplicates the same data as the 1st component.

Is this assumption correct and intended? Is there fix for this or an alternative way around reading large, raw datasets using this format? I'm attaching a sample xmf file

Thank you,
Jesus

_______________________________________________
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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150730/3096c395/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: debug.txt
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150730/3096c395/attachment.txt>

From M.Deij at marin.nl  Fri Jul 31 02:44:42 2015
From: M.Deij at marin.nl (Deij-van Rijswijk, Menno)
Date: Fri, 31 Jul 2015 06:44:42 +0000
Subject: [Paraview] Using SpatioTemporalParallelism plugin in ParaView
In-Reply-To: <CAPHwKk6esyqjhDVVjiQ9+4BDrPjicDs-mjuj4VxOfm_risekTQ@mail.gmail.com>
References: <CAPHwKk6esyqjhDVVjiQ9+4BDrPjicDs-mjuj4VxOfm_risekTQ@mail.gmail.com>
Message-ID: <4d1baa43969a45dba25f2296b993ddb3@MAR190n2.marin.local>

If I?m not mistaken, it should be called like this

xdmf_test_v01xdmf = STP.CreateReader(XDMFReader, '/lustre/cmf/scratch/k/kpai/projects/NeptuneData_2015-07-28/xdmf_test_v01.xdmf')

That is, without the keyword argument fileinfo='<path>'

Best wishes,


Menno


[cid:image20810f.JPG at bd15c35e.4dac0214][cid:imageb1c161.JPG at a28c36d2.4ca583ea]

dr. ir. Menno A. Deij-van Rijswijk


Researcher / Software Engineer


Maritime Simulation & Software Group




MARIN




        2, Haagsteeg

E M.Deij at marin.nl<mailto:M.Deij at marin.nl>       P.O. Box 28     T +31 317 49 39 11
        6700 AA Wageningen      F +31 317 49 32 45
T  +31 317 49 35 06     The Netherlands I  www.marin.nl<http://www.marin.nl>



MARIN news: Co?peratief zonne-energieproject op dak MARIN<http://www.marin.nl/web/News/News-items/Cooperatief-zonneenergieproject-op-dak-MARIN.htm>

This e-mail may be confidential, privileged and/or protected by copyright. If you are not the intended recipient, you should return it to the sender immediately and delete your copy from your system.


From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Krishna Pai
Sent: donderdag 30 juli 2015 21:20
To: paraview at paraview.org
Subject: [Paraview] Using SpatioTemporalParallelism plugin in ParaView

Hi all,
I've been working with spatio-temporal data stored in an xdmf file. I found that ParaView doesn't handle parallel processing of this file well, so I thought I would use the SpatioTemporalParallelism plugin to partition the data better. I chose the Parallel Image Data Writer to write to a .pvti before using the plugin to export state. Once the python script was generated, and I tried running it with pvbatch, I got the following error message:

Traceback (most recent call last):
  File "./yoda.py", line 26, in <module>
    xdmf_test_v01xdmf = STP.CreateReader(XDMFReader, fileinfo='/lustre/cmf/scratch/k/kpai/projects/NeptuneData_2015-07-28/xdmf_test_v01.xdmf')
TypeError: CreateReader() takes exactly 2 non-keyword arguments (1 given)
The file path above is to the xdmf file on a remote machine.
I'm not sure what other arguments need to be given, considering the script was generated by ParaView (maybe I exported state incorrectly?). I would appreciate any help.
Thanks,
Krishna Pai



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/f4b258b5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image20810f.JPG
Type: image/jpeg
Size: 1069 bytes
Desc: image20810f.JPG
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/f4b258b5/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imageb1c161.JPG
Type: image/jpeg
Size: 1622 bytes
Desc: imageb1c161.JPG
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/f4b258b5/attachment-0001.jpe>

From joachim.pouderoux at kitware.com  Fri Jul 31 03:41:24 2015
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Fri, 31 Jul 2015 09:41:24 +0200
Subject: [Paraview] Differences between OpenGL and OpenGL2 versions of
	ParaView
In-Reply-To: <CANjddW2ooLsY9yo+7+-ON9-uRftDmvc0CiMNS1qCy_6bb2-bOw@mail.gmail.com>
References: <CANjddW2ooLsY9yo+7+-ON9-uRftDmvc0CiMNS1qCy_6bb2-bOw@mail.gmail.com>
Message-ID: <CACJ=gTjh6_QEHRAJoUa_0_GC1zb5-vC9Uq6-4TGLS-f5VvxfSw@mail.gmail.com>

Adam,

The color difference can be explained by the default coloring mode
introduced recently (before the git tag version you tested with).
Multiblocks are now automatically colored by blocks. Toggle the Color
Legend and see the coloring array, "vtkBlockColors" is selected wereas in
previous version it was Solid Color I guess.
Regarding the missing pieces, I can tell that with the same git version and
with the OpenGL backend 1 (the old), all pieces are correctly drawn. What
is specific is that this missing blocks (the data has like a global gemetry
block + all the internal pieces) are the last block if the first level
block hierarchy.

Joachim


*Joachim Pouderoux*

*PhD, Technical Expert*
*Kitware SAS <http://www.kitware.fr>*


2015-07-30 22:19 GMT+02:00 Adam Lyon <lyon at fnal.gov>:

> Hi,  I'm trying to use ParaView built with OpenGL2, hoping to see some
> speed improvement when I interact with my visualization. Indeed for a
> complicated geometry I see significant speed up (e.g. ~25 fps with OpenGL2
> vs. 5 fps with regular ParaView). But I also see serious errors in the
> display. I've attached two images of our "g-2 muon storage ring" (never
> mind what it actually is, though it is very cool :-) ..
>
> [image: Inline image 1]
>
> The first, mostly blue image, is from regular ParaView (downloaded Mac
> binary 4.3.1 64 bit)  and is what the ring is supposed to look like. There
> is a color vector selected and I've unchecked "Map scalars" so that the
> colors are "true". And indeed the RGB color values in the vector are what
> is shown on the display.
>
>
> [image: Inline image 2]
> The next image, with a chunk on the left side missing, is from the OpenGL2
> ParaView (Mac built from source 4.3.1-882-gbdceec7 64 bit) configured
> identically as the other ParaView. So it should look identical to the
> mostly blue picture. Along with the missing chunk, you see the colors look
> very wrong. What's even stranger is that the missing chunk is really
> missing - not invisible - the visualization is made of multiblock datasets,
> and right clicking where a structure should be only brings up the link
> camera option.
>
> You can try this yourself -- see
> https://www.dropbox.com/sh/900ocfc90v0w3r6/AACmqz8kVrGPUMnJbpxAFOzBa?dl=0
> . The "gm2ring.zip" file has gm2ring.vtm (with the corresponding gm2ring
> directory) and gm2ring.pvsm to restore my configuration.
>
> I'm looking forward to using the OpenGL2 version when it works better. I
> hope this helps in working out its kinks (or hoping to find out I've built
> or configured something incorrectly). Let me know how I can help!  Thanks!
> -- Adam
> *------*
>
> *Adam L. Lyon*
> *Scientist; Associate Division Head for Systems for Scientific
> Applications*
>
> Scientific Computing Division & Muon g-2 Experiment
> Fermi National Accelerator Laboratory
> 630 840 5522 office
> www.fnal.gov
> lyon at fnal.gov
>
> Connect with us!
> Newsletter <http://www.fnal.gov/pub/today/>  |  Facebook
> <https://www.facebook.com/Fermilab>  |  Twitter
> <https://twitter.com/Fermilab>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/63e84567/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gm2ringsim_opengl2_bad.png
Type: image/png
Size: 16709 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/63e84567/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gm2ringsim_opengl_good.png
Type: image/png
Size: 19431 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/63e84567/attachment-0003.png>

From utkarsh.ayachit at kitware.com  Fri Jul 31 10:16:34 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 31 Jul 2015 10:16:34 -0400
Subject: [Paraview] Reg. paraview using off
In-Reply-To: <CAFtK+evtZpHF3+sX9=CGDADAFf8b+HZJnVq-8oH+=eEYN7FvOQ@mail.gmail.com>
References: <CAFtK+eubFC-2qodP-4sA66uvknW5d5tbSA7PApWmXypG-joseg@mail.gmail.com>
 <CADHSJjB-cAmvTGoFfjR49y0c0WfbCQsw4YTW2Tiehg5reqyg2g@mail.gmail.com>
 <CAFtK+evtZpHF3+sX9=CGDADAFf8b+HZJnVq-8oH+=eEYN7FvOQ@mail.gmail.com>
Message-ID: <CADHSJjAu0_1eNyNm5OHoObxBxNCyxRXkT23CCSS+61qckx1qPQ@mail.gmail.com>

Great! Glad it's working for you now.

On Thu, Jul 30, 2015 at 5:01 PM, Ganesh Vijayakumar <ganesh.iitm at gmail.com>
wrote:

> Thanks all. This is super awesome and now allows me to get real time
> updates on the status of simulations instead of wheeling the data out to
> some other place.. tarring, scping, untarring.... phew!
>
> ganesh
>
> On Wed, Jul 29, 2015 at 12:00 PM Utkarsh Ayachit <
> utkarsh.ayachit at kitware.com> wrote:
>
>> Check this out:
>>
>> http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D#Configuring_ParaView_for_use_with_OSMesa
>>
>> You're missing several other flags needed for ParaView to use OSMesa
>> e.g. VTK_OPENGL_HAS_OSMESA. Also, your CMakeCache.txt shows that
>> OPENGL_gl_LIBRARY, OPENGL_glu_LIBRARY, OPENGL_INCLUDE_DIR are set to
>> use system OpenGL. That will cause runtime issues. The Wiki indicates
>> the values that these should be set to.
>>
>> On Tue, Jul 28, 2015 at 11:39 PM, Ganesh Vijayakumar
>> <ganesh.iitm at gmail.com> wrote:
>> > Hello,
>> >
>> >   I'm trying to install paraview using off-screen rendering on a
>> cluster. I
>> > attached my CMakeCache. It configures just fine. However, I'm unable to
>> > progress beyond this error during the compile. Could anyone please help?
>> > I load the required modules first
>> >
>> > module load gcc/4.9.2
>> > module load cmake/3.1.0
>> > module load python/2.7.9
>> > module load hdf5/1.8.14
>> > export HDF5_ROOT=/opt/aci/sw/gcc/hdf5/1.8.14_gcc-4.9.2/
>> > export
>> PYTHON_INCLUDE_DIRS=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/include/
>> > export
>> > PYTHON_LIBRARY=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/lib/
>> libpython2.7.so
>> > export
>> PYTHON_EXECUTABLE=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/bin/python
>> >
>> > Then, I configured as
>> >
>> > ccmake ~/software/ParaView-v4.3.1-source
>> >
>> -DOSMESA_INCLUDE_DIR:PATH=/storage/home/guv106/software/mesa-10.5.4/include
>> >
>> -DOSMESA_LIBRARY:FILEPATH=/storage/home/guv106/software/mesa-10.5.4/lib/gallium/libOSMesa.so
>> > -DVTK_USE_X:BOOL=OFF  -DVTK_USE_SYSTEM_HDF5:BOOL=ON
>> >
>> -DPYTHON_INCLUDE_DIRS=/opt/aci/sw/python27/2.7.9_gcc-4.9.2-1/include/python2.7/
>> >
>> > The error during the make process is
>> >
>> > [ 11%] Building CXX object
>> >
>> VTK/Rendering/OpenGL/CMakeFiles/vtkRenderingOpenGL.dir/vtkOSOpenGLRenderWindow.cxx.o
>> > cd
>> /storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Rendering/OpenGL
>> > && /usr/bin/c++   -DVTK_IN_VTK -DvtkRenderingO
>> > penGL_EXPORTS -O3 -DNDEBUG -fPIC
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-build
>> > -I/storage/home/guv106/software/mes
>> > a-10.5.4/include
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Imaging/Hybrid
>> > -I/storage/home/guv106/software/
>> > ParaView-v4.3.1-source/VTK/Imaging/Hybrid
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/IO/Image
>> > -I/storage/ho
>> > me/guv106/software/ParaView-v4.3.1-source/VTK/IO/Image
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/Da
>> > taModel
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/DataModel
>> > -I/storage/home/guv106/software/ParaVi
>> > ew-v4.3.1-build/VTK/Common/Math
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/Math
>> > -I/storage/home/guv
>> > 106/software/ParaView-v4.3.1-build/VTK/Common/Core
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/Core
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/KWSys
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-
>> > source/VTK/Utilities/KWSys
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/Misc
>> > -I/storage/home/guv106/so
>> > ftware/ParaView-v4.3.1-source/VTK/Common/Misc
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/System
>> -I/s
>> > torage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/System
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-build
>> > /VTK/Common/Transforms
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/Transforms
>> > -I/storage/home/guv106
>> > /software/ParaView-v4.3.1-build/VTK/Common/ExecutionModel
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Commo
>> > n/ExecutionModel
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/DICOMParser
>> > -I/storage/home/guv106/so
>> > ftware/ParaView-v4.3.1-source/VTK/Utilities/DICOMParser
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/IO/Core
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/IO/Core
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/zlib
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/zlib
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/MetaIO/vtkmetaio
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/MetaIO
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/MetaIO
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/jpeg
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/jpeg
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/png
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/png
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/tiff
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/tiff
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Imaging/Core
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Imaging/Core
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/ParseOGLExt
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/ParseOGLExt
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Rendering/Core
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/Core
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/Color
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/Color
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Extraction
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Extraction
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Core
>> > -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Core
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/General
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/General
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Common/ComputationalGeometry
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Common/ComputationalGeometry
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Statistics
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Statistics
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Imaging/Fourier
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Imaging/Fourier
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/ThirdParty/alglib
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/ThirdParty/alglib
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Geometry
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Geometry
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Filters/Sources
>> > -I/storage/
>> home/guv106/software/ParaView-v4.3.1-source/VTK/Filters/Sources
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Utilities/EncodeString
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Utilities/EncodeString
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-build/VTK/Rendering/OpenGL
>> >
>> -I/storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL
>> > -fvisibility=hidden -fvisibility-inlines-hidden -o
>> > CMakeFiles/vtkRenderingOpenGL.dir/vtkOSOpenGLRenderWindow.cxx.o -c
>> >
>> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx
>> >
>> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:52:
>> > error: ?OSMesaContext? does not name a type
>> >
>> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:
>> > In constructor
>> >
>> ?vtkOSOpenGLRenderWindowInternal::vtkOSOpenGLRenderWindowInternal(vtkRenderWindow*)?:
>> >
>> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:64:
>> > error: ?class vtkOSOpenGLRenderWindowInternal? has no member named
>> > ?OffScreenContextId?
>> >
>> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:
>> > In member function ?virtual void
>> > vtkOSOpenGLRenderWindow::SetStereoCapableWindow(int)?:
>> >
>> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:128:
>> > error: ?class vtkOSOpenGLRenderWindowInternal? has no member named
>> > ?OffScreenContextId?
>> >
>> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:
>> > In member function ?void
>> vtkOSOpenGLRenderWindow::CreateOffScreenWindow(int,
>> > int)?:
>> >
>> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:185:
>> > error: ?class vtkOSOpenGLRenderWindowInternal? has no member named
>> > ?OffScreenContextId?
>> >
>> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:187:
>> > error: ?class vtkOSOpenGLRenderWindowInternal? has no member named
>> > ?OffScreenContextId?
>> >
>> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:187:
>> > error: ?OSMesaCreateContext? was not declared in this scope
>> >
>> /storage/home/guv106/software/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkOSOpenGLRenderWindow.cxx:
>> > In member function ?void
>> vtkOSOpenGLRenderWindow::DestroyOffScreenWindow()?:
>> >
>> >
>> > ganesh
>> >
>> > _______________________________________________
>> > Powered by www.kitware.com
>> >
>> > Visit other Kitware open-source projects at
>> > http://www.kitware.com/opensource/opensource.html
>> >
>> > Please keep messages on-topic and check the ParaView Wiki at:
>> > http://paraview.org/Wiki/ParaView
>> >
>> > Search the list archives at: http://markmail.org/search/?q=ParaView
>> >
>> > Follow this link to subscribe/unsubscribe:
>> > http://public.kitware.com/mailman/listinfo/paraview
>> >
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/e44dd94f/attachment.html>

From lyon at fnal.gov  Fri Jul 31 11:53:43 2015
From: lyon at fnal.gov (Adam Lyon)
Date: Fri, 31 Jul 2015 10:53:43 -0500
Subject: [Paraview] Differences between OpenGL and OpenGL2 versions of
	ParaView
In-Reply-To: <df1a83ae294e4325a80c0301532c640d@MAIL05V-CAS02.fnal.gov>
References: <CANjddW2ooLsY9yo+7+-ON9-uRftDmvc0CiMNS1qCy_6bb2-bOw@mail.gmail.com>
 <df1a83ae294e4325a80c0301532c640d@MAIL05V-CAS02.fnal.gov>
Message-ID: <CANjddW1QKkhTtKJNmE13ikwVm=7ZYRZgN6DVB_RGd=77Hw+uSQ@mail.gmail.com>

Hi Joachim - Yes, I noticed that the default color is now vtkBlockColors.
However I changed that to the "color" vector in my data and that change was
not honored by the program. Thanks, Adam

*------*

*Adam L. Lyon*
*Scientist; Associate Division Head for Systems for Scientific Applications*

Scientific Computing Division & Muon g-2 Experiment
Fermi National Accelerator Laboratory
630 840 5522 office
www.fnal.gov
lyon at fnal.gov

Connect with us!
Newsletter <http://www.fnal.gov/pub/today/>  |  Facebook
<https://www.facebook.com/Fermilab>  |  Twitter
<https://twitter.com/Fermilab>

On Fri, Jul 31, 2015 at 2:41 AM, Joachim Pouderoux <
joachim.pouderoux at kitware.com> wrote:

> Adam,
>
> The color difference can be explained by the default coloring mode
> introduced recently (before the git tag version you tested with).
> Multiblocks are now automatically colored by blocks. Toggle the Color
> Legend and see the coloring array, "vtkBlockColors" is selected wereas in
> previous version it was Solid Color I guess.
> Regarding the missing pieces, I can tell that with the same git version
> and with the OpenGL backend 1 (the old), all pieces are correctly drawn.
> What is specific is that this missing blocks (the data has like a global
> gemetry block + all the internal pieces) are the last block if the first
> level block hierarchy.
>
> Joachim
>
>
> *Joachim Pouderoux*
>
> *PhD, Technical Expert*
> *Kitware SAS <http://www.kitware.fr>*
>
>
> 2015-07-30 22:19 GMT+02:00 Adam Lyon <lyon at fnal.gov>:
>
>> Hi,  I'm trying to use ParaView built with OpenGL2, hoping to see some
>> speed improvement when I interact with my visualization. Indeed for a
>> complicated geometry I see significant speed up (e.g. ~25 fps with OpenGL2
>> vs. 5 fps with regular ParaView). But I also see serious errors in the
>> display. I've attached two images of our "g-2 muon storage ring" (never
>> mind what it actually is, though it is very cool :-) ..
>>
>> [image: Inline image 1]
>>
>> The first, mostly blue image, is from regular ParaView (downloaded Mac
>> binary 4.3.1 64 bit)  and is what the ring is supposed to look like. There
>> is a color vector selected and I've unchecked "Map scalars" so that the
>> colors are "true". And indeed the RGB color values in the vector are what
>> is shown on the display.
>>
>>
>> [image: Inline image 2]
>> The next image, with a chunk on the left side missing, is from the
>> OpenGL2 ParaView (Mac built from source 4.3.1-882-gbdceec7 64 bit)
>> configured identically as the other ParaView. So it should look identical
>> to the mostly blue picture. Along with the missing chunk, you see the
>> colors look very wrong. What's even stranger is that the missing chunk is
>> really missing - not invisible - the visualization is made of multiblock
>> datasets, and right clicking where a structure should be only brings up the
>> link camera option.
>>
>> You can try this yourself -- see
>> https://www.dropbox.com/sh/900ocfc90v0w3r6/AACmqz8kVrGPUMnJbpxAFOzBa?dl=0
>> . The "gm2ring.zip" file has gm2ring.vtm (with the corresponding gm2ring
>> directory) and gm2ring.pvsm to restore my configuration.
>>
>> I'm looking forward to using the OpenGL2 version when it works better. I
>> hope this helps in working out its kinks (or hoping to find out I've built
>> or configured something incorrectly). Let me know how I can help!  Thanks!
>> -- Adam
>> *------*
>>
>> *Adam L. Lyon*
>> *Scientist; Associate Division Head for Systems for Scientific
>> Applications*
>>
>> Scientific Computing Division & Muon g-2 Experiment
>> Fermi National Accelerator Laboratory
>> 630 840 5522 office
>> www.fnal.gov
>> lyon at fnal.gov
>>
>> Connect with us!
>> Newsletter <http://www.fnal.gov/pub/today/>  |  Facebook
>> <https://www.facebook.com/Fermilab>  |  Twitter
>> <https://twitter.com/Fermilab>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/6c08853e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gm2ringsim_opengl_good.png
Type: image/png
Size: 19431 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/6c08853e/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gm2ringsim_opengl2_bad.png
Type: image/png
Size: 16709 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/6c08853e/attachment-0001.png>

From krishnapai09 at gmail.com  Fri Jul 31 12:30:01 2015
From: krishnapai09 at gmail.com (Krishna Pai)
Date: Fri, 31 Jul 2015 12:30:01 -0400
Subject: [Paraview] Using SpatioTemporalParallelism plugin in ParaView
In-Reply-To: <4d1baa43969a45dba25f2296b993ddb3@MAR190n2.marin.local>
References: <CAPHwKk6esyqjhDVVjiQ9+4BDrPjicDs-mjuj4VxOfm_risekTQ@mail.gmail.com>
 <4d1baa43969a45dba25f2296b993ddb3@MAR190n2.marin.local>
Message-ID: <CAPHwKk4M-rHJ2R+FOBwv4B5T1e2hbyQHgCYRSDLfb+t1eVfsKQ@mail.gmail.com>

Thanks for the reply, Menno. I tried doing that before, but I got a
segmentation fault due to a missing filename, and I'm not sure where in the
function call for CreateReader I would put a file name or what file name I
should use. I ended up getting the following error message along with 2
slight variations on it, followed by the segmentation fault message:

ERROR: In
/lustre/cmf/scratch/k/kpai/projects/ParaView-v4.3.1-source/VTK/IO/Xdmf2/vtkXdmfReader.cxx,
line 189
vtkXdmfReader (0x48997f0): File name not set

ERROR: In
/lustre/cmf/scratch/k/kpai/projects/ParaView-v4.3.1-source/VTK/Common/ExecutionModel/vtkExecutive.cxx,
line 784
vtkPVCompositeDataPipeline (0x489fe20): Algorithm
vtkFileSeriesReader(0x489de90) returned failure for request: vtkInformation
(0x4891ab0)
  Debug: Off
  Modified Time: 165325
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_DATA_OBJECT
  FORWARD_DIRECTION: 0
  ALGORITHM_AFTER_FORWARD: 1

Unless there's a bug in the plugin, I don't think this should be happening
if I input the required information correctly. Here's what I did:

1. I opened the xdmf file in ParaView and added a ParallelImageDataWriter
to it in the pipeline. In the File Name field of ParallelImageDataWriter, I
entered output%t.pvti. I expect the output files to be in this form if I
understand what ParallelImageDataWriter does correctly.

2. I exported state from the SpatioTemporal menu. As my xdmf file was the
only file in the pipeline, I simply added it.

3. Next, as the xdmf file gets its data from binary files in a separate
directory, I entered the file path to those files in the file location
field (i.e. <path>/NeptuneData_2015-07-28/0000/f*.bin). I think this is
where the plugin will get its data (this may be where the problem is).

4. Finally, I chose not to output images, entered a time compartment size
of 4, and chose a location to save the generated python script.

Obviously, the generated script contained the fileinfo=<path> argument in
the CreateReader call among other issues, and I just want to understand
what's going wrong. As always, any help is appreciated.

Thanks,
Krishna Pai


On Fri, Jul 31, 2015 at 2:44 AM, Deij-van Rijswijk, Menno <M.Deij at marin.nl>
wrote:

> If I?m not mistaken, it should be called like this
>
>
>
> xdmf_test_v01xdmf = STP.CreateReader(XDMFReader,
> '/lustre/cmf/scratch/k/kpai/projects/NeptuneData_2015-07-28/xdmf_test_v01.xdmf')
>
>
>
> That is, without the keyword argument fileinfo='<path>'
>
>
>
> Best wishes,
>
>
>
>
>
> Menno
>
>
>
> dr. ir. Menno A. Deij-van Rijswijk
>
> Researcher / Software Engineer
> Maritime Simulation & Software Group
>
>
>
> *MARIN*
>
>
> 2, Haagsteeg E M.Deij at marin.nl P.O. Box 28 T +31 317 49 39 11 6700 AA
> Wageningen F +31 317 49 32 45 T  +31 317 49 35 06 The Netherlands I
> www.marin.nl
>
>
>
> MARIN news: Co?peratief zonne-energieproject op dak MARIN
> <http://www.marin.nl/web/News/News-items/Cooperatief-zonneenergieproject-op-dak-MARIN.htm>
>
> This e-mail may be confidential, privileged and/or protected by copyright.
> If you are not the intended recipient, you should return it to the sender
> immediately and delete your copy from your system.
>
>
>
> *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *Krishna
> Pai
> *Sent:* donderdag 30 juli 2015 21:20
> *To:* paraview at paraview.org
> *Subject:* [Paraview] Using SpatioTemporalParallelism plugin in ParaView
>
>
>
> Hi all,
>
> I've been working with spatio-temporal data stored in an xdmf file. I
> found that ParaView doesn't handle parallel processing of this file well,
> so I thought I would use the SpatioTemporalParallelism plugin to partition
> the data better. I chose the Parallel Image Data Writer to write to a .pvti
> before using the plugin to export state. Once the python script was
> generated, and I tried running it with pvbatch, I got the following error
> message:
>
>
> Traceback (most recent call last):
>   File "./yoda.py", line 26, in <module>
>     xdmf_test_v01xdmf = STP.CreateReader(XDMFReader,
> fileinfo='/lustre/cmf/scratch/k/kpai/projects/NeptuneData_2015-07-28/xdmf_test_v01.xdmf')
> TypeError: CreateReader() takes exactly 2 non-keyword arguments (1 given)
>
> The file path above is to the xdmf file on a remote machine.
>
> I'm not sure what other arguments need to be given, considering the script
> was generated by ParaView (maybe I exported state incorrectly?). I would
> appreciate any help.
>
> Thanks,
>
> Krishna Pai
>
>
>
>


-- 
          1   1
          1   /
          1 1                     1
          1 1      _    0   _   1 _       _      _
          1   \   1  1  1  (     1   7   1  7    _)
          1    !  1      1   )    1   1   1  1   {_}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/86c61407/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imageb1c161.JPG
Type: image/jpeg
Size: 1622 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/86c61407/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image20810f.JPG
Type: image/jpeg
Size: 1069 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/86c61407/attachment-0001.jpe>

From bruce.david.jones at gmail.com  Fri Jul 31 12:34:49 2015
From: bruce.david.jones at gmail.com (Bruce Jones)
Date: Fri, 31 Jul 2015 16:34:49 +0000
Subject: [Paraview] Error building superbuild VS2010
Message-ID: <CAEc4V-ZjcqgdVpR9Cf=Yz4EL2gwXY6v=pqrKy5NpGwgh0nzPvA@mail.gmail.com>

Hi,

I am trying to build the superbuild for x64 on windows. I have configured
everything with cmake (i have only selected ENABLE_paraview and ENABLE_qt)
and am trying to do a release build. The build fails with,

7>  CMake Error at VTK/CMake/vtkModuleAPI.cmake:53 (message):
7>    No such module: "vtkCommonDataModel"

Any suggestions?

Cheers,
Bruce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/a9351c79/attachment.html>

From krishnapai09 at gmail.com  Fri Jul 31 15:07:28 2015
From: krishnapai09 at gmail.com (Krishna Pai)
Date: Fri, 31 Jul 2015 15:07:28 -0400
Subject: [Paraview] Using SpatioTemporalParallelism plugin in ParaView
In-Reply-To: <CAPHwKk4M-rHJ2R+FOBwv4B5T1e2hbyQHgCYRSDLfb+t1eVfsKQ@mail.gmail.com>
References: <CAPHwKk6esyqjhDVVjiQ9+4BDrPjicDs-mjuj4VxOfm_risekTQ@mail.gmail.com>
 <4d1baa43969a45dba25f2296b993ddb3@MAR190n2.marin.local>
 <CAPHwKk4M-rHJ2R+FOBwv4B5T1e2hbyQHgCYRSDLfb+t1eVfsKQ@mail.gmail.com>
Message-ID: <CAPHwKk58_jqcigsrUZF5khVYj9YO112gVOG7g8YL3vDLNwbgsQ@mail.gmail.com>

I've attached the xdmf file and the generated python script for
clarification.

On Fri, Jul 31, 2015 at 12:30 PM, Krishna Pai <krishnapai09 at gmail.com>
wrote:

> Thanks for the reply, Menno. I tried doing that before, but I got a
> segmentation fault due to a missing filename, and I'm not sure where in the
> function call for CreateReader I would put a file name or what file name I
> should use. I ended up getting the following error message along with 2
> slight variations on it, followed by the segmentation fault message:
>
> ERROR: In
> /lustre/cmf/scratch/k/kpai/projects/ParaView-v4.3.1-source/VTK/IO/Xdmf2/vtkXdmfReader.cxx,
> line 189
> vtkXdmfReader (0x48997f0): File name not set
>
> ERROR: In
> /lustre/cmf/scratch/k/kpai/projects/ParaView-v4.3.1-source/VTK/Common/ExecutionModel/vtkExecutive.cxx,
> line 784
> vtkPVCompositeDataPipeline (0x489fe20): Algorithm
> vtkFileSeriesReader(0x489de90) returned failure for request: vtkInformation
> (0x4891ab0)
>   Debug: Off
>   Modified Time: 165325
>   Reference Count: 1
>   Registered Events: (none)
>   Request: REQUEST_DATA_OBJECT
>   FORWARD_DIRECTION: 0
>   ALGORITHM_AFTER_FORWARD: 1
>
> Unless there's a bug in the plugin, I don't think this should be happening
> if I input the required information correctly. Here's what I did:
>
> 1. I opened the xdmf file in ParaView and added a ParallelImageDataWriter
> to it in the pipeline. In the File Name field of ParallelImageDataWriter, I
> entered output%t.pvti. I expect the output files to be in this form if I
> understand what ParallelImageDataWriter does correctly.
>
> 2. I exported state from the SpatioTemporal menu. As my xdmf file was the
> only file in the pipeline, I simply added it.
>
> 3. Next, as the xdmf file gets its data from binary files in a separate
> directory, I entered the file path to those files in the file location
> field (i.e. <path>/NeptuneData_2015-07-28/0000/f*.bin). I think this is
> where the plugin will get its data (this may be where the problem is).
>
> 4. Finally, I chose not to output images, entered a time compartment size
> of 4, and chose a location to save the generated python script.
>
> Obviously, the generated script contained the fileinfo=<path> argument in
> the CreateReader call among other issues, and I just want to understand
> what's going wrong. As always, any help is appreciated.
>
> Thanks,
> Krishna Pai
>
>
> On Fri, Jul 31, 2015 at 2:44 AM, Deij-van Rijswijk, Menno <M.Deij at marin.nl
> > wrote:
>
>> If I?m not mistaken, it should be called like this
>>
>>
>>
>> xdmf_test_v01xdmf = STP.CreateReader(XDMFReader,
>> '/lustre/cmf/scratch/k/kpai/projects/NeptuneData_2015-07-28/xdmf_test_v01.xdmf')
>>
>>
>>
>> That is, without the keyword argument fileinfo='<path>'
>>
>>
>>
>> Best wishes,
>>
>>
>>
>>
>>
>> Menno
>>
>>
>>
>> dr. ir. Menno A. Deij-van Rijswijk
>>
>> Researcher / Software Engineer
>> Maritime Simulation & Software Group
>>
>>
>>
>> *MARIN*
>>
>>
>> 2, Haagsteeg E M.Deij at marin.nl P.O. Box 28 T +31 317 49 39 11 6700 AA
>> Wageningen F +31 317 49 32 45 T  +31 317 49 35 06 The Netherlands I
>> www.marin.nl
>>
>>
>>
>> MARIN news: Co?peratief zonne-energieproject op dak MARIN
>> <http://www.marin.nl/web/News/News-items/Cooperatief-zonneenergieproject-op-dak-MARIN.htm>
>>
>> This e-mail may be confidential, privileged and/or protected by
>> copyright. If you are not the intended recipient, you should return it to
>> the sender immediately and delete your copy from your system.
>>
>>
>>
>> *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *Krishna
>> Pai
>> *Sent:* donderdag 30 juli 2015 21:20
>> *To:* paraview at paraview.org
>> *Subject:* [Paraview] Using SpatioTemporalParallelism plugin in ParaView
>>
>>
>>
>> Hi all,
>>
>> I've been working with spatio-temporal data stored in an xdmf file. I
>> found that ParaView doesn't handle parallel processing of this file well,
>> so I thought I would use the SpatioTemporalParallelism plugin to partition
>> the data better. I chose the Parallel Image Data Writer to write to a .pvti
>> before using the plugin to export state. Once the python script was
>> generated, and I tried running it with pvbatch, I got the following error
>> message:
>>
>>
>> Traceback (most recent call last):
>>   File "./yoda.py", line 26, in <module>
>>     xdmf_test_v01xdmf = STP.CreateReader(XDMFReader,
>> fileinfo='/lustre/cmf/scratch/k/kpai/projects/NeptuneData_2015-07-28/xdmf_test_v01.xdmf')
>> TypeError: CreateReader() takes exactly 2 non-keyword arguments (1 given)
>>
>> The file path above is to the xdmf file on a remote machine.
>>
>> I'm not sure what other arguments need to be given, considering the
>> script was generated by ParaView (maybe I exported state incorrectly?). I
>> would appreciate any help.
>>
>> Thanks,
>>
>> Krishna Pai
>>
>>
>>
>>
>
>
> --
>           1   1
>           1   /
>           1 1                     1
>           1 1      _    0   _   1 _       _      _
>           1   \   1  1  1  (     1   7   1  7    _)
>           1    !  1      1   )    1   1   1  1   {_}
>



-- 
          1   1
          1   /
          1 1                     1
          1 1      _    0   _   1 _       _      _
          1   \   1  1  1  (     1   7   1  7    _)
          1    !  1      1   )    1   1   1  1   {_}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/5c15d69c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image20810f.JPG
Type: image/jpeg
Size: 1069 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/5c15d69c/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imageb1c161.JPG
Type: image/jpeg
Size: 1622 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/5c15d69c/attachment-0001.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: yoda.py
Type: text/x-python
Size: 1453 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/5c15d69c/attachment.py>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xdmf_test_v01.xdmf
Type: application/octet-stream
Size: 14876 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/5c15d69c/attachment.obj>

From ben.boeckel at kitware.com  Fri Jul 31 16:59:09 2015
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Fri, 31 Jul 2015 16:59:09 -0400
Subject: [Paraview] Error building superbuild VS2010
In-Reply-To: <CAEc4V-ZjcqgdVpR9Cf=Yz4EL2gwXY6v=pqrKy5NpGwgh0nzPvA@mail.gmail.com>
References: <CAEc4V-ZjcqgdVpR9Cf=Yz4EL2gwXY6v=pqrKy5NpGwgh0nzPvA@mail.gmail.com>
Message-ID: <20150731205909.GC6556@megas.kitware.com>

On Fri, Jul 31, 2015 at 16:34:49 +0000, Bruce Jones wrote:
> I am trying to build the superbuild for x64 on windows. I have configured
> everything with cmake (i have only selected ENABLE_paraview and ENABLE_qt)
> and am trying to do a release build. The build fails with,
> 
> 7>  CMake Error at VTK/CMake/vtkModuleAPI.cmake:53 (message):
> 7>    No such module: "vtkCommonDataModel"
> 
> Any suggestions?

What CMake generator did you use? The superbuild is only tested with
Ninja on Windows:

    C:\> REM Open a VS2010 x64 Command Tools Prompt
    C:\> cmake -GNinja ../path/to/superbuild/source
    C:\> REM Edit configuration in cmake-gui
    C:\> ninja

Ninja is available from:

    https://martine.github.io/ninja

if you do not have it already.

--Ben

From chrisneal at ufl.edu  Fri Jul 31 19:24:17 2015
From: chrisneal at ufl.edu (Neal,Christopher R)
Date: Fri, 31 Jul 2015 23:24:17 +0000
Subject: [Paraview] Extract the x,y,z extents of a domain in Paraview
Message-ID: <BY2PR0801MB1573F874C6AD71A890EB0AC5BA8A0@BY2PR0801MB1573.namprd08.prod.outlook.com>

Hi all,


I have noticed that  the max and min values of the x, y, and z coordinates of all of the vertices are displayed at the bottom of the 'Information' tab when I load a computational grid file into Paraview.  Is there a way to extract this information via a Python call to the Paraview library?

Thank you,


Christopher R. Neal
Graduate Student
Center for Compressible Multiphase Turbulence
Mechanical and Aerospace Engineering Department
University of Florida
Cell: (863)-697-1958
E-mail:  chrisneal at ufl.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150731/df697597/attachment.html>

From jfavre at cscs.ch  Mon Jul 20 06:26:06 2015
From: jfavre at cscs.ch (Favre  Jean)
Date: Mon, 20 Jul 2015 10:26:06 -0000
Subject: [Paraview] Transforming a spherical slice into a map projection
In-Reply-To: <CAK3vnGf8e_AHmruBokgujpBCqyA44_A1eX2dwxNSEN0WvkdjUw@mail.gmail.com>
References: <CAK3vnGc2pHaxZXhGtto8JzOo6Nu_UL84+rEMES6z5-x6Ei+=bw@mail.gmail.com>
 <CADHSJjAZmDV+7QY7VqAEMxWtumyDK08fGyjpWT8T-JwVY8y4og@mail.gmail.com>,
 <CAK3vnGf8e_AHmruBokgujpBCqyA44_A1eX2dwxNSEN0WvkdjUw@mail.gmail.com>
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F6841F1E77B@MBX211.d.ethz.ch>

Here is a state file to try, and the snapshot I created.

The sampling resolution is set to be 128x64. You can change that to anything you want, in the ProgrammableSource. Two objects are created (a sphere and a plane). The sphere is used to resample the volume. The plane is used, to "flatten" the data copied over from the sphere.

Details on how to use the Programmable Sources and Filters are in the PV Guide (Chapter 13)

let me know if this works.
-----------------
Jean M. Favre
Swiss National Supercomputing Center
CH-6900 Lugano
Switzerland

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/f34c7c78/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Sphere+Plane.png
Type: image/png
Size: 179649 bytes
Desc: Sphere+Plane.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/f34c7c78/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: solution-spherical-sampling.pvsm
Type: application/octet-stream
Size: 462210 bytes
Desc: solution-spherical-sampling.pvsm
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150720/f34c7c78/attachment-0001.obj>

From aashish.chaudhary at kitware.com  Fri Jul 17 11:48:33 2015
From: aashish.chaudhary at kitware.com (Aashish Chaudhary)
Date: Fri, 17 Jul 2015 15:48:33 -0000
Subject: [Paraview] [vtk-developers] GPU volume rendering failure on
 Intel HD XXXX/Iris, Windows and recent drivers
In-Reply-To: <CY1PR0701MB16131DE5669DA94BF51225A1D8980@CY1PR0701MB1613.namprd07.prod.outlook.com>
References: <CAC9gB0ArB3vVBbcQnk-52ymwKYpBuk7ZLRXJD8-RevF7NRGg6w@mail.gmail.com>
 <CAEw35Z9KtCZn2MBYaom=8AYocGLJMypMfSf0hZ3m1pUkfhzdXA@mail.gmail.com>
 <CAC9gB0B=OJ4YBQa=hs=3J=X-4nfEQ3VBqyUSgQG-=LDJSSA6Bg@mail.gmail.com>
 <CY1PR0701MB16131DE5669DA94BF51225A1D8980@CY1PR0701MB1613.namprd07.prod.outlook.com>
Message-ID: <CAEw35Z-3JcFUo8Pd_wSmpBAs+qDnQo-5Nn99wySxCcHYZwMGVQ@mail.gmail.com>

Hi Andras,

Please find the patchs attached. If you run into issues let me know. I
should mention that apply these patches at your discretion as I have not
done enough testing to ensure the quality of the patches but the test
passed last time I applied them.



On Fri, Jul 17, 2015 at 11:40 AM, Andras Lasso <lasso at queensu.ca> wrote:

>  Please share the patch publicly, we would need it for some of our
> projects, too. Thank you!
>
>
>
> Andras
>
>
>
> *From:* vtk-developers [mailto:vtk-developers-bounces at vtk.org] *On Behalf
> Of *Simon ESNEAULT
> *Sent:* Friday, July 17, 2015 11:35 AM
> *To:* Aashish Chaudhary
> *Cc:* VTK Developers; vtkusers at vtk.org; ParaView list
> *Subject:* Re: [vtk-developers] [Paraview] GPU volume rendering failure
> on Intel HD XXXX/Iris, Windows and recent drivers
>
>
>
> Dear Aashish,
>
>
>
> Thank you very much for you answer.
>
> Yes you are right, we are waiting for a new VTK release that defaults to
> the new OpenGL2 backend, for safety and because a change of VTK version
> requires a lot of extra work with our current framework... But the green
> dashboard indeed looks really promising, and we will probably make the move
> as soon as it's ready !
>
> Meanwhile, I would be really glad if you could send me the patch that
> solves this issue with the old backend, or guide me through the needed
> modification to make it work.
>
> Thanks again
>
> Simon
>
>
>
> 2015-07-17 16:22 GMT+02:00 Aashish Chaudhary <
> aashish.chaudhary at kitware.com>:
>
>  Dear Simon,
>
>
>
> On Fri, Jul 17, 2015 at 4:43 AM, Simon ESNEAULT <simon.esneault at gmail.com>
> wrote:
>
>  Hi All,
>
> We're experiencing GPU volume rendering failure on a lot (maybe all ?)
> Intel HD windows system with up to date drivers.
>
>
> This is reproducible in Paraview or with the GPURenderDemo example from
> VTK, just load a volume and try to render the volume... Here is a result
> image from paraview on a Dell Latitude E7450 (Intel HD 5500 inside), with
> GPU rendering [1] and the same volume with CPU VR rendering [2].
> Interestingly, the volume rendering used to work with drivers older or
> equal to the version 10.18.10.3496 [3]. As a work around, we ask our
> customers to downgrade their driver version to this one, and they're
> enjoying smooth GPU rendering. But this driver is quite old and does not
> support recent chipset...
>
> I've built and tested the GPURenderDemo with the brand new OpenGL2 backend
> on an affected machine and of course it does work out of the box
> (congratulations for this amazing work !).
>
>  Great!
>
>
>
>  But our application is FDA/CE marked and we need to wait that this new
> backend is completely ready for prime time. So for now, we have to stick
> with VTK 6.1 ...
>
>
>
> Most of the tests are passing for OpenGL2 (
> https://open.cdash.org/index.php?project=VTK) on most of the dashboards
> (various configurations etc) but it is a moving target just like VTK itself
> is a moving target. I guess you are waiting for a VTK release that defaults
> to OpenGL2 as oppose to OpenGL?
>
>
> Anyone has any clue ? They're some warning that pop up from paraview
> related to the extension "gl_version_1_2" that could not be loaded, not
> sure if that could be related ? Following this thread [4] and the fix
> proposed, I've tried to replace
>
> /*****************/
>
> extensions->LoadExtension("GL_VERSION_1_2")
>
> /*****************/
>
> by
>
> /*****************/
>
> extensions->LoadExtension("GL_EXT_texture3D");
> extensions->LoadExtension( "GL_ARB_texture_non_power_of_two" );
>
> /*****************/
>
> in the vtkOpenGLGPUVolumeRayCastMapper.cxx, The warning disappears but
> there is still no volume rendering (tested with GPURenderDemo). Maybe it
> needs some others extensions ?
>
>
>
> Yes, there is a patch and I can send it to you. I have to talk to folks
> here if we can fix the old mapper with those changes but as of now it is
> not in the plan.
>
>
>
>
> Should I fill a bug in paraview, vtk ? Are there any plan to maintain and
> maybe fix this for the old backend ?
>
>
>
> - Aashish
>
>
>
>
> Thanks,
> --
>
> ------------------------------------------------------------------
> Simon Esneault
>
> Rennes, France
> ------------------------------------------------------------------
>
>
> [1] http://picpaste.com/pics/Paraview-4-3-1-GPU-VR_fail.1437122217.PNG
>
> [2] http://picpaste.com/pics/Paraview-4-3-1-CPU-VR_win.1437122267.PNG
>
> [3] https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23339
> [4] http://public.kitware.com/pipermail/vtkusers/2014-April/083584.html
>
>
> _______________________________________________
> 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
>
>
>
>
>
> --
>
>
>
> *| Aashish Chaudhary | Technical Leader          | Kitware Inc.
> *
>
> *| http://www.kitware.com/company/team/chaudhary.html
> <http://www.kitware.com/company/team/chaudhary.html>*
>
>
>
>
>
> --
>
> ------------------------------------------------------------------
> Simon Esneault
>
> Rennes, France
> ------------------------------------------------------------------
>



-- 



*| Aashish Chaudhary | Technical Leader         | Kitware Inc.            *
*| http://www.kitware.com/company/team/chaudhary.html
<http://www.kitware.com/company/team/chaudhary.html>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150717/ac709971/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vtkOpenGLVolumeTextureMapper3D.cxx
Type: text/x-c++src
Size: 70251 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150717/ac709971/attachment-0002.cxx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vtkgl.cxx
Type: text/x-c++src
Size: 573322 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150717/ac709971/attachment-0003.cxx>

From sevensam at udel.edu  Fri Jul  3 05:57:25 2015
From: sevensam at udel.edu (Jesse Samluk)
Date: Fri, 03 Jul 2015 09:57:25 -0000
Subject: [Paraview] Custom animation help?
Message-ID: <3EA27BD7-25EE-4A60-8229-64ABE18836AC@udel.edu>

Greetings all,

   I?m trying to make an animation in Paraview. I took a stab at it before with Paraview, but I recall it as being tedious. Maybe I can get some pointers from the experts.

  So, the attached imaged is a cube view of the electromagnetic response over sea ice. What Im trying to do with this animation is two things:

  1.) Move the horizontal slice and Y-Z vertical slice (the slice without the tubes) up and down, and side to side, respectively, such that as if you selected the particular slide in the Pipeline browser, you could drag the slice in question and move it manually to see the different responses. Therefore I?m trying to automate it.

  2.) Rotate it about the z-axis 5 degrees (to about 180) at each iteration and return, then rotate it 5 degrees at each iteration about the y-axis (till about 45 degrees) and return. These rotations will occur while ?action item" 1 is happening.

   Any thoughts/suggestions?

    Thanks!
    Jesse
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/0f1e4e6b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: YZPlaneInitialForParaview.tiff
Type: image/tiff
Size: 781630 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/0f1e4e6b/attachment-0001.tiff>

From aka at alphanet.ch  Wed Jul  8 15:54:54 2015
From: aka at alphanet.ch (A. Kapetanovic)
Date: Wed, 08 Jul 2015 19:54:54 -0000
Subject: [Paraview] Impossible to see a movement.
In-Reply-To: <CADHSJjBqUBn7yScdubZkM1v4+WWi3AwegXyjuTJFuT9LjN22XA@mail.gmail.com>
References: <20150708074214.ED383124F2D5@shakotay.alphanet.ch>
 <CADHSJjBqUBn7yScdubZkM1v4+WWi3AwegXyjuTJFuT9LjN22XA@mail.gmail.com>
Message-ID: <559D7FFA.5030301@alphanet.ch>

An embedded and charset-unspecified text was scrubbed...
Name: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150708/82a43b19/attachment-0001.ksh>
-------------- next part --------------
Hi,

Thanks for your reply.

Of course I have data to share. The rmed result comressed file is too 
big (35 MB), so I send here the hdf and comm files, you only need to 
compute the (3) meshes and to run the simulation to have this rmed file.

Say me if you need something else, I hope all is clear enough like this   :)

Amel


Le 08. 07. 15 15:44, Utkarsh Ayachit a ?crit :
> Do you have a sample dataset to share? That'll make this easier.
>
> Typically, movement comes from one of the following:
> 1. Readers: the reader itself translates the points in the grid as time
> changes
> 2. Filters: if the grid doesn't change but has attributes that indicate
> the displacement, one can apply a filter to transform the grid using
> those displacement vectors.
>
> Utkarsh
>
> On Wed, Jul 8, 2015 at 3:59 AM <aka at alphanet.ch
> <mailto:aka at alphanet.ch>> wrote:
>
>     Hi,
>
>     I am using Paraview with Salome-Meca + Code_Aster and I have e little
>     problem : impossible to see the movement of a part that is moving.
>
>     In fact the simulation is very simple : I have 2 cylinders, one is
>     fixed by
>     one face and the other have a movement on a face. The simulation
>     converges
>     and when I open the mmed or rmed file (result) with Paraview,
>     impossible to
>     see any movement even if I clic "play".
>
>     Simply nothing happens.
>
>     Can please someone help me ?
>
>     Best regards,
>
>     Amka
>     _______________________________________________
>     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
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: defang-0.binary
Type: application/binary
Size: 2248940 bytes
Desc: renamed/protected to defang-0.binary
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150708/82a43b19/attachment-0001.bin>
-------------- next part --------------
DEBUT();

#Materials_______________________________________________________________________
Mater = DEFI_MATERIAU( ELAS = _F( E = 200.0E9, NU = 0.3));

#Mesh__________________________________________________________________________
Mesh = LIRE_MAILLAGE( FORMAT = 'MED');

Mesh = MODI_MAILLAGE( reuse        = Mesh,
                      MAILLAGE     = Mesh,
                      ORIE_PEAU_3D = _F( GROUP_MA = ('m1ct', 'm2mct')));

ChamMatr = AFFE_MATERIAU( MAILLAGE = Mesh,
                          AFFE     = ( _F( TOUT  = 'OUI',
                                           MATER = Mater)));

#Model__________________________________________________________________________
Model = AFFE_MODELE( MAILLAGE = Mesh,
                     AFFE     = _F( TOUT         = 'OUI',
                                    PHENOMENE    = 'MECANIQUE',
                                    MODELISATION = '3D'));

#BCs____________________________________________________________________________
CharMec1 = AFFE_CHAR_MECA( MODELE   = Model,
                           DDL_IMPO = ( _F(GROUP_MA = 'm2mref',
                                           LIAISON  = 'ENCASTRE')));

CharMec2 = AFFE_CHAR_MECA( MODELE   = Model,
                           DDL_IMPO = _F( GROUP_MA = 'm1ref',
                                          DX = 0.0, DY = 0.0, DZ = -3 ));

petiteF = AFFE_CHAR_MECA ( MODELE = Model,
                           FORCE_FACE =  _F( GROUP_MA = 'm1bout', FZ = 1 ));
                                   
fmul = DEFI_FONCTION( NOM_PARA = 'INST', VALE = ( 0.0, 0.0, 1.0, 1.0));
                                                     
CharCont = DEFI_CONTACT ( MODELE      = Model,
                          FORMULATION = 'CONTINUE',
                          ZONE        = _F( GROUP_MA_MAIT = 'm1ct' ,
                                            GROUP_MA_ESCL = 'm2mct',)
                         );                 

#Solve__________________________________________________________________________
Listr8 = DEFI_LIST_REEL( DEBUT      = 0.0,
                         INTERVALLE = _F( JUSQU_A = 1.0,
                                          PAS     = 0.05 ));

Result = STAT_NON_LINE( MODELE = Model,
                    CHAM_MATER = ChamMatr,  
                    EXCIT = ( _F(CHARGE     = CharMec1),
                              _F(CHARGE     = petiteF),
                              _F( CHARGE    = CharMec2,
                                  FONC_MULT = fmul)),
                    CONTACT   = CharCont,                 
                    COMP_ELAS = _F( RELATION  = 'ELAS'), 
                    INCREMENT = _F( LIST_INST = Listr8),
                    NEWTON    = _F( MATRICE   = 'TANGENTE',
                                    REAC_ITER = 1,),
                    CONVERGENCE = _F( RESI_GLOB_RELA = 0.0001,
                                      ITER_GLOB_MAXI = 30),
                    );

#Results________________________________________________________________________
Result = CALC_CHAMP( reuse = Result, RESULTAT = Result,
                  CRITERES = 'SIEQ_ELNO');

IMPR_RESU( FORMAT = 'MED',
          RESU = _F( MAILLAGE = Mesh,
                  RESULTAT = Result));
                
#End____________________________________________________________________________
FIN();