From robcoorens at gmail.com Sun Aug 2 11:30:57 2015 From: robcoorens at gmail.com (Rob Coorens) Date: Sun, 2 Aug 2015 17:30:57 +0200 Subject: [Paraview] scalars and vectors Message-ID: Dear All, I am new to paraview and cant work out the following(which is essential to my thesis project). I have two datasets, one with vectors and one with scalars. I want to create glyphs that are scaled and oriented by the vector data and coloured by the scalar data. I grouped my datasets and then in glyphs i set my scale mode to vectors and colouring to scalars. However i think i also see zero vectors from my scalar dataset created by paraview. How can i remove these. Because they interfere with my visualization. Any help would be great!! kindest Regards Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: From sergi.mateo.bellido at gmail.com Sun Aug 2 12:41:13 2015 From: sergi.mateo.bellido at gmail.com (Sergi Mateo Bellido) Date: Sun, 02 Aug 2015 18:41:13 +0200 Subject: [Paraview] [BUG] segfault playing a simulation In-Reply-To: <55B20445.7060809@gmail.com> References: <55895735.2030202@gmail.com> <559381DE.5030504@gmail.com> <559422EF.3070304@gmail.com> <55A0E2AE.5050101@gmail.com> <55A9056C.2000101@gmail.com> <55A90F76.8000804@gmail.com> <55B20445.7060809@gmail.com> Message-ID: <55BE4829.5030209@gmail.com> Hi, After a few hours debugging ParaView's code I think that I finally found the bug! :) The problem is that the meaning of the piece extent changes depending on if the piece has the whole dimensions or only a portion of them. For example, imagine that we have the following *.pvti file: In this case, the dimensions of the pieces are: 1st piece -> [0..200], [0..200], [0..101) 2nd piece -> [0..200], [0..200], [101..200] Note that the last dimension range of the 1st piece doesn't include the 101 value which is included in the 2nd piece. The issue here is that the code is not taking into account this when it's computing the dimensions of the current piece. In file VTK/IO/XML/vtkXMLPStructuredDataReader.cxx:155 we have the next call to 'ComputePointDimensions' function: this->ComputePointDimensions(this->SubExtent, this->SubPointDimensions); I printed the values of 'this->SubExtent' and they were the same values specified in the Piece Extent field: (gdb) p SubExtent $1 = {0, 200, 0, 200, 0, 101} For these values, the 'ComputePointDimensions' function, which is defined in VTK/IO/XML/vtkXMLReader.cxx:916, computed the next dimensions: (gdb) p this->SubPointDimensions $2 = {201, 201, 102} How these values are computed is very simple: upper_bound - lower_bound + 1. Note that the value of the third dimension is wrong: it should be 101 instead of 102. Finally, the segfault is produced in the 'CopySubExtent' function, which is defined in VTK/IO/XML/vtkXMLPStructuredDataReader.cxx:342, because SubPointDimensions information is used to copy the regions and we are doing an extra copy (loop defined in 371 line). Could you confirm me this bug? Best regards, Sergi Mateo PS1: Source references are related to the last version of ParaView's source published in your webpage: http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.3&type=source&os=all&downloadFile=ParaView-v4.3.1-source.tar.gz PS2: You can reproduce this bug using one of the examples that I sent you in my previous emails. On 07/24/2015 11:24 AM, Sergi Mateo Bellido wrote: > 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 >>>> >>> > 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 >>>>> >>>> > 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 >>>>>> >>>>> > 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 >>>>>>> >>>>>> > 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&, bool) [(libQtGui.so.4) ???:-1] >>>>>>> 0x7f54d019ca94 : ??? [(???) ???:-1] >>>>>>> 0x7f54d019b877 : >>>>>>> QApplication::x11ProcessEvent(_XEvent*) >>>>>>> [(libQtGui.so.4) ???:-1] >>>>>>> 0x7f54d01c4805 : ??? [(???) ???:-1] >>>>>>> 0x7f54cfa7f375 : >>>>>>> QEventLoop::processEvents(QFlags) >>>>>>> [(libQtCore.so.4) ???:-1] >>>>>>> 0x7f54cfa7f748 : >>>>>>> QEventLoop::exec(QFlags) >>>>>>> [(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: From joachim.pouderoux at kitware.com Mon Aug 3 03:06:42 2015 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Mon, 3 Aug 2015 09:06:42 +0200 Subject: [Paraview] Extract the x,y,z extents of a domain in Paraview In-Reply-To: References: Message-ID: Christopher, Fetching the bounds of a source in Python is as simple as: >>> mySource.GetDataInformation().GetBounds() The vtkPVDataInformation object returned by GetDataInformation() contains many other information about the source like: - DataSetType - MemorySize - PolygonCount - NumberOfPoints - NumberOfCels etc. Regards, *Joachim Pouderoux* *PhD, Technical Expert* *Kitware SAS * 2015-08-01 1:24 GMT+02:00 Neal,Christopher R : > 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 > > _______________________________________________ > 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: From antech777 at gmail.com Mon Aug 3 04:46:09 2015 From: antech777 at gmail.com (Andrew) Date: Mon, 3 Aug 2015 11:46:09 +0300 Subject: [Paraview] IntegrateVariables filter (add variables) In-Reply-To: References: Message-ID: Hello. Thanks for solution. I tried ExtractBlock filter and it works OK (I able to use Calculator and IntegrateVariables then) but only for volume (Fluid Domain in my case), not for boundaries. I understand that it's not a ParaView problem because it's related to variable sets that CodeSaturne implemets for volumes and surfaces (boundaries). It just does not write velocity components and other needed variables into boundary blocks, only into Fluid Domain block. Is this a way to extract layer of cells *adjacent to boundary* by boundary (block) name in ParaView, or I need to "dig" in methods to force CodeSaturne to output additional variables for boundaries? I tried different output formats in CodeSaturne but it did not solve the problem. Thanks for your attension. -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.Deij at marin.nl Mon Aug 3 04:48:09 2015 From: M.Deij at marin.nl (Deij-van Rijswijk, Menno) Date: Mon, 3 Aug 2015 08:48:09 +0000 Subject: [Paraview] [Catalyst] multi-block names are not written to file Message-ID: Hi, I?m trying to set up a co-processing pipeline by supplying it with a multi-block dataset, of which the individual unstructured grids have names. TL;DR: the block names are not written to XML files when using a Python co-processing pipeline. In detail: The block names are supplied like so /// vtkInformation* md = multiBlockGrid->GetMetaData(static_cast(0)); if (md) { md->Set(vtkCompositeDataSet::NAME(), "Interior"); } /// The grid is added as a producer with the name "grid". Then, in the Python pipeline, I simply write the full grid using the following code: /// grid = coprocessor.CreateProducer( datadescription, "grid" ) ParallelMultiBlockDataSetWriter1 = coprocessor.CreateWriter( XMLMultiBlockDataWriter, "fullgrid_%t.vtm", 100 ) /// This writes the fullgrid_0.vtm file, directory and each block in a separate vtu file. All is good, except that the block names that were set are not written in the file in the "name" attribute. I have tried to write an XML file directly using XMLMultiBlockDataWriter, but that did not work due to the implementation of a mapped data array which has no implementation for NewIterator(). Weird - how does the Python pipeline write the file? I don't know, but it works. To still check the names having been set, I emulate the first few steps of the XMLMultiBlockDataWriter, to see if the block names come through like so: /// vtkSmartPointer iter; iter.TakeReference( vtkDataObjectTree::SafeDownCast(multiBlockGrid)->NewTreeIterator()); iter->VisitOnlyLeavesOff(); iter->TraverseSubTreeOff(); iter->SkipEmptyNodesOff(); int index = 0; int RetVal = 0; for (iter->InitTraversal(); !iter->IsDoneWithTraversal(); iter->GoToNextItem(), index++) { vtkDataObject* curDO = iter->GetCurrentDataObject(); const char *name = NULL; if (iter->HasCurrentMetaData()) { name = iter->GetCurrentMetaData()->Get(vtkCompositeDataSet::NAME()); cout << "Name found by pseudo-write code: " << (name ? name : "NULL") << endl; } else { cout << "No metadata found on iterator" << endl; } } /// And this clearly shows that the names are found as they are written to stdout. So, the question is: how can I get the Python co-processing pipeline to write the block names? Thanks and best wishes, Menno dr. ir. Menno A. Deij-van Rijswijk Researcher / Software Engineer Maritime Simulation & Software Group E mailto:M.Deij at marin.nl T +31 317 49 35 06 MARIN 2, Haagsteeg, P.O. Box 28, 6700 AA Wageningen, The Netherlands T +31 317 49 39 11, F +31 317 49 32 45, I www.marin.nl From zhz1993622 at 163.com Mon Aug 3 04:48:27 2015 From: zhz1993622 at 163.com (=?GBK?B?1ty649ba?=) Date: Mon, 3 Aug 2015 16:48:27 +0800 (CST) Subject: [Paraview] FullScreen and No Boraders Message-ID: <1d8a719b.e40d.14ef2bf692e.Coremail.zhz1993622@163.com> I want to ask some question about VTK. Now I want to create a renderwindow without borders and full of screen . I write code like this: vtkSmartPointer sphereSource = vtkSmartPointer::New(); vtkSmartPointer mapper = vtkSmartPointer::New(); mapper->SetInputConnection(sphereSource->GetOutputPort()); vtkSmartPointer actor = vtkSmartPointer::New(); actor->SetMapper(mapper); vtkSmartPointer renderer = vtkSmartPointer::New(); vtkSmartPointer renderWindow = vtkSmartPointer::New(); renderWindow->AddRenderer(renderer); vtkSmartPointer renderWindowInteractor = vtkSmartPointer::New(); renderWindowInteractor->SetRenderWindow(renderWindow); renderer->AddActor(actor); renderWindow->BordersOff(); renderWindow->SetFullScreen(true); renderWindow->Render(); renderWindowInteractor->Start(); But when I run this program . The renderwindow also have borders. How can I do to make the renderwindow without borders . Thank you for your help. zhz -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Aug 3 07:55:19 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 3 Aug 2015 07:55:19 -0400 Subject: [Paraview] FullScreen and No Boraders In-Reply-To: <1d8a719b.e40d.14ef2bf692e.Coremail.zhz1993622@163.com> References: <1d8a719b.e40d.14ef2bf692e.Coremail.zhz1993622@163.com> Message-ID: > renderWindow->BordersOff(); > renderWindow->SetFullScreen(true); That should have done the trick. Try moving this code to right after the RenderWIndow is created i.e. after vtkSmartPointer::New(); (more specifically, before the RenderWindowInteractor is setup). If I remember correctly, the setting up of the interactor does affect the render window state. Utkarsh On Mon, Aug 3, 2015 at 4:48 AM, ??? wrote: > > I want to ask some question about VTK. Now I want to create a > renderwindow without borders and full of screen . I write code like this: > vtkSmartPointer sphereSource = > vtkSmartPointer::New(); > > vtkSmartPointer mapper = > vtkSmartPointer::New(); > mapper->SetInputConnection(sphereSource->GetOutputPort()); > > vtkSmartPointer actor = > vtkSmartPointer::New(); > actor->SetMapper(mapper); > > vtkSmartPointer renderer = > vtkSmartPointer::New(); > vtkSmartPointer renderWindow = > vtkSmartPointer::New(); > renderWindow->AddRenderer(renderer); > vtkSmartPointer renderWindowInteractor = > vtkSmartPointer::New(); > renderWindowInteractor->SetRenderWindow(renderWindow); > > renderer->AddActor(actor); > > > renderWindow->Render(); > renderWindowInteractor->Start(); > > But when I run this program . The renderwindow also have borders. > How can I do to make the renderwindow without borders . Thank you for your > help. > > zhz > > > > _______________________________________________ > 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 andy.bauer at kitware.com Mon Aug 3 11:28:15 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 3 Aug 2015 11:28:15 -0400 Subject: [Paraview] [Catalyst] multi-block names are not written to file In-Reply-To: References: Message-ID: Hi, This appears to be a bug in VTK. I have a potential fix at https://gitlab.kitware.com/acbauer/vtk/blob/parallelmultiblockdatawriter_write_block_names/IO/ParallelXML/vtkXMLPMultiBlockDataWriter.cxx. You can track the fix at https://gitlab.kitware.com/vtk/vtk/merge_requests/471. Thanks for reporting this. Cheers, Andy On Mon, Aug 3, 2015 at 4:48 AM, Deij-van Rijswijk, Menno wrote: > Hi, > > I?m trying to set up a co-processing pipeline by supplying it with a > multi-block dataset, of which the individual unstructured grids have names. > > TL;DR: the block names are not written to XML files when using a Python > co-processing pipeline. > > > In detail: > The block names are supplied like so > > /// > vtkInformation* md = > multiBlockGrid->GetMetaData(static_cast(0)); > if (md) > { > md->Set(vtkCompositeDataSet::NAME(), "Interior"); > } > /// > > The grid is added as a producer with the name "grid". Then, in the Python > pipeline, I simply write the full grid using the following code: > > /// > grid = coprocessor.CreateProducer( datadescription, "grid" ) > ParallelMultiBlockDataSetWriter1 = coprocessor.CreateWriter( > XMLMultiBlockDataWriter, "fullgrid_%t.vtm", 100 ) > /// > > This writes the fullgrid_0.vtm file, directory and each block in a > separate vtu file. All is good, except that the block names that were set > are not written in the file in the "name" attribute. > > I have tried to write an XML file directly using XMLMultiBlockDataWriter, > but that did not work due to the implementation of a mapped data array > which has no implementation for NewIterator(). Weird - how does the Python > pipeline write the file? I don't know, but it works. > > To still check the names having been set, I emulate the first few steps of > the XMLMultiBlockDataWriter, to see if the block names come through like so: > > /// > vtkSmartPointer iter; > iter.TakeReference( > vtkDataObjectTree::SafeDownCast(multiBlockGrid)->NewTreeIterator()); > iter->VisitOnlyLeavesOff(); > iter->TraverseSubTreeOff(); > iter->SkipEmptyNodesOff(); > > int index = 0; > int RetVal = 0; > for (iter->InitTraversal(); !iter->IsDoneWithTraversal(); > iter->GoToNextItem(), index++) > { > vtkDataObject* curDO = iter->GetCurrentDataObject(); > const char *name = NULL; > if (iter->HasCurrentMetaData()) > { > name = iter->GetCurrentMetaData()->Get(vtkCompositeDataSet::NAME()); > cout << "Name found by pseudo-write code: " << (name ? name : "NULL") << > endl; > } > else > { > cout << "No metadata found on iterator" << endl; > } > } > /// > > And this clearly shows that the names are found as they are written to > stdout. > > So, the question is: how can I get the Python co-processing pipeline to > write the block names? > > Thanks and best wishes, > > > Menno > > > dr. ir. Menno A. Deij-van Rijswijk > Researcher / Software Engineer > Maritime Simulation & Software Group > E mailto:M.Deij at marin.nl > T +31 317 49 35 06 > > > MARIN > 2, Haagsteeg, P.O. Box 28, 6700 AA Wageningen, The Netherlands > T +31 317 49 39 11, F +31 317 49 32 45, I www.marin.nl > > _______________________________________________ > 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: From chrisneal at ufl.edu Mon Aug 3 11:59:42 2015 From: chrisneal at ufl.edu (Neal,Christopher R) Date: Mon, 3 Aug 2015 15:59:42 +0000 Subject: [Paraview] Extract the x,y,z extents of a domain in Paraview In-Reply-To: References: , Message-ID: Thanks Joachim! Do you also happen to know how to obtain the list of plotting variables once a data set has been loaded into Paraview? I would like to get something like, ['Pressure','Density',Velocity']. 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 ________________________________ From: Joachim Pouderoux Sent: Monday, August 3, 2015 3:06 AM To: Neal,Christopher R Cc: paraview at paraview.org Subject: Re: [Paraview] Extract the x,y,z extents of a domain in Paraview Christopher, Fetching the bounds of a source in Python is as simple as: >>> mySource.GetDataInformation().GetBounds() The vtkPVDataInformation object returned by GetDataInformation() contains many other information about the source like: - DataSetType - MemorySize - PolygonCount - NumberOfPoints - NumberOfCels etc. Regards, Joachim Pouderoux PhD, Technical Expert Kitware SAS 2015-08-01 1:24 GMT+02:00 Neal,Christopher R >: 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 _______________________________________________ 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: From dave.demarle at kitware.com Mon Aug 3 12:20:01 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Mon, 3 Aug 2015 12:20:01 -0400 Subject: [Paraview] adjusting vertical level setting via paraview python script In-Reply-To: References: Message-ID: Andy Bauer just explained it to me. He'll get back to you soon with a detailed explanation and hints about how to get what you want done. Meanwhile, what is tripping us up is that MPAS's catalyst adaptor is not the same thing as ParaViews MPAS reader. The reader has the SetVerticalLevel(int) method, but the adaptor probably has an entirely different method for doing that. I don't know firsthand what that method is so we'll have to wait for his response. 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 4:20 PM, Eatmon Jr., Arnold wrote: > # 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 > Date: Thursday, July 30, 2015 at 1:45 PM > To: First name Last name > 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 > 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 >> >> >> # 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 >> Date: Thursday, July 30, 2015 at 12:32 PM >> To: First name Last name >> Cc: "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 >> 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: From andy.bauer at kitware.com Mon Aug 3 13:33:14 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 3 Aug 2015 13:33:14 -0400 Subject: [Paraview] adjusting vertical level setting via paraview python script In-Reply-To: References: Message-ID: Hi, Dave is correct in that the reader's output needs to match what the adaptor is producing and in this case the MPAS NetCDF reader does not match what the adaptor provides to Catalyst. The way to get around this is to run Catalyst with a sample Python script that outputs the full data set that the adaptor provides. For MPAS this is slightly more complex because it provides several outputs, 10 in fact, depending on how the scientists want the data (e.g. spherical vs. projected, primal vs. dual grid, single level vs. multiple levels) for what they're trying to do. The attached script can be used to write out all 10 of these outputs which is done every 5th output (this can be changed by changing the outputfrequency value). The general workflow would be to run MPAS with this script for a small amount of time steps (maybe also with a smaller input data set). Then use those outputs to generate the Catalyst script that you want from the GUI. If this is a bit unclear, I'd recommend going through the Catalyst User's Guide ( http://www.paraview.org/files/catalyst/docs/ParaViewCatalystUsersGuide_v2.pdf) for more details. Regards, Andy On Mon, Aug 3, 2015 at 12:20 PM, David E DeMarle wrote: > Andy Bauer just explained it to me. He'll get back to you soon with a > detailed explanation and hints about how to get what you want done. > > Meanwhile, what is tripping us up is that MPAS's catalyst adaptor is not > the same thing as ParaViews MPAS reader. The reader has the > SetVerticalLevel(int) method, but the adaptor probably has an entirely > different method for doing that. > > I don't know firsthand what that method is so we'll have to wait for his > response. > > > > > > 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 4:20 PM, Eatmon Jr., Arnold > wrote: > >> # 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 >> Date: Thursday, July 30, 2015 at 1:45 PM >> To: First name Last name >> 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 >> 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 >>> >>> >>> # 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 >>> Date: Thursday, July 30, 2015 at 12:32 PM >>> To: First name Last name >>> Cc: "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 >>> 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: mpasgridwriter.py Type: text/x-python Size: 4374 bytes Desc: not available URL: From lyon at fnal.gov Mon Aug 3 14:59:55 2015 From: lyon at fnal.gov (Adam Lyon) Date: Mon, 3 Aug 2015 13:59:55 -0500 Subject: [Paraview] Differences between OpenGL and OpenGL2 versions of ParaView In-Reply-To: <3b80307dd0184a7081060df719e33861@MAIL06V-CAS04.fnal.gov> References: <3b80307dd0184a7081060df719e33861@MAIL06V-CAS04.fnal.gov> Message-ID: Hi Joachim, Do you want me to send in a bug report for these problems? I assume there's no work-around that I can do to make things work. Using OpenGL2 is quite a bit faster, so I'm hoping a fix can come out soon. 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 | Facebook | Twitter On Fri, Jul 31, 2015 at 10:53 AM, Adam L Lyon wrote: > 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 | Facebook > | Twitter > > > 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 * >> >> >> 2015-07-30 22:19 GMT+02:00 Adam Lyon : >> >>> 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 | Facebook >>> | Twitter >>> >>> >>> _______________________________________________ >>> 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: gm2ringsim_opengl_good.png Type: image/png Size: 19431 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: gm2ringsim_opengl2_bad.png Type: image/png Size: 16709 bytes Desc: not available URL: From andy.bauer at kitware.com Mon Aug 3 15:14:15 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 3 Aug 2015 15:14:15 -0400 Subject: [Paraview] adjusting vertical level setting via paraview python script In-Reply-To: References: Message-ID: Hi, Please reply to everyone so that anyone that wants to follow along with the conversation can. Did you get a chance to look through the Catalyst User's Guide? For MPAS, the names of the adaptor outputs are: 'X_Y_NLAYER-primal', 'X_Y_NLAYER-dual', 'X_Y_Z_1LAYER-primal', 'X_Y_Z_1LAYER-dual', 'X_Y_Z_NLAYER-primal', 'X_Y_Z_NLAYER-dual', 'LON_LAT_1LAYER-primal', 'LON_LAT_1LAYER-dual', 'LON_LAT_NLAYER-primal', 'LON_LAT_NLAYER-dual' The files that you want are the ones provided by Catalyst and not the ones that MPAS natively writes out. The Catalyst files all should be written out with pvtu extensions (e.g. X_Y_NLAYER-primal_1.pvtu). The MPAS native output is the .nc file. The other error that you're getting is that you have an active Python trace when going through the Catalyst export wizard and that trace needs to be stopped. Regards, Andy On Mon, Aug 3, 2015 at 3:00 PM, Eatmon Jr., Arnold wrote: > Alright, in order of what I did just to be clear, I uploaded the attached > python to my directory, soft linked it to mpas.py, ran the simulation for > a single timestep, and got a file in my output folder labeled > output.0015-01-01_00.00.00.nc. I took that file and opened it in the > Paraview desktop gui. In paraview with coprocessing enabled (Tools > Plugin > Manager > under catalyst option, hit load), I made the adjustment to the > vertical level and then exported the state (CoProcessing > Export State). I > do not get a python script as an output, I get the error > > "Cannot generate Python state when tracing is active." > > RuntimeError: Cannot generate Python state when tracing is active. > > > > > > From: Andy Bauer > Date: Monday, August 3, 2015 at 11:33 AM > To: David E DeMarle > Cc: First name Last name , "Patchett, John M" < > patchett at lanl.gov>, "paraview at paraview.org" > > Subject: Re: [Paraview] adjusting vertical level setting via paraview > python script > > Hi, > > Dave is correct in that the reader's output needs to match what the > adaptor is producing and in this case the MPAS NetCDF reader does not match > what the adaptor provides to Catalyst. The way to get around this is to run > Catalyst with a sample Python script that outputs the full data set that > the adaptor provides. For MPAS this is slightly more complex because it > provides several outputs, 10 in fact, depending on how the scientists want > the data (e.g. spherical vs. projected, primal vs. dual grid, single level > vs. multiple levels) for what they're trying to do. The attached script can > be used to write out all 10 of these outputs which is done every 5th output > (this can be changed by changing the outputfrequency value). > > The general workflow would be to run MPAS with this script for a small > amount of time steps (maybe also with a smaller input data set). Then use > those outputs to generate the Catalyst script that you want from the GUI. > > If this is a bit unclear, I'd recommend going through the Catalyst User's > Guide ( > http://www.paraview.org/files/catalyst/docs/ParaViewCatalystUsersGuide_v2.pdf) > for more details. > > Regards, > Andy > > On Mon, Aug 3, 2015 at 12:20 PM, David E DeMarle > wrote: > >> Andy Bauer just explained it to me. He'll get back to you soon with a >> detailed explanation and hints about how to get what you want done. >> >> Meanwhile, what is tripping us up is that MPAS's catalyst adaptor is not >> the same thing as ParaViews MPAS reader. The reader has the >> SetVerticalLevel(int) method, but the adaptor probably has an entirely >> different method for doing that. >> >> I don't know firsthand what that method is so we'll have to wait for his >> response. >> >> >> >> >> >> 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 4:20 PM, Eatmon Jr., Arnold >> wrote: >> >>> # 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 >>> Date: Thursday, July 30, 2015 at 1:45 PM >>> To: First name Last name >>> 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 >>> 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 >>>> >>>> >>>> # 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 >>>> Date: Thursday, July 30, 2015 at 12:32 PM >>>> To: First name Last name >>>> Cc: "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 >>>> 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: From aeatmon at lanl.gov Mon Aug 3 15:56:51 2015 From: aeatmon at lanl.gov (Eatmon Jr., Arnold) Date: Mon, 3 Aug 2015 19:56:51 +0000 Subject: [Paraview] adjusting vertical level setting via paraview python script In-Reply-To: References: Message-ID: Oh, my mistake I didn?t understand the instructions. I will run it again to get .pvtu output, however in my previous scripts that generate VTK output there was an issue where the currently released 4.3.1 version of Paraview could not open the files due to a back compatability issue. I had a developers head on an old machine that could open them, however I do not any longer and the source code is no longer available on the paraview downloads page. Will v4.3.1 be able to open these .pvtu output files? From: Andy Bauer > Date: Monday, August 3, 2015 at 1:14 PM To: First name Last name >, "Patchett, John M" >, Dave DeMarle >, "paraview at paraview.org" > Subject: Re: [Paraview] adjusting vertical level setting via paraview python script Hi, Please reply to everyone so that anyone that wants to follow along with the conversation can. Did you get a chance to look through the Catalyst User's Guide? For MPAS, the names of the adaptor outputs are: 'X_Y_NLAYER-primal', 'X_Y_NLAYER-dual', 'X_Y_Z_1LAYER-primal', 'X_Y_Z_1LAYER-dual', 'X_Y_Z_NLAYER-primal', 'X_Y_Z_NLAYER-dual', 'LON_LAT_1LAYER-primal', 'LON_LAT_1LAYER-dual', 'LON_LAT_NLAYER-primal', 'LON_LAT_NLAYER-dual' The files that you want are the ones provided by Catalyst and not the ones that MPAS natively writes out. The Catalyst files all should be written out with pvtu extensions (e.g. X_Y_NLAYER-primal_1.pvtu). The MPAS native output is the .nc file. The other error that you're getting is that you have an active Python trace when going through the Catalyst export wizard and that trace needs to be stopped. Regards, Andy On Mon, Aug 3, 2015 at 3:00 PM, Eatmon Jr., Arnold > wrote: Alright, in order of what I did just to be clear, I uploaded the attached python to my directory, soft linked it to mpas.py, ran the simulation for a single timestep, and got a file in my output folder labeled output.0015-01-01_00.00.00.nc. I took that file and opened it in the Paraview desktop gui. In paraview with coprocessing enabled (Tools > Plugin Manager > under catalyst option, hit load), I made the adjustment to the vertical level and then exported the state (CoProcessing > Export State). I do not get a python script as an output, I get the error "Cannot generate Python state when tracing is active." RuntimeError: Cannot generate Python state when tracing is active. From: Andy Bauer > Date: Monday, August 3, 2015 at 11:33 AM To: David E DeMarle > Cc: First name Last name >, "Patchett, John M" >, "paraview at paraview.org" > Subject: Re: [Paraview] adjusting vertical level setting via paraview python script Hi, Dave is correct in that the reader's output needs to match what the adaptor is producing and in this case the MPAS NetCDF reader does not match what the adaptor provides to Catalyst. The way to get around this is to run Catalyst with a sample Python script that outputs the full data set that the adaptor provides. For MPAS this is slightly more complex because it provides several outputs, 10 in fact, depending on how the scientists want the data (e.g. spherical vs. projected, primal vs. dual grid, single level vs. multiple levels) for what they're trying to do. The attached script can be used to write out all 10 of these outputs which is done every 5th output (this can be changed by changing the outputfrequency value). The general workflow would be to run MPAS with this script for a small amount of time steps (maybe also with a smaller input data set). Then use those outputs to generate the Catalyst script that you want from the GUI. If this is a bit unclear, I'd recommend going through the Catalyst User's Guide (http://www.paraview.org/files/catalyst/docs/ParaViewCatalystUsersGuide_v2.pdf) for more details. Regards, Andy On Mon, Aug 3, 2015 at 12:20 PM, David E DeMarle > wrote: Andy Bauer just explained it to me. He'll get back to you soon with a detailed explanation and hints about how to get what you want done. Meanwhile, what is tripping us up is that MPAS's catalyst adaptor is not the same thing as ParaViews MPAS reader. The reader has the SetVerticalLevel(int) method, but the adaptor probably has an entirely different method for doing that. I don't know firsthand what that method is so we'll have to wait for his response. 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 4:20 PM, Eatmon Jr., Arnold > wrote: # 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 > Date: Thursday, July 30, 2015 at 1:45 PM To: First name Last name > 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 > 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 # 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 > Date: Thursday, July 30, 2015 at 12:32 PM To: First name Last name > Cc: "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 > 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: From andy.bauer at kitware.com Mon Aug 3 16:03:15 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 3 Aug 2015 16:03:15 -0400 Subject: [Paraview] adjusting vertical level setting via paraview python script In-Reply-To: References: Message-ID: I think the changes to the XML formats were done prior to PV 4.3.1 but am not certain. When making the scripts in the GUI you'll want to use the same version of ParaView though that is linked with MPAS to make sure the generated Python scripts are compatible. On Mon, Aug 3, 2015 at 3:56 PM, Eatmon Jr., Arnold wrote: > Oh, my mistake I didn?t understand the instructions. I will run it again > to get .pvtu output, however in my previous scripts that generate VTK > output there was an issue where the currently released 4.3.1 version of > Paraview could not open the files due to a back compatability issue. I had > a developers head on an old machine that could open them, however I do not > any longer and the source code is no longer available on the paraview > downloads page. Will v4.3.1 be able to open these .pvtu output files? > > From: Andy Bauer > Date: Monday, August 3, 2015 at 1:14 PM > To: First name Last name , "Patchett, John M" < > patchett at lanl.gov>, Dave DeMarle , " > paraview at paraview.org" > > Subject: Re: [Paraview] adjusting vertical level setting via paraview > python script > > Hi, > > Please reply to everyone so that anyone that wants to follow along with > the conversation can. > > Did you get a chance to look through the Catalyst User's Guide? > > For MPAS, the names of the adaptor outputs are: > 'X_Y_NLAYER-primal', > 'X_Y_NLAYER-dual', > 'X_Y_Z_1LAYER-primal', > 'X_Y_Z_1LAYER-dual', > 'X_Y_Z_NLAYER-primal', > 'X_Y_Z_NLAYER-dual', > 'LON_LAT_1LAYER-primal', > 'LON_LAT_1LAYER-dual', > 'LON_LAT_NLAYER-primal', > 'LON_LAT_NLAYER-dual' > > The files that you want are the ones provided by Catalyst and not the ones > that MPAS natively writes out. The Catalyst files all should be written out > with pvtu extensions (e.g. X_Y_NLAYER-primal_1.pvtu). The MPAS native > output is the .nc file. > > The other error that you're getting is that you have an active Python > trace when going through the Catalyst export wizard and that trace needs to > be stopped. > > Regards, > Andy > > On Mon, Aug 3, 2015 at 3:00 PM, Eatmon Jr., Arnold > wrote: > >> Alright, in order of what I did just to be clear, I uploaded the attached >> python to my directory, soft linked it to mpas.py, ran the simulation >> for a single timestep, and got a file in my output folder labeled >> output.0015-01-01_00.00.00.nc. I took that file and opened it in the >> Paraview desktop gui. In paraview with coprocessing enabled (Tools > Plugin >> Manager > under catalyst option, hit load), I made the adjustment to the >> vertical level and then exported the state (CoProcessing > Export State). I >> do not get a python script as an output, I get the error >> >> "Cannot generate Python state when tracing is active." >> >> RuntimeError: Cannot generate Python state when tracing is active. >> >> >> >> >> >> From: Andy Bauer >> Date: Monday, August 3, 2015 at 11:33 AM >> To: David E DeMarle >> Cc: First name Last name , "Patchett, John M" < >> patchett at lanl.gov>, "paraview at paraview.org" >> >> Subject: Re: [Paraview] adjusting vertical level setting via paraview >> python script >> >> Hi, >> >> Dave is correct in that the reader's output needs to match what the >> adaptor is producing and in this case the MPAS NetCDF reader does not match >> what the adaptor provides to Catalyst. The way to get around this is to run >> Catalyst with a sample Python script that outputs the full data set that >> the adaptor provides. For MPAS this is slightly more complex because it >> provides several outputs, 10 in fact, depending on how the scientists want >> the data (e.g. spherical vs. projected, primal vs. dual grid, single level >> vs. multiple levels) for what they're trying to do. The attached script can >> be used to write out all 10 of these outputs which is done every 5th output >> (this can be changed by changing the outputfrequency value). >> >> The general workflow would be to run MPAS with this script for a small >> amount of time steps (maybe also with a smaller input data set). Then use >> those outputs to generate the Catalyst script that you want from the GUI. >> >> If this is a bit unclear, I'd recommend going through the Catalyst User's >> Guide ( >> http://www.paraview.org/files/catalyst/docs/ParaViewCatalystUsersGuide_v2.pdf) >> for more details. >> >> Regards, >> Andy >> >> On Mon, Aug 3, 2015 at 12:20 PM, David E DeMarle < >> dave.demarle at kitware.com> wrote: >> >>> Andy Bauer just explained it to me. He'll get back to you soon with a >>> detailed explanation and hints about how to get what you want done. >>> >>> Meanwhile, what is tripping us up is that MPAS's catalyst adaptor is not >>> the same thing as ParaViews MPAS reader. The reader has the >>> SetVerticalLevel(int) method, but the adaptor probably has an entirely >>> different method for doing that. >>> >>> I don't know firsthand what that method is so we'll have to wait for his >>> response. >>> >>> >>> >>> >>> >>> 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 4:20 PM, Eatmon Jr., Arnold >>> wrote: >>> >>>> # 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 >>>> Date: Thursday, July 30, 2015 at 1:45 PM >>>> To: First name Last name >>>> 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 >>>> 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 >>>>> >>>>> >>>>> # 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 >>>>> Date: Thursday, July 30, 2015 at 12:32 PM >>>>> To: First name Last name >>>>> Cc: "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 >>>>> 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: From chrisneal at ufl.edu Mon Aug 3 16:20:44 2015 From: chrisneal at ufl.edu (Neal,Christopher R) Date: Mon, 3 Aug 2015 20:20:44 +0000 Subject: [Paraview] How to extract a list of the plotting variable names with Python Message-ID: Hi, I'm trying to extract a list of the names of the available plotting variables from a data set that I have loaded. The variable names are all related to cell data in the data set. Something like ['Density','Pressure','Temperature','Velocity'] is what I am trying to extract from the Ensight Reader data object using Python. I have a feeling that this is something that can be extracted from the vtkPVDataInformation Class, but I'm unsure about which method to use. 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: From aeatmon at lanl.gov Mon Aug 3 16:21:25 2015 From: aeatmon at lanl.gov (Eatmon Jr., Arnold) Date: Mon, 3 Aug 2015 20:21:25 +0000 Subject: [Paraview] FW: adjusting vertical level setting via paraview python script In-Reply-To: References: Message-ID: From: "", First name Last name > Date: Monday, August 3, 2015 at 2:12 PM To: Andy Bauer > Subject: Re: [Paraview] adjusting vertical level setting via paraview python script Unfortunately I do not think that version is available which is why I was not using a script exported from Paraview gui with a .pvtu file open in it. Attempting to open vtk files generated in MPAS-O in the paraview GUI results in paraview not knowing which reader to use and crashing. John Patchett contacted kitware about this issue a few weeks ago; but again the build for version 4.3.2 that could open the output Vtk files is no longer up on the paraview site. I will attempt to follow your instructions and find out nonetheless, to be clear I should: 1. Use your script and write out a vtk file from MPAS-O 2. Open that file in the Paraview gui 3. Make the changes I want and export that change to a python script via coprocessing Is this correct? From: Andy Bauer > Date: Monday, August 3, 2015 at 2:03 PM To: First name Last name > Cc: "Patchett, John M" >, Dave DeMarle >, "paraview at paraview.org" > Subject: Re: [Paraview] adjusting vertical level setting via paraview python script I think the changes to the XML formats were done prior to PV 4.3.1 but am not certain. When making the scripts in the GUI you'll want to use the same version of ParaView though that is linked with MPAS to make sure the generated Python scripts are compatible. On Mon, Aug 3, 2015 at 3:56 PM, Eatmon Jr., Arnold > wrote: Oh, my mistake I didn?t understand the instructions. I will run it again to get .pvtu output, however in my previous scripts that generate VTK output there was an issue where the currently released 4.3.1 version of Paraview could not open the files due to a back compatability issue. I had a developers head on an old machine that could open them, however I do not any longer and the source code is no longer available on the paraview downloads page. Will v4.3.1 be able to open these .pvtu output files? From: Andy Bauer > Date: Monday, August 3, 2015 at 1:14 PM To: First name Last name >, "Patchett, John M" >, Dave DeMarle >, "paraview at paraview.org" > Subject: Re: [Paraview] adjusting vertical level setting via paraview python script Hi, Please reply to everyone so that anyone that wants to follow along with the conversation can. Did you get a chance to look through the Catalyst User's Guide? For MPAS, the names of the adaptor outputs are: 'X_Y_NLAYER-primal', 'X_Y_NLAYER-dual', 'X_Y_Z_1LAYER-primal', 'X_Y_Z_1LAYER-dual', 'X_Y_Z_NLAYER-primal', 'X_Y_Z_NLAYER-dual', 'LON_LAT_1LAYER-primal', 'LON_LAT_1LAYER-dual', 'LON_LAT_NLAYER-primal', 'LON_LAT_NLAYER-dual' The files that you want are the ones provided by Catalyst and not the ones that MPAS natively writes out. The Catalyst files all should be written out with pvtu extensions (e.g. X_Y_NLAYER-primal_1.pvtu). The MPAS native output is the .nc file. The other error that you're getting is that you have an active Python trace when going through the Catalyst export wizard and that trace needs to be stopped. Regards, Andy On Mon, Aug 3, 2015 at 3:00 PM, Eatmon Jr., Arnold > wrote: Alright, in order of what I did just to be clear, I uploaded the attached python to my directory, soft linked it to mpas.py, ran the simulation for a single timestep, and got a file in my output folder labeled output.0015-01-01_00.00.00.nc. I took that file and opened it in the Paraview desktop gui. In paraview with coprocessing enabled (Tools > Plugin Manager > under catalyst option, hit load), I made the adjustment to the vertical level and then exported the state (CoProcessing > Export State). I do not get a python script as an output, I get the error "Cannot generate Python state when tracing is active." RuntimeError: Cannot generate Python state when tracing is active. From: Andy Bauer > Date: Monday, August 3, 2015 at 11:33 AM To: David E DeMarle > Cc: First name Last name >, "Patchett, John M" >, "paraview at paraview.org" > Subject: Re: [Paraview] adjusting vertical level setting via paraview python script Hi, Dave is correct in that the reader's output needs to match what the adaptor is producing and in this case the MPAS NetCDF reader does not match what the adaptor provides to Catalyst. The way to get around this is to run Catalyst with a sample Python script that outputs the full data set that the adaptor provides. For MPAS this is slightly more complex because it provides several outputs, 10 in fact, depending on how the scientists want the data (e.g. spherical vs. projected, primal vs. dual grid, single level vs. multiple levels) for what they're trying to do. The attached script can be used to write out all 10 of these outputs which is done every 5th output (this can be changed by changing the outputfrequency value). The general workflow would be to run MPAS with this script for a small amount of time steps (maybe also with a smaller input data set). Then use those outputs to generate the Catalyst script that you want from the GUI. If this is a bit unclear, I'd recommend going through the Catalyst User's Guide (http://www.paraview.org/files/catalyst/docs/ParaViewCatalystUsersGuide_v2.pdf) for more details. Regards, Andy On Mon, Aug 3, 2015 at 12:20 PM, David E DeMarle > wrote: Andy Bauer just explained it to me. He'll get back to you soon with a detailed explanation and hints about how to get what you want done. Meanwhile, what is tripping us up is that MPAS's catalyst adaptor is not the same thing as ParaViews MPAS reader. The reader has the SetVerticalLevel(int) method, but the adaptor probably has an entirely different method for doing that. I don't know firsthand what that method is so we'll have to wait for his response. 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 4:20 PM, Eatmon Jr., Arnold > wrote: # 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 > Date: Thursday, July 30, 2015 at 1:45 PM To: First name Last name > 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 > 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 # 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 > Date: Thursday, July 30, 2015 at 12:32 PM To: First name Last name > Cc: "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 > 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: From dave.demarle at kitware.com Mon Aug 3 16:24:53 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Mon, 3 Aug 2015 16:24:53 -0400 Subject: [Paraview] How to extract a list of the plotting variable names with Python In-Reply-To: References: Message-ID: Try: src = GetActiveSource() src.CellData.keys() David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Aug 3, 2015 at 4:20 PM, Neal,Christopher R wrote: > Hi, > > > I'm trying to extract a list of the names of the available plotting > variables from a data set that I have loaded. The variable names are all > related to cell data in the data set. Something like > ['Density','Pressure','Temperature','Velocity'] is what I am trying to > extract from the Ensight Reader data object using Python. > > > I have a feeling that this is something that can be extracted from the > vtkPVDataInformation Class, but I'm unsure about which method to use. > > > > 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 > > _______________________________________________ > 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: From andy.bauer at kitware.com Mon Aug 3 16:39:58 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 3 Aug 2015 16:39:58 -0400 Subject: [Paraview] FW: adjusting vertical level setting via paraview python script In-Reply-To: References: Message-ID: Yes, that should be the proper workflow. On Mon, Aug 3, 2015 at 4:21 PM, Eatmon Jr., Arnold wrote: > > > From: "", First name Last name > Date: Monday, August 3, 2015 at 2:12 PM > To: Andy Bauer > > Subject: Re: [Paraview] adjusting vertical level setting via paraview > python script > > Unfortunately I do not think that version is available which is why I was > not using a script exported from Paraview gui with a .pvtu file open in it. > Attempting to open vtk files generated in MPAS-O in the paraview GUI > results in paraview not knowing which reader to use and crashing. John > Patchett contacted kitware about this issue a few weeks ago; but again the > build for version 4.3.2 that could open the output Vtk files is no longer > up on the paraview site. I will attempt to follow your instructions and > find out nonetheless, to be clear I should: > > 1. Use your script and write out a vtk file from MPAS-O > 2. Open that file in the Paraview gui > 3. Make the changes I want and export that change to a python script via > coprocessing > > Is this correct? > > > > From: Andy Bauer > Date: Monday, August 3, 2015 at 2:03 PM > To: First name Last name > Cc: "Patchett, John M" , Dave DeMarle < > dave.demarle at kitware.com>, "paraview at paraview.org" > Subject: Re: [Paraview] adjusting vertical level setting via paraview > python script > > I think the changes to the XML formats were done prior to PV 4.3.1 but am > not certain. When making the scripts in the GUI you'll want to use the same > version of ParaView though that is linked with MPAS to make sure the > generated Python scripts are compatible. > > On Mon, Aug 3, 2015 at 3:56 PM, Eatmon Jr., Arnold > wrote: > >> Oh, my mistake I didn?t understand the instructions. I will run it again >> to get .pvtu output, however in my previous scripts that generate VTK >> output there was an issue where the currently released 4.3.1 version of >> Paraview could not open the files due to a back compatability issue. I had >> a developers head on an old machine that could open them, however I do not >> any longer and the source code is no longer available on the paraview >> downloads page. Will v4.3.1 be able to open these .pvtu output files? >> >> From: Andy Bauer >> Date: Monday, August 3, 2015 at 1:14 PM >> To: First name Last name , "Patchett, John M" < >> patchett at lanl.gov>, Dave DeMarle , " >> paraview at paraview.org" >> >> Subject: Re: [Paraview] adjusting vertical level setting via paraview >> python script >> >> Hi, >> >> Please reply to everyone so that anyone that wants to follow along with >> the conversation can. >> >> Did you get a chance to look through the Catalyst User's Guide? >> >> For MPAS, the names of the adaptor outputs are: >> 'X_Y_NLAYER-primal', >> 'X_Y_NLAYER-dual', >> 'X_Y_Z_1LAYER-primal', >> 'X_Y_Z_1LAYER-dual', >> 'X_Y_Z_NLAYER-primal', >> 'X_Y_Z_NLAYER-dual', >> 'LON_LAT_1LAYER-primal', >> 'LON_LAT_1LAYER-dual', >> 'LON_LAT_NLAYER-primal', >> 'LON_LAT_NLAYER-dual' >> >> The files that you want are the ones provided by Catalyst and not the >> ones that MPAS natively writes out. The Catalyst files all should be >> written out with pvtu extensions (e.g. X_Y_NLAYER-primal_1.pvtu). The MPAS >> native output is the .nc file. >> >> The other error that you're getting is that you have an active Python >> trace when going through the Catalyst export wizard and that trace needs to >> be stopped. >> >> Regards, >> Andy >> >> On Mon, Aug 3, 2015 at 3:00 PM, Eatmon Jr., Arnold >> wrote: >> >>> Alright, in order of what I did just to be clear, I uploaded the >>> attached python to my directory, soft linked it to mpas.py, ran the >>> simulation for a single timestep, and got a file in my output folder >>> labeled output.0015-01-01_00.00.00.nc. I took that file and opened it >>> in the Paraview desktop gui. In paraview with coprocessing enabled (Tools > >>> Plugin Manager > under catalyst option, hit load), I made the adjustment to >>> the vertical level and then exported the state (CoProcessing > Export >>> State). I do not get a python script as an output, I get the error >>> >>> "Cannot generate Python state when tracing is active." >>> >>> RuntimeError: Cannot generate Python state when tracing is active. >>> >>> >>> >>> >>> >>> From: Andy Bauer >>> Date: Monday, August 3, 2015 at 11:33 AM >>> To: David E DeMarle >>> Cc: First name Last name , "Patchett, John M" < >>> patchett at lanl.gov>, "paraview at paraview.org" >>> >>> Subject: Re: [Paraview] adjusting vertical level setting via paraview >>> python script >>> >>> Hi, >>> >>> Dave is correct in that the reader's output needs to match what the >>> adaptor is producing and in this case the MPAS NetCDF reader does not match >>> what the adaptor provides to Catalyst. The way to get around this is to run >>> Catalyst with a sample Python script that outputs the full data set that >>> the adaptor provides. For MPAS this is slightly more complex because it >>> provides several outputs, 10 in fact, depending on how the scientists want >>> the data (e.g. spherical vs. projected, primal vs. dual grid, single level >>> vs. multiple levels) for what they're trying to do. The attached script can >>> be used to write out all 10 of these outputs which is done every 5th output >>> (this can be changed by changing the outputfrequency value). >>> >>> The general workflow would be to run MPAS with this script for a small >>> amount of time steps (maybe also with a smaller input data set). Then use >>> those outputs to generate the Catalyst script that you want from the GUI. >>> >>> If this is a bit unclear, I'd recommend going through the Catalyst >>> User's Guide ( >>> http://www.paraview.org/files/catalyst/docs/ParaViewCatalystUsersGuide_v2.pdf) >>> for more details. >>> >>> Regards, >>> Andy >>> >>> On Mon, Aug 3, 2015 at 12:20 PM, David E DeMarle < >>> dave.demarle at kitware.com> wrote: >>> >>>> Andy Bauer just explained it to me. He'll get back to you soon with a >>>> detailed explanation and hints about how to get what you want done. >>>> >>>> Meanwhile, what is tripping us up is that MPAS's catalyst adaptor is >>>> not the same thing as ParaViews MPAS reader. The reader has the >>>> SetVerticalLevel(int) method, but the adaptor probably has an entirely >>>> different method for doing that. >>>> >>>> I don't know firsthand what that method is so we'll have to wait for >>>> his response. >>>> >>>> >>>> >>>> >>>> >>>> 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 4:20 PM, Eatmon Jr., Arnold >>>> wrote: >>>> >>>>> # 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 >>>>> Date: Thursday, July 30, 2015 at 1:45 PM >>>>> To: First name Last name >>>>> 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 >>>>> 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 >>>>>> >>>>>> >>>>>> # 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 >>>>>> Date: Thursday, July 30, 2015 at 12:32 PM >>>>>> To: First name Last name >>>>>> Cc: "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 >>>>> > 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 >>>> >>>> >>> >> > > _______________________________________________ > 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: From dennis_conklin at goodyear.com Mon Aug 3 16:05:57 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Mon, 3 Aug 2015 20:05:57 +0000 Subject: [Paraview] How to detect valid read in Programmable filter Message-ID: All, I want to try to read some point arrays in the Programmable Filter and take action based on whether or not the arrays have been loaded into Paraview. I am pretty lost in the PF, so take that for what it's worth. If I try something like try: displ=block.PointData['DISPL'] Print displ except: Print 'DISPL read failed' else: Print 'DISPL read succeeded' The try never fails - it always prints "DISPL read succeeded, whether I actually loaded the DISPL array or not. If I print displ, I get an array of values if I loaded the DISPL array into Paraview and a vtk.numpy_interface.dataset_adapter.VTKNoneArray object if I haven't loaded the array. Not to be too dense, but how do I test to see if I got an array or a VTKNoneArray object? Thanks Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisneal at ufl.edu Mon Aug 3 16:54:55 2015 From: chrisneal at ufl.edu (Neal,Christopher R) Date: Mon, 3 Aug 2015 20:54:55 +0000 Subject: [Paraview] How to extract a list of the plotting variable names with Python In-Reply-To: References: , Message-ID: That did exactly what I wanted. Thanks David! 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 ________________________________ From: David E DeMarle Sent: Monday, August 3, 2015 4:24 PM To: Neal,Christopher R Cc: paraview at paraview.org Subject: Re: [Paraview] How to extract a list of the plotting variable names with Python Try: src = GetActiveSource() src.CellData.keys() David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Aug 3, 2015 at 4:20 PM, Neal,Christopher R > wrote: Hi, I'm trying to extract a list of the names of the available plotting variables from a data set that I have loaded. The variable names are all related to cell data in the data set. Something like ['Density','Pressure','Temperature','Velocity'] is what I am trying to extract from the Ensight Reader data object using Python. I have a feeling that this is something that can be extracted from the vtkPVDataInformation Class, but I'm unsure about which method to use. 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 _______________________________________________ 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: From bruce.david.jones at gmail.com Mon Aug 3 20:55:16 2015 From: bruce.david.jones at gmail.com (Bruce Jones) Date: Tue, 04 Aug 2015 00:55:16 +0000 Subject: [Paraview] Error building superbuild VS2010 In-Reply-To: <20150731205909.GC6556@megas.kitware.com> References: <20150731205909.GC6556@megas.kitware.com> Message-ID: Thanks Ben, I followed your instructions and the build was successful in release mode. However, when I run the executable it crashes on load. Attempting to debug this I tried to build in debug mode using the same approach. Unfortunately the debug build fails with an error, qtmain.lib(qtmain_win.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in paraview_main.cxx.obj MSVCRTD.lib(cinitexe.obj) : warning LNK4098: defaultlib 'msvcrt.lib' conflicts with use of other libs; use /NODEFAULTLIB:library bin\paraview.exe : fatal error LNK1319: 1 mismatches detected LINK Pass 1 failed. with 1319 I am not sure why this is occurring. Bruce On Fri, 31 Jul 2015 at 16:59 Ben Boeckel wrote: > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisneal at ufl.edu Mon Aug 3 20:58:06 2015 From: chrisneal at ufl.edu (Neal,Christopher R) Date: Tue, 4 Aug 2015 00:58:06 +0000 Subject: [Paraview] Update data after timestep is taken Message-ID: Hi, I have a Python script that opens an ENSIGHT data file that contains cell data for several timesteps. I'd like to be able to perform an operation on one timestep and then advance to the next timetstep. I have tried using the GoToNext() method on the animation scene like it shows when I do a Python trace of stepping through timesteps, but that isn't working. It looks like it just never updates the cell data to match the data for the timesteps that I'm iterating over. I only ever get data for the first timestep. I've tried to use the UpdatePipeline() method as well, but it didn't fix my issue. Does anyone have experience with iterating over timesteps and updating the data set for each timestep? 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: From dan.lipsa at kitware.com Mon Aug 3 22:37:22 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Tue, 04 Aug 2015 02:37:22 +0000 Subject: [Paraview] Update data after timestep is taken In-Reply-To: References: Message-ID: Christopher, See the following wiki page http://www.paraview.org/Wiki/ParaView/Python/Dealing_with_time On Mon, Aug 3, 2015 at 8:58 PM Neal,Christopher R wrote: > Hi, > > > I have a Python script that opens an ENSIGHT data file that contains cell > data for several timesteps. I'd like to be able to perform an operation on > one timestep and then advance to the next timetstep. I have tried using > the GoToNext() method on the animation scene like it shows when I do a > Python trace of stepping through timesteps, but that isn't working. It > looks like it just never updates the cell data to match the data for the > timesteps that I'm iterating over. I only ever get data for the first > timestep. I've tried to use the UpdatePipeline() method as well, but it > didn't fix my issue. Does anyone have experience with iterating over > timesteps and updating the data set for each timestep? > > > 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 > _______________________________________________ > 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: From G.D.Weymouth at soton.ac.uk Mon Aug 3 23:12:55 2015 From: G.D.Weymouth at soton.ac.uk (Gabe Weymouth) Date: Tue, 4 Aug 2015 11:12:55 +0800 Subject: [Paraview] Tensor transpose for lambda 2 Message-ID: I'm doing some fluid flow visualizations, and I'm trying to compute the lambda_2 scalar field (which is the second eigenvalue of a tensor based on the velocity gradient). It seems like the python calculator has NEARLY everything I need (eigenvalue, gradient) but I also need to be able to take the transpose of the gradient tensor to get the symmetric and skew-symmetric parts. I can't find it anywhere in the documentation but there must be a transpose function, right? If not - or if I'm approaching this wrong - how else can I compute the lambda_2 value from the velocity field? Thanks! *Gabe* -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Mon Aug 3 23:31:01 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Tue, 04 Aug 2015 03:31:01 +0000 Subject: [Paraview] How to detect valid read in Programmable filter In-Reply-To: References: Message-ID: Hi Dennis, Try isinstance(displ, vtk.numpy_interface.dataset_adapter.VTKNoneArray) Dan On Mon, Aug 3, 2015 at 4:40 PM Dennis Conklin wrote: > All, > > > > I want to try to read some point arrays in the Programmable Filter and > take action based on whether or not the arrays have been loaded into > Paraview. I am pretty lost in the PF, so take that for what it?s worth. > > > > If I try something like > > > > try: > > displ=block.PointData[?DISPL?] > > Print displ > > except: > > Print ?DISPL read failed? > > else: > > Print ?DISPL read succeeded? > > > > The try never fails ? it always prints ?DISPL read succeeded, whether I > actually loaded the DISPL array or not. > > > > If I print displ, I get an array of values if I loaded the DISPL array > into Paraview and a vtk.numpy_interface.dataset_adapter.VTKNoneArray object > if I haven?t loaded the array. > > > > Not to be too dense, but how do I test to see if I got an array or a > VTKNoneArray object? > > > > Thanks > > > > Dennis > _______________________________________________ > 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: From joachim.pouderoux at kitware.com Tue Aug 4 06:04:28 2015 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Tue, 4 Aug 2015 12:04:28 +0200 Subject: [Paraview] Extract the x,y,z extents of a domain in Paraview In-Reply-To: References: Message-ID: Neal, Try this: >>> mySource.PointData.values() >>> mySource.CellData.values() Joachim *Joachim Pouderoux* *PhD, Technical Expert* *Kitware SAS * 2015-08-03 17:59 GMT+02:00 Neal,Christopher R : > Thanks Joachim! > > > Do you also happen to know how to obtain the list of plotting variables > once a data set has been loaded into Paraview? I would like to get > something like, ['Pressure','Density',Velocity']. > > > 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 > > > ------------------------------ > *From:* Joachim Pouderoux > *Sent:* Monday, August 3, 2015 3:06 AM > *To:* Neal,Christopher R > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] Extract the x,y,z extents of a domain in > Paraview > > Christopher, > > Fetching the bounds of a source in Python is as simple as: > > >>> mySource.GetDataInformation().GetBounds() > > The vtkPVDataInformation > > object returned by GetDataInformation() contains many other information > about the source like: > - DataSetType > - MemorySize > - PolygonCount > - NumberOfPoints > - NumberOfCels > etc. > > > Regards, > > *Joachim Pouderoux* > > *PhD, Technical Expert* > *Kitware SAS * > > > 2015-08-01 1:24 GMT+02:00 Neal,Christopher R : > >> 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 >> >> _______________________________________________ >> 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: From c.coutinho at redstack.nl Tue Aug 4 07:28:11 2015 From: c.coutinho at redstack.nl (Chris Coutinho) Date: Tue, 4 Aug 2015 11:28:11 +0000 Subject: [Paraview] Trouble building paraview431 from source on workstation Message-ID: <1e74bded1899445aab499cc09c57e5b2@NLZWMBX01.a-hak.local> Hello ParaView community, Introduction I have a workstation here at work where I want to utilize the additional functionality (MPI and python) of ParaView 4.3.1, therefore I want to install it from source. Although I think I compiled ParaView successfully, as root, another program that I use for CAD geometry (Salome) no longer opens correctly. This is directly due to the ParaView installation. Executing either of these two programs as root does not reproduce the errors discussed below. Some background I run OpenFOAM 2.4.x, which comes with ParaView 4.1.0 as a 'Third party package'. This is my attempt at installing another version of ParaView on the same system. I assumed I didn't need to remove the previous version, but this could be a mistake. Here is my system: * OpenSUSE 13.2, KDE 4.14.9 * Cmake 3.0.2 * Vtk 6.1.0 * Qmake 2.01a * Qt 4.8.6 * OpenMPI 1.7.2 My steps I cloned the git repository and configured the build using Cmake (in a separate build directory) as mentioned on the build-from-source wiki, everything building the objects went fine until I tried to compile them. Since I want to place all compiled binaries and libraries into /usr/local/, I need to compile using sudo. My first question is: is this correct? This could be my problem. My second problem was that after compiling paraview, executing paraview resulted in a segmentation fault. Some digging on archives of this mailing list and other forums hinted at adding the following library (/usr/lib64/libdl.so) to the MPI_C_LIBRARIES and MPI_CXX_LIBRARIES paths in ccmake. This solved the SegFault problem, and now I'm able to run paraview, but I'm getting the following errors: libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast Concluding remarks Running Salome also shows the same errors, and doesn't open correctly (No GUI shown) when executed as a user. Running either program as root does not cause these problems/errors, but the errors that occur when opening Salome are more detrimental. I'm not a Linux veteran by any stretch, so I'm not sure how to diagnose what the issue is. Can someone give me an idea of how to solve this problem? I reproduced my ccmake build configuration settings below. Ccmake build options BUILD_DOCUMENTATION OFF BUILD_EXAMPLES OFF BUILD_SHARED_LIBS OFF BUILD_TESTING ON BUILD_USER_DEFINED_LIBS OFF CMAKE_BUILD_TYPE Debug CMAKE_INSTALL_PREFIX /usr/local CTEST_TEST_TIMEOUT 3600 GMVReader_GMVREAD_LIB_DIR /opt/ParaView/ParaView-v4.3.1-source/Utilities/VisItBridge/databases/GMV GMVReader_SKIP_DATARANGE_CALCU OFF MPI_C_INCLUDE_PATH /usr/lib64/mpi/gcc/openmpi/include/openmpi/opal/mca/hwloc/hwloc152/hwloc/include;/usr/lib64/mpi/gcc/openmpi/include/openmpi MPI_C_LIBRARIES /usr/lib64/mpi/gcc/openmpi/lib64/libmpi.so;/usr/lib64/libdl.so PARAVIEW_BUILD_QT_GUI ON PARAVIEW_ENABLE_CATALYST ON PARAVIEW_ENABLE_FFMPEG OFF PARAVIEW_ENABLE_PYTHON ON PARAVIEW_INSTALL_DEVELOPMENT_F OFF PARAVIEW_USE_DAX OFF PARAVIEW_USE_MPI ON PARAVIEW_USE_PISTON OFF PARAVIEW_USE_UNIFIED_BINDINGS OFF PARAVIEW_USE_VISITBRIDGE OFF RMANTREE RMANTREE-NOTFOUND SURFACELIC_PLUGIN_TESTING ON VISIT_BUILD_READER_CGNS OFF VISIT_BUILD_READER_GMV OFF VISIT_BUILD_READER_Mili OFF VISIT_BUILD_READER_Silo OFF VTK_ANDROID_BUILD OFF VTK_IOS_BUILD OFF VTK_PYTHON_VERSION 2 VTK_QT_VERSION 4 VTK_RENDERING_BACKEND OpenGL VTK_SMP_IMPLEMENTATION_TYPE OpenMP VTK_USE_LARGE_DATA OFF VTK_USE_SYSTEM_GLEW OFF XDMF_USE_BZIP2 OFF XDMF_USE_GZIP OFF Vriendelijke groeten, Chris Coutinho, EIT Onderzoeker REDstack, B.V. Pieter Zeemanstraat 6 8606 JR Sneek, The Netherlands work: +31 6 2222 5785 mobile: +31 6 1689 0287 www.redstack.nl -------------- next part -------------- An HTML attachment was scrubbed... URL: From dennis_conklin at goodyear.com Tue Aug 4 08:20:06 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Tue, 4 Aug 2015 12:20:06 +0000 Subject: [Paraview] [EXT] Re: How to detect valid read in Programmable filter In-Reply-To: References: Message-ID: Dan, Thanks for that hint. A little experimenting proved that the fully qualified name didn?t work but dataset_adapter.VTKNoneArray worked so I wrapped up my filter this morning Dennis From: Dan Lipsa [mailto:dan.lipsa at kitware.com] Sent: Monday, August 03, 2015 11:31 PM To: Dennis Conklin; Paraview (paraview at paraview.org) Subject: [EXT] Re: [Paraview] How to detect valid read in Programmable filter Hi Dennis, Try isinstance(displ, vtk.numpy_interface.dataset_adapter.VTKNoneArray) Dan On Mon, Aug 3, 2015 at 4:40 PM Dennis Conklin > wrote: All, I want to try to read some point arrays in the Programmable Filter and take action based on whether or not the arrays have been loaded into Paraview. I am pretty lost in the PF, so take that for what it?s worth. If I try something like try: displ=block.PointData[?DISPL?] Print displ except: Print ?DISPL read failed? else: Print ?DISPL read succeeded? The try never fails ? it always prints ?DISPL read succeeded, whether I actually loaded the DISPL array or not. If I print displ, I get an array of values if I loaded the DISPL array into Paraview and a vtk.numpy_interface.dataset_adapter.VTKNoneArray object if I haven?t loaded the array. Not to be too dense, but how do I test to see if I got an array or a VTKNoneArray object? Thanks Dennis _______________________________________________ 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: From jeffrey.c.becker at nasa.gov Tue Aug 4 14:14:06 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Tue, 4 Aug 2015 11:14:06 -0700 Subject: [Paraview] vtkTransmitImageDataPiece question Message-ID: <55C100EE.50807@nasa.gov> Hi. I'm trying to run a Python Programmable source across four nodes (started with mpirun -np 4 pvserver). My script contains the following code, but the output looks wrong, so I'm not sure if the extents are right. The partitioning among nodes is correct (using processId filter). Also I'm careful to set Output Data Set Type to vtkImageData. import vtk import vtk.util.numpy_support as ns contr = vtk.vtkMultiProcessController.GetGlobalController() nranks = contr.GetNumberOfProcesses() rank = contr.GetLocalProcessId() ... executive = self.GetExecutive() outInfo = executive.GetOutputInformation(0) updateExtent = [executive.UPDATE_EXTENT().Get(outInfo, i) for i in xrange(6)] imageData = self.GetOutput() imageData.SetExtent(updateExtent) myout = ns.numpy_to_vtk(bmag.ravel(),1,vtk.VTK_FLOAT) myout.SetName("B field magnitude") imageData.GetPointData().SetScalars(myout) tp = vtk.vtkTrivialProducer() tp.SetOutput(imageData) tp.SetWholeExtent(0, mesh.MX-1, 0, mesh.MY-1, 0, mesh.MZ-1) xmit = vtk.vtkTransmitImageDataPiece() xmit.SetInputConnection(tp.GetOutputPort()) xmit.UpdateInformation() xmit.SetUpdateExtent(rank, nranks, 0) xmit.Update() For completeness, here is my requestInformation script (mesh has dimensions, and coordinate arrays for each of X,Y,Z) executive = self.GetExecutive() outInfo = executive.GetOutputInformation(0) outInfo.Set(vtk.vtkAlgorithm.CAN_PRODUCE_SUB_EXTENT(), 1) outInfo.Set(executive.WHOLE_EXTENT(), 0, mesh.MX-1, 0, mesh.MY-1, 0, mesh.MZ-1) xspacing = (mesh.xcoords[-1] - mesh.xcoords[0])/mesh.MX yspacing = (mesh.ycoords[-1] - mesh.ycoords[0])/mesh.MY zspacing = (mesh.zcoords[-1] - mesh.zcoords[0])/mesh.MZ outInfo.Set(vtk.vtkDataObject.SPACING(), xspacing, yspacing, zspacing) This is what I've been able to come up with after spending much time reading documentation and examples, but I've obviously missed something. Please advise. Thanks. -jeff From ben.boeckel at kitware.com Tue Aug 4 14:24:10 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 4 Aug 2015 14:24:10 -0400 Subject: [Paraview] Error building superbuild VS2010 In-Reply-To: References: <20150731205909.GC6556@megas.kitware.com> Message-ID: <20150804182410.GA11615@megas.kitware.com> On Tue, Aug 04, 2015 at 00:55:16 +0000, Bruce Jones wrote: > I followed your instructions and the build was successful in release mode. > However, when I run the executable it crashes on load. > > Attempting to debug this I tried to build in debug mode using the same > approach. Unfortunately the debug build fails with an error, > > qtmain.lib(qtmain_win.obj) : error LNK2038: mismatch detected for > '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in > paraview_main.cxx.obj > MSVCRTD.lib(cinitexe.obj) : warning LNK4098: defaultlib 'msvcrt.lib' > conflicts with use of other libs; use /NODEFAULTLIB:library > bin\paraview.exe : fatal error LNK1319: 1 mismatches detected > LINK Pass 1 failed. with 1319 > > I am not sure why this is occurring. This typically occurs because Qt is built in release while ParaView is debug and the two can't mix on Windows. I'd recommend starting from a completely clean build tree to avoid any lingering files and setting CMAKE_BUILD_TYPE=Release. --Ben From bruce.david.jones at gmail.com Tue Aug 4 14:26:42 2015 From: bruce.david.jones at gmail.com (Bruce Jones) Date: Tue, 04 Aug 2015 18:26:42 +0000 Subject: [Paraview] Error building superbuild VS2010 In-Reply-To: <20150804182410.GA11615@megas.kitware.com> References: <20150731205909.GC6556@megas.kitware.com> <20150804182410.GA11615@megas.kitware.com> Message-ID: Thanks again Ben. For the debug build I was using a completely new build directory, I moved the compiled files from the release build elsewhere and deleted everything else. Then started on the debug build from step one. On Tue, 4 Aug 2015 at 14:24 Ben Boeckel wrote: > On Tue, Aug 04, 2015 at 00:55:16 +0000, Bruce Jones wrote: > > I followed your instructions and the build was successful in release > mode. > > However, when I run the executable it crashes on load. > > > > Attempting to debug this I tried to build in debug mode using the same > > approach. Unfortunately the debug build fails with an error, > > > > qtmain.lib(qtmain_win.obj) : error LNK2038: mismatch detected for > > '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in > > paraview_main.cxx.obj > > MSVCRTD.lib(cinitexe.obj) : warning LNK4098: defaultlib 'msvcrt.lib' > > conflicts with use of other libs; use /NODEFAULTLIB:library > > bin\paraview.exe : fatal error LNK1319: 1 mismatches detected > > LINK Pass 1 failed. with 1319 > > > > I am not sure why this is occurring. > > This typically occurs because Qt is built in release while ParaView is > debug and the two can't mix on Windows. I'd recommend starting from a > completely clean build tree to avoid any lingering files and setting > CMAKE_BUILD_TYPE=Release. > > --Ben > -------------- next part -------------- An HTML attachment was scrubbed... URL: From S.R.Kharche at exeter.ac.uk Tue Aug 4 15:44:24 2015 From: S.R.Kharche at exeter.ac.uk (Kharche, Sanjay) Date: Tue, 4 Aug 2015 19:44:24 +0000 Subject: [Paraview] non-interactive viz on cluster In-Reply-To: References: , , Message-ID: Hi David, All Can you point out what are the paraview objects in the script pasted below? My approach for the next step of improving its efficiency is by deleting all the objects that I create at each iteration. Whereas this may be suboptimal, I will get it working before I go to the next step. cheers Sanjay try: paraview.simple except: from paraview.simple import * for i in range(0,4999,1): paraview.simple._DisableFirstRenderCameraReset() RenderView1 = GetRenderView() my_2d0_vts = XMLStructuredGridReader( FileName=['my_2d%i.vts' % (i)] ) RenderView1.CenterAxesVisibility = 0 RenderView1.OrientationAxesVisibility = 0 my_2d0_vts.PointArrayStatus = ['Unnamed0'] 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.0, 0.23, 0.299, 0.754, 1.0, 0.7059953924945706, 0.01625293517428646, 0.1500022472819457], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 ) a1_Unnamed0_PiecewiseFunction = CreatePiecewiseFunction( Points=[-0.1, 0.0, 1.0, 1.0] ) ScalarBarWidgetRepresentation1 = CreateScalarBar( Title='Unnamed0', LabelFontSize=12, Enabled=1, LookupTable=a1_Unnamed0_PVLookupTable, TitleFontSize=12 ) GetRenderView().Representations.append(ScalarBarWidgetRepresentation1) 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] Text1 = Text() RenderView1.CameraViewUp = [0.0, 1.0, 0.0] RenderView1.CameraPosition = [78.0, -58.5, 376.71107225273664] RenderView1.CameraFocalPoint = [78.0, -58.5, 0.0] RenderView1.CenterOfRotation = [78.0, -58.5, 0.0] RenderView1.CameraClippingRange = [372.94396153020926, 382.3617383365277] Text1.Text = '2D macro re-entry' DataRepresentation3 = Show() DataRepresentation3.Color = [0.3333333333333333, 0.0, 0.4980392156862745] WriteImage('reentry2d%06i.png' % (i)) Render() Delete(my_2d0_vts) Delete(RenderView1) Delete(Text1) # Delete(DataRepresentation1) # pvbatch didnt like this Delete(DataRepresentation2) # Delete(DataRepresentation3) # pbatch didnt like this, not defined for Delete # Delte(LookupTable) # not defined for Delete Delete(a1_Unnamed0_PVLookupTable) Delete(a1_Unnamed0_PiecewiseFunction) Delete(ScalarBarWidgetRepresentation1) # Delete(RGBPoints) # not defined for Delete -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisneal at ufl.edu Tue Aug 4 18:13:22 2015 From: chrisneal at ufl.edu (Neal,Christopher R) Date: Tue, 4 Aug 2015 22:13:22 +0000 Subject: [Paraview] Update data after timestep is taken In-Reply-To: References: , Message-ID: Thank you Dan. That page was very helpful. For me it looks like it was also an issue with forgetting to render/show the updated scene once it had transitioned to the newer timestep. I'm not 100% sure about the source of my issue, but with the help of that Wiki and the Paraview Trace tool I was able to get my script to work. Best regards, 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 ________________________________ From: Dan Lipsa Sent: Monday, August 3, 2015 10:37 PM To: Neal,Christopher R; paraview at paraview.org Subject: Re: [Paraview] Update data after timestep is taken Christopher, See the following wiki page http://www.paraview.org/Wiki/ParaView/Python/Dealing_with_time On Mon, Aug 3, 2015 at 8:58 PM Neal,Christopher R > wrote: Hi, I have a Python script that opens an ENSIGHT data file that contains cell data for several timesteps. I'd like to be able to perform an operation on one timestep and then advance to the next timetstep. I have tried using the GoToNext() method on the animation scene like it shows when I do a Python trace of stepping through timesteps, but that isn't working. It looks like it just never updates the cell data to match the data for the timesteps that I'm iterating over. I only ever get data for the first timestep. I've tried to use the UpdatePipeline() method as well, but it didn't fix my issue. Does anyone have experience with iterating over timesteps and updating the data set for each timestep? 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 _______________________________________________ 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: From jeffrey.c.becker at nasa.gov Wed Aug 5 16:54:45 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Wed, 5 Aug 2015 13:54:45 -0700 Subject: [Paraview] running parallel pvservers In-Reply-To: References: <55B12A0A.6070106@nasa.gov> <55B12F05.6070005@nasa.gov> Message-ID: <55C27815.2080802@nasa.gov> Hi David and list. I'm still struggling with distributing my dataset (bmag) across nodes. My Python Programmable source script below produces correct output when run on a single node. contr = vtk.vtkMultiProcessController.GetGlobalController() nranks = contr.GetNumberOfProcesses() rank = contr.GetLocalProcessId() # read in bmag data and process executive = self.GetExecutive() outInfo = executive.GetOutputInformation(0) updateExtent = [executive.UPDATE_EXTENT().Get(outInfo, i) for i in xrange(6)] imageData = self.GetOutput() imageData.SetExtent(updateExtent) myout = ns.numpy_to_vtk(bmag.ravel(),1,vtk.VTK_FLOAT) myout.SetName("B field magnitude") imageData.GetPointData().SetScalars(myout) I then used the Filters/Parallel/Testing/Python/testTransmit.py test code as a basis to continue the script to work on multiple nodes. Following the last line above, I added: da = vtk.vtkIntArray() da.SetNumberOfTuples(6) if rank == 0: ext = imageData.GetExtent() for i in range(6): da.SetValue(i,ext[i]) contr.Broadcast(da,0) ext = [] for i in range(6): ext.append(da.GetValue(i)) ext = tuple(ext) tp = vtk.vtkTrivialProducer() tp.SetOutput(imageData) tp.SetWholeExtent(ext) xmit = vtk.vtkTransmitImageDataPiece() xmit.SetInputConnection(tp.GetOutputPort()) xmit.UpdateInformation() xmit.SetUpdateExtent(rank, nranks, 0) xmit.Update() However, when I run this on two nodes, it looks like both of them get the same half of the data, rather than the whole dataset getting split between the two. Can anyone see what might be wrong? 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 > > 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 >> > 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: From raphael.schubert at iwm.fraunhofer.de Thu Aug 6 11:07:03 2015 From: raphael.schubert at iwm.fraunhofer.de (Schubert, Raphael) Date: Thu, 6 Aug 2015 15:07:03 +0000 Subject: [Paraview] (no subject) Message-ID: <13DD8C6B6309B94AA144319F72195FFD3731A238@IWMDAG2.iwm.fraunhofer.de> I use the following script to generate three vtk files containing different dataset types and an additional FIELD. import numpy as np import vtk from vtk.util.numpy_support import numpy_to_vtk for dataset in (vtk.vtkStructuredPoints, vtk.vtkRectilinearGrid, vtk.vtkPolyData): vtkData = dataset() if dataset is vtk.vtkStructuredPoints: vtkWriter = vtk.vtkStructuredPointsWriter() vtkData.SetOrigin(0.0, 0.0, 0.0) vtkData.SetSpacing(1.0, 1.0, 1.0) vtkData.SetExtent(0, 1, 0, 1, 0, 1) elif dataset is vtk.vtkPolyData: vtkWriter = vtk.vtkPolyDataWriter() vtkPoints = vtk.vtkPoints() vtkPoints.SetData(numpy_to_vtk(np.asarray( [[0.0, 0.0, 0.0], [1.0, 0.0, 0.0], [0.0, 1.0, 0.0], [1.0, 1.0, 0.0], [0.0, 0.0, 1.0], [1.0, 0.0, 1.0], [0.0, 1.0, 1.0], [1.0, 1.0, 1.0]]))) vtkData.SetPoints(vtkPoints) elif dataset is vtk.vtkRectilinearGrid: vtkWriter = vtk.vtkRectilinearGridWriter() vtkData.SetDimensions(2,2,2) vtkData.SetXCoordinates(numpy_to_vtk(np.asarray([0.0, 1.0]))) vtkData.SetYCoordinates(numpy_to_vtk(np.asarray([0.0, 1.0]))) vtkData.SetZCoordinates(numpy_to_vtk(np.asarray([0.0, 1.0]))) # file scope definition of Pi vtkArray = numpy_to_vtk(np.asarray(3.141).reshape(1,1),deep=1) vtkArray.SetName("Pi") vtkData.GetFieldData().AddArray(vtkArray) vtkWriter.SetFileName(str(dataset) + ".vtk") vtkWriter.SetHeader("") vtkWriter.SetFileTypeToASCII() vtkWriter.SetInput(vtkData) vtkWriter.Write() /endscript The files generated from this are # vtk DataFile Version 3.0 ASCII DATASET POLYDATA FIELD FieldData 1 Pi 1 1 double 3.141 POINTS 8 double 0 0 0 1 0 0 0 1 0 1 1 0 0 0 1 1 0 1 0 1 1 1 1 1 # vtk DataFile Version 3.0 ASCII DATASET RECTILINEAR_GRID FIELD FieldData 1 Pi 1 1 double 3.141 DIMENSIONS 2 2 2 X_COORDINATES 2 double 0 1 Y_COORDINATES 2 double 0 1 Z_COORDINATES 2 double 0 1 # vtk DataFile Version 3.0 ASCII DATASET STRUCTURED_POINTS FIELD FieldData 1 Pi 1 1 double 3.141 DIMENSIONS 2 2 2 SPACING 1 1 1 ORIGIN 0 0 0 Note the FIELD preceding the dataset details. All files can be read back into python without problems, but when trying to view each file in using Paraview 4.3.1, things get interesting: - POLYDATA works. - RECTILINEAR_GRID produces an error (which, btw, contains a typo), refuses to render anything but displays everything correctly in the Information tab. ERROR: In /home/kitware/Dashboards/buildbot/paraview-debian4dash-linux-shared-release_qt4_superbuild/source-paraview/VTK/IO/Parallel/vtkPDataSetReader.cxx, line 701 vtkPDataSetReader (0x8874010): Expecting 'DIMENSIONS' insted of: FIELD - STRUCTURED_POINTS does not produce any errors, still refuses to render but displays everything correctly in the Information tab. If I now (manually) put the FIELDS definition after the dataset details, everything works fine. Is this problem with Paraview, or am I doing something with the vtk format that should not be possible at all? I got the idea from http://www.visitusers.org/index.php?title=Time_and_Cycle_in_VTK_files. Thanks Raphael Software versions: Paraview 4.3.1 Linux 64bit Python 2.7.8 |Anaconda 2.1.0 (64-bit)| (default, Aug 21 2014, 18:22:21) [GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] on linux2 vtk.vtkVersion().GetVTKVersion() '5.10.1' -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Aug 6 16:53:22 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 6 Aug 2015 16:53:22 -0400 Subject: [Paraview] Update: Upcoming ParaView Releases (4.4 and 5.0) In-Reply-To: References: Message-ID: Folks, Just wanted to let everyone know we're closing on a ParaView 4.4 release candidate (think next week or two). If you spot any major issues, or there's something you're keen on committing, you should do that now. Utkarsh On Fri, Jul 17, 2015 at 2:29 PM, Utkarsh Ayachit 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. From dan.lipsa at kitware.com Thu Aug 6 23:11:43 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Fri, 07 Aug 2015 03:11:43 +0000 Subject: [Paraview] (no subject) In-Reply-To: <13DD8C6B6309B94AA144319F72195FFD3731A238@IWMDAG2.iwm.fraunhofer.de> References: <13DD8C6B6309B94AA144319F72195FFD3731A238@IWMDAG2.iwm.fraunhofer.de> Message-ID: Raphael, Indeed, the FIELD definitions have to be after the dataset details according to: http://www.vtk.org/wp-content/uploads/2015/04/file-formats.pdf On Thu, Aug 6, 2015 at 11:14 AM Schubert, Raphael < raphael.schubert at iwm.fraunhofer.de> wrote: > I use the following script to generate three vtk files containing > different dataset types and an additional FIELD. > > import numpy as np > import vtk > from vtk.util.numpy_support import numpy_to_vtk > > for dataset in (vtk.vtkStructuredPoints, > vtk.vtkRectilinearGrid, > vtk.vtkPolyData): > > vtkData = dataset() > > if dataset is vtk.vtkStructuredPoints: > vtkWriter = vtk.vtkStructuredPointsWriter() > > vtkData.SetOrigin(0.0, 0.0, 0.0) > vtkData.SetSpacing(1.0, 1.0, 1.0) > vtkData.SetExtent(0, 1, 0, 1, 0, 1) > > elif dataset is vtk.vtkPolyData: > vtkWriter = vtk.vtkPolyDataWriter() > > vtkPoints = vtk.vtkPoints() > vtkPoints.SetData(numpy_to_vtk(np.asarray( > [[0.0, 0.0, 0.0], > [1.0, 0.0, 0.0], > [0.0, 1.0, 0.0], > [1.0, 1.0, 0.0], > [0.0, 0.0, 1.0], > [1.0, 0.0, 1.0], > [0.0, 1.0, 1.0], > [1.0, 1.0, 1.0]]))) > vtkData.SetPoints(vtkPoints) > > elif dataset is vtk.vtkRectilinearGrid: > vtkWriter = vtk.vtkRectilinearGridWriter() > > vtkData.SetDimensions(2,2,2) > vtkData.SetXCoordinates(numpy_to_vtk(np.asarray([0.0, 1.0]))) > vtkData.SetYCoordinates(numpy_to_vtk(np.asarray([0.0, 1.0]))) > vtkData.SetZCoordinates(numpy_to_vtk(np.asarray([0.0, 1.0]))) > > # file scope definition of Pi > vtkArray = numpy_to_vtk(np.asarray(3.141).reshape(1,1),deep=1) > vtkArray.SetName("Pi") > vtkData.GetFieldData().AddArray(vtkArray) > > vtkWriter.SetFileName(str(dataset) + ".vtk") > vtkWriter.SetHeader("") > vtkWriter.SetFileTypeToASCII() > > vtkWriter.SetInput(vtkData) > vtkWriter.Write() > > /endscript > > The files generated from this are > # vtk DataFile Version 3.0 > > ASCII > DATASET POLYDATA > FIELD FieldData 1 > Pi 1 1 double > 3.141 > POINTS 8 double > 0 0 0 1 0 0 0 1 0 > 1 1 0 0 0 1 1 0 1 > 0 1 1 1 1 1 > > # vtk DataFile Version 3.0 > > ASCII > DATASET RECTILINEAR_GRID > FIELD FieldData 1 > Pi 1 1 double > 3.141 > DIMENSIONS 2 2 2 > X_COORDINATES 2 double > 0 1 > Y_COORDINATES 2 double > 0 1 > Z_COORDINATES 2 double > 0 1 > > # vtk DataFile Version 3.0 > > ASCII > DATASET STRUCTURED_POINTS > FIELD FieldData 1 > Pi 1 1 double > 3.141 > DIMENSIONS 2 2 2 > SPACING 1 1 1 > ORIGIN 0 0 0 > > Note the FIELD preceding the dataset details. All files can be read back > into python without problems, but when trying to view each file in using > Paraview 4.3.1, things get interesting: > > - POLYDATA works. > - RECTILINEAR_GRID produces an error (which, btw, contains a typo), > refuses to render anything but displays everything correctly in the > Information tab. > > ERROR: In > /home/kitware/Dashboards/buildbot/paraview-debian4dash-linux-shared-release_qt4_superbuild/source-paraview/VTK/IO/Parallel/vtkPDataSetReader.cxx, > line 701 > vtkPDataSetReader (0x8874010): Expecting 'DIMENSIONS' insted of: FIELD > > - STRUCTURED_POINTS does not produce any errors, still refuses to render > but displays everything correctly in the Information tab. > > If I now (manually) put the FIELDS definition after the dataset details, > everything works fine. > > Is this problem with Paraview, or am I doing something with the vtk > format that should not be possible at all? I got the idea from > http://www.visitusers.org/index.php?title=Time_and_Cycle_in_VTK_files. > > Thanks > Raphael > > Software versions: > > Paraview 4.3.1 Linux 64bit > > Python 2.7.8 |Anaconda 2.1.0 (64-bit)| (default, Aug 21 2014, 18:22:21) > [GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] on linux2 > > vtk.vtkVersion().GetVTKVersion() > '5.10.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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From raphael.schubert at iwm.fraunhofer.de Fri Aug 7 05:01:57 2015 From: raphael.schubert at iwm.fraunhofer.de (Schubert, Raphael) Date: Fri, 7 Aug 2015 09:01:57 +0000 Subject: [Paraview] (no subject) In-Reply-To: References: <13DD8C6B6309B94AA144319F72195FFD3731A238@IWMDAG2.iwm.fraunhofer.de>, Message-ID: <13DD8C6B6309B94AA144319F72195FFD3731A521@IWMDAG2.iwm.fraunhofer.de> The way I understand the file format specification it should be illegal to define a FIELD dataset in addition to, e.g, STRUCTURED_POINTS, as I can find it neither explicitly allowed (there is only mention of one dataset per file) nor presented in an example. It therefore seems like an accidental feature in vtk that I can actually read back the produced files. Am I missing something in the file format? Maybe I presented this poorly, please let me give another example with additional point data, also straight out of python. Here are two fields, one in the dataset section, and one in the point data section. By my reading of the file format spec, the field in the dataset section should not be permitted to be there, even after the details for the STRUCTURED_POINTS. # vtk DataFile Version 3.0 ASCII DATASET STRUCTURED_POINTS FIELD FieldData 1 Pi 1 1 double 3.141 DIMENSIONS 2 2 2 SPACING 1 1 1 ORIGIN 0 0 0 POINT_DATA 8 FIELD FieldData 1 Index 1 8 long 0 1 2 3 4 5 6 7 ________________________________ Von: Dan Lipsa [dan.lipsa at kitware.com] Gesendet: Freitag, 7. August 2015 05:11 Bis: Schubert, Raphael; paraview at paraview.org; vtkusers at vtk.org Betreff: Re: [Paraview] (no subject) Raphael, Indeed, the FIELD definitions have to be after the dataset details according to: http://www.vtk.org/wp-content/uploads/2015/04/file-formats.pdf On Thu, Aug 6, 2015 at 11:14 AM Schubert, Raphael > wrote: I use the following script to generate three vtk files containing different dataset types and an additional FIELD. import numpy as np import vtk from vtk.util.numpy_support import numpy_to_vtk for dataset in (vtk.vtkStructuredPoints, vtk.vtkRectilinearGrid, vtk.vtkPolyData): vtkData = dataset() if dataset is vtk.vtkStructuredPoints: vtkWriter = vtk.vtkStructuredPointsWriter() vtkData.SetOrigin(0.0, 0.0, 0.0) vtkData.SetSpacing(1.0, 1.0, 1.0) vtkData.SetExtent(0, 1, 0, 1, 0, 1) elif dataset is vtk.vtkPolyData: vtkWriter = vtk.vtkPolyDataWriter() vtkPoints = vtk.vtkPoints() vtkPoints.SetData(numpy_to_vtk(np.asarray( [[0.0, 0.0, 0.0], [1.0, 0.0, 0.0], [0.0, 1.0, 0.0], [1.0, 1.0, 0.0], [0.0, 0.0, 1.0], [1.0, 0.0, 1.0], [0.0, 1.0, 1.0], [1.0, 1.0, 1.0]]))) vtkData.SetPoints(vtkPoints) elif dataset is vtk.vtkRectilinearGrid: vtkWriter = vtk.vtkRectilinearGridWriter() vtkData.SetDimensions(2,2,2) vtkData.SetXCoordinates(numpy_to_vtk(np.asarray([0.0, 1.0]))) vtkData.SetYCoordinates(numpy_to_vtk(np.asarray([0.0, 1.0]))) vtkData.SetZCoordinates(numpy_to_vtk(np.asarray([0.0, 1.0]))) # file scope definition of Pi vtkArray = numpy_to_vtk(np.asarray(3.141).reshape(1,1),deep=1) vtkArray.SetName("Pi") vtkData.GetFieldData().AddArray(vtkArray) vtkWriter.SetFileName(str(dataset) + ".vtk") vtkWriter.SetHeader("") vtkWriter.SetFileTypeToASCII() vtkWriter.SetInput(vtkData) vtkWriter.Write() /endscript The files generated from this are # vtk DataFile Version 3.0 ASCII DATASET POLYDATA FIELD FieldData 1 Pi 1 1 double 3.141 POINTS 8 double 0 0 0 1 0 0 0 1 0 1 1 0 0 0 1 1 0 1 0 1 1 1 1 1 # vtk DataFile Version 3.0 ASCII DATASET RECTILINEAR_GRID FIELD FieldData 1 Pi 1 1 double 3.141 DIMENSIONS 2 2 2 X_COORDINATES 2 double 0 1 Y_COORDINATES 2 double 0 1 Z_COORDINATES 2 double 0 1 # vtk DataFile Version 3.0 ASCII DATASET STRUCTURED_POINTS FIELD FieldData 1 Pi 1 1 double 3.141 DIMENSIONS 2 2 2 SPACING 1 1 1 ORIGIN 0 0 0 Note the FIELD preceding the dataset details. All files can be read back into python without problems, but when trying to view each file in using Paraview 4.3.1, things get interesting: - POLYDATA works. - RECTILINEAR_GRID produces an error (which, btw, contains a typo), refuses to render anything but displays everything correctly in the Information tab. ERROR: In /home/kitware/Dashboards/buildbot/paraview-debian4dash-linux-shared-release_qt4_superbuild/source-paraview/VTK/IO/Parallel/vtkPDataSetReader.cxx, line 701 vtkPDataSetReader (0x8874010): Expecting 'DIMENSIONS' insted of: FIELD - STRUCTURED_POINTS does not produce any errors, still refuses to render but displays everything correctly in the Information tab. If I now (manually) put the FIELDS definition after the dataset details, everything works fine. Is this problem with Paraview, or am I doing something with the vtk format that should not be possible at all? I got the idea from http://www.visitusers.org/index.php?title=Time_and_Cycle_in_VTK_files. Thanks Raphael Software versions: Paraview 4.3.1 Linux 64bit Python 2.7.8 |Anaconda 2.1.0 (64-bit)| (default, Aug 21 2014, 18:22:21) [GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] on linux2 vtk.vtkVersion().GetVTKVersion() '5.10.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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Fri Aug 7 10:04:50 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 7 Aug 2015 10:04:50 -0400 Subject: [Paraview] [vtkusers] (no subject) In-Reply-To: <13DD8C6B6309B94AA144319F72195FFD3731A521@IWMDAG2.iwm.fraunhofer.de> References: <13DD8C6B6309B94AA144319F72195FFD3731A238@IWMDAG2.iwm.fraunhofer.de> <13DD8C6B6309B94AA144319F72195FFD3731A521@IWMDAG2.iwm.fraunhofer.de> Message-ID: A single data set has three FIELDs, one the collection of arrays that are aligned with the geometry(ie points ie nodes) (vtkPointData), one the collection of arrays that are aligned with the connectivity (aka cells aka elements) (vtkCellData) and another the collection of arrays which are not aligned with anything other than the data set (vtkFieldData). You may have found a bug in the writer. Would you mind filing a bug report and referencing the email thread? cheers David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Aug 7, 2015 at 5:01 AM, Schubert, Raphael < raphael.schubert at iwm.fraunhofer.de> wrote: > The way I understand the file format specification it should be illegal to > define a FIELD dataset in addition to, e.g, STRUCTURED_POINTS, as I can > find it neither explicitly allowed (there is only mention of one dataset > per file) nor presented in an example. It therefore seems like an > accidental feature in vtk that I can actually read back the produced files. > > Am I missing something in the file format? > > Maybe I presented this poorly, please let me give another example with > additional point data, also straight out of python. Here are two fields, > one in the dataset section, and one in the point data section. By my > reading of the file format spec, the field in the dataset section should > not be permitted to be there, even after the details for the > STRUCTURED_POINTS. > > # vtk DataFile Version 3.0 > > ASCII > DATASET STRUCTURED_POINTS > FIELD FieldData 1 > Pi 1 1 double > 3.141 > DIMENSIONS 2 2 2 > SPACING 1 1 1 > ORIGIN 0 0 0 > POINT_DATA 8 > FIELD FieldData 1 > Index 1 8 long > 0 1 2 3 4 5 6 7 > ------------------------------ > *Von:* Dan Lipsa [dan.lipsa at kitware.com] > *Gesendet:* Freitag, 7. August 2015 05:11 > *Bis:* Schubert, Raphael; paraview at paraview.org; vtkusers at vtk.org > *Betreff:* Re: [Paraview] (no subject) > > Raphael, > Indeed, the FIELD definitions have to be after the dataset details > according to: > > http://www.vtk.org/wp-content/uploads/2015/04/file-formats.pdf > > > > On Thu, Aug 6, 2015 at 11:14 AM Schubert, Raphael < > raphael.schubert at iwm.fraunhofer.de> wrote: > >> I use the following script to generate three vtk files containing >> different dataset types and an additional FIELD. >> >> import numpy as np >> import vtk >> from vtk.util.numpy_support import numpy_to_vtk >> >> for dataset in (vtk.vtkStructuredPoints, >> vtk.vtkRectilinearGrid, >> vtk.vtkPolyData): >> >> vtkData = dataset() >> >> if dataset is vtk.vtkStructuredPoints: >> vtkWriter = vtk.vtkStructuredPointsWriter() >> >> vtkData.SetOrigin(0.0, 0.0, 0.0) >> vtkData.SetSpacing(1.0, 1.0, 1.0) >> vtkData.SetExtent(0, 1, 0, 1, 0, 1) >> >> elif dataset is vtk.vtkPolyData: >> vtkWriter = vtk.vtkPolyDataWriter() >> >> vtkPoints = vtk.vtkPoints() >> vtkPoints.SetData(numpy_to_vtk(np.asarray( >> [[0.0, 0.0, 0.0], >> [1.0, 0.0, 0.0], >> [0.0, 1.0, 0.0], >> [1.0, 1.0, 0.0], >> [0.0, 0.0, 1.0], >> [1.0, 0.0, 1.0], >> [0.0, 1.0, 1.0], >> [1.0, 1.0, 1.0]]))) >> vtkData.SetPoints(vtkPoints) >> >> elif dataset is vtk.vtkRectilinearGrid: >> vtkWriter = vtk.vtkRectilinearGridWriter() >> >> vtkData.SetDimensions(2,2,2) >> vtkData.SetXCoordinates(numpy_to_vtk(np.asarray([0.0, 1.0]))) >> vtkData.SetYCoordinates(numpy_to_vtk(np.asarray([0.0, 1.0]))) >> vtkData.SetZCoordinates(numpy_to_vtk(np.asarray([0.0, 1.0]))) >> >> # file scope definition of Pi >> vtkArray = numpy_to_vtk(np.asarray(3.141).reshape(1,1),deep=1) >> vtkArray.SetName("Pi") >> vtkData.GetFieldData().AddArray(vtkArray) >> >> vtkWriter.SetFileName(str(dataset) + ".vtk") >> vtkWriter.SetHeader("") >> vtkWriter.SetFileTypeToASCII() >> >> vtkWriter.SetInput(vtkData) >> vtkWriter.Write() >> >> /endscript >> >> The files generated from this are >> # vtk DataFile Version 3.0 >> >> ASCII >> DATASET POLYDATA >> FIELD FieldData 1 >> Pi 1 1 double >> 3.141 >> POINTS 8 double >> 0 0 0 1 0 0 0 1 0 >> 1 1 0 0 0 1 1 0 1 >> 0 1 1 1 1 1 >> >> # vtk DataFile Version 3.0 >> >> ASCII >> DATASET RECTILINEAR_GRID >> FIELD FieldData 1 >> Pi 1 1 double >> 3.141 >> DIMENSIONS 2 2 2 >> X_COORDINATES 2 double >> 0 1 >> Y_COORDINATES 2 double >> 0 1 >> Z_COORDINATES 2 double >> 0 1 >> >> # vtk DataFile Version 3.0 >> >> ASCII >> DATASET STRUCTURED_POINTS >> FIELD FieldData 1 >> Pi 1 1 double >> 3.141 >> DIMENSIONS 2 2 2 >> SPACING 1 1 1 >> ORIGIN 0 0 0 >> >> Note the FIELD preceding the dataset details. All files can be read back >> into python without problems, but when trying to view each file in using >> Paraview 4.3.1, things get interesting: >> >> - POLYDATA works. >> - RECTILINEAR_GRID produces an error (which, btw, contains a typo), >> refuses to render anything but displays everything correctly in the >> Information tab. >> >> ERROR: In >> /home/kitware/Dashboards/buildbot/paraview-debian4dash-linux-shared-release_qt4_superbuild/source-paraview/VTK/IO/Parallel/vtkPDataSetReader.cxx, >> line 701 >> vtkPDataSetReader (0x8874010): Expecting 'DIMENSIONS' insted of: FIELD >> >> - STRUCTURED_POINTS does not produce any errors, still refuses to render >> but displays everything correctly in the Information tab. >> >> If I now (manually) put the FIELDS definition after the dataset details, >> everything works fine. >> >> Is this problem with Paraview, or am I doing something with the vtk >> format that should not be possible at all? I got the idea from >> http://www.visitusers.org/index.php?title=Time_and_Cycle_in_VTK_files. >> >> Thanks >> Raphael >> >> Software versions: >> >> Paraview 4.3.1 Linux 64bit >> >> Python 2.7.8 |Anaconda 2.1.0 (64-bit)| (default, Aug 21 2014, 18:22:21) >> [GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] on linux2 >> >> vtk.vtkVersion().GetVTKVersion() >> '5.10.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 VTK FAQ at: > http://www.vtk.org/Wiki/VTK_FAQ > > Search the list archives at: http://markmail.org/search/?q=vtkusers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtkusers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Fri Aug 7 10:16:31 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Fri, 07 Aug 2015 14:16:31 +0000 Subject: [Paraview] [vtkusers] (no subject) In-Reply-To: <13DD8C6B6309B94AA144319F72195FFD3731A521@IWMDAG2.iwm.fraunhofer.de> References: <13DD8C6B6309B94AA144319F72195FFD3731A238@IWMDAG2.iwm.fraunhofer.de> <13DD8C6B6309B94AA144319F72195FFD3731A521@IWMDAG2.iwm.fraunhofer.de> Message-ID: Hi Raphael, On Fri, Aug 7, 2015 at 5:02 AM Schubert, Raphael < raphael.schubert at iwm.fraunhofer.de> wrote: > The way I understand the file format specification it should be illegal to > define a FIELD dataset in addition to, e.g, STRUCTURED_POINTS, as I can > find it neither explicitly allowed (there is only mention of one dataset > per file) nor presented in an example. It therefore seems like an > accidental feature in vtk that I can actually read back the produced files. > A FIELD dataset is a way to specify data without topological or geometrical structure. One can also define FIELD arrays after CELL_DATA or POINT_DATA for a dataset. Look at the first example on page 7. In the CELL_DATA section there is a field arrays. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Fri Aug 7 12:39:28 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Fri, 07 Aug 2015 16:39:28 +0000 Subject: [Paraview] [vtkusers] (no subject) In-Reply-To: References: <13DD8C6B6309B94AA144319F72195FFD3731A238@IWMDAG2.iwm.fraunhofer.de> <13DD8C6B6309B94AA144319F72195FFD3731A521@IWMDAG2.iwm.fraunhofer.de> Message-ID: Raphael, In talking to Dave, it seems that indeed you have found a bug in the writer (and in the specification). It does not seem to be a way to save field data unless your dataset is of type FIELD (a collection of arrays). The arrays attached to POINT_DATA (or CELL_DATA) which are designated as FIELD have to have the same number of tuples as the points (or cells). The terminology is kind of confusing as well. Would you mind filing a bug report. Thanks, Dan On Fri, Aug 7, 2015 at 10:16 AM Dan Lipsa wrote: > Hi Raphael, > > On Fri, Aug 7, 2015 at 5:02 AM Schubert, Raphael < > raphael.schubert at iwm.fraunhofer.de> wrote: > >> The way I understand the file format specification it should be illegal >> to define a FIELD dataset in addition to, e.g, STRUCTURED_POINTS, as I can >> find it neither explicitly allowed (there is only mention of one dataset >> per file) nor presented in an example. It therefore seems like an >> accidental feature in vtk that I can actually read back the produced files. >> > > A FIELD dataset is a way to specify data without topological or > geometrical structure. One can also define FIELD arrays after CELL_DATA or > POINT_DATA for a dataset. Look at the first example on page 7. In the > CELL_DATA section there is a field arrays. > > > >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Fri Aug 7 13:08:32 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Fri, 7 Aug 2015 13:08:32 -0400 Subject: [Paraview] vtkTransmitImageDataPiece question In-Reply-To: <55C100EE.50807@nasa.gov> References: <55C100EE.50807@nasa.gov> Message-ID: Hey Jeff, Can you clarify a bit? What kind of wrong is the output? Also, I would probably do this a bit differently, assuming you use a newer ParaView (>= 4.2). The issue is that vtkTransmitImageDataPiece is not a "CAN_PRODUCE_SUB_EXTENT()" filter. Rather it is a "CAN_HANDLE_PIECE_REQUEST()" filter. Meaning that it wants to determine the extents of the output based on the piece request it receives. So some changes: * Swap CAN_PRODUCE_SUB_EXTENT() with CAN_HANDLE_PIECE_REQUEST() in request info. * In the main script, do something like this: executive = self.GetExecutive() outInfo = executive.GetOutputInformation(0) #updateExtent = [executive.UPDATE_EXTENT().Get(outInfo, i) for i in xrange(6)] #imageData = self.GetOutput() #imageData.SetExtent(updateExtent) # >> this probably needs to happen on rank 0 only myout = ns.numpy_to_vtk(bmag.ravel(),1,vtk.VTK_FLOAT) myout.SetName("B field magnitude") imageData.GetPointData().SetScalars(myout) tp = vtk.vtkTrivialProducer() tp.SetOutput(imageData) tp.SetWholeExtent(0, mesh.MX-1, 0, mesh.MY-1, 0, mesh.MZ-1) xmit = vtk.vtkTransmitImageDataPiece() xmit.SetInputConnection(tp.GetOutputPort()) xmit.UpdateInformation() xmit.SetUpdateExtent(rank, nranks, 0) xmit.Update() self.GetOutput().ShallowCopy(xmit,GetOutput()) I didn't verify the code so it may need tweaking. Best, -berk On Tue, Aug 4, 2015 at 2:14 PM, Jeff Becker wrote: > Hi. I'm trying to run a Python Programmable source across four nodes > (started with mpirun -np 4 pvserver). My script contains the following > code, but the output looks wrong, so I'm not sure if the extents are > right. The partitioning among nodes is correct (using processId filter). > Also I'm careful to set Output Data Set Type to vtkImageData. > > import vtk > import vtk.util.numpy_support as ns > contr = vtk.vtkMultiProcessController.GetGlobalController() > nranks = contr.GetNumberOfProcesses() > rank = contr.GetLocalProcessId() > > ... > executive = self.GetExecutive() > outInfo = executive.GetOutputInformation(0) > updateExtent = [executive.UPDATE_EXTENT().Get(outInfo, i) for i in > xrange(6)] > imageData = self.GetOutput() > imageData.SetExtent(updateExtent) > myout = ns.numpy_to_vtk(bmag.ravel(),1,vtk.VTK_FLOAT) > myout.SetName("B field magnitude") > imageData.GetPointData().SetScalars(myout) > tp = vtk.vtkTrivialProducer() > tp.SetOutput(imageData) > tp.SetWholeExtent(0, mesh.MX-1, 0, mesh.MY-1, 0, mesh.MZ-1) > xmit = vtk.vtkTransmitImageDataPiece() > xmit.SetInputConnection(tp.GetOutputPort()) > xmit.UpdateInformation() > xmit.SetUpdateExtent(rank, nranks, 0) > xmit.Update() > > For completeness, here is my requestInformation script (mesh has > dimensions, and coordinate arrays for each of X,Y,Z) > > executive = self.GetExecutive() > outInfo = executive.GetOutputInformation(0) > outInfo.Set(vtk.vtkAlgorithm.CAN_PRODUCE_SUB_EXTENT(), 1) > outInfo.Set(executive.WHOLE_EXTENT(), 0, mesh.MX-1, 0, mesh.MY-1, 0, > mesh.MZ-1) > xspacing = (mesh.xcoords[-1] - mesh.xcoords[0])/mesh.MX > yspacing = (mesh.ycoords[-1] - mesh.ycoords[0])/mesh.MY > zspacing = (mesh.zcoords[-1] - mesh.zcoords[0])/mesh.MZ > outInfo.Set(vtk.vtkDataObject.SPACING(), xspacing, yspacing, zspacing) > > This is what I've been able to come up with after spending much time > reading documentation and examples, but I've obviously missed something. > Please advise. 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: From utkarsh.ayachit at kitware.com Fri Aug 7 13:32:35 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 7 Aug 2015 13:32:35 -0400 Subject: [Paraview] Differences between OpenGL and OpenGL2 versions of ParaView In-Reply-To: References: <3b80307dd0184a7081060df719e33861@MAIL06V-CAS04.fnal.gov> Message-ID: Adam, The problem is that the OpenGL2 implementation doesn't work correctly for field-data arrays yet. I've reported a bug: http://www.paraview.org/Bug/view.php?id=15627 We'll have in tracked down soon. Utkarsh On Mon, Aug 3, 2015 at 2:59 PM, Adam Lyon wrote: > Hi Joachim, Do you want me to send in a bug report for these problems? I > assume there's no work-around that I can do to make things work. Using > OpenGL2 is quite a bit faster, so I'm hoping a fix can come out soon. > 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 | Facebook > | Twitter > > > On Fri, Jul 31, 2015 at 10:53 AM, Adam L Lyon wrote: > >> 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 | Facebook >> | Twitter >> >> >> 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 * >>> >>> >>> 2015-07-30 22:19 GMT+02:00 Adam Lyon : >>> >>>> 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 | Facebook >>>> | Twitter >>>> >>>> >>>> _______________________________________________ >>>> 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: gm2ringsim_opengl_good.png Type: image/png Size: 19431 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: gm2ringsim_opengl2_bad.png Type: image/png Size: 16709 bytes Desc: not available URL: From jeffrey.c.becker at nasa.gov Fri Aug 7 13:47:04 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Fri, 7 Aug 2015 10:47:04 -0700 Subject: [Paraview] vtkTransmitImageDataPiece question In-Reply-To: References: <55C100EE.50807@nasa.gov> Message-ID: <55C4EF18.7050102@nasa.gov> Hi Berk, On 08/07/2015 10:08 AM, Berk Geveci wrote: > Hey Jeff, > > Can you clarify a bit? What kind of wrong is the output? I have an updated report in the mail I sent to the list on Wednesday. I will forward you that directly. Please see updated code in that mail. Right now, if I run my script on two processors, it looks like both processors get the same half of the data. In the meantime, I will try to incorporate your suggestion below. Thanks. -jeff > > Also, I would probably do this a bit differently, assuming you use a > newer ParaView (>= 4.2). The issue is that vtkTransmitImageDataPiece > is not a "CAN_PRODUCE_SUB_EXTENT()" filter. Rather it is a > "CAN_HANDLE_PIECE_REQUEST()" filter. Meaning that it wants to > determine the extents of the output based on the piece request it > receives. So some changes: > > * Swap CAN_PRODUCE_SUB_EXTENT() with CAN_HANDLE_PIECE_REQUEST() in > request info. > * In the main script, do something like this: > > executive = self.GetExecutive() > outInfo = executive.GetOutputInformation(0) > #updateExtent = [executive.UPDATE_EXTENT().Get(outInfo, i) for i in > xrange(6)] > #imageData = self.GetOutput() > #imageData.SetExtent(updateExtent) > # >> this probably needs to happen on rank 0 only > myout = ns.numpy_to_vtk(bmag.ravel(),1,vtk.VTK_FLOAT) > myout.SetName("B field magnitude") > imageData.GetPointData().SetScalars(myout) > tp = vtk.vtkTrivialProducer() > tp.SetOutput(imageData) > tp.SetWholeExtent(0, mesh.MX-1, 0, mesh.MY-1, 0, mesh.MZ-1) > xmit = vtk.vtkTransmitImageDataPiece() > xmit.SetInputConnection(tp.GetOutputPort()) > xmit.UpdateInformation() > xmit.SetUpdateExtent(rank, nranks, 0) > xmit.Update() > self.GetOutput().ShallowCopy(xmit,GetOutput()) > > I didn't verify the code so it may need tweaking. > > Best, > -berk > > > On Tue, Aug 4, 2015 at 2:14 PM, Jeff Becker > wrote: > > Hi. I'm trying to run a Python Programmable source across four > nodes (started with mpirun -np 4 pvserver). My script contains the > following code, but the output looks wrong, so I'm not sure if the > extents are right. The partitioning among nodes is correct (using > processId filter). Also I'm careful to set Output Data Set Type to > vtkImageData. > > import vtk > import vtk.util.numpy_support as ns > contr = vtk.vtkMultiProcessController.GetGlobalController() > nranks = contr.GetNumberOfProcesses() > rank = contr.GetLocalProcessId() > > ... > executive = self.GetExecutive() > outInfo = executive.GetOutputInformation(0) > updateExtent = [executive.UPDATE_EXTENT().Get(outInfo, i) for i in > xrange(6)] > imageData = self.GetOutput() > imageData.SetExtent(updateExtent) > myout = ns.numpy_to_vtk(bmag.ravel(),1,vtk.VTK_FLOAT) > myout.SetName("B field magnitude") > imageData.GetPointData().SetScalars(myout) > tp = vtk.vtkTrivialProducer() > tp.SetOutput(imageData) > tp.SetWholeExtent(0, mesh.MX-1, 0, mesh.MY-1, 0, mesh.MZ-1) > xmit = vtk.vtkTransmitImageDataPiece() > xmit.SetInputConnection(tp.GetOutputPort()) > xmit.UpdateInformation() > xmit.SetUpdateExtent(rank, nranks, 0) > xmit.Update() > > For completeness, here is my requestInformation script (mesh has > dimensions, and coordinate arrays for each of X,Y,Z) > > executive = self.GetExecutive() > outInfo = executive.GetOutputInformation(0) > outInfo.Set(vtk.vtkAlgorithm.CAN_PRODUCE_SUB_EXTENT(), 1) > outInfo.Set(executive.WHOLE_EXTENT(), 0, mesh.MX-1, 0, mesh.MY-1, > 0, mesh.MZ-1) > xspacing = (mesh.xcoords[-1] - mesh.xcoords[0])/mesh.MX > yspacing = (mesh.ycoords[-1] - mesh.ycoords[0])/mesh.MY > zspacing = (mesh.zcoords[-1] - mesh.zcoords[0])/mesh.MZ > outInfo.Set(vtk.vtkDataObject.SPACING(), xspacing, yspacing, zspacing) > > This is what I've been able to come up with after spending much > time reading documentation and examples, but I've obviously missed > something. Please advise. 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: From lyon at fnal.gov Fri Aug 7 13:53:17 2015 From: lyon at fnal.gov (Adam Lyon) Date: Fri, 7 Aug 2015 12:53:17 -0500 Subject: [Paraview] Differences between OpenGL and OpenGL2 versions of ParaView In-Reply-To: <39f822d31fde44f480e4a52108b21e0d@MAIL06V-CAS04.fnal.gov> References: <3b80307dd0184a7081060df719e33861@MAIL06V-CAS04.fnal.gov> <39f822d31fde44f480e4a52108b21e0d@MAIL06V-CAS04.fnal.gov> Message-ID: Awesome! Thanks -- Adam On Friday, August 7, 2015, Utkarsh Ayachit wrote: > Adam, > > The problem is that the OpenGL2 implementation doesn't work correctly for > field-data arrays yet. > I've reported a bug: http://www.paraview.org/Bug/view.php?id=15627 > > We'll have in tracked down soon. > > Utkarsh > > On Mon, Aug 3, 2015 at 2:59 PM, Adam Lyon > wrote: > >> Hi Joachim, Do you want me to send in a bug report for these problems? I >> assume there's no work-around that I can do to make things work. Using >> OpenGL2 is quite a bit faster, so I'm hoping a fix can come out soon. >> 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 | Facebook >> | Twitter >> >> >> On Fri, Jul 31, 2015 at 10:53 AM, Adam L Lyon > > wrote: >> >>> 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 | Facebook >>> | Twitter >>> >>> >>> 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 * >>>> >>>> >>>> 2015-07-30 22:19 GMT+02:00 Adam Lyon >>> >: >>>> >>>>> 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 | Facebook >>>>> | Twitter >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >> >> > -- *------* *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 | Facebook | Twitter -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: gm2ringsim_opengl_good.png Type: image/png Size: 19431 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: gm2ringsim_opengl2_bad.png Type: image/png Size: 16709 bytes Desc: not available URL: From jeffrey.c.becker at nasa.gov Fri Aug 7 14:22:15 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Fri, 7 Aug 2015 11:22:15 -0700 Subject: [Paraview] vtkTransmitImageDataPiece question In-Reply-To: <55C4EF18.7050102@nasa.gov> References: <55C100EE.50807@nasa.gov> <55C4EF18.7050102@nasa.gov> Message-ID: <55C4F757.3080804@nasa.gov> Hi again. I have a quick question below. On 08/07/2015 10:47 AM, Jeff Becker wrote: > Hi Berk, > > On 08/07/2015 10:08 AM, Berk Geveci wrote: >> Hey Jeff, >> >> Can you clarify a bit? What kind of wrong is the output? > > I have an updated report in the mail I sent to the list on Wednesday. > I will forward you that directly. Please see updated code in that > mail. Right now, if I run my script on two processors, it looks like > both processors get the same half of the data. > > In the meantime, I will try to incorporate your suggestion below. Thanks. In your version of my code below, you commented out the line: imagedata = self.GetOutput() I was using the example in: http://www.paraview.org/Wiki/ParaView/Simple_ParaView_3_Python_Filters#Producing_Image_Data_.28Source.29 Instead should I generate a new vtkImageData instance? Thanks again, -jeff > > -jeff >> >> Also, I would probably do this a bit differently, assuming you use a >> newer ParaView (>= 4.2). The issue is that vtkTransmitImageDataPiece >> is not a "CAN_PRODUCE_SUB_EXTENT()" filter. Rather it is a >> "CAN_HANDLE_PIECE_REQUEST()" filter. Meaning that it wants to >> determine the extents of the output based on the piece request it >> receives. So some changes: >> >> * Swap CAN_PRODUCE_SUB_EXTENT() with CAN_HANDLE_PIECE_REQUEST() in >> request info. >> * In the main script, do something like this: >> >> executive = self.GetExecutive() >> outInfo = executive.GetOutputInformation(0) >> #updateExtent = [executive.UPDATE_EXTENT().Get(outInfo, i) for i in >> xrange(6)] >> #imageData = self.GetOutput() >> #imageData.SetExtent(updateExtent) >> # >> this probably needs to happen on rank 0 only >> myout = ns.numpy_to_vtk(bmag.ravel(),1,vtk.VTK_FLOAT) >> myout.SetName("B field magnitude") >> imageData.GetPointData().SetScalars(myout) >> tp = vtk.vtkTrivialProducer() >> tp.SetOutput(imageData) >> tp.SetWholeExtent(0, mesh.MX-1, 0, mesh.MY-1, 0, mesh.MZ-1) >> xmit = vtk.vtkTransmitImageDataPiece() >> xmit.SetInputConnection(tp.GetOutputPort()) >> xmit.UpdateInformation() >> xmit.SetUpdateExtent(rank, nranks, 0) >> xmit.Update() >> self.GetOutput().ShallowCopy(xmit,GetOutput()) >> >> I didn't verify the code so it may need tweaking. >> >> Best, >> -berk >> >> >> On Tue, Aug 4, 2015 at 2:14 PM, Jeff Becker >> > wrote: >> >> Hi. I'm trying to run a Python Programmable source across four >> nodes (started with mpirun -np 4 pvserver). My script contains >> the following code, but the output looks wrong, so I'm not sure >> if the extents are right. The partitioning among nodes is >> correct (using processId filter). Also I'm careful to set Output >> Data Set Type to vtkImageData. >> >> import vtk >> import vtk.util.numpy_support as ns >> contr = vtk.vtkMultiProcessController.GetGlobalController() >> nranks = contr.GetNumberOfProcesses() >> rank = contr.GetLocalProcessId() >> >> ... >> executive = self.GetExecutive() >> outInfo = executive.GetOutputInformation(0) >> updateExtent = [executive.UPDATE_EXTENT().Get(outInfo, i) for i >> in xrange(6)] >> imageData = self.GetOutput() >> imageData.SetExtent(updateExtent) >> myout = ns.numpy_to_vtk(bmag.ravel(),1,vtk.VTK_FLOAT) >> myout.SetName("B field magnitude") >> imageData.GetPointData().SetScalars(myout) >> tp = vtk.vtkTrivialProducer() >> tp.SetOutput(imageData) >> tp.SetWholeExtent(0, mesh.MX-1, 0, mesh.MY-1, 0, mesh.MZ-1) >> xmit = vtk.vtkTransmitImageDataPiece() >> xmit.SetInputConnection(tp.GetOutputPort()) >> xmit.UpdateInformation() >> xmit.SetUpdateExtent(rank, nranks, 0) >> xmit.Update() >> >> For completeness, here is my requestInformation script (mesh has >> dimensions, and coordinate arrays for each of X,Y,Z) >> >> executive = self.GetExecutive() >> outInfo = executive.GetOutputInformation(0) >> outInfo.Set(vtk.vtkAlgorithm.CAN_PRODUCE_SUB_EXTENT(), 1) >> outInfo.Set(executive.WHOLE_EXTENT(), 0, mesh.MX-1, 0, mesh.MY-1, >> 0, mesh.MZ-1) >> xspacing = (mesh.xcoords[-1] - mesh.xcoords[0])/mesh.MX >> yspacing = (mesh.ycoords[-1] - mesh.ycoords[0])/mesh.MY >> zspacing = (mesh.zcoords[-1] - mesh.zcoords[0])/mesh.MZ >> outInfo.Set(vtk.vtkDataObject.SPACING(), xspacing, yspacing, >> zspacing) >> >> This is what I've been able to come up with after spending much >> time reading documentation and examples, but I've obviously >> missed something. Please advise. 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: From cory.quammen at kitware.com Fri Aug 7 14:32:11 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 7 Aug 2015 14:32:11 -0400 Subject: [Paraview] [BUG] segfault playing a simulation In-Reply-To: <55BE4829.5030209@gmail.com> References: <55895735.2030202@gmail.com> <559381DE.5030504@gmail.com> <559422EF.3070304@gmail.com> <55A0E2AE.5050101@gmail.com> <55A9056C.2000101@gmail.com> <55A90F76.8000804@gmail.com> <55B20445.7060809@gmail.com> <55BE4829.5030209@gmail.com> Message-ID: Sergi, Thanks for investigating and posting the information. I will take a look. - Cory On Sun, Aug 2, 2015 at 12:41 PM, Sergi Mateo Bellido < sergi.mateo.bellido at gmail.com> wrote: > Hi, > > After a few hours debugging ParaView's code I think that I finally found > the bug! :) > > The problem is that the meaning of the piece extent changes depending on > if the piece has the whole dimensions or only a portion of them. For > example, imagine that we have the following *.pvti file: > > > > > > > > > > > > In this case, the dimensions of the pieces are: > 1st piece -> [0..200], [0..200], [0..101) > 2nd piece -> [0..200], [0..200], [101..200] > > Note that the last dimension range of the 1st piece doesn't include the > 101 value which is included in the 2nd piece. > > The issue here is that the code is not taking into account this when it's > computing the dimensions of the current piece. In file > VTK/IO/XML/vtkXMLPStructuredDataReader.cxx:155 we have the next call to > 'ComputePointDimensions' function: > > this->ComputePointDimensions(this->SubExtent, this->SubPointDimensions); > > I printed the values of 'this->SubExtent' and they were the same values > specified in the Piece Extent field: > > (gdb) p SubExtent > $1 = {0, 200, 0, 200, 0, 101} > > For these values, the 'ComputePointDimensions' function, which is defined > in VTK/IO/XML/vtkXMLReader.cxx:916, computed the next dimensions: > > (gdb) p this->SubPointDimensions > $2 = {201, 201, 102} > > How these values are computed is very simple: upper_bound - lower_bound + > 1. Note that the value of the third dimension is wrong: it should be 101 > instead of 102. > > Finally, the segfault is produced in the 'CopySubExtent' function, which > is defined in VTK/IO/XML/vtkXMLPStructuredDataReader.cxx:342, because > SubPointDimensions information is used to copy the regions and we are doing > an extra copy (loop defined in 371 line). > > Could you confirm me this bug? > > Best regards, > > Sergi Mateo > > PS1: Source references are related to the last version of ParaView's > source published in your webpage: > http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.3&type=source&os=all&downloadFile=ParaView-v4.3.1-source.tar.gz > > PS2: You can reproduce this bug using one of the examples that I sent you > in my previous emails. > > On 07/24/2015 11:24 AM, Sergi Mateo Bellido wrote: > > 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> 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&, bool) >>>>> [(libQtGui.so.4) ???:-1] >>>>> 0x7f54d019ca94 : ??? [(???) ???:-1] >>>>> 0x7f54d019b877 : QApplication::x11ProcessEvent(_XEvent*) >>>>> [(libQtGui.so.4) ???:-1] >>>>> 0x7f54d01c4805 : ??? [(???) ???:-1] >>>>> 0x7f54cfa7f375 : >>>>> QEventLoop::processEvents(QFlags) >>>>> [(libQtCore.so.4) ???:-1] >>>>> 0x7f54cfa7f748 : >>>>> QEventLoop::exec(QFlags) [(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. > > > > > > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From haonrolyat at gmail.com Fri Aug 7 15:16:48 2015 From: haonrolyat at gmail.com (Noah Taylor) Date: Fri, 7 Aug 2015 13:16:48 -0600 Subject: [Paraview] ParaView Llvm on Supercomputer Message-ID: Hi All, I have worked with one of the IT persons to finally be able to use the capabilities of ParaView to capture a high resolution image of each time step at the end of my model run on a supercomputer. The problem that I am seeing is that Llvm is taking quite some time per rendered image. I currently only have 1 node with 8 cores that I use to my disposal. I run the script using pvbatch and the xmf read to get like 10 images in 10 minutes. I am asking my IT guy to try and redo the compile so that it enables MPI so I can take advantage of multiple cores. Has any one else tried using Llvm with pvbatch to save out an image per time step? I saw the graph here - http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D - that talks about having 8 - 10 cores seems to be efficient. Would it make sense to span Llvm across mutlple nodes / would it be quicker? Thanks for any input - I am just a little confused on how pvbatch would work between multiple nodes / what command to use. Thanks, Noah -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Fri Aug 7 15:30:03 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 7 Aug 2015 19:30:03 +0000 Subject: [Paraview] [EXTERNAL] ParaView Llvm on Supercomputer In-Reply-To: References: Message-ID: <3868d85f387544d49bab16480f477b03@ES01AMSNLNT.srn.sandia.gov> Noah, I am not going to comment on implementing LLVM/Mesa ? compile and parallel run issues are a pain and generally over my head. A few thoughts. ? If you are not using MPI, you are only using 1 core of your node. ParaView is not multithreaded. Even more than having more nodes, you need to get the cores you have available being used. Then, if you need more speed again, obviously add nodes. ? If you don?t need the memory, and have the data available, do your rendering on a workstation. That should have hardware rendering, which will be much faster. From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Noah Taylor Sent: Friday, August 07, 2015 1:17 PM To: ParaView Subject: [EXTERNAL] [Paraview] ParaView Llvm on Supercomputer Hi All, I have worked with one of the IT persons to finally be able to use the capabilities of ParaView to capture a high resolution image of each time step at the end of my model run on a supercomputer. The problem that I am seeing is that Llvm is taking quite some time per rendered image. I currently only have 1 node with 8 cores that I use to my disposal. I run the script using pvbatch and the xmf read to get like 10 images in 10 minutes. I am asking my IT guy to try and redo the compile so that it enables MPI so I can take advantage of multiple cores. Has any one else tried using Llvm with pvbatch to save out an image per time step? I saw the graph here - http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D - that talks about having 8 - 10 cores seems to be efficient. Would it make sense to span Llvm across mutlple nodes / would it be quicker? Thanks for any input - I am just a little confused on how pvbatch would work between multiple nodes / what command to use. Thanks, Noah -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Fri Aug 7 17:43:26 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 7 Aug 2015 21:43:26 +0000 Subject: [Paraview] [EXTERNAL] Is there a way to make Spreadsheet view Text larger? In-Reply-To: References: Message-ID: <5180abb65ea543939904d76a95bfd7b7@ES01AMSNLNT.srn.sandia.gov> Dennis, I just created a feature request for this. http://www.paraview.org/Bug/view.php?id=15628 Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Dennis Conklin Sent: Thursday, July 30, 2015 12:38 PM To: Paraview (paraview at paraview.org) Subject: [EXTERNAL] [Paraview] Is there a way to make Spreadsheet view Text larger? 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: From zhz1993622 at 163.com Sat Aug 8 00:07:27 2015 From: zhz1993622 at 163.com (=?UTF-8?B?5ZGo5oGS5LyX?=) Date: Sat, 8 Aug 2015 12:07:27 +0800 (CST) Subject: [Paraview] FullScreen and No Boraders In-Reply-To: References: <1d8a719b.e40d.14ef2bf692e.Coremail.zhz1993622@163.com> Message-ID: <2a1f1731.14c3a.14f0b7df364.Coremail.zhz1993622@163.com> you are right?
Thank you? At 2015-08-03 19:55:19, "Utkarsh Ayachit" wrote: >> renderWindow->BordersOff(); >> renderWindow->SetFullScreen(true); > >That should have done the trick. Try moving this code to right after >the RenderWIndow is created i.e. after >vtkSmartPointer::New(); (more specifically, before >the RenderWindowInteractor is setup). If I remember correctly, the >setting up of the interactor does affect the render window state. > >Utkarsh > >On Mon, Aug 3, 2015 at 4:48 AM, ??? wrote: >> >> I want to ask some question about VTK. Now I want to create a >> renderwindow without borders and full of screen . I write code like this: >> vtkSmartPointer sphereSource = >> vtkSmartPointer::New(); >> >> vtkSmartPointer mapper = >> vtkSmartPointer::New(); >> mapper->SetInputConnection(sphereSource->GetOutputPort()); >> >> vtkSmartPointer actor = >> vtkSmartPointer::New(); >> actor->SetMapper(mapper); >> >> vtkSmartPointer renderer = >> vtkSmartPointer::New(); >> vtkSmartPointer renderWindow = >> vtkSmartPointer::New(); >> renderWindow->AddRenderer(renderer); >> vtkSmartPointer renderWindowInteractor = >> vtkSmartPointer::New(); >> renderWindowInteractor->SetRenderWindow(renderWindow); >> >> renderer->AddActor(actor); >> > >> >> renderWindow->Render(); >> renderWindowInteractor->Start(); >> >> But when I run this program . The renderwindow also have borders. >> How can I do to make the renderwindow without borders . Thank you for your >> help. >> >> zhz >> >> >> >> _______________________________________________ >> 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 ondrej.certik at gmail.com Mon Aug 10 10:02:55 2015 From: ondrej.certik at gmail.com (=?UTF-8?B?T25kxZllaiDEjGVydMOtaw==?=) Date: Mon, 10 Aug 2015 08:02:55 -0600 Subject: [Paraview] Make XDMF Sets work in Multi-block Inspector Message-ID: Hi, We would like to use the Multi-block inspector to turn solutions on and off on a given subdomain (set of blocks). Just like it works if you load an Exodus file. We use XDMF and we were told to use Sets to designate subdomains. We did that and indeed they appear in the Multi-block inspector, but unfortunately they do not work to turn solutions on and off. For some reason, they only appear to add geometry *over* the solutions, so you don't see any solutions at all. Only if you turn them off, then you can see the solution on the whole mesh. In particular, you can't use those to turn off a solution on just part of it. Essentially it looks like if Sets created a new geometry without any solutions associated with it (and allow to turn parts of this geometry on and off, as expected), and then visualized it on top of the original mesh+solutions. Any ideas how to resolve that? I tested ParaView 4.3.1. Thanks, Ondrej Certik Los Alamos National Laboratory From cory.quammen at kitware.com Mon Aug 10 11:12:39 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 10 Aug 2015 11:12:39 -0400 Subject: [Paraview] [BUG] segfault playing a simulation In-Reply-To: References: <55895735.2030202@gmail.com> <559381DE.5030504@gmail.com> <559422EF.3070304@gmail.com> <55A0E2AE.5050101@gmail.com> <55A9056C.2000101@gmail.com> <55A90F76.8000804@gmail.com> <55B20445.7060809@gmail.com> <55BE4829.5030209@gmail.com> Message-ID: Sergi, Quick update: I'm having even stranger behavior than a crash. When I load the ascii files you sent in mpi_test.tar.gz with ParaView running with the built-in server, I can see the different values of "var" for the first and second blocks (0 and 1, respectively). The same is true when I run a separate pvserver and connect to it from the client. However, when I connect to a server running with mpirun -np2 pvserver "var" has only the value 0. This same behavior occurs for the zipped_binary and raw_binary files as well. I'll look into it some more. Thanks, Cory On Fri, Aug 7, 2015 at 2:32 PM, Cory Quammen wrote: > Sergi, > > Thanks for investigating and posting the information. I will take a look. > > - Cory > > On Sun, Aug 2, 2015 at 12:41 PM, Sergi Mateo Bellido < > sergi.mateo.bellido at gmail.com> wrote: > >> Hi, >> >> After a few hours debugging ParaView's code I think that I finally found >> the bug! :) >> >> The problem is that the meaning of the piece extent changes depending on >> if the piece has the whole dimensions or only a portion of them. For >> example, imagine that we have the following *.pvti file: >> >> >> >> >> >> >> >> >> >> >> >> In this case, the dimensions of the pieces are: >> 1st piece -> [0..200], [0..200], [0..101) >> 2nd piece -> [0..200], [0..200], [101..200] >> >> Note that the last dimension range of the 1st piece doesn't include the >> 101 value which is included in the 2nd piece. >> >> The issue here is that the code is not taking into account this when it's >> computing the dimensions of the current piece. In file >> VTK/IO/XML/vtkXMLPStructuredDataReader.cxx:155 we have the next call to >> 'ComputePointDimensions' function: >> >> this->ComputePointDimensions(this->SubExtent, this->SubPointDimensions); >> >> I printed the values of 'this->SubExtent' and they were the same values >> specified in the Piece Extent field: >> >> (gdb) p SubExtent >> $1 = {0, 200, 0, 200, 0, 101} >> >> For these values, the 'ComputePointDimensions' function, which is defined >> in VTK/IO/XML/vtkXMLReader.cxx:916, computed the next dimensions: >> >> (gdb) p this->SubPointDimensions >> $2 = {201, 201, 102} >> >> How these values are computed is very simple: upper_bound - lower_bound + >> 1. Note that the value of the third dimension is wrong: it should be 101 >> instead of 102. >> >> Finally, the segfault is produced in the 'CopySubExtent' function, which >> is defined in VTK/IO/XML/vtkXMLPStructuredDataReader.cxx:342, because >> SubPointDimensions information is used to copy the regions and we are doing >> an extra copy (loop defined in 371 line). >> >> Could you confirm me this bug? >> >> Best regards, >> >> Sergi Mateo >> >> PS1: Source references are related to the last version of ParaView's >> source published in your webpage: >> http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.3&type=source&os=all&downloadFile=ParaView-v4.3.1-source.tar.gz >> >> PS2: You can reproduce this bug using one of the examples that I sent you >> in my previous emails. >> >> On 07/24/2015 11:24 AM, Sergi Mateo Bellido wrote: >> >> 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> 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&, bool) >>>>>> [(libQtGui.so.4) ???:-1] >>>>>> 0x7f54d019ca94 : ??? [(???) ???:-1] >>>>>> 0x7f54d019b877 : QApplication::x11ProcessEvent(_XEvent*) >>>>>> [(libQtGui.so.4) ???:-1] >>>>>> 0x7f54d01c4805 : ??? [(???) ???:-1] >>>>>> 0x7f54cfa7f375 : >>>>>> QEventLoop::processEvents(QFlags) >>>>>> [(libQtCore.so.4) ???:-1] >>>>>> 0x7f54cfa7f748 : >>>>>> QEventLoop::exec(QFlags) [(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. >> >> >> >> >> >> > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfavre at cscs.ch Mon Aug 10 13:33:57 2015 From: jfavre at cscs.ch (Favre Jean) Date: Mon, 10 Aug 2015 17:33:57 +0000 Subject: [Paraview] SC '15 Scientific Visualization Showcase Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F6841F24610@MBX211.d.ethz.ch> Folks, there has been several requests to push the deadline for submission of the Supercomputing`15 Scientific Visualization Showcase; A new and final deadline for submission has been set to 2015-08-21 23:59, AOE see details at; http://sc15.supercomputing.org/program/scientific-visualization-showcase We look forward to great visualizations and analytics showcases. ----------------- Jean M. Favre SC15 Scientific Visualization Showcase Chair -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Mon Aug 10 15:39:46 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Mon, 10 Aug 2015 15:39:46 -0400 Subject: [Paraview] vtkTransmitImageDataPiece question In-Reply-To: <55C4F757.3080804@nasa.gov> References: <55C100EE.50807@nasa.gov> <55C4EF18.7050102@nasa.gov> <55C4F757.3080804@nasa.gov> Message-ID: Hi Jeff, I commented that line out to mainly remove the SetExtent() call. When you set the CAN_HANDLE_PIECE_REQUEST() key instead of the CAN_PRODUCE_SUB_EXTENT() key, the filter is no longer passed an update extent local to the MPI rank it is on. Rather it is passed a global update extent and is asked to partition it as it sees fit. This means that you can no longer do imageData.SetExtent(updateExtent) Rather, you have to do: self.GetOutput().ShallowCopy(xmit,GetOutput()) This copy will copy the extent from the xmit filter's output. The transmit filter internally decides on a partition so you need to use that. For reference to others that may be following this thread, I recommended to Jeff that he uses the Nrrd reader, which uses MPI-IO to read raw files (structured datasets). It is a more efficient approach. Best, -berk On Fri, Aug 7, 2015 at 2:22 PM, Jeff Becker wrote: > Hi again. I have a quick question below. > > On 08/07/2015 10:47 AM, Jeff Becker wrote: > > Hi Berk, > > On 08/07/2015 10:08 AM, Berk Geveci wrote: > > Hey Jeff, > > Can you clarify a bit? What kind of wrong is the output? > > > I have an updated report in the mail I sent to the list on Wednesday. I > will forward you that directly. Please see updated code in that mail. > Right now, if I run my script on two processors, it looks like both > processors get the same half of the data. > > In the meantime, I will try to incorporate your suggestion below. Thanks. > > > In your version of my code below, you commented out the line: > > imagedata = self.GetOutput() > > I was using the example in: > > > http://www.paraview.org/Wiki/ParaView/Simple_ParaView_3_Python_Filters#Producing_Image_Data_.28Source.29 > > Instead should I generate a new vtkImageData instance? > > > Thanks again, > > -jeff > > > -jeff > > > Also, I would probably do this a bit differently, assuming you use a newer > ParaView (>= 4.2). The issue is that vtkTransmitImageDataPiece is not a > "CAN_PRODUCE_SUB_EXTENT()" filter. Rather it is a > "CAN_HANDLE_PIECE_REQUEST()" filter. Meaning that it wants to determine the > extents of the output based on the piece request it receives. So some > changes: > > * Swap CAN_PRODUCE_SUB_EXTENT() with CAN_HANDLE_PIECE_REQUEST() in > request info. > * In the main script, do something like this: > > executive = self.GetExecutive() > outInfo = executive.GetOutputInformation(0) > #updateExtent = [executive.UPDATE_EXTENT().Get(outInfo, i) for i in > xrange(6)] > #imageData = self.GetOutput() > #imageData.SetExtent(updateExtent) > # >> this probably needs to happen on rank 0 only > myout = ns.numpy_to_vtk(bmag.ravel(),1,vtk.VTK_FLOAT) > myout.SetName("B field magnitude") > imageData.GetPointData().SetScalars(myout) > tp = vtk.vtkTrivialProducer() > tp.SetOutput(imageData) > tp.SetWholeExtent(0, mesh.MX-1, 0, mesh.MY-1, 0, mesh.MZ-1) > xmit = vtk.vtkTransmitImageDataPiece() > xmit.SetInputConnection(tp.GetOutputPort()) > xmit.UpdateInformation() > xmit.SetUpdateExtent(rank, nranks, 0) > xmit.Update() > self.GetOutput().ShallowCopy(xmit,GetOutput()) > > I didn't verify the code so it may need tweaking. > > Best, > -berk > > > On Tue, Aug 4, 2015 at 2:14 PM, Jeff Becker > wrote: > >> Hi. I'm trying to run a Python Programmable source across four nodes >> (started with mpirun -np 4 pvserver). My script contains the following >> code, but the output looks wrong, so I'm not sure if the extents are >> right. The partitioning among nodes is correct (using processId filter). >> Also I'm careful to set Output Data Set Type to vtkImageData. >> >> import vtk >> import vtk.util.numpy_support as ns >> contr = vtk.vtkMultiProcessController.GetGlobalController() >> nranks = contr.GetNumberOfProcesses() >> rank = contr.GetLocalProcessId() >> >> ... >> executive = self.GetExecutive() >> outInfo = executive.GetOutputInformation(0) >> updateExtent = [executive.UPDATE_EXTENT().Get(outInfo, i) for i in >> xrange(6)] >> imageData = self.GetOutput() >> imageData.SetExtent(updateExtent) >> myout = ns.numpy_to_vtk(bmag.ravel(),1,vtk.VTK_FLOAT) >> myout.SetName("B field magnitude") >> imageData.GetPointData().SetScalars(myout) >> tp = vtk.vtkTrivialProducer() >> tp.SetOutput(imageData) >> tp.SetWholeExtent(0, mesh.MX-1, 0, mesh.MY-1, 0, mesh.MZ-1) >> xmit = vtk.vtkTransmitImageDataPiece() >> xmit.SetInputConnection(tp.GetOutputPort()) >> xmit.UpdateInformation() >> xmit.SetUpdateExtent(rank, nranks, 0) >> xmit.Update() >> >> For completeness, here is my requestInformation script (mesh has >> dimensions, and coordinate arrays for each of X,Y,Z) >> >> executive = self.GetExecutive() >> outInfo = executive.GetOutputInformation(0) >> outInfo.Set(vtk.vtkAlgorithm.CAN_PRODUCE_SUB_EXTENT(), 1) >> outInfo.Set(executive.WHOLE_EXTENT(), 0, mesh.MX-1, 0, mesh.MY-1, 0, >> mesh.MZ-1) >> xspacing = (mesh.xcoords[-1] - mesh.xcoords[0])/mesh.MX >> yspacing = (mesh.ycoords[-1] - mesh.ycoords[0])/mesh.MY >> zspacing = (mesh.zcoords[-1] - mesh.zcoords[0])/mesh.MZ >> outInfo.Set(vtk.vtkDataObject.SPACING(), xspacing, yspacing, zspacing) >> >> This is what I've been able to come up with after spending much time >> reading documentation and examples, but I've obviously missed something. >> Please advise. 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: From ganesh.iitm at gmail.com Mon Aug 10 19:02:41 2015 From: ganesh.iitm at gmail.com (Ganesh Vijayakumar) Date: Mon, 10 Aug 2015 23:02:41 +0000 Subject: [Paraview] scalarBar location Message-ID: Dear All, Could you please help me with setting the location of the scalarBar location using python scripting? I'm unable to see any changes to a python script generated by "trace" when I move the scalar bar around. ganesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From sergi.mateo.bellido at gmail.com Tue Aug 11 01:35:34 2015 From: sergi.mateo.bellido at gmail.com (Sergi Mateo Bellido) Date: Tue, 11 Aug 2015 07:35:34 +0200 Subject: [Paraview] [BUG] segfault playing a simulation In-Reply-To: References: <55895735.2030202@gmail.com> <559381DE.5030504@gmail.com> <559422EF.3070304@gmail.com> <55A0E2AE.5050101@gmail.com> <55A9056C.2000101@gmail.com> <55A90F76.8000804@gmail.com> <55B20445.7060809@gmail.com> <55BE4829.5030209@gmail.com> Message-ID: <55C989A6.7060809@gmail.com> Hi Cory, Apart from that issues, Could you reproduce the segfault? I was running the client directly, I wasn't using the server. Thanks! Sergi On 08/10/2015 05:12 PM, Cory Quammen wrote: > Sergi, > > Quick update: > > I'm having even stranger behavior than a crash. When I load the ascii > files you sent in mpi_test.tar.gz with ParaView running with the > built-in server, I can see the different values of "var" for the first > and second blocks (0 and 1, respectively). The same is true when I run > a separate pvserver and connect to it from the client. > > However, when I connect to a server running with > > mpirun -np2 pvserver > > "var" has only the value 0. > > This same behavior occurs for the zipped_binary and raw_binary files > as well. > > I'll look into it some more. > > Thanks, > Cory > > On Fri, Aug 7, 2015 at 2:32 PM, Cory Quammen > wrote: > > Sergi, > > Thanks for investigating and posting the information. I will take > a look. > > - Cory > > On Sun, Aug 2, 2015 at 12:41 PM, Sergi Mateo Bellido > > wrote: > > Hi, > > After a few hours debugging ParaView's code I think that I > finally found the bug! :) > > The problem is that the meaning of the piece extent changes > depending on if the piece has the whole dimensions or only a > portion of them. For example, imagine that we have the > following *.pvti file: > > compressor="vtkZLibDataCompressor"> > > > > > Source="raw_binary_0_0.vti"/> > Source="raw_binary_0_1.vti"/> > > > > In this case, the dimensions of the pieces are: > 1st piece -> [0..200], [0..200], [0..101) > 2nd piece -> [0..200], [0..200], [101..200] > > Note that the last dimension range of the 1st piece doesn't > include the 101 value which is included in the 2nd piece. > > The issue here is that the code is not taking into account > this when it's computing the dimensions of the current piece. > In file VTK/IO/XML/vtkXMLPStructuredDataReader.cxx:155 we have > the next call to 'ComputePointDimensions' function: > > this->ComputePointDimensions(this->SubExtent, > this->SubPointDimensions); > > I printed the values of 'this->SubExtent' and they were the > same values specified in the Piece Extent field: > > (gdb) p SubExtent > $1 = {0, 200, 0, 200, 0, 101} > > For these values, the 'ComputePointDimensions' function, which > is defined in VTK/IO/XML/vtkXMLReader.cxx:916, computed the > next dimensions: > > (gdb) p this->SubPointDimensions > $2 = {201, 201, 102} > > How these values are computed is very simple: upper_bound - > lower_bound + 1. Note that the value of the third dimension is > wrong: it should be 101 instead of 102. > > Finally, the segfault is produced in the 'CopySubExtent' > function, which is defined in > VTK/IO/XML/vtkXMLPStructuredDataReader.cxx:342, because > SubPointDimensions information is used to copy the regions and > we are doing an extra copy (loop defined in 371 line). > > Could you confirm me this bug? > > Best regards, > > Sergi Mateo > > PS1: Source references are related to the last version of > ParaView's source published in your webpage: > http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.3&type=source&os=all&downloadFile=ParaView-v4.3.1-source.tar.gz > > PS2: You can reproduce this bug using one of the examples that > I sent you in my previous emails. > > On 07/24/2015 11:24 AM, Sergi Mateo Bellido wrote: >> 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 >>>>> >>>> > 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 >>>>>> >>>>> > 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 >>>>>> > 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 >>>>>>>> >>>>>>> > 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&, bool) >>>>>>>> [(libQtGui.so.4) ???:-1] >>>>>>>> 0x7f54d019ca94 : ??? [(???) ???:-1] >>>>>>>> 0x7f54d019b877 : >>>>>>>> QApplication::x11ProcessEvent(_XEvent*) >>>>>>>> [(libQtGui.so.4) ???:-1] >>>>>>>> 0x7f54d01c4805 : ??? [(???) ???:-1] >>>>>>>> 0x7f54cfa7f375 : >>>>>>>> QEventLoop::processEvents(QFlags) >>>>>>>> [(libQtCore.so.4) ???:-1] >>>>>>>> 0x7f54cfa7f748 : >>>>>>>> QEventLoop::exec(QFlags) >>>>>>>> [(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. >>>> >>> >> > > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Aug 11 10:32:25 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 11 Aug 2015 10:32:25 -0400 Subject: [Paraview] [BUG] segfault playing a simulation In-Reply-To: <55C989A6.7060809@gmail.com> References: <55895735.2030202@gmail.com> <559381DE.5030504@gmail.com> <559422EF.3070304@gmail.com> <55A0E2AE.5050101@gmail.com> <55A9056C.2000101@gmail.com> <55A90F76.8000804@gmail.com> <55B20445.7060809@gmail.com> <55BE4829.5030209@gmail.com> <55C989A6.7060809@gmail.com> Message-ID: I do sometimes get a crash. I'm still looking into it. Cory On Tue, Aug 11, 2015 at 1:35 AM, Sergi Mateo Bellido < sergi.mateo.bellido at gmail.com> wrote: > Hi Cory, > > Apart from that issues, Could you reproduce the segfault? I was running > the client directly, I wasn't using the server. > > Thanks! > Sergi > > > On 08/10/2015 05:12 PM, Cory Quammen wrote: > > Sergi, > > Quick update: > > I'm having even stranger behavior than a crash. When I load the ascii > files you sent in mpi_test.tar.gz with ParaView running with the built-in > server, I can see the different values of "var" for the first and second > blocks (0 and 1, respectively). The same is true when I run a separate > pvserver and connect to it from the client. > > However, when I connect to a server running with > > mpirun -np2 pvserver > > "var" has only the value 0. > > This same behavior occurs for the zipped_binary and raw_binary files as > well. > > I'll look into it some more. > > Thanks, > Cory > > On Fri, Aug 7, 2015 at 2:32 PM, Cory Quammen > wrote: > >> Sergi, >> >> Thanks for investigating and posting the information. I will take a look. >> >> - Cory >> >> On Sun, Aug 2, 2015 at 12:41 PM, Sergi Mateo Bellido < >> sergi.mateo.bellido at gmail.com> wrote: >> >>> Hi, >>> >>> After a few hours debugging ParaView's code I think that I finally found >>> the bug! :) >>> >>> The problem is that the meaning of the piece extent changes depending on >>> if the piece has the whole dimensions or only a portion of them. For >>> example, imagine that we have the following *.pvti file: >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> In this case, the dimensions of the pieces are: >>> 1st piece -> [0..200], [0..200], [0..101) >>> 2nd piece -> [0..200], [0..200], [101..200] >>> >>> Note that the last dimension range of the 1st piece doesn't include the >>> 101 value which is included in the 2nd piece. >>> >>> The issue here is that the code is not taking into account this when >>> it's computing the dimensions of the current piece. In file >>> VTK/IO/XML/vtkXMLPStructuredDataReader.cxx:155 we have the next call to >>> 'ComputePointDimensions' function: >>> >>> this->ComputePointDimensions(this->SubExtent, this->SubPointDimensions); >>> >>> I printed the values of 'this->SubExtent' and they were the same values >>> specified in the Piece Extent field: >>> >>> (gdb) p SubExtent >>> $1 = {0, 200, 0, 200, 0, 101} >>> >>> For these values, the 'ComputePointDimensions' function, which is >>> defined in VTK/IO/XML/vtkXMLReader.cxx:916, computed the next dimensions: >>> >>> (gdb) p this->SubPointDimensions >>> $2 = {201, 201, 102} >>> >>> How these values are computed is very simple: upper_bound - lower_bound >>> + 1. Note that the value of the third dimension is wrong: it should be 101 >>> instead of 102. >>> >>> Finally, the segfault is produced in the 'CopySubExtent' function, which >>> is defined in VTK/IO/XML/vtkXMLPStructuredDataReader.cxx:342, because >>> SubPointDimensions information is used to copy the regions and we are doing >>> an extra copy (loop defined in 371 line). >>> >>> Could you confirm me this bug? >>> >>> Best regards, >>> >>> Sergi Mateo >>> >>> PS1: Source references are related to the last version of ParaView's >>> source published in your webpage: >>> http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.3&type=source&os=all&downloadFile=ParaView-v4.3.1-source.tar.gz >>> >>> PS2: You can reproduce this bug using one of the examples that I sent >>> you in my previous emails. >>> >>> On 07/24/2015 11:24 AM, Sergi Mateo Bellido wrote: >>> >>> 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> 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&, bool) >>>>>>> [(libQtGui.so.4) ???:-1] >>>>>>> 0x7f54d019ca94 : ??? [(???) ???:-1] >>>>>>> 0x7f54d019b877 : QApplication::x11ProcessEvent(_XEvent*) >>>>>>> [(libQtGui.so.4) ???:-1] >>>>>>> 0x7f54d01c4805 : ??? [(???) ???:-1] >>>>>>> 0x7f54cfa7f375 : >>>>>>> QEventLoop::processEvents(QFlags) >>>>>>> [(libQtCore.so.4) ???:-1] >>>>>>> 0x7f54cfa7f748 : >>>>>>> QEventLoop::exec(QFlags) [(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. >>> >>> >>> >>> >>> >>> >> >> >> -- >> 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: From cory.quammen at kitware.com Tue Aug 11 14:32:01 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 11 Aug 2015 14:32:01 -0400 Subject: [Paraview] [BUG] segfault playing a simulation In-Reply-To: References: <55895735.2030202@gmail.com> <559381DE.5030504@gmail.com> <559422EF.3070304@gmail.com> <55A0E2AE.5050101@gmail.com> <55A9056C.2000101@gmail.com> <55A90F76.8000804@gmail.com> <55B20445.7060809@gmail.com> <55BE4829.5030209@gmail.com> <55C989A6.7060809@gmail.com> Message-ID: Sergi, Okay, I think I understand what is going on. Recall that you were seeing that the reader was trying to read an extra slice of the first piece. After looking at another example of a multipiece XML image file, it is apparent that you are in fact expected to provide that extra slice in your first piece. So if you change your writer to write the extra slice, that should solve the problem. I'm checking to see if this is documented anywhere. Cheers, Cory On Tue, Aug 11, 2015 at 10:32 AM, Cory Quammen wrote: > I do sometimes get a crash. I'm still looking into it. > > Cory > > On Tue, Aug 11, 2015 at 1:35 AM, Sergi Mateo Bellido < > sergi.mateo.bellido at gmail.com> wrote: > >> Hi Cory, >> >> Apart from that issues, Could you reproduce the segfault? I was running >> the client directly, I wasn't using the server. >> >> Thanks! >> Sergi >> >> >> On 08/10/2015 05:12 PM, Cory Quammen wrote: >> >> Sergi, >> >> Quick update: >> >> I'm having even stranger behavior than a crash. When I load the ascii >> files you sent in mpi_test.tar.gz with ParaView running with the built-in >> server, I can see the different values of "var" for the first and second >> blocks (0 and 1, respectively). The same is true when I run a separate >> pvserver and connect to it from the client. >> >> However, when I connect to a server running with >> >> mpirun -np2 pvserver >> >> "var" has only the value 0. >> >> This same behavior occurs for the zipped_binary and raw_binary files as >> well. >> >> I'll look into it some more. >> >> Thanks, >> Cory >> >> On Fri, Aug 7, 2015 at 2:32 PM, Cory Quammen >> wrote: >> >>> Sergi, >>> >>> Thanks for investigating and posting the information. I will take a look. >>> >>> - Cory >>> >>> On Sun, Aug 2, 2015 at 12:41 PM, Sergi Mateo Bellido < >>> sergi.mateo.bellido at gmail.com> wrote: >>> >>>> Hi, >>>> >>>> After a few hours debugging ParaView's code I think that I finally >>>> found the bug! :) >>>> >>>> The problem is that the meaning of the piece extent changes depending >>>> on if the piece has the whole dimensions or only a portion of them. For >>>> example, imagine that we have the following *.pvti file: >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> In this case, the dimensions of the pieces are: >>>> 1st piece -> [0..200], [0..200], [0..101) >>>> 2nd piece -> [0..200], [0..200], [101..200] >>>> >>>> Note that the last dimension range of the 1st piece doesn't include the >>>> 101 value which is included in the 2nd piece. >>>> >>>> The issue here is that the code is not taking into account this when >>>> it's computing the dimensions of the current piece. In file >>>> VTK/IO/XML/vtkXMLPStructuredDataReader.cxx:155 we have the next call to >>>> 'ComputePointDimensions' function: >>>> >>>> this->ComputePointDimensions(this->SubExtent, >>>> this->SubPointDimensions); >>>> >>>> I printed the values of 'this->SubExtent' and they were the same values >>>> specified in the Piece Extent field: >>>> >>>> (gdb) p SubExtent >>>> $1 = {0, 200, 0, 200, 0, 101} >>>> >>>> For these values, the 'ComputePointDimensions' function, which is >>>> defined in VTK/IO/XML/vtkXMLReader.cxx:916, computed the next dimensions: >>>> >>>> (gdb) p this->SubPointDimensions >>>> $2 = {201, 201, 102} >>>> >>>> How these values are computed is very simple: upper_bound - lower_bound >>>> + 1. Note that the value of the third dimension is wrong: it should be 101 >>>> instead of 102. >>>> >>>> Finally, the segfault is produced in the 'CopySubExtent' function, >>>> which is defined in VTK/IO/XML/vtkXMLPStructuredDataReader.cxx:342, because >>>> SubPointDimensions information is used to copy the regions and we are doing >>>> an extra copy (loop defined in 371 line). >>>> >>>> Could you confirm me this bug? >>>> >>>> Best regards, >>>> >>>> Sergi Mateo >>>> >>>> PS1: Source references are related to the last version of ParaView's >>>> source published in your webpage: >>>> http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.3&type=source&os=all&downloadFile=ParaView-v4.3.1-source.tar.gz >>>> >>>> PS2: You can reproduce this bug using one of the examples that I sent >>>> you in my previous emails. >>>> >>>> On 07/24/2015 11:24 AM, Sergi Mateo Bellido wrote: >>>> >>>> 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> 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&, bool) >>>>>>>> [(libQtGui.so.4) ???:-1] >>>>>>>> 0x7f54d019ca94 : ??? [(???) ???:-1] >>>>>>>> 0x7f54d019b877 : QApplication::x11ProcessEvent(_XEvent*) >>>>>>>> [(libQtGui.so.4) ???:-1] >>>>>>>> 0x7f54d01c4805 : ??? [(???) ???:-1] >>>>>>>> 0x7f54cfa7f375 : >>>>>>>> QEventLoop::processEvents(QFlags) >>>>>>>> [(libQtCore.so.4) ???:-1] >>>>>>>> 0x7f54cfa7f748 : >>>>>>>> QEventLoop::exec(QFlags) [(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. >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >>> -- >>> 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: From utkarsh.ayachit at kitware.com Wed Aug 12 10:57:00 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 12 Aug 2015 10:57:00 -0400 Subject: [Paraview] scalarBar location In-Reply-To: References: Message-ID: Ganesh, It'll be something like this: lut = GetColorTransferFunction("RTData") sb = GetScalarBar(a, GetActiveView()) sb.Position = [x, y] sb.Position2 = [x2, y2] sb.Orientation = "Horizontal' # or | "Vertical" I've also reported a bug: http://www.paraview.org/Bug/view.php?id=15640 Utkarsh On Mon, Aug 10, 2015 at 7:02 PM, Ganesh Vijayakumar wrote: > Dear All, > > Could you please help me with setting the location of the scalarBar > location using python scripting? I'm unable to see any changes to a python > script generated by "trace" when I move the scalar bar around. > > 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 berk.geveci at kitware.com Wed Aug 12 17:25:40 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Wed, 12 Aug 2015 17:25:40 -0400 Subject: [Paraview] Bug for vti in Paraview 4.3 In-Reply-To: References: Message-ID: I have a fix for the clip issue in the works - clip has not worked with 2D image data in quite a while. There is another bug where clip crashes unless the 2D image is on the x-y plane. We will work on a fix for that also. Best, -berk On Thu, Jun 18, 2015 at 7:43 AM, Gabe Weymouth 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 > > Visit other Kitware open-source projects 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: From G.D.Weymouth at soton.ac.uk Thu Aug 13 00:20:07 2015 From: G.D.Weymouth at soton.ac.uk (Gabe Weymouth) Date: Thu, 13 Aug 2015 12:20:07 +0800 Subject: [Paraview] Bug for vti in Paraview 4.3 In-Reply-To: References: Message-ID: Great. Thanks for letting me know. *Gabriel D Weymouth* Southampton Marine and Maritime Institute Lecturer University of Southampton Boldrewood Campus, Building 176, Room 3029 Southampton, SO16 7QF, UK On Thu, Aug 13, 2015 at 5:25 AM, Berk Geveci wrote: > I have a fix for the clip issue in the works - clip has not worked with 2D > image data in quite a while. There is another bug where clip crashes unless > the 2D image is on the x-y plane. We will work on a fix for that also. > > Best, > -berk > > On Thu, Jun 18, 2015 at 7:43 AM, Gabe Weymouth > 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 > > Visit other Kitware open-source projects 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: From dave.demarle at kitware.com Thu Aug 13 22:02:35 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 13 Aug 2015 22:02:35 -0400 Subject: [Paraview] non-interactive viz on cluster In-Reply-To: References: Message-ID: Does this not work? try: paraview.simple except: from paraview.simple import * i = 0 paraview.simple._DisableFirstRenderCameraReset() RenderView1 = GetRenderView() my_2d0_vts = XMLStructuredGridReader( FileName=['file_%i.vts' % (i)] ) RenderView1.CenterAxesVisibility = 0 RenderView1.OrientationAxesVisibility = 0 my_2d0_vts.PointArrayStatus = ['Unnamed0'] 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.0, 0.23, 0.299, 0.754, 1.0, 0.7059953924945706, 0.01625293517428646, 0.1500022472819457], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 ) a1_Unnamed0_PiecewiseFunction = CreatePiecewiseFunction( Points=[-0.1, 0.0, 1.0, 1.0] ) ScalarBarWidgetRepresentation1 = CreateScalarBar( Title='Unnamed0', LabelFontSize=12, Enabled=1, LookupTable=a1_Unnamed0_PVLookupTable, TitleFontSize=12 ) GetRenderView().Representations.append(ScalarBarWidgetRepresentation1) 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] Text1 = Text() RenderView1.CameraViewUp = [0.0, 1.0, 0.0] RenderView1.CameraPosition = [78.0, -58.5, 376.71107225273664] RenderView1.CameraFocalPoint = [78.0, -58.5, 0.0] RenderView1.CenterOfRotation = [78.0, -58.5, 0.0] RenderView1.CameraClippingRange = [372.94396153020926, 382.3617383365277] Text1.Text = '2D macro re-entry' DataRepresentation3 = Show() DataRepresentation3.Color = [0.3333333333333333, 0.0, 0.4980392156862745] WriteImage('reentry2d%06i.png' % (i)) Render() for i in range(1,10,1): my_2d0_vts.FileName=['file_%i.vts' % (i)] Render() WriteImage('reentry2d%06i.png' % (i)) 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: From dave.demarle at kitware.com Thu Aug 13 22:06:04 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 13 Aug 2015 22:06:04 -0400 Subject: [Paraview] Make XDMF Sets work in Multi-block Inspector In-Reply-To: References: Message-ID: Ondrej, Do you have a small example that I can use to reproduce the problem? thankyou David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Aug 10, 2015 at 10:02 AM, Ond?ej ?ert?k wrote: > Hi, > > We would like to use the Multi-block inspector to turn solutions on > and off on a given subdomain (set of blocks). Just like it works if > you load an Exodus file. We use XDMF and we were told to use Sets to > designate subdomains. We did that and indeed they appear in the > Multi-block inspector, but unfortunately they do not work to turn > solutions on and off. For some reason, they only appear to add > geometry *over* the solutions, so you don't see any solutions at all. > Only if you turn them off, then you can see the solution on the whole > mesh. In particular, you can't use those to turn off a solution on > just part of it. > > Essentially it looks like if Sets created a new geometry without any > solutions associated with it (and allow to turn parts of this geometry > on and off, as expected), and then visualized it on top of the > original mesh+solutions. > > Any ideas how to resolve that? > > I tested ParaView 4.3.1. > > Thanks, > Ondrej Certik > Los Alamos National Laboratory > _______________________________________________ > 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: From dennis_conklin at goodyear.com Thu Aug 13 22:07:13 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Fri, 14 Aug 2015 02:07:13 +0000 Subject: [Paraview] How to detect element type inside Programmable Filter Message-ID: All, I have something like: def process_block(block) # do different things based on element type of block for block in output: process_block(block) But I cannot figure out how to determine the element type in each block thanks for any help - I may be dense but I'm persistent! Dennis Conklin, PE RDE&Q Principal Engineer Goodyear Innovation Center, 5th Floor South, Pillar M34 Phone: 330-796-5701 Email: dennis_conklin at goodyear.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Aug 13 22:32:05 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 13 Aug 2015 22:32:05 -0400 Subject: [Paraview] Make XDMF Sets work in Multi-block Inspector In-Reply-To: References: Message-ID: Actually I can see what you mean on a sample I have here (attached). Sets in xdmf identifying some portion of the geometry/topology of another mesh so that you can add arbitrary attributes to that subset without affecting the whole thing. As you've surmised in practice the VTK reader just makes a new unstructured grid for the subset. The subset block has has very little relationship to the whole that it was extracted from. (Supposed we could have a not set complement and then you could get at it.) I think what you want is a plain old collection instead. See the attached example (xmf portion only, the h5 part is to big for email but you can find it in the VTK/ParaView regression test data suite). hth David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Aug 13, 2015 at 10:06 PM, David E DeMarle wrote: > Ondrej, > > Do you have a small example that I can use to reproduce the problem? > > thankyou > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Mon, Aug 10, 2015 at 10:02 AM, Ond?ej ?ert?k > wrote: > >> Hi, >> >> We would like to use the Multi-block inspector to turn solutions on >> and off on a given subdomain (set of blocks). Just like it works if >> you load an Exodus file. We use XDMF and we were told to use Sets to >> designate subdomains. We did that and indeed they appear in the >> Multi-block inspector, but unfortunately they do not work to turn >> solutions on and off. For some reason, they only appear to add >> geometry *over* the solutions, so you don't see any solutions at all. >> Only if you turn them off, then you can see the solution on the whole >> mesh. In particular, you can't use those to turn off a solution on >> just part of it. >> >> Essentially it looks like if Sets created a new geometry without any >> solutions associated with it (and allow to turn parts of this geometry >> on and off, as expected), and then visualized it on top of the >> original mesh+solutions. >> >> Any ideas how to resolve that? >> >> I tested ParaView 4.3.1. >> >> Thanks, >> Ondrej Certik >> Los Alamos National Laboratory >> _______________________________________________ >> 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: set.xmf Type: application/octet-stream Size: 2019 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Test1.h5 Type: application/octet-stream Size: 15072 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Iron_Protein.ImageData.Collection.xmf Type: application/octet-stream Size: 9726 bytes Desc: not available URL: From dave.demarle at kitware.com Thu Aug 13 22:42:39 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 13 Aug 2015 22:42:39 -0400 Subject: [Paraview] How to detect element type inside Programmable Filter In-Reply-To: References: Message-ID: On Thu, Aug 13, 2015 at 10:07 PM, Dennis Conklin < dennis_conklin at goodyear.com> wrote: > I may be dense but I'm persistent! I am more persistent (and more dense). :) def process_block(block): #print dir(block) #print dir(block.VTKObject) print block.VTKObject.GetClassName() for block in output: process_block(block) 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: From dave.demarle at kitware.com Thu Aug 13 22:46:52 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 13 Aug 2015 22:46:52 -0400 Subject: [Paraview] running parallel pvservers In-Reply-To: <55C27815.2080802@nasa.gov> References: <55B12A0A.6070106@nasa.gov> <55B12F05.6070005@nasa.gov> <55C27815.2080802@nasa.gov> Message-ID: Jeff, Have you gotten this running? //with Berk's help on the transmit*piece part? best wishes, David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Aug 5, 2015 at 4:54 PM, Jeff Becker wrote: > Hi David and list. I'm still struggling with distributing my dataset > (bmag) across nodes. My Python Programmable source script below produces > correct output when run on a single node. > > contr = vtk.vtkMultiProcessController.GetGlobalController() > nranks = contr.GetNumberOfProcesses() > rank = contr.GetLocalProcessId() > > # read in bmag data and process > > executive = self.GetExecutive() > outInfo = executive.GetOutputInformation(0) > updateExtent = [executive.UPDATE_EXTENT().Get(outInfo, i) for i in > xrange(6)] > imageData = self.GetOutput() > imageData.SetExtent(updateExtent) > myout = ns.numpy_to_vtk(bmag.ravel(),1,vtk.VTK_FLOAT) > myout.SetName("B field magnitude") > imageData.GetPointData().SetScalars(myout) > > > I then used the Filters/Parallel/Testing/Python/testTransmit.py test code > as a basis to continue the script to work on multiple nodes. Following the > last line above, I added: > > da = vtk.vtkIntArray() > da.SetNumberOfTuples(6) > if rank == 0: > ext = imageData.GetExtent() > for i in range(6): > da.SetValue(i,ext[i]) > contr.Broadcast(da,0) > > ext = [] > for i in range(6): > ext.append(da.GetValue(i)) > ext = tuple(ext) > > tp = vtk.vtkTrivialProducer() > tp.SetOutput(imageData) > tp.SetWholeExtent(ext) > > xmit = vtk.vtkTransmitImageDataPiece() > xmit.SetInputConnection(tp.GetOutputPort()) > xmit.UpdateInformation() > xmit.SetUpdateExtent(rank, nranks, 0) > xmit.Update() > > However, when I run this on two nodes, it looks like both of them get the > same half of the data, rather than the whole dataset getting split between > the two. Can anyone see what might be wrong? 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 > 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 >> 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: From S.R.Kharche at exeter.ac.uk Fri Aug 14 04:24:22 2015 From: S.R.Kharche at exeter.ac.uk (Kharche, Sanjay) Date: Fri, 14 Aug 2015 08:24:22 +0000 Subject: [Paraview] non-interactive viz on cluster In-Reply-To: References: , Message-ID: Hi David Your suggestion of a loop within the python script did not work. I make 5k to 10k pngs, and the process was killed at a few hundred. Since my process is serial at the moment, my solution is that I take an input from a bash script: import system i = system(argv[1]) (or something similar). And my python is for 1 i that is read in. That gives me a consistent predictable (in terms of time it takes) working of my visualisation. cheers Sanjay ________________________________ From: David E DeMarle Sent: 13 August 2015 14:02 To: Kharche, Sanjay Cc: paraview at paraview.org Subject: Re: [Paraview] non-interactive viz on cluster Does this not work? try: paraview.simple except: from paraview.simple import * i = 0 paraview.simple._DisableFirstRenderCameraReset() RenderView1 = GetRenderView() my_2d0_vts = XMLStructuredGridReader( FileName=['file_%i.vts' % (i)] ) RenderView1.CenterAxesVisibility = 0 RenderView1.OrientationAxesVisibility = 0 my_2d0_vts.PointArrayStatus = ['Unnamed0'] 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.0, 0.23, 0.299, 0.754, 1.0, 0.7059953924945706, 0.01625293517428646, 0.1500022472819457], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 ) a1_Unnamed0_PiecewiseFunction = CreatePiecewiseFunction( Points=[-0.1, 0.0, 1.0, 1.0] ) ScalarBarWidgetRepresentation1 = CreateScalarBar( Title='Unnamed0', LabelFontSize=12, Enabled=1, LookupTable=a1_Unnamed0_PVLookupTable, TitleFontSize=12 ) GetRenderView().Representations.append(ScalarBarWidgetRepresentation1) 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] Text1 = Text() RenderView1.CameraViewUp = [0.0, 1.0, 0.0] RenderView1.CameraPosition = [78.0, -58.5, 376.71107225273664] RenderView1.CameraFocalPoint = [78.0, -58.5, 0.0] RenderView1.CenterOfRotation = [78.0, -58.5, 0.0] RenderView1.CameraClippingRange = [372.94396153020926, 382.3617383365277] Text1.Text = '2D macro re-entry' DataRepresentation3 = Show() DataRepresentation3.Color = [0.3333333333333333, 0.0, 0.4980392156862745] WriteImage('reentry2d%06i.png' % (i)) Render() for i in range(1,10,1): my_2d0_vts.FileName=['file_%i.vts' % (i)] Render() WriteImage('reentry2d%06i.png' % (i)) 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: From victorsv at gmail.com Fri Aug 14 06:25:00 2015 From: victorsv at gmail.com (victor sv) Date: Fri, 14 Aug 2015 12:25:00 +0200 Subject: [Paraview] XDMF and hyperslabs Message-ID: Hello all, I'm trying to create and visualize an XDMF/HDF5 file containing a partitioned mesh using hyperslabs. Is this supported by Paraview/VTK ?? The HDF5 (solution1.h5) looks as follows: GROUP "/" { GROUP "Grid" { DATASET "Connectivities" { DATATYPE H5T_STD_I32BE DATASPACE SIMPLE { ( 18 ) / ( 18 ) } DATA { (0): 0, 1, 2, 3, 2, 1, 4, 5, 6, 7, 6, 5, 6, 7, 8, 9, 8, 7 } } DATASET "Coordinates" { DATATYPE H5T_IEEE_F64BE DATASPACE SIMPLE { ( 20 ) / ( 20 ) } DATA { (0): 0, 0, 1, 0, 0, 0.5, 1, 0.5, 0, 0.5, 1, 0.5, 0, 1, 1, 1, 0, 1.5, (18): 1, 1.5 } } DATASET "Solution" { DATATYPE H5T_IEEE_F64BE DATASPACE SIMPLE { ( 10 ) / ( 10 ) } DATA { (0): 0, 0, 0, 0, 1, 1, 1, 1, 1, 1 } } } } And the XDMF file to represent a 2-triangle (4 points) piece of the full mesh is: 0 1 6 solution1.h5:Grid/Connectivities 0 1 8 solution1.h5:Grid/Coordinates I'm trying to use the syntax explained at the XDMF webpage ( http://www.xdmf.org/index.php/XDMF_Model_and_Format ), but I'm feeling confused about the version of the documentation and current version of XDMF library included in VTK library. Can anyone give me some info about this? It is XDMFv3 already public ? Thanks in advance, V?ctor. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dennis_conklin at goodyear.com Fri Aug 14 07:47:26 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Fri, 14 Aug 2015 11:47:26 +0000 Subject: [Paraview] [EXT] Re: How to detect element type inside Programmable Filter In-Reply-To: References: Message-ID: David, Yes, but I am more dense!! print block.VTKObject.GetClassName() prints out vtkUnstructuredGrid, which I already know. Within my UnstructuredGrid, some blocks are hex elements, some blocks are shell elements and some blocks are truss elements ? that is what I am trying to detect! Dennis From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Thursday, August 13, 2015 10:43 PM To: Dennis Conklin Cc: Paraview (paraview at paraview.org) Subject: [EXT] Re: [Paraview] How to detect element type inside Programmable Filter On Thu, Aug 13, 2015 at 10:07 PM, Dennis Conklin > wrote: I may be dense but I'm persistent! I am more persistent (and more dense). :) def process_block(block): #print dir(block) #print dir(block.VTKObject) print block.VTKObject.GetClassName() for block in output: process_block(block) 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: From dave.demarle at kitware.com Fri Aug 14 08:11:55 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 14 Aug 2015 08:11:55 -0400 Subject: [Paraview] non-interactive viz on cluster In-Reply-To: References: Message-ID: Interesting. Glad to hear you got a work around. Cheers On Aug 14, 2015 4:24 AM, "Kharche, Sanjay" wrote: > > Hi David > > > Your suggestion of a loop within the python script did not work. I make 5k > to 10k pngs, > > and the process was killed at a few hundred. > > > Since my process is serial at the moment, my solution is that I take an > input from a bash > > script: > > > import system > > > i = system(argv[1]) > > > (or something similar). And my python is for 1 i that is read in. > > > That gives me a consistent predictable (in terms of time it takes) > > working of my visualisation. > > > cheers > > Sanjay > ------------------------------ > *From:* David E DeMarle > *Sent:* 13 August 2015 14:02 > *To:* Kharche, Sanjay > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] non-interactive viz on cluster > > > Does this not work? > try: paraview.simple > except: from paraview.simple import * > > i = 0 > paraview.simple._DisableFirstRenderCameraReset() > RenderView1 = GetRenderView() > my_2d0_vts = XMLStructuredGridReader( FileName=['file_%i.vts' % (i)] ) > RenderView1.CenterAxesVisibility = 0 > RenderView1.OrientationAxesVisibility = 0 > my_2d0_vts.PointArrayStatus = ['Unnamed0'] > 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.0, 0.23, 0.299, 0.754, 1.0, > 0.7059953924945706, 0.01625293517428646, 0.1500022472819457], > VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 ) > a1_Unnamed0_PiecewiseFunction = CreatePiecewiseFunction( Points=[-0.1, > 0.0, 1.0, 1.0] ) > ScalarBarWidgetRepresentation1 = CreateScalarBar( Title='Unnamed0', > LabelFontSize=12, Enabled=1, LookupTable=a1_Unnamed0_PVLookupTable, > TitleFontSize=12 ) > GetRenderView().Representations.append(ScalarBarWidgetRepresentation1) > 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] > Text1 = Text() > RenderView1.CameraViewUp = [0.0, 1.0, 0.0] > RenderView1.CameraPosition = [78.0, -58.5, 376.71107225273664] > RenderView1.CameraFocalPoint = [78.0, -58.5, 0.0] > RenderView1.CenterOfRotation = [78.0, -58.5, 0.0] > RenderView1.CameraClippingRange = [372.94396153020926, 382.3617383365277] > Text1.Text = '2D macro re-entry' > DataRepresentation3 = Show() > DataRepresentation3.Color = [0.3333333333333333, 0.0, 0.4980392156862745] > WriteImage('reentry2d%06i.png' % (i)) > Render() > > for i in range(1,10,1): > my_2d0_vts.FileName=['file_%i.vts' % (i)] > Render() > WriteImage('reentry2d%06i.png' % (i)) > > > 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: From S.R.Kharche at exeter.ac.uk Fri Aug 14 08:28:04 2015 From: S.R.Kharche at exeter.ac.uk (Kharche, Sanjay) Date: Fri, 14 Aug 2015 12:28:04 +0000 Subject: [Paraview] non-interactive viz on cluster In-Reply-To: References: , Message-ID: Yes, giving an input to the pvbatch absolutely eliminates working out what was causing the memory leak in my viz simulation. Now I will try this in parallel: mpirun -n 12 pvbatch --offscreen ... I will post if I find a better performance. ________________________________ From: David E DeMarle Sent: 14 August 2015 00:11 To: Kharche, Sanjay Cc: paraview at paraview.org Subject: Re: [Paraview] non-interactive viz on cluster Interesting. Glad to hear you got a work around. Cheers On Aug 14, 2015 4:24 AM, "Kharche, Sanjay" > wrote: Hi David Your suggestion of a loop within the python script did not work. I make 5k to 10k pngs, and the process was killed at a few hundred. Since my process is serial at the moment, my solution is that I take an input from a bash script: import system i = system(argv[1]) (or something similar). And my python is for 1 i that is read in. That gives me a consistent predictable (in terms of time it takes) working of my visualisation. cheers Sanjay ________________________________ From: David E DeMarle > Sent: 13 August 2015 14:02 To: Kharche, Sanjay Cc: paraview at paraview.org Subject: Re: [Paraview] non-interactive viz on cluster Does this not work? try: paraview.simple except: from paraview.simple import * i = 0 paraview.simple._DisableFirstRenderCameraReset() RenderView1 = GetRenderView() my_2d0_vts = XMLStructuredGridReader( FileName=['file_%i.vts' % (i)] ) RenderView1.CenterAxesVisibility = 0 RenderView1.OrientationAxesVisibility = 0 my_2d0_vts.PointArrayStatus = ['Unnamed0'] 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.0, 0.23, 0.299, 0.754, 1.0, 0.7059953924945706, 0.01625293517428646, 0.1500022472819457], VectorMode='Magnitude', ColorSpace='Diverging', LockScalarRange=1 ) a1_Unnamed0_PiecewiseFunction = CreatePiecewiseFunction( Points=[-0.1, 0.0, 1.0, 1.0] ) ScalarBarWidgetRepresentation1 = CreateScalarBar( Title='Unnamed0', LabelFontSize=12, Enabled=1, LookupTable=a1_Unnamed0_PVLookupTable, TitleFontSize=12 ) GetRenderView().Representations.append(ScalarBarWidgetRepresentation1) 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] Text1 = Text() RenderView1.CameraViewUp = [0.0, 1.0, 0.0] RenderView1.CameraPosition = [78.0, -58.5, 376.71107225273664] RenderView1.CameraFocalPoint = [78.0, -58.5, 0.0] RenderView1.CenterOfRotation = [78.0, -58.5, 0.0] RenderView1.CameraClippingRange = [372.94396153020926, 382.3617383365277] Text1.Text = '2D macro re-entry' DataRepresentation3 = Show() DataRepresentation3.Color = [0.3333333333333333, 0.0, 0.4980392156862745] WriteImage('reentry2d%06i.png' % (i)) Render() for i in range(1,10,1): my_2d0_vts.FileName=['file_%i.vts' % (i)] Render() WriteImage('reentry2d%06i.png' % (i)) 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: From dave.demarle at kitware.com Fri Aug 14 08:33:36 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 14 Aug 2015 08:33:36 -0400 Subject: [Paraview] Memory seeking problems in using the xdmf2 reader In-Reply-To: References: Message-ID: Mind trying this? diff --git a/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfValuesBinary.cxx b/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfValuesBinary.cxx index 04ea0a7..d4cb2ed 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(atoi(this->Seek)); + return static_cast(atol(this->Seek)); } @@ -244,6 +244,7 @@ XdmfValuesBinary::Read(XdmfArray *anArray){ }else{ this->Seek = NULL; } + cerr << "Seek as string is " << Value << endl; } { XdmfConstString Value = this->Get("Compression"); @@ -291,6 +292,7 @@ XdmfValuesBinary::Read(XdmfArray *anArray){ //strcpy(path+strlen(this->DOM->GetWorkingDirectory()), DataSetName); try{ size_t seek = this->getSeek(); + cerr << "SEEK as size_t is " << seek << endl; switch(getCompressionType()){ case Zlib: XdmfDebug("Compression: Zlib"); 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 5:55 PM, Pulido, Jesus wrote: > 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(atoi(this->Seek)); > + return static_cast(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 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: From dave.demarle at kitware.com Fri Aug 14 08:56:13 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 14 Aug 2015 08:56:13 -0400 Subject: [Paraview] [EXT] Re: How to detect element type inside Programmable Filter In-Reply-To: References: Message-ID: Shell means locally 2D and Truss means locally 3D? def process_block(block): #print dir(block) #print dir(block.VTKObject) print block.VTKObject.GetClassName() for x in range(0,block.GetNumberOfCells()): #print dir(block.GetCell(x)) print x, block.GetCellType(x) for block in output: process_block(block) The printed cell types correspond to: http://www.vtk.org/doc/nightly/html/vtkCellType_8h_source.html There is probably a macro somewhere to get a GetCellTypeAsString() but easy enough to do in the filter. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Aug 14, 2015 at 7:47 AM, Dennis Conklin wrote: > David, > > > > Yes, but I am more dense!! > > > > print block.VTKObject.GetClassName() > > prints out vtkUnstructuredGrid, which I already know. > > > > Within my UnstructuredGrid, some blocks are hex elements, some blocks are > shell elements and some blocks are truss elements ? that is what I am > trying to detect! > > > > Dennis > > > > *From:* David E DeMarle [mailto:dave.demarle at kitware.com] > *Sent:* Thursday, August 13, 2015 10:43 PM > *To:* Dennis Conklin > *Cc:* Paraview (paraview at paraview.org) > *Subject:* [EXT] Re: [Paraview] How to detect element type inside > Programmable Filter > > > > > > On Thu, Aug 13, 2015 at 10:07 PM, Dennis Conklin < > dennis_conklin at goodyear.com> wrote: > > I may be dense but I'm persistent! > > > > I am more persistent (and more dense). :) > > > > def process_block(block): > > #print dir(block) > > #print dir(block.VTKObject) > > print block.VTKObject.GetClassName() > > for block in output: > > process_block(block) > > > > > > 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: From dennis_conklin at goodyear.com Fri Aug 14 09:28:16 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Fri, 14 Aug 2015 13:28:16 +0000 Subject: [Paraview] [EXT] Re: How to detect element type inside Programmable Filter In-Reply-To: References: Message-ID: David, Thanks very much, I?ve sorted through my stuff and found out what VTK thinks each of them are. Since EXODUS limits each block to a single element type, it never occurred to me to test the type of an individual cell, I was sure there would be a block level cell type. Thanks again Dennis From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Friday, August 14, 2015 8:56 AM To: Dennis Conklin Cc: Paraview (paraview at paraview.org) Subject: Re: [EXT] Re: [Paraview] How to detect element type inside Programmable Filter Shell means locally 2D and Truss means locally 3D? def process_block(block): #print dir(block) #print dir(block.VTKObject) print block.VTKObject.GetClassName() for x in range(0,block.GetNumberOfCells()): #print dir(block.GetCell(x)) print x, block.GetCellType(x) for block in output: process_block(block) The printed cell types correspond to: http://www.vtk.org/doc/nightly/html/vtkCellType_8h_source.html There is probably a macro somewhere to get a GetCellTypeAsString() but easy enough to do in the filter. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Aug 14, 2015 at 7:47 AM, Dennis Conklin > wrote: David, Yes, but I am more dense!! print block.VTKObject.GetClassName() prints out vtkUnstructuredGrid, which I already know. Within my UnstructuredGrid, some blocks are hex elements, some blocks are shell elements and some blocks are truss elements ? that is what I am trying to detect! Dennis From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Thursday, August 13, 2015 10:43 PM To: Dennis Conklin Cc: Paraview (paraview at paraview.org) Subject: [EXT] Re: [Paraview] How to detect element type inside Programmable Filter On Thu, Aug 13, 2015 at 10:07 PM, Dennis Conklin > wrote: I may be dense but I'm persistent! I am more persistent (and more dense). :) def process_block(block): #print dir(block) #print dir(block.VTKObject) print block.VTKObject.GetClassName() for block in output: process_block(block) 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: From antech777 at gmail.com Fri Aug 14 09:37:45 2015 From: antech777 at gmail.com (Andrew) Date: Fri, 14 Aug 2015 16:37:45 +0300 Subject: [Paraview] Compiling ParaView 3.12 with OSMesa Message-ID: Hello. I need to compile ParaView 3.12.0 for co-processing with Code_Saturne (Catalyst). I tried current version 4.3.1 but it seems that Saturne (v 4.0.2) is incompatible with it's Catalyst. So I compile ParaView 3.12.0 with recommended options: http://www.paraview.org/Wiki/ParaView:Build_And_Install http://www.paraview.org/Wiki/ParaView_And_Mesa_3D Mesa libraries version is 9.2.0 (libGLU 9.0.0 compiled separately). All sources are from official websites. Configure with ccmake is OK, it creates Makefile and I start make. But at 97% many errors appear relating to XDMF: many unresolved (undefined) references. Example undefined references: vtkXRenderWindowInteractor_Init, vtkXRenderWindowInteractor::BreakLoopFlag, vtkXRenderWindowInteractor::App, XtDispatchEvent, vtkXRenderWindowInteractor::vtkXRenderWindowInteractor. Full make output is in attach "make.log" (it's not a first run). I also attached Makefile created with ccmake. OS is Linux CentOS 6.5 (gcc 4.4.6). What is the problem? Can somebody, please, help me? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: make.log Type: application/octet-stream Size: 11471 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Makefile Type: application/octet-stream Size: 97221 bytes Desc: not available URL: From sujin.philip at kitware.com Fri Aug 14 09:46:37 2015 From: sujin.philip at kitware.com (Sujin Philip) Date: Fri, 14 Aug 2015 09:46:37 -0400 Subject: [Paraview] Compiling ParaView 3.12 with OSMesa In-Reply-To: References: Message-ID: Hi Andrew, I think you need to set the cmake cache variable -DVTK_USE_X=OFF. I recently did some work on compiling Paraview with osmesa for the Xeon Phi. You can find the details about it at: http://www.paraview.org/Wiki/ParaView_and_VTK_on_Xeon_Phi_%28KNC%29. You should be able to compile ParaView by following these steps, minus the cross compiling part. Thanks Sujin On Fri, Aug 14, 2015 at 9:37 AM, Andrew wrote: > Hello. > > I need to compile ParaView 3.12.0 for co-processing with Code_Saturne > (Catalyst). I tried current version 4.3.1 but it seems that Saturne (v > 4.0.2) is incompatible with it's Catalyst. > > So I compile ParaView 3.12.0 with recommended options: > http://www.paraview.org/Wiki/ParaView:Build_And_Install > http://www.paraview.org/Wiki/ParaView_And_Mesa_3D > Mesa libraries version is 9.2.0 (libGLU 9.0.0 compiled separately). > All sources are from official websites. > > Configure with ccmake is OK, it creates Makefile and I start make. But at > 97% many errors appear relating to XDMF: many unresolved (undefined) > references. Example undefined references: vtkXRenderWindowInteractor_Init, > vtkXRenderWindowInteractor::BreakLoopFlag, vtkXRenderWindowInteractor::App, > XtDispatchEvent, vtkXRenderWindowInteractor::vtkXRenderWindowInteractor. > Full make output is in attach "make.log" (it's not a first run). I also > attached Makefile created with ccmake. OS is Linux CentOS 6.5 (gcc 4.4.6). > > What is the problem? Can somebody, please, help me? > > _______________________________________________ > 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: From berk.geveci at kitware.com Fri Aug 14 09:52:47 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Fri, 14 Aug 2015 09:52:47 -0400 Subject: [Paraview] running parallel pvservers In-Reply-To: References: <55B12A0A.6070106@nasa.gov> <55B12F05.6070005@nasa.gov> <55C27815.2080802@nasa.gov> Message-ID: I have been helping Jeff to read his (raw) data using the Nrrd reader in parallel so that there is no need to repartition. Best, -berk On Thu, Aug 13, 2015 at 10:46 PM, David E DeMarle wrote: > Jeff, > > Have you gotten this running? //with Berk's help on the transmit*piece > part? > > best wishes, > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Wed, Aug 5, 2015 at 4:54 PM, Jeff Becker > wrote: > >> Hi David and list. I'm still struggling with distributing my dataset >> (bmag) across nodes. My Python Programmable source script below produces >> correct output when run on a single node. >> >> contr = vtk.vtkMultiProcessController.GetGlobalController() >> nranks = contr.GetNumberOfProcesses() >> rank = contr.GetLocalProcessId() >> >> # read in bmag data and process >> >> executive = self.GetExecutive() >> outInfo = executive.GetOutputInformation(0) >> updateExtent = [executive.UPDATE_EXTENT().Get(outInfo, i) for i in >> xrange(6)] >> imageData = self.GetOutput() >> imageData.SetExtent(updateExtent) >> myout = ns.numpy_to_vtk(bmag.ravel(),1,vtk.VTK_FLOAT) >> myout.SetName("B field magnitude") >> imageData.GetPointData().SetScalars(myout) >> >> >> I then used the Filters/Parallel/Testing/Python/testTransmit.py test code >> as a basis to continue the script to work on multiple nodes. Following the >> last line above, I added: >> >> da = vtk.vtkIntArray() >> da.SetNumberOfTuples(6) >> if rank == 0: >> ext = imageData.GetExtent() >> for i in range(6): >> da.SetValue(i,ext[i]) >> contr.Broadcast(da,0) >> >> ext = [] >> for i in range(6): >> ext.append(da.GetValue(i)) >> ext = tuple(ext) >> >> tp = vtk.vtkTrivialProducer() >> tp.SetOutput(imageData) >> tp.SetWholeExtent(ext) >> >> xmit = vtk.vtkTransmitImageDataPiece() >> xmit.SetInputConnection(tp.GetOutputPort()) >> xmit.UpdateInformation() >> xmit.SetUpdateExtent(rank, nranks, 0) >> xmit.Update() >> >> However, when I run this on two nodes, it looks like both of them get the >> same half of the data, rather than the whole dataset getting split between >> the two. Can anyone see what might be wrong? 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 >> 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 >>> 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: From stefan.ringe.tum at gmail.com Fri Aug 14 10:00:03 2015 From: stefan.ringe.tum at gmail.com (Stefan Ringe) Date: Fri, 14 Aug 2015 16:00:03 +0200 Subject: [Paraview] potential mapped on isosurface Message-ID: <55CDF463.4010004@gmail.com> Hi! I have datafiles of type: x y z f(x,y,z) so 4 columns with datapoints. The grid is not regular. Until now I load the files as VTK particle files and plotting works fine. Now I have two files, a density file (x y z rho(x,y,z)) and a potential file (x y z phi(x,y,z)). I want to plot a contour map of phi on an isodensity surface of rho. How can I do this? thanks! Stefan Ringe From cory.quammen at kitware.com Fri Aug 14 10:07:49 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 14 Aug 2015 10:07:49 -0400 Subject: [Paraview] potential mapped on isosurface In-Reply-To: <55CDF463.4010004@gmail.com> References: <55CDF463.4010004@gmail.com> Message-ID: Stefan, To combine data from these files, I suggest using the Resample With Data Set Filter. Set the Input to your phi file and the Source to your isocontour. Your phi variable should now be available to color with in the ResampleWithDataset filter in the pipeline browser. Cory On Fri, Aug 14, 2015 at 10:00 AM, Stefan Ringe wrote: > Hi! > > I have datafiles of type: > > x y z f(x,y,z) > > so 4 columns with datapoints. The grid is not regular. Until now I load > the files as VTK particle files and plotting works fine. Now I have two > files, a density file (x y z rho(x,y,z)) and a potential file (x y z > phi(x,y,z)). I want to plot a contour map of phi on an isodensity surface > of rho. How can I do this? > > thanks! > > Stefan Ringe > _______________________________________________ > 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: From stefan.ringe.tum at gmail.com Fri Aug 14 11:05:42 2015 From: stefan.ringe.tum at gmail.com (Stefan Ringe) Date: Fri, 14 Aug 2015 17:05:42 +0200 Subject: [Paraview] potential mapped on isosurface Message-ID: <55CE03C6.4030507@gmail.com> Thanks for the reply! I already heard of the filter, but I cannot use it. If I select my data and go to filters it is always greyed out. How can I assign the imported data to "source" or "Input"? Stefan From stefan.ringe.tum at gmail.com Fri Aug 14 11:25:11 2015 From: stefan.ringe.tum at gmail.com (Stefan Ringe) Date: Fri, 14 Aug 2015 17:25:11 +0200 Subject: [Paraview] potential mapped on isosurface Message-ID: <55CE0857.8010202@gmail.com> Made it work now. I had to apply a filter first to the dataset. After that i could select the option. From dan.lipsa at kitware.com Fri Aug 14 11:56:47 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Fri, 14 Aug 2015 11:56:47 -0400 Subject: [Paraview] [vtkusers] (no subject) In-Reply-To: References: <13DD8C6B6309B94AA144319F72195FFD3731A238@IWMDAG2.iwm.fraunhofer.de> <13DD8C6B6309B94AA144319F72195FFD3731A521@IWMDAG2.iwm.fraunhofer.de> Message-ID: Here is the bug I filed for this: http://www.vtk.org/Bug/view.php?id=15653 On Fri, Aug 7, 2015 at 12:39 PM, Dan Lipsa wrote: > Raphael, > In talking to Dave, it seems that indeed you have found a bug in the > writer (and in the specification). It does not seem to be a way to save > field data unless your dataset is of type FIELD (a collection of arrays). > The arrays attached to POINT_DATA (or CELL_DATA) which are designated as > FIELD have to have the same number of tuples as the points (or cells). The > terminology is kind of confusing as well. Would you mind filing a bug > report. Thanks, > Dan > > > On Fri, Aug 7, 2015 at 10:16 AM Dan Lipsa wrote: > >> Hi Raphael, >> >> On Fri, Aug 7, 2015 at 5:02 AM Schubert, Raphael < >> raphael.schubert at iwm.fraunhofer.de> wrote: >> >>> The way I understand the file format specification it should be illegal >>> to define a FIELD dataset in addition to, e.g, STRUCTURED_POINTS, as I can >>> find it neither explicitly allowed (there is only mention of one dataset >>> per file) nor presented in an example. It therefore seems like an >>> accidental feature in vtk that I can actually read back the produced files. >>> >> >> A FIELD dataset is a way to specify data without topological or >> geometrical structure. One can also define FIELD arrays after CELL_DATA or >> POINT_DATA for a dataset. Look at the first example on page 7. In the >> CELL_DATA section there is a field arrays. >> >> >> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan.ringe.tum at gmail.com Fri Aug 14 12:16:14 2015 From: stefan.ringe.tum at gmail.com (Stefan Ringe) Date: Fri, 14 Aug 2015 18:16:14 +0200 Subject: [Paraview] smoothing isosurfaces on unstructured grids Message-ID: <55CE144E.80202@gmail.com> Hi! I am using unstructured grid files of format x y z f(x,y,z) (so 4 columns of data points) which I import as VTK particle data. I want to plot a smooth isosurface. I already tried the Delaunay3d, but there are 2 main problems with it. 1. it seems to cut off hills of my surface and create straigt lines to combine the top of the hills, so that in the end it looks like there are really large areas on the surface spanning from one hill to the other. 2. my function is also not that smooth so I would like to smooth the result in the end. However the smooth filter is greyed out, if I select my data file or the Delaunay3d input, Stefan From cory.quammen at kitware.com Fri Aug 14 13:17:51 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 14 Aug 2015 13:17:51 -0400 Subject: [Paraview] smoothing isosurfaces on unstructured grids In-Reply-To: <55CE144E.80202@gmail.com> References: <55CE144E.80202@gmail.com> Message-ID: Stefan, Delaunay 3D will give you the convex hull of the points in your isosurface, which likely isn't what you want. Try the Extract Surface filter on your file first, then apply the Smooth filter. HTH, Cory On Fri, Aug 14, 2015 at 12:16 PM, Stefan Ringe wrote: > Hi! > > I am using unstructured grid files of format x y z f(x,y,z) (so 4 columns > of data points) which I import as VTK particle data. I want to plot a > smooth isosurface. I already tried the Delaunay3d, but there are 2 main > problems with it. 1. it seems to cut off hills of my surface and create > straigt lines to combine the top of the hills, so that in the end it looks > like there are really large areas on the surface spanning from one hill to > the other. 2. my function is also not that smooth so I would like to smooth > the result in the end. However the smooth filter is greyed out, if I select > my data file or the Delaunay3d input, > > Stefan > _______________________________________________ > 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: From stefan.ringe.tum at gmail.com Fri Aug 14 13:38:15 2015 From: stefan.ringe.tum at gmail.com (Stefan Ringe) Date: Fri, 14 Aug 2015 19:38:15 +0200 Subject: [Paraview] smoothing isosurfaces on unstructured grids Message-ID: <55CE2787.1010305@gmail.com> Hi! Thanks for the reply. I tried to apply the extract surface filter to the set of points, but it had no effect at all. Do I have to consider something specific? From cory.quammen at kitware.com Fri Aug 14 13:59:40 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 14 Aug 2015 13:59:40 -0400 Subject: [Paraview] smoothing isosurfaces on unstructured grids In-Reply-To: <55CE2787.1010305@gmail.com> References: <55CE2787.1010305@gmail.com> Message-ID: Stefan, I assume this is in reference to your earlier email about smoothing an isosurface. I think I misunderstood the problem with the Smooth filter being grayed out. You actually need to highlight the Contour filter in your pipeline browser and then select Smooth. It should not be grayed out. HTH, Cory On Fri, Aug 14, 2015 at 1:38 PM, Stefan Ringe wrote: > Hi! Thanks for the reply. I tried to apply the extract surface filter to > the set of points, but it had no effect at all. Do I have to consider > something specific? > _______________________________________________ > 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: From stefan.ringe.tum at gmail.com Fri Aug 14 14:05:12 2015 From: stefan.ringe.tum at gmail.com (Stefan Ringe) Date: Fri, 14 Aug 2015 20:05:12 +0200 Subject: [Paraview] smoothing isosurfaces on unstructured grids Message-ID: <55CE2DD8.7030402@gmail.com> But in order to use the contour filter, I have to run Delauney first right? So I cannot use the contour filter directly on my point data, can I? Because it seems to just give nothing, if I apply it. From pulido at lanl.gov Fri Aug 14 14:52:13 2015 From: pulido at lanl.gov (Pulido, Jesus) Date: Fri, 14 Aug 2015 18:52:13 +0000 Subject: [Paraview] Memory seeking problems in using the xdmf2 reader In-Reply-To: References: , Message-ID: Hi David, Here's the output from the code changes (parsed output of one scalar field), focusing on XdmfValuesBinary.cxx. XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 231 (Accessing Binary CDATA) Seek as string is 3221225664 XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 267 (Data Size : 134217728) XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 268 (Size[Byte]: 1073741824) XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 269 ( Byte 8) XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 287 (Opening Binary Data for Reading : F:/rstrt//r SEEK as size_t is 2147483647 XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 322 (Seek: 2147483647) XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 331 (Hyperslab data) XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 161 (Reduce Rank: 3 to 1) XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 178 (Contiguous byte: 1073741824) As a string, it looks like the seek location is being read right. Somewhere when it's converted to size_t, it defaults to 2147483647. Jesus ________________________________ From: David E DeMarle [dave.demarle at kitware.com] Sent: Friday, August 14, 2015 6:33 AM To: Pulido, Jesus Cc: paraview at paraview.org Subject: Re: [Paraview] Memory seeking problems in using the xdmf2 reader Mind trying this? diff --git a/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfValuesBinary.cxx b/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfValuesBinary.cxx index 04ea0a7..d4cb2ed 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(atoi(this->Seek)); + return static_cast(atol(this->Seek)); } @@ -244,6 +244,7 @@ XdmfValuesBinary::Read(XdmfArray *anArray){ }else{ this->Seek = NULL; } + cerr << "Seek as string is " << Value << endl; } { XdmfConstString Value = this->Get("Compression"); @@ -291,6 +292,7 @@ XdmfValuesBinary::Read(XdmfArray *anArray){ //strcpy(path+strlen(this->DOM->GetWorkingDirectory()), DataSetName); try{ size_t seek = this->getSeek(); + cerr << "SEEK as size_t is " << seek << endl; switch(getCompressionType()){ case Zlib: XdmfDebug("Compression: Zlib"); 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 5:55 PM, Pulido, Jesus > wrote: 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(atoi(this->Seek)); + return static_cast(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 > 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: From stefan.ringe.tum at gmail.com Fri Aug 14 15:18:57 2015 From: stefan.ringe.tum at gmail.com (Stefan Ringe) Date: Fri, 14 Aug 2015 21:18:57 +0200 Subject: [Paraview] Paraview gives error for TableToStructuredDataFilter Message-ID: <55CE3F21.3070508@gmail.com> Hi. Tried to load a simple csv file: x coord, y coord, z coord, scalar 0, 0, 0, 0 1, 0, 0, 1 0, 1, 0, 2 1, 1, 0, 3 -0.5, -0.5, 1, 4 0.5, -0.5, 1, 5 -0.5, 0.5, 1, 6 0.5, 0.5, 1, 7 That worked. But when I used the TableToStructuredDataFilter, I get an error: (I already set the array ranges correctly...), I use Paraview 4.0.1-1 ERROR: In /tmp/buildd/paraview-4.0.1/VTK/Filters/General/vtkTableToStructuredGrid.cxx, line 97 vtkPTableToStructuredGrid (0x1cb7910): The input table must have exactly 1 rows. Currently it has 8 rows. ERROR: In /tmp/buildd/paraview-4.0.1/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 754 vtkPVCompositeDataPipeline (0x1ce0520): Algorithm vtkPTableToStructuredGrid(0x1cb7910) returned failure for request: vtkInformation (0x2219bc0) Debug: Off Modified Time: 100264 Reference Count: 1 Registered Events: (none) Request: REQUEST_DATA FORWARD_DIRECTION: 0 FROM_OUTPUT_PORT: 0 ALGORITHM_AFTER_FORWARD: 1 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pulido at lanl.gov Fri Aug 14 16:11:23 2015 From: pulido at lanl.gov (Pulido, Jesus) Date: Fri, 14 Aug 2015 20:11:23 +0000 Subject: [Paraview] Memory seeking problems in using the xdmf2 reader In-Reply-To: References: , , Message-ID: Hi David, I ran a test and now I can confirm that the problem has been fixed by changing atoi on line 187 to "atof". Trying "atol" as previously suggested did not seem to work but "atof" does. Thank you for helping us debug this problem, at least on our self-compiled version we can now read large xmf binary files. Cheers, Jesus ________________________________ From: Pulido, Jesus Sent: Friday, August 14, 2015 12:52 PM To: David E DeMarle Cc: paraview at paraview.org Subject: RE: [Paraview] Memory seeking problems in using the xdmf2 reader Hi David, Here's the output from the code changes (parsed output of one scalar field), focusing on XdmfValuesBinary.cxx. XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 231 (Accessing Binary CDATA) Seek as string is 3221225664 XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 267 (Data Size : 134217728) XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 268 (Size[Byte]: 1073741824) XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 269 ( Byte 8) XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 287 (Opening Binary Data for Reading : F:/rstrt//r SEEK as size_t is 2147483647 XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 322 (Seek: 2147483647) XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 331 (Hyperslab data) XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 161 (Reduce Rank: 3 to 1) XDMF Debug : ..\..\..\..\..\..\VTK\ThirdParty\xdmf2\vtkxdmf2\libsrc\XdmfValuesBinary.cxx line 178 (Contiguous byte: 1073741824) As a string, it looks like the seek location is being read right. Somewhere when it's converted to size_t, it defaults to 2147483647. Jesus ________________________________ From: David E DeMarle [dave.demarle at kitware.com] Sent: Friday, August 14, 2015 6:33 AM To: Pulido, Jesus Cc: paraview at paraview.org Subject: Re: [Paraview] Memory seeking problems in using the xdmf2 reader Mind trying this? diff --git a/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfValuesBinary.cxx b/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfValuesBinary.cxx index 04ea0a7..d4cb2ed 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(atoi(this->Seek)); + return static_cast(atol(this->Seek)); } @@ -244,6 +244,7 @@ XdmfValuesBinary::Read(XdmfArray *anArray){ }else{ this->Seek = NULL; } + cerr << "Seek as string is " << Value << endl; } { XdmfConstString Value = this->Get("Compression"); @@ -291,6 +292,7 @@ XdmfValuesBinary::Read(XdmfArray *anArray){ //strcpy(path+strlen(this->DOM->GetWorkingDirectory()), DataSetName); try{ size_t seek = this->getSeek(); + cerr << "SEEK as size_t is " << seek << endl; switch(getCompressionType()){ case Zlib: XdmfDebug("Compression: Zlib"); 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 5:55 PM, Pulido, Jesus > wrote: 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(atoi(this->Seek)); + return static_cast(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 > 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: From stefan.ringe.tum at gmail.com Fri Aug 14 16:20:46 2015 From: stefan.ringe.tum at gmail.com (Stefan Ringe) Date: Fri, 14 Aug 2015 22:20:46 +0200 Subject: [Paraview] Paraview gives error for TableToStructuredDataFilter Message-ID: <55CE4D9E.2080105@gmail.com> My mistake, somehow, I had an error in the array dimensions. Everything works fine. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Aug 14 22:22:24 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 14 Aug 2015 22:22:24 -0400 Subject: [Paraview] smoothing isosurfaces on unstructured grids In-Reply-To: <55CE2DD8.7030402@gmail.com> References: <55CE2DD8.7030402@gmail.com> Message-ID: Looking back through this email thread, I think what you want to do is the following: - Load xyz rho -- Delaunay 3D to create a volume from rho points -- Contour of Delaunay 3D at desired row - Load xyz phi -- Delaunay 3D to create a volume from phi points - Resample With Dataset -- Select the isosurface as the Source and phi Delaunay 3D as Input - color your isosurface with phi On Fri, Aug 14, 2015 at 2:05 PM, Stefan Ringe wrote: > But in order to use the contour filter, I have to run Delauney first > right? So I cannot use the contour filter directly on my point data, can I? > Because it seems to just give nothing, if I apply it. > _______________________________________________ > 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: From ganesh.iitm at gmail.com Sun Aug 16 19:47:24 2015 From: ganesh.iitm at gmail.com (Ganesh Vijayakumar) Date: Sun, 16 Aug 2015 19:47:24 -0400 Subject: [Paraview] scalarBar location In-Reply-To: References: Message-ID: Thanks...I wasn't sure if it's a bug or not. Will report next time. ganesh On Wed, Aug 12, 2015 at 10:57 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Ganesh, > > It'll be something like this: > > lut = GetColorTransferFunction("RTData") > sb = GetScalarBar(a, GetActiveView()) > sb.Position = [x, y] > sb.Position2 = [x2, y2] > sb.Orientation = "Horizontal' # or | "Vertical" > > > I've also reported a bug: http://www.paraview.org/Bug/view.php?id=15640 > > Utkarsh > > > On Mon, Aug 10, 2015 at 7:02 PM, Ganesh Vijayakumar > wrote: > > Dear All, > > > > Could you please help me with setting the location of the scalarBar > > location using python scripting? I'm unable to see any changes to a > python > > script generated by "trace" when I move the scalar bar around. > > > > 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 > > > -- ganesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From ganesh.iitm at gmail.com Sun Aug 16 20:15:20 2015 From: ganesh.iitm at gmail.com (Ganesh Vijayakumar) Date: Sun, 16 Aug 2015 20:15:20 -0400 Subject: [Paraview] CameraParallelProjection vs. InteractionMode in python scripting for renderView objects Message-ID: Hello, Could someone explain me the difference between the two as far as RenderViews are concerned? Is one of them deprecated? In my experience, once renderViewObject.CameraParallelProjection is set to 1, no amount of setting it back to 0 seems to help. Should I stop using CameraParallelProjection for RenderViews? ganesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Aug 17 07:54:15 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 17 Aug 2015 07:54:15 -0400 Subject: [Paraview] scalarBar location In-Reply-To: References: Message-ID: Sure...it generally isn't a bad idea to grab attention on the mailing list in any case. On Sun, Aug 16, 2015 at 7:47 PM, Ganesh Vijayakumar wrote: > Thanks...I wasn't sure if it's a bug or not. Will report next time. > > ganesh > > On Wed, Aug 12, 2015 at 10:57 AM, Utkarsh Ayachit > wrote: >> >> Ganesh, >> >> It'll be something like this: >> >> lut = GetColorTransferFunction("RTData") >> sb = GetScalarBar(a, GetActiveView()) >> sb.Position = [x, y] >> sb.Position2 = [x2, y2] >> sb.Orientation = "Horizontal' # or | "Vertical" >> >> >> I've also reported a bug: http://www.paraview.org/Bug/view.php?id=15640 >> >> Utkarsh >> >> >> On Mon, Aug 10, 2015 at 7:02 PM, Ganesh Vijayakumar >> wrote: >> > Dear All, >> > >> > Could you please help me with setting the location of the scalarBar >> > location using python scripting? I'm unable to see any changes to a >> > python >> > script generated by "trace" when I move the scalar bar around. >> > >> > 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 >> > > > > > > -- > ganesh From Tobias.Beeh at t-online.de Mon Aug 17 11:58:05 2015 From: Tobias.Beeh at t-online.de (Tobias Beeh) Date: Mon, 17 Aug 2015 17:58:05 +0200 Subject: [Paraview] Integrate globe view into custom application Message-ID: <55D2048D.1050208@t-online.de> Hello, our team (11 students from the university of Stuttgart) is trying to build a geovisualization environment on top of paraview. Right now we're planning the architecture, which is quite difficult as no one of us has any previous experience with paraview. We discovered the class vtkGeoView and wondered if we could integrate this view into the paraview UI. If possible we would like to combine this view with other data loaded into the paraview pipeline. Otherwise we would need to re-write the whole vtkGeoView with LoD and dynamic loading because the whole globe hi-res texture is probably too big to load it into the RAM at once - even if not some other large data sets need to fit in there as well. We would like to avoid this of course. Another approach we discussed was to tile the globe for different zoom levels and load only those currently displayed, but we could not find an automated way to reload geometry based on the camera position. Pointers to useful development resources (other than the official paraview guide, documentation, wiki and examples) are appreciated as well. Thank you for your time, Tobias Beeh From shawn.waldon at kitware.com Mon Aug 17 12:18:00 2015 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Mon, 17 Aug 2015 12:18:00 -0400 Subject: [Paraview] Integrate globe view into custom application In-Reply-To: <55D2048D.1050208@t-online.de> References: <55D2048D.1050208@t-online.de> Message-ID: Hi Tobias, I'll let others answer your first few questions since they have more experience there. But I can answer your question about updating based on camera position. On Mon, Aug 17, 2015 at 11:58 AM, Tobias Beeh wrote: > Hello, > > > our team (11 students from the university of Stuttgart) is trying to > build a geovisualization environment on top of paraview. > Right now we're planning the architecture, which is quite difficult as > no one of us has any previous experience with paraview. > > We discovered the class vtkGeoView and wondered if we could integrate > this view into the paraview UI. > If possible we would like to combine this view with other data loaded > into the paraview pipeline. > Otherwise we would need to re-write the whole vtkGeoView with LoD and > dynamic loading because the whole globe hi-res texture is probably too > big to load it into the RAM at once - even if not some other large data > sets need to fit in there as well. > We would like to avoid this of course. > > > Another approach we discussed was to tile the globe for different zoom > levels and load only those currently displayed, but we could not find an > automated way to reload geometry based on the camera position. > To do this you'll want to use the mutliresolution streaming support. There are some details here: http://www.paraview.org/ParaView/index.php/Multi-Resolution_Rendering_with_Overlapping_AMR The best example code is probably in the Streaming Particles plugin. This can be found in the ParaView source tree under Plugins/StreamingParticles. There should be an example data source that produces streamable data as well as the ParaView representation to support streaming. You'll probably have to customize your own versions of both since these were designed to work with sets of points rather than geometry. HTH, --Shawn > > > Pointers to useful development resources (other than the official > paraview guide, documentation, wiki and examples) are appreciated as well. > Thank you for your time, > > Tobias Beeh > > _______________________________________________ > 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: From M.Deij at marin.nl Tue Aug 18 02:28:28 2015 From: M.Deij at marin.nl (Deij-van Rijswijk, Menno) Date: Tue, 18 Aug 2015 06:28:28 +0000 Subject: [Paraview] [Catalyst] segfault during destructor vtkCPProcessor -->vtkPVRenderWindow Message-ID: Hi, I have a headless ParaView build of the HEAD origin/master (commit number 1018) with libOSMesa 10.6.3 as offscreen renderer, to support a Catalyst workflow. Everything works fine, except that the process of MPI-rank 0 will give a segfault when a render window has been used in the catalyst pipeline (this happens also when not running with mpiexec/mpirun). I'm not familiar enough with VTK/PV or gdb to try to solve this on my own, so I post the gdb backtrace here in case someone has an idea what is going on. Any clues on how to fix this are welcome :-) Let me know if you need more information. Best wishes, Menno Deij - van Rijswijk #0 0x00002aaac65a0137 in glIsTextureEXT () from /home/mdeij/Programs/lib/libOSMesa.so.8 #1 0x00002aaac4252def in vtkOpenGLTexture::ReleaseGraphicsResources (this=0x2, win=0x0) at /home/mdeij/src/ParaView/VTK/Rendering/OpenGL/vtkOpenGLTexture.cxx:80 #2 0x00002aaac01ef377 in vtkPVScalarBarActor::ReleaseGraphicsResources (this=0x2, window=0x0) at /home/mdeij/src/ParaView/ParaViewCore/VTKExtensions/Rendering/vtkPVScalarBarActor.cxx:176 #3 0x00002aaac4bc0584 in vtkScalarBarRepresentation::ReleaseGraphicsResources (this=0x2, w=0x0) at /home/mdeij/src/ParaView/VTK/Interaction/Widgets/vtkScalarBarRepresentation.cxx:227 #4 0x00002aaaaf6f1522 in vtkRenderer::SetRenderWindow (this=0x2, renwin=0x0) at /home/mdeij/src/ParaView/VTK/Rendering/Core/vtkRenderer.cxx:1211 #5 0x00002aaaaf6f4f65 in vtkRenderWindow::RemoveRenderer (this=0x2, ren=0x0) at /home/mdeij/src/ParaView/VTK/Rendering/Core/vtkRenderWindow.cxx:831 #6 0x00002aaabe043c85 in vtkPVRenderView::~vtkPVRenderView (this=0x68f1de0) at /home/mdeij/src/ParaView/ParaViewCore/ClientServerCore/Rendering/vtkPVRenderView.cxx:426 #7 0x00002aaabe043c3a in vtkPVRenderView::~vtkPVRenderView (this=0x2) at /home/mdeij/src/ParaView/ParaViewCore/ClientServerCore/Rendering/vtkPVRenderView.cxx:567 #8 0x00002aaab4a9c446 in vtkSmartPointerBase::operator= (this=0x2, r=0x0) at /home/mdeij/src/ParaView/VTK/Common/Core/vtkSmartPointerBase.cxx:75 #9 0x00002aaaaebdded3 in vtkSIProxy::~vtkSIProxy (this=0x68f1a00) at /home/mdeij/src/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx:93 #10 0x00002aaaaebdde9a in vtkSIProxy::~vtkSIProxy (this=0x2) from /home/mdeij/src/build_ParaView/lib/libvtkPVServerImplementationCore-pv4.3.so.1 #11 0x00002aaaaebbe523 in ~vtkInternals (this=, $30=) at /home/mdeij/src/ParaView/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:125 #12 vtkPVSessionCore::~vtkPVSessionCore (this=0x39fd830) at /home/mdeij/src/ParaView/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:351 #13 0x00002aaaaebbe3aa in vtkPVSessionCore::~vtkPVSessionCore (this=0x2) from /home/mdeij/src/build_ParaView/lib/libvtkPVServerImplementationCore-pv4.3.so.1 #14 0x00002aaaaebbb867 in vtkPVSessionBase::~vtkPVSessionBase (this=0x39fdc80) at /home/mdeij/src/ParaView/ParaViewCore/ServerImplementation/Core/vtkPVSessionBase.cxx:86 #15 0x00002aaaae8b873a in vtkSMSession::~vtkSMSession (this=0x2) from /home/mdeij/src/build_ParaView/lib/libvtkPVServerManagerCore-pv4.3.so.1 #16 0x00002aaaaee83d01 in ~vtkSmartPointer (this=, $3=) at /home/mdeij/src/ParaView/VTK/Common/Core/vtkSmartPointer.h:26 #17 ~pair (this=, $2=) at /usr/include/c++/4.4.7/bits/stl_pair.h:67 #18 destroy (this=, __p=, $0=, $1=) at /usr/include/c++/4.4.7/ext/new_allocator.h:115 #19 _M_destroy_node (this=, __p=, $8=, $9=) at /usr/include/c++/4.4.7/bits/stl_tree.h:383 #20 _M_erase (this=, __x=, $5=, $6=) at /usr/include/c++/4.4.7/bits/stl_tree.h:972 #21 clear (this=0x0, $3=) at /usr/include/c++/4.4.7/bits/stl_tree.h:726 #22 clear (this=, $2=) at /usr/include/c++/4.4.7/bits/stl_map.h:626 #23 vtkProcessModule::Finalize () at /home/mdeij/src/ParaView/ParaViewCore/ClientServerCore/Core/vtkProcessModule.cxx:290 #24 0x00002aaaad674142 in vtkInitializationHelper::Finalize () at /home/mdeij/src/ParaView/ParaViewCore/ServerManager/SMApplication/vtkInitializationHelper.cxx:279 #25 0x00002aaaad242e48 in vtkCPCxxHelper::~vtkCPCxxHelper (this=0x2840fe0) at /home/mdeij/src/ParaView/CoProcessing/Catalyst/vtkCPCxxHelper.cxx:58 #26 0x00002aaaad242dfa in vtkCPCxxHelper::~vtkCPCxxHelper (this=0x2) at /home/mdeij/src/ParaView/CoProcessing/Catalyst/vtkCPCxxHelper.cxx:124 #27 0x00002aaaad246ad2 in vtkCPProcessor::~vtkCPProcessor (this=0x3a0cbd0) at /home/mdeij/src/ParaView/CoProcessing/Catalyst/vtkCPProcessor.cxx:66 #28 0x00002aaaad246a4a in vtkCPProcessor::~vtkCPProcessor (this=0x2) at /home/mdeij/src/ParaView/CoProcessing/Catalyst/vtkCPProcessor.cxx:278 dr. ir. Menno A. Deij-van Rijswijk Researcher / Software Engineer Maritime Simulation & Software Group E mailto:M.Deij at marin.nl T +31 317 49 35 06 MARIN 2, Haagsteeg, P.O. Box 28, 6700 AA Wageningen, The Netherlands T +31 317 49 39 11, F +31 317 49 32 45, I www.marin.nl From berger at chem.helsinki.fi Tue Aug 18 03:25:21 2015 From: berger at chem.helsinki.fi (berger at chem.helsinki.fi) Date: Tue, 18 Aug 2015 10:25:21 +0300 Subject: [Paraview] screenshot of high-res LIC plot (4.2.0 precompiled on mac yosemite) Message-ID: <0fc03ba44314b8a654060ae5659fa887.squirrel@www.chem.helsinki.fi> Hello, when I try to get a high-resolution (higher than windows or even display size) resolution from a surface LIC plot using: File->Save Screenshot and adjusting here the resolution (for example 2048x2048) I get a plots with ugly borders that are apparently patched from plots of the size of my "Render View" window. What would we the proper way to get such high resolution plots? greetings R.B. From antech777 at gmail.com Tue Aug 18 06:50:50 2015 From: antech777 at gmail.com (Andrew) Date: Tue, 18 Aug 2015 13:50:50 +0300 Subject: [Paraview] Compiling ParaView 4.3.1 with OpenMPI Message-ID: Hello. I need to compile ParaView 4.3.1 with MPI. I tried different settings but I can't get rid of this error: /usr/bin/ld: warning: libmpi_cxx.so.1, needed by ../lib/libvtkPVServerManagerApplication-pv4.3.so.1, not found (try using -rpath or -rpath-link) /usr/bin/ld: warning: libmpi.so.1, needed by ../lib/libvtkPVServerManagerApplication-pv4.3.so.1, not found (try using -rpath or -rpath-link) I use OpenMPI 1.8.4 that was successfuly compiled and installed in /Programs/openmpi-1.8.4/build (not into system directories, I need to have programs installed into custom directories). So I set the following options for MPI: MPIEXEC:FILEPATH=/Programs/openmpi-1.8.4/build/bin/mpiexec MPIEXEC_MAX_NUMPROCS:STRING=8 MPIEXEC_NUMPROC_FLAG:STRING=-np MPIEXEC_POSTFLAGS:STRING= MPIEXEC_PREFLAGS:STRING= MPI_CXX_COMPILER:FILEPATH=/Programs/openmpi-1.8.4/build/bin/mpicxx MPI_CXX_COMPILE_FLAGS:STRING=-Wl,-rpath -Wl,/Programs/openmpi-1.8.4/build/lib/ MPI_CXX_INCLUDE_PATH:STRING=/Programs/openmpi-1.8.4/build/include/ MPI_CXX_LIBRARIES:STRING=-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/ MPI_CXX_LINK_FLAGS:STRING= MPI_C_COMPILER:FILEPATH=/Programs/openmpi-1.8.4/build/bin/mpicc MPI_C_COMPILE_FLAGS:STRING=-Wl,-rpath -Wl,/Programs/openmpi-1.8.4/build/lib/ MPI_C_INCLUDE_PATH:STRING=/Programs/openmpi-1.8.4/build/include/ MPI_C_LIBRARIES:STRING=-lmpi -L/Programs/openmpi-1.8.4/build/lib/ MPI_C_LINK_FLAGS:STRING= MPI_EXTRA_LIBRARY:STRING=MPI_EXTRA_LIBRARY-NOTFOUND MPI_Fortran_COMPILER:FILEPATH=/Programs/openmpi-1.8.4/build/bin/mpif90 MPI_Fortran_COMPILE_FLAGS:STRING=-Wl,-rpath -Wl,/Programs/openmpi-1.8.4/build/lib/ MPI_Fortran_INCLUDE_PATH:STRING=/Programs/openmpi-1.8.4/build/include/ MPI_Fortran_LIBRARIES:STRING=-lmpi_mpifh -L/Programs/openmpi-1.8.4/build/lib/ MPI_Fortran_LINK_FLAGS:STRING= MPI_LIBRARY:FILEPATH=-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib It's a copy from the Makefile without comments. Actually I used ccmake to configure and generate Makefile. Compilation is normal until 98%. Then a number of errors appear because the linker cannot find MPI libraries (libmpi.so.1 and libmpi_cxx.so.1). I verified that these files are in "/Programs/openmpi-1.8.4/build/lib/" (searched with file manager to avoid typos, files are there). The interesting moment is that libmpi.so and libmpi_cxx.so are found (I don't point to *.so files, point only to lib directory). But then linker don't want to follow symlinks (libmpi.so => libmpi.so.1), if I get it right. I attached CMakeCache.txt file. If it's needed, I will post other details (Makefile + CMakeCache are too big for 500 KB limit of mailing list). Please, help me to compile ParaView with OpenMPI. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- # This is the CMakeCache file. # For build in directory: /Programs/ParaView-4.3.1/build-catalyst # It was generated by CMake: /usr/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 IceT with shared libraries. BUILD_SHARED_LIBS:BOOL=ON //Build the testing tree. BUILD_TESTING:BOOL=OFF //Build With User Defined Values BUILD_USER_DEFINED_LIBS:BOOL=OFF //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 minsize builds. CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds (/MD /Ob1 /Oi // /Ot /Oy /Gs will produce slightly less optimized but smaller // files). CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during Release with Debug Info builds. 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 minsize builds. CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds (/MD /Ob1 /Oi // /Ot /Oy /Gs will produce slightly less optimized but smaller // files). CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during Release with Debug Info builds. 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 minsize builds. CMAKE_Fortran_FLAGS_MINSIZEREL:STRING=-Os //Flags used by the compiler during release builds (/MD /Ob1 /Oi // /Ot /Oy /Gs will produce slightly less optimized but smaller // files). CMAKE_Fortran_FLAGS_RELEASE:STRING=-O3 //Flags used by the compiler during Release with Debug Info builds. CMAKE_Fortran_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //Install path prefix, prepended onto install directories. CMAKE_INSTALL_PREFIX:PATH=/usr/local //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=/usr/bin/gcov //Extra command line flags to pass to the coverage tool COVERAGE_EXTRA_FLAGS:STRING=-l //Enable to build Debian packages CPACK_BINARY_DEB:BOOL=OFF //Enable to build NSIS packages CPACK_BINARY_NSIS:BOOL=OFF //Enable to build RPM packages CPACK_BINARY_RPM:BOOL=OFF //Enable to build STGZ packages CPACK_BINARY_STGZ:BOOL=ON //Enable to build TBZ2 packages CPACK_BINARY_TBZ2:BOOL=OFF //Enable to build TGZ packages CPACK_BINARY_TGZ:BOOL=ON //Enable to build TZ packages CPACK_BINARY_TZ:BOOL=ON //Enable to build TBZ2 source packages CPACK_SOURCE_TBZ2:BOOL=ON //Enable to build TGZ source packages CPACK_SOURCE_TGZ:BOOL=ON //Enable to build TZ source packages CPACK_SOURCE_TZ:BOOL=ON //Enable to build ZIP source packages CPACK_SOURCE_ZIP:BOOL=OFF //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 //Maximum time allowed before CTest will kill the test. CTEST_TEST_TIMEOUT:STRING=3600 //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=3600 //Value Computed by CMake DICOMParser_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/Utilities/DICOMParser //Value Computed by CMake DICOMParser_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/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=/Programs/ParaView-4.3.1/source-std/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=/Programs/ParaView-4.3.1/build-catalyst/Plugins/EyeDomeLighting //Value Computed by CMake EyeDomeLighting_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/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=/Programs/ParaView-4.3.1/source-std/Utilities/VisItBridge/databases/GMV //Dependencies for the target GMVReader_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/;general;-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/; //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;vtkhdf5_hl;general;vtkhdf5;general;vtksys;general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/;general;-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/; //Value Computed by CMake HDF5_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/hdf5/vtkhdf5 //Build Static Executabless HDF5_BUILD_STATIC_EXECS:BOOL=OFF //Enable all warnings HDF5_ENABLE_ALL_WARNINGS:BOOL=OFF //Turn on debugging in all packages HDF5_ENABLE_DEBUG_APIS:BOOL=OFF //Build the Direct I/O Virtual File Driver HDF5_ENABLE_DIRECT_VFD:BOOL=ON //embed library info into executables HDF5_ENABLE_EMBEDDED_LIBINFO:BOOL=ON //Enable group five warnings HDF5_ENABLE_GROUPFIVE_WARNINGS:BOOL=OFF //Enable group four warnings HDF5_ENABLE_GROUPFOUR_WARNINGS:BOOL=OFF //Enable group one warnings HDF5_ENABLE_GROUPONE_WARNINGS:BOOL=OFF //Enable group three warnings HDF5_ENABLE_GROUPTHREE_WARNINGS:BOOL=OFF //Enable group two warnings HDF5_ENABLE_GROUPTWO_WARNINGS:BOOL=OFF //Enable group zero warnings HDF5_ENABLE_GROUPZERO_WARNINGS:BOOL=OFF //Instrument The library HDF5_ENABLE_INSTRUMENT:BOOL=OFF //Value Computed by CMake HDF5_HL_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/hdf5/vtkhdf5/hl //Value Computed by CMake HDF5_HL_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/hdf5/vtkhdf5/hl //Value Computed by CMake HDF5_HL_SRC_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/hdf5/vtkhdf5/hl/src //Value Computed by CMake HDF5_HL_SRC_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/hdf5/vtkhdf5/hl/src //CPACK - Disable packaging HDF5_NO_PACKAGES:BOOL=OFF //Package the HDF5 Library Examples Compressed File HDF5_PACK_EXAMPLES:BOOL=OFF //Value Computed by CMake HDF5_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/hdf5/vtkhdf5 //Value Computed by CMake HDF5_SRC_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/hdf5/vtkhdf5/src //Value Computed by CMake HDF5_SRC_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/hdf5/vtkhdf5/src //Execute tests with different VFDs HDF5_TEST_VFD:BOOL=OFF //Enable folder grouping of projects in IDEs. HDF5_USE_FOLDERS:BOOL=ON //Path to a program. HGCOMMAND:FILEPATH=HGCOMMAND-NOTFOUND //Value Computed by CMake ICET_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/ThirdParty/IceT/vtkicet //Sets the preferred `k' value for the radix-k algorithm. This // is the amount of simultaneous messages each process receives. // A value of 8 is generally good on most architectures, but in // others that have slower computation with respect to network // (such as BlueGene), a larger value may give better performance. ICET_MAGIC_K:STRING=8 //Sets the preferred number of times an image may be split. Some // image compositing algorithms prefer to partition the images // such that each process gets a piece. Too many partitions, though, // and you end up spending more time collecting them than you save // balancing the compositing. ICET_MAX_IMAGE_SPLIT:STRING=512 //Value Computed by CMake ICET_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/ThirdParty/IceT/vtkicet //Use MPE to trace MPI communications. This is helpful for developers // trying to measure the performance of parallel compositing algorithms. ICET_USE_MPE:BOOL=OFF //Build MPI communication layer for IceT. ICET_USE_MPI:BOOL=ON //Build OpenGL support layer for IceT. ICET_USE_OPENGL:BOOL=ON //Dependencies for the target IceTCore_LIB_DEPENDS:STATIC=general;m;general;m; //Dependencies for the target IceTGL_LIB_DEPENDS:STATIC=general;m;general;IceTCore;general;/Programs/glu-9.0.0/build/lib/libGLU.so;general;/Programs/mesa-10.5.4/build-llvmpipe/lib/libOSMesa.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 IceTMPI_LIB_DEPENDS:STATIC=general;m;general;IceTCore;general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/; //Value Computed by CMake JsonCpp_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/jsoncpp/vtkjsoncpp //Value Computed by CMake JsonCpp_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/jsoncpp/vtkjsoncpp //Command to build the project MAKECOMMAND:STRING=/usr/bin/gmake -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= //Executable for running MPI programs. MPIEXEC:FILEPATH=/Programs/openmpi-1.8.4/build/bin/mpiexec //Maximum number of processors available to run MPI applications. MPIEXEC_MAX_NUMPROCS:STRING=8 //Flag used by MPI to specify the number of processes for MPIEXEC; // the next option will be the number of processes. MPIEXEC_NUMPROC_FLAG:STRING=-np //These flags will come after all flags given to MPIEXEC. MPIEXEC_POSTFLAGS:STRING= //These flags will be directly before the executable that is being // run by MPIEXEC. MPIEXEC_PREFLAGS:STRING= //Cleared MPI_CXX_COMPILER:FILEPATH=/Programs/openmpi-1.8.4/build/bin/mpicxx //MPI CXX compilation flags MPI_CXX_COMPILE_FLAGS:STRING=-Wl,-rpath -Wl,/Programs/openmpi-1.8.4/build/lib/ //MPI CXX include path MPI_CXX_INCLUDE_PATH:STRING=/Programs/openmpi-1.8.4/build/include/ //MPI CXX libraries to link against MPI_CXX_LIBRARIES:STRING=-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/ //MPI CXX linking flags MPI_CXX_LINK_FLAGS:STRING= //Cleared MPI_C_COMPILER:FILEPATH=/Programs/openmpi-1.8.4/build/bin/mpicc //MPI C compilation flags MPI_C_COMPILE_FLAGS:STRING=-Wl,-rpath -Wl,/Programs/openmpi-1.8.4/build/lib/ //MPI C include path MPI_C_INCLUDE_PATH:STRING=/Programs/openmpi-1.8.4/build/include/ //MPI C libraries to link against MPI_C_LIBRARIES:STRING=-lmpi -L/Programs/openmpi-1.8.4/build/lib/ //MPI C linking flags MPI_C_LINK_FLAGS:STRING= //Extra MPI libraries to link against MPI_EXTRA_LIBRARY:STRING=MPI_EXTRA_LIBRARY-NOTFOUND //Cleared MPI_Fortran_COMPILER:FILEPATH=/Programs/openmpi-1.8.4/build/bin/mpif90 //MPI Fortran compilation flags MPI_Fortran_COMPILE_FLAGS:STRING=-Wl,-rpath -Wl,/Programs/openmpi-1.8.4/build/lib/ //MPI Fortran include path MPI_Fortran_INCLUDE_PATH:STRING=/Programs/openmpi-1.8.4/build/include/ //MPI Fortran libraries to link against MPI_Fortran_LIBRARIES:STRING=-lmpi_mpifh -L/Programs/openmpi-1.8.4/build/lib/ //MPI Fortran linking flags MPI_Fortran_LINK_FLAGS:STRING= //MPI library to link against MPI_LIBRARY:FILEPATH=-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib //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 vtkFiltersMatlab Module_vtkFiltersMatlab:BOOL=OFF //Request building vtkFiltersParallelGeometry Module_vtkFiltersParallelGeometry: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 vtkIOMPIParallel Module_vtkIOMPIParallel:BOOL=OFF //Request building vtkIOMySQL Module_vtkIOMySQL:BOOL=OFF //Request building vtkIOODBC Module_vtkIOODBC: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 vtkPVCatalystTestDriver Module_vtkPVCatalystTestDriver:BOOL=OFF //Request building vtkPVVTKExtensionsCosmoTools Module_vtkPVVTKExtensionsCosmoTools:BOOL=OFF //Request building vtkParaViewWebDocumentation Module_vtkParaViewWebDocumentation: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 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 vtkTestingGenericBridge Module_vtkTestingGenericBridge: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 vtklibproj4 Module_vtklibproj4: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; //Specify default maximum number of elements in the file chunk // cache chunk for HDF5 files (should be prime number). NETCDF4_CHUNK_CACHE_NELEMS:STRING=1009 //Specify default file chunk cache preemption policy for HDF5 files // (a number between 0 and 1, inclusive). NETCDF4_CHUNK_CACHE_PREEMPTION:STRING=0.75 //Specify default file cache chunk size for HDF5 files in bytes. NETCDF4_CHUNK_CACHE_SIZE:STRING=4194304 //Specify the number of chunks to store in default per-variable // cache. NETCDF4_DEFAULT_CHUNKS_IN_CACHE:STRING=10 //Specify default size of chunks in bytes. NETCDF4_DEFAULT_CHUNK_SIZE:STRING=4194304 //Specify maximum size (in bytes) for the default per-var chunk // cache. NETCDF4_MAX_DEFAULT_CACHE_SIZE:STRING=67108864 //Disable compiler warnings NETCDF_DISABLE_COMPILER_WARNINGS:BOOL=ON //Build netcdf C++ API NETCDF_ENABLE_CXX:BOOL=ON //Path to NVCONTROL headers (NVCtrlLib.h and NVCtrl.h) NVCtrlLib_INCLUDE_DIR:PATH=NVCtrlLib_INCLUDE_DIR-NOTFOUND //Path to NVCONTROL static library (libXNVCtrl.a) NVCtrlLib_LIBRARY:FILEPATH=NVCtrlLib_LIBRARY-NOTFOUND //Dependencies for the target NonOrthogonalSource_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Path to a file. OPENGL_INCLUDE_DIR:PATH=/Programs/mesa-10.5.4/build-llvmpipe/include //Path to a library. OPENGL_gl_LIBRARY:FILEPATH=/Programs/mesa-10.5.4/build-llvmpipe/lib/libOSMesa.so //Path to a library. OPENGL_glu_LIBRARY:FILEPATH=/Programs/glu-9.0.0/build/lib/libGLU.so //Path to a file. OPENGL_xmesa_INCLUDE_DIR:PATH=OPENGL_xmesa_INCLUDE_DIR-NOTFOUND //Path to a file. OSMESA_INCLUDE_DIR:PATH=/Programs/mesa-10.5.4/build-llvmpipe/include //Path to a library. OSMESA_LIBRARY:FILEPATH=/Programs/mesa-10.5.4/build-llvmpipe/lib/libOSMesa.so //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 Nektar Plugin PARAVIEW_BUILD_PLUGIN_Nektar:BOOL=FALSE //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 //Build ParaView with CosmoTools VTK Extensions PARAVIEW_ENABLE_COSMOTOOLS:BOOL=OFF //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 //Initialize MPI on client-processes by default. Can be overridden // using command line arguments PARAVIEW_INITIALIZE_MPI_ON_CLIENT:BOOL=OFF //When enabled, "make install" will install development files PARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON //Expected Qt version PARAVIEW_QT_VERSION:STRING=4 //Build ParaView with Dax many-core filters PARAVIEW_USE_DAX:BOOL=OFF //Enable IceT (needed for parallel rendering) PARAVIEW_USE_ICE_T:BOOL=ON //Enable MPI support for parallel computing PARAVIEW_USE_MPI:BOOL=ON //Use MPI synchronous-send commands for communication PARAVIEW_USE_MPI_SSEND: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 //Add module mpi4py.MPE PYTHON_ENABLE_MODULE_mpi4py.MPE:BOOL=ON //Add module mpi4py.MPI PYTHON_ENABLE_MODULE_mpi4py.MPI:BOOL=ON //Add module mpi4py.dl PYTHON_ENABLE_MODULE_mpi4py.dl:BOOL=ON //Path to a program. PYTHON_EXECUTABLE:FILEPATH=/usr/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=/usr/include/python2.6 //Path to a library. PYTHON_LIBRARY:FILEPATH=/usr/lib64/libpython2.6.so //Add module mpi4py.MPE shared PYTHON_MODULE_mpi4py.MPE_BUILD_SHARED:BOOL=ON //Add module mpi4py.MPI shared PYTHON_MODULE_mpi4py.MPI_BUILD_SHARED:BOOL=ON //Add module mpi4py.dl shared PYTHON_MODULE_mpi4py.dl_BUILD_SHARED:BOOL=ON //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=/Programs/ParaView-4.3.1/build-catalyst //Value Computed by CMake ParaView_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std //Value Computed by CMake PointSpritePlugin_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/Plugins/PointSprite //Value Computed by CMake PointSpritePlugin_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/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_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 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=QT_QTWEBKIT_INCLUDE_DIR-NOTFOUND //The Qt QTWEBKIT library QT_QTWEBKIT_LIBRARY:STRING= //Path to a library. QT_QTWEBKIT_LIBRARY_DEBUG:FILEPATH=QT_QTWEBKIT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTWEBKIT_LIBRARY_RELEASE:FILEPATH=QT_QTWEBKIT_LIBRARY_RELEASE-NOTFOUND //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=/Programs/ParaView-4.3.1/build-catalyst/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=/Programs/ParaView-4.3.1/source-std/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=AntechPC //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=/Programs/ParaView-4.3.1/build-catalyst/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;general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/;general;-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/; //Value Computed by CMake SciberQuestToolKit_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/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;general;vtkRenderingParallelLIC; //Use HIDDEN visibility support if available. USE_COMPILER_HIDDEN_VISIBILITY:BOOL=ON //Value Computed by CMake VPIC_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/VPIC //Dependencies for the target VPIC_LIB_DEPENDS:STATIC=general;vtksys;general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/;general;-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/; //Value Computed by CMake VPIC_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/VPIC //Value Computed by CMake VTKEXPAT_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/expat/vtkexpat //Value Computed by CMake VTKEXPAT_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/expat/vtkexpat //Value Computed by CMake VTKFREETYPE_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/freetype/vtkfreetype //Value Computed by CMake VTKFREETYPE_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/freetype/vtkfreetype //Value Computed by CMake VTKFTGL_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/ftgl //Value Computed by CMake VTKFTGL_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/ftgl //Value Computed by CMake VTKGL2PS_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/gl2ps/vtkgl2ps //Value Computed by CMake VTKGL2PS_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/gl2ps/vtkgl2ps //Value Computed by CMake VTKJPEG_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/jpeg/vtkjpeg //Value Computed by CMake VTKJPEG_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/jpeg/vtkjpeg //Value Computed by CMake VTKNETCDF_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/netcdf/vtknetcdf //Value Computed by CMake VTKNETCDF_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/netcdf/vtknetcdf //Value Computed by CMake VTKOGGTHEORA_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/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="/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/oggtheora/vtkoggtheora/vtkoggtheora.vscript" //Value Computed by CMake VTKOGGTHEORA_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/oggtheora/vtkoggtheora //Value Computed by CMake VTKPNG_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/png/vtkpng //Value Computed by CMake VTKPNG_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/png/vtkpng //Value Computed by CMake VTKTIFF_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/tiff/vtktiff //Value Computed by CMake VTKTIFF_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/tiff/vtktiff //Value Computed by CMake VTKZLIB_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/zlib/vtkzlib //Value Computed by CMake VTKZLIB_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/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=/Programs/ParaView-4.3.1/build-catalyst/VTK //Request to build all modules VTK_BUILD_ALL_MODULES: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=/Programs/ParaView-4.3.1/source-std/VTK/Utilities/ParseOGLExt/headers/glext.h //Location of the GLX extensions header file (glxext.h). VTK_GLXEXT_FILE:FILEPATH=/Programs/ParaView-4.3.1/source-std/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 full path to mpirun command VTK_MPIRUN_EXE:FILEPATH=/Programs/openmpi-1.8.4/build/bin/mpiexec //Maximum number of processors available to run parallel applications. // (see /Programs/ParaView-4.3.1/source-std/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_MAX_NUMPROCS:STRING=8 //Flag used by mpi to specify the number of processes, the next // option will be the number of processes. (see /Programs/ParaView-4.3.1/source-std/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_NUMPROC_FLAG:STRING=-np //These flags will come after all flags given to MPIRun.(see /Programs/ParaView-4.3.1/source-std/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_POSTFLAGS:STRING= //These flags will be directly before the executable that is being // run by VTK_MPIRUN_EXE. (see /Programs/ParaView-4.3.1/source-std/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_PREFLAGS:STRING= //These flags will be directly before the number of processess // flag (see /Programs/ParaView-4.3.1/source-std/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_PRENUMPROC_FLAGS:STRING= //The OpenGL library being used supports off screen Mesa calls VTK_OPENGL_HAS_OSMESA:BOOL=ON //Python version to use: 2, 2.x, or empty VTK_PYTHON_VERSION:STRING=2 VTK_QT_VERSION:STRING=4 //enable parallel timers for the 2d line integral convolution VTK_RENDERINGPARALLELLIC_LINEINTEGRALCONVLOLUTION2D_TIMER:BOOL=OFF //enable parallel timers for the surface lic painter VTK_RENDERINGPARALLELLIC_SURFACELICPAINTER_TIMER:BOOL=OFF //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=/Programs/ParaView-4.3.1/source-std/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=OFF //Use system-installed icet VTK_USE_SYSTEM_ICET:BOOL=OFF //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 'mpi4py' Python package VTK_USE_SYSTEM_MPI4PY: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 '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=ON //Location of the WGL extensions header file (wglext.h). VTK_WGLEXT_FILE:FILEPATH=/Programs/ParaView-4.3.1/source-std/VTK/Utilities/ParseOGLExt/headers/wglext.h //Path to a file. VTK_WRAP_HINTS:FILEPATH=/Programs/ParaView-4.3.1/source-std/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=/usr/include //Path to a library. X11_XTest_LIB:FILEPATH=/usr/lib64/libXtst.so //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=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/alglib //Value Computed by CMake alglib_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/alglib //Path to a program. file_cmd:FILEPATH=/usr/bin/file //Dependencies for the target mpi4py.MPE_LIB_DEPENDS:STATIC=general;/usr/lib64/libpython2.6.so;general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/; //Dependencies for the target mpi4py.MPI_LIB_DEPENDS:STATIC=general;/usr/lib64/libpython2.6.so;general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/;general;dl; //Dependencies for the target mpi4py.dl_LIB_DEPENDS:STATIC=general;/usr/lib64/libpython2.6.so;general;dl; //Value Computed by CMake mpi4py_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/mpi4py/vtkmpi4py //Value Computed by CMake mpi4py_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/mpi4py/vtkmpi4py //Value Computed by CMake netcdf_cxx_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/netcdf/vtknetcdf/cxx //Value Computed by CMake netcdf_cxx_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/netcdf/vtknetcdf/cxx //Value Computed by CMake netcdf_libdispatch_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch //Value Computed by CMake netcdf_libdispatch_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch //Value Computed by CMake netcdf_liblib_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/netcdf/vtknetcdf/liblib //Value Computed by CMake netcdf_liblib_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/netcdf/vtknetcdf/liblib //Value Computed by CMake netcdf_libsrc4_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4 //Value Computed by CMake netcdf_libsrc4_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4 //Value Computed by CMake netcdf_libsrc_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/netcdf/vtknetcdf/libsrc //Value Computed by CMake netcdf_libsrc_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/netcdf/vtknetcdf/libsrc //Dependencies for the target pmpi-mpe_LIB_DEPENDS:STATIC=general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/; //Dependencies for the target pmpi-vt-hyb_LIB_DEPENDS:STATIC=general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/; //Dependencies for the target pmpi-vt-mpi_LIB_DEPENDS:STATIC=general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/; //Dependencies for the target pmpi-vt_LIB_DEPENDS:STATIC=general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/; //Dependencies for the target protobuf-lite_LIB_DEPENDS:STATIC=general;-lpthread; //Value Computed by CMake protobuf_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/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=/Programs/ParaView-4.3.1/source-std/ThirdParty/protobuf/vtkprotobuf //Path to smooth.flash data file. smooth_flash:FILEPATH=smooth_flash-NOTFOUND //Value Computed by CMake verdict_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/verdict/vtkverdict //Dependencies for target verdict_LIB_DEPENDS:STATIC= //Value Computed by CMake verdict_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/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;/usr/lib64/libpython2.6.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=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/exodusII/vtkexodusII //Value Computed by CMake vtkExodus2_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/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 vtkFiltersImagingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersImaging; //Dependencies for the target vtkFiltersImagingPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersImaging;general;vtkWrappingPythonCore;general;vtkFiltersStatisticsPythonD;general;vtkImagingGeneralPythonD;general;vtkImagingSourcesPythonD; //Dependencies for the target vtkFiltersImagingPython_LIB_DEPENDS:STATIC=general;vtkFiltersImagingPythonD; //Dependencies for the target vtkFiltersImaging_LIB_DEPENDS:STATIC=general;vtkFiltersStatistics;general;vtkImagingGeneral;general;vtkImagingSources; //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 vtkFiltersParallelFlowPathsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelFlowPaths; //Dependencies for the target vtkFiltersParallelFlowPathsPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersParallelFlowPaths;general;vtkWrappingPythonCore;general;vtkFiltersAMRPythonD;general;vtkFiltersFlowPathsPythonD;general;vtkParallelCorePythonD;general;vtkParallelMPIPythonD; //Dependencies for the target vtkFiltersParallelFlowPathsPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelFlowPathsPythonD; //Dependencies for the target vtkFiltersParallelFlowPaths_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkFiltersFlowPaths;general;vtkParallelCore;general;vtkParallelMPI; //Dependencies for the target vtkFiltersParallelImagingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelImaging; //Dependencies for the target vtkFiltersParallelImagingPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersParallelImaging;general;vtkWrappingPythonCore;general;vtkFiltersImagingPythonD;general;vtkFiltersParallelPythonD;general;vtkIOLegacyPythonD;general;vtkImagingCorePythonD;general;vtkParallelCorePythonD; //Dependencies for the target vtkFiltersParallelImagingPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelImagingPythonD; //Dependencies for the target vtkFiltersParallelImaging_LIB_DEPENDS:STATIC=general;vtkFiltersImaging;general;vtkFiltersParallel;general;vtkIOLegacy;general;vtkImagingCore;general;vtkParallelCore; //Dependencies for the target vtkFiltersParallelMPICS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelMPI; //Dependencies for the target vtkFiltersParallelMPIPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersParallelMPI;general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersParallelPythonD;general;vtkImagingCorePythonD;general;vtkParallelCorePythonD;general;vtkParallelMPIPythonD; //Dependencies for the target vtkFiltersParallelMPIPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelMPIPythonD; //Dependencies for the target vtkFiltersParallelMPI_LIB_DEPENDS:STATIC=general;vtkFiltersExtraction;general;vtkFiltersGeneral;general;vtkFiltersParallel;general;vtkImagingCore;general;vtkParallelCore;general;vtkParallelMPI; //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;/usr/lib64/libpython2.6.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;vtkhdf5_hl;general;vtkhdf5;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 vtkIOMPIImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMPIImage; //Dependencies for the target vtkIOMPIImagePythonD_LIB_DEPENDS:STATIC=general;vtkIOMPIImage;general;vtkWrappingPythonCore;general;vtkIOImagePythonD;general;vtkIOImagePythonD;general;vtkParallelMPIPythonD; //Dependencies for the target vtkIOMPIImagePython_LIB_DEPENDS:STATIC=general;vtkIOMPIImagePythonD; //Dependencies for the target vtkIOMPIImage_LIB_DEPENDS:STATIC=general;vtkIOImage;general;vtkIOImage;general;vtkParallelMPI;general;vtksys;general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/;general;-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/; //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 vtkIOParallelNetCDFCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelNetCDF; //Dependencies for the target vtkIOParallelNetCDFPythonD_LIB_DEPENDS:STATIC=general;vtkIOParallelNetCDF;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkParallelMPIPythonD; //Dependencies for the target vtkIOParallelNetCDFPython_LIB_DEPENDS:STATIC=general;vtkIOParallelNetCDFPythonD; //Dependencies for the target vtkIOParallelNetCDF_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkParallelMPI;general;vtkNetCDF;general;vtkNetCDF_cxx;general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/;general;-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/; //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;vtkhdf5_hl;general;vtkhdf5;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 vtkPVCatalystTestDriver_LIB_DEPENDS:STATIC=general;vtkPVCatalyst; //Dependencies for the target vtkPVCatalyst_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtksys;general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/;general;-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/; //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;vtkParallelMPIPythonD;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;vtkParallelMPI;general;vtkPythonInterpreter;general;vtksys;general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/;general;-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/; //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;vtkFiltersParallelFlowPathsPythonD;general;vtkFiltersParallelImagingPythonD;general;vtkFiltersParallelMPIPythonD;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;vtkIOMPIImagePythonD;general;vtkIOMoviePythonD;general;vtkIONetCDFPythonD;general;vtkIOPLYPythonD;general;vtkIOParallelPythonD;general;vtkIOParallelPythonD;general;vtkIOParallelExodusPythonD;general;vtkIOParallelLSDynaPythonD;general;vtkIOParallelNetCDFPythonD;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;vtkParallelMPIPythonD;general;vtkParallelMPI4PyPythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingFreeTypeOpenGLPythonD;general;vtkRenderingLICPythonD;general;vtkRenderingLODPythonD;general;vtkRenderingLabelPythonD;general;vtkRenderingMatplotlibPythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingParallelPythonD;general;vtkRenderingParallelLICPythonD;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;vtkPythonInterpreterCS;general;vtkIOCoreCS;general;vtkIOGeometryCS;general;vtkIOXMLParserCS;general;vtkIOXMLCS;general;vtkDomainsChemistryCS;general;vtkIOLegacyCS;general;vtkParallelCoreCS;general;vtkFiltersAMRCS;general;vtkFiltersFlowPathsCS;general;vtkFiltersGenericCS;general;vtkImagingSourcesCS;general;vtkFiltersHybridCS;general;vtkFiltersHyperTreeCS;general;vtkImagingGeneralCS;general;vtkFiltersImagingCS;general;vtkFiltersModelingCS;general;vtkFiltersParallelCS;general;vtkParallelMPICS;general;vtkFiltersParallelFlowPathsCS;general;vtkFiltersParallelImagingCS;general;vtkFiltersParallelMPICS;general;vtkFiltersParallelStatisticsCS;general;vtkFiltersProgrammableCS;general;vtkFiltersPythonCS;general;vtkFiltersTextureCS;general;vtkFiltersVerdictCS;general;vtkIOAMRCS;general;vtkIOEnSightCS;general;vtkIOExodusCS;general;vtkIOImageCS;general;vtkImagingColorCS;general;vtkRenderingAnnotationCS;general;vtkImagingHybridCS;general;vtkRenderingOpenGLCS;general;vtkRenderingContextOpenGLCS;general;vtkRenderingGL2PSCS;general;vtkRenderingLabelCS;general;vtkIOExportCS;general;vtkIOImportCS;general;vtkIOInfovisCS;general;vtkIOLSDynaCS;general;vtkIOMPIImageCS;general;vtkIOMovieCS;general;vtkIONetCDFCS;general;vtkIOPLYCS;general;vtkIOParallelCS;general;vtkIOParallelExodusCS;general;vtkIOParallelLSDynaCS;general;vtkIOParallelNetCDFCS;general;vtkIOParallelXMLCS;general;vtkIOVPICCS;general;vtkIOXdmf2CS;general;vtkImagingMorphologicalCS;general;vtkInteractionStyleCS;general;vtkRenderingVolumeCS;general;vtkInteractionWidgetsCS;general;vtkInteractionImageCS;general;vtkPVCommonCS;general;vtkPVVTKExtensionsCoreCS;general;vtkPVClientServerCoreCoreCS;general;vtkPVServerImplementationCoreCS;general;vtkPVServerManagerCoreCS;general;vtkRenderingFreeTypeOpenGLCS;general;vtkRenderingLICCS;general;vtkRenderingMatplotlibCS;general;vtkRenderingParallelCS;general;vtkRenderingParallelLICCS;general;vtkPVVTKExtensionsRenderingCS;general;vtkPVVTKExtensionsDefaultCS;general;vtkRenderingVolumeOpenGLCS;general;vtkRenderingVolumeAMRCS;general;vtkViewsCoreCS;general;vtkViewsContext2DCS;general;vtkWebGLExporterCS;general;vtkPVClientServerCoreRenderingCS;general;vtkPVClientServerCoreDefaultCS;general;vtkPVServerImplementationRenderingCS;general;vtkPVServerManagerRenderingCS;general;vtkTestingRenderingCS;general;vtkPVServerManagerDefaultCS;general;vtkPVAnimationCS;general;vtkParallelMPI4PyCS;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;vtkIOMPIImagePythonD;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;vtkIOMPIImage;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;vtkFiltersParallelMPIPythonD;general;vtkIOExportPythonD;general;vtkIOXMLPythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingFreeTypeOpenGLPythonD;general;vtkRenderingLICPythonD;general;vtkRenderingMatplotlibPythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingParallelPythonD;general;vtkRenderingParallelLICPythonD; //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;vtkFiltersParallelMPI;general;vtkIOExport;general;vtkIOXML;general;vtkInteractionStyle;general;vtkInteractionWidgets;general;vtkPVVTKExtensionsCore;general;vtkRenderingAnnotation;general;vtkRenderingFreeTypeOpenGL;general;vtkRenderingLIC;general;vtkRenderingMatplotlib;general;vtkRenderingOpenGL;general;vtkRenderingParallel;general;vtkRenderingParallelLIC;general;IceTCore;general;IceTMPI;general;IceTGL;general;vtkCommonColor;general;vtkzlib;general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/;general;-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/; //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 vtkParallelMPI4PyCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallelMPI4Py; //Dependencies for the target vtkParallelMPI4PyPythonD_LIB_DEPENDS:STATIC=general;vtkParallelMPI4Py;general;vtkWrappingPythonCore;general;vtkParallelMPIPythonD; //Dependencies for the target vtkParallelMPI4PyPython_LIB_DEPENDS:STATIC=general;vtkParallelMPI4PyPythonD; //Dependencies for the target vtkParallelMPI4Py_LIB_DEPENDS:STATIC=general;vtkParallelMPI;general;/usr/lib64/libpython2.6.so;general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/;general;-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/; //Dependencies for the target vtkParallelMPICS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallelMPI; //Dependencies for the target vtkParallelMPIPythonD_LIB_DEPENDS:STATIC=general;vtkParallelMPI;general;vtkWrappingPythonCore;general;vtkParallelCorePythonD; //Dependencies for the target vtkParallelMPIPython_LIB_DEPENDS:STATIC=general;vtkParallelMPIPythonD; //Dependencies for the target vtkParallelMPI_LIB_DEPENDS:STATIC=general;vtkParallelCore;general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/;general;-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/; //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;/usr/lib64/libpython2.6.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;/Programs/glu-9.0.0/build/lib/libGLU.so;general;/Programs/mesa-10.5.4/build-llvmpipe/lib/libOSMesa.so;general;/usr/lib64/libSM.so;general;/usr/lib64/libICE.so;general;/usr/lib64/libX11.so;general;/usr/lib64/libXext.so;general;/Programs/mesa-10.5.4/build-llvmpipe/lib/libOSMesa.so; //Dependencies for the target vtkRenderingParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingParallel; //Dependencies for the target vtkRenderingParallelLICCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingParallelLIC; //Dependencies for the target vtkRenderingParallelLICPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingParallelLIC;general;vtkWrappingPythonCore;general;vtkIOLegacyPythonD;general;vtkParallelMPIPythonD;general;vtkRenderingLICPythonD;general;vtkRenderingOpenGLPythonD; //Dependencies for the target vtkRenderingParallelLICPython_LIB_DEPENDS:STATIC=general;vtkRenderingParallelLICPythonD; //Dependencies for the target vtkRenderingParallelLIC_LIB_DEPENDS:STATIC=general;vtkIOLegacy;general;vtkParallelMPI;general;vtkRenderingLIC;general;vtkRenderingOpenGL;general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/;general;-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/; //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;general;-lmpi -L/Programs/openmpi-1.8.4/build/lib/;general;-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/; //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;/usr/lib64/libpython2.6.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;/usr/lib64/libpython2.6.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;/Programs/mesa-10.5.4/build-llvmpipe/lib/libOSMesa.so;general;/Programs/mesa-10.5.4/build-llvmpipe/lib/libOSMesa.so;general;vtkfreetype; //Dependencies for the target vtkgl2ps_LIB_DEPENDS:STATIC=general;/Programs/mesa-10.5.4/build-llvmpipe/lib/libOSMesa.so;general;/Programs/mesa-10.5.4/build-llvmpipe/lib/libOSMesa.so;general;m;general;vtkzlib;general;vtkpng;general;m; //Dependencies for the target vtkhdf5_LIB_DEPENDS:STATIC=general;m;general;dl;general;rt;general;vtkzlib; //Dependencies for the target vtkhdf5_hl_LIB_DEPENDS:STATIC=general;vtkhdf5; //Dependencies for target vtkjpeg_LIB_DEPENDS:STATIC= //Dependencies for target vtkjsoncpp_LIB_DEPENDS:STATIC= //Value Computed by CMake vtklibxml2_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/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=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/libxml2/vtklibxml2 //Value Computed by CMake vtkmetaio_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/Utilities/MetaIO/vtkmetaio //Dependencies for the target vtkmetaio_LIB_DEPENDS:STATIC=general;vtkzlib; //Value Computed by CMake vtkmetaio_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/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=/Programs/ParaView-4.3.1/build-catalyst/VTK/Utilities/KWSys/vtksys //Dependencies for the target vtksys_LIB_DEPENDS:STATIC=general;dl;general;dl; //Value Computed by CMake vtksys_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/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;vtkhdf5_hl;general;vtkhdf5; //Dependencies for target vtkzlib_LIB_DEPENDS:STATIC= //Value Computed by CMake xdmf2_BINARY_DIR:STATIC=/Programs/ParaView-4.3.1/build-catalyst/VTK/ThirdParty/xdmf2/vtkxdmf2 //Value Computed by CMake xdmf2_SOURCE_DIR:STATIC=/Programs/ParaView-4.3.1/source-std/VTK/ThirdParty/xdmf2/vtkxdmf2 ######################## # INTERNAL cache entries ######################## ALGLIB_SHARED_LIB:INTERNAL=ON //Host Arcitecture : Linux IRIXN32 IRIX64 AIX CYGWIN ARCH_TO_BUILD:INTERNAL=Linux //CXX test BOOL_NOTDEFINED:INTERNAL= //MODIFIED property for variable: BUILD_TESTING BUILD_TESTING-MODIFIED:INTERNAL=ON //ADVANCED property for variable: BZRCOMMAND BZRCOMMAND-ADVANCED:INTERNAL=1 //Have function clock_gettime CLOCK_GETTIME_IN_LIBC:INTERNAL= //Have library posix4 CLOCK_GETTIME_IN_LIBPOSIX4:INTERNAL= //Have library rt CLOCK_GETTIME_IN_LIBRT: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 //ADVANCED property for variable: CMAKE_BUILD_TOOL CMAKE_BUILD_TOOL-ADVANCED:INTERNAL=1 //What is the target build tool cmake is generating for. CMAKE_BUILD_TOOL:INTERNAL=/usr/bin/gmake //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=/Programs/ParaView-4.3.1/build-catalyst //Major version of cmake used to create the current loaded cache CMAKE_CACHE_MAJOR_VERSION:INTERNAL=2 //Minor version of cmake used to create the current loaded cache CMAKE_CACHE_MINOR_VERSION:INTERNAL=8 //Patch version of cmake used to create the current loaded cache CMAKE_CACHE_PATCH_VERSION:INTERNAL=12 //ADVANCED property for variable: CMAKE_COLOR_MAKEFILE CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1 //Path to CMake executable. CMAKE_COMMAND:INTERNAL=/usr/bin/cmake //Path to cpack program executable. CMAKE_CPACK_COMMAND:INTERNAL=/usr/bin/cpack //Path to ctest program executable. CMAKE_CTEST_COMMAND:INTERNAL=/usr/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 //MODIFIED property for variable: CMAKE_CXX_FLAGS CMAKE_CXX_FLAGS-MODIFIED:INTERNAL=ON //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 //MODIFIED property for variable: CMAKE_C_FLAGS CMAKE_C_FLAGS-MODIFIED:INTERNAL=ON //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=/usr/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 //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 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=/Programs/ParaView-4.3.1/source-std //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=225 //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=/usr/share/cmake //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: CPACK_BINARY_DEB CPACK_BINARY_DEB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_NSIS CPACK_BINARY_NSIS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_RPM CPACK_BINARY_RPM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_STGZ CPACK_BINARY_STGZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_TBZ2 CPACK_BINARY_TBZ2-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_TGZ CPACK_BINARY_TGZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_TZ CPACK_BINARY_TZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_SOURCE_TBZ2 CPACK_SOURCE_TBZ2-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_SOURCE_TGZ CPACK_SOURCE_TGZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_SOURCE_TZ CPACK_SOURCE_TZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_SOURCE_ZIP CPACK_SOURCE_ZIP-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 //Result of TRY_COMPILE CXX_HAVE_OFFSETOF:INTERNAL=TRUE //ADVANCED property for variable: DART_TESTING_TIMEOUT DART_TESTING_TIMEOUT-ADVANCED:INTERNAL=1 //Result of TRY_COMPILE DEV_T_IS_SCALAR:INTERNAL=TRUE //ADVANCED property for variable: EXECINFO_LIB EXECINFO_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: EXECUTABLE_OUTPUT_PATH EXECUTABLE_OUTPUT_PATH-ADVANCED:INTERNAL=1 EXECUTABLE_OUTPUT_PATH:INTERNAL=/Programs/ParaView-4.3.1/build-catalyst/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 MPI_C FIND_PACKAGE_MESSAGE_DETAILS_MPI_C:INTERNAL=[-lmpi -L/Programs/openmpi-1.8.4/build/lib/][/Programs/openmpi-1.8.4/build/include/][v()] //Details about finding MPI_CXX FIND_PACKAGE_MESSAGE_DETAILS_MPI_CXX:INTERNAL=[-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/][/Programs/openmpi-1.8.4/build/include/][v()] //Details about finding MPI_Fortran FIND_PACKAGE_MESSAGE_DETAILS_MPI_Fortran:INTERNAL=[-lmpi_mpifh -L/Programs/openmpi-1.8.4/build/lib/][/Programs/openmpi-1.8.4/build/include/][v()] //Details about finding OSMesa FIND_PACKAGE_MESSAGE_DETAILS_OSMesa:INTERNAL=[/Programs/mesa-10.5.4/build-llvmpipe/lib/libOSMesa.so][/Programs/mesa-10.5.4/build-llvmpipe/include][v()] //Details about finding OpenGL FIND_PACKAGE_MESSAGE_DETAILS_OpenGL:INTERNAL=[/Programs/mesa-10.5.4/build-llvmpipe/lib/libOSMesa.so][/Programs/mesa-10.5.4/build-llvmpipe/include][v()] //Details about finding PythonInterp FIND_PACKAGE_MESSAGE_DETAILS_PythonInterp:INTERNAL=[/usr/bin/python2][v2.6.6()] //Details about finding PythonLibs FIND_PACKAGE_MESSAGE_DETAILS_PythonLibs:INTERNAL=[/usr/lib64/libpython2.6.so][/usr/include/python2.6][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()] //Result of TRY_COMPILE GETTIMEOFDAY_GIVES_TZ:INTERNAL=TRUE //ADVANCED property for variable: GITCOMMAND GITCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: GIT_EXECUTABLE GIT_EXECUTABLE-ADVANCED:INTERNAL=1 //Test GLX_DECLARES_FUNCTION_glXGetProcAddress GLX_DECLARES_FUNCTION_glXGetProcAddress:INTERNAL=1 //Test GLX_DECLARES_FUNCTION_glXGetProcAddressARB GLX_DECLARES_FUNCTION_glXGetProcAddressARB:INTERNAL=1 //Test GLX_DECLARES_FUNCTION_glXGetProcAddressARB_AS_EMPTY GLX_DECLARES_FUNCTION_glXGetProcAddressARB_AS_EMPTY:INTERNAL= //Test GLX_DECLARES_FUNCTION_glXGetProcAddress_AS_EMPTY GLX_DECLARES_FUNCTION_glXGetProcAddress_AS_EMPTY:INTERNAL= //Test GLX_DEFINES_MACRO_GLX_ARB_get_proc_address GLX_DEFINES_MACRO_GLX_ARB_get_proc_address:INTERNAL=1 //Test GLX_DEFINES_MACRO_GLX_VERSION_1_1 GLX_DEFINES_MACRO_GLX_VERSION_1_1:INTERNAL=1 //Test GLX_DEFINES_MACRO_GLX_VERSION_1_2 GLX_DEFINES_MACRO_GLX_VERSION_1_2:INTERNAL=1 //Test GLX_DEFINES_MACRO_GLX_VERSION_1_3 GLX_DEFINES_MACRO_GLX_VERSION_1_3:INTERNAL=1 //Test GLX_DEFINES_MACRO_GLX_VERSION_1_4 GLX_DEFINES_MACRO_GLX_VERSION_1_4:INTERNAL=1 //Test GLX_DEFINES_TYPE_GLXFBConfig GLX_DEFINES_TYPE_GLXFBConfig:INTERNAL=1 //Test GLX_DEFINES_TYPE_GLXextFuncPtr GLX_DEFINES_TYPE_GLXextFuncPtr:INTERNAL=1 //Test GLX_DEFINES_TYPE_GLXextFuncPtr_AS_EMPTY GLX_DEFINES_TYPE_GLXextFuncPtr_AS_EMPTY:INTERNAL= //Test GLX_INCLUDES_GLXEXT GLX_INCLUDES_GLXEXT:INTERNAL=1 GLX_USES_MACRO_GLX_GLXEXT_LEGACY:INTERNAL=TRUE //Define if your system generates wrong code for log2 routine H5_BAD_LOG2_CODE_GENERATED:INTERNAL=0 //Other test H5_CXX_HAVE_OFFSETOF:INTERNAL=1 //Other test H5_DEV_T_IS_SCALAR:INTERNAL=1 //Checking IF overflows normally converting floating-point to integer // values H5_FP_TO_INTEGER_OVERFLOW_WORKS:INTERNAL=1 //Result of TRY_COMPILE H5_FP_TO_INTEGER_OVERFLOW_WORKS_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_FP_TO_INTEGER_OVERFLOW_WORKS_RUN:INTERNAL=0 //Checking IF accurately roundup converting floating-point to unsigned // long long values H5_FP_TO_ULLONG_ACCURATE:INTERNAL=1 //Result of TRY_COMPILE H5_FP_TO_ULLONG_ACCURATE_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_FP_TO_ULLONG_ACCURATE_RUN:INTERNAL=0 //Checking IF right maximum converting floating-point to unsigned // long long values H5_FP_TO_ULLONG_RIGHT_MAXIMUM:INTERNAL= //Result of TRY_COMPILE H5_FP_TO_ULLONG_RIGHT_MAXIMUM_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_FP_TO_ULLONG_RIGHT_MAXIMUM_RUN:INTERNAL=1 //Other test H5_GETTIMEOFDAY_GIVES_TZ:INTERNAL=1 //Have function alarm H5_HAVE_ALARM:INTERNAL=1 //Other test H5_HAVE_ATTRIBUTE:INTERNAL=1 //Other test H5_HAVE_C99_DESIGNATED_INITIALIZER:INTERNAL=1 //Other test H5_HAVE_C99_FUNC:INTERNAL=1 //Have symbol tzname H5_HAVE_DECL_TZNAME:INTERNAL=1 //Have function difftime H5_HAVE_DIFFTIME:INTERNAL=1 //Other test H5_HAVE_DIRECT:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h H5_HAVE_DIRENT_H:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;string.h;strings.h;time.h;stdlib.h;memory.h;dlfcn.h H5_HAVE_DLFCN_H:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h H5_HAVE_FEATURES_H:INTERNAL=1 //Have function fork H5_HAVE_FORK:INTERNAL=1 //Have function frexpf H5_HAVE_FREXPF:INTERNAL=1 //Have function frexpl H5_HAVE_FREXPL:INTERNAL=1 //Have function fseeko H5_HAVE_FSEEKO:INTERNAL=1 //Have function fseeko64 H5_HAVE_FSEEKO64:INTERNAL=1 //Have function fstat64 H5_HAVE_FSTAT64:INTERNAL=1 //Have function ftello H5_HAVE_FTELLO:INTERNAL=1 //Have function ftello64 H5_HAVE_FTELLO64:INTERNAL=1 //Have function ftruncate64 H5_HAVE_FTRUNCATE64:INTERNAL=1 //Other test H5_HAVE_FUNCTION:INTERNAL=1 //Have function GetConsoleScreenBufferInfo H5_HAVE_GETCONSOLESCREENBUFFERINFO:INTERNAL= //Have function gethostname H5_HAVE_GETHOSTNAME:INTERNAL=1 //Have function getpwuid H5_HAVE_GETPWUID:INTERNAL=1 //Have function getrusage H5_HAVE_GETRUSAGE:INTERNAL=1 //Have function gettextinfo H5_HAVE_GETTEXTINFO:INTERNAL= //H5_HAVE_GETTIMEOFDAY H5_HAVE_GETTIMEOFDAY:INTERNAL=1 //Have includes sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;globus/common.h H5_HAVE_GLOBUS_COMMON_H:INTERNAL= //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;string.h;strings.h;time.h;stdlib.h;memory.h;dlfcn.h;inttypes.h H5_HAVE_INTTYPES_H:INTERNAL=1 //Have function ioctl H5_HAVE_IOCTL:INTERNAL=1 //Have includes sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;io.h H5_HAVE_IO_H:INTERNAL= //Have library dl;m H5_HAVE_LIBDL:INTERNAL=1 //Have library m; H5_HAVE_LIBM:INTERNAL=1 //Have library socket;m;dl H5_HAVE_LIBSOCKET:INTERNAL= //Have library ucb;m;dl H5_HAVE_LIBUCB:INTERNAL= //Have library ws2_32;m;dl H5_HAVE_LIBWS2_32:INTERNAL= //Have library wsock32;m;dl H5_HAVE_LIBWSOCK32:INTERNAL= //Have function longjmp H5_HAVE_LONGJMP:INTERNAL=1 //Have function lseek64 H5_HAVE_LSEEK64:INTERNAL=1 //Have function lstat H5_HAVE_LSTAT:INTERNAL=1 //Have includes sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;mach/mach_time.h H5_HAVE_MACH_MACH_TIME_H:INTERNAL= //Have symbol sigsetjmp H5_HAVE_MACRO_SIGSETJMP:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;string.h;strings.h;time.h;stdlib.h;memory.h H5_HAVE_MEMORY_H:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;string.h;strings.h;time.h;stdlib.h;memory.h;dlfcn.h;inttypes.h;netinet/in.h H5_HAVE_NETINET_IN_H:INTERNAL=1 //Other test H5_HAVE_OFF64_T:INTERNAL=1 //Have includes sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pdb.h H5_HAVE_PDB_H:INTERNAL= //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h H5_HAVE_PTHREAD_H:INTERNAL=1 //Have function random H5_HAVE_RANDOM:INTERNAL=1 //Have function rand_r H5_HAVE_RAND_R:INTERNAL=1 //Have function setjmp H5_HAVE_SETJMP:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h H5_HAVE_SETJMP_H:INTERNAL=1 //Have function setsysinfo H5_HAVE_SETSYSINFO:INTERNAL= //Have function sigaction H5_HAVE_SIGACTION:INTERNAL=1 //Have function siglongjmp H5_HAVE_SIGLONGJMP:INTERNAL=1 //Have function signal H5_HAVE_SIGNAL:INTERNAL=1 //Have function sigprocmask H5_HAVE_SIGPROCMASK:INTERNAL=1 //Have function sigsetjmp H5_HAVE_SIGSETJMP:INTERNAL= //Have function snprintf H5_HAVE_SNPRINTF:INTERNAL=1 //Other test H5_HAVE_SOCKLEN_T:INTERNAL=1 //Have function srandom H5_HAVE_SRANDOM:INTERNAL=1 //Have includes sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;srbclient.h H5_HAVE_SRBCLIENT_H:INTERNAL= //Have function stat64 H5_HAVE_STAT64:INTERNAL=1 //Other test H5_HAVE_STAT64_STRUCT:INTERNAL=1 //Other test H5_HAVE_STAT_ST_BLOCKS:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h H5_HAVE_STDDEF_H:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h H5_HAVE_STDINT_H:INTERNAL=1 //Have include stdint.h H5_HAVE_STDINT_H_CXX:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;string.h;strings.h;time.h;stdlib.h H5_HAVE_STDLIB_H:INTERNAL=1 //Have function strdup H5_HAVE_STRDUP:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;string.h;strings.h H5_HAVE_STRINGS_H:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;string.h H5_HAVE_STRING_H:INTERNAL=1 //Other test H5_HAVE_STRUCT_TEXT_INFO:INTERNAL= //Other test H5_HAVE_STRUCT_TIMEZONE:INTERNAL=1 //Other test H5_HAVE_STRUCT_TM_TM_ZONE:INTERNAL=1 //Other test H5_HAVE_STRUCT_VIDEOCONFIG:INTERNAL= //Have function symlink H5_HAVE_SYMLINK:INTERNAL=1 //Have function system H5_HAVE_SYSTEM:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h H5_HAVE_SYS_IOCTL_H:INTERNAL=1 H5_HAVE_SYS_PROC_H:INTERNAL= //Have include ;sys/resource.h H5_HAVE_SYS_RESOURCE_H:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h H5_HAVE_SYS_SOCKET_H:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h H5_HAVE_SYS_STAT_H:INTERNAL=1 H5_HAVE_SYS_SYSINFO_H:INTERNAL= //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h H5_HAVE_SYS_TIMEB_H:INTERNAL=1 //H5_HAVE_SYS_TIME_GETTIMEOFDAY H5_HAVE_SYS_TIME_GETTIMEOFDAY:INTERNAL=1 //Have include sys/resource.h;sys/time.h H5_HAVE_SYS_TIME_H:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h H5_HAVE_SYS_TYPES_H:INTERNAL=1 //Other test H5_HAVE_TIMEZONE:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;string.h;strings.h;time.h H5_HAVE_TIME_H:INTERNAL=1 //Have symbol TIOCGETD H5_HAVE_TIOCGETD:INTERNAL=1 //Have symbol TIOCGWINSZ H5_HAVE_TIOCGWINSZ:INTERNAL=1 //Other test H5_HAVE_TM_GMTOFF:INTERNAL=1 //Other test H5_HAVE_TM_ZONE:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h H5_HAVE_UNISTD_H:INTERNAL=1 //Have function vasprintf H5_HAVE_VASPRINTF:INTERNAL=1 //Have function vsnprintf H5_HAVE_VSNPRINTF:INTERNAL=1 //Have function waitpid H5_HAVE_WAITPID:INTERNAL=1 //Have includes sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;winsock2.h H5_HAVE_WINSOCK2_H:INTERNAL= //Have function _getvideoconfig H5_HAVE__GETVIDEOCONFIG:INTERNAL= //Have function _scrsize H5_HAVE__SCRSIZE:INTERNAL= //Other test H5_HAVE___TM_GMTOFF:INTERNAL= //Other test H5_INLINE_TEST___inline:INTERNAL=1 //Other test H5_INLINE_TEST___inline__:INTERNAL=1 //Other test H5_INLINE_TEST_inline:INTERNAL=1 //checking IF accurately converting from integers to long double H5_INTEGER_TO_LDOUBLE_ACCURATE:INTERNAL=1 //checking IF converting from long double to integers is accurate H5_LDOUBLE_TO_INTEGER_ACCURATE:INTERNAL=1 //Checking IF converting from long double to integers works H5_LDOUBLE_TO_INTEGER_WORKS:INTERNAL=1 //Result of TRY_COMPILE H5_LDOUBLE_TO_INTEGER_WORKS_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_LDOUBLE_TO_INTEGER_WORKS_RUN:INTERNAL=0 //Checking IF correctly converting long double to (unsigned) long // long values H5_LDOUBLE_TO_LLONG_ACCURATE:INTERNAL=1 //Result of TRY_COMPILE H5_LDOUBLE_TO_LLONG_ACCURATE_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_LDOUBLE_TO_LLONG_ACCURATE_RUN:INTERNAL=0 //Define if your system converts long double to (unsigned) long // values with special algorithm H5_LDOUBLE_TO_LONG_SPECIAL:INTERNAL=0 //Checking IF correctly converting long double to unsigned int // values H5_LDOUBLE_TO_UINT_ACCURATE:INTERNAL=1 //Result of TRY_COMPILE H5_LDOUBLE_TO_UINT_ACCURATE_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_LDOUBLE_TO_UINT_ACCURATE_RUN:INTERNAL=0 //Use Legacy Names for Libraries and Programs H5_LEGACY_NAMING:INTERNAL=ON //Checking IF compiling long long to floating-point typecasts work H5_LLONG_TO_FP_CAST_WORKS:INTERNAL=1 //Checking IF correctly converting (unsigned) long long to long // double values H5_LLONG_TO_LDOUBLE_CORRECT:INTERNAL=1 //Result of TRY_COMPILE H5_LLONG_TO_LDOUBLE_CORRECT_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_LLONG_TO_LDOUBLE_CORRECT_RUN:INTERNAL=0 //Other test H5_LONE_COLON:INTERNAL=1 //Define if your system can convert (unsigned) long to long double // values with special algorithm H5_LONG_TO_LDOUBLE_SPECIAL:INTERNAL=0 //Checking IF alignment restrictions are strictly enforced H5_NO_ALIGNMENT_RESTRICTIONS:INTERNAL=1 //Result of TRY_COMPILE H5_NO_ALIGNMENT_RESTRICTIONS_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_NO_ALIGNMENT_RESTRICTIONS_RUN:INTERNAL=0 //CXX test H5_NO_NAMESPACE:INTERNAL= //CXX test H5_NO_STD:INTERNAL= //Width for printf for type `long long' or `__int64', us. `ll H5_PRINTF_LL_WIDTH:INTERNAL="ll" //CHECK_TYPE_SIZE: sizeof(char) H5_SIZEOF_CHAR:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(double) H5_SIZEOF_DOUBLE:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(float) H5_SIZEOF_FLOAT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int) H5_SIZEOF_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int16_t) H5_SIZEOF_INT16_T:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(int32_t) H5_SIZEOF_INT32_T:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int64_t) H5_SIZEOF_INT64_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(int8_t) H5_SIZEOF_INT8_T:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(int_fast16_t) H5_SIZEOF_INT_FAST16_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(int_fast32_t) H5_SIZEOF_INT_FAST32_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(int_fast64_t) H5_SIZEOF_INT_FAST64_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(int_fast8_t) H5_SIZEOF_INT_FAST8_T:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(int_least16_t) H5_SIZEOF_INT_LEAST16_T:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(int_least32_t) H5_SIZEOF_INT_LEAST32_T:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int_least64_t) H5_SIZEOF_INT_LEAST64_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(int_least8_t) H5_SIZEOF_INT_LEAST8_T:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(long) H5_SIZEOF_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(long double) H5_SIZEOF_LONG_DOUBLE:INTERNAL=16 //CHECK_TYPE_SIZE: sizeof(long long) H5_SIZEOF_LONG_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(off64_t) H5_SIZEOF_OFF64_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(off_t) H5_SIZEOF_OFF_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(ptrdiff_t) H5_SIZEOF_PTRDIFF_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(short) H5_SIZEOF_SHORT:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(size_t) H5_SIZEOF_SIZE_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(ssize_t) H5_SIZEOF_SSIZE_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(uint16_t) H5_SIZEOF_UINT16_T:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(uint32_t) H5_SIZEOF_UINT32_T:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(uint64_t) H5_SIZEOF_UINT64_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(uint8_t) H5_SIZEOF_UINT8_T:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(uint_fast16_t) H5_SIZEOF_UINT_FAST16_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(uint_fast32_t) H5_SIZEOF_UINT_FAST32_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(uint_fast64_t) H5_SIZEOF_UINT_FAST64_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(uint_fast8_t) H5_SIZEOF_UINT_FAST8_T:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(uint_least16_t) H5_SIZEOF_UINT_LEAST16_T:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(uint_least32_t) H5_SIZEOF_UINT_LEAST32_T:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(uint_least64_t) H5_SIZEOF_UINT_LEAST64_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(uint_least8_t) H5_SIZEOF_UINT_LEAST8_T:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(unsigned) H5_SIZEOF_UNSIGNED:INTERNAL=4 //SizeOf for __int64 H5_SIZEOF___INT64:INTERNAL=0 //Other test H5_STDC_HEADERS:INTERNAL=1 //Other test H5_SYSTEM_SCOPE_THREADS:INTERNAL=1 //Other test H5_TIME_WITH_SYS_TIME:INTERNAL=1 //Checking IF compiling unsigned long long to floating-point typecasts // work H5_ULLONG_TO_FP_CAST_WORKS:INTERNAL=1 //Checking IF converting unsigned long long to long double with // precision H5_ULLONG_TO_LDOUBLE_PRECISION:INTERNAL=1 //Result of TRY_COMPILE H5_ULLONG_TO_LDOUBLE_PRECISION_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_ULLONG_TO_LDOUBLE_PRECISION_RUN:INTERNAL=0 //Checking IF accurately converting unsigned long to float values H5_ULONG_TO_FLOAT_ACCURATE:INTERNAL=1 //Result of TRY_COMPILE H5_ULONG_TO_FLOAT_ACCURATE_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_ULONG_TO_FLOAT_ACCURATE_RUN:INTERNAL=0 //Other test H5_VSNPRINTF_WORKS:INTERNAL=1 //Result of TEST_BIG_ENDIAN H5_WORDS_BIGENDIAN:INTERNAL=0 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_ATTRIBUTE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_C99_DESIGNATED_INITIALIZER:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_C99_FUNC:INTERNAL=TRUE //Have variable CLOCK_MONOTONIC HAVE_CLOCK_MONOTONIC:INTERNAL= //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 //Result of TRY_COMPILE HAVE_DIRECT: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 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 //Result of TRY_COMPILE HAVE_FUNCTION:INTERNAL=TRUE //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 //Result of TRY_COMPILE HAVE_H5_SIZEOF_CHAR:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_DOUBLE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_FLOAT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT32_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT64_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT8_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT_FAST16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT_FAST32_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT_FAST64_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT_FAST8_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT_LEAST16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT_LEAST32_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT_LEAST64_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT_LEAST8_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_LONG_DOUBLE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_LONG_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_OFF64_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_OFF_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_PTRDIFF_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_SIZE_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_SSIZE_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT32_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT64_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT8_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT_FAST16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT_FAST32_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT_FAST64_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT_FAST8_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT_LEAST16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT_LEAST32_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT_LEAST64_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT_LEAST8_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UNSIGNED:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF___INT64:INTERNAL=FALSE //Result of TRY_COMPILE HAVE_H5_WORDS_BIGENDIAN:INTERNAL=TRUE HAVE_HASH_MAP:INTERNAL=1 HAVE_HASH_SET:INTERNAL=1 //Result of TRY_COMPILE HAVE_ICET_SIZEOF_CHAR:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_DOUBLE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_FLOAT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_LONG_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_VOID_P:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF___INT64:INTERNAL=FALSE //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 //Result of TRY_COMPILE HAVE_OFF64_T:INTERNAL=TRUE //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:INTERNAL=TRUE //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 //Result of TRY_COMPILE HAVE_STAT64_STRUCT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_STAT_ST_BLOCKS: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 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 //Result of TRY_COMPILE HAVE_STRUCT_TEXT_INFO:INTERNAL=FALSE //Result of TRY_COMPILE HAVE_STRUCT_TIMEZONE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_STRUCT_TM_TM_ZONE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_STRUCT_VIDEOCONFIG:INTERNAL=FALSE //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 //Result of TRY_COMPILE HAVE_SYS_TIME_GETTIMEOFDAY:INTERNAL=TRUE //Have include sys/time.h HAVE_SYS_TIME_H:INTERNAL=1 //Have include sys/types.h HAVE_SYS_TYPES_H:INTERNAL=1 //Result of TRY_COMPILE HAVE_TIMEZONE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_TIME_GETTIMEOFDAY: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;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h HAVE_TIME_H:INTERNAL=1 //Result of TRY_COMPILE HAVE_TM_GMTOFF:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_TM_ZONE:INTERNAL=TRUE //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___TM_GMTOFF:INTERNAL=FALSE //Result of TRY_COMPILE HAVE___VA_COPY_COMPILED:INTERNAL=TRUE //Allow External Library Building (NO SVN TGZ) HDF5_ALLOW_EXTERNAL_SUPPORT:INTERNAL=OFF //Build HDF5 C++ Library HDF5_BUILD_CPP_LIB:INTERNAL=OFF //Build HIGH Level HDF5 Library HDF5_BUILD_HL_LIB:INTERNAL=ON //ADVANCED property for variable: HDF5_BUILD_STATIC_EXECS HDF5_BUILD_STATIC_EXECS-ADVANCED:INTERNAL=1 //Disable compiler warnings HDF5_DISABLE_COMPILER_WARNINGS:INTERNAL=ON //ADVANCED property for variable: HDF5_ENABLE_ALL_WARNINGS HDF5_ENABLE_ALL_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_ENABLE_CODESTACK HDF5_ENABLE_CODESTACK-ADVANCED:INTERNAL=1 //Enable the function stack tracing (for developer debugging). HDF5_ENABLE_CODESTACK:INTERNAL=OFF //Enable code coverage for Libraries and Programs HDF5_ENABLE_COVERAGE:INTERNAL=OFF //ADVANCED property for variable: HDF5_ENABLE_DEBUG_APIS HDF5_ENABLE_DEBUG_APIS-ADVANCED:INTERNAL=1 //Enable deprecated public API symbols HDF5_ENABLE_DEPRECATED_SYMBOLS:INTERNAL=ON //ADVANCED property for variable: HDF5_ENABLE_DIRECT_VFD HDF5_ENABLE_DIRECT_VFD-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_ENABLE_EMBEDDED_LIBINFO HDF5_ENABLE_EMBEDDED_LIBINFO-ADVANCED:INTERNAL=1 //Enable GPFS hints for the MPI/POSIX file driver HDF5_ENABLE_GPFS:INTERNAL=OFF //ADVANCED property for variable: HDF5_ENABLE_GROUPFIVE_WARNINGS HDF5_ENABLE_GROUPFIVE_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_ENABLE_GROUPFOUR_WARNINGS HDF5_ENABLE_GROUPFOUR_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_ENABLE_GROUPONE_WARNINGS HDF5_ENABLE_GROUPONE_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_ENABLE_GROUPTHREE_WARNINGS HDF5_ENABLE_GROUPTHREE_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_ENABLE_GROUPTWO_WARNINGS HDF5_ENABLE_GROUPTWO_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_ENABLE_GROUPZERO_WARNINGS HDF5_ENABLE_GROUPZERO_WARNINGS-ADVANCED:INTERNAL=1 //Enable datasets larger than memory HDF5_ENABLE_HSIZET:INTERNAL=ON //ADVANCED property for variable: HDF5_ENABLE_INSTRUMENT HDF5_ENABLE_INSTRUMENT-ADVANCED:INTERNAL=1 //Enable support for large (64-bit) files on Linux. HDF5_ENABLE_LARGE_FILE:INTERNAL=ON //Enable parallel build (requires MPI) HDF5_ENABLE_PARALLEL:INTERNAL=OFF //Use SZip Filter HDF5_ENABLE_SZIP_SUPPORT:INTERNAL=OFF //Enable Threadsafety HDF5_ENABLE_THREADSAFE:INTERNAL=OFF //Enable API tracing capability HDF5_ENABLE_TRACE:INTERNAL=OFF //Indicate that a memory checker is used HDF5_ENABLE_USING_MEMCHECKER:INTERNAL=OFF //Enable Zlib Filters HDF5_ENABLE_Z_LIB_SUPPORT:INTERNAL=ON //ADVANCED property for variable: HDF5_Enable_Clear_File_Buffers HDF5_Enable_Clear_File_Buffers-ADVANCED:INTERNAL=1 //Securely clear file buffers before writing to file HDF5_Enable_Clear_File_Buffers:INTERNAL=ON //Instrument The library HDF5_Enable_Instrument:INTERNAL=OFF //Used to pass variables between directories HDF5_LIBRARIES_TO_EXPORT:INTERNAL=vtkhdf5;vtkhdf5_hl //ADVANCED property for variable: HDF5_METADATA_TRACE_FILE HDF5_METADATA_TRACE_FILE-ADVANCED:INTERNAL=1 //Enable metadata trace file collection HDF5_METADATA_TRACE_FILE:INTERNAL=OFF //ADVANCED property for variable: HDF5_NO_PACKAGES HDF5_NO_PACKAGES-ADVANCED:INTERNAL=1 //CPACK - include external libraries HDF5_PACKAGE_EXTLIBS:INTERNAL=OFF //ADVANCED property for variable: HDF5_PACK_EXAMPLES HDF5_PACK_EXAMPLES-ADVANCED:INTERNAL=1 //Result of TRY_COMPILE HDF5_PRINTF_LL_TEST_COMPILE:INTERNAL=TRUE //Result of TRY_RUN HDF5_PRINTF_LL_TEST_RUN:INTERNAL=0 //ADVANCED property for variable: HDF5_STRICT_FORMAT_CHECKS HDF5_STRICT_FORMAT_CHECKS-ADVANCED:INTERNAL=1 //Whether to perform strict file format checks HDF5_STRICT_FORMAT_CHECKS:INTERNAL=OFF //ADVANCED property for variable: HDF5_TEST_VFD HDF5_TEST_VFD-ADVANCED:INTERNAL=1 //Use the HDF5 1.6.x API by default HDF5_USE_16_API_DEFAULT:INTERNAL=OFF //Use the FLETCHER32 Filter HDF5_USE_FILTER_FLETCHER32:INTERNAL=ON //Use the NBIT Filter HDF5_USE_FILTER_NBIT:INTERNAL=ON //Use the SCALEOFFSET Filter HDF5_USE_FILTER_SCALEOFFSET:INTERNAL=ON //Use the SHUFFLE Filter HDF5_USE_FILTER_SHUFFLE:INTERNAL=ON //ADVANCED property for variable: HDF5_USE_FOLDERS HDF5_USE_FOLDERS-ADVANCED:INTERNAL=1 //Use the PACKED BITS feature in h5dump HDF5_USE_H5DUMP_PACKED_BITS:INTERNAL=ON //ADVANCED property for variable: HDF5_WANT_DATA_ACCURACY HDF5_WANT_DATA_ACCURACY-ADVANCED:INTERNAL=1 //IF data accuracy is guaranteed during data conversions HDF5_WANT_DATA_ACCURACY:INTERNAL=ON //ADVANCED property for variable: HDF5_WANT_DCONV_EXCEPTION HDF5_WANT_DCONV_EXCEPTION-ADVANCED:INTERNAL=1 //exception handling functions is checked during data conversions HDF5_WANT_DCONV_EXCEPTION:INTERNAL=ON //ADVANCED property for variable: HGCOMMAND HGCOMMAND-ADVANCED:INTERNAL=1 ICET_INSTALL_TARGETS:INTERNAL=IceTCore;IceTMPI;IceTGL //ADVANCED property for variable: ICET_MAGIC_K ICET_MAGIC_K-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ICET_MAX_IMAGE_SPLIT ICET_MAX_IMAGE_SPLIT-ADVANCED:INTERNAL=1 //This is set from VTK_MPIRUN_EXE. ICET_MPIRUN_EXE:INTERNAL=/Programs/openmpi-1.8.4/build/bin/mpiexec //ADVANCED property for variable: ICET_MPI_MAX_NUMPROCS ICET_MPI_MAX_NUMPROCS-ADVANCED:INTERNAL=1 //This is set from VTK_MPI_MAX_NUMPROCS. ICET_MPI_MAX_NUMPROCS:INTERNAL=8 //This is set from a combination of VTK_MPI_PRENUMPROC_FLAGS and // VTK_MPI_NUMPROC_FLAG ICET_MPI_NUMPROC_FLAG:INTERNAL=;-np //This is set from VTK_MPI_POSTFLAGS. ICET_MPI_POSTFLAGS:INTERNAL= //This is set from VTK_MPI_PREFLAGS. ICET_MPI_PREFLAGS:INTERNAL= //CHECK_TYPE_SIZE: sizeof(char) ICET_SIZEOF_CHAR:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(double) ICET_SIZEOF_DOUBLE:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(float) ICET_SIZEOF_FLOAT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int) ICET_SIZEOF_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(long) ICET_SIZEOF_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(long long) ICET_SIZEOF_LONG_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(short) ICET_SIZEOF_SHORT:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(void*) ICET_SIZEOF_VOID_P:INTERNAL=8 //CHECK_TYPE_SIZE: __int64 unknown ICET_SIZEOF___INT64:INTERNAL= //ADVANCED property for variable: ICET_USE_MPE ICET_USE_MPE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ICET_USE_MPI ICET_USE_MPI-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ICET_USE_OPENGL ICET_USE_OPENGL-ADVANCED:INTERNAL=1 //Result of TRY_COMPILE INLINE_TEST___inline:INTERNAL=TRUE //Result of TRY_COMPILE INLINE_TEST___inline__:INTERNAL=TRUE //Result of TRY_COMPILE INLINE_TEST_inline:INTERNAL=TRUE //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 //ADVANCED property for variable: LIBRARY_OUTPUT_PATH LIBRARY_OUTPUT_PATH-ADVANCED:INTERNAL=1 LIBRARY_OUTPUT_PATH:INTERNAL=/Programs/ParaView-4.3.1/build-catalyst/ThirdParty/protobuf/vtkprotobuf/bin //Result of TRY_COMPILE LONE_COLON:INTERNAL=TRUE //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: MPIEXEC MPIEXEC-ADVANCED:INTERNAL=1 //MODIFIED property for variable: MPIEXEC MPIEXEC-MODIFIED:INTERNAL=ON //ADVANCED property for variable: MPIEXEC_MAX_NUMPROCS MPIEXEC_MAX_NUMPROCS-ADVANCED:INTERNAL=1 //MODIFIED property for variable: MPIEXEC_MAX_NUMPROCS MPIEXEC_MAX_NUMPROCS-MODIFIED:INTERNAL=ON //ADVANCED property for variable: MPIEXEC_NUMPROC_FLAG MPIEXEC_NUMPROC_FLAG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPIEXEC_POSTFLAGS MPIEXEC_POSTFLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPIEXEC_PREFLAGS MPIEXEC_PREFLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_CXX_COMPILER MPI_CXX_COMPILER-ADVANCED:INTERNAL=1 //MODIFIED property for variable: MPI_CXX_COMPILER MPI_CXX_COMPILER-MODIFIED:INTERNAL=ON //ADVANCED property for variable: MPI_CXX_COMPILE_FLAGS MPI_CXX_COMPILE_FLAGS-ADVANCED:INTERNAL=1 //MODIFIED property for variable: MPI_CXX_COMPILE_FLAGS MPI_CXX_COMPILE_FLAGS-MODIFIED:INTERNAL=ON //ADVANCED property for variable: MPI_CXX_INCLUDE_PATH MPI_CXX_INCLUDE_PATH-ADVANCED:INTERNAL=1 //MODIFIED property for variable: MPI_CXX_INCLUDE_PATH MPI_CXX_INCLUDE_PATH-MODIFIED:INTERNAL=ON //ADVANCED property for variable: MPI_CXX_LIBRARIES MPI_CXX_LIBRARIES-ADVANCED:INTERNAL=1 //MODIFIED property for variable: MPI_CXX_LIBRARIES MPI_CXX_LIBRARIES-MODIFIED:INTERNAL=ON //ADVANCED property for variable: MPI_CXX_LINK_FLAGS MPI_CXX_LINK_FLAGS-ADVANCED:INTERNAL=1 //MODIFIED property for variable: MPI_CXX_LINK_FLAGS MPI_CXX_LINK_FLAGS-MODIFIED:INTERNAL=ON //ADVANCED property for variable: MPI_C_COMPILER MPI_C_COMPILER-ADVANCED:INTERNAL=1 //MODIFIED property for variable: MPI_C_COMPILER MPI_C_COMPILER-MODIFIED:INTERNAL=ON //ADVANCED property for variable: MPI_C_COMPILE_FLAGS MPI_C_COMPILE_FLAGS-ADVANCED:INTERNAL=1 //MODIFIED property for variable: MPI_C_COMPILE_FLAGS MPI_C_COMPILE_FLAGS-MODIFIED:INTERNAL=ON //ADVANCED property for variable: MPI_C_INCLUDE_PATH MPI_C_INCLUDE_PATH-ADVANCED:INTERNAL=0 //MODIFIED property for variable: MPI_C_INCLUDE_PATH MPI_C_INCLUDE_PATH-MODIFIED:INTERNAL=ON //ADVANCED property for variable: MPI_C_LIBRARIES MPI_C_LIBRARIES-ADVANCED:INTERNAL=0 //MODIFIED property for variable: MPI_C_LIBRARIES MPI_C_LIBRARIES-MODIFIED:INTERNAL=ON //ADVANCED property for variable: MPI_C_LINK_FLAGS MPI_C_LINK_FLAGS-ADVANCED:INTERNAL=1 //MODIFIED property for variable: MPI_C_LINK_FLAGS MPI_C_LINK_FLAGS-MODIFIED:INTERNAL=ON //ADVANCED property for variable: MPI_EXTRA_LIBRARY MPI_EXTRA_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_Fortran_COMPILER MPI_Fortran_COMPILER-ADVANCED:INTERNAL=1 //MODIFIED property for variable: MPI_Fortran_COMPILER MPI_Fortran_COMPILER-MODIFIED:INTERNAL=ON //ADVANCED property for variable: MPI_Fortran_COMPILE_FLAGS MPI_Fortran_COMPILE_FLAGS-ADVANCED:INTERNAL=1 //MODIFIED property for variable: MPI_Fortran_COMPILE_FLAGS MPI_Fortran_COMPILE_FLAGS-MODIFIED:INTERNAL=ON //ADVANCED property for variable: MPI_Fortran_INCLUDE_PATH MPI_Fortran_INCLUDE_PATH-ADVANCED:INTERNAL=1 //MODIFIED property for variable: MPI_Fortran_INCLUDE_PATH MPI_Fortran_INCLUDE_PATH-MODIFIED:INTERNAL=ON //ADVANCED property for variable: MPI_Fortran_LIBRARIES MPI_Fortran_LIBRARIES-ADVANCED:INTERNAL=1 //MODIFIED property for variable: MPI_Fortran_LIBRARIES MPI_Fortran_LIBRARIES-MODIFIED:INTERNAL=ON //ADVANCED property for variable: MPI_Fortran_LINK_FLAGS MPI_Fortran_LINK_FLAGS-ADVANCED:INTERNAL=1 //MODIFIED property for variable: MPI_Fortran_LINK_FLAGS MPI_Fortran_LINK_FLAGS-MODIFIED:INTERNAL=ON //Scratch variable for MPI header detection MPI_HEADER_PATH:INTERNAL=MPI_HEADER_PATH-NOTFOUND //Scratch variable for MPI lib detection MPI_LIB:INTERNAL=MPI_LIB-NOTFOUND //ADVANCED property for variable: MPI_LIBRARY MPI_LIBRARY-ADVANCED:INTERNAL=1 //MODIFIED property for variable: MPI_LIBRARY MPI_LIBRARY-MODIFIED:INTERNAL=ON //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 //Request building vtkFiltersImaging Module_vtkFiltersImaging:INTERNAL=OFF //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 //Request building vtkFiltersParallelFlowPaths Module_vtkFiltersParallelFlowPaths:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersParallelGeometry Module_vtkFiltersParallelGeometry-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersParallelImaging Module_vtkFiltersParallelImaging-ADVANCED:INTERNAL=1 //Request building vtkFiltersParallelImaging Module_vtkFiltersParallelImaging:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersParallelMPI Module_vtkFiltersParallelMPI-ADVANCED:INTERNAL=1 //Request building vtkFiltersParallelMPI Module_vtkFiltersParallelMPI:INTERNAL=OFF //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 //Request building vtkIOMPIImage Module_vtkIOMPIImage:INTERNAL=OFF //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 //Request building vtkIOParallelNetCDF Module_vtkIOParallelNetCDF:INTERNAL=OFF //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 //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 //Request building vtkParallelMPI Module_vtkParallelMPI:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParallelMPI4Py Module_vtkParallelMPI4Py-ADVANCED:INTERNAL=1 //Request building vtkParallelMPI4Py Module_vtkParallelMPI4Py:INTERNAL=OFF //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 //Request building vtkRenderingParallelLIC Module_vtkRenderingParallelLIC:INTERNAL=OFF //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 //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 //Request building vtkicet Module_vtkicet:INTERNAL=OFF //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 //Request building vtkmpi4py Module_vtkmpi4py:INTERNAL=OFF //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: NETCDF4_CHUNK_CACHE_NELEMS NETCDF4_CHUNK_CACHE_NELEMS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF4_CHUNK_CACHE_PREEMPTION NETCDF4_CHUNK_CACHE_PREEMPTION-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF4_CHUNK_CACHE_SIZE NETCDF4_CHUNK_CACHE_SIZE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF4_DEFAULT_CHUNKS_IN_CACHE NETCDF4_DEFAULT_CHUNKS_IN_CACHE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF4_DEFAULT_CHUNK_SIZE NETCDF4_DEFAULT_CHUNK_SIZE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF4_MAX_DEFAULT_CACHE_SIZE NETCDF4_MAX_DEFAULT_CACHE_SIZE-ADVANCED:INTERNAL=1 //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 //Have library c NOT_NEED_LIBNSL:INTERNAL=1 //CXX test NO_STATIC_CAST:INTERNAL= //ADVANCED property for variable: NVCtrlLib_INCLUDE_DIR NVCtrlLib_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NVCtrlLib_LIBRARY NVCtrlLib_LIBRARY-ADVANCED:INTERNAL=1 //CXX test OLD_HEADER_FILENAME:INTERNAL= //ADVANCED property for variable: OPENGL_INCLUDE_DIR OPENGL_INCLUDE_DIR-ADVANCED:INTERNAL=1 //MODIFIED property for variable: OPENGL_INCLUDE_DIR OPENGL_INCLUDE_DIR-MODIFIED:INTERNAL=ON //ADVANCED property for variable: OPENGL_gl_LIBRARY OPENGL_gl_LIBRARY-ADVANCED:INTERNAL=1 //MODIFIED property for variable: OPENGL_gl_LIBRARY OPENGL_gl_LIBRARY-MODIFIED:INTERNAL=ON //ADVANCED property for variable: OPENGL_glu_LIBRARY OPENGL_glu_LIBRARY-ADVANCED:INTERNAL=1 //MODIFIED property for variable: OPENGL_glu_LIBRARY OPENGL_glu_LIBRARY-MODIFIED:INTERNAL=ON //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 //MODIFIED property for variable: OSMESA_INCLUDE_DIR OSMESA_INCLUDE_DIR-MODIFIED:INTERNAL=ON //ADVANCED property for variable: OSMESA_LIBRARY OSMESA_LIBRARY-ADVANCED:INTERNAL=1 //MODIFIED property for variable: OSMESA_LIBRARY OSMESA_LIBRARY-MODIFIED:INTERNAL=ON //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_Nektar PARAVIEW_BUILD_PLUGIN_Nektar-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;vtkPythonInterpreter;vtkIOCore;vtkIOGeometry;vtkIOXMLParser;vtkIOXML;vtkDomainsChemistry;vtkIOLegacy;vtkParallelCore;vtkFiltersAMR;vtkFiltersFlowPaths;vtkFiltersGeneric;vtkImagingSources;vtkFiltersHybrid;vtkFiltersHyperTree;vtkImagingGeneral;vtkFiltersImaging;vtkFiltersModeling;vtkFiltersParallel;vtkParallelMPI;vtkFiltersParallelFlowPaths;vtkFiltersParallelImaging;vtkFiltersParallelMPI;vtkFiltersParallelStatistics;vtkFiltersProgrammable;vtkFiltersPython;vtkFiltersTexture;vtkFiltersVerdict;vtkIOAMR;vtkIOEnSight;vtkIOExodus;vtkIOImage;vtkImagingColor;vtkRenderingAnnotation;vtkImagingHybrid;vtkRenderingOpenGL;vtkRenderingContextOpenGL;vtkRenderingGL2PS;vtkRenderingLabel;vtkIOExport;vtkIOImport;vtkIOInfovis;vtkIOLSDyna;vtkIOMPIImage;vtkIOMovie;vtkIONetCDF;vtkIOPLY;vtkIOParallel;vtkIOParallelExodus;vtkIOParallelLSDyna;vtkIOParallelNetCDF;vtkIOParallelXML;vtkIOVPIC;vtkIOXdmf2;vtkImagingMorphological;vtkInteractionStyle;vtkRenderingVolume;vtkInteractionWidgets;vtkInteractionImage;vtkPVCommon;vtkPVVTKExtensionsCore;vtkPVClientServerCoreCore;vtkPVServerImplementationCore;vtkPVServerManagerCore;vtkRenderingFreeTypeOpenGL;vtkRenderingLIC;vtkRenderingMatplotlib;vtkRenderingParallel;vtkRenderingParallelLIC;vtkPVVTKExtensionsRendering;vtkPVVTKExtensionsDefault;vtkRenderingVolumeOpenGL;vtkRenderingVolumeAMR;vtkViewsCore;vtkViewsContext2D;vtkWebGLExporter;vtkPVClientServerCoreRendering;vtkPVClientServerCoreDefault;vtkPVServerImplementationRendering;vtkPVServerManagerRendering;vtkTestingRendering;vtkPVServerManagerDefault;vtkPVAnimation;vtkParallelMPI4Py;vtkRenderingLOD;vtkPVServerManagerApplication;vtkPVCatalyst;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_COSMOTOOLS PARAVIEW_ENABLE_COSMOTOOLS-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_INITIALIZE_MPI_ON_CLIENT PARAVIEW_INITIALIZE_MPI_ON_CLIENT-ADVANCED:INTERNAL=1 //MODIFIED property for variable: PARAVIEW_INSTALL_DEVELOPMENT_FILES PARAVIEW_INSTALL_DEVELOPMENT_FILES-MODIFIED:INTERNAL=ON //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=/Programs/ParaView-4.3.1/source-std/ParaViewCore/ServerManager/SMApplication/Resources/3d_widgets.xml;/Programs/ParaView-4.3.1/source-std/ParaViewCore/ServerManager/SMApplication/Resources/filters.xml;/Programs/ParaView-4.3.1/source-std/ParaViewCore/ServerManager/SMApplication/Resources/internal_writers.xml;/Programs/ParaView-4.3.1/source-std/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml;/Programs/ParaView-4.3.1/source-std/ParaViewCore/ServerManager/SMApplication/Resources/rendering.xml;/Programs/ParaView-4.3.1/source-std/ParaViewCore/ServerManager/SMApplication/Resources/sources.xml;/Programs/ParaView-4.3.1/source-std/ParaViewCore/ServerManager/SMApplication/Resources/utilities.xml;/Programs/ParaView-4.3.1/source-std/ParaViewCore/ServerManager/SMApplication/Resources/views_and_representations.xml;/Programs/ParaView-4.3.1/source-std/ParaViewCore/ServerManager/SMApplication/Resources/writers.xml;/Programs/ParaView-4.3.1/source-std/ParaViewCore/ServerManager/Default/settings.xml;/Programs/ParaView-4.3.1/source-std/ParaViewCore/Animation/animation.xml;/Programs/ParaView-4.3.1/source-std/ParaViewCore/ServerManager/SMApplication/Resources/pythonfilter.xml //ADVANCED property for variable: PARAVIEW_USE_ICE_T PARAVIEW_USE_ICE_T-ADVANCED:INTERNAL=1 //MODIFIED property for variable: PARAVIEW_USE_MPI PARAVIEW_USE_MPI-MODIFIED:INTERNAL=ON //ADVANCED property for variable: PARAVIEW_USE_MPI_SSEND PARAVIEW_USE_MPI_SSEND-ADVANCED:INTERNAL=1 //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_ENABLE_MODULE_mpi4py.MPE PYTHON_ENABLE_MODULE_mpi4py.MPE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_ENABLE_MODULE_mpi4py.MPI PYTHON_ENABLE_MODULE_mpi4py.MPI-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_ENABLE_MODULE_mpi4py.dl PYTHON_ENABLE_MODULE_mpi4py.dl-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_MODULE_mpi4py.MPE_BUILD_SHARED PYTHON_MODULE_mpi4py.MPE_BUILD_SHARED-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_MODULE_mpi4py.MPI_BUILD_SHARED PYTHON_MODULE_mpi4py.MPI_BUILD_SHARED-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_MODULE_mpi4py.dl_BUILD_SHARED PYTHON_MODULE_mpi4py.dl_BUILD_SHARED-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 //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_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_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 //Result of TRY_COMPILE STDC_HEADERS:INTERNAL=TRUE //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 //Result of TRY_COMPILE SYSTEM_SCOPE_THREADS:INTERNAL=TRUE //Performing TEST_DIRECT_VFD_WORKS TEST_DIRECT_VFD_WORKS:INTERNAL= //Result of TRY_COMPILE TEST_DIRECT_VFD_WORKS_COMPILE:INTERNAL=TRUE //Result of TRY_RUN TEST_DIRECT_VFD_WORKS_RUN:INTERNAL=0 //Performing TEST_LFS_WORKS TEST_LFS_WORKS:INTERNAL=1 //Result of TRY_COMPILE TEST_LFS_WORKS_COMPILE:INTERNAL=TRUE //Result of TRY_RUN TEST_LFS_WORKS_RUN:INTERNAL=0 //Result of TRY_COMPILE TIME_WITH_SYS_TIME:INTERNAL=TRUE //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= //Result of TRY_COMPILE VSNPRINTF_WORKS:INTERNAL=TRUE //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=0 //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 //Enable modules as needed for testing all the enabled modules VTK_BUILD_ALL_MODULES_FOR_TESTS:INTERNAL=OFF //Directory where python modules will be built VTK_BUILD_PYTHON_MODULE_DIR:INTERNAL=/Programs/ParaView-4.3.1/build-catalyst/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 //Result of TRY_COMPILE VTK_GLX_GET_PROC_ADDRESS_ARB_PROTOTYPE_EXISTS:INTERNAL=TRUE //OpenGL includes used to test glXGetProcAddressARB prototype. VTK_GLX_GET_PROC_ADDRESS_ARB_PROTOTYPE_EXISTS_INCLUDES:INTERNAL=/usr/include //Already set VTK_GLX_GET_PROC_ADDRESS_ARB_PROTOTYPE_EXISTS VTK_GLX_GET_PROC_ADDRESS_ARB_PROTOTYPE_EXISTS_TESTED: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 //ADVANCED property for variable: VTK_MPIRUN_EXE VTK_MPIRUN_EXE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_MAX_NUMPROCS VTK_MPI_MAX_NUMPROCS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_NUMPROC_FLAG VTK_MPI_NUMPROC_FLAG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_POSTFLAGS VTK_MPI_POSTFLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_PREFLAGS VTK_MPI_PREFLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_PRENUMPROC_FLAGS VTK_MPI_PRENUMPROC_FLAGS-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 //MODIFIED property for variable: VTK_OPENGL_HAS_OSMESA VTK_OPENGL_HAS_OSMESA-MODIFIED:INTERNAL=ON //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 //ADVANCED property for variable: VTK_RENDERINGPARALLELLIC_LINEINTEGRALCONVLOLUTION2D_TIMER VTK_RENDERINGPARALLELLIC_LINEINTEGRALCONVLOLUTION2D_TIMER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_RENDERINGPARALLELLIC_SURFACELICPAINTER_TIMER VTK_RENDERINGPARALLELLIC_SURFACELICPAINTER_TIMER-ADVANCED:INTERNAL=1 //STRINGS property for variable: VTK_RENDERING_BACKEND VTK_RENDERING_BACKEND-STRINGS:INTERNAL=OpenGL2;OpenGL;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 //Have function glXGetProcAddressARB VTK_USE_GLX_GET_PROC_ADDRESS_ARB: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_ICET VTK_USE_SYSTEM_ICET-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_MPI4PY VTK_USE_SYSTEM_MPI4PY-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_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 //MODIFIED property for variable: VTK_USE_X VTK_USE_X-MODIFIED:INTERNAL=ON //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 //ADVANCED property for variable: file_cmd file_cmd-ADVANCED:INTERNAL=1 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 M.Deij at marin.nl Tue Aug 18 07:04:58 2015 From: M.Deij at marin.nl (Deij-van Rijswijk, Menno) Date: Tue, 18 Aug 2015 11:04:58 +0000 Subject: [Paraview] Compiling ParaView 4.3.1 with OpenMPI In-Reply-To: References: Message-ID: <6a08fc07b7d34d9782c11acaf4ad1b1c@MAR190n2.marin.local> Hi Andrew, I checked my CMakeCache to see the variables of MPI and I think you need to change the MPI_LIBRARY:FILEPATH to MPI_LIBRARY:FILEPATH=/Programs/openmpi-1.8.4/build/lib/libmpi_cxx.so That is, directly use the full path to the mpi shared library, instead of using the link flag. Also, change the other LIBRARIES variables. In my case there are multiple libraries: MPI_C_LIBRARIES:STRING=libmpi.so MPI_CXX_LIBRARIES:STRING=libmpi_cxx.so;libmpi.so MPI_Fortran_LIBRARIES:STRING=libmpi_usempif08.so;libmpi_usempi_ignore_tkr.so;libmpi_mpifh.so;libmpi.so Where should expand to your install path, which is /Programs/openmpi-1.8.4/build/lib/ Good luck and best wishes, Menno Deij - van Rijswijk From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Andrew Sent: dinsdag 18 augustus 2015 12:51 To: paraview at paraview.org Subject: [Paraview] Compiling ParaView 4.3.1 with OpenMPI Hello. I need to compile ParaView 4.3.1 with MPI. I tried different settings but I can't get rid of this error: /usr/bin/ld: warning: libmpi_cxx.so.1, needed by ../lib/libvtkPVServerManagerApplication-pv4.3.so.1, not found (try using -rpath or -rpath-link) /usr/bin/ld: warning: libmpi.so.1, needed by ../lib/libvtkPVServerManagerApplication-pv4.3.so.1, not found (try using -rpath or -rpath-link) I use OpenMPI 1.8.4 that was successfuly compiled and installed in /Programs/openmpi-1.8.4/build (not into system directories, I need to have programs installed into custom directories). So I set the following options for MPI: MPIEXEC:FILEPATH=/Programs/openmpi-1.8.4/build/bin/mpiexec MPIEXEC_MAX_NUMPROCS:STRING=8 MPIEXEC_NUMPROC_FLAG:STRING=-np MPIEXEC_POSTFLAGS:STRING= MPIEXEC_PREFLAGS:STRING= MPI_CXX_COMPILER:FILEPATH=/Programs/openmpi-1.8.4/build/bin/mpicxx MPI_CXX_COMPILE_FLAGS:STRING=-Wl,-rpath -Wl,/Programs/openmpi-1.8.4/build/lib/ MPI_CXX_INCLUDE_PATH:STRING=/Programs/openmpi-1.8.4/build/include/ MPI_CXX_LIBRARIES:STRING=-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/ MPI_CXX_LINK_FLAGS:STRING= MPI_C_COMPILER:FILEPATH=/Programs/openmpi-1.8.4/build/bin/mpicc MPI_C_COMPILE_FLAGS:STRING=-Wl,-rpath -Wl,/Programs/openmpi-1.8.4/build/lib/ MPI_C_INCLUDE_PATH:STRING=/Programs/openmpi-1.8.4/build/include/ MPI_C_LIBRARIES:STRING=-lmpi -L/Programs/openmpi-1.8.4/build/lib/ MPI_C_LINK_FLAGS:STRING= MPI_EXTRA_LIBRARY:STRING=MPI_EXTRA_LIBRARY-NOTFOUND MPI_Fortran_COMPILER:FILEPATH=/Programs/openmpi-1.8.4/build/bin/mpif90 MPI_Fortran_COMPILE_FLAGS:STRING=-Wl,-rpath -Wl,/Programs/openmpi-1.8.4/build/lib/ MPI_Fortran_INCLUDE_PATH:STRING=/Programs/openmpi-1.8.4/build/include/ MPI_Fortran_LIBRARIES:STRING=-lmpi_mpifh -L/Programs/openmpi-1.8.4/build/lib/ MPI_Fortran_LINK_FLAGS:STRING= MPI_LIBRARY:FILEPATH=-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib It's a copy from the Makefile without comments. Actually I used ccmake to configure and generate Makefile. Compilation is normal until 98%. Then a number of errors appear because the linker cannot find MPI libraries (libmpi.so.1 and libmpi_cxx.so.1). I verified that these files are in "/Programs/openmpi-1.8.4/build/lib/" (searched with file manager to avoid typos, files are there). The interesting moment is that libmpi.so and libmpi_cxx.so are found (I don't point to *.so files, point only to lib directory). But then linker don't want to follow symlinks (libmpi.so => libmpi.so.1), if I get it right. I attached CMakeCache.txt file. If it's needed, I will post other details (Makefile + CMakeCache are too big for 500 KB limit of mailing list). Please, help me to compile ParaView with OpenMPI. Thanks. dr. ir. Menno A. Deij-van Rijswijk Researcher / Software Engineer Maritime Simulation & Software Group E mailto:M.Deij at marin.nl T +31 317 49 35 06 MARIN 2, Haagsteeg, P.O. Box 28, 6700 AA Wageningen, The Netherlands T +31 317 49 39 11, F +31 317 49 32 45, I www.marin.nl From antech777 at gmail.com Tue Aug 18 08:23:59 2015 From: antech777 at gmail.com (Andrew) Date: Tue, 18 Aug 2015 15:23:59 +0300 Subject: [Paraview] Compiling ParaView 4.3.1 with OpenMPI In-Reply-To: <6a08fc07b7d34d9782c11acaf4ad1b1c@MAR190n2.marin.local> References: <6a08fc07b7d34d9782c11acaf4ad1b1c@MAR190n2.marin.local> Message-ID: Menno Deij - van Rijswijk, Great thanks! Your suggestions worked perfectly! Now I have ParaView 4.3.1 compiled with MPI and Catalyst for co-processing. 2015-08-18 14:04 GMT+03:00 Deij-van Rijswijk, Menno : > Hi Andrew, > > I checked my CMakeCache to see the variables of MPI and I think you need > to change the MPI_LIBRARY:FILEPATH to > MPI_LIBRARY:FILEPATH=/Programs/openmpi-1.8.4/build/lib/libmpi_cxx.so > > That is, directly use the full path to the mpi shared library, instead of > using the link flag. > Also, change the other LIBRARIES variables. In my case there are multiple > libraries: > > MPI_C_LIBRARIES:STRING=libmpi.so > MPI_CXX_LIBRARIES:STRING=libmpi_cxx.so;libmpi.so > > MPI_Fortran_LIBRARIES:STRING=libmpi_usempif08.so;libmpi_usempi_ignore_tkr.so;libmpi_mpifh.so;libmpi.so > > Where should expand to your install path, which is > /Programs/openmpi-1.8.4/build/lib/ > > Good luck and best wishes, > > > Menno Deij - van Rijswijk > > > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Andrew > Sent: dinsdag 18 augustus 2015 12:51 > To: paraview at paraview.org > Subject: [Paraview] Compiling ParaView 4.3.1 with OpenMPI > > Hello. > > I need to compile ParaView 4.3.1 with MPI. I tried different settings but > I can't get rid of this error: > > /usr/bin/ld: warning: libmpi_cxx.so.1, needed by > ../lib/libvtkPVServerManagerApplication-pv4.3.so.1, not found (try using > -rpath or -rpath-link) > /usr/bin/ld: warning: libmpi.so.1, needed by > ../lib/libvtkPVServerManagerApplication-pv4.3.so.1, not found (try using > -rpath or -rpath-link) > > I use OpenMPI 1.8.4 that was successfuly compiled and installed in > /Programs/openmpi-1.8.4/build (not into system directories, I need to have > programs installed into custom directories). So I set the following options > for MPI: > MPIEXEC:FILEPATH=/Programs/openmpi-1.8.4/build/bin/mpiexec > MPIEXEC_MAX_NUMPROCS:STRING=8 > MPIEXEC_NUMPROC_FLAG:STRING=-np > MPIEXEC_POSTFLAGS:STRING= > MPIEXEC_PREFLAGS:STRING= > MPI_CXX_COMPILER:FILEPATH=/Programs/openmpi-1.8.4/build/bin/mpicxx > MPI_CXX_COMPILE_FLAGS:STRING=-Wl,-rpath > -Wl,/Programs/openmpi-1.8.4/build/lib/ > MPI_CXX_INCLUDE_PATH:STRING=/Programs/openmpi-1.8.4/build/include/ > MPI_CXX_LIBRARIES:STRING=-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib/ > MPI_CXX_LINK_FLAGS:STRING= > MPI_C_COMPILER:FILEPATH=/Programs/openmpi-1.8.4/build/bin/mpicc > MPI_C_COMPILE_FLAGS:STRING=-Wl,-rpath > -Wl,/Programs/openmpi-1.8.4/build/lib/ > MPI_C_INCLUDE_PATH:STRING=/Programs/openmpi-1.8.4/build/include/ > MPI_C_LIBRARIES:STRING=-lmpi -L/Programs/openmpi-1.8.4/build/lib/ > MPI_C_LINK_FLAGS:STRING= > MPI_EXTRA_LIBRARY:STRING=MPI_EXTRA_LIBRARY-NOTFOUND > MPI_Fortran_COMPILER:FILEPATH=/Programs/openmpi-1.8.4/build/bin/mpif90 > MPI_Fortran_COMPILE_FLAGS:STRING=-Wl,-rpath > -Wl,/Programs/openmpi-1.8.4/build/lib/ > MPI_Fortran_INCLUDE_PATH:STRING=/Programs/openmpi-1.8.4/build/include/ > MPI_Fortran_LIBRARIES:STRING=-lmpi_mpifh > -L/Programs/openmpi-1.8.4/build/lib/ > MPI_Fortran_LINK_FLAGS:STRING= > MPI_LIBRARY:FILEPATH=-lmpi_cxx -L/Programs/openmpi-1.8.4/build/lib > It's a copy from the Makefile without comments. Actually I used ccmake to > configure and generate Makefile. > > Compilation is normal until 98%. Then a number of errors appear because > the linker cannot find MPI libraries (libmpi.so.1 and libmpi_cxx.so.1). I > verified that these files are in "/Programs/openmpi-1.8.4/build/lib/" > (searched with file manager to avoid typos, files are there). The > interesting moment is that libmpi.so and libmpi_cxx.so are found (I don't > point to *.so files, point only to lib directory). But then linker don't > want to follow symlinks (libmpi.so => libmpi.so.1), if I get it right. > > I attached CMakeCache.txt file. If it's needed, I will post other details > (Makefile + CMakeCache are too big for 500 KB limit of mailing list). > > Please, help me to compile ParaView with OpenMPI. > Thanks. > > > dr. ir. Menno A. Deij-van Rijswijk > Researcher / Software Engineer > Maritime Simulation & Software Group > E mailto:M.Deij at marin.nl > T +31 317 49 35 06 > > > MARIN > 2, Haagsteeg, P.O. Box 28, 6700 AA Wageningen, The Netherlands > T +31 317 49 39 11, F +31 317 49 32 45, I www.marin.nl > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tanakas at gmx.ch Tue Aug 18 10:10:37 2015 From: tanakas at gmx.ch (Tanaka Simon) Date: Tue, 18 Aug 2015 16:10:37 +0200 Subject: [Paraview] colormaps: white is not really white In-Reply-To: <55D33C69.8050709@gmx.ch> References: <55D33C69.8050709@gmx.ch> Message-ID: <55D33CDD.5040700@gmx.ch> Hello, please see attachment. for example, i have a colormap which is plain white. but the rendering of the values (in the background of the color legend) would always be in a dirty ivory. how can i get a real white rendering? thanks s -------------- next part -------------- A non-text attachment was scrubbed... Name: notwhite.png Type: image/png Size: 9215 bytes Desc: not available URL: From dan.lipsa at kitware.com Tue Aug 18 10:42:34 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Tue, 18 Aug 2015 10:42:34 -0400 Subject: [Paraview] colormaps: white is not really white In-Reply-To: <55D33CDD.5040700@gmx.ch> References: <55D33C69.8050709@gmx.ch> <55D33CDD.5040700@gmx.ch> Message-ID: The ivory color comes from OpenGL lighting. The only way to get plain white is to disable OpenGL lighting - it does not seem to be a way to do this in ParaView. This would only make sense if you have a 2D only scene. On Tue, Aug 18, 2015 at 10:10 AM, Tanaka Simon wrote: > Hello, > > please see attachment. > > for example, i have a colormap which is plain white. but the rendering > of the values (in the background of the color legend) would always be in > a dirty ivory. > > how can i get a real white rendering? > > thanks > s > > > > > _______________________________________________ > 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: From kmorel at sandia.gov Tue Aug 18 10:48:37 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Tue, 18 Aug 2015 14:48:37 +0000 Subject: [Paraview] colormaps: white is not really white Message-ID: What I believe is happening is that you are coloring an object as white in the 3D view, and the 3D shading is dropping the intensity of the color. By default, the 3D view in ParaView is set up with 4 lights similar to the lights used in a photography studio with the brightest light above your head and a little to the right. This helps accentuate shades for 3D objects and make their shape more clear. However, I am guessing that you have a 2D object that is facing flat parallel to the viewing screen. In this case, there is no shading to be seen and the offset lights will dull the color. You can fix the problem by adjusting the lights. To do this in (ParaView 4.3 and later), type "Lights" in the search bar at the top of the Properties panel. When you do that, under the View section you will see a group named "Lights" with a button marked "Edit." Click the Edit button to get the "Lights Editor" dialog box. Turn off the checkmark next to "Light Kit" and turn on the one next to "Additional Headlight." Your object should look white now. -Ken On 8/18/15, 8:10 AM, "ParaView on behalf of Tanaka Simon" wrote: >Hello, > >please see attachment. > >for example, i have a colormap which is plain white. but the rendering >of the values (in the background of the color legend) would always be in >a dirty ivory. > >how can i get a real white rendering? > >thanks >s > > > From dan.lipsa at kitware.com Tue Aug 18 11:15:55 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Tue, 18 Aug 2015 11:15:55 -0400 Subject: [Paraview] colormaps: white is not really white In-Reply-To: References: Message-ID: Turn off the checkmark next to "Light Kit" and turn on the one > next to "Additional Headlight." Your object should look white now. > Great tip! I was wondering what this additional light is good for. :-) -------------- next part -------------- An HTML attachment was scrubbed... URL: From tanakas at gmx.ch Tue Aug 18 11:13:05 2015 From: tanakas at gmx.ch (Tanaka Simon) Date: Tue, 18 Aug 2015 17:13:05 +0200 Subject: [Paraview] colormaps: white is not really white In-Reply-To: References: Message-ID: <55D34B81.7040805@gmx.ch> thanks you, Ken, that solved my problem! s On 18.08.2015 16:48, Moreland, Kenneth wrote: > What I believe is happening is that you are coloring an object as white in > the 3D view, and the 3D shading is dropping the intensity of the color. By > default, the 3D view in ParaView is set up with 4 lights similar to the > lights used in a photography studio with the brightest light above your > head and a little to the right. This helps accentuate shades for 3D > objects and make their shape more clear. > > However, I am guessing that you have a 2D object that is facing flat > parallel to the viewing screen. In this case, there is no shading to be > seen and the offset lights will dull the color. You can fix the problem by > adjusting the lights. To do this in (ParaView 4.3 and later), type > "Lights" in the search bar at the top of the Properties panel. When you do > that, under the View section you will see a group named "Lights" with a > button marked "Edit." Click the Edit button to get the "Lights Editor" > dialog box. Turn off the checkmark next to "Light Kit" and turn on the one > next to "Additional Headlight." Your object should look white now. > > -Ken > > > > On 8/18/15, 8:10 AM, "ParaView on behalf of Tanaka Simon" > wrote: > >> Hello, >> >> please see attachment. >> >> for example, i have a colormap which is plain white. but the rendering >> of the values (in the background of the color legend) would always be in >> a dirty ivory. >> >> how can i get a real white rendering? >> >> thanks >> s >> >> >> From houssen at ipgp.fr Tue Aug 18 12:40:24 2015 From: houssen at ipgp.fr (houssen) Date: Tue, 18 Aug 2015 18:40:24 +0200 Subject: [Paraview] =?utf-8?q?How_to_use_a_plugin_from_the_python_script_s?= =?utf-8?q?hell_prompt_=3F?= Message-ID: <5bdf8a75fa5c6b1f9c2d06ee195e1754@imap.ipgp.fr> Hello, How to use a plugin from the python script shell prompt ? I have a plugin (filter) that works fine (manual load with "tools / manage plugins" + apply filter : OK). I'd like to use python to manipulate it (to test it actually within "make test"). Here is the python script: ~> more applyFilter.py #!/usr/bin/env python from paraview.simple import * LoadPlugin ( '/mnt/users/.../libMyFilter.so' ) data = XDMFReader ( FileNames = [ '/mnt/users/.../data.xmf' ] ) MyFilter () In interactive mode : 1. Make sure I start from scratch : myFilter is not in the "tools / manage plugins" list. 2. Open a Python shell prompt + run the script. 3. I get this error : >>> Traceback (most recent call last): File "", line 6, in NameError: name 'MyFilter' is not defined At this point, I was like "OK, there is perhaps a problem in the python wrapping of the C++ class". I google a bit and found that : http://www.cmake.org/pipermail/paraview/2013-December/030229.html. I tried to modify my plugin CMakeLists.txt (in particular with pv_setup_module_environment / pv_process_modules from the EyeDomeLighting plugin example) : didn't succeed to make it work. I cancelled all related modifications and got back to the initial CMakeList.txt which contains essentially this : ADD_PARAVIEW_PLUGIN ( myFilter "${CPACK_PACKAGE_VERSION_MAJOR}.${CPACK_PACKAGE_VERSION_MAJOR}" SERVER_MANAGER_XML myFilter.xml SERVER_MANAGER_SOURCES myFilter.cpp DOCUMENTATION_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc" ). After that, I was like "OK, maybe I need to import the python module corresponding to my plugin". As I don't know which one this could be, I tried to add in the script the line "from paraview.simple import *" a 2d time after the "LoadPlugin". I get another type of error: >>> Traceback (most recent call last): File "", line 7, in File "/home/houssen/Programs/ParaView/ParaView-v4.3.1-source/local/lib/paraview-4.3/site-packages/paraview/simple.py", line 1481, in CreateObject elif active_objects.source: File "/home/houssen/Programs/ParaView/ParaView-v4.3.1-source/local/lib/paraview-4.3/site-packages/paraview/simple.py", line 1690, in get_source self.__get_selection_model("ActiveSources").GetCurrentProxy()) File "/home/houssen/Programs/ParaView/ParaView-v4.3.1-source/local/lib/paraview-4.3/site-packages/paraview/simple.py", line 1684, in __convert_proxy servermanager._getPyProxy(px.GetSourceProxy()), AttributeError: GetSourceProxy After some testing, I ended up on this scenario which makes me think that there is actually no python wrapping problem. Here is the 2d scenario (in interactive mode): 1. In the GUI use "tools / manage plugins" to load myFilter : OK 2. In the GUI, open a data file 3. Open a Python shell prompt + type only the last script line "myFilter ()" : this works ?!... Surprisingly ?! So I would say there is no problem with the python binding. What did I miss ? Can somebody help me ? Franck PS : I run Ubuntu-14.04, I use ParaView-4.3.1 built from source From mosha at ntu.edu.sg Thu Aug 20 02:24:56 2015 From: mosha at ntu.edu.sg (Sha Mo) Date: Thu, 20 Aug 2015 06:24:56 +0000 Subject: [Paraview] How to redirect the path of python interpreter? Message-ID: <27A5A8A0-43CD-464E-A7D5-1E5DDED77D25@ntu.edu.sg> Hi everyone, After I install the preview, the preview python shell will be direct to the system default python interpreter path like ?/usr/bin/python?. The thing is, I want to redirect it to an other path for an other python interpreter, how can I do it? Thanks. Mo [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 antech777 at gmail.com Thu Aug 20 04:20:26 2015 From: antech777 at gmail.com (Andrew) Date: Thu, 20 Aug 2015 11:20:26 +0300 Subject: [Paraview] ParaView's Catalyst: problem with Python interpreter Message-ID: Hello. I have compiled ParaView 4.3.1 for offscreen rendering (Catalyst + CodeSaturne). Thanks for suggestions how to do it properly. But when I run calculation in CodeSaturne with co-processing enabled an error occures: Traceback (most recent call last): File "", line 104, in File "Catalyst.py", line 3, in from paraview import coprocessing File "/Programs/ParaView-4.3.1/build-catalyst/lib/site-packages/paraview/simple.py", line 40, in import lookuptable File "/Programs/ParaView-4.3.1/build-catalyst/lib/site-packages/paraview/lookuptable.py", line 21, in from math import sqrt ImportError: /usr/lib64/python2.6/lib-dynload/mathmodule.so: undefined symbol: PyExc_ValueError Here we see that execution of Catalyst.py (created with "usual" ParaView 4.3.1 build) starts, then some ParaView scripts start, but when importing *sqrt* function from *math* module in "lookuptable.py" the error occures because symbol "PyExc_ValueError" is "not seen" for some reason. I asked this question on Saturne forume and was given a suggestion to set some paths, but it didn't help. I searched the Internet for this error and found this info: https://bugzilla.redhat.com/show_bug.cgi?id=874874 I use CentOS 6.5 that, as I know, is very similar to RedHat 6.5 and uses the same version numbering. Is this problem relevant to my case? How can I solve it? CMakeCache.txt and Makefile used to build "catalyst edition" of ParaView 4.3.1 is in attached archive. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ParaViewConfig.zip Type: application/zip Size: 62838 bytes Desc: not available URL: From houssen at ipgp.fr Thu Aug 20 09:32:46 2015 From: houssen at ipgp.fr (houssen) Date: Thu, 20 Aug 2015 15:32:46 +0200 Subject: [Paraview] =?utf-8?q?How_to_use_a_plugin_from_the_python_script_s?= =?utf-8?q?hell_prompt_=3F?= In-Reply-To: <5bdf8a75fa5c6b1f9c2d06ee195e1754@imap.ipgp.fr> References: <5bdf8a75fa5c6b1f9c2d06ee195e1754@imap.ipgp.fr> Message-ID: <3d5638c1c44221b12c6e8f1447793d3d@imap.ipgp.fr> For the record, I finally found the solution : use ns = globals when loading the plugin ! LoadPlugin ( '/mnt/users/.../libMyFilter.so', remote = False, ns = globals () ) FH Le 2015-08-18 18:40, houssen a ?crit?: > Hello, > > How to use a plugin from the python script shell prompt ? > > I have a plugin (filter) that works fine (manual load with "tools / > manage plugins" + apply filter : OK). I'd like to use python to > manipulate it (to test it actually within "make test"). > > Here is the python script: > ~> more applyFilter.py > #!/usr/bin/env python > from paraview.simple import * > LoadPlugin ( '/mnt/users/.../libMyFilter.so' ) > data = XDMFReader ( FileNames = [ '/mnt/users/.../data.xmf' ] ) > MyFilter () > > In interactive mode : > 1. Make sure I start from scratch : myFilter is not in the "tools / > manage plugins" list. > 2. Open a Python shell prompt + run the script. > 3. I get this error : >>>> Traceback (most recent call last): > File "", line 6, in > NameError: name 'MyFilter' is not defined > > At this point, I was like "OK, there is perhaps a problem in the > python wrapping of the C++ class". I google a bit and found that : > http://www.cmake.org/pipermail/paraview/2013-December/030229.html. I > tried to modify my plugin CMakeLists.txt (in particular with > pv_setup_module_environment / pv_process_modules from the > EyeDomeLighting plugin example) : didn't succeed to make it work. I > cancelled all related modifications and got back to the initial > CMakeList.txt which contains essentially this : > ADD_PARAVIEW_PLUGIN ( myFilter > "${CPACK_PACKAGE_VERSION_MAJOR}.${CPACK_PACKAGE_VERSION_MAJOR}" > SERVER_MANAGER_XML myFilter.xml SERVER_MANAGER_SOURCES myFilter.cpp > DOCUMENTATION_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc" ). > > After that, I was like "OK, maybe I need to import the python module > corresponding to my plugin". As I don't know which one this could be, > I tried to add in the script the line "from paraview.simple import *" > a 2d time after the "LoadPlugin". I get another type of error: >>>> Traceback (most recent call last): > File "", line 7, in > File > > "/home/houssen/Programs/ParaView/ParaView-v4.3.1-source/local/lib/paraview-4.3/site-packages/paraview/simple.py", > line 1481, in CreateObject > elif active_objects.source: > File > > "/home/houssen/Programs/ParaView/ParaView-v4.3.1-source/local/lib/paraview-4.3/site-packages/paraview/simple.py", > line 1690, in get_source > self.__get_selection_model("ActiveSources").GetCurrentProxy()) > File > > "/home/houssen/Programs/ParaView/ParaView-v4.3.1-source/local/lib/paraview-4.3/site-packages/paraview/simple.py", > line 1684, in __convert_proxy > servermanager._getPyProxy(px.GetSourceProxy()), > AttributeError: GetSourceProxy > > After some testing, I ended up on this scenario which makes me think > that there is actually no python wrapping problem. Here is the 2d > scenario (in interactive mode): > 1. In the GUI use "tools / manage plugins" to load myFilter : OK > 2. In the GUI, open a data file > 3. Open a Python shell prompt + type only the last script line > "myFilter ()" : this works ?!... Surprisingly ?! > So I would say there is no problem with the python binding. > > What did I miss ? Can somebody help me ? > > Franck > > PS : I run Ubuntu-14.04, I use ParaView-4.3.1 built from source > _______________________________________________ > 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 dennis_conklin at goodyear.com Thu Aug 20 15:51:49 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Thu, 20 Aug 2015 19:51:49 +0000 Subject: [Paraview] How to find the nearest quad element? Message-ID: All, I have an Exodus, multi-block model. Most of the blocks are hex elements, and some are layers of quads (tires are composite structures). I would like to establish local strains which are oriented in the direction of the nearest quad layer. To do this I need to identify, for each hex in the model, which quad element in the model is closest to the hex. Then I can extract directions from the quad element and rotate the strain tensor in the hex to these local coordinates. My question is, is there some clever and efficient way to quickly determine the nearest quad for each hex in the model. Keep in mind that there are multiple blocks of quads, but if there is some way to address the quad blocks one at a time, I could make this work. The brute force way is: Loop over every hex in the model: Loop over every quad in the model: Calculate the distance between hex and quad Smallest distance wins! That is a pretty brutally inefficient calc (several million hex elements) that I am trying to avoid - any ideas about how best to approach this. I'm hoping for some elegant way to use connectivity or something of that sort. Thanks for looking Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: From matei.stroila at gmail.com Thu Aug 20 18:54:27 2015 From: matei.stroila at gmail.com (Matei Stroila) Date: Thu, 20 Aug 2015 22:54:27 +0000 Subject: [Paraview] Color by array component from Python script not working Message-ID: Hi, I am using ParaView 4.3.1 on Mac OSX. I used to be able to loop through the components of an attribute array and change the color of the representation. I am not sure why this is no longer working (don't recall when it was working, maybe 4.2?). It does work from GUI. This is the GUI trace for changing the color attribute three times: #### import the simple module from the paraview from paraview.simple import * #### disable automatic camera reset on 'Show' paraview.simple._DisableFirstRenderCameraReset() # get color transfer function/color map for 'SpeedArray' speedArrayLUT = GetColorTransferFunction('SpeedArray') speedArrayLUT.InterpretValuesAsCategories = 0 speedArrayLUT.EnableOpacityMapping = 0 speedArrayLUT.RGBPoints = [0.0, 1.0, 0.0, 0.0, 150.0, 0.0, 0.0, 1.0] speedArrayLUT.UseLogScale = 0 speedArrayLUT.LockScalarRange = 1 speedArrayLUT.ColorSpace = 'HSV' speedArrayLUT.UseBelowRangeColor = 0 speedArrayLUT.BelowRangeColor = [0.0, 0.0, 0.0] speedArrayLUT.UseAboveRangeColor = 0 speedArrayLUT.AboveRangeColor = [1.0, 1.0, 1.0] speedArrayLUT.NanColor = [0.498039, 0.498039, 0.498039] speedArrayLUT.Discretize = 1 speedArrayLUT.NumberOfTableValues = 256 speedArrayLUT.ScalarRangeInitialized = 1.0 speedArrayLUT.HSVWrap = 0 speedArrayLUT.VectorComponent = 96 speedArrayLUT.VectorMode = 'Component' speedArrayLUT.AllowDuplicateScalars = 1 speedArrayLUT.Annotations = [] speedArrayLUT.IndexedColors = [] # get opacity transfer function/opacity map for 'SpeedArray' speedArrayPWF = GetOpacityTransferFunction('SpeedArray') speedArrayPWF.Points = [0.0, 0.0, 0.5, 0.0, 150.0, 1.0, 0.5, 0.0] speedArrayPWF.AllowDuplicateScalars = 1 speedArrayPWF.ScalarRangeInitialized = 1 #change array component used for coloring speedArrayLUT.RGBPoints = [2.0, 1.0, 0.0, 0.0, 134.079086144, 0.0, 0.0, 1.0] speedArrayLUT.VectorComponent = 111 # Properties modified on speedArrayPWF speedArrayPWF.Points = [2.0, 0.0, 0.5, 0.0, 134.079086144, 1.0, 0.5, 0.0] #change array component used for coloring speedArrayLUT.RGBPoints = [2.0, 1.0, 0.0, 0.0, 131.302099153, 0.0, 0.0, 1.0] speedArrayLUT.VectorComponent = 127 # Properties modified on speedArrayPWF speedArrayPWF.Points = [2.0, 0.0, 0.5, 0.0, 131.302099153, 1.0, 0.5, 0.0] #change array component used for coloring speedArrayLUT.RGBPoints = [2.0, 1.0, 0.0, 0.0, 143.468496117, 0.0, 0.0, 1.0] speedArrayLUT.VectorComponent = 175 # Properties modified on speedArrayPWF speedArrayPWF.Points = [2.0, 0.0, 0.5, 0.0, 143.468496117, 1.0, 0.5, 0.0] #### uncomment the following to render all views # RenderAllViews() # alternatively, if you want to write images, you can use SaveScreenshot(...). I try to do the same from a script, this time keeping the color map the same (not rescaling), and that does not work, the color of the geometry stays the same: ############### *speedArrayLUT = GetColorTransferFunction('SpeedArray')* *speedArrayLUT.RGBPoints = [0.0, 1.0, 0.0, 0.0, 150.0, 0.0, 0.0, 1.0]* *speedArrayLUT.LockScalarRange = 1* *speedArrayLUT.ColorSpace = 'HSV'* *speedArrayLUT.NanColor = [0.498039, 0.498039, 0.498039]* *speedArrayLUT.ScalarRangeInitialized = 1.0* *speedArrayLUT.VectorComponent = 671* *speedArrayLUT.VectorMode = 'Component'* *speedArrayPWF = GetOpacityTransferFunction('SpeedArray')* *speedArrayPWF.Points = [0.0, 0.0, 0.5, 0.0, 150.0, 1.0, 0.5, 0.0]* *speedArrayPWF.ScalarRangeInitialized = 1* *attributesLUTColorBar = GetScalarBar(speedArrayLUT, renderView1)* *attributesLUTColorBar.Title = 'Speed (km/h)'* *for i in range_15min: * * speedArrayLUT.VectorComponent = i* * Render()* ################# If I add: *readerDisplay.RescaleTransferFunctionToDataRange() * in the loop, I do see the range of the color bar changing with each iteration, but the color of the rendered geometry does not change. Is there a way to force an update on the readerDisplay (where, *readerDisplay = GetDisplayProperties(reader, view=renderView1)*) Thanks for any suggestions. Matei -------------- next part -------------- An HTML attachment was scrubbed... URL: From samuelkey at bresnan.net Thu Aug 20 19:12:46 2015 From: samuelkey at bresnan.net (Samuel Key) Date: Thu, 20 Aug 2015 17:12:46 -0600 Subject: [Paraview] How to find the nearest quad element? In-Reply-To: References: Message-ID: <55D65EEE.2070905@bresnan.net> An HTML attachment was scrubbed... URL: From pcxjf1 at nottingham.ac.uk Fri Aug 21 06:55:16 2015 From: pcxjf1 at nottingham.ac.uk (James Furness) Date: Fri, 21 Aug 2015 10:55:16 +0000 Subject: [Paraview] Writing a Paraview Reader - Only part of the data available Message-ID: <7B8194A7-4FA4-42E8-8A16-9E332B25CA25@exmail.nottingham.ac.uk> Hello, I have a program that will produce an output either in csv, or a binary format (which I have written and can alter). The data points are constructed by taking 3 vectors, and stepping at set intervals along these vectors to construct a 3D set of data. Ultimately there shouldn?t be a restriction on the three vectors, so the data may not be in a rectilinear array. But I?m leaving this for now and assuming the data is constructed from 3 orthogonal Axis aligned vectors to create a rectilinear structured grid. When I have a better grasp of preview readers I?ll update the reader to account for this. I guess it would require an unstructured data type to handle non-orthogonal grids? Also, the user is free to select what data they save from the program. This could be many fields, both vector and scalar quantities. What has been selected is stored in a header to the file, and known on reading. For my toy example I save only one scalar quantity. I?ve been trying to write a reader for paraview to import the binary files output. The csv format works ok, but the files can become large and it is a pain to have to construct the vector quantities from 3 scalars in each case, I want to avoid the user having to do this work. Another reason for writing a custom reader is to include additional information into the binary file for visualisation (e.g. the position of atoms, not a field quantity). With that background and reasoning I have managed to follow the documentation enough to read a basic test file, get the origin and point spacing, and read a single scalar quantity into a vtkDataArray owned by a vtkImageData object. Paraview picks this up seemingly correctly, with one flaw: It only takes 2 elements from each dimension, 0 and 1 displaying 8 elements in total. I am confident it has read the other values correctly as the Information tab reports ?X extent 0 to 3? ?X range: -1 to 1? (as expected) and similar for the other dimensions. If I view the data in spreadsheet layout the 8 values it has seem correct, but the others are missing. The code I am using in the reader?s RequestData( ) function is added below. Does anyone know why this may be happening and how to fix it? Also, any advice on how I should structure the reader to handle the non-orthogonal data? Thanks for your time, and thank you for such a stellar program. The results paraview produces for this data is brilliant, hence my want to make it convenient for our users! Regards, James Furness CODE for RequestData( ) Method: ??????????????????????? int LondonReader::RequestData( vtkInformation*, vtkInformationVector**, vtkInformationVector *outputVector) { vtkWarningMacro("Requesting the data!"); ifstream finp; finp.open(this->FileName, ios::in | ios::binary); if (finp.is_open()) { cerr << "File is open without problem!" << endl; } else { cerr << "File failed to open :(" << endl; return 0; } // size of real numbers may not be 8. Check for this from file header int realSize; finp.read((char*)&realSize, sizeof(int)); if(realSize != 8) { cerr << "Not implimented yet!" << endl; return 0; } // number of data fields int nFields; finp.read((char*)&nFields, sizeof(int)); vtkImageData* image = vtkImageData::GetData(outputVector); // Read the dimensions of the grid and set the extent accordingly int gridDim[3]; finp.read((char*)&gridDim, 3*sizeof(int)); int extent[6] = {0, gridDim[0]-1, 0, gridDim[1]-1, 0, gridDim[2]-1}; image->SetExtent(extent); // Read the field names from the file std::vector fields; std::string strBuf; for (int i = 0; i < nFields; i++) { std::getline( finp, strBuf, '\0'); fields.push_back(strBuf); cerr << "Printing Fields (" << i << "): " << fields[i] << endl; } // setup image for only one field for test case image->AllocateScalars(VTK_FLOAT, 1); vtkDataArray* scalars = image->GetPointData()->GetScalars(); // currently there is only one field 'rho' scalars->SetName(fields[3].c_str()); double x, y, z, rho; double oX, oY, oZ; //origin coordinates double sX, sY, sZ; //spacing of points for (vtkIdType itx = 0; itx < gridDim[0]; itx++) { for (vtkIdType ity = 0; ity < gridDim[1]; ity++) { for (vtkIdType itz = 0; itz < gridDim[2]; itz++) { finp.read((char*)&x, realSize); finp.read((char*)&y, realSize); finp.read((char*)&z, realSize); finp.read((char*)&rho, realSize); // Find and set the origin and spacing if (itx == 0 && ity == 0 && itz == 0) { image->SetOrigin(x, y, z); oX = x; oY = y; oZ = z; } else if (itx == 1 && ity == 0 && itz == 0) { sX = x - oX; } else if (itx == 0 && ity == 1 && itz == 0) { sY = y - oY; } else if (itx == 0 && ity == 0 && itz == 1) { sZ = z - oZ; } //check correct read. cerr << x << "," << y << "," << z << "," << rho << ", at " << itx*(gridDim[1]*gridDim[2]) + ity*gridDim[2] + itz << endl; //add value scalars->SetTuple1(itx*gridDim[1]*gridDim[2] + ity*gridDim[2] + itz, rho); } } } image->SetSpacing(sX, sY, sZ); image->Print(cerr); return 1; } This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. From dennis_conklin at goodyear.com Fri Aug 21 08:21:46 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Fri, 21 Aug 2015 12:21:46 +0000 Subject: [Paraview] How to find the nearest quad element? Message-ID: Sam, Thanks for responding. You have helped me several times in the past and I am always grateful for your insights. In this case there is considerable refinement in the model, so only a very small portion of the hex elements are in immediate contact with quads. Also you could think of places like the tread in the tire where there is no reinforcement whatsoever. Another approach which I have considered is a wave propagation technique, where in the first wave every hex immediately adjacent to a quad gets direction cosines assigned (as you suggest). Then you loop thru the remaining elements and assign cosines from any adjacent quad or hex that has cosines. Eventually the direction cosines will propagate throughout the model. A major complication is that wavefronts will collide and then you will have to choose which of several conflicting neighbor cosines to adopt. Averaging is one approach but certain structures give adjoining cosines which are 180 degrees reversed, so averaging would give you an indeterminate direction. I am toying now with some pseudo-variables, such as combinations of radius and lateral location, combined with zoning, to try to find a quantity that is unique for a local section of the geometry, to reduce the search size for each hex element. I am still hoping for a very clever scheme which someone may suggest before I proceed with these much more brute force methods. Dennis Sam Key Wrote: Dennis, Assuming for the moment that each quad 4-tuple is a finite element that contains one or more tire reinforcement items, and that each quad 4-tuple is "sandwiched" in between two hex 8-node finite elements, then the quad's 4-tuple is also a surface facet of two different 8-node hexahedrons. Both hexhedrons are the 'closest' hexhedrons to the quad. Given the usual organization of 'element blocks' in the Exodus-II datum structures, the two closest hexahedrons will be located on the surface of their respective element blocks. Using material ID's which are also element block ID's, have the software generate surface side-sets for each of these two element blocks specified with these two material ID's. With luck, each member in the side-set will be specified as a 2-tuple, (Elem# in the block, Quad-Face# in the hexah) With his info, you can confine your search to finding the side-set item that has a 4-tuple that matches your quad's 4-tuple. The search is reduced to a relatively small collection of hexahedral surface 4-tuple faces. Hope this helps. Samuel W Key FMA Development, LLC 1005 39th Ave NE Great Falls, Montana 59404 USA From: Dennis Conklin Sent: Thursday, August 20, 2015 3:52 PM To: Paraview (paraview at paraview.org) Subject: How to find the nearest quad element? All, I have an Exodus, multi-block model. Most of the blocks are hex elements, and some are layers of quads (tires are composite structures). I would like to establish local strains which are oriented in the direction of the nearest quad layer. To do this I need to identify, for each hex in the model, which quad element in the model is closest to the hex. Then I can extract directions from the quad element and rotate the strain tensor in the hex to these local coordinates. My question is, is there some clever and efficient way to quickly determine the nearest quad for each hex in the model. Keep in mind that there are multiple blocks of quads, but if there is some way to address the quad blocks one at a time, I could make this work. The brute force way is: Loop over every hex in the model: Loop over every quad in the model: Calculate the distance between hex and quad Smallest distance wins! That is a pretty brutally inefficient calc (several million hex elements) that I am trying to avoid - any ideas about how best to approach this. I'm hoping for some elegant way to use connectivity or something of that sort. Thanks for looking Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: From S.R.Kharche at exeter.ac.uk Fri Aug 21 08:58:26 2015 From: S.R.Kharche at exeter.ac.uk (Kharche, Sanjay) Date: Fri, 21 Aug 2015 12:58:26 +0000 Subject: [Paraview] calculating the curl of a scalar field Message-ID: Hi I have time series data of a scalar field. Is there any way I can use paraview to calculate the curl of this scalar data? cheers Sanjay -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Fri Aug 21 11:25:45 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Fri, 21 Aug 2015 11:25:45 -0400 Subject: [Paraview] calculating the curl of a scalar field In-Reply-To: References: Message-ID: Hi Sanjay, How is the curl computed on scalar data? From my understanding, the curl must be done on a vector. Andy On Fri, Aug 21, 2015 at 8:58 AM, Kharche, Sanjay wrote: > > Hi > > > I have time series data of a scalar field. Is there any way I can use > paraview to calculate the curl of this > > scalar data? > > > cheers > > Sanjay > > _______________________________________________ > 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: From andy.bauer at kitware.com Fri Aug 21 11:38:20 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Fri, 21 Aug 2015 11:38:20 -0400 Subject: [Paraview] [Catalyst] segfault during destructor vtkCPProcessor -->vtkPVRenderWindow In-Reply-To: References: Message-ID: My guess would be that it's a memory issue. Can you try running with a memory checker? I've used valgrind in the past for stuff like this. On Tue, Aug 18, 2015 at 2:28 AM, Deij-van Rijswijk, Menno wrote: > Hi, > > I have a headless ParaView build of the HEAD origin/master (commit number > 1018) with libOSMesa 10.6.3 as offscreen renderer, to support a Catalyst > workflow. Everything works fine, except that the process of MPI-rank 0 will > give a segfault when a render window has been used in the catalyst pipeline > (this happens also when not running with mpiexec/mpirun). > > I'm not familiar enough with VTK/PV or gdb to try to solve this on my own, > so I post the gdb backtrace here in case someone has an idea what is going > on. Any clues on how to fix this are welcome :-) Let me know if you need > more information. > > Best wishes, > > > Menno Deij - van Rijswijk > > > > #0 0x00002aaac65a0137 in glIsTextureEXT () from > /home/mdeij/Programs/lib/libOSMesa.so.8 > #1 0x00002aaac4252def in vtkOpenGLTexture::ReleaseGraphicsResources > (this=0x2, win=0x0) > at > /home/mdeij/src/ParaView/VTK/Rendering/OpenGL/vtkOpenGLTexture.cxx:80 > #2 0x00002aaac01ef377 in vtkPVScalarBarActor::ReleaseGraphicsResources > (this=0x2, window=0x0) > at > /home/mdeij/src/ParaView/ParaViewCore/VTKExtensions/Rendering/vtkPVScalarBarActor.cxx:176 > #3 0x00002aaac4bc0584 in > vtkScalarBarRepresentation::ReleaseGraphicsResources (this=0x2, w=0x0) > at > /home/mdeij/src/ParaView/VTK/Interaction/Widgets/vtkScalarBarRepresentation.cxx:227 > #4 0x00002aaaaf6f1522 in vtkRenderer::SetRenderWindow (this=0x2, > renwin=0x0) > at /home/mdeij/src/ParaView/VTK/Rendering/Core/vtkRenderer.cxx:1211 > #5 0x00002aaaaf6f4f65 in vtkRenderWindow::RemoveRenderer (this=0x2, > ren=0x0) > at /home/mdeij/src/ParaView/VTK/Rendering/Core/vtkRenderWindow.cxx:831 > #6 0x00002aaabe043c85 in vtkPVRenderView::~vtkPVRenderView > (this=0x68f1de0) > at > /home/mdeij/src/ParaView/ParaViewCore/ClientServerCore/Rendering/vtkPVRenderView.cxx:426 > #7 0x00002aaabe043c3a in vtkPVRenderView::~vtkPVRenderView (this=0x2) > at > /home/mdeij/src/ParaView/ParaViewCore/ClientServerCore/Rendering/vtkPVRenderView.cxx:567 > #8 0x00002aaab4a9c446 in vtkSmartPointerBase::operator= (this=0x2, r=0x0) > at /home/mdeij/src/ParaView/VTK/Common/Core/vtkSmartPointerBase.cxx:75 > #9 0x00002aaaaebdded3 in vtkSIProxy::~vtkSIProxy (this=0x68f1a00) > at > /home/mdeij/src/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx:93 > #10 0x00002aaaaebdde9a in vtkSIProxy::~vtkSIProxy (this=0x2) > from > /home/mdeij/src/build_ParaView/lib/libvtkPVServerImplementationCore-pv4.3.so.1 > #11 0x00002aaaaebbe523 in ~vtkInternals (this=, > $30=) > at > /home/mdeij/src/ParaView/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:125 > #12 vtkPVSessionCore::~vtkPVSessionCore (this=0x39fd830) > at > /home/mdeij/src/ParaView/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:351 > #13 0x00002aaaaebbe3aa in vtkPVSessionCore::~vtkPVSessionCore (this=0x2) > from > /home/mdeij/src/build_ParaView/lib/libvtkPVServerImplementationCore-pv4.3.so.1 > #14 0x00002aaaaebbb867 in vtkPVSessionBase::~vtkPVSessionBase > (this=0x39fdc80) > at > /home/mdeij/src/ParaView/ParaViewCore/ServerImplementation/Core/vtkPVSessionBase.cxx:86 > #15 0x00002aaaae8b873a in vtkSMSession::~vtkSMSession (this=0x2) > from > /home/mdeij/src/build_ParaView/lib/libvtkPVServerManagerCore-pv4.3.so.1 > #16 0x00002aaaaee83d01 in ~vtkSmartPointer (this=, > $3=) > at /home/mdeij/src/ParaView/VTK/Common/Core/vtkSmartPointer.h:26 > #17 ~pair (this=, $2=) at > /usr/include/c++/4.4.7/bits/stl_pair.h:67 > #18 destroy (this=, __p=, $0= out>, $1=) > at /usr/include/c++/4.4.7/ext/new_allocator.h:115 > #19 _M_destroy_node (this=, __p=, > $8=, $9=) > at /usr/include/c++/4.4.7/bits/stl_tree.h:383 > #20 _M_erase (this=, __x=, $5= out>, $6=) > at /usr/include/c++/4.4.7/bits/stl_tree.h:972 > #21 clear (this=0x0, $3=) at > /usr/include/c++/4.4.7/bits/stl_tree.h:726 > #22 clear (this=, $2=) at > /usr/include/c++/4.4.7/bits/stl_map.h:626 > #23 vtkProcessModule::Finalize () at > /home/mdeij/src/ParaView/ParaViewCore/ClientServerCore/Core/vtkProcessModule.cxx:290 > #24 0x00002aaaad674142 in vtkInitializationHelper::Finalize () > at > /home/mdeij/src/ParaView/ParaViewCore/ServerManager/SMApplication/vtkInitializationHelper.cxx:279 > #25 0x00002aaaad242e48 in vtkCPCxxHelper::~vtkCPCxxHelper (this=0x2840fe0) > at /home/mdeij/src/ParaView/CoProcessing/Catalyst/vtkCPCxxHelper.cxx:58 > #26 0x00002aaaad242dfa in vtkCPCxxHelper::~vtkCPCxxHelper (this=0x2) > at > /home/mdeij/src/ParaView/CoProcessing/Catalyst/vtkCPCxxHelper.cxx:124 > #27 0x00002aaaad246ad2 in vtkCPProcessor::~vtkCPProcessor (this=0x3a0cbd0) > at /home/mdeij/src/ParaView/CoProcessing/Catalyst/vtkCPProcessor.cxx:66 > #28 0x00002aaaad246a4a in vtkCPProcessor::~vtkCPProcessor (this=0x2) > at > /home/mdeij/src/ParaView/CoProcessing/Catalyst/vtkCPProcessor.cxx:278 > > > dr. ir. Menno A. Deij-van Rijswijk > Researcher / Software Engineer > Maritime Simulation & Software Group > E mailto:M.Deij at marin.nl > T +31 317 49 35 06 > > > MARIN > 2, Haagsteeg, P.O. Box 28, 6700 AA Wageningen, The Netherlands > T +31 317 49 39 11, F +31 317 49 32 45, I www.marin.nl > > _______________________________________________ > 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: From S.R.Kharche at exeter.ac.uk Fri Aug 21 11:38:35 2015 From: S.R.Kharche at exeter.ac.uk (Kharche, Sanjay) Date: Fri, 21 Aug 2015 15:38:35 +0000 Subject: [Paraview] calculating the curl of a scalar field In-Reply-To: References: , Message-ID: Hi Andy Yes, I should rephrase. In my codes, I first calculate the spatial gradient of the scalar field. I need the curl of that at each FD location in my structured mesh. cheers Sanjay ________________________________ From: Andy Bauer Sent: 21 August 2015 03:25 To: Kharche, Sanjay Cc: paraview at paraview.org Subject: Re: [Paraview] calculating the curl of a scalar field Hi Sanjay, How is the curl computed on scalar data? From my understanding, the curl must be done on a vector. Andy On Fri, Aug 21, 2015 at 8:58 AM, Kharche, Sanjay > wrote: Hi I have time series data of a scalar field. Is there any way I can use paraview to calculate the curl of this scalar data? cheers Sanjay _______________________________________________ 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: From andy.bauer at kitware.com Fri Aug 21 11:56:23 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Fri, 21 Aug 2015 11:56:23 -0400 Subject: [Paraview] calculating the curl of a scalar field In-Reply-To: References: Message-ID: Well, the curl of the gradient of a scalar field should always be zero, assuming that the scalar field is twice differentiable. If you still want to do that though you can do the following: 1. Apply the Gradient of Unstructured Data Set filter on the scalar variable. You can leave the Result Array Name as Gradients. 2. Use the Python Calculator filter's curl function. The expression will be "curl(Gradients)". On Fri, Aug 21, 2015 at 11:38 AM, Kharche, Sanjay wrote: > > Hi Andy > > > Yes, I should rephrase. > > > In my codes, I first calculate the spatial gradient of the scalar field. > > I need the curl of that at each FD location in my structured mesh. > > > cheers > > Sanjay > > > ------------------------------ > *From:* Andy Bauer > *Sent:* 21 August 2015 03:25 > *To:* Kharche, Sanjay > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] calculating the curl of a scalar field > > Hi Sanjay, > > How is the curl computed on scalar data? From my understanding, the curl > must be done on a vector. > > Andy > > On Fri, Aug 21, 2015 at 8:58 AM, Kharche, Sanjay > wrote: > >> >> Hi >> >> >> I have time series data of a scalar field. Is there any way I can use >> paraview to calculate the curl of this >> >> scalar data? >> >> >> cheers >> >> Sanjay >> >> _______________________________________________ >> 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: From denis.cohen at gmail.com Mon Aug 24 02:59:48 2015 From: denis.cohen at gmail.com (denis cohen) Date: Mon, 24 Aug 2015 08:59:48 +0200 Subject: [Paraview] How to change value of index for time Message-ID: Hello, I have several vtu files with the same file names. I'd like to make a movie of all these files so how can I increment the value of index (for time) in these files. How can I do that? Thank you Denis -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Mon Aug 24 09:50:34 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Mon, 24 Aug 2015 09:50:34 -0400 Subject: [Paraview] How to change value of index for time In-Reply-To: References: Message-ID: Denis, Try renaming the files name-01.vtu, name-02.vtu, ... On Mon, Aug 24, 2015 at 2:59 AM, denis cohen wrote: > Hello, > I have several vtu files with the same file names. > I'd like to make a movie of all these files so how can I increment the > value of index (for time) in these files. > How can I do that? > > Thank you > > Denis > > _______________________________________________ > 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: From nawijn at gmail.com Mon Aug 24 10:27:53 2015 From: nawijn at gmail.com (Marco Nawijn) Date: Mon, 24 Aug 2015 16:27:53 +0200 Subject: [Paraview] How to find the nearest quad element? In-Reply-To: References: Message-ID: What about the following: Generate two additional datasets, one containing (an approximate of) the center of the hex elements, the second the center of the quads. Then create a vtkKdTreePointLocator object based on the center points of the quad elements. Than loop over the centers of the hex elements and use one of the Find* methods to get the closest quad. Marco On Fri, Aug 21, 2015 at 2:21 PM, Dennis Conklin wrote: > Sam, > > Thanks for responding. You have helped me several times in the past and I > am always grateful for your insights. In this case there is considerable > refinement in the model, so only a very small portion of the hex elements > are in immediate contact with quads. Also you could think of places like > the tread in the tire where there is no reinforcement whatsoever. > > Another approach which I have considered is a wave propagation technique, > where in the first wave every hex immediately adjacent to a quad gets > direction cosines assigned (as you suggest). Then you loop thru the > remaining elements and assign cosines from any adjacent quad or hex that > has cosines. Eventually the direction cosines will propagate throughout > the model. A major complication is that wavefronts will collide and then > you will have to choose which of several conflicting neighbor cosines to > adopt. Averaging is one approach but certain structures give adjoining > cosines which are 180 degrees reversed, so averaging would give you an > indeterminate direction. > > I am toying now with some pseudo-variables, such as combinations of radius > and lateral location, combined with zoning, to try to find a quantity that > is unique for a local section of the geometry, to reduce the search size > for each hex element. > > I am still hoping for a very clever scheme which someone may suggest > before I proceed with these much more brute force methods. > > Dennis > > > > *Sam Key Wrote:* > > *Dennis, * > > *Assuming for the moment that each quad 4-tuple is a finite element that > contains one or more tire reinforcement items, and that each quad 4-tuple > is "sandwiched" in between two hex 8-node finite elements, then the quad's > 4-tuple is also a surface facet of two different 8-node hexahedrons. Both > hexhedrons are the 'closest' hexhedrons to the quad. Given the usual > organization of 'element blocks' in the Exodus-II datum structures, the two > closest hexahedrons will be located on the surface of their respective > element blocks. * > > *Using material ID's which are also element block ID's, have the software > generate surface side-sets for each of these two element blocks specified > with these two material ID's. With luck, each member in the side-set will > be specified as a 2-tuple, (Elem# in the block, Quad-Face# in the hexah) * > > *With his info, you can confine your search to finding the side-set item > that has a 4-tuple that matches your quad's 4-tuple. The search is reduced > to a relatively small collection of hexahedral surface 4-tuple faces. * > > *Hope this helps. * > > *Samuel W Key FMA Development, LLC 1005 39th Ave NE Great Falls, Montana > 59404 USA * > > > > > > *From:* Dennis Conklin > *Sent:* Thursday, August 20, 2015 3:52 PM > *To:* Paraview (paraview at paraview.org) > *Subject:* How to find the nearest quad element? > > > > All, > > > > I have an Exodus, multi-block model. Most of the blocks are hex elements, > and some are layers of quads (tires are composite structures). I would > like to establish local strains which are oriented in the direction of the > nearest quad layer. To do this I need to identify, for each hex in the > model, which quad element in the model is closest to the hex. Then I can > extract directions from the quad element and rotate the strain tensor in > the hex to these local coordinates. > > > > My question is, is there some clever and efficient way to quickly > determine the nearest quad for each hex in the model. Keep in mind that > there are multiple blocks of quads, but if there is some way to address the > quad blocks one at a time, I could make this work. > > > > The brute force way is: > > Loop over every hex in the model: > > Loop over every quad in the model: > > Calculate the distance between hex and quad > > Smallest distance wins! > > > > That is a pretty brutally inefficient calc (several million hex elements) > that I am trying to avoid ? any ideas about how best to approach this. > I?m hoping for some elegant way to use connectivity or something of that > sort. > > > > Thanks for looking > > > > Dennis > > _______________________________________________ > 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: From dan.lipsa at kitware.com Mon Aug 24 10:31:05 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Mon, 24 Aug 2015 10:31:05 -0400 Subject: [Paraview] Writing a Paraview Reader - Only part of the data available In-Reply-To: <7B8194A7-4FA4-42E8-8A16-9E332B25CA25@exmail.nottingham.ac.uk> References: <7B8194A7-4FA4-42E8-8A16-9E332B25CA25@exmail.nottingham.ac.uk> Message-ID: James, You are missing image->SetDimensions() - that may be a reason why your scalar does not have all values. vtkRectilinear grid is like an image data with variable extents and warped grid. On Fri, Aug 21, 2015 at 6:55 AM, James Furness wrote: > Hello, > > I have a program that will produce an output either in csv, or a binary > format (which I have written and can alter). > > The data points are constructed by taking 3 vectors, and stepping at set > intervals along these vectors to construct a 3D set of data. Ultimately > there shouldn?t be a restriction on the three vectors, so the data may not > be in a rectilinear array. But I?m leaving this for now and assuming the > data is constructed from 3 orthogonal Axis aligned vectors to create a > rectilinear structured grid. When I have a better grasp of preview readers > I?ll update the reader to account for this. I guess it would require an > unstructured data type to handle non-orthogonal grids? > > Also, the user is free to select what data they save from the program. > This could be many fields, both vector and scalar quantities. What has been > selected is stored in a header to the file, and known on reading. For my > toy example I save only one scalar quantity. > > I?ve been trying to write a reader for paraview to import the binary files > output. The csv format works ok, but the files can become large and it is a > pain to have to construct the vector quantities from 3 scalars in each > case, I want to avoid the user having to do this work. Another reason for > writing a custom reader is to include additional information into the > binary file for visualisation (e.g. the position of atoms, not a field > quantity). > > With that background and reasoning I have managed to follow the > documentation enough to read a basic test file, get the origin and point > spacing, and read a single scalar quantity into a vtkDataArray owned by a > vtkImageData object. Paraview picks this up seemingly correctly, with one > flaw: > > It only takes 2 elements from each dimension, 0 and 1 displaying 8 > elements in total. I am confident it has read the other values correctly as > the Information tab reports ?X extent 0 to 3? ?X range: -1 to 1? (as > expected) and similar for the other dimensions. If I view the data in > spreadsheet layout the 8 values it has seem correct, but the others are > missing. > > The code I am using in the reader?s RequestData( ) function is added > below. > > Does anyone know why this may be happening and how to fix it? Also, any > advice on how I should structure the reader to handle the non-orthogonal > data? > > Thanks for your time, and thank you for such a stellar program. The > results paraview produces for this data is brilliant, hence my want to make > it convenient for our users! > > Regards, > James Furness > > > CODE for RequestData( ) Method: > ??????????????????????? > > int LondonReader::RequestData( > vtkInformation*, > vtkInformationVector**, > vtkInformationVector *outputVector) > { > vtkWarningMacro("Requesting the data!"); > > > ifstream finp; > finp.open(this->FileName, ios::in | ios::binary); > > if (finp.is_open()) { > cerr << "File is open without problem!" << endl; > } else { > cerr << "File failed to open :(" << endl; > return 0; > } > > // size of real numbers may not be 8. Check for this from file header > int realSize; > finp.read((char*)&realSize, sizeof(int)); > if(realSize != 8) { > cerr << "Not implimented yet!" << endl; > return 0; > } > > // number of data fields > int nFields; > finp.read((char*)&nFields, sizeof(int)); > > vtkImageData* image = vtkImageData::GetData(outputVector); > > // Read the dimensions of the grid and set the extent accordingly > int gridDim[3]; > finp.read((char*)&gridDim, 3*sizeof(int)); > int extent[6] = {0, gridDim[0]-1, 0, gridDim[1]-1, 0, gridDim[2]-1}; > image->SetExtent(extent); > > > // Read the field names from the file > std::vector fields; > std::string strBuf; > for (int i = 0; i < nFields; i++) { > std::getline( finp, strBuf, '\0'); > fields.push_back(strBuf); > cerr << "Printing Fields (" << i << "): " << fields[i] << endl; > } > > // setup image for only one field for test case > image->AllocateScalars(VTK_FLOAT, 1); > vtkDataArray* scalars = image->GetPointData()->GetScalars(); > > // currently there is only one field 'rho' > scalars->SetName(fields[3].c_str()); > > double x, y, z, rho; > double oX, oY, oZ; //origin coordinates > double sX, sY, sZ; //spacing of points > > for (vtkIdType itx = 0; itx < gridDim[0]; itx++) { > for (vtkIdType ity = 0; ity < gridDim[1]; ity++) { > for (vtkIdType itz = 0; itz < gridDim[2]; itz++) { > finp.read((char*)&x, realSize); > finp.read((char*)&y, realSize); > finp.read((char*)&z, realSize); > finp.read((char*)&rho, realSize); > > // Find and set the origin and spacing > if (itx == 0 && ity == 0 && itz == 0) { > image->SetOrigin(x, y, z); > oX = x; oY = y; oZ = z; > } else if (itx == 1 && ity == 0 && itz == 0) { > sX = x - oX; > } else if (itx == 0 && ity == 1 && itz == 0) { > sY = y - oY; > } else if (itx == 0 && ity == 0 && itz == 1) { > sZ = z - oZ; > } > //check correct read. > cerr << x << "," << y << "," << z << "," << rho << ", at " > << itx*(gridDim[1]*gridDim[2]) + ity*gridDim[2] + itz << endl; > > //add value > scalars->SetTuple1(itx*gridDim[1]*gridDim[2] + > ity*gridDim[2] + itz, > rho); > } > } > } > > image->SetSpacing(sX, sY, sZ); > > image->Print(cerr); > > return 1; > } > > > > > > This message and any attachment are intended solely for the addressee > and may contain confidential information. If you have received this > message in error, please send it back to me, and immediately delete it. > > Please do not use, copy or disclose the information contained in this > message or in any attachment. Any views or opinions expressed by the > author of this email do not necessarily reflect the views of the > University of Nottingham. > > This message has been checked for viruses but the contents of an > attachment may still contain software viruses which could damage your > computer system, you are advised to perform your own checks. Email > communications with the University of Nottingham may be monitored as > permitted by UK legislation. > > _______________________________________________ > 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: From samuelkey at bresnan.net Mon Aug 24 11:54:41 2015 From: samuelkey at bresnan.net (Samuel Key) Date: Mon, 24 Aug 2015 09:54:41 -0600 Subject: [Paraview] How to change value of index for time In-Reply-To: References: Message-ID: <55DB3E41.4030606@bresnan.net> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: example.pvd Type: text/xml Size: 3420 bytes Desc: not available URL: From fabian.braun at epfl.ch Tue Aug 25 06:13:20 2015 From: fabian.braun at epfl.ch (Braun Fabian) Date: Tue, 25 Aug 2015 10:13:20 +0000 Subject: [Paraview] Read EnsightGold with different timesteps Message-ID: Dear all, In order to nicely visualize a dynamic 3D model I want to use ParaView in combination which EnsightGold (*.case) files. My tetrahedral FE model has a static geometry and only one variable of the elements (scalar per element) is changing over time. To this end I created three files: (1) example.case, (2) example.geo, (3) example.sigma. The latter is holding all timesteps of the dynamic variable (in my case the conductivity). Furthermore, I've verified these files using the ens_checker application which concludes with a positive "Hooray! Data format verification SUCCESSFUL with No Warnings". However, if I load the casefile in ParaView only the first timestep can be visualized. As soon as I change the time to another timestep ParaView freezes (no more reaction and consumes 100% of CPU). Is it possible that what I want to do using the EnsightGold files is not supported by ParaView? What else would you suggest me to resolve this problem? Thank you very much for your help in advance. Best wishes, Fab PS: I am using ParaView 4.3.1 on a Win 7 64-bit machine PS2: A hint which might be useful for others looking for the ens_checker application: I simply downloaded the current trial version of Ensight, opened the executable of the setup in an archive manager (e.g. 7-zip), located and extracted the ens_checker.exe. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dennis_conklin at goodyear.com Tue Aug 25 07:40:24 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Tue, 25 Aug 2015 11:40:24 +0000 Subject: [Paraview] [EXT] Re: How to find the nearest quad element? In-Reply-To: References: Message-ID: Marco, Thanks for that tip ? I?m not very familiar with vtk and I?ve never heard of that class but it seems appropriate so I will try to dig into it. Thanks again Dennis From: Marco Nawijn [mailto:nawijn at gmail.com] Sent: Monday, August 24, 2015 10:28 AM To: Dennis Conklin Cc: Paraview (paraview at paraview.org) Subject: [EXT] Re: [Paraview] How to find the nearest quad element? What about the following: Generate two additional datasets, one containing (an approximate of) the center of the hex elements, the second the center of the quads. Then create a vtkKdTreePointLocator object based on the center points of the quad elements. Than loop over the centers of the hex elements and use one of the Find* methods to get the closest quad. Marco On Fri, Aug 21, 2015 at 2:21 PM, Dennis Conklin > wrote: Sam, Thanks for responding. You have helped me several times in the past and I am always grateful for your insights. In this case there is considerable refinement in the model, so only a very small portion of the hex elements are in immediate contact with quads. Also you could think of places like the tread in the tire where there is no reinforcement whatsoever. Another approach which I have considered is a wave propagation technique, where in the first wave every hex immediately adjacent to a quad gets direction cosines assigned (as you suggest). Then you loop thru the remaining elements and assign cosines from any adjacent quad or hex that has cosines. Eventually the direction cosines will propagate throughout the model. A major complication is that wavefronts will collide and then you will have to choose which of several conflicting neighbor cosines to adopt. Averaging is one approach but certain structures give adjoining cosines which are 180 degrees reversed, so averaging would give you an indeterminate direction. I am toying now with some pseudo-variables, such as combinations of radius and lateral location, combined with zoning, to try to find a quantity that is unique for a local section of the geometry, to reduce the search size for each hex element. I am still hoping for a very clever scheme which someone may suggest before I proceed with these much more brute force methods. Dennis Sam Key Wrote: Dennis, Assuming for the moment that each quad 4-tuple is a finite element that contains one or more tire reinforcement items, and that each quad 4-tuple is "sandwiched" in between two hex 8-node finite elements, then the quad's 4-tuple is also a surface facet of two different 8-node hexahedrons. Both hexhedrons are the 'closest' hexhedrons to the quad. Given the usual organization of 'element blocks' in the Exodus-II datum structures, the two closest hexahedrons will be located on the surface of their respective element blocks. Using material ID's which are also element block ID's, have the software generate surface side-sets for each of these two element blocks specified with these two material ID's. With luck, each member in the side-set will be specified as a 2-tuple, (Elem# in the block, Quad-Face# in the hexah) With his info, you can confine your search to finding the side-set item that has a 4-tuple that matches your quad's 4-tuple. The search is reduced to a relatively small collection of hexahedral surface 4-tuple faces. Hope this helps. Samuel W Key FMA Development, LLC 1005 39th Ave NE Great Falls, Montana 59404 USA From: Dennis Conklin Sent: Thursday, August 20, 2015 3:52 PM To: Paraview (paraview at paraview.org) Subject: How to find the nearest quad element? All, I have an Exodus, multi-block model. Most of the blocks are hex elements, and some are layers of quads (tires are composite structures). I would like to establish local strains which are oriented in the direction of the nearest quad layer. To do this I need to identify, for each hex in the model, which quad element in the model is closest to the hex. Then I can extract directions from the quad element and rotate the strain tensor in the hex to these local coordinates. My question is, is there some clever and efficient way to quickly determine the nearest quad for each hex in the model. Keep in mind that there are multiple blocks of quads, but if there is some way to address the quad blocks one at a time, I could make this work. The brute force way is: Loop over every hex in the model: Loop over every quad in the model: Calculate the distance between hex and quad Smallest distance wins! That is a pretty brutally inefficient calc (several million hex elements) that I am trying to avoid ? any ideas about how best to approach this. I?m hoping for some elegant way to use connectivity or something of that sort. Thanks for looking Dennis _______________________________________________ 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: From dan.lipsa at kitware.com Tue Aug 25 10:39:14 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Tue, 25 Aug 2015 10:39:14 -0400 Subject: [Paraview] Writing a Paraview Reader - Only part of the data available In-Reply-To: <80331877-BCB4-45B1-8194-29671BF0284B@exmail.nottingham.ac.uk> References: <7B8194A7-4FA4-42E8-8A16-9E332B25CA25@exmail.nottingham.ac.uk> <80331877-BCB4-45B1-8194-29671BF0284B@exmail.nottingham.ac.uk> Message-ID: Hi James, I was used to the old style and it kind of made sense with the problem you are seeing, but you are right, setDimensions does not seem to be the problem. Is it any way I can get the code and a sample data so that I can run it through a debugger. I cannot see anything else in the code. Dan On Tue, Aug 25, 2015 at 9:20 AM, James Furness wrote: > Thanks for your advice, however it hasn?t quite solved my problem. > > You are missing image->SetDimensions() - that may be a reason why your > scalar does not have all values. > > > The documentation marks vtkImageData::SetDimensions( ... ) as > depreciated, and instead vtkImageData::SetExtent( ... ) should be used. It > remarks that SetDimension is equivalent to SetExtent(0, i-1, 0, j-1, 0, > k-1). > > (( doc page - > http://www.vtk.org/doc/nightly/html/classvtkImageData.html#a42bc5faee908c50407e9d9ec97f74238 > )) > > Regardless, I tried using SetDimensions in this way, and resulted in some > nasty set-fault crashes. Whilst now 64 elements were found correctly, all > passed the first 8 were memory junk. When I use SetExtent( ? ) the > information print on the image object happily reports dimensions of 4, 4, 4 > as expected. So it seems this is set by SetExtent( ? ). > > vtkRectilinear grid is like an image data with variable extents and warped > grid. > > > I?ll look into this class. It?s possible that I am mangling this reader by > trying to shoehorn my problem into an inappropriate class at the moment. > Thanks for pointing this out. > > Many thanks, > James > > On 24 Aug 2015, at 15:31, Dan Lipsa wrote: > > James, > You are missing image->SetDimensions() - that may be a reason why your > scalar does not have all values. > > vtkRectilinear grid is like an image data with variable extents and warped > grid. > > > On Fri, Aug 21, 2015 at 6:55 AM, James Furness > wrote: > >> Hello, >> >> I have a program that will produce an output either in csv, or a binary >> format (which I have written and can alter). >> >> The data points are constructed by taking 3 vectors, and stepping at set >> intervals along these vectors to construct a 3D set of data. Ultimately >> there shouldn?t be a restriction on the three vectors, so the data may not >> be in a rectilinear array. But I?m leaving this for now and assuming the >> data is constructed from 3 orthogonal Axis aligned vectors to create a >> rectilinear structured grid. When I have a better grasp of preview readers >> I?ll update the reader to account for this. I guess it would require an >> unstructured data type to handle non-orthogonal grids? >> >> Also, the user is free to select what data they save from the program. >> This could be many fields, both vector and scalar quantities. What has been >> selected is stored in a header to the file, and known on reading. For my >> toy example I save only one scalar quantity. >> >> I?ve been trying to write a reader for paraview to import the binary >> files output. The csv format works ok, but the files can become large and >> it is a pain to have to construct the vector quantities from 3 scalars in >> each case, I want to avoid the user having to do this work. Another reason >> for writing a custom reader is to include additional information into the >> binary file for visualisation (e.g. the position of atoms, not a field >> quantity). >> >> With that background and reasoning I have managed to follow the >> documentation enough to read a basic test file, get the origin and point >> spacing, and read a single scalar quantity into a vtkDataArray owned by a >> vtkImageData object. Paraview picks this up seemingly correctly, with one >> flaw: >> >> It only takes 2 elements from each dimension, 0 and 1 displaying 8 >> elements in total. I am confident it has read the other values correctly as >> the Information tab reports ?X extent 0 to 3? ?X range: -1 to 1? (as >> expected) and similar for the other dimensions. If I view the data in >> spreadsheet layout the 8 values it has seem correct, but the others are >> missing. >> >> The code I am using in the reader?s RequestData( ) function is added >> below. >> >> Does anyone know why this may be happening and how to fix it? Also, any >> advice on how I should structure the reader to handle the non-orthogonal >> data? >> >> Thanks for your time, and thank you for such a stellar program. The >> results paraview produces for this data is brilliant, hence my want to make >> it convenient for our users! >> >> Regards, >> James Furness >> >> >> CODE for RequestData( ) Method: >> ??????????????????????? >> >> int LondonReader::RequestData( >> vtkInformation*, >> vtkInformationVector**, >> vtkInformationVector *outputVector) >> { >> vtkWarningMacro("Requesting the data!"); >> >> >> ifstream finp; >> finp.open(this->FileName, ios::in | ios::binary); >> >> if (finp.is_open()) { >> cerr << "File is open without problem!" << endl; >> } else { >> cerr << "File failed to open :(" << endl; >> return 0; >> } >> >> // size of real numbers may not be 8. Check for this from file header >> int realSize; >> finp.read((char*)&realSize, sizeof(int)); >> if(realSize != 8) { >> cerr << "Not implimented yet!" << endl; >> return 0; >> } >> >> // number of data fields >> int nFields; >> finp.read((char*)&nFields, sizeof(int)); >> >> vtkImageData* image = vtkImageData::GetData(outputVector); >> >> // Read the dimensions of the grid and set the extent accordingly >> int gridDim[3]; >> finp.read((char*)&gridDim, 3*sizeof(int)); >> int extent[6] = {0, gridDim[0]-1, 0, gridDim[1]-1, 0, gridDim[2]-1}; >> image->SetExtent(extent); >> >> >> // Read the field names from the file >> std::vector fields; >> std::string strBuf; >> for (int i = 0; i < nFields; i++) { >> std::getline( finp, strBuf, '\0'); >> fields.push_back(strBuf); >> cerr << "Printing Fields (" << i << "): " << fields[i] << endl; >> } >> >> // setup image for only one field for test case >> image->AllocateScalars(VTK_FLOAT, 1); >> vtkDataArray* scalars = image->GetPointData()->GetScalars(); >> >> // currently there is only one field 'rho' >> scalars->SetName(fields[3].c_str()); >> >> double x, y, z, rho; >> double oX, oY, oZ; //origin coordinates >> double sX, sY, sZ; //spacing of points >> >> for (vtkIdType itx = 0; itx < gridDim[0]; itx++) { >> for (vtkIdType ity = 0; ity < gridDim[1]; ity++) { >> for (vtkIdType itz = 0; itz < gridDim[2]; itz++) { >> finp.read((char*)&x, realSize); >> finp.read((char*)&y, realSize); >> finp.read((char*)&z, realSize); >> finp.read((char*)&rho, realSize); >> >> // Find and set the origin and spacing >> if (itx == 0 && ity == 0 && itz == 0) { >> image->SetOrigin(x, y, z); >> oX = x; oY = y; oZ = z; >> } else if (itx == 1 && ity == 0 && itz == 0) { >> sX = x - oX; >> } else if (itx == 0 && ity == 1 && itz == 0) { >> sY = y - oY; >> } else if (itx == 0 && ity == 0 && itz == 1) { >> sZ = z - oZ; >> } >> //check correct read. >> cerr << x << "," << y << "," << z << "," << rho << ", at >> " << itx*(gridDim[1]*gridDim[2]) + ity*gridDim[2] + itz << endl; >> >> //add value >> scalars->SetTuple1(itx*gridDim[1]*gridDim[2] + >> ity*gridDim[2] + itz, >> rho); >> } >> } >> } >> >> image->SetSpacing(sX, sY, sZ); >> >> image->Print(cerr); >> >> return 1; >> } >> >> >> >> >> >> This message and any attachment are intended solely for the addressee >> and may contain confidential information. If you have received this >> message in error, please send it back to me, and immediately delete it. >> >> Please do not use, copy or disclose the information contained in this >> message or in any attachment. Any views or opinions expressed by the >> author of this email do not necessarily reflect the views of the >> University of Nottingham. >> >> This message has been checked for viruses but the contents of an >> attachment may still contain software viruses which could damage your >> computer system, you are advised to perform your own checks. Email >> communications with the University of Nottingham may be monitored as >> permitted by UK legislation. >> >> _______________________________________________ >> 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 >> > > > This message and any attachment are intended solely for the addressee > and may contain confidential information. If you have received this > message in error, please send it back to me, and immediately delete it. > > Please do not use, copy or disclose the information contained in this > message or in any attachment. Any views or opinions expressed by the > author of this email do not necessarily reflect the views of the > University of Nottingham. > > This message has been checked for viruses but the contents of an > attachment may still contain software viruses which could damage your > computer system, you are advised to perform your own checks. Email > communications with the University of Nottingham may be monitored as > permitted by UK legislation. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nawijn at gmail.com Tue Aug 25 11:21:13 2015 From: nawijn at gmail.com (Marco Nawijn) Date: Tue, 25 Aug 2015 17:21:13 +0200 Subject: [Paraview] [EXT] Re: How to find the nearest quad element? In-Reply-To: References: Message-ID: Hi Dennis, You might also be interested in the vtkCellCenters filter. As the name suggests, it will generate the centers of the cells for you. If you are not in a big rush, I can build you a small self contained sample in Python that demonstrates the filter and the use of the point locator. I am a little busy at the moment, but I can post the sample in a couple of days. Marco On Tue, Aug 25, 2015 at 1:40 PM, Dennis Conklin wrote: > Marco, > > > > Thanks for that tip ? I?m not very familiar with vtk and I?ve never heard > of that class but it seems appropriate so I will try to dig into it. > > > > Thanks again > > > > Dennis > > > > *From:* Marco Nawijn [mailto:nawijn at gmail.com] > *Sent:* Monday, August 24, 2015 10:28 AM > *To:* Dennis Conklin > *Cc:* Paraview (paraview at paraview.org) > *Subject:* [EXT] Re: [Paraview] How to find the nearest quad element? > > > > What about the following: > > > > Generate two additional datasets, one containing (an approximate of) the > center of the hex elements, the second the center of the quads. Then create > a vtkKdTreePointLocator object based on the center points of the quad > elements. Than loop over the centers of the hex elements and use one of the > Find* methods to get the closest quad. > > > > Marco > > > > > > > > > > On Fri, Aug 21, 2015 at 2:21 PM, Dennis Conklin < > dennis_conklin at goodyear.com> wrote: > > Sam, > > Thanks for responding. You have helped me several times in the past and I > am always grateful for your insights. In this case there is considerable > refinement in the model, so only a very small portion of the hex elements > are in immediate contact with quads. Also you could think of places like > the tread in the tire where there is no reinforcement whatsoever. > > Another approach which I have considered is a wave propagation technique, > where in the first wave every hex immediately adjacent to a quad gets > direction cosines assigned (as you suggest). Then you loop thru the > remaining elements and assign cosines from any adjacent quad or hex that > has cosines. Eventually the direction cosines will propagate throughout > the model. A major complication is that wavefronts will collide and then > you will have to choose which of several conflicting neighbor cosines to > adopt. Averaging is one approach but certain structures give adjoining > cosines which are 180 degrees reversed, so averaging would give you an > indeterminate direction. > > I am toying now with some pseudo-variables, such as combinations of radius > and lateral location, combined with zoning, to try to find a quantity that > is unique for a local section of the geometry, to reduce the search size > for each hex element. > > I am still hoping for a very clever scheme which someone may suggest > before I proceed with these much more brute force methods. > > Dennis > > > > *Sam Key Wrote:* > > *Dennis, * > > *Assuming for the moment that each quad 4-tuple is a finite element that > contains one or more tire reinforcement items, and that each quad 4-tuple > is "sandwiched" in between two hex 8-node finite elements, then the quad's > 4-tuple is also a surface facet of two different 8-node hexahedrons. Both > hexhedrons are the 'closest' hexhedrons to the quad. Given the usual > organization of 'element blocks' in the Exodus-II datum structures, the two > closest hexahedrons will be located on the surface of their respective > element blocks. * > > *Using material ID's which are also element block ID's, have the software > generate surface side-sets for each of these two element blocks specified > with these two material ID's. With luck, each member in the side-set will > be specified as a 2-tuple, (Elem# in the block, Quad-Face# in the hexah) * > > *With his info, you can confine your search to finding the side-set item > that has a 4-tuple that matches your quad's 4-tuple. The search is reduced > to a relatively small collection of hexahedral surface 4-tuple faces. * > > *Hope this helps. * > > *Samuel W Key FMA Development, LLC 1005 39th Ave NE Great Falls, Montana > 59404 USA * > > > > > > *From:* Dennis Conklin > *Sent:* Thursday, August 20, 2015 3:52 PM > *To:* Paraview (paraview at paraview.org) > *Subject:* How to find the nearest quad element? > > > > All, > > > > I have an Exodus, multi-block model. Most of the blocks are hex elements, > and some are layers of quads (tires are composite structures). I would > like to establish local strains which are oriented in the direction of the > nearest quad layer. To do this I need to identify, for each hex in the > model, which quad element in the model is closest to the hex. Then I can > extract directions from the quad element and rotate the strain tensor in > the hex to these local coordinates. > > > > My question is, is there some clever and efficient way to quickly > determine the nearest quad for each hex in the model. Keep in mind that > there are multiple blocks of quads, but if there is some way to address the > quad blocks one at a time, I could make this work. > > > > The brute force way is: > > Loop over every hex in the model: > > Loop over every quad in the model: > > Calculate the distance between hex and quad > > Smallest distance wins! > > > > That is a pretty brutally inefficient calc (several million hex elements) > that I am trying to avoid ? any ideas about how best to approach this. > I?m hoping for some elegant way to use connectivity or something of that > sort. > > > > Thanks for looking > > > > Dennis > > > _______________________________________________ > 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: From dennis_conklin at goodyear.com Tue Aug 25 11:24:17 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Tue, 25 Aug 2015 15:24:17 +0000 Subject: [Paraview] [EXT] Re: How to find the nearest quad element? In-Reply-To: References: Message-ID: Marco, I am actually tied up for the next week or so, so if you can post a sample in that timeframe that would be perfect. Thanks very much Dennis From: Marco Nawijn [mailto:nawijn at gmail.com] Sent: Tuesday, August 25, 2015 11:21 AM To: Dennis Conklin Cc: Paraview (paraview at paraview.org) Subject: Re: [EXT] Re: [Paraview] How to find the nearest quad element? Hi Dennis, You might also be interested in the vtkCellCenters filter. As the name suggests, it will generate the centers of the cells for you. If you are not in a big rush, I can build you a small self contained sample in Python that demonstrates the filter and the use of the point locator. I am a little busy at the moment, but I can post the sample in a couple of days. Marco On Tue, Aug 25, 2015 at 1:40 PM, Dennis Conklin > wrote: Marco, Thanks for that tip ? I?m not very familiar with vtk and I?ve never heard of that class but it seems appropriate so I will try to dig into it. Thanks again Dennis From: Marco Nawijn [mailto:nawijn at gmail.com] Sent: Monday, August 24, 2015 10:28 AM To: Dennis Conklin Cc: Paraview (paraview at paraview.org) Subject: [EXT] Re: [Paraview] How to find the nearest quad element? What about the following: Generate two additional datasets, one containing (an approximate of) the center of the hex elements, the second the center of the quads. Then create a vtkKdTreePointLocator object based on the center points of the quad elements. Than loop over the centers of the hex elements and use one of the Find* methods to get the closest quad. Marco On Fri, Aug 21, 2015 at 2:21 PM, Dennis Conklin > wrote: Sam, Thanks for responding. You have helped me several times in the past and I am always grateful for your insights. In this case there is considerable refinement in the model, so only a very small portion of the hex elements are in immediate contact with quads. Also you could think of places like the tread in the tire where there is no reinforcement whatsoever. Another approach which I have considered is a wave propagation technique, where in the first wave every hex immediately adjacent to a quad gets direction cosines assigned (as you suggest). Then you loop thru the remaining elements and assign cosines from any adjacent quad or hex that has cosines. Eventually the direction cosines will propagate throughout the model. A major complication is that wavefronts will collide and then you will have to choose which of several conflicting neighbor cosines to adopt. Averaging is one approach but certain structures give adjoining cosines which are 180 degrees reversed, so averaging would give you an indeterminate direction. I am toying now with some pseudo-variables, such as combinations of radius and lateral location, combined with zoning, to try to find a quantity that is unique for a local section of the geometry, to reduce the search size for each hex element. I am still hoping for a very clever scheme which someone may suggest before I proceed with these much more brute force methods. Dennis Sam Key Wrote: Dennis, Assuming for the moment that each quad 4-tuple is a finite element that contains one or more tire reinforcement items, and that each quad 4-tuple is "sandwiched" in between two hex 8-node finite elements, then the quad's 4-tuple is also a surface facet of two different 8-node hexahedrons. Both hexhedrons are the 'closest' hexhedrons to the quad. Given the usual organization of 'element blocks' in the Exodus-II datum structures, the two closest hexahedrons will be located on the surface of their respective element blocks. Using material ID's which are also element block ID's, have the software generate surface side-sets for each of these two element blocks specified with these two material ID's. With luck, each member in the side-set will be specified as a 2-tuple, (Elem# in the block, Quad-Face# in the hexah) With his info, you can confine your search to finding the side-set item that has a 4-tuple that matches your quad's 4-tuple. The search is reduced to a relatively small collection of hexahedral surface 4-tuple faces. Hope this helps. Samuel W Key FMA Development, LLC 1005 39th Ave NE Great Falls, Montana 59404 USA From: Dennis Conklin Sent: Thursday, August 20, 2015 3:52 PM To: Paraview (paraview at paraview.org) Subject: How to find the nearest quad element? All, I have an Exodus, multi-block model. Most of the blocks are hex elements, and some are layers of quads (tires are composite structures). I would like to establish local strains which are oriented in the direction of the nearest quad layer. To do this I need to identify, for each hex in the model, which quad element in the model is closest to the hex. Then I can extract directions from the quad element and rotate the strain tensor in the hex to these local coordinates. My question is, is there some clever and efficient way to quickly determine the nearest quad for each hex in the model. Keep in mind that there are multiple blocks of quads, but if there is some way to address the quad blocks one at a time, I could make this work. The brute force way is: Loop over every hex in the model: Loop over every quad in the model: Calculate the distance between hex and quad Smallest distance wins! That is a pretty brutally inefficient calc (several million hex elements) that I am trying to avoid ? any ideas about how best to approach this. I?m hoping for some elegant way to use connectivity or something of that sort. Thanks for looking Dennis _______________________________________________ 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: From nawijn at gmail.com Tue Aug 25 11:26:02 2015 From: nawijn at gmail.com (Marco Nawijn) Date: Tue, 25 Aug 2015 17:26:02 +0200 Subject: [Paraview] [EXT] Re: How to find the nearest quad element? In-Reply-To: References: Message-ID: Hi Dennis, That timeframe is ok for me. Marco On Tue, Aug 25, 2015 at 5:24 PM, Dennis Conklin wrote: > Marco, > > > > I am actually tied up for the next week or so, so if you can post a sample > in that timeframe that would be perfect. > > > > Thanks very much > > > > Dennis > > > > *From:* Marco Nawijn [mailto:nawijn at gmail.com] > *Sent:* Tuesday, August 25, 2015 11:21 AM > *To:* Dennis Conklin > *Cc:* Paraview (paraview at paraview.org) > *Subject:* Re: [EXT] Re: [Paraview] How to find the nearest quad element? > > > > Hi Dennis, > > > > You might also be interested in the vtkCellCenters filter. As the name > suggests, it > > will generate the centers of the cells for you. If you are not in a big > rush, I can build > > you a small self contained sample in Python that demonstrates the filter > and the > > use of the point locator. I am a little busy at the moment, but I can post > the sample > > in a couple of days. > > > > Marco > > > > > > On Tue, Aug 25, 2015 at 1:40 PM, Dennis Conklin < > dennis_conklin at goodyear.com> wrote: > > Marco, > > > > Thanks for that tip ? I?m not very familiar with vtk and I?ve never heard > of that class but it seems appropriate so I will try to dig into it. > > > > Thanks again > > > > Dennis > > > > *From:* Marco Nawijn [mailto:nawijn at gmail.com] > *Sent:* Monday, August 24, 2015 10:28 AM > *To:* Dennis Conklin > *Cc:* Paraview (paraview at paraview.org) > *Subject:* [EXT] Re: [Paraview] How to find the nearest quad element? > > > > What about the following: > > > > Generate two additional datasets, one containing (an approximate of) the > center of the hex elements, the second the center of the quads. Then create > a vtkKdTreePointLocator object based on the center points of the quad > elements. Than loop over the centers of the hex elements and use one of the > Find* methods to get the closest quad. > > > > Marco > > > > > > > > > > On Fri, Aug 21, 2015 at 2:21 PM, Dennis Conklin < > dennis_conklin at goodyear.com> wrote: > > Sam, > > Thanks for responding. You have helped me several times in the past and I > am always grateful for your insights. In this case there is considerable > refinement in the model, so only a very small portion of the hex elements > are in immediate contact with quads. Also you could think of places like > the tread in the tire where there is no reinforcement whatsoever. > > Another approach which I have considered is a wave propagation technique, > where in the first wave every hex immediately adjacent to a quad gets > direction cosines assigned (as you suggest). Then you loop thru the > remaining elements and assign cosines from any adjacent quad or hex that > has cosines. Eventually the direction cosines will propagate throughout > the model. A major complication is that wavefronts will collide and then > you will have to choose which of several conflicting neighbor cosines to > adopt. Averaging is one approach but certain structures give adjoining > cosines which are 180 degrees reversed, so averaging would give you an > indeterminate direction. > > I am toying now with some pseudo-variables, such as combinations of radius > and lateral location, combined with zoning, to try to find a quantity that > is unique for a local section of the geometry, to reduce the search size > for each hex element. > > I am still hoping for a very clever scheme which someone may suggest > before I proceed with these much more brute force methods. > > Dennis > > > > *Sam Key Wrote:* > > *Dennis, * > > *Assuming for the moment that each quad 4-tuple is a finite element that > contains one or more tire reinforcement items, and that each quad 4-tuple > is "sandwiched" in between two hex 8-node finite elements, then the quad's > 4-tuple is also a surface facet of two different 8-node hexahedrons. Both > hexhedrons are the 'closest' hexhedrons to the quad. Given the usual > organization of 'element blocks' in the Exodus-II datum structures, the two > closest hexahedrons will be located on the surface of their respective > element blocks. * > > *Using material ID's which are also element block ID's, have the software > generate surface side-sets for each of these two element blocks specified > with these two material ID's. With luck, each member in the side-set will > be specified as a 2-tuple, (Elem# in the block, Quad-Face# in the hexah) * > > *With his info, you can confine your search to finding the side-set item > that has a 4-tuple that matches your quad's 4-tuple. The search is reduced > to a relatively small collection of hexahedral surface 4-tuple faces. * > > *Hope this helps. * > > *Samuel W Key FMA Development, LLC 1005 39th Ave NE Great Falls, Montana > 59404 USA * > > > > > > *From:* Dennis Conklin > *Sent:* Thursday, August 20, 2015 3:52 PM > *To:* Paraview (paraview at paraview.org) > *Subject:* How to find the nearest quad element? > > > > All, > > > > I have an Exodus, multi-block model. Most of the blocks are hex elements, > and some are layers of quads (tires are composite structures). I would > like to establish local strains which are oriented in the direction of the > nearest quad layer. To do this I need to identify, for each hex in the > model, which quad element in the model is closest to the hex. Then I can > extract directions from the quad element and rotate the strain tensor in > the hex to these local coordinates. > > > > My question is, is there some clever and efficient way to quickly > determine the nearest quad for each hex in the model. Keep in mind that > there are multiple blocks of quads, but if there is some way to address the > quad blocks one at a time, I could make this work. > > > > The brute force way is: > > Loop over every hex in the model: > > Loop over every quad in the model: > > Calculate the distance between hex and quad > > Smallest distance wins! > > > > That is a pretty brutally inefficient calc (several million hex elements) > that I am trying to avoid ? any ideas about how best to approach this. > I?m hoping for some elegant way to use connectivity or something of that > sort. > > > > Thanks for looking > > > > Dennis > > > _______________________________________________ > 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: From pcxjf1 at nottingham.ac.uk Wed Aug 26 10:49:43 2015 From: pcxjf1 at nottingham.ac.uk (James Furness) Date: Wed, 26 Aug 2015 14:49:43 +0000 Subject: [Paraview] Writing a Paraview Reader - Only part of the data available In-Reply-To: References: <7B8194A7-4FA4-42E8-8A16-9E332B25CA25@exmail.nottingham.ac.uk> <80331877-BCB4-45B1-8194-29671BF0284B@exmail.nottingham.ac.uk> Message-ID: <963888E9-B821-4857-B8A2-52005968F05A@exmail.nottingham.ac.uk> Thanks Dan, I found the problem whilst cleaning up the code to send you a copy. Funny how that happens? It turned out to be an old int extent[6] = {0, 1, 0, 1, 0, 1}; outInfo->Set (vtkStreamingDemandDrivenPipeline::WHOLE_EXTENT(), extent, 6); call in RequestInformation( ? ) that was wrongly setting the extent to [0,1,0,1,0,1]. Fixing that seemed to fix the problem of only 8 points showing up. I?ve been looking now at using the vtkRectilinearGrid class, I?ve set the X, Y and Z coordinates using the respective SetXCoordinates (vtkDataArray *) methods. But I can?t work out from the documentation how to enter my scalar data into this grid for use within paraview. Can you offer any advice on this? Or better point me to an example to learn from? Many thanks, James On 25 Aug 2015, at 15:39, Dan Lipsa > wrote: Hi James, I was used to the old style and it kind of made sense with the problem you are seeing, but you are right, setDimensions does not seem to be the problem. Is it any way I can get the code and a sample data so that I can run it through a debugger. I cannot see anything else in the code. Dan On Tue, Aug 25, 2015 at 9:20 AM, James Furness > wrote: Thanks for your advice, however it hasn?t quite solved my problem. You are missing image->SetDimensions() - that may be a reason why your scalar does not have all values. The documentation marks vtkImageData::SetDimensions( ... ) as depreciated, and instead vtkImageData::SetExtent( ... ) should be used. It remarks that SetDimension is equivalent to SetExtent(0, i-1, 0, j-1, 0, k-1). (( doc page - http://www.vtk.org/doc/nightly/html/classvtkImageData.html#a42bc5faee908c50407e9d9ec97f74238 )) Regardless, I tried using SetDimensions in this way, and resulted in some nasty set-fault crashes. Whilst now 64 elements were found correctly, all passed the first 8 were memory junk. When I use SetExtent( ? ) the information print on the image object happily reports dimensions of 4, 4, 4 as expected. So it seems this is set by SetExtent( ? ). vtkRectilinear grid is like an image data with variable extents and warped grid. I?ll look into this class. It?s possible that I am mangling this reader by trying to shoehorn my problem into an inappropriate class at the moment. Thanks for pointing this out. Many thanks, James On 24 Aug 2015, at 15:31, Dan Lipsa > wrote: James, You are missing image->SetDimensions() - that may be a reason why your scalar does not have all values. vtkRectilinear grid is like an image data with variable extents and warped grid. On Fri, Aug 21, 2015 at 6:55 AM, James Furness > wrote: Hello, I have a program that will produce an output either in csv, or a binary format (which I have written and can alter). The data points are constructed by taking 3 vectors, and stepping at set intervals along these vectors to construct a 3D set of data. Ultimately there shouldn?t be a restriction on the three vectors, so the data may not be in a rectilinear array. But I?m leaving this for now and assuming the data is constructed from 3 orthogonal Axis aligned vectors to create a rectilinear structured grid. When I have a better grasp of preview readers I?ll update the reader to account for this. I guess it would require an unstructured data type to handle non-orthogonal grids? Also, the user is free to select what data they save from the program. This could be many fields, both vector and scalar quantities. What has been selected is stored in a header to the file, and known on reading. For my toy example I save only one scalar quantity. I?ve been trying to write a reader for paraview to import the binary files output. The csv format works ok, but the files can become large and it is a pain to have to construct the vector quantities from 3 scalars in each case, I want to avoid the user having to do this work. Another reason for writing a custom reader is to include additional information into the binary file for visualisation (e.g. the position of atoms, not a field quantity). With that background and reasoning I have managed to follow the documentation enough to read a basic test file, get the origin and point spacing, and read a single scalar quantity into a vtkDataArray owned by a vtkImageData object. Paraview picks this up seemingly correctly, with one flaw: It only takes 2 elements from each dimension, 0 and 1 displaying 8 elements in total. I am confident it has read the other values correctly as the Information tab reports ?X extent 0 to 3? ?X range: -1 to 1? (as expected) and similar for the other dimensions. If I view the data in spreadsheet layout the 8 values it has seem correct, but the others are missing. The code I am using in the reader?s RequestData( ) function is added below. Does anyone know why this may be happening and how to fix it? Also, any advice on how I should structure the reader to handle the non-orthogonal data? Thanks for your time, and thank you for such a stellar program. The results paraview produces for this data is brilliant, hence my want to make it convenient for our users! Regards, James Furness CODE for RequestData( ) Method: ??????????????????????? int LondonReader::RequestData( vtkInformation*, vtkInformationVector**, vtkInformationVector *outputVector) { vtkWarningMacro("Requesting the data!"); ifstream finp; finp.open(this->FileName, ios::in | ios::binary); if (finp.is_open()) { cerr << "File is open without problem!" << endl; } else { cerr << "File failed to open :(" << endl; return 0; } // size of real numbers may not be 8. Check for this from file header int realSize; finp.read((char*)&realSize, sizeof(int)); if(realSize != 8) { cerr << "Not implimented yet!" << endl; return 0; } // number of data fields int nFields; finp.read((char*)&nFields, sizeof(int)); vtkImageData* image = vtkImageData::GetData(outputVector); // Read the dimensions of the grid and set the extent accordingly int gridDim[3]; finp.read((char*)&gridDim, 3*sizeof(int)); int extent[6] = {0, gridDim[0]-1, 0, gridDim[1]-1, 0, gridDim[2]-1}; image->SetExtent(extent); // Read the field names from the file std::vector fields; std::string strBuf; for (int i = 0; i < nFields; i++) { std::getline( finp, strBuf, '\0'); fields.push_back(strBuf); cerr << "Printing Fields (" << i << "): " << fields[i] << endl; } // setup image for only one field for test case image->AllocateScalars(VTK_FLOAT, 1); vtkDataArray* scalars = image->GetPointData()->GetScalars(); // currently there is only one field 'rho' scalars->SetName(fields[3].c_str()); double x, y, z, rho; double oX, oY, oZ; //origin coordinates double sX, sY, sZ; //spacing of points for (vtkIdType itx = 0; itx < gridDim[0]; itx++) { for (vtkIdType ity = 0; ity < gridDim[1]; ity++) { for (vtkIdType itz = 0; itz < gridDim[2]; itz++) { finp.read((char*)&x, realSize); finp.read((char*)&y, realSize); finp.read((char*)&z, realSize); finp.read((char*)&rho, realSize); // Find and set the origin and spacing if (itx == 0 && ity == 0 && itz == 0) { image->SetOrigin(x, y, z); oX = x; oY = y; oZ = z; } else if (itx == 1 && ity == 0 && itz == 0) { sX = x - oX; } else if (itx == 0 && ity == 1 && itz == 0) { sY = y - oY; } else if (itx == 0 && ity == 0 && itz == 1) { sZ = z - oZ; } //check correct read. cerr << x << "," << y << "," << z << "," << rho << ", at " << itx*(gridDim[1]*gridDim[2]) + ity*gridDim[2] + itz << endl; //add value scalars->SetTuple1(itx*gridDim[1]*gridDim[2] + ity*gridDim[2] + itz, rho); } } } image->SetSpacing(sX, sY, sZ); image->Print(cerr); return 1; } This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ 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 This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Aug 26 11:13:26 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 26 Aug 2015 11:13:26 -0400 Subject: [Paraview] Color by array component from Python script not working In-Reply-To: References: Message-ID: Hi Matei, Do your vectors really have up to 672 components? That's fine, just surprisingly high. Changing among vector components seems to be working fine in ParaView 4.3.1 On Windows. Here is the test script I ran. #### import the simple module from the paraview from paraview.simple import * #### disable automatic camera reset on 'Show' paraview.simple._DisableFirstRenderCameraReset() # create a new 'Sphere' sphere1 = Sphere() # get active view renderView1 = GetActiveViewOrCreate('RenderView') # uncomment following to set a specific view size # renderView1.ViewSize = [659, 468] # show data in view sphere1Display = Show(sphere1, renderView1) # trace defaults for the display properties. sphere1Display.ColorArrayName = [None, ''] # reset view to fit data renderView1.ResetCamera() # set scalar coloring ColorBy(sphere1Display, ('POINTS', 'Normals')) # rescale color and/or opacity maps used to include current data range sphere1Display.RescaleTransferFunctionToDataRange(True) # show color bar/color legend sphere1Display.SetScalarBarVisibility(renderView1, True) # get color transfer function/color map for 'Normals' normalsLUT = GetColorTransferFunction('Normals') # get opacity transfer function/opacity map for 'Normals' normalsPWF = GetOpacityTransferFunction('Normals') #change array component used for coloring normalsLUT.RGBPoints = [-0.9749279022216797, 0.231373, 0.298039, 0.752941, 0.0, 0.865003, 0.865003, 0.865003, 0.9749279022216797, 0.705882, 0.0156863, 0.14902] normalsLUT.VectorMode = 'Component' # Properties modified on normalsPWF normalsPWF.Points = [-0.9749279022216797, 0.0, 0.5, 0.0, 0.9749279022216797, 1.0, 0.5, 0.0] normalsLUT.VectorComponent = 0 RenderAllViews() SaveScreenshot('component0.png') #change array component used for coloring normalsLUT.VectorComponent = 1 RenderAllViews() SaveScreenshot('component1.png') #change array component used for coloring normalsLUT.RGBPoints = [-1.0, 0.231373, 0.298039, 0.752941, 0.0, 0.865003, 0.865003, 0.865003, 1.0, 0.705882, 0.0156863, 0.14902] normalsLUT.VectorComponent = 2 RenderAllViews() SaveScreenshot('component2.png') # Properties modified on normalsPWF normalsPWF.Points = [-1.0, 0.0, 0.5, 0.0, 1.0, 1.0, 0.5, 0.0] #### saving camera placements for all active views # current camera placement for renderView1 renderView1.CameraPosition = [0.0, 0.0, 3.2903743041222895] renderView1.CameraParallelScale = 0.8516115354228021 #### uncomment the following to render all views RenderAllViews() # alternatively, if you want to write images, you can use SaveScreenshot(...). Can you confirm this works on your ParaView installation? There might be some errors about file writing if the current working directory on your system is write-protected - you can ignore those. Cheers, Cory On Thu, Aug 20, 2015 at 6:54 PM, Matei Stroila wrote: > Hi, > > I am using ParaView 4.3.1 on Mac OSX. > I used to be able to loop through the components of an attribute array and > change the color of the representation. I am not sure why this is no longer > working (don't recall when it was working, maybe 4.2?). It does work from > GUI. This is the GUI trace for changing the color attribute three times: > > #### import the simple module from the paraview > > from paraview.simple import * > > #### disable automatic camera reset on 'Show' > > paraview.simple._DisableFirstRenderCameraReset() > > > # get color transfer function/color map for 'SpeedArray' > > speedArrayLUT = GetColorTransferFunction('SpeedArray') > > speedArrayLUT.InterpretValuesAsCategories = 0 > > speedArrayLUT.EnableOpacityMapping = 0 > > speedArrayLUT.RGBPoints = [0.0, 1.0, 0.0, 0.0, 150.0, 0.0, 0.0, 1.0] > > speedArrayLUT.UseLogScale = 0 > > speedArrayLUT.LockScalarRange = 1 > > speedArrayLUT.ColorSpace = 'HSV' > > speedArrayLUT.UseBelowRangeColor = 0 > > speedArrayLUT.BelowRangeColor = [0.0, 0.0, 0.0] > > speedArrayLUT.UseAboveRangeColor = 0 > > speedArrayLUT.AboveRangeColor = [1.0, 1.0, 1.0] > > speedArrayLUT.NanColor = [0.498039, 0.498039, 0.498039] > > speedArrayLUT.Discretize = 1 > > speedArrayLUT.NumberOfTableValues = 256 > > speedArrayLUT.ScalarRangeInitialized = 1.0 > > speedArrayLUT.HSVWrap = 0 > > speedArrayLUT.VectorComponent = 96 > > speedArrayLUT.VectorMode = 'Component' > > speedArrayLUT.AllowDuplicateScalars = 1 > > speedArrayLUT.Annotations = [] > > speedArrayLUT.IndexedColors = [] > > > # get opacity transfer function/opacity map for 'SpeedArray' > > speedArrayPWF = GetOpacityTransferFunction('SpeedArray') > > speedArrayPWF.Points = [0.0, 0.0, 0.5, 0.0, 150.0, 1.0, 0.5, 0.0] > > speedArrayPWF.AllowDuplicateScalars = 1 > > speedArrayPWF.ScalarRangeInitialized = 1 > > > #change array component used for coloring > > speedArrayLUT.RGBPoints = [2.0, 1.0, 0.0, 0.0, 134.079086144, 0.0, 0.0, 1.0] > > speedArrayLUT.VectorComponent = 111 > > > # Properties modified on speedArrayPWF > > speedArrayPWF.Points = [2.0, 0.0, 0.5, 0.0, 134.079086144, 1.0, 0.5, 0.0] > > > #change array component used for coloring > > speedArrayLUT.RGBPoints = [2.0, 1.0, 0.0, 0.0, 131.302099153, 0.0, 0.0, 1.0] > > speedArrayLUT.VectorComponent = 127 > > > # Properties modified on speedArrayPWF > > speedArrayPWF.Points = [2.0, 0.0, 0.5, 0.0, 131.302099153, 1.0, 0.5, 0.0] > > > #change array component used for coloring > > speedArrayLUT.RGBPoints = [2.0, 1.0, 0.0, 0.0, 143.468496117, 0.0, 0.0, 1.0] > > speedArrayLUT.VectorComponent = 175 > > > # Properties modified on speedArrayPWF > > speedArrayPWF.Points = [2.0, 0.0, 0.5, 0.0, 143.468496117, 1.0, 0.5, 0.0] > > > #### uncomment the following to render all views > > # RenderAllViews() > > # alternatively, if you want to write images, you can use SaveScreenshot(...). > > > I try to do the same from a script, this time keeping the color map the > same (not rescaling), and that does not work, the color of the geometry > stays the same: > > ############### > > *speedArrayLUT = GetColorTransferFunction('SpeedArray')* > *speedArrayLUT.RGBPoints = [0.0, 1.0, 0.0, 0.0, 150.0, 0.0, 0.0, 1.0]* > *speedArrayLUT.LockScalarRange = 1* > *speedArrayLUT.ColorSpace = 'HSV'* > *speedArrayLUT.NanColor = [0.498039, 0.498039, 0.498039]* > *speedArrayLUT.ScalarRangeInitialized = 1.0* > *speedArrayLUT.VectorComponent = 671* > *speedArrayLUT.VectorMode = 'Component'* > > *speedArrayPWF = GetOpacityTransferFunction('SpeedArray')* > *speedArrayPWF.Points = [0.0, 0.0, 0.5, 0.0, 150.0, 1.0, 0.5, 0.0]* > *speedArrayPWF.ScalarRangeInitialized = 1* > > *attributesLUTColorBar = GetScalarBar(speedArrayLUT, renderView1)* > *attributesLUTColorBar.Title = 'Speed (km/h)'* > > *for i in range_15min: * > > * speedArrayLUT.VectorComponent = i* > * Render()* > ################# > > If I add: > > *readerDisplay.RescaleTransferFunctionToDataRange() * > > in the loop, I do see the range of the color bar changing with each > iteration, but the color of the rendered geometry does not change. Is there > a way to force an update on the readerDisplay (where, *readerDisplay = > GetDisplayProperties(reader, view=renderView1)*) > > Thanks for any suggestions. > > Matei > > > > > _______________________________________________ > 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: From matei.stroila at gmail.com Wed Aug 26 11:58:36 2015 From: matei.stroila at gmail.com (Matei Stroila) Date: Wed, 26 Aug 2015 15:58:36 +0000 Subject: [Paraview] Color by array component from Python script not working In-Reply-To: References: Message-ID: Hi Cory, Yes, your script works on my machine. Then, after testing your script, I deleted my ParaView4.3.1.ini file and now my script works too :-) Not sure what happened. Yes I have a vector with that many components for a time animation. Thanks for your attention. Best, Matei On Wed, Aug 26, 2015 at 10:13 AM Cory Quammen wrote: > Hi Matei, > > Do your vectors really have up to 672 components? That's fine, just > surprisingly high. > > Changing among vector components seems to be working fine in ParaView > 4.3.1 On Windows. Here is the test script I ran. > > #### import the simple module from the paraview > from paraview.simple import * > #### disable automatic camera reset on 'Show' > paraview.simple._DisableFirstRenderCameraReset() > > # create a new 'Sphere' > sphere1 = Sphere() > > # get active view > renderView1 = GetActiveViewOrCreate('RenderView') > # uncomment following to set a specific view size > # renderView1.ViewSize = [659, 468] > > # show data in view > sphere1Display = Show(sphere1, renderView1) > # trace defaults for the display properties. > sphere1Display.ColorArrayName = [None, ''] > > # reset view to fit data > renderView1.ResetCamera() > > # set scalar coloring > ColorBy(sphere1Display, ('POINTS', 'Normals')) > > # rescale color and/or opacity maps used to include current data range > sphere1Display.RescaleTransferFunctionToDataRange(True) > > # show color bar/color legend > sphere1Display.SetScalarBarVisibility(renderView1, True) > > # get color transfer function/color map for 'Normals' > normalsLUT = GetColorTransferFunction('Normals') > > # get opacity transfer function/opacity map for 'Normals' > normalsPWF = GetOpacityTransferFunction('Normals') > > #change array component used for coloring > normalsLUT.RGBPoints = [-0.9749279022216797, 0.231373, 0.298039, 0.752941, > 0.0, 0.865003, 0.865003, 0.865003, 0.9749279022216797, 0.705882, 0.0156863, > 0.14902] > normalsLUT.VectorMode = 'Component' > > # Properties modified on normalsPWF > normalsPWF.Points = [-0.9749279022216797, 0.0, 0.5, 0.0, > 0.9749279022216797, 1.0, 0.5, 0.0] > > normalsLUT.VectorComponent = 0 > RenderAllViews() > SaveScreenshot('component0.png') > > #change array component used for coloring > normalsLUT.VectorComponent = 1 > RenderAllViews() > SaveScreenshot('component1.png') > > #change array component used for coloring > normalsLUT.RGBPoints = [-1.0, 0.231373, 0.298039, 0.752941, 0.0, 0.865003, > 0.865003, 0.865003, 1.0, 0.705882, 0.0156863, 0.14902] > normalsLUT.VectorComponent = 2 > RenderAllViews() > SaveScreenshot('component2.png') > > # Properties modified on normalsPWF > normalsPWF.Points = [-1.0, 0.0, 0.5, 0.0, 1.0, 1.0, 0.5, 0.0] > > #### saving camera placements for all active views > > # current camera placement for renderView1 > renderView1.CameraPosition = [0.0, 0.0, 3.2903743041222895] > renderView1.CameraParallelScale = 0.8516115354228021 > > #### uncomment the following to render all views > RenderAllViews() > # alternatively, if you want to write images, you can use > SaveScreenshot(...). > > Can you confirm this works on your ParaView installation? There might be > some errors about file writing if the current working directory on your > system is write-protected - you can ignore those. > > Cheers, > Cory > > > On Thu, Aug 20, 2015 at 6:54 PM, Matei Stroila > wrote: > >> Hi, >> >> I am using ParaView 4.3.1 on Mac OSX. >> I used to be able to loop through the components of an attribute array >> and change the color of the representation. I am not sure why this is no >> longer working (don't recall when it was working, maybe 4.2?). It does work >> from GUI. This is the GUI trace for changing the color attribute three >> times: >> >> #### import the simple module from the paraview >> >> from paraview.simple import * >> >> #### disable automatic camera reset on 'Show' >> >> paraview.simple._DisableFirstRenderCameraReset() >> >> >> # get color transfer function/color map for 'SpeedArray' >> >> speedArrayLUT = GetColorTransferFunction('SpeedArray') >> >> speedArrayLUT.InterpretValuesAsCategories = 0 >> >> speedArrayLUT.EnableOpacityMapping = 0 >> >> speedArrayLUT.RGBPoints = [0.0, 1.0, 0.0, 0.0, 150.0, 0.0, 0.0, 1.0] >> >> speedArrayLUT.UseLogScale = 0 >> >> speedArrayLUT.LockScalarRange = 1 >> >> speedArrayLUT.ColorSpace = 'HSV' >> >> speedArrayLUT.UseBelowRangeColor = 0 >> >> speedArrayLUT.BelowRangeColor = [0.0, 0.0, 0.0] >> >> speedArrayLUT.UseAboveRangeColor = 0 >> >> speedArrayLUT.AboveRangeColor = [1.0, 1.0, 1.0] >> >> speedArrayLUT.NanColor = [0.498039, 0.498039, 0.498039] >> >> speedArrayLUT.Discretize = 1 >> >> speedArrayLUT.NumberOfTableValues = 256 >> >> speedArrayLUT.ScalarRangeInitialized = 1.0 >> >> speedArrayLUT.HSVWrap = 0 >> >> speedArrayLUT.VectorComponent = 96 >> >> speedArrayLUT.VectorMode = 'Component' >> >> speedArrayLUT.AllowDuplicateScalars = 1 >> >> speedArrayLUT.Annotations = [] >> >> speedArrayLUT.IndexedColors = [] >> >> >> # get opacity transfer function/opacity map for 'SpeedArray' >> >> speedArrayPWF = GetOpacityTransferFunction('SpeedArray') >> >> speedArrayPWF.Points = [0.0, 0.0, 0.5, 0.0, 150.0, 1.0, 0.5, 0.0] >> >> speedArrayPWF.AllowDuplicateScalars = 1 >> >> speedArrayPWF.ScalarRangeInitialized = 1 >> >> >> #change array component used for coloring >> >> speedArrayLUT.RGBPoints = [2.0, 1.0, 0.0, 0.0, 134.079086144, 0.0, 0.0, 1.0] >> >> speedArrayLUT.VectorComponent = 111 >> >> >> # Properties modified on speedArrayPWF >> >> speedArrayPWF.Points = [2.0, 0.0, 0.5, 0.0, 134.079086144, 1.0, 0.5, 0.0] >> >> >> #change array component used for coloring >> >> speedArrayLUT.RGBPoints = [2.0, 1.0, 0.0, 0.0, 131.302099153, 0.0, 0.0, 1.0] >> >> speedArrayLUT.VectorComponent = 127 >> >> >> # Properties modified on speedArrayPWF >> >> speedArrayPWF.Points = [2.0, 0.0, 0.5, 0.0, 131.302099153, 1.0, 0.5, 0.0] >> >> >> #change array component used for coloring >> >> speedArrayLUT.RGBPoints = [2.0, 1.0, 0.0, 0.0, 143.468496117, 0.0, 0.0, 1.0] >> >> speedArrayLUT.VectorComponent = 175 >> >> >> # Properties modified on speedArrayPWF >> >> speedArrayPWF.Points = [2.0, 0.0, 0.5, 0.0, 143.468496117, 1.0, 0.5, 0.0] >> >> >> #### uncomment the following to render all views >> >> # RenderAllViews() >> >> # alternatively, if you want to write images, you can use SaveScreenshot(...). >> >> >> I try to do the same from a script, this time keeping the color map the >> same (not rescaling), and that does not work, the color of the geometry >> stays the same: >> >> ############### >> >> *speedArrayLUT = GetColorTransferFunction('SpeedArray')* >> *speedArrayLUT.RGBPoints = [0.0, 1.0, 0.0, 0.0, 150.0, 0.0, 0.0, 1.0]* >> *speedArrayLUT.LockScalarRange = 1* >> *speedArrayLUT.ColorSpace = 'HSV'* >> *speedArrayLUT.NanColor = [0.498039, 0.498039, 0.498039]* >> *speedArrayLUT.ScalarRangeInitialized = 1.0* >> *speedArrayLUT.VectorComponent = 671* >> *speedArrayLUT.VectorMode = 'Component'* >> >> *speedArrayPWF = GetOpacityTransferFunction('SpeedArray')* >> *speedArrayPWF.Points = [0.0, 0.0, 0.5, 0.0, 150.0, 1.0, 0.5, 0.0]* >> *speedArrayPWF.ScalarRangeInitialized = 1* >> >> *attributesLUTColorBar = GetScalarBar(speedArrayLUT, renderView1)* >> *attributesLUTColorBar.Title = 'Speed (km/h)'* >> >> *for i in range_15min: * >> >> * speedArrayLUT.VectorComponent = i* >> * Render()* >> ################# >> >> If I add: >> >> *readerDisplay.RescaleTransferFunctionToDataRange() * >> >> in the loop, I do see the range of the color bar changing with each >> iteration, but the color of the rendered geometry does not change. Is there >> a way to force an update on the readerDisplay (where, *readerDisplay = >> GetDisplayProperties(reader, view=renderView1)*) >> >> Thanks for any suggestions. >> >> Matei >> >> >> >> >> _______________________________________________ >> 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: From dan.lipsa at kitware.com Wed Aug 26 12:16:06 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Wed, 26 Aug 2015 12:16:06 -0400 Subject: [Paraview] Writing a Paraview Reader - Only part of the data available In-Reply-To: <963888E9-B821-4857-B8A2-52005968F05A@exmail.nottingham.ac.uk> References: <7B8194A7-4FA4-42E8-8A16-9E332B25CA25@exmail.nottingham.ac.uk> <80331877-BCB4-45B1-8194-29671BF0284B@exmail.nottingham.ac.uk> <963888E9-B821-4857-B8A2-52005968F05A@exmail.nottingham.ac.uk> Message-ID: James, Great. I am glad you found the problem. You set scalar data by 1. create and fill a vtkDataArray 2. dataset->GetPointData()->SetScalars(vtkDataArray*) On Wed, Aug 26, 2015 at 10:49 AM, James Furness wrote: > Thanks Dan, > > I found the problem whilst cleaning up the code to send you a copy. Funny > how that happens? > > It turned out to be an old > > int extent[6] = {0, 1, 0, 1, 0, 1}; > outInfo->Set > (vtkStreamingDemandDrivenPipeline::WHOLE_EXTENT(), extent, 6); > > call in RequestInformation( ? ) that was wrongly setting the extent to > [0,1,0,1,0,1]. > > Fixing that seemed to fix the problem of only 8 points showing up. > > I?ve been looking now at using the vtkRectilinearGrid class, I?ve set the > X, Y and Z coordinates using the respective > SetXCoordinates (vtkDataArray *) methods. But I can?t work out from the > documentation how to enter my scalar data into this grid for use within > paraview. > > Can you offer any advice on this? Or better point me to an example to > learn from? > > Many thanks, > James > > On 25 Aug 2015, at 15:39, Dan Lipsa wrote: > > Hi James, > I was used to the old style and it kind of made sense with the problem you > are seeing, but you are right, setDimensions does not seem to be the > problem. > > Is it any way I can get the code and a sample data so that I can run it > through a debugger. I cannot see anything else in the code. > > Dan > > > On Tue, Aug 25, 2015 at 9:20 AM, James Furness > wrote: > >> Thanks for your advice, however it hasn?t quite solved my problem. >> >> You are missing image->SetDimensions() - that may be a reason why your >> scalar does not have all values. >> >> >> The documentation marks vtkImageData::SetDimensions( ... ) as >> depreciated, and instead vtkImageData::SetExtent( ... ) should be used. It >> remarks that SetDimension is equivalent to SetExtent(0, i-1, 0, j-1, 0, >> k-1). >> >> (( doc page - >> http://www.vtk.org/doc/nightly/html/classvtkImageData.html#a42bc5faee908c50407e9d9ec97f74238 >> )) >> >> Regardless, I tried using SetDimensions in this way, and resulted in some >> nasty set-fault crashes. Whilst now 64 elements were found correctly, all >> passed the first 8 were memory junk. When I use SetExtent( ? ) the >> information print on the image object happily reports dimensions of 4, 4, 4 >> as expected. So it seems this is set by SetExtent( ? ). >> >> vtkRectilinear grid is like an image data with variable extents and >> warped grid. >> >> >> I?ll look into this class. It?s possible that I am mangling this reader >> by trying to shoehorn my problem into an inappropriate class at the moment. >> Thanks for pointing this out. >> >> Many thanks, >> James >> >> On 24 Aug 2015, at 15:31, Dan Lipsa wrote: >> >> James, >> You are missing image->SetDimensions() - that may be a reason why your >> scalar does not have all values. >> >> vtkRectilinear grid is like an image data with variable extents and >> warped grid. >> >> >> On Fri, Aug 21, 2015 at 6:55 AM, James Furness >> wrote: >> >>> Hello, >>> >>> I have a program that will produce an output either in csv, or a binary >>> format (which I have written and can alter). >>> >>> The data points are constructed by taking 3 vectors, and stepping at set >>> intervals along these vectors to construct a 3D set of data. Ultimately >>> there shouldn?t be a restriction on the three vectors, so the data may not >>> be in a rectilinear array. But I?m leaving this for now and assuming the >>> data is constructed from 3 orthogonal Axis aligned vectors to create a >>> rectilinear structured grid. When I have a better grasp of preview readers >>> I?ll update the reader to account for this. I guess it would require an >>> unstructured data type to handle non-orthogonal grids? >>> >>> Also, the user is free to select what data they save from the program. >>> This could be many fields, both vector and scalar quantities. What has been >>> selected is stored in a header to the file, and known on reading. For my >>> toy example I save only one scalar quantity. >>> >>> I?ve been trying to write a reader for paraview to import the binary >>> files output. The csv format works ok, but the files can become large and >>> it is a pain to have to construct the vector quantities from 3 scalars in >>> each case, I want to avoid the user having to do this work. Another reason >>> for writing a custom reader is to include additional information into the >>> binary file for visualisation (e.g. the position of atoms, not a field >>> quantity). >>> >>> With that background and reasoning I have managed to follow the >>> documentation enough to read a basic test file, get the origin and point >>> spacing, and read a single scalar quantity into a vtkDataArray owned by a >>> vtkImageData object. Paraview picks this up seemingly correctly, with one >>> flaw: >>> >>> It only takes 2 elements from each dimension, 0 and 1 displaying 8 >>> elements in total. I am confident it has read the other values correctly as >>> the Information tab reports ?X extent 0 to 3? ?X range: -1 to 1? (as >>> expected) and similar for the other dimensions. If I view the data in >>> spreadsheet layout the 8 values it has seem correct, but the others are >>> missing. >>> >>> The code I am using in the reader?s RequestData( ) function is added >>> below. >>> >>> Does anyone know why this may be happening and how to fix it? Also, any >>> advice on how I should structure the reader to handle the non-orthogonal >>> data? >>> >>> Thanks for your time, and thank you for such a stellar program. The >>> results paraview produces for this data is brilliant, hence my want to make >>> it convenient for our users! >>> >>> Regards, >>> James Furness >>> >>> >>> CODE for RequestData( ) Method: >>> ??????????????????????? >>> >>> int LondonReader::RequestData( >>> vtkInformation*, >>> vtkInformationVector**, >>> vtkInformationVector *outputVector) >>> { >>> vtkWarningMacro("Requesting the data!"); >>> >>> >>> ifstream finp; >>> finp.open(this->FileName, ios::in | ios::binary); >>> >>> if (finp.is_open()) { >>> cerr << "File is open without problem!" << endl; >>> } else { >>> cerr << "File failed to open :(" << endl; >>> return 0; >>> } >>> >>> // size of real numbers may not be 8. Check for this from file header >>> int realSize; >>> finp.read((char*)&realSize, sizeof(int)); >>> if(realSize != 8) { >>> cerr << "Not implimented yet!" << endl; >>> return 0; >>> } >>> >>> // number of data fields >>> int nFields; >>> finp.read((char*)&nFields, sizeof(int)); >>> >>> vtkImageData* image = vtkImageData::GetData(outputVector); >>> >>> // Read the dimensions of the grid and set the extent accordingly >>> int gridDim[3]; >>> finp.read((char*)&gridDim, 3*sizeof(int)); >>> int extent[6] = {0, gridDim[0]-1, 0, gridDim[1]-1, 0, gridDim[2]-1}; >>> image->SetExtent(extent); >>> >>> >>> // Read the field names from the file >>> std::vector fields; >>> std::string strBuf; >>> for (int i = 0; i < nFields; i++) { >>> std::getline( finp, strBuf, '\0'); >>> fields.push_back(strBuf); >>> cerr << "Printing Fields (" << i << "): " << fields[i] << endl; >>> } >>> >>> // setup image for only one field for test case >>> image->AllocateScalars(VTK_FLOAT, 1); >>> vtkDataArray* scalars = image->GetPointData()->GetScalars(); >>> >>> // currently there is only one field 'rho' >>> scalars->SetName(fields[3].c_str()); >>> >>> double x, y, z, rho; >>> double oX, oY, oZ; //origin coordinates >>> double sX, sY, sZ; //spacing of points >>> >>> for (vtkIdType itx = 0; itx < gridDim[0]; itx++) { >>> for (vtkIdType ity = 0; ity < gridDim[1]; ity++) { >>> for (vtkIdType itz = 0; itz < gridDim[2]; itz++) { >>> finp.read((char*)&x, realSize); >>> finp.read((char*)&y, realSize); >>> finp.read((char*)&z, realSize); >>> finp.read((char*)&rho, realSize); >>> >>> // Find and set the origin and spacing >>> if (itx == 0 && ity == 0 && itz == 0) { >>> image->SetOrigin(x, y, z); >>> oX = x; oY = y; oZ = z; >>> } else if (itx == 1 && ity == 0 && itz == 0) { >>> sX = x - oX; >>> } else if (itx == 0 && ity == 1 && itz == 0) { >>> sY = y - oY; >>> } else if (itx == 0 && ity == 0 && itz == 1) { >>> sZ = z - oZ; >>> } >>> //check correct read. >>> cerr << x << "," << y << "," << z << "," << rho << ", at >>> " << itx*(gridDim[1]*gridDim[2]) + ity*gridDim[2] + itz << endl; >>> >>> //add value >>> scalars->SetTuple1(itx*gridDim[1]*gridDim[2] + >>> ity*gridDim[2] + itz, >>> rho); >>> } >>> } >>> } >>> >>> image->SetSpacing(sX, sY, sZ); >>> >>> image->Print(cerr); >>> >>> return 1; >>> } >>> >>> >>> >>> >>> >>> This message and any attachment are intended solely for the addressee >>> and may contain confidential information. If you have received this >>> message in error, please send it back to me, and immediately delete it. >>> >>> Please do not use, copy or disclose the information contained in this >>> message or in any attachment. Any views or opinions expressed by the >>> author of this email do not necessarily reflect the views of the >>> University of Nottingham. >>> >>> This message has been checked for viruses but the contents of an >>> attachment may still contain software viruses which could damage your >>> computer system, you are advised to perform your own checks. Email >>> communications with the University of Nottingham may be monitored as >>> permitted by UK legislation. >>> >>> _______________________________________________ >>> 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 >>> >> >> >> This message and any attachment are intended solely for the addressee >> and may contain confidential information. If you have received this >> message in error, please send it back to me, and immediately delete it. >> >> Please do not use, copy or disclose the information contained in this >> message or in any attachment. Any views or opinions expressed by the >> author of this email do not necessarily reflect the views of the >> University of Nottingham. >> >> This message has been checked for viruses but the contents of an >> attachment may still contain software viruses which could damage your >> computer system, you are advised to perform your own checks. Email >> communications with the University of Nottingham may be monitored as >> permitted by UK legislation. >> >> > > > > This message and any attachment are intended solely for the addressee > and may contain confidential information. If you have received this > message in error, please send it back to me, and immediately delete it. > > Please do not use, copy or disclose the information contained in this > message or in any attachment. Any views or opinions expressed by the > author of this email do not necessarily reflect the views of the > University of Nottingham. > > This message has been checked for viruses but the contents of an > attachment may still contain software viruses which could damage your > computer system, you are advised to perform your own checks. Email > communications with the University of Nottingham may be monitored as > permitted by UK legislation. > > > _______________________________________________ > 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: From dennis_conklin at goodyear.com Wed Aug 26 12:52:52 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Wed, 26 Aug 2015 16:52:52 +0000 Subject: [Paraview] How to Tell if Apply Displacements checked and Displacement Magnitude for Exodus multi-block dataset from Programmable filter Message-ID: All, Let's say I load an Exodus file with a multi-block dataset. At that time I either Apply Displacements or not and I can change the default Displacement Magnitude of 1. Then I want to run a Programmable filter. In that filter, I want to take different actions depending on Apply Displacements and Displacement Magnitude. I sort of have 2 questions: 1. Is it possible to determine the state of Apply Displacements and Displacement Magnitude if I run the programmable filter directly on the exodus file, immediately after loading it? 2. If I am further down the Pipeline Browser and I run it on a descendent of the exodus file, possibly with several filters between the original Exodus file and my programmable filter, is there still a way to determine the state of those 2? Thanks for any help. Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Aug 27 10:51:54 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 27 Aug 2015 10:51:54 -0400 Subject: [Paraview] How to Tell if Apply Displacements checked and Displacement Magnitude for Exodus multi-block dataset from Programmable filter In-Reply-To: References: Message-ID: Hi Dennis, 1. Is it possible to determine the state of Apply Displacements and > Displacement Magnitude if I run the programmable filter directly on the > exodus file, immediately after loading it? > Unfortunately, no. The script within the Programmable Filter does not have access to the reader's settings (or anything else in ParaView, for that matter). 2. If I am further down the Pipeline Browser and I run it on a > descendent of the exodus file, possibly with several filters between the > original Exodus file and my programmable filter, is there still a way to > determine the state of those 2? > Again, no. You're best bet might be to create a macro that is essentially a ParaView python script. In this script, you could look for the Exodus reader source and get the value of the ApplyDisplacements property, then modify the Programmable Filter Script text accordingly. When you import the script as a macro, you can apply it by selecting it from the Macros menu. HTH, Cory > Thanks for any help. > > > > Dennis > > _______________________________________________ > 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: From berk.geveci at kitware.com Thu Aug 27 12:40:04 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Thu, 27 Aug 2015 12:40:04 -0400 Subject: [Paraview] VTK and ParaView for HPCWire awards! Message-ID: VTK and ParaView have witnessed significant growth thanks to all of the members of the community. To recognize VTK and ParaView?s development, please nominate them for 2015 HPCwire Readers? and Editors? Choice Awards. Please nominate VTK and ParaView for ?Best HPC Visualization Product or Technology.? Nominations can be made at http://www.hpcwire.com/2015-hpcwire-readers-choice-awards/. Thank you for your support! -berk -------------- next part -------------- An HTML attachment was scrubbed... URL: From dennis_conklin at goodyear.com Fri Aug 28 16:13:42 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Fri, 28 Aug 2015 20:13:42 +0000 Subject: [Paraview] Exodus Block Names Message-ID: All, Once again, I need help. We are starting to assign names to our Exodus blocks (outside of Paraview). This is very useful for ease and clarity of post processing and allows convenient reference to actual components. The good news is that Paraview seems perfectly happy to read in the Block Names and use them in the Properties Panel and the Multi-block Inspector and the Find Data screen if they exist (no action or programming required for this). So, for instance, instead of Paraview generating the non-useful name of "Unnamed block ID: 13 Type: hex" when the blockname is empty, it will automagically use the more useful Blockname of "Tread" if that is in the Exodus file. However, there has been an unintended consequence of this change. If I select some elements and examine them in Spreadsheet View, I see Block Number 14( the +1 offset from Block_ID and Block Number is NOT the problem!). And now I can no longer associate the element (Block Number 14) with it's block in the Properties Panel or the Multi-block Inspector or the Find Data panel - where the same block is called "Tread". So, to remedy this situation I would like to add an element variable of BlockName, which would contain "Tread" for all the elements in BlockID 13, etc., etc. for all the blocks. My only problem is I can't seem to find the list of Block Names. I'm pretty weak at vtk, so it must be available but I surrender - I can't seem to find it. If someone can help me find the list of Block Names from inside the Programmable Filter, I'll be happy to add the element variable myself. Thanks for any help, again! Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Fri Aug 28 16:44:07 2015 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Fri, 28 Aug 2015 16:44:07 -0400 Subject: [Paraview] Exodus Block Names In-Reply-To: References: Message-ID: Hi Dennis, The block name is in the block metadata, which is not where I looked the first time either. Here is a code snippet that shows how to access it. mb = vtk.vtkMultiBlockDataSet() ... for i in range(mb.GetNumberOfBlocks): metadata = mb.GetMetaData(i) name = metadata.Get(vtk.vtkCompositeDataSet.NAME()) HTH, Shawn On Fri, Aug 28, 2015 at 4:13 PM, Dennis Conklin wrote: > All, > > > > Once again, I need help. We are starting to assign names to our Exodus > blocks (outside of Paraview). This is very useful for ease and clarity of > post processing and allows convenient reference to actual components. The > good news is that Paraview seems perfectly happy to read in the Block Names > and use them in the Properties Panel and the Multi-block Inspector and the > Find Data screen if they exist (no action or programming required for > this). So, for instance, instead of Paraview generating the non-useful > name of ?Unnamed block ID: 13 Type: hex? when the blockname is empty, it > will automagically use the more useful Blockname of ?Tread? if that is in > the Exodus file. > > > > However, there has been an unintended consequence of this change. If I > select some elements and examine them in Spreadsheet View, I see Block > Number 14( the +1 offset from Block_ID and Block Number is NOT the > problem!). And now I can no longer associate the element (Block Number > 14) with it?s block in the Properties Panel or the Multi-block Inspector or > the Find Data panel ? where the same block is called ?Tread?. > > > > So, to remedy this situation I would like to add an element variable of > BlockName, which would contain ?Tread? for all the elements in BlockID 13, > etc., etc. for all the blocks. > > > > My only problem is I can?t seem to find the list of Block Names. I?m > pretty weak at vtk, so it must be available but I surrender ? I can?t seem > to find it. If someone can help me find the list of Block Names from > inside the Programmable Filter, I?ll be happy to add the element variable > myself. > > > > Thanks for any help, again! > > > > Dennis > > _______________________________________________ > 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: From stephen.wornom at inria.fr Sat Aug 29 03:39:29 2015 From: stephen.wornom at inria.fr (Stephen Wornom) Date: Sat, 29 Aug 2015 09:39:29 +0200 (CEST) Subject: [Paraview] PV 4.1.0 how to plot over line for two different time step on same figure In-Reply-To: <2025517584.14036153.1440833898346.JavaMail.zimbra@inria.fr> Message-ID: <1513416284.14036329.1440833969840.JavaMail.zimbra@inria.fr> Plot ove line creates a figure. Is it possible to impose two different time steps on the same figure? Hope my question is clear. Thanks, Stephen -------------- next part -------------- An HTML attachment was scrubbed... URL: From sergi.mateo.bellido at gmail.com Mon Aug 31 03:27:23 2015 From: sergi.mateo.bellido at gmail.com (Sergi Mateo Bellido) Date: Mon, 31 Aug 2015 09:27:23 +0200 Subject: [Paraview] [BUG] segfault playing a simulation In-Reply-To: <55CB402B.10300@gmail.com> References: <55895735.2030202@gmail.com> <559422EF.3070304@gmail.com> <55A0E2AE.5050101@gmail.com> <55A9056C.2000101@gmail.com> <55A90F76.8000804@gmail.com> <55B20445.7060809@gmail.com> <55BE4829.5030209@gmail.com> <55C989A6.7060809@gmail.com> <55CADDE1.7010309@gmail.com> <55CB402B.10300@gmail.com> Message-ID: <55E401DB.5030007@gmail.com> Hi Cory, I'm stuck with this issue :( 1. Changing just the pvti file is not enough: I got a segfault using the raw binary files. 2. I tried also adding a dummy slice at the end of all pieces to fix the problem that I reported in one of my previous emails. So, instead of changing the PVTI files I tried changing the VTI files. 2.1. First of all, I had to increase the number of tuples of the VtkArray because I was adding the dummy slice. Since I didn't change the whole extent and the piece extent of each VTI file, I got this warning message: Warning: In /opt/VTK-6.2.0/Common/DataModel/vtkDataSet.cxx, line 421 vtkImageData (0x3450390): Point array Var with 1 components, has 4080501 tuples but there are only 4040100 points This didn't work either. 2.2. Afterwards, I tried modifying also the whole extent and the piece extent. This seemed to work :) Despite 2.2 seemed to work, I'm not sure if this is a valid solution or just a workaround: If I open a VTI file directly (because I want to see the data produced by a MPI process) the dummy slice is visualized. From my point of view, I think that we're trying to address an issue of the PVTI format modifying something that works fine (VTI files). Best regards, Sergi On 08/12/2015 02:46 PM, Sergi Mateo Bellido wrote: > Cory, > > I did not change the VTI files in the first experiment but it crashed > anyway. > > Thanks! > Sergi > > On 08/12/2015 01:55 PM, Cory Quammen wrote: >> Sergi, >> >> Note that I did *not* change the whole extents of the VTI files after >> I changed the listed extents in the PVTI files. >> >> Cory >> >> On Wed, Aug 12, 2015 at 1:47 AM, Sergi Mateo Bellido >> > > wrote: >> >> Cory, >> >> The ascii version is the more stable version and it usually >> doesn't crash (even the original version, I reported that in one >> of my first emails). I tried to different things without >> regenerating the *.vti *.pvti (using the zipped raw version): >> >> 1. Changing the piece extent in all the *.pvti files to what you >> proposed in your last email -> segfault >> 2. Changes describe in 1. + changing the whole extension of the >> VTI files that contain the second piece -> Paraview warns me >> because the size of the second piece doesn't correspond with the >> data. >> >> vtkXMLImageDataReader (0x419ef70): Cannot read point data array >> "var" from PointData in piece 0. The data array in the element >> may be too short. >> >> Following your advice, I will try to generate an extra dummy >> slice in the first piece. I will let you know the results :) >> >> Best, >> Sergi >> >> >> >> On 08/11/2015 11:57 PM, Cory Quammen wrote: >>> Actually, you could try one other thing first: >>> >>> Change the extents of the pieces in the .pvti files to the >>> following: >>> >>> >>> >>> >>> I'm able to load the files and move between time steps fine >>> doing this. >>> >>> Cory >>> >>> On Tue, Aug 11, 2015 at 5:10 PM, Cory Quammen >>> > wrote: >>> >>> Ideally both pieces would contain a copy of the slice, but I >>> think for the first piece you could just write some dummy >>> values into this extra slice. When you load it, the valid >>> values from the first piece will overwrite the dummy values. >>> >>> I'm frankly surprised this extra slice would be needed >>> because the ghost level is set to 0. But I'll admit I don't >>> fully understand this format yet. >>> >>> Cory >>> >>> On Tue, Aug 11, 2015 at 3:37 PM, Sergi Mateo Bellido >>> >> > wrote: >>> >>> Hi Cory, >>> >>> This extra slice is the first slice of the second piece. >>> Should both pieces contain this slice? >>> >>> In my case, each MPI process computes something and >>> writes its portion of the mesh. All these portions are >>> completely disjoint among them. >>> >>> Thanks! >>> Sergi >>> >>> >>> >>> >>> -- >>> 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: tests.tar.gz Type: application/gzip Size: 16409 bytes Desc: not available URL: From dennis_conklin at goodyear.com Mon Aug 31 08:31:10 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Mon, 31 Aug 2015 12:31:10 +0000 Subject: [Paraview] [EXT] Re: Exodus Block Names In-Reply-To: References: Message-ID: Shawn, Thanks for that tip but I can?t seem to access this structure. Really, I need it within the Programmable Filter, but even when I run a Python script and try to find it directly in an Exodus reader, I can?t seem to locate this metadata. If I print dir(ExodusReader), there doesn?t seem to be anything about metadata. Dennis From: Shawn Waldon [mailto:shawn.waldon at kitware.com] Sent: Friday, August 28, 2015 4:44 PM To: Dennis Conklin Cc: Paraview (paraview at paraview.org) Subject: [EXT] Re: [Paraview] Exodus Block Names Hi Dennis, The block name is in the block metadata, which is not where I looked the first time either. Here is a code snippet that shows how to access it. mb = vtk.vtkMultiBlockDataSet() ... for i in range(mb.GetNumberOfBlocks): metadata = mb.GetMetaData(i) name = metadata.Get(vtk.vtkCompositeDataSet.NAME()) HTH, Shawn On Fri, Aug 28, 2015 at 4:13 PM, Dennis Conklin > wrote: All, Once again, I need help. We are starting to assign names to our Exodus blocks (outside of Paraview). This is very useful for ease and clarity of post processing and allows convenient reference to actual components. The good news is that Paraview seems perfectly happy to read in the Block Names and use them in the Properties Panel and the Multi-block Inspector and the Find Data screen if they exist (no action or programming required for this). So, for instance, instead of Paraview generating the non-useful name of ?Unnamed block ID: 13 Type: hex? when the blockname is empty, it will automagically use the more useful Blockname of ?Tread? if that is in the Exodus file. However, there has been an unintended consequence of this change. If I select some elements and examine them in Spreadsheet View, I see Block Number 14( the +1 offset from Block_ID and Block Number is NOT the problem!). And now I can no longer associate the element (Block Number 14) with it?s block in the Properties Panel or the Multi-block Inspector or the Find Data panel ? where the same block is called ?Tread?. So, to remedy this situation I would like to add an element variable of BlockName, which would contain ?Tread? for all the elements in BlockID 13, etc., etc. for all the blocks. My only problem is I can?t seem to find the list of Block Names. I?m pretty weak at vtk, so it must be available but I surrender ? I can?t seem to find it. If someone can help me find the list of Block Names from inside the Programmable Filter, I?ll be happy to add the element variable myself. Thanks for any help, again! Dennis _______________________________________________ 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: From shawn.waldon at kitware.com Mon Aug 31 09:46:03 2015 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Mon, 31 Aug 2015 09:46:03 -0400 Subject: [Paraview] [EXT] Re: Exodus Block Names In-Reply-To: References: Message-ID: Hi Dennis, The metadata is on the reader's output, which is a vtkMultiBlockDataSet. reader.GetOutput() should get you the dataset in your python script. Inside the programmable filter you will need to get the input dataset (self.GetInput() should get you the input dataset and self.GetOutput() should get you the output dataset). So something like the following for your programmable filter: mbi = self.GetInput() mbo = self.GetOutput() mbo.ShallowCopy(mbi) for i in range(mbo.GetNumberOfBlocks()): metadata = mbo.GetMetaData(i) name = metadata.Get(vtk.vtkCompositeDataSet.NAME()) # do something with the name HTH, Shawn On Mon, Aug 31, 2015 at 8:31 AM, Dennis Conklin wrote: > Shawn, > > > > Thanks for that tip but I can?t seem to access this structure. Really, I > need it within the Programmable Filter, but even when I run a Python script > and try to find it directly in an Exodus reader, I can?t seem to locate > this metadata. > > > > If I print dir(ExodusReader), there doesn?t seem to be anything about > metadata. > > Dennis > > > > *From:* Shawn Waldon [mailto:shawn.waldon at kitware.com] > *Sent:* Friday, August 28, 2015 4:44 PM > *To:* Dennis Conklin > *Cc:* Paraview (paraview at paraview.org) > *Subject:* [EXT] Re: [Paraview] Exodus Block Names > > > > Hi Dennis, > > The block name is in the block metadata, which is not where I looked the > first time either. Here is a code snippet that shows how to access it. > > mb = vtk.vtkMultiBlockDataSet() > ... > > for i in range(mb.GetNumberOfBlocks): > > metadata = mb.GetMetaData(i) > > name = metadata.Get(vtk.vtkCompositeDataSet.NAME()) > > HTH, > > Shawn > > > > On Fri, Aug 28, 2015 at 4:13 PM, Dennis Conklin < > dennis_conklin at goodyear.com> wrote: > > All, > > > > Once again, I need help. We are starting to assign names to our Exodus > blocks (outside of Paraview). This is very useful for ease and clarity of > post processing and allows convenient reference to actual components. The > good news is that Paraview seems perfectly happy to read in the Block Names > and use them in the Properties Panel and the Multi-block Inspector and the > Find Data screen if they exist (no action or programming required for > this). So, for instance, instead of Paraview generating the non-useful > name of ?Unnamed block ID: 13 Type: hex? when the blockname is empty, it > will automagically use the more useful Blockname of ?Tread? if that is in > the Exodus file. > > > > However, there has been an unintended consequence of this change. If I > select some elements and examine them in Spreadsheet View, I see Block > Number 14( the +1 offset from Block_ID and Block Number is NOT the > problem!). And now I can no longer associate the element (Block Number > 14) with it?s block in the Properties Panel or the Multi-block Inspector or > the Find Data panel ? where the same block is called ?Tread?. > > > > So, to remedy this situation I would like to add an element variable of > BlockName, which would contain ?Tread? for all the elements in BlockID 13, > etc., etc. for all the blocks. > > > > My only problem is I can?t seem to find the list of Block Names. I?m > pretty weak at vtk, so it must be available but I surrender ? I can?t seem > to find it. If someone can help me find the list of Block Names from > inside the Programmable Filter, I?ll be happy to add the element variable > myself. > > > > Thanks for any help, again! > > > > Dennis > > > _______________________________________________ > 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: From dennis_conklin at goodyear.com Mon Aug 31 10:40:06 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Mon, 31 Aug 2015 14:40:06 +0000 Subject: [Paraview] [EXT] Re: Exodus Block Names In-Reply-To: References: Message-ID: Shawn, Ok, I?m dense. When I run your code inside the Programmable Filter, I see some confusing things: mbi.GetNumberOfBlocks returns 8, which is NOT the number of blocks in my model but IS the number of MetaData blocks. The mbi.GetMetaData[i].Get(vtk.vtkCompositeDataSet.NAME()) then is Value of i Name 0 Element Blocks 1 Face Blocks 2 Edge Blocks 3 Element Sets 4 Side Sets 5 Face Sets 6 Edge Sets 7 Node Sets 8 I am poking around mbi.GetMetaData[0] (Element Blocks) but I still haven?t found any Block Names there. I feel like I am completely missing something here, but I have no idea what it is. Dennis From: Shawn Waldon [mailto:shawn.waldon at kitware.com] Sent: Monday, August 31, 2015 9:46 AM To: Dennis Conklin Cc: Paraview (paraview at paraview.org) Subject: Re: [EXT] Re: [Paraview] Exodus Block Names Hi Dennis, The metadata is on the reader's output, which is a vtkMultiBlockDataSet. reader.GetOutput() should get you the dataset in your python script. Inside the programmable filter you will need to get the input dataset (self.GetInput() should get you the input dataset and self.GetOutput() should get you the output dataset). So something like the following for your programmable filter: mbi = self.GetInput() mbo = self.GetOutput() mbo.ShallowCopy(mbi) for i in range(mbo.GetNumberOfBlocks()): metadata = mbo.GetMetaData(i) name = metadata.Get(vtk.vtkCompositeDataSet.NAME()) # do something with the name HTH, Shawn On Mon, Aug 31, 2015 at 8:31 AM, Dennis Conklin > wrote: Shawn, Thanks for that tip but I can?t seem to access this structure. Really, I need it within the Programmable Filter, but even when I run a Python script and try to find it directly in an Exodus reader, I can?t seem to locate this metadata. If I print dir(ExodusReader), there doesn?t seem to be anything about metadata. Dennis From: Shawn Waldon [mailto:shawn.waldon at kitware.com] Sent: Friday, August 28, 2015 4:44 PM To: Dennis Conklin Cc: Paraview (paraview at paraview.org) Subject: [EXT] Re: [Paraview] Exodus Block Names Hi Dennis, The block name is in the block metadata, which is not where I looked the first time either. Here is a code snippet that shows how to access it. mb = vtk.vtkMultiBlockDataSet() ... for i in range(mb.GetNumberOfBlocks): metadata = mb.GetMetaData(i) name = metadata.Get(vtk.vtkCompositeDataSet.NAME()) HTH, Shawn On Fri, Aug 28, 2015 at 4:13 PM, Dennis Conklin > wrote: All, Once again, I need help. We are starting to assign names to our Exodus blocks (outside of Paraview). This is very useful for ease and clarity of post processing and allows convenient reference to actual components. The good news is that Paraview seems perfectly happy to read in the Block Names and use them in the Properties Panel and the Multi-block Inspector and the Find Data screen if they exist (no action or programming required for this). So, for instance, instead of Paraview generating the non-useful name of ?Unnamed block ID: 13 Type: hex? when the blockname is empty, it will automagically use the more useful Blockname of ?Tread? if that is in the Exodus file. However, there has been an unintended consequence of this change. If I select some elements and examine them in Spreadsheet View, I see Block Number 14( the +1 offset from Block_ID and Block Number is NOT the problem!). And now I can no longer associate the element (Block Number 14) with it?s block in the Properties Panel or the Multi-block Inspector or the Find Data panel ? where the same block is called ?Tread?. So, to remedy this situation I would like to add an element variable of BlockName, which would contain ?Tread? for all the elements in BlockID 13, etc., etc. for all the blocks. My only problem is I can?t seem to find the list of Block Names. I?m pretty weak at vtk, so it must be available but I surrender ? I can?t seem to find it. If someone can help me find the list of Block Names from inside the Programmable Filter, I?ll be happy to add the element variable myself. Thanks for any help, again! Dennis _______________________________________________ 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: From shawn.waldon at kitware.com Mon Aug 31 10:47:55 2015 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Mon, 31 Aug 2015 10:47:55 -0400 Subject: [Paraview] [EXT] Re: Exodus Block Names In-Reply-To: References: Message-ID: Dennis, Given those block names, I think I know what you are missing. It is possible for a block to be a vtkMultiBlockDataSet itself, in which case you would need to get the block with mbi.GetBlock(0) and then do another loop over the blocks in that one to look at the block names. A quick way to check this is to look at the Information panel in ParaView. The tree there reflects the tree in the data and each node you can expand is a vtkMultiBlockDataSet (or other composite dataset type, but that one is the most common). Shawn On Mon, Aug 31, 2015 at 10:40 AM, Dennis Conklin < dennis_conklin at goodyear.com> wrote: > Shawn, > > > > Ok, I?m dense. > > > > When I run your code inside the Programmable Filter, I see some confusing > things: > > mbi.GetNumberOfBlocks returns 8, which is NOT the number of blocks in my > model but IS the number of MetaData blocks. > > > > The mbi.GetMetaData[i].Get(vtk.vtkCompositeDataSet.NAME()) then is > > Value of i Name > > 0 Element Blocks > > 1 Face Blocks > > 2 Edge Blocks > > 3 Element Sets > > 4 Side Sets > > 5 Face Sets > > 6 Edge Sets > > 7 Node Sets > > 8 > > > > I am poking around mbi.GetMetaData[0] (Element Blocks) but I still haven?t > found any Block Names there. I feel like I am completely missing > something here, but I have no idea what it is. > > > > Dennis > > > > > > *From:* Shawn Waldon [mailto:shawn.waldon at kitware.com] > *Sent:* Monday, August 31, 2015 9:46 AM > *To:* Dennis Conklin > *Cc:* Paraview (paraview at paraview.org) > *Subject:* Re: [EXT] Re: [Paraview] Exodus Block Names > > > > Hi Dennis, > > The metadata is on the reader's output, which is a vtkMultiBlockDataSet. > reader.GetOutput() should get you the dataset in your python script. > Inside the programmable filter you will need to get the input dataset > (self.GetInput() should get you the input dataset and self.GetOutput() > should get you the output dataset). So something like the following for > your programmable filter: > > mbi = self.GetInput() > > mbo = self.GetOutput() > > mbo.ShallowCopy(mbi) > > for i in range(mbo.GetNumberOfBlocks()): > metadata = mbo.GetMetaData(i) > name = metadata.Get(vtk.vtkCompositeDataSet.NAME()) > > # do something with the name > > > > > > HTH, > > Shawn > > > > On Mon, Aug 31, 2015 at 8:31 AM, Dennis Conklin < > dennis_conklin at goodyear.com> wrote: > > Shawn, > > > > Thanks for that tip but I can?t seem to access this structure. Really, I > need it within the Programmable Filter, but even when I run a Python script > and try to find it directly in an Exodus reader, I can?t seem to locate > this metadata. > > > > If I print dir(ExodusReader), there doesn?t seem to be anything about > metadata. > > Dennis > > > > *From:* Shawn Waldon [mailto:shawn.waldon at kitware.com] > *Sent:* Friday, August 28, 2015 4:44 PM > *To:* Dennis Conklin > *Cc:* Paraview (paraview at paraview.org) > *Subject:* [EXT] Re: [Paraview] Exodus Block Names > > > > Hi Dennis, > > The block name is in the block metadata, which is not where I looked the > first time either. Here is a code snippet that shows how to access it. > > mb = vtk.vtkMultiBlockDataSet() > ... > > for i in range(mb.GetNumberOfBlocks): > > metadata = mb.GetMetaData(i) > > name = metadata.Get(vtk.vtkCompositeDataSet.NAME()) > > HTH, > > Shawn > > > > On Fri, Aug 28, 2015 at 4:13 PM, Dennis Conklin < > dennis_conklin at goodyear.com> wrote: > > All, > > > > Once again, I need help. We are starting to assign names to our Exodus > blocks (outside of Paraview). This is very useful for ease and clarity of > post processing and allows convenient reference to actual components. The > good news is that Paraview seems perfectly happy to read in the Block Names > and use them in the Properties Panel and the Multi-block Inspector and the > Find Data screen if they exist (no action or programming required for > this). So, for instance, instead of Paraview generating the non-useful > name of ?Unnamed block ID: 13 Type: hex? when the blockname is empty, it > will automagically use the more useful Blockname of ?Tread? if that is in > the Exodus file. > > > > However, there has been an unintended consequence of this change. If I > select some elements and examine them in Spreadsheet View, I see Block > Number 14( the +1 offset from Block_ID and Block Number is NOT the > problem!). And now I can no longer associate the element (Block Number > 14) with it?s block in the Properties Panel or the Multi-block Inspector or > the Find Data panel ? where the same block is called ?Tread?. > > > > So, to remedy this situation I would like to add an element variable of > BlockName, which would contain ?Tread? for all the elements in BlockID 13, > etc., etc. for all the blocks. > > > > My only problem is I can?t seem to find the list of Block Names. I?m > pretty weak at vtk, so it must be available but I surrender ? I can?t seem > to find it. If someone can help me find the list of Block Names from > inside the Programmable Filter, I?ll be happy to add the element variable > myself. > > > > Thanks for any help, again! > > > > Dennis > > > _______________________________________________ > 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: From david.thompson at kitware.com Mon Aug 31 10:49:54 2015 From: david.thompson at kitware.com (David Thompson) Date: Mon, 31 Aug 2015 10:49:54 -0400 Subject: [Paraview] [EXT] Re: Exodus Block Names In-Reply-To: References: Message-ID: <7C3F4A15-133C-41D0-BF86-50B60039B7AF@kitware.com> Hi all, The Exodus reader creates 8 top-level blocks to identify different types of data present in each file (corresponding to the names you see for 0-7). Each of these blocks contains child blocks for the actual data loaded from the file (which may be a subset of the data present in the file). It is these sub-blocks whose metadata will hold the names from the Exodus file. David > On Aug 31, 2015, at 10:40 AM, Dennis Conklin wrote: > > Shawn, > > Ok, I?m dense. > > When I run your code inside the Programmable Filter, I see some confusing things: > mbi.GetNumberOfBlocks returns 8, which is NOT the number of blocks in my model but IS the number of MetaData blocks. > > The mbi.GetMetaData[i].Get(vtk.vtkCompositeDataSet.NAME()) then is > Value of i Name > 0 Element Blocks > 1 Face Blocks > 2 Edge Blocks > 3 Element Sets > 4 Side Sets > 5 Face Sets > 6 Edge Sets > 7 Node Sets > 8 > > I am poking around mbi.GetMetaData[0] (Element Blocks) but I still haven?t found any Block Names there. I feel like I am completely missing something here, but I have no idea what it is. > > Dennis > > > From: Shawn Waldon [mailto:shawn.waldon at kitware.com] > Sent: Monday, August 31, 2015 9:46 AM > To: Dennis Conklin > Cc: Paraview (paraview at paraview.org) > Subject: Re: [EXT] Re: [Paraview] Exodus Block Names > > Hi Dennis, > > The metadata is on the reader's output, which is a vtkMultiBlockDataSet. reader.GetOutput() should get you the dataset in your python script. Inside the programmable filter you will need to get the input dataset (self.GetInput() should get you the input dataset and self.GetOutput() should get you the output dataset). So something like the following for your programmable filter: > > mbi = self.GetInput() > mbo = self.GetOutput() > > mbo.ShallowCopy(mbi) > > for i in range(mbo.GetNumberOfBlocks()): > metadata = mbo.GetMetaData(i) > name = metadata.Get(vtk.vtkCompositeDataSet.NAME()) > # do something with the name > > > HTH, > Shawn > > On Mon, Aug 31, 2015 at 8:31 AM, Dennis Conklin wrote: > Shawn, > > Thanks for that tip but I can?t seem to access this structure. Really, I need it within the Programmable Filter, but even when I run a Python script and try to find it directly in an Exodus reader, I can?t seem to locate this metadata. > > If I print dir(ExodusReader), there doesn?t seem to be anything about metadata. > Dennis > > From: Shawn Waldon [mailto:shawn.waldon at kitware.com] > Sent: Friday, August 28, 2015 4:44 PM > To: Dennis Conklin > Cc: Paraview (paraview at paraview.org) > Subject: [EXT] Re: [Paraview] Exodus Block Names > > Hi Dennis, > > The block name is in the block metadata, which is not where I looked the first time either. Here is a code snippet that shows how to access it. > > mb = vtk.vtkMultiBlockDataSet() > ... > for i in range(mb.GetNumberOfBlocks): > metadata = mb.GetMetaData(i) > name = metadata.Get(vtk.vtkCompositeDataSet.NAME()) > > HTH, > Shawn > > On Fri, Aug 28, 2015 at 4:13 PM, Dennis Conklin wrote: > All, > > Once again, I need help. We are starting to assign names to our Exodus blocks (outside of Paraview). This is very useful for ease and clarity of post processing and allows convenient reference to actual components. The good news is that Paraview seems perfectly happy to read in the Block Names and use them in the Properties Panel and the Multi-block Inspector and the Find Data screen if they exist (no action or programming required for this). So, for instance, instead of Paraview generating the non-useful name of ?Unnamed block ID: 13 Type: hex? when the blockname is empty, it will automagically use the more useful Blockname of ?Tread? if that is in the Exodus file. > > However, there has been an unintended consequence of this change. If I select some elements and examine them in Spreadsheet View, I see Block Number 14( the +1 offset from Block_ID and Block Number is NOT the problem!). And now I can no longer associate the element (Block Number 14) with it?s block in the Properties Panel or the Multi-block Inspector or the Find Data panel ? where the same block is called ?Tread?. > > So, to remedy this situation I would like to add an element variable of BlockName, which would contain ?Tread? for all the elements in BlockID 13, etc., etc. for all the blocks. > > My only problem is I can?t seem to find the list of Block Names. I?m pretty weak at vtk, so it must be available but I surrender ? I can?t seem to find it. If someone can help me find the list of Block Names from inside the Programmable Filter, I?ll be happy to add the element variable myself. > > Thanks for any help, again! > > Dennis > > _______________________________________________ > 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 From dan.lipsa at kitware.com Mon Aug 31 14:23:56 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Mon, 31 Aug 2015 14:23:56 -0400 Subject: [Paraview] python changes 4.0/4.1 to 4.3? In-Reply-To: References: <201506082339.t58NddUv065709@mech-as222.men.bris.ac.uk> Message-ID: Anton, I think the relevant change in ParaView 4.3 is that it now colors data resulted from a threshold operation using the default color map. This makes sense as you may see data with different values within a given threshold. (this is not the case in your particular case). This is why your DiffuseColor settings have no effect. If you want to color you threshold data with a plain color as you have done in the past you have to add ColorBy(DataRepresentationX, None) after you set DataRepresentationx.DifuseColor = ... Where X is 2, 3 and 4. Dan On Tue, Jun 9, 2015 at 2:40 PM, Anton Shterenlikht wrote: > There is no error, just instead of the requested colours: > > DataRepresentation2.DiffuseColor = [ 1, 0, 1 ] <- purple > DataRepresentation3.DiffuseColor = [1.0, 1.0, 0.0] <- yellow > DataRepresentation4.DiffuseColor = [0.0, 1.0, 0.5] <- greenish > > I get red and blue. > > The colours I had with pv 4.0/4.1 can be seen here: > http://eis.bris.ac.uk/~mexas/cgpack/201502res/cr.png > http://eis.bris.ac.uk/~mexas/cgpack/201503res/gb.png > > The colours I'm getting now with 4.3 (with the same script) > can be seen here: > http://eis.bris.ac.uk/~mexas/cgpack/201506res/cr.png > http://eis.bris.ac.uk/~mexas/cgpack/201506res/gb.png > > The 2 data files I used are: > http://eis.bris.ac.uk/~mexas/zg0.raw > http://eis.bris.ac.uk/~mexas/zf5.raw > > The files are raw binary, 40MB each. > > I might have done something really stupid, > in which case I apologise for wasting your time. > > Thanks for your help > > Anton > > > On 09/06/2015, Utkarsh Ayachit wrote: > > Anton, > > > > DiffuseColor still exists. Can you post the full error message that > you're > > getting? If you can share the dataset you're using to test this script, > > that'll be even better! > > > > Utkarsh > > > > > > On Mon, Jun 8, 2015 at 7:39 PM Anton Shterenlikht > wrote: > > > >> I've a script that used to work ok on 4.0 and 4.1, > >> but now something is wrong with the colours. > >> Has anything changed between 4.0/4.1 to 4.3 to make > >> > >> DataRepresentation3.DiffuseColor = [1.0, 1.0, 0.0] > >> > >> not understood? > >> > >> > >> The full script: > >> > >> ######################################################################72 > >> # Adjust these parameters > >> ext1 = 220 # data extent along 1 > >> ext2 = 220 # data extent along 2 > >> ext3 = 220 # data extent along 3 > >> ffile = "zf5.raw" # fracture file > >> gfile = "zg0.raw" # grain file > >> imsize1 = 1000 # size, in pixels, of the resulting image along 1 > >> imsize2 = 1000 # size, in pixels, of the resulting image along 2 > >> > >> # End of adjustable parameters > >> ######################################################################72 > >> > >> # define the centre of rotation (cor) > >> cor1 = 0.5 * ext1 > >> cor2 = 0.5 * ext2 > >> cor3 = 0.5 * ext3 > >> > >> from paraview.simple import * > >> > >> # the extents start from zero, so need to lower > >> # the upper extents by 1 > >> cracks = ImageReader( FilePrefix= ffile ) > >> cracks.DataExtent=[ 0, ext1-1, 0, ext2-1, 0, ext3-1 ] > >> cracks.DataByteOrder = 'LittleEndian' > >> cracks.DataScalarType = 'int' > >> > >> RenderView1 = GetRenderView() > >> DataRepresentation1 = Show() > >> > >> DataRepresentation1.Representation = 'Outline' > >> DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5] > >> > >> # grain boundaries, cell state 2 > >> > >> Threshold1 = Threshold() > >> Threshold1.Scalars = ['POINTS', 'ImageFile'] > >> Threshold1.ThresholdRange = [ 2, 2 ] > >> Threshold1.AllScalars = 0 > >> > >> DataRepresentation2 = Show() > >> DataRepresentation2.ScalarOpacityUnitDistance = 1.0 > >> DataRepresentation2.SelectionPointFieldDataArrayName = 'ImageFile' > >> DataRepresentation2.DiffuseColor = [ 1, 0, 1 ] > >> > >> camera = GetActiveCamera() > >> camera.SetViewUp(-1,0,0) > >> camera.Azimuth(30) > >> camera.Elevation(30) > >> > >> RenderView1.ResetCamera() > >> > >> # gradient background colour > >> RenderView1.UseGradientBackground = 1 > >> RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117] > >> RenderView1.Background = [0.3215686274509804, 0.3411764705882353, > >> 0.43137254901960786] > >> > >> RenderView1.CenterAxesVisibility = 0 > >> RenderView1.OrientationAxesVisibility = 1 > >> RenderView1.CenterOfRotation = [ cor1, cor2, cor3 ] > >> RenderView1.CameraFocalPoint = [ cor1, cor2, cor3 ] > >> RenderView1.ViewSize = [ imsize1, imsize2 ] > >> RenderView1.CameraViewAngle = 30 > >> > >> # do all crack states from the main dataset > >> SetActiveSource( cracks ) > >> > >> # (100) cracks > >> cracks100 = Threshold() > >> cracks100.Scalars = ['POINTS', 'ImageFile'] > >> cracks100.ThresholdRange = [ 0, 0 ] > >> cracks100.AllScalars = 0 > >> > >> DataRepresentation3 = Show() > >> DataRepresentation3.ScalarOpacityUnitDistance = 1.0 > >> DataRepresentation3.SelectionPointFieldDataArrayName = 'ImageFile' > >> DataRepresentation3.DiffuseColor = [1.0, 1.0, 0.0] > >> > >> # (110) cracks > >> SetActiveSource( cracks ) > >> cracks110 = Threshold() > >> cracks110.Scalars = ['POINTS', 'ImageFile'] > >> cracks110.ThresholdRange = [ -1, -1 ] > >> cracks110.AllScalars = 0 > >> > >> DataRepresentation4 = Show() > >> DataRepresentation4.ScalarOpacityUnitDistance = 1.0 > >> DataRepresentation4.SelectionPointFieldDataArrayName = 'ImageFile' > >> DataRepresentation4.DiffuseColor = [0.0, 1.0, 0.5] > >> > >> # 1 is to show, 0 not to show > >> # data2 is GB > >> # data3 is cracks > >> # data4 is grains microstructure > >> > >> DataRepresentation2.Opacity = 0.1 > >> WriteImage( "crgb.png" ) > >> > >> DataRepresentation2.Opacity = 1 > >> DataRepresentation3.Visibility = 0 > >> WriteImage( "gb.png" ) > >> > >> DataRepresentation2.Visibility = 0 > >> DataRepresentation3.Visibility = 1 > >> WriteImage( "cr.png" ) > >> > >> RenderView1.ResetCamera() > >> > >> Render() > >> > >> > >> **** > >> > >> Is there anything wrong in this script for 4.3? > >> > >> Many thanks > >> > >> Anton > >> > >> _______________________________________________ > >> 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: From dennis_conklin at goodyear.com Mon Aug 31 14:47:18 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Mon, 31 Aug 2015 18:47:18 +0000 Subject: [Paraview] [EXT] Re: Exodus Block Names In-Reply-To: <7C3F4A15-133C-41D0-BF86-50B60039B7AF@kitware.com> References: <7C3F4A15-133C-41D0-BF86-50B60039B7AF@kitware.com> Message-ID: All, Just to wrap this up for the benefit of anyone who searches on this later: From a python script, it's pretty easy # Get a pointer to Exodus Reader, either open a file or get Active Source rdr=GetActiveSource() Block1=rdr.ElementBlocks[0] Print Block1 # output will be block name In a Programmable Filter, things are a little more complicated: # First create list of Block_names # Input=self.GetInput() # Element Block data is in DataBlock(0) of composite database ElementBlocks=input.GetBlock(0) #Number of ElementBlocks numElemBlocks=ElementBlocks.GetNumberOfBlocks() # Block_names=[] #list # # names for all blocks in file are available # normally only care about blocks that are loaded # make a list of all and index blocks of interest later For blk in range(numElemBlocks): meta=ElementBlocks.GetMetaData(blk) Name=meta.Get(vtk.vtkCompositeDataSet.NAME()) Block_names.append(Name) # # Loop over all loaded blocks and find associated names For block in output: Blk_id=block.FieldData.GetArray('ElementBlockIds') Blk_name=Block_names[Blk_id-1] Thanks to everyone for their help. Dennis -----Original Message----- From: David Thompson [mailto:david.thompson at kitware.com] Sent: Monday, August 31, 2015 10:50 AM To: Dennis Conklin Cc: Shawn Waldon; Paraview (paraview at paraview.org) Subject: Re: [Paraview] [EXT] Re: Exodus Block Names Hi all, The Exodus reader creates 8 top-level blocks to identify different types of data present in each file (corresponding to the names you see for 0-7). Each of these blocks contains child blocks for the actual data loaded from the file (which may be a subset of the data present in the file). It is these sub-blocks whose metadata will hold the names from the Exodus file. David > On Aug 31, 2015, at 10:40 AM, Dennis Conklin wrote: > > Shawn, > > Ok, I?m dense. > > When I run your code inside the Programmable Filter, I see some confusing things: > mbi.GetNumberOfBlocks returns 8, which is NOT the number of blocks in my model but IS the number of MetaData blocks. > > The mbi.GetMetaData[i].Get(vtk.vtkCompositeDataSet.NAME()) then is > Value of i Name > 0 Element Blocks > 1 Face Blocks > 2 Edge Blocks > 3 Element Sets > 4 Side Sets > 5 Face Sets > 6 Edge Sets > 7 Node Sets > 8 > > I am poking around mbi.GetMetaData[0] (Element Blocks) but I still haven?t found any Block Names there. I feel like I am completely missing something here, but I have no idea what it is. > > Dennis > > > From: Shawn Waldon [mailto:shawn.waldon at kitware.com] > Sent: Monday, August 31, 2015 9:46 AM > To: Dennis Conklin > Cc: Paraview (paraview at paraview.org) > Subject: Re: [EXT] Re: [Paraview] Exodus Block Names > > Hi Dennis, > > The metadata is on the reader's output, which is a vtkMultiBlockDataSet. reader.GetOutput() should get you the dataset in your python script. Inside the programmable filter you will need to get the input dataset (self.GetInput() should get you the input dataset and self.GetOutput() should get you the output dataset). So something like the following for your programmable filter: > > mbi = self.GetInput() > mbo = self.GetOutput() > > mbo.ShallowCopy(mbi) > > for i in range(mbo.GetNumberOfBlocks()): > metadata = mbo.GetMetaData(i) > name = metadata.Get(vtk.vtkCompositeDataSet.NAME()) > # do something with the name > > > HTH, > Shawn > > On Mon, Aug 31, 2015 at 8:31 AM, Dennis Conklin wrote: > Shawn, > > Thanks for that tip but I can?t seem to access this structure. Really, I need it within the Programmable Filter, but even when I run a Python script and try to find it directly in an Exodus reader, I can?t seem to locate this metadata. > > If I print dir(ExodusReader), there doesn?t seem to be anything about metadata. > Dennis > > From: Shawn Waldon [mailto:shawn.waldon at kitware.com] > Sent: Friday, August 28, 2015 4:44 PM > To: Dennis Conklin > Cc: Paraview (paraview at paraview.org) > Subject: [EXT] Re: [Paraview] Exodus Block Names > > Hi Dennis, > > The block name is in the block metadata, which is not where I looked the first time either. Here is a code snippet that shows how to access it. > > mb = vtk.vtkMultiBlockDataSet() > ... > for i in range(mb.GetNumberOfBlocks): > metadata = mb.GetMetaData(i) > name = metadata.Get(vtk.vtkCompositeDataSet.NAME()) > > HTH, > Shawn > > On Fri, Aug 28, 2015 at 4:13 PM, Dennis Conklin wrote: > All, > > Once again, I need help. We are starting to assign names to our Exodus blocks (outside of Paraview). This is very useful for ease and clarity of post processing and allows convenient reference to actual components. The good news is that Paraview seems perfectly happy to read in the Block Names and use them in the Properties Panel and the Multi-block Inspector and the Find Data screen if they exist (no action or programming required for this). So, for instance, instead of Paraview generating the non-useful name of ?Unnamed block ID: 13 Type: hex? when the blockname is empty, it will automagically use the more useful Blockname of ?Tread? if that is in the Exodus file. > > However, there has been an unintended consequence of this change. If I select some elements and examine them in Spreadsheet View, I see Block Number 14( the +1 offset from Block_ID and Block Number is NOT the problem!). And now I can no longer associate the element (Block Number 14) with it?s block in the Properties Panel or the Multi-block Inspector or the Find Data panel ? where the same block is called ?Tread?. > > So, to remedy this situation I would like to add an element variable of BlockName, which would contain ?Tread? for all the elements in BlockID 13, etc., etc. for all the blocks. > > My only problem is I can?t seem to find the list of Block Names. I?m pretty weak at vtk, so it must be available but I surrender ? I can?t seem to find it. If someone can help me find the list of Block Names from inside the Programmable Filter, I?ll be happy to add the element variable myself. > > Thanks for any help, again! > > Dennis > > _______________________________________________ > 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 From wascott at sandia.gov Mon Aug 31 15:16:51 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 31 Aug 2015 19:16:51 +0000 Subject: [Paraview] [EXTERNAL] Re: [EXT] Re: Exodus Block Names In-Reply-To: References: <7C3F4A15-133C-41D0-BF86-50B60039B7AF@kitware.com> Message-ID: <1bc10baecc0e4fe99f45832268aaf217@ES01AMSNLNT.srn.sandia.gov> Excellent, thanks Dennis! Alan -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Dennis Conklin Sent: Monday, August 31, 2015 12:47 PM To: David Thompson Cc: Paraview (paraview at paraview.org) Subject: [EXTERNAL] Re: [Paraview] [EXT] Re: Exodus Block Names All, Just to wrap this up for the benefit of anyone who searches on this later: From a python script, it's pretty easy # Get a pointer to Exodus Reader, either open a file or get Active Source rdr=GetActiveSource() Block1=rdr.ElementBlocks[0] Print Block1 # output will be block name In a Programmable Filter, things are a little more complicated: # First create list of Block_names # Input=self.GetInput() # Element Block data is in DataBlock(0) of composite database ElementBlocks=input.GetBlock(0) #Number of ElementBlocks numElemBlocks=ElementBlocks.GetNumberOfBlocks() # Block_names=[] #list # # names for all blocks in file are available # normally only care about blocks that are loaded # make a list of all and index blocks of interest later For blk in range(numElemBlocks): meta=ElementBlocks.GetMetaData(blk) Name=meta.Get(vtk.vtkCompositeDataSet.NAME()) Block_names.append(Name) # # Loop over all loaded blocks and find associated names For block in output: Blk_id=block.FieldData.GetArray('ElementBlockIds') Blk_name=Block_names[Blk_id-1] Thanks to everyone for their help. Dennis -----Original Message----- From: David Thompson [mailto:david.thompson at kitware.com] Sent: Monday, August 31, 2015 10:50 AM To: Dennis Conklin Cc: Shawn Waldon; Paraview (paraview at paraview.org) Subject: Re: [Paraview] [EXT] Re: Exodus Block Names Hi all, The Exodus reader creates 8 top-level blocks to identify different types of data present in each file (corresponding to the names you see for 0-7). Each of these blocks contains child blocks for the actual data loaded from the file (which may be a subset of the data present in the file). It is these sub-blocks whose metadata will hold the names from the Exodus file. David > On Aug 31, 2015, at 10:40 AM, Dennis Conklin wrote: > > Shawn, > > Ok, I?m dense. > > When I run your code inside the Programmable Filter, I see some confusing things: > mbi.GetNumberOfBlocks returns 8, which is NOT the number of blocks in my model but IS the number of MetaData blocks. > > The mbi.GetMetaData[i].Get(vtk.vtkCompositeDataSet.NAME()) then is > Value of i Name > 0 Element Blocks > 1 Face Blocks > 2 Edge Blocks > 3 Element Sets > 4 Side Sets > 5 Face Sets > 6 Edge Sets > 7 Node Sets > 8 > > I am poking around mbi.GetMetaData[0] (Element Blocks) but I still haven?t found any Block Names there. I feel like I am completely missing something here, but I have no idea what it is. > > Dennis > > > From: Shawn Waldon [mailto:shawn.waldon at kitware.com] > Sent: Monday, August 31, 2015 9:46 AM > To: Dennis Conklin > Cc: Paraview (paraview at paraview.org) > Subject: Re: [EXT] Re: [Paraview] Exodus Block Names > > Hi Dennis, > > The metadata is on the reader's output, which is a vtkMultiBlockDataSet. reader.GetOutput() should get you the dataset in your python script. Inside the programmable filter you will need to get the input dataset (self.GetInput() should get you the input dataset and self.GetOutput() should get you the output dataset). So something like the following for your programmable filter: > > mbi = self.GetInput() > mbo = self.GetOutput() > > mbo.ShallowCopy(mbi) > > for i in range(mbo.GetNumberOfBlocks()): > metadata = mbo.GetMetaData(i) > name = metadata.Get(vtk.vtkCompositeDataSet.NAME()) > # do something with the name > > > HTH, > Shawn > > On Mon, Aug 31, 2015 at 8:31 AM, Dennis Conklin wrote: > Shawn, > > Thanks for that tip but I can?t seem to access this structure. Really, I need it within the Programmable Filter, but even when I run a Python script and try to find it directly in an Exodus reader, I can?t seem to locate this metadata. > > If I print dir(ExodusReader), there doesn?t seem to be anything about metadata. > Dennis > > From: Shawn Waldon [mailto:shawn.waldon at kitware.com] > Sent: Friday, August 28, 2015 4:44 PM > To: Dennis Conklin > Cc: Paraview (paraview at paraview.org) > Subject: [EXT] Re: [Paraview] Exodus Block Names > > Hi Dennis, > > The block name is in the block metadata, which is not where I looked the first time either. Here is a code snippet that shows how to access it. > > mb = vtk.vtkMultiBlockDataSet() > ... > for i in range(mb.GetNumberOfBlocks): > metadata = mb.GetMetaData(i) > name = metadata.Get(vtk.vtkCompositeDataSet.NAME()) > > HTH, > Shawn > > On Fri, Aug 28, 2015 at 4:13 PM, Dennis Conklin wrote: > All, > > Once again, I need help. We are starting to assign names to our Exodus blocks (outside of Paraview). This is very useful for ease and clarity of post processing and allows convenient reference to actual components. The good news is that Paraview seems perfectly happy to read in the Block Names and use them in the Properties Panel and the Multi-block Inspector and the Find Data screen if they exist (no action or programming required for this). So, for instance, instead of Paraview generating the non-useful name of ?Unnamed block ID: 13 Type: hex? when the blockname is empty, it will automagically use the more useful Blockname of ?Tread? if that is in the Exodus file. > > However, there has been an unintended consequence of this change. If I select some elements and examine them in Spreadsheet View, I see Block Number 14( the +1 offset from Block_ID and Block Number is NOT the problem!). And now I can no longer associate the element (Block Number 14) with it?s block in the Properties Panel or the Multi-block Inspector or the Find Data panel ? where the same block is called ?Tread?. > > So, to remedy this situation I would like to add an element variable of BlockName, which would contain ?Tread? for all the elements in BlockID 13, etc., etc. for all the blocks. > > My only problem is I can?t seem to find the list of Block Names. I?m pretty weak at vtk, so it must be available but I surrender ? I can?t seem to find it. If someone can help me find the list of Block Names from inside the Programmable Filter, I?ll be happy to add the element variable myself. > > Thanks for any help, again! > > Dennis > > _______________________________________________ > 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 From dennis_conklin at goodyear.com Mon Aug 31 17:22:08 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Mon, 31 Aug 2015 21:22:08 +0000 Subject: [Paraview] [EXT] Re: Exodus Block Names References: <7C3F4A15-133C-41D0-BF86-50B60039B7AF@kitware.com> Message-ID: All, My final complication is that I am having trouble assigning String Element Variables. When I run the following code (assuming my earlier code): def process_block(block): numElems=block.GetNumberOfCells() block_id=block.FieldData.GetArray('ElementBlockIds') #print block_id name=Blk_names[block_id-1] name_length=name.__len__() #print name #print name_length Block_Names=numpy.chararray( (numElems),itemsize=name_length ) Block_Names.fill(name) #print Block_Names block.CellData.append(Block_Names,"Block Name") I end up with a character array the size of numElems and holding the BlockName for every element. The append fails with the error shown below. It looks like it doesn't want me to append a string variable to block.CellData. Is there a way to do this? Thanks, yet again, for the umpteenth time! Dennis Traceback (most recent call last): File "", line 21, in File "", line 45, in RequestData File "", line 15, in process_block File "/apps/share/paraview/4.3.1/Linux/lib/paraview-4.3/site-packages/vtk/numpy_interface/dataset_adapter.py", line 649, in append arr = numpyTovtkDataArray(copy, name) File "/apps/share/paraview/4.3.1/Linux/lib/paraview-4.3/site-packages/vtk/numpy_interface/dataset_adapter.py", line 148, in numpyTovtkDataArray vtkarray = numpy_support.numpy_to_vtk(array) File "/apps/share/paraview/4.3.1/Linux/lib/paraview-4.3/site-packages/vtk/util/numpy_support.py", line 166, in numpy_to_vtk z_flat = numpy.ravel(z).astype(arr_dtype) ValueError: invalid literal for int() with base 10: 'Apex_1' -----Original Message----- From: Dennis Conklin Sent: Monday, August 31, 2015 2:47 PM To: 'David Thompson' Cc: Shawn Waldon; Paraview (paraview at paraview.org) Subject: RE: [Paraview] [EXT] Re: Exodus Block Names All, Just to wrap this up for the benefit of anyone who searches on this later: From a python script, it's pretty easy # Get a pointer to Exodus Reader, either open a file or get Active Source rdr=GetActiveSource() Block1=rdr.ElementBlocks[0] Print Block1 # output will be block name In a Programmable Filter, things are a little more complicated: # First create list of Block_names # Input=self.GetInput() # Element Block data is in DataBlock(0) of composite database ElementBlocks=input.GetBlock(0) #Number of ElementBlocks numElemBlocks=ElementBlocks.GetNumberOfBlocks() # Block_names=[] #list # # names for all blocks in file are available # normally only care about blocks that are loaded # make a list of all and index blocks of interest later For blk in range(numElemBlocks): meta=ElementBlocks.GetMetaData(blk) Name=meta.Get(vtk.vtkCompositeDataSet.NAME()) Block_names.append(Name) # # Loop over all loaded blocks and find associated names For block in output: Blk_id=block.FieldData.GetArray('ElementBlockIds') Blk_name=Block_names[Blk_id-1] Thanks to everyone for their help. Dennis -----Original Message----- From: David Thompson [mailto:david.thompson at kitware.com] Sent: Monday, August 31, 2015 10:50 AM To: Dennis Conklin Cc: Shawn Waldon; Paraview (paraview at paraview.org) Subject: Re: [Paraview] [EXT] Re: Exodus Block Names Hi all, The Exodus reader creates 8 top-level blocks to identify different types of data present in each file (corresponding to the names you see for 0-7). Each of these blocks contains child blocks for the actual data loaded from the file (which may be a subset of the data present in the file). It is these sub-blocks whose metadata will hold the names from the Exodus file. David > On Aug 31, 2015, at 10:40 AM, Dennis Conklin wrote: > > Shawn, > > Ok, I?m dense. > > When I run your code inside the Programmable Filter, I see some confusing things: > mbi.GetNumberOfBlocks returns 8, which is NOT the number of blocks in my model but IS the number of MetaData blocks. > > The mbi.GetMetaData[i].Get(vtk.vtkCompositeDataSet.NAME()) then is > Value of i Name > 0 Element Blocks > 1 Face Blocks > 2 Edge Blocks > 3 Element Sets > 4 Side Sets > 5 Face Sets > 6 Edge Sets > 7 Node Sets > 8 > > I am poking around mbi.GetMetaData[0] (Element Blocks) but I still haven?t found any Block Names there. I feel like I am completely missing something here, but I have no idea what it is. > > Dennis > > > From: Shawn Waldon [mailto:shawn.waldon at kitware.com] > Sent: Monday, August 31, 2015 9:46 AM > To: Dennis Conklin > Cc: Paraview (paraview at paraview.org) > Subject: Re: [EXT] Re: [Paraview] Exodus Block Names > > Hi Dennis, > > The metadata is on the reader's output, which is a vtkMultiBlockDataSet. reader.GetOutput() should get you the dataset in your python script. Inside the programmable filter you will need to get the input dataset (self.GetInput() should get you the input dataset and self.GetOutput() should get you the output dataset). So something like the following for your programmable filter: > > mbi = self.GetInput() > mbo = self.GetOutput() > > mbo.ShallowCopy(mbi) > > for i in range(mbo.GetNumberOfBlocks()): > metadata = mbo.GetMetaData(i) > name = metadata.Get(vtk.vtkCompositeDataSet.NAME()) > # do something with the name > > > HTH, > Shawn > > On Mon, Aug 31, 2015 at 8:31 AM, Dennis Conklin wrote: > Shawn, > > Thanks for that tip but I can?t seem to access this structure. Really, I need it within the Programmable Filter, but even when I run a Python script and try to find it directly in an Exodus reader, I can?t seem to locate this metadata. > > If I print dir(ExodusReader), there doesn?t seem to be anything about metadata. > Dennis > > From: Shawn Waldon [mailto:shawn.waldon at kitware.com] > Sent: Friday, August 28, 2015 4:44 PM > To: Dennis Conklin > Cc: Paraview (paraview at paraview.org) > Subject: [EXT] Re: [Paraview] Exodus Block Names > > Hi Dennis, > > The block name is in the block metadata, which is not where I looked the first time either. Here is a code snippet that shows how to access it. > > mb = vtk.vtkMultiBlockDataSet() > ... > for i in range(mb.GetNumberOfBlocks): > metadata = mb.GetMetaData(i) > name = metadata.Get(vtk.vtkCompositeDataSet.NAME()) > > HTH, > Shawn > > On Fri, Aug 28, 2015 at 4:13 PM, Dennis Conklin wrote: > All, > > Once again, I need help. We are starting to assign names to our Exodus blocks (outside of Paraview). This is very useful for ease and clarity of post processing and allows convenient reference to actual components. The good news is that Paraview seems perfectly happy to read in the Block Names and use them in the Properties Panel and the Multi-block Inspector and the Find Data screen if they exist (no action or programming required for this). So, for instance, instead of Paraview generating the non-useful name of ?Unnamed block ID: 13 Type: hex? when the blockname is empty, it will automagically use the more useful Blockname of ?Tread? if that is in the Exodus file. > > However, there has been an unintended consequence of this change. If I select some elements and examine them in Spreadsheet View, I see Block Number 14( the +1 offset from Block_ID and Block Number is NOT the problem!). And now I can no longer associate the element (Block Number 14) with it?s block in the Properties Panel or the Multi-block Inspector or the Find Data panel ? where the same block is called ?Tread?. > > So, to remedy this situation I would like to add an element variable of BlockName, which would contain ?Tread? for all the elements in BlockID 13, etc., etc. for all the blocks. > > My only problem is I can?t seem to find the list of Block Names. I?m pretty weak at vtk, so it must be available but I surrender ? I can?t seem to find it. If someone can help me find the list of Block Names from inside the Programmable Filter, I?ll be happy to add the element variable myself. > > Thanks for any help, again! > > Dennis > > _______________________________________________ > 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 From marcus.hanwell at kitware.com Mon Aug 31 17:37:28 2015 From: marcus.hanwell at kitware.com (Marcus D. Hanwell) Date: Mon, 31 Aug 2015 17:37:28 -0400 Subject: [Paraview] Tomviz 0.6.1 released - custom ParaView application tomography/volume rendering Message-ID: Hi, I wanted to let ParaView users know that we have released tomviz 0.6.1. It is a ParaView based application with a focus on visualization and analysis of volumetric data, with a particular focus on materials tomography. It features a simplified interface, and an extended Python environment offering SciPy, NumPy, and pretty soon the Python-wrapped ITK library. http://tomviz.org/ is the main project web site, and you can download binaries for Windows and Mac OS X from there. We would love to hear feedback, and we will extend out the functionality over the next few years. It features the new OpenGL2 rendering backend, and so this is a chance to try out some of the new rendering before ParaView begins packaging it. Thanks, Marcus From aeatmon at lanl.gov Mon Aug 3 16:44:55 2015 From: aeatmon at lanl.gov (Eatmon Jr., Arnold) Date: Mon, 03 Aug 2015 20:44:55 -0000 Subject: [Paraview] FW: adjusting vertical level setting via paraview python script In-Reply-To: References: Message-ID: I ran the script and attained the expected output (a set of vtu and pvtu files for all adaptor output). I am unable to open them due to a compatibility issue with paraview 4.3.1 and the version 4.3.2 used in MPAS. Attached is a screenshot of the selection of readers asked for when opening one of the files. I also included a section that explicitly lists the file names I downloaded. From: Andy Bauer > Date: Monday, August 3, 2015 at 2:39 PM To: First name Last name > Cc: "arnoldeatmon at gmail.com" >, "Patchett, John M" >, "paraview at paraview.org" > Subject: Re: [Paraview] FW: adjusting vertical level setting via paraview python script Yes, that should be the proper workflow. On Mon, Aug 3, 2015 at 4:21 PM, Eatmon Jr., Arnold > wrote: From: "", First name Last name > Date: Monday, August 3, 2015 at 2:12 PM To: Andy Bauer > Subject: Re: [Paraview] adjusting vertical level setting via paraview python script Unfortunately I do not think that version is available which is why I was not using a script exported from Paraview gui with a .pvtu file open in it. Attempting to open vtk files generated in MPAS-O in the paraview GUI results in paraview not knowing which reader to use and crashing. John Patchett contacted kitware about this issue a few weeks ago; but again the build for version 4.3.2 that could open the output Vtk files is no longer up on the paraview site. I will attempt to follow your instructions and find out nonetheless, to be clear I should: 1. Use your script and write out a vtk file from MPAS-O 2. Open that file in the Paraview gui 3. Make the changes I want and export that change to a python script via coprocessing Is this correct? From: Andy Bauer > Date: Monday, August 3, 2015 at 2:03 PM To: First name Last name > Cc: "Patchett, John M" >, Dave DeMarle >, "paraview at paraview.org" > Subject: Re: [Paraview] adjusting vertical level setting via paraview python script I think the changes to the XML formats were done prior to PV 4.3.1 but am not certain. When making the scripts in the GUI you'll want to use the same version of ParaView though that is linked with MPAS to make sure the generated Python scripts are compatible. On Mon, Aug 3, 2015 at 3:56 PM, Eatmon Jr., Arnold > wrote: Oh, my mistake I didn?t understand the instructions. I will run it again to get .pvtu output, however in my previous scripts that generate VTK output there was an issue where the currently released 4.3.1 version of Paraview could not open the files due to a back compatability issue. I had a developers head on an old machine that could open them, however I do not any longer and the source code is no longer available on the paraview downloads page. Will v4.3.1 be able to open these .pvtu output files? From: Andy Bauer > Date: Monday, August 3, 2015 at 1:14 PM To: First name Last name >, "Patchett, John M" >, Dave DeMarle >, "paraview at paraview.org" > Subject: Re: [Paraview] adjusting vertical level setting via paraview python script Hi, Please reply to everyone so that anyone that wants to follow along with the conversation can. Did you get a chance to look through the Catalyst User's Guide? For MPAS, the names of the adaptor outputs are: 'X_Y_NLAYER-primal', 'X_Y_NLAYER-dual', 'X_Y_Z_1LAYER-primal', 'X_Y_Z_1LAYER-dual', 'X_Y_Z_NLAYER-primal', 'X_Y_Z_NLAYER-dual', 'LON_LAT_1LAYER-primal', 'LON_LAT_1LAYER-dual', 'LON_LAT_NLAYER-primal', 'LON_LAT_NLAYER-dual' The files that you want are the ones provided by Catalyst and not the ones that MPAS natively writes out. The Catalyst files all should be written out with pvtu extensions (e.g. X_Y_NLAYER-primal_1.pvtu). The MPAS native output is the .nc file. The other error that you're getting is that you have an active Python trace when going through the Catalyst export wizard and that trace needs to be stopped. Regards, Andy On Mon, Aug 3, 2015 at 3:00 PM, Eatmon Jr., Arnold > wrote: Alright, in order of what I did just to be clear, I uploaded the attached python to my directory, soft linked it to mpas.py, ran the simulation for a single timestep, and got a file in my output folder labeled output.0015-01-01_00.00.00.nc. I took that file and opened it in the Paraview desktop gui. In paraview with coprocessing enabled (Tools > Plugin Manager > under catalyst option, hit load), I made the adjustment to the vertical level and then exported the state (CoProcessing > Export State). I do not get a python script as an output, I get the error "Cannot generate Python state when tracing is active." RuntimeError: Cannot generate Python state when tracing is active. From: Andy Bauer > Date: Monday, August 3, 2015 at 11:33 AM To: David E DeMarle > Cc: First name Last name >, "Patchett, John M" >, "paraview at paraview.org" > Subject: Re: [Paraview] adjusting vertical level setting via paraview python script Hi, Dave is correct in that the reader's output needs to match what the adaptor is producing and in this case the MPAS NetCDF reader does not match what the adaptor provides to Catalyst. The way to get around this is to run Catalyst with a sample Python script that outputs the full data set that the adaptor provides. For MPAS this is slightly more complex because it provides several outputs, 10 in fact, depending on how the scientists want the data (e.g. spherical vs. projected, primal vs. dual grid, single level vs. multiple levels) for what they're trying to do. The attached script can be used to write out all 10 of these outputs which is done every 5th output (this can be changed by changing the outputfrequency value). The general workflow would be to run MPAS with this script for a small amount of time steps (maybe also with a smaller input data set). Then use those outputs to generate the Catalyst script that you want from the GUI. If this is a bit unclear, I'd recommend going through the Catalyst User's Guide (http://www.paraview.org/files/catalyst/docs/ParaViewCatalystUsersGuide_v2.pdf) for more details. Regards, Andy On Mon, Aug 3, 2015 at 12:20 PM, David E DeMarle > wrote: Andy Bauer just explained it to me. He'll get back to you soon with a detailed explanation and hints about how to get what you want done. Meanwhile, what is tripping us up is that MPAS's catalyst adaptor is not the same thing as ParaViews MPAS reader. The reader has the SetVerticalLevel(int) method, but the adaptor probably has an entirely different method for doing that. I don't know firsthand what that method is so we'll have to wait for his response. 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 4:20 PM, Eatmon Jr., Arnold > wrote: # 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 > Date: Thursday, July 30, 2015 at 1:45 PM To: First name Last name > 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 > 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 # 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 > Date: Thursday, July 30, 2015 at 12:32 PM To: First name Last name > Cc: "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 > 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 _______________________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2015-08-03 at 2.38.16 PM.png Type: image/png Size: 136595 bytes Desc: Screen Shot 2015-08-03 at 2.38.16 PM.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2015-08-03 at 2.43.00 PM.png Type: image/png Size: 460342 bytes Desc: Screen Shot 2015-08-03 at 2.43.00 PM.png URL: From robcoorens at gmail.com Tue Aug 4 04:07:51 2015 From: robcoorens at gmail.com (Rob Coorens) Date: Tue, 04 Aug 2015 08:07:51 -0000 Subject: [Paraview] scalars shown as vectors Message-ID: Dear All, Last time i wasnt a member to the list so not sure if sending my question worked. So here it is again: I am new to paraview and cant work out the following(which is essential to my thesis project). I have two datasets, one with vectors and one with scalars. I want to create glyphs that are scaled and oriented by the vector data and coloured by the scalar data. I grouped my datasets and then in glyphs i set my scale mode to vectors and colouring to scalars. However i think i also see vectors from my scalar dataset created by paraview. How can i remove these. Because they interfere with my visualization. I've included a screenshot :) Any help would be great!! kindest Regards Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: wrongvectors.png Type: image/png Size: 379099 bytes Desc: not available URL: