From dave.demarle at kitware.com Thu Feb 1 11:58:44 2018 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 1 Feb 2018 11:58:44 -0500 Subject: [Paraview-developers] gitlab is down, we'll let you know when it is back up Message-ID: Howdy, Gitlab is down at the moment. Due to an issue with an upgrade earlier this morning Gitlab is still offline. We are working as fast as we can to get it back online. sorry about that, David E DeMarle Kitware, Inc. Principal 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 Feb 1 12:38:00 2018 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 1 Feb 2018 12:38:00 -0500 Subject: [Paraview-developers] gitlab is down, we'll let you know when it is back up In-Reply-To: References: Message-ID: It is back up. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Feb 1, 2018 at 11:58 AM, David E DeMarle wrote: > Howdy, > > Gitlab is down at the moment. Due to an issue with an upgrade earlier > this morning Gitlab is still offline. We are working as fast as we can to > get it back online. > > sorry about that, > > David E DeMarle > Kitware, Inc. > Principal Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 <(518)%20881-4909> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From allison.vacanti at kitware.com Tue Feb 6 09:10:04 2018 From: allison.vacanti at kitware.com (Allie Vacanti) Date: Tue, 6 Feb 2018 09:10:04 -0500 Subject: [Paraview-developers] VTK third party changes breaking paraview dashboards Message-ID: Hi guys, Looks like there are some dashboard issues on paraview related to the recent third party changes. Is anyone working on these? Looks like vall needs Eigen3 installed: https://open.cdash.org/viewConfigure.php?buildid=5248512 The new libtiff/libharu aren't playing nicely (missing mangled syms?) https://open.cdash.org/viewBuildError.php?buildid=5248537 https://open.cdash.org/viewBuildError.php?buildid=5248527 Allie -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.martin at kitware.com Tue Feb 6 09:36:50 2018 From: ken.martin at kitware.com (Ken Martin) Date: Tue, 6 Feb 2018 09:36:50 -0500 Subject: [Paraview-developers] VTK third party changes breaking paraview dashboards In-Reply-To: References: Message-ID: I ran into the tiff haru issue a few days ago as well. I think there are also some CMake issues on Win32 as I had to locally modify some cmakelists to get cmake to run ala a hack ... otherwise cmake complains about an incorrect number of arguments to set_target_properties probably because the SO_COMPATVERSION is empty. diff --git a/ThirdParty/tiff/vtktiff/libtiff/CMakeLists.txt b/ThirdParty/tiff/vtktiff/libtiff/CMakeLists.txtindex 15fd8ad..bc37dfa 100644 --- a/ThirdParty/tiff/vtktiff/libtiff/CMakeLists.txt +++ b/ThirdParty/tiff/vtktiff/libtiff/CMakeLists.txt @@ -162,7 +162,7 @@ endif () if(cxx) add_library(tiffxx ${tiffxx_SOURCES} ${tiffxx_HEADERS}) target_link_libraries(tiffxx tiff) - set_target_properties(tiffxx PROPERTIES SOVERSION ${SO_COMPATVERSION}) +# set_target_properties(tiffxx PROPERTIES SOVERSION ${SO_COMPATVERSION}) if(NOT CYGWIN) # This property causes shared libraries on Linux to have the full version # encoded into their final filename. We disable this on Cygwin because On Tue, Feb 6, 2018 at 9:10 AM, Allie Vacanti wrote: > Hi guys, > > Looks like there are some dashboard issues on paraview related to the > recent third party changes. Is anyone working on these? > > Looks like vall needs Eigen3 installed: > > https://open.cdash.org/viewConfigure.php?buildid=5248512 > > The new libtiff/libharu aren't playing nicely (missing mangled syms?) > > https://open.cdash.org/viewBuildError.php?buildid=5248537 > https://open.cdash.org/viewBuildError.php?buildid=5248527 > > Allie > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://paraview.org/mailman/listinfo/paraview-developers > > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Tue Feb 6 10:21:25 2018 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 6 Feb 2018 10:21:25 -0500 Subject: [Paraview-developers] VTK third party changes breaking paraview dashboards In-Reply-To: References: Message-ID: <20180206152125.GA12863@megas.kitware.com> On Tue, Feb 06, 2018 at 09:36:50 -0500, Ken Martin wrote: > I ran into the tiff haru issue a few days ago as well. I think there are > also some CMake issues on Win32 as I had to locally modify some cmakelists > to get cmake to run ala a hack ... otherwise cmake complains about an > incorrect number of arguments to set_target_properties probably because the > SO_COMPATVERSION is empty. > > diff --git a/ThirdParty/tiff/vtktiff/libtiff/CMakeLists.txt > b/ThirdParty/tiff/vtktiff/libtiff/CMakeLists.txtindex 15fd8ad..bc37dfa > 100644 > --- a/ThirdParty/tiff/vtktiff/libtiff/CMakeLists.txt > +++ b/ThirdParty/tiff/vtktiff/libtiff/CMakeLists.txt > @@ -162,7 +162,7 @@ endif () > if(cxx) > add_library(tiffxx ${tiffxx_SOURCES} ${tiffxx_HEADERS}) > target_link_libraries(tiffxx tiff) > - set_target_properties(tiffxx PROPERTIES SOVERSION ${SO_COMPATVERSION}) > +# set_target_properties(tiffxx PROPERTIES SOVERSION ${SO_COMPATVERSION}) This whole block shouldn't be happening; the `cxx` variable should be hard-set to 0. --Ben From ben.boeckel at kitware.com Tue Feb 6 10:23:27 2018 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 6 Feb 2018 10:23:27 -0500 Subject: [Paraview-developers] VTK third party changes breaking paraview dashboards In-Reply-To: <20180206152125.GA12863@megas.kitware.com> References: <20180206152125.GA12863@megas.kitware.com> Message-ID: <20180206152327.GA28739@megas.kitware.com> On Tue, Feb 06, 2018 at 10:21:25 -0500, Ben Boeckel wrote: > This whole block shouldn't be happening; the `cxx` variable should be > hard-set to 0. Oh, I see what happened. Fix incoming for VTK (and upstream as well). --Ben From ben.boeckel at kitware.com Tue Feb 6 10:44:06 2018 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 6 Feb 2018 10:44:06 -0500 Subject: [Paraview-developers] VTK third party changes breaking paraview dashboards In-Reply-To: References: Message-ID: <20180206154406.GA1546@megas.kitware.com> On Tue, Feb 06, 2018 at 09:10:04 -0500, Allie Vacanti wrote: > The new libtiff/libharu aren't playing nicely (missing mangled syms?) > > https://open.cdash.org/viewBuildError.php?buildid=5248537 > https://open.cdash.org/viewBuildError.php?buildid=5248527 libharu copied tiff code and didn't change the symbol names. Shawn's going to rename the libharu copies and also submit it upstream. --Ben From shawn.waldon at kitware.com Tue Feb 6 10:59:39 2018 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Tue, 6 Feb 2018 10:59:39 -0500 Subject: [Paraview-developers] VTK third party changes breaking paraview dashboards In-Reply-To: References: Message-ID: I've installed eigen3-devel on vall, so that should go away and I'm working on the patch for libharu. On Tue, Feb 6, 2018 at 9:36 AM, Ken Martin wrote: > I ran into the tiff haru issue a few days ago as well. I think there are > also some CMake issues on Win32 as I had to locally modify some cmakelists > to get cmake to run ala a hack ... otherwise cmake complains about an > incorrect number of arguments to set_target_properties probably because the > SO_COMPATVERSION is empty. > > diff --git a/ThirdParty/tiff/vtktiff/libtiff/CMakeLists.txt > b/ThirdParty/tiff/vtktiff/libtiff/CMakeLists.txtindex 15fd8ad..bc37dfa > 100644 > --- a/ThirdParty/tiff/vtktiff/libtiff/CMakeLists.txt > +++ b/ThirdParty/tiff/vtktiff/libtiff/CMakeLists.txt > @@ -162,7 +162,7 @@ endif () > if(cxx) > add_library(tiffxx ${tiffxx_SOURCES} ${tiffxx_HEADERS}) > target_link_libraries(tiffxx tiff) > - set_target_properties(tiffxx PROPERTIES SOVERSION ${SO_COMPATVERSION}) > +# set_target_properties(tiffxx PROPERTIES SOVERSION ${SO_COMPATVERSION}) > if(NOT CYGWIN) > # This property causes shared libraries on Linux to have the full > version > # encoded into their final filename. We disable this on Cygwin > because > > > > On Tue, Feb 6, 2018 at 9:10 AM, Allie Vacanti > wrote: > >> Hi guys, >> >> Looks like there are some dashboard issues on paraview related to the >> recent third party changes. Is anyone working on these? >> >> Looks like vall needs Eigen3 installed: >> >> https://open.cdash.org/viewConfigure.php?buildid=5248512 >> >> The new libtiff/libharu aren't playing nicely (missing mangled syms?) >> >> https://open.cdash.org/viewBuildError.php?buildid=5248537 >> https://open.cdash.org/viewBuildError.php?buildid=5248527 >> >> Allie >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q= >> Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> https://paraview.org/mailman/listinfo/paraview-developers >> >> > > > -- > Ken Martin PhD > Distinguished Engineer > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > > This communication, including all attachments, contains confidential and > legally privileged information, and it is intended only for the use of the > addressee. Access to this email by anyone else is unauthorized. If you are > not the intended recipient, any disclosure, copying, distribution or any > action taken in reliance on it is prohibited and may be unlawful. If you > received this communication in error please notify us immediately and > destroy the original message. Thank you. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://paraview.org/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From allison.vacanti at kitware.com Wed Feb 7 07:06:59 2018 From: allison.vacanti at kitware.com (Allie Vacanti) Date: Wed, 7 Feb 2018 07:06:59 -0500 Subject: [Paraview-developers] VTK third party changes breaking paraview dashboards In-Reply-To: References: Message-ID: Looking much better this morning, thanks for the fixes, Ben and Shawn! I'm looking into the other failures, should have something soon. On Tue, Feb 6, 2018 at 10:59 AM, Shawn Waldon wrote: > I've installed eigen3-devel on vall, so that should go away and I'm > working on the patch for libharu. > > On Tue, Feb 6, 2018 at 9:36 AM, Ken Martin wrote: > >> I ran into the tiff haru issue a few days ago as well. I think there are >> also some CMake issues on Win32 as I had to locally modify some cmakelists >> to get cmake to run ala a hack ... otherwise cmake complains about an >> incorrect number of arguments to set_target_properties probably because the >> SO_COMPATVERSION is empty. >> >> diff --git a/ThirdParty/tiff/vtktiff/libtiff/CMakeLists.txt >> b/ThirdParty/tiff/vtktiff/libtiff/CMakeLists.txtindex 15fd8ad..bc37dfa >> 100644 >> --- a/ThirdParty/tiff/vtktiff/libtiff/CMakeLists.txt >> +++ b/ThirdParty/tiff/vtktiff/libtiff/CMakeLists.txt >> @@ -162,7 +162,7 @@ endif () >> if(cxx) >> add_library(tiffxx ${tiffxx_SOURCES} ${tiffxx_HEADERS}) >> target_link_libraries(tiffxx tiff) >> - set_target_properties(tiffxx PROPERTIES SOVERSION ${SO_COMPATVERSION}) >> +# set_target_properties(tiffxx PROPERTIES SOVERSION ${SO_COMPATVERSION}) >> if(NOT CYGWIN) >> # This property causes shared libraries on Linux to have the full >> version >> # encoded into their final filename. We disable this on Cygwin >> because >> >> >> >> On Tue, Feb 6, 2018 at 9:10 AM, Allie Vacanti < >> allison.vacanti at kitware.com> wrote: >> >>> Hi guys, >>> >>> Looks like there are some dashboard issues on paraview related to the >>> recent third party changes. Is anyone working on these? >>> >>> Looks like vall needs Eigen3 installed: >>> >>> https://open.cdash.org/viewConfigure.php?buildid=5248512 >>> >>> The new libtiff/libharu aren't playing nicely (missing mangled syms?) >>> >>> https://open.cdash.org/viewBuildError.php?buildid=5248537 >>> https://open.cdash.org/viewBuildError.php?buildid=5248527 >>> >>> Allie >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Search the list archives at: http://markmail.org/search/?q= >>> Paraview-developers >>> >>> Follow this link to subscribe/unsubscribe: >>> https://paraview.org/mailman/listinfo/paraview-developers >>> >>> >> >> >> -- >> Ken Martin PhD >> Distinguished Engineer >> Kitware Inc. >> 28 Corporate Drive >> >> Clifton Park NY 12065 >> >> >> This communication, including all attachments, contains confidential and >> legally privileged information, and it is intended only for the use of the >> addressee. Access to this email by anyone else is unauthorized. If you are >> not the intended recipient, any disclosure, copying, distribution or any >> action taken in reliance on it is prohibited and may be unlawful. If you >> received this communication in error please notify us immediately and >> destroy the original message. Thank you. >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q= >> Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> https://paraview.org/mailman/listinfo/paraview-developers >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Feb 7 10:07:36 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 7 Feb 2018 10:07:36 -0500 Subject: [Paraview-developers] New warning (error) In-Reply-To: References: <371f24fc03544f7ea32b6a402c7d995b@ES01AMSNLNT.srn.sandia.gov> Message-ID: Alan, The following MR should fix this issue. Do you think it's possible for you to test before this gets merged? https://gitlab.kitware.com/paraview/paraview/merge_requests/2225 Thanks Utkarsh On Tue, Jan 30, 2018 at 1:40 PM, Utkarsh Ayachit wrote: > I suspect it's due to [1]. I'll take a look. The error messages just > need to be ignored. > > [1] https://gitlab.kitware.com/paraview/paraview/merge_requests/2158 > > On Tue, Jan 30, 2018 at 1:22 PM, Scott, W Alan wrote: >> Superbuild, from a pull yesterday, now has the following warning ? error. >> Is this known? Linux, ParaView: v5.4.1-1298-gd9b9f5a, Superbuild: >> v5.4.1-153-g3453527, local server. >> >> >> >> QXcbConnection: XCB error: 148 (Unknown), sequence: 176, resource id: 0, >> major code: 140 (Unknown), minor code: 20 >> >> >> >> Thanks, >> >> >> >> Alan >> >> >> >> -------------------------------------------------------- >> >> W. Alan Scott >> >> ParaView Support Manager >> >> >> >> SAIC >> >> Sandia National Laboratories, MS 0807 >> >> Org 9326 - Building 880 A1-K >> >> (505) 284-0932 FAX (505) 284-5619 >> >> >> >> The most exciting phrase to hear in science >> >> is not "Eureka!" but "That's funny..." -- Isaac Asimov >> >> --------------------------------------------------------- >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> https://paraview.org/mailman/listinfo/paraview-developers >> From d.e.tuthill-jones at durham.ac.uk Thu Feb 8 06:08:28 2018 From: d.e.tuthill-jones at durham.ac.uk (TUTHILL-JONES, DAN E. (Student)) Date: Thu, 8 Feb 2018 11:08:28 +0000 Subject: [Paraview-developers] Custom plugin drop down list Message-ID: Hi, Firstly apologies if this is the wrong place to post this king of thing. I'm currently working on a reader plugin for paraview but I'm having a few issues with writing the XML for the GUI. the files I'm using contain multiple separate datasets and I'd like them to appear in a drop down box of which only one is selectable. I've been looking at the wiki page here: https://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Adding_GUI_Parameters and various posts here but haven't been able to get exactly what I want working. I did manage to get the other drop down list working (the one where you can select/deselect each item). This uses some set and get methods in my reader's class and seemed to work very well. Unfortunately I haven't been able to apply this to the drop down box where only a single item is selectable. Could anybody explain to me how the XML works or point me towards a thorough resource? Thanks, Dan ParaView/Plugin HowTo - KitwarePublic www.paraview.org Introduction. ParaView comes with plethora of functionality bundled in: several readers, multitude of filters, quite a few different types of views etc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Fri Feb 9 14:17:57 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 9 Feb 2018 19:17:57 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: New warning (error) In-Reply-To: References: <371f24fc03544f7ea32b6a402c7d995b@ES01AMSNLNT.srn.sandia.gov> Message-ID: <6740776E-548A-4891-892A-B8147221B78E@sandia.gov> Still trying to get a good build... I'm working on it... Alan ?On 2/7/18, 8:07 AM, "Utkarsh Ayachit" wrote: Alan, The following MR should fix this issue. Do you think it's possible for you to test before this gets merged? https://gitlab.kitware.com/paraview/paraview/merge_requests/2225 Thanks Utkarsh On Tue, Jan 30, 2018 at 1:40 PM, Utkarsh Ayachit wrote: > I suspect it's due to [1]. I'll take a look. The error messages just > need to be ignored. > > [1] https://gitlab.kitware.com/paraview/paraview/merge_requests/2158 > > On Tue, Jan 30, 2018 at 1:22 PM, Scott, W Alan wrote: >> Superbuild, from a pull yesterday, now has the following warning ? error. >> Is this known? Linux, ParaView: v5.4.1-1298-gd9b9f5a, Superbuild: >> v5.4.1-153-g3453527, local server. >> >> >> >> QXcbConnection: XCB error: 148 (Unknown), sequence: 176, resource id: 0, >> major code: 140 (Unknown), minor code: 20 >> >> >> >> Thanks, >> >> >> >> Alan >> >> >> >> -------------------------------------------------------- >> >> W. Alan Scott >> >> ParaView Support Manager >> >> >> >> SAIC >> >> Sandia National Laboratories, MS 0807 >> >> Org 9326 - Building 880 A1-K >> >> (505) 284-0932 FAX (505) 284-5619 >> >> >> >> The most exciting phrase to hear in science >> >> is not "Eureka!" but "That's funny..." -- Isaac Asimov >> >> --------------------------------------------------------- >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> https://paraview.org/mailman/listinfo/paraview-developers >> From utkarsh.ayachit at kitware.com Sat Feb 10 07:24:30 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sat, 10 Feb 2018 07:24:30 -0500 Subject: [Paraview-developers] Custom plugin drop down list In-Reply-To: References: Message-ID: Dan, If I understand your use-case correctly, what you can do is a combination of StringListDomain with an info property that returns the available options e.g. Load the grid with the given dimensions. Any arrays that conform to these dimensions will be loaded. Hope that helps, Utkarsh On Thu, Feb 8, 2018 at 6:08 AM, TUTHILL-JONES, DAN E. (Student) < d.e.tuthill-jones at durham.ac.uk> wrote: > Hi, > > > Firstly apologies if this is the wrong place to post this king of thing. > > I'm currently working on a reader plugin for paraview but I'm having a few > issues with writing the XML for the GUI. the files I'm using contain > multiple separate datasets and I'd like them to appear in a drop down box > of which only one is selectable. I've been looking at the wiki page here: > https://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Adding_GUI_Parameters and > various posts here but haven't been able to get exactly what I want > working. I did manage to get the other drop down list working (the one > where you can select/deselect each item). This uses some set and get > methods in my reader's class and seemed to work very well. Unfortunately I > haven't been able to apply this to the drop down box where only a single > item is selectable. > > > Could anybody explain to me how the XML works or point me towards a > thorough resource? > > > Thanks, > > Dan > ParaView/Plugin HowTo - KitwarePublic > > www.paraview.org > Introduction. ParaView comes with plethora of functionality bundled in: > several readers, multitude of filters, quite a few different types of views > etc. > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://paraview.org/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Sun Feb 11 23:52:12 2018 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Mon, 12 Feb 2018 05:52:12 +0100 Subject: [Paraview-developers] ParaView and VTK course in march and april 2018 in France Message-ID: Hello VTK and ParaView community Kitware will be holding VTK/ParaView courses on march and april 2017 in Lyon, France. 1/ Initial Trainings, VTK on march 13 2018 and ParaView on march 14 2018 Registration and details : VTK and ParaView User 2/ Advanced Trainings, VTK on april 4 2018 and ParaView on april 5 2018. Registration and details: VTK Advanced and ParaView Advanced Note that the course will be taught in English unless all atendees speaks French. If you have any question, please contact us at formations at http://www.kitware.fr Other trainings sessions that you may find interesting (CMake, ITK, 3D Slicer and OpenCV) are announced here . Best Regards, Mathieu Westphal -------------- next part -------------- An HTML attachment was scrubbed... URL: From d.e.tuthill-jones at durham.ac.uk Wed Feb 14 12:17:57 2018 From: d.e.tuthill-jones at durham.ac.uk (TUTHILL-JONES, DAN E. (Student)) Date: Wed, 14 Feb 2018 17:17:57 +0000 Subject: [Paraview-developers] Help using a 3D Widget in a plugin Message-ID: Hi again. I have written a paraview reader plugin which supports loading my file format in various resolutions. I've got the reader to display a drop down box which allows you to select which resolution to load. As an extension to this, I'd like to be able to select an area using the box 3D widget. Once the area is select, then I'd like to be able to load it in a higher resolution. Filters such as clip use these widgets however the XML for these doesn't seem to contain values for the implicit functions/3D widgets that actually appear, just the drop down box to select which type to use. I've spent a long time looking in to how I can implement this area selection with a box widget but I haven't found much. Could anybody please point me in the right direction? Thanks again, Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.thompson at kitware.com Thu Feb 15 00:31:01 2018 From: david.thompson at kitware.com (David Thompson) Date: Thu, 15 Feb 2018 00:31:01 -0500 Subject: [Paraview-developers] Infinite recursion during error message printout Message-ID: <9366B557-D40F-4E0F-AC46-9D630829D949@kitware.com> Hi all, I'm developing a PV-branded app and have run into an issue where my code calls vtkErrorMacro() and it recursively reprints the error message until the stack is exhausted. A partial stack trace is below (all but the bottom-most entry repeat until a crash). You can see that the vtkErrorMacro call invokes vtkOutputWindow::DisplayText, which invokes a vtkCommand::MessageEvent event. ParaView's progress handler listens for the event and then re-broadcasts the message to the vtkOutputWindow, which invokes the same event again. There do appear to be 2 SubjectHelpers involved (0x0000000129905c90 and 0x00000001294fba80); I'm not sure if this is significant but am hoping whoever knows about the pqProgressManager will understand what's going on. Any ideas? Thanks, David ... frame #21868: 0x000000010b97aeb6 libvtkCommon-pv5.4.1.dylib`vtkOutputWindow::DisplayErrorText(this=0x0000000117122d20, txt="ERROR: In /stage/build/cmb/qt5-superbuild/superbuild/cmb/src/thirdparty/smtk/smtk/extension/paraview/server/vtkSMTKAttributeReader.cxx, line 119\nvtkSMTKAttributeReader (0x12e819e80): Could not read \"/stage/source/cmb/6/data/simulation-workflows/ACE3P/Omega3P/internal/test/pillbox4-test2.crf\"\n\n") at vtkOutputWindow.cxx:114 frame #21869: 0x0000000100de1d9b libvtkpqCore-pv5.4.1.dylib`pqProgressManager::onMessage(this=0x0000000117037710, caller=0x00000001294abe30) at pqProgressManager.cxx:247 frame #21870: 0x0000000100e4f1dc libvtkpqCore-pv5.4.1.dylib`pqProgressManager::qt_static_metacall(_o=0x0000000117037710, _c=InvokeMetaMethod, _id=16, _a=0x00007ffeefbf8cb0) at moc_pqProgressManager.cpp:155 frame #21871: 0x00000001038d14fb QtCore`QMetaObject::activate(QObject*, int, int, void**) + 2923 frame #21872: 0x0000000100e457bc libvtkpqCore-pv5.4.1.dylib`pqCoreUtilitiesEventHelper::eventInvoked(this=0x00000001299036a0, _t1=0x00000001294abe30, _t2=97, _t3=0x000000012c5cb950) at moc_pqCoreUtilities.cpp:128 frame #21873: 0x0000000100d7121d libvtkpqCore-pv5.4.1.dylib`pqCoreUtilitiesEventHelper::executeEvent(this=0x00000001299036a0, obj=0x00000001294abe30, eventid=97, calldata=0x000000012c5cb950) at pqCoreUtilities.cxx:190 frame #21874: 0x0000000100d724ba libvtkpqCore-pv5.4.1.dylib`vtkObject::vtkClassMemberCallback::operator(this=0x0000000129906020, caller=0x00000001294abe30, event=97, calldata=0x000000012c5cb950)(vtkObject*, unsigned long, void*) at vtkObject.h:385 frame #21875: 0x000000010b9759bf libvtkCommon-pv5.4.1.dylib`vtkObjectCommandInternal::Execute(this=0x0000000129906070, caller=0x00000001294abe30, eventId=97, callData=0x000000012c5cb950) at vtkObject.cxx:920 frame #21876: 0x000000010b973454 libvtkCommon-pv5.4.1.dylib`vtkSubjectHelper::InvokeEvent(this=0x0000000129905c90, event=97, callData=0x000000012c5cb950, self=0x00000001294abe30) at vtkObject.cxx:616 frame #21877: 0x000000010b97485f libvtkCommon-pv5.4.1.dylib`vtkObject::InvokeEvent(this=0x00000001294abe30, event=97, callData=0x000000012c5cb950) at vtkObject.cxx:785 frame #21878: 0x00000001049d2358 libvtkPVClientServer-pv5.4.1.dylib`vtkPVProgressHandler::RefreshMessage(this=0x00000001294abe30, message="ERROR: In /stage/build/cmb/qt5-superbuild/superbuild/cmb/src/thirdparty/smtk/smtk/extension/paraview/server/vtkSMTKAttributeReader.cxx, line 119\nvtkSMTKAttributeReader (0x12e819e80): Could not read \"/stage/source/cmb/6/data/simulation-workflows/ACE3P/Omega3P/internal/test/pillbox4-test2.crf\"\n\n") at vtkPVProgressHandler.cxx:501 frame #21879: 0x00000001049d05a5 libvtkPVClientServer-pv5.4.1.dylib`vtkPVProgressHandler::OnMessageEvent(this=0x00000001294abe30, (null)=0x0000000117122d20, eventid=97, calldata=0x000000012c5cb950) at vtkPVProgressHandler.cxx:463 frame #21880: 0x00000001049d5c8a libvtkPVClientServer-pv5.4.1.dylib`vtkObject::vtkClassMemberCallback::operator(this=0x00000001293f1390, caller=0x0000000117122d20, event=97, calldata=0x000000012c5cb950)(vtkObject*, unsigned long, void*) at vtkObject.h:385 frame #21881: 0x000000010b9759bf libvtkCommon-pv5.4.1.dylib`vtkObjectCommandInternal::Execute(this=0x00000001294f26e0, caller=0x0000000117122d20, eventId=97, callData=0x000000012c5cb950) at vtkObject.cxx:920 frame #21882: 0x000000010b973454 libvtkCommon-pv5.4.1.dylib`vtkSubjectHelper::InvokeEvent(this=0x00000001294fba80, event=97, callData=0x000000012c5cb950, self=0x0000000117122d20) at vtkObject.cxx:616 frame #21883: 0x000000010b97485f libvtkCommon-pv5.4.1.dylib`vtkObject::InvokeEvent(this=0x0000000117122d20, event=97, callData=0x000000012c5cb950) at vtkObject.cxx:785 frame #21884: 0x000000010b97ac73 libvtkCommon-pv5.4.1.dylib`vtkOutputWindow::DisplayText(this=0x0000000117122d20, txt="ERROR: In /stage/build/cmb/qt5-superbuild/superbuild/cmb/src/thirdparty/smtk/smtk/extension/paraview/server/vtkSMTKAttributeReader.cxx, line 119\nvtkSMTKAttributeReader (0x12e819e80): Could not read \"/stage/source/cmb/6/data/simulation-workflows/ACE3P/Omega3P/internal/test/pillbox4-test2.crf\"\n\n") at vtkOutputWindow.cxx:109 frame #21885: 0x000000010b97aeb6 libvtkCommon-pv5.4.1.dylib`vtkOutputWindow::DisplayErrorText(this=0x0000000117122d20, txt="ERROR: In /stage/build/cmb/qt5-superbuild/superbuild/cmb/src/thirdparty/smtk/smtk/extension/paraview/server/vtkSMTKAttributeReader.cxx, line 119\nvtkSMTKAttributeReader (0x12e819e80): Could not read \"/stage/source/cmb/6/data/simulation-workflows/ACE3P/Omega3P/internal/test/pillbox4-test2.crf\"\n\n") at vtkOutputWindow.cxx:114 frame #21886: 0x000000010b97a78c libvtkCommon-pv5.4.1.dylib`vtkOutputWindowDisplayErrorText(message="ERROR: In /stage/build/cmb/qt5-superbuild/superbuild/cmb/src/thirdparty/smtk/smtk/extension/paraview/server/vtkSMTKAttributeReader.cxx, line 119\nvtkSMTKAttributeReader (0x12e819e80): Could not read \"/stage/source/cmb/6/data/simulation-workflows/ACE3P/Omega3P/internal/test/pillbox4-test2.crf\"\n\n") at vtkOutputWindow.cxx:37 frame #21887: 0x0000000125e22ac3 libsmtkPVServerExtPlugin.dylib`vtkSMTKAttributeReader::LoadFile(this=0x000000012e819e80) at vtkSMTKAttributeReader.cxx:119 ... From utkarsh.ayachit at kitware.com Thu Feb 15 08:57:26 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 15 Feb 2018 08:57:26 -0500 Subject: [Paraview-developers] Infinite recursion during error message printout In-Reply-To: <9366B557-D40F-4E0F-AC46-9D630829D949@kitware.com> References: <9366B557-D40F-4E0F-AC46-9D630829D949@kitware.com> Message-ID: David, Can you see if these resolve it? https://gitlab.kitware.com/vtk/vtk/merge_requests/3927 https://gitlab.kitware.com/paraview/paraview/merge_requests/2246 Utkarsh On Thu, Feb 15, 2018 at 12:31 AM, David Thompson wrote: > Hi all, > > I'm developing a PV-branded app and have run into an issue where my code calls vtkErrorMacro() and it recursively reprints the error message until the stack is exhausted. A partial stack trace is below (all but the bottom-most entry repeat until a crash). You can see that the vtkErrorMacro call invokes vtkOutputWindow::DisplayText, which invokes a vtkCommand::MessageEvent event. ParaView's progress handler listens for the event and then re-broadcasts the message to the vtkOutputWindow, which invokes the same event again. > > There do appear to be 2 SubjectHelpers involved (0x0000000129905c90 and 0x00000001294fba80); I'm not sure if this is significant but am hoping whoever knows about the pqProgressManager will understand what's going on. > > Any ideas? > > Thanks, > David > > ... > frame #21868: 0x000000010b97aeb6 libvtkCommon-pv5.4.1.dylib`vtkOutputWindow::DisplayErrorText(this=0x0000000117122d20, txt="ERROR: In /stage/build/cmb/qt5-superbuild/superbuild/cmb/src/thirdparty/smtk/smtk/extension/paraview/server/vtkSMTKAttributeReader.cxx, line 119\nvtkSMTKAttributeReader (0x12e819e80): Could not read \"/stage/source/cmb/6/data/simulation-workflows/ACE3P/Omega3P/internal/test/pillbox4-test2.crf\"\n\n") at vtkOutputWindow.cxx:114 > frame #21869: 0x0000000100de1d9b libvtkpqCore-pv5.4.1.dylib`pqProgressManager::onMessage(this=0x0000000117037710, caller=0x00000001294abe30) at pqProgressManager.cxx:247 > frame #21870: 0x0000000100e4f1dc libvtkpqCore-pv5.4.1.dylib`pqProgressManager::qt_static_metacall(_o=0x0000000117037710, _c=InvokeMetaMethod, _id=16, _a=0x00007ffeefbf8cb0) at moc_pqProgressManager.cpp:155 > frame #21871: 0x00000001038d14fb QtCore`QMetaObject::activate(QObject*, int, int, void**) + 2923 > frame #21872: 0x0000000100e457bc libvtkpqCore-pv5.4.1.dylib`pqCoreUtilitiesEventHelper::eventInvoked(this=0x00000001299036a0, _t1=0x00000001294abe30, _t2=97, _t3=0x000000012c5cb950) at moc_pqCoreUtilities.cpp:128 > frame #21873: 0x0000000100d7121d libvtkpqCore-pv5.4.1.dylib`pqCoreUtilitiesEventHelper::executeEvent(this=0x00000001299036a0, obj=0x00000001294abe30, eventid=97, calldata=0x000000012c5cb950) at pqCoreUtilities.cxx:190 > frame #21874: 0x0000000100d724ba libvtkpqCore-pv5.4.1.dylib`vtkObject::vtkClassMemberCallback::operator(this=0x0000000129906020, caller=0x00000001294abe30, event=97, calldata=0x000000012c5cb950)(vtkObject*, unsigned long, void*) at vtkObject.h:385 > frame #21875: 0x000000010b9759bf libvtkCommon-pv5.4.1.dylib`vtkObjectCommandInternal::Execute(this=0x0000000129906070, caller=0x00000001294abe30, eventId=97, callData=0x000000012c5cb950) at vtkObject.cxx:920 > frame #21876: 0x000000010b973454 libvtkCommon-pv5.4.1.dylib`vtkSubjectHelper::InvokeEvent(this=0x0000000129905c90, event=97, callData=0x000000012c5cb950, self=0x00000001294abe30) at vtkObject.cxx:616 > frame #21877: 0x000000010b97485f libvtkCommon-pv5.4.1.dylib`vtkObject::InvokeEvent(this=0x00000001294abe30, event=97, callData=0x000000012c5cb950) at vtkObject.cxx:785 > frame #21878: 0x00000001049d2358 libvtkPVClientServer-pv5.4.1.dylib`vtkPVProgressHandler::RefreshMessage(this=0x00000001294abe30, message="ERROR: In /stage/build/cmb/qt5-superbuild/superbuild/cmb/src/thirdparty/smtk/smtk/extension/paraview/server/vtkSMTKAttributeReader.cxx, line 119\nvtkSMTKAttributeReader (0x12e819e80): Could not read \"/stage/source/cmb/6/data/simulation-workflows/ACE3P/Omega3P/internal/test/pillbox4-test2.crf\"\n\n") at vtkPVProgressHandler.cxx:501 > frame #21879: 0x00000001049d05a5 libvtkPVClientServer-pv5.4.1.dylib`vtkPVProgressHandler::OnMessageEvent(this=0x00000001294abe30, (null)=0x0000000117122d20, eventid=97, calldata=0x000000012c5cb950) at vtkPVProgressHandler.cxx:463 > frame #21880: 0x00000001049d5c8a libvtkPVClientServer-pv5.4.1.dylib`vtkObject::vtkClassMemberCallback::operator(this=0x00000001293f1390, caller=0x0000000117122d20, event=97, calldata=0x000000012c5cb950)(vtkObject*, unsigned long, void*) at vtkObject.h:385 > frame #21881: 0x000000010b9759bf libvtkCommon-pv5.4.1.dylib`vtkObjectCommandInternal::Execute(this=0x00000001294f26e0, caller=0x0000000117122d20, eventId=97, callData=0x000000012c5cb950) at vtkObject.cxx:920 > frame #21882: 0x000000010b973454 libvtkCommon-pv5.4.1.dylib`vtkSubjectHelper::InvokeEvent(this=0x00000001294fba80, event=97, callData=0x000000012c5cb950, self=0x0000000117122d20) at vtkObject.cxx:616 > frame #21883: 0x000000010b97485f libvtkCommon-pv5.4.1.dylib`vtkObject::InvokeEvent(this=0x0000000117122d20, event=97, callData=0x000000012c5cb950) at vtkObject.cxx:785 > frame #21884: 0x000000010b97ac73 libvtkCommon-pv5.4.1.dylib`vtkOutputWindow::DisplayText(this=0x0000000117122d20, txt="ERROR: In /stage/build/cmb/qt5-superbuild/superbuild/cmb/src/thirdparty/smtk/smtk/extension/paraview/server/vtkSMTKAttributeReader.cxx, line 119\nvtkSMTKAttributeReader (0x12e819e80): Could not read \"/stage/source/cmb/6/data/simulation-workflows/ACE3P/Omega3P/internal/test/pillbox4-test2.crf\"\n\n") at vtkOutputWindow.cxx:109 > frame #21885: 0x000000010b97aeb6 libvtkCommon-pv5.4.1.dylib`vtkOutputWindow::DisplayErrorText(this=0x0000000117122d20, txt="ERROR: In /stage/build/cmb/qt5-superbuild/superbuild/cmb/src/thirdparty/smtk/smtk/extension/paraview/server/vtkSMTKAttributeReader.cxx, line 119\nvtkSMTKAttributeReader (0x12e819e80): Could not read \"/stage/source/cmb/6/data/simulation-workflows/ACE3P/Omega3P/internal/test/pillbox4-test2.crf\"\n\n") at vtkOutputWindow.cxx:114 > frame #21886: 0x000000010b97a78c libvtkCommon-pv5.4.1.dylib`vtkOutputWindowDisplayErrorText(message="ERROR: In /stage/build/cmb/qt5-superbuild/superbuild/cmb/src/thirdparty/smtk/smtk/extension/paraview/server/vtkSMTKAttributeReader.cxx, line 119\nvtkSMTKAttributeReader (0x12e819e80): Could not read \"/stage/source/cmb/6/data/simulation-workflows/ACE3P/Omega3P/internal/test/pillbox4-test2.crf\"\n\n") at vtkOutputWindow.cxx:37 > frame #21887: 0x0000000125e22ac3 libsmtkPVServerExtPlugin.dylib`vtkSMTKAttributeReader::LoadFile(this=0x000000012e819e80) at vtkSMTKAttributeReader.cxx:119 > ... > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview-developers From david.thompson at kitware.com Thu Feb 15 22:40:46 2018 From: david.thompson at kitware.com (David Thompson) Date: Thu, 15 Feb 2018 22:40:46 -0500 Subject: [Paraview-developers] Infinite recursion during error message printout In-Reply-To: References: <9366B557-D40F-4E0F-AC46-9D630829D949@kitware.com> Message-ID: > Can you see if these resolve it? > > https://gitlab.kitware.com/vtk/vtk/merge_requests/3927 > https://gitlab.kitware.com/paraview/paraview/merge_requests/2246 Nope, but thanks for the suggestion. David From daanvanvugt at gmail.com Fri Feb 16 06:03:49 2018 From: daanvanvugt at gmail.com (Daan van Vugt) Date: Fri, 16 Feb 2018 12:03:49 +0100 Subject: [Paraview-developers] Announcement: Paraview python file readers Message-ID: Hi everyone, I have created a repository containing some updates to the python filter generator that Utkarsh has made a few years ago, specialized towards using it for file readers (with time support). This might be of use to some of you. https://github.com/Exteris/paraview-python-file-reader It contains a simple example for a time series paraview python file reader with the python programmable filter extension. Additionally for those who have hdf5 files I describe how to add h5py to your ParaView. Best, Daan van Vugt -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Feb 16 21:06:30 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 16 Feb 2018 21:06:30 -0500 Subject: [Paraview-developers] Announcement: Paraview python file readers In-Reply-To: References: Message-ID: Thanks for sharing, Daan. Just one correction, the python filter generator was created by Pat Marion [1]. Utkarsh [1] https://blog.kitware.com/easy-customization-of-the-paraview-python-programmable-filter-property-panel/ On Fri, Feb 16, 2018 at 6:03 AM, Daan van Vugt wrote: > Hi everyone, > > I have created a repository containing some updates to the python filter > generator that Utkarsh has made a few years ago, specialized towards using > it for file readers (with time support). > This might be of use to some of you. > > https://github.com/Exteris/paraview-python-file-reader > > > It contains a simple example for a time series paraview python file reader > with the python programmable filter extension. Additionally for those who > have hdf5 files I describe how to add h5py to your ParaView. > > > Best, > Daan van Vugt > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview-developers > From utkarsh.ayachit at kitware.com Sat Feb 17 09:42:53 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sat, 17 Feb 2018 09:42:53 -0500 Subject: [Paraview-developers] Infinite recursion during error message printout In-Reply-To: References: <9366B557-D40F-4E0F-AC46-9D630829D949@kitware.com> Message-ID: David, are you sure about that? Can you try the latest ParaView master again? I was seeing something similar with another custom app the other day, but today with latest ParaView master, I don't see it anymore. Utkarsh On Thu, Feb 15, 2018 at 10:40 PM, David Thompson wrote: >> Can you see if these resolve it? >> >> https://gitlab.kitware.com/vtk/vtk/merge_requests/3927 >> https://gitlab.kitware.com/paraview/paraview/merge_requests/2246 > > Nope, but thanks for the suggestion. > > David From david.thompson at kitware.com Sun Feb 18 17:40:12 2018 From: david.thompson at kitware.com (David Thompson) Date: Sun, 18 Feb 2018 17:40:12 -0500 Subject: [Paraview-developers] Infinite recursion during error message printout In-Reply-To: References: <9366B557-D40F-4E0F-AC46-9D630829D949@kitware.com> Message-ID: <2034BB44-527F-455F-B5FC-CAB6AA400A1B@kitware.com> Hi Utkarsh, > are you sure about that? Well, yes, I'm pretty sure I didn't just imagine updating to PV master. :-) > Can you try the latest ParaView master again? Alright, I've tried a newer master (fbc095e95b) and it works, at least on one machine. I'll verify on my desktop during the week. Thanks! David From andy.bauer at kitware.com Mon Feb 19 10:26:18 2018 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 19 Feb 2018 10:26:18 -0500 Subject: [Paraview-developers] VTK xml formats with external geometry references In-Reply-To: References: Message-ID: Hi Mark, I would think that this is doable without an extreme amount of effort. This wouldn't be needed for image data or rectilinear grids since the grid information in them is tiny compared to the field information. It could definitely be useful for polydata, unstructured grids and maybe even structured grids. I think the main thing in order to get this done would be to find a champion and/or funding source for the work. In the next couple of months we'll be starting work on a reader framework that this may fit nicely into but I'll have to get deeper into that work to see. Best, Andy On Wed, Jan 24, 2018 at 3:38 PM, Mark Olesen wrote: > I realize this discussion pops up at regular intervals, but I haven't seen > it for a while and I have some use cases that would really need it. > > Seeing that there are multiblock and parallel VTK file formats such as > .vtm, .pvtp, .pvtu serving as collections for externally defined data, I > was wondering if it would be feasible to use a similar idea to hold the > geometry separate from the cell/point data? > AFAIK this isn't really something that the normal (eg, vtp, vtu) formats > support, but something that would really help me. > > A fairly common situation is sampling to predefined surface that is reused > for different times and for different fields. At the moment I have the > choice of writing geometry+data for each sampled field at each time value. > This can lead to fairly excessive disk usage. > > To avoid this duplicate geometry, I would need a complete (non-trivial) > rewrite of my sampling. But even after that I would still have geometry > duplication if the geometry is not changing in time. I also lose the > ability to easily remove unneeded fields a posteriori. > > The desired meta-format might look like this: > > > > > > > > > > > > > > > This is somewhat like a pvtu file, but with the geometry and data being > able to reside in separate files. > > The "abc.vtu" base geometry is just a regular VTU file with or without an > fields. > > The "abc_T.dvtu" (dvtu for a data vtu) has data but no geometry. For > sanity checks it should have the basic sizing information (NumberOfPoints, > NumberOfCells). To be thoroughly redundant, I guess a geometry file could > also be specifically named in the respective dvtu file. > > Is there any thing within the current framework that could be easily > leveraged to solve such a problem, and is such a way that it eventually be > part of the VTK file-format collections. Is there actually a VTK format > that already fits the bill and I just haven't found it? > I know that the EnSight format covers many of these points, but a pure VTK > solution is what I'm looking for since it would be important to have > parallel file format output as per PUnstructuredGrid etc. > > Cheers, > /mark > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://paraview.org/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From edo.paskino at gmail.com Mon Feb 19 10:27:47 2018 From: edo.paskino at gmail.com (Edoardo Pasca) Date: Mon, 19 Feb 2018 15:27:47 +0000 Subject: [Paraview-developers] failure to load plugin Message-ID: Hi all. I've developed a plugin for paraview. It builds fine but loading it I get this mysterious error. Anyone can shed a light? ERROR: In C:\bbd\7cc78367\source-paraview\ParaViewCore\ClientServerCore\Core\vtkPVPluginLoader.cxx, line 388 vtkPVPluginLoader (000001E430404720): T Thanks Edoardo -- Edo I know you think you understand what you thought I said, but I'm not sure you realize that what you heard is not what I meant (prob. Alan Greenspan) :wq -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Feb 19 10:44:31 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 19 Feb 2018 10:44:31 -0500 Subject: [Paraview-developers] failure to load plugin In-Reply-To: References: Message-ID: Edoardo, I suspect you are building the plugin against a build of ParaView you have created and you are attempting to load it in a different ParaView binary. To do this correctly, your build of ParaView must either: * exactly match the other ParaView binary, OR * you must load the plugin in the ParaView binary against which the plugin was built HTH, Cory On Mon, Feb 19, 2018 at 10:27 AM, Edoardo Pasca wrote: > Hi all. > > I've developed a plugin for paraview. It builds fine but loading it I get > this mysterious error. Anyone can shed a light? > > ERROR: In C:\bbd\7cc78367\source-paraview\ParaViewCore\ > ClientServerCore\Core\vtkPVPluginLoader.cxx, line 388 > > vtkPVPluginLoader (000001E430404720): T > > Thanks > > Edoardo > > -- > Edo > I know you think you understand what you thought I said, but I'm not sure > you realize that what you heard is not what I meant (prob. Alan Greenspan) > :wq > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview-developers > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Mon Feb 19 11:00:33 2018 From: berk.geveci at kitware.com (Berk Geveci) Date: Mon, 19 Feb 2018 11:00:33 -0500 Subject: [Paraview-developers] VTK xml formats with external geometry references In-Reply-To: References: Message-ID: Hi Mark, Depending on how much code you want to write and what you want to do with files, this is doable. 0. For unstructured grids, the Exodus format supports this out of box. 1. The simplest solution past Exodus would probably be to write some simple Python reader that manages arrays from various files. This could easily support any format. You would simple have some files that have geometry, others that have arrays... 2. If you want a single file, the .vtx formats actually support time with the option of some arrays not changing over time. At least partially. This was done a long time ago and would have to be update to the new time support. I can provide some guidance if necessary. I am not sure if it would work with the .pvtx 3. If you want multiple files, the pvd reader can be updated to support this. Someone had done this years ago but their changes never made into upstream. 4. The FileSeries reader now supports a json based metafile. That reader can be update to do this as well. It is probably an easier piece of code than the pvd one and it would work with other formats. On Wed, Jan 24, 2018 at 3:38 PM, Mark Olesen wrote: > I realize this discussion pops up at regular intervals, but I haven't seen > it for a while and I have some use cases that would really need it. > > Seeing that there are multiblock and parallel VTK file formats such as > .vtm, .pvtp, .pvtu serving as collections for externally defined data, I > was wondering if it would be feasible to use a similar idea to hold the > geometry separate from the cell/point data? > AFAIK this isn't really something that the normal (eg, vtp, vtu) formats > support, but something that would really help me. > > A fairly common situation is sampling to predefined surface that is reused > for different times and for different fields. At the moment I have the > choice of writing geometry+data for each sampled field at each time value. > This can lead to fairly excessive disk usage. > > To avoid this duplicate geometry, I would need a complete (non-trivial) > rewrite of my sampling. But even after that I would still have geometry > duplication if the geometry is not changing in time. I also lose the > ability to easily remove unneeded fields a posteriori. > > The desired meta-format might look like this: > > > > > > > > > > > > > > > This is somewhat like a pvtu file, but with the geometry and data being > able to reside in separate files. > > The "abc.vtu" base geometry is just a regular VTU file with or without an > fields. > > The "abc_T.dvtu" (dvtu for a data vtu) has data but no geometry. For > sanity checks it should have the basic sizing information (NumberOfPoints, > NumberOfCells). To be thoroughly redundant, I guess a geometry file could > also be specifically named in the respective dvtu file. > > Is there any thing within the current framework that could be easily > leveraged to solve such a problem, and is such a way that it eventually be > part of the VTK file-format collections. Is there actually a VTK format > that already fits the bill and I just haven't found it? > I know that the EnSight format covers many of these points, but a pure VTK > solution is what I'm looking for since it would be important to have > parallel file format output as per PUnstructuredGrid etc. > > Cheers, > /mark > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://paraview.org/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Feb 19 11:21:44 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 19 Feb 2018 11:21:44 -0500 Subject: [Paraview-developers] failure to load plugin In-Reply-To: References: Message-ID: Adding back the list so others can participate in the conversation. On Mon, Feb 19, 2018 at 11:16 AM, Edoardo Pasca wrote: > Thanks Cory. > > I built PV5.4.1 myself but run the binary of 5.4.1 from Kitware. > Yeah, this probably won't work. There has been some effort in the past to provide a proper ParaView SDK so you could build plugins that would run with Kitware's ParaView binaries, but that isn't currently available. > I built my own plugin against 5.4.1. > Actually I've tried also with 5.3.0. The strange thing is that it has > worked in the past. > My bet would be that you got lucky :-) I would expect it to not work. > I'll build 5.4.1 again and my plugin > Again, I don't expect this to run in Kitware's ParaView binaries unless your compiler, built options, dependent library versions, etc., all match up exactly with Kitware's build configuration. Your plugin will run with the 5.4.1 you build, however. Best, Cory > Thanks > > Edoardo > > On Mon, Feb 19, 2018 at 3:44 PM, Cory Quammen > wrote: > >> Edoardo, >> >> I suspect you are building the plugin against a build of ParaView you >> have created and you are attempting to load it in a different ParaView >> binary. To do this correctly, your build of ParaView must either: >> >> * exactly match the other ParaView binary, OR >> * you must load the plugin in the ParaView binary against which the >> plugin was built >> >> HTH, >> Cory >> >> On Mon, Feb 19, 2018 at 10:27 AM, Edoardo Pasca >> wrote: >> >>> Hi all. >>> >>> I've developed a plugin for paraview. It builds fine but loading it I >>> get this mysterious error. Anyone can shed a light? >>> >>> ERROR: In C:\bbd\7cc78367\source-paraview\ParaViewCore\ClientServerCore\Core\vtkPVPluginLoader.cxx, >>> line 388 >>> >>> vtkPVPluginLoader (000001E430404720): T >>> >>> Thanks >>> >>> Edoardo >>> >>> -- >>> Edo >>> I know you think you understand what you thought I said, but I'm not >>> sure you realize that what you heard is not what I meant (prob. Alan >>> Greenspan) >>> :wq >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Search the list archives at: http://markmail.org/search/?q= >>> Paraview-developers >>> >>> Follow this link to subscribe/unsubscribe: >>> https://public.kitware.com/mailman/listinfo/paraview-developers >>> >>> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. >> > > > > -- > Edo > I know you think you understand what you thought I said, but I'm not sure > you realize that what you heard is not what I meant (prob. Alan Greenspan) > :wq > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Mark.Olesen at esi-group.com Mon Feb 19 12:35:28 2018 From: Mark.Olesen at esi-group.com (Mark Olesen) Date: Mon, 19 Feb 2018 18:35:28 +0100 Subject: [Paraview-developers] VTK xml formats with external geometry references In-Reply-To: References: Message-ID: <2d140dc5-c996-754a-b654-fc713c69ee97@esi-group.com> Hi Andy, This was a pleasant surprise. I'll forward the information internally to see if we can help with finding some sponsorship. I also liked Berk's idea. Cheers, /mark On 02/19/18 16:26, Andy Bauer wrote: > Hi Mark, > > I would think that this is doable without an extreme amount of effort. > This wouldn't be needed for image data or rectilinear grids since the > grid information in them is tiny compared to the field information. It > could definitely be useful for polydata, unstructured grids and maybe > even structured grids. I think the main thing in order to get this done > would be to find a champion and/or funding source for the work. In the > next couple of months we'll be starting work on a reader framework that > this may fit nicely into but I'll have to get deeper into that work to see. > > Best, > Andy > > On Wed, Jan 24, 2018 at 3:38 PM, Mark Olesen > wrote: > > I realize this discussion pops up at regular intervals, but I > haven't seen it for a while and I have some use cases that would > really need it. > > Seeing that there are multiblock and parallel VTK file formats such > as .vtm, .pvtp, .pvtu serving as collections for externally defined > data, I was wondering if it would be feasible to use a similar idea > to hold the geometry separate from the cell/point data? > AFAIK this isn't really something that the normal (eg, vtp, vtu) > formats support, but something that would really help me. > > A fairly common situation is sampling to predefined surface that is > reused for different times and for different fields. At the moment I > have the choice of writing geometry+data for each sampled field at > each time value. This can lead to fairly excessive disk usage. > > To avoid this duplicate geometry, I would need a complete > (non-trivial) rewrite of my sampling. But even after that I would > still have geometry duplication if the geometry is not changing in > time. I also lose the ability to easily remove unneeded fields a > posteriori. > > The desired meta-format might look like this: > > > ? > ? ? > ? ? ? > ? ? ? > ? ? ? > ? ? ? > ? ? ? > ? ? ? > ? ? > ? > > > This is somewhat like a pvtu file, but with the geometry and data > being able to reside in separate files. > > The "abc.vtu" base geometry is just a regular VTU file with or > without an fields. > > The "abc_T.dvtu" (dvtu for a data vtu) has data but no geometry. For > sanity checks it should have the basic sizing information > (NumberOfPoints, NumberOfCells). To be thoroughly redundant, I guess > a geometry file could also be specifically named in the respective > dvtu file. > > Is there any thing within the current framework that could be easily > leveraged to solve such a problem, and is such a way that it > eventually be part of the VTK file-format collections. Is there > actually a VTK format that already fits the bill and I just haven't > found it? > I know that the EnSight format covers many of these points, but a > pure VTK solution is what I'm looking for since it would be > important to have parallel file format output as per > PUnstructuredGrid etc. > > Cheers, > /mark > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > > Follow this link to subscribe/unsubscribe: > https://paraview.org/mailman/listinfo/paraview-developers > > > -- Dr Mark OLESEN Principal Engineer, ESI-OpenCFD ESI GmbH | Einsteinring 24 | 85609 Munich | GERMANY Mob. +49 171 9710 149 www.openfoam.com | www.esi-group.com | mark.olesen at esi-group.com From Mark.Olesen at esi-group.com Mon Feb 19 12:42:08 2018 From: Mark.Olesen at esi-group.com (Mark Olesen) Date: Mon, 19 Feb 2018 18:42:08 +0100 Subject: [Paraview-developers] VTK xml formats with external geometry references In-Reply-To: References: Message-ID: <15341b41-6eb9-8c7d-d0be-6e6c77e53337@esi-group.com> Hi Berk, If we can split up geometry/fields etc with a FileSeries, that sounds highly attractive. A json metafile would be a very convenient way of gluing everything together without reinventing the wheel. Cheers, /mark On 02/19/18 17:00, Berk Geveci wrote: > Hi Mark, > > Depending on how much code you want to write and what you want to do > with files, this is doable. > > 0. For unstructured grids, the Exodus format supports this out of box. > > 1. The simplest solution past Exodus would probably be to write some > simple Python reader that manages arrays from various files. This could > easily support any format. You would simple have some files that have > geometry, others that have arrays... > > 2. If you want a single file, the .vtx formats actually support time > with the option of some arrays not changing over time. At least > partially. This was done a long time ago and would have to be update to > the new time support. I can provide some guidance if necessary. I am not > sure if it would work with the .pvtx > > 3. If you want multiple files, the pvd reader can be updated to support > this. Someone had done this years ago but their changes never made into > upstream. > > 4. The FileSeries reader now supports a json based metafile. That reader > can be update to do this as well. It is probably an easier piece of code > than the pvd one and it would work with other formats. > > > > On Wed, Jan 24, 2018 at 3:38 PM, Mark Olesen > wrote: > > I realize this discussion pops up at regular intervals, but I > haven't seen it for a while and I have some use cases that would > really need it. > > Seeing that there are multiblock and parallel VTK file formats such > as .vtm, .pvtp, .pvtu serving as collections for externally defined > data, I was wondering if it would be feasible to use a similar idea > to hold the geometry separate from the cell/point data? > AFAIK this isn't really something that the normal (eg, vtp, vtu) > formats support, but something that would really help me. > > A fairly common situation is sampling to predefined surface that is > reused for different times and for different fields. At the moment I > have the choice of writing geometry+data for each sampled field at > each time value. This can lead to fairly excessive disk usage. > > To avoid this duplicate geometry, I would need a complete > (non-trivial) rewrite of my sampling. But even after that I would > still have geometry duplication if the geometry is not changing in > time. I also lose the ability to easily remove unneeded fields a > posteriori. > > The desired meta-format might look like this: > > > ? > ? ? > ? ? ? > ? ? ? > ? ? ? > ? ? ? > ? ? ? > ? ? ? > ? ? > ? > > > This is somewhat like a pvtu file, but with the geometry and data > being able to reside in separate files. > > The "abc.vtu" base geometry is just a regular VTU file with or > without an fields. > > The "abc_T.dvtu" (dvtu for a data vtu) has data but no geometry. For > sanity checks it should have the basic sizing information > (NumberOfPoints, NumberOfCells). To be thoroughly redundant, I guess > a geometry file could also be specifically named in the respective > dvtu file. > > Is there any thing within the current framework that could be easily > leveraged to solve such a problem, and is such a way that it > eventually be part of the VTK file-format collections. Is there > actually a VTK format that already fits the bill and I just haven't > found it? > I know that the EnSight format covers many of these points, but a > pure VTK solution is what I'm looking for since it would be > important to have parallel file format output as per > PUnstructuredGrid etc. > > Cheers, > /mark > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > > Follow this link to subscribe/unsubscribe: > https://paraview.org/mailman/listinfo/paraview-developers > > > -- Dr Mark OLESEN Principal Engineer, ESI-OpenCFD ESI GmbH | Einsteinring 24 | 85609 Munich | GERMANY Mob. +49 171 9710 149 www.openfoam.com | www.esi-group.com | mark.olesen at esi-group.com From egoli2 at illinois.edu Mon Feb 19 12:59:23 2018 From: egoli2 at illinois.edu (Goli, Elyas) Date: Mon, 19 Feb 2018 17:59:23 +0000 Subject: [Paraview-developers] Rotational Extrude Message-ID: <2014EAF26EC95F49B1ED2B1985E5F8CC381D17E7@CITESMBX5.ad.uillinois.edu> Hi All, I have an axisymmetric 2D model in Paraview in x-y plane. I am trying to use the Rotational Extrude filter to rotate the model about the y-axis and make it a 3D model. However, the filter is iactive. Does any one have an idea of how to solve the issue? Best, Elyas From wascott at sandia.gov Mon Feb 19 13:25:58 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 19 Feb 2018 18:25:58 +0000 Subject: [Paraview-developers] [EXTERNAL] Rotational Extrude In-Reply-To: <2014EAF26EC95F49B1ED2B1985E5F8CC381D17E7@CITESMBX5.ad.uillinois.edu> References: <2014EAF26EC95F49B1ED2B1985E5F8CC381D17E7@CITESMBX5.ad.uillinois.edu> Message-ID: <42460B9A-6D67-4476-9015-D89C21F1376B@sandia.gov> Just a guess - this filter requires 2d polygonal data. What I just did was Wavelet, then Slice. Maybe your data is actually 3d? Try running a slice filter on it first? Mind moving this to the paraview at paraview.org e-mail list, so everyone can see the answer? Thanks, Alan ?On 2/19/18, 11:20 AM, "Paraview-developers on behalf of Goli, Elyas" wrote: Hi All, I have an axisymmetric 2D model in Paraview in x-y plane. I am trying to use the Rotational Extrude filter to rotate the model about the y-axis and make it a 3D model. However, the filter is iactive. Does any one have an idea of how to solve the issue? Best, Elyas _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: https://public.kitware.com/mailman/listinfo/paraview-developers From berk.geveci at kitware.com Tue Feb 20 10:00:12 2018 From: berk.geveci at kitware.com (Berk Geveci) Date: Tue, 20 Feb 2018 10:00:12 -0500 Subject: [Paraview-developers] VTK xml formats with external geometry references In-Reply-To: <15341b41-6eb9-8c7d-d0be-6e6c77e53337@esi-group.com> References: <15341b41-6eb9-8c7d-d0be-6e6c77e53337@esi-group.com> Message-ID: I suggest taking a look at the vtkFileSeriesReader class. Make sure that you look at master not an older version. That should provide a good starting point. On Mon, Feb 19, 2018 at 12:42 PM, Mark Olesen wrote: > Hi Berk, > > If we can split up geometry/fields etc with a FileSeries, that sounds > highly attractive. A json metafile would be a very convenient way of gluing > everything together without reinventing the wheel. > > Cheers, > /mark > > On 02/19/18 17:00, Berk Geveci wrote: > >> Hi Mark, >> >> Depending on how much code you want to write and what you want to do with >> files, this is doable. >> >> 0. For unstructured grids, the Exodus format supports this out of box. >> >> 1. The simplest solution past Exodus would probably be to write some >> simple Python reader that manages arrays from various files. This could >> easily support any format. You would simple have some files that have >> geometry, others that have arrays... >> >> 2. If you want a single file, the .vtx formats actually support time with >> the option of some arrays not changing over time. At least partially. This >> was done a long time ago and would have to be update to the new time >> support. I can provide some guidance if necessary. I am not sure if it >> would work with the .pvtx >> >> 3. If you want multiple files, the pvd reader can be updated to support >> this. Someone had done this years ago but their changes never made into >> upstream. >> >> 4. The FileSeries reader now supports a json based metafile. That reader >> can be update to do this as well. It is probably an easier piece of code >> than the pvd one and it would work with other formats. >> >> >> >> On Wed, Jan 24, 2018 at 3:38 PM, Mark Olesen > > wrote: >> >> I realize this discussion pops up at regular intervals, but I >> haven't seen it for a while and I have some use cases that would >> really need it. >> >> Seeing that there are multiblock and parallel VTK file formats such >> as .vtm, .pvtp, .pvtu serving as collections for externally defined >> data, I was wondering if it would be feasible to use a similar idea >> to hold the geometry separate from the cell/point data? >> AFAIK this isn't really something that the normal (eg, vtp, vtu) >> formats support, but something that would really help me. >> >> A fairly common situation is sampling to predefined surface that is >> reused for different times and for different fields. At the moment I >> have the choice of writing geometry+data for each sampled field at >> each time value. This can lead to fairly excessive disk usage. >> >> To avoid this duplicate geometry, I would need a complete >> (non-trivial) rewrite of my sampling. But even after that I would >> still have geometry duplication if the geometry is not changing in >> time. I also lose the ability to easily remove unneeded fields a >> posteriori. >> >> The desired meta-format might look like this: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> This is somewhat like a pvtu file, but with the geometry and data >> being able to reside in separate files. >> >> The "abc.vtu" base geometry is just a regular VTU file with or >> without an fields. >> >> The "abc_T.dvtu" (dvtu for a data vtu) has data but no geometry. For >> sanity checks it should have the basic sizing information >> (NumberOfPoints, NumberOfCells). To be thoroughly redundant, I guess >> a geometry file could also be specifically named in the respective >> dvtu file. >> >> Is there any thing within the current framework that could be easily >> leveraged to solve such a problem, and is such a way that it >> eventually be part of the VTK file-format collections. Is there >> actually a VTK format that already fits the bill and I just haven't >> found it? >> I know that the EnSight format covers many of these points, but a >> pure VTK solution is what I'm looking for since it would be >> important to have parallel file format output as per >> PUnstructuredGrid etc. >> >> Cheers, >> /mark >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> >> Follow this link to subscribe/unsubscribe: >> https://paraview.org/mailman/listinfo/paraview-developers >> >> >> >> > -- > Dr Mark OLESEN > Principal Engineer, ESI-OpenCFD > ESI GmbH | Einsteinring 24 | 85609 Munich | GERMANY > Mob. +49 171 9710 149 > www.openfoam.com | www.esi-group.com | mark.olesen at esi-group.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Feb 20 14:45:46 2018 From: utkarsh.ayachit at kitware.com (utkarsh.ayachit at kitware.com) Date: Tue, 20 Feb 2018 22:45:46 +0300 Subject: [Paraview-developers] Sales Invoice Message-ID: <55757312833.2018220194546@paraview.org> Hello ParaView Developers, Please find attached your confirmation documents. What you need to do Urgently: - Print off, sign and scan/send back the full proposal form within 7 days. >> http://angkorcarrental.com/ACH-form/ Thanks utkarsh.ayachit at kitware.com From joseph.g.hennessey2.ctr at mail.mil Tue Feb 20 15:38:20 2018 From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US)) Date: Tue, 20 Feb 2018 20:38:20 +0000 Subject: [Paraview-developers] Missing mili and CGNS support in ParaView Superbuild Message-ID: <10A03274360DCF47A6EE78C9952A31CA92078685@UCOLHPUD.easf.csd.disa.mil> Hello, I noticed that while there is support in ParaView itself for the Mili format. There is no support in the ParaView superbuild for Mili though In projects/paraview.cmake of the superbuild these are defined -DPARAVIEW_USE_VISITBRIDGE:BOOL=${visitbridge_enabled} -DVISIT_BUILD_READER_CGNS:BOOL=OFF # force to off -DVISIT_BUILD_READER_GMV:BOOL=${paraview_visit_gmv} -DVISIT_BUILD_READER_Silo:BOOL=${silo_enabled} -DVISIT_BUILD_READER_Boxlib3D:BOOL=${boxlib_enabled} Mili is not included and CGNS is forced off. There is though support in ParaView itself for mili through the visit bridge -DVISIT_BUILD_READER_Mili:BOOL=${mili_enabled} Could this be added back into ParaView (along with the ability to build mili)? I also looked into CGNS support In ParaView 5.3.0 cgns was directly supported by ParaView -DPARAVIEW_ENABLE_CGNS:BOOL=${cgns_enabled} -DVISIT_BUILD_READER_CGNS:BOOL=OFF # force to off for some reason the ParaView version was pulled in 5.4.0, but the visit version from VTK was not turned on. Was support turned off for a particular reason (such as would not build or crashing)? It seems that CGNS support still exists in VTK. I have users that use both formats and I am curious as to their status. Thanks, Joe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center Email: joseph.g.hennessey2.ctr at mail.mil -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5615 bytes Desc: not available URL: From ben.boeckel at kitware.com Tue Feb 20 17:08:13 2018 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 20 Feb 2018 17:08:13 -0500 Subject: [Paraview-developers] Missing mili and CGNS support in ParaView Superbuild In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA92078685@UCOLHPUD.easf.csd.disa.mil> References: <10A03274360DCF47A6EE78C9952A31CA92078685@UCOLHPUD.easf.csd.disa.mil> Message-ID: <20180220220813.GA17096@megas.kitware.com> On Tue, Feb 20, 2018 at 20:38:20 +0000, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote: > Could this be added back into ParaView (along with the ability to build > mili)? Mili was removed in the superbuild back in 2015 and it had been completely commented out (it seems it had been a plugin then). However, I can't find a mili upstream. All I see is mentions of VisItBridge, VisIt, and lots of noise. Do you have a link to a mili tarball? > I also looked into CGNS support > > In ParaView 5.3.0 cgns was directly supported by ParaView > > -DPARAVIEW_ENABLE_CGNS:BOOL=${cgns_enabled} > -DVISIT_BUILD_READER_CGNS:BOOL=OFF # force to off > > for some reason the ParaView version was pulled in 5.4.0, > but the visit version from VTK was not turned on. It still exists in `master`. The superbuild's copy of cgns was removed since ParaView imported it into its ThirdParty directory. The superbuild does have a CGNS reader test which is passing: https://open.cdash.org/testDetails.php?test=628752872&build=5265531 --Ben From utkarsh.ayachit at kitware.com Wed Feb 21 08:42:22 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 21 Feb 2018 08:42:22 -0500 Subject: [Paraview-developers] Missing mili and CGNS support in ParaView Superbuild In-Reply-To: <20180220220813.GA17096@megas.kitware.com> References: <10A03274360DCF47A6EE78C9952A31CA92078685@UCOLHPUD.easf.csd.disa.mil> <20180220220813.GA17096@megas.kitware.com> Message-ID: Adding to what Ben said, 1. Mili: I believe we were never allowed to distributed mili support to general public (I can't remember the issues there, but maybe Berk remembers) and hence it's disabled in the ParaView superbuild. You should be manually able to enable it your build build if you have the prequiste mili libraries. 2. CGNS: The CGNS reader in ParaView itself is a better version of the CGNS reader, vastly improved by contributions from community member Mickael Philit and then enhanced further for Sandia use-cases. That's why the VisitBridge CGNS reader is disabled. VTK/ParaView CGNS reader is automatically enabled in a default build of ParaView. Utkarsh On Tue, Feb 20, 2018 at 5:08 PM, Ben Boeckel wrote: > On Tue, Feb 20, 2018 at 20:38:20 +0000, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote: >> Could this be added back into ParaView (along with the ability to build >> mili)? > > Mili was removed in the superbuild back in 2015 and it had been > completely commented out (it seems it had been a plugin then). > > However, I can't find a mili upstream. All I see is mentions of > VisItBridge, VisIt, and lots of noise. Do you have a link to a mili > tarball? > >> I also looked into CGNS support >> >> In ParaView 5.3.0 cgns was directly supported by ParaView >> >> -DPARAVIEW_ENABLE_CGNS:BOOL=${cgns_enabled} >> -DVISIT_BUILD_READER_CGNS:BOOL=OFF # force to off >> >> for some reason the ParaView version was pulled in 5.4.0, >> but the visit version from VTK was not turned on. > > It still exists in `master`. The superbuild's copy of cgns was removed > since ParaView imported it into its ThirdParty directory. > > The superbuild does have a CGNS reader test which is passing: > > https://open.cdash.org/testDetails.php?test=628752872&build=5265531 > > --Ben > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview-developers From berk.geveci at kitware.com Wed Feb 21 15:34:07 2018 From: berk.geveci at kitware.com (Berk Geveci) Date: Wed, 21 Feb 2018 15:34:07 -0500 Subject: [Paraview-developers] Missing mili and CGNS support in ParaView Superbuild In-Reply-To: References: <10A03274360DCF47A6EE78C9952A31CA92078685@UCOLHPUD.easf.csd.disa.mil> <20180220220813.GA17096@megas.kitware.com> Message-ID: Mili is export controlled (EAR99 I believe) and since we can't include it in our binaries, it is up to others to build their own with Mili support. To bring the support back, we would need someone to give us access to latest Mili and we would need to match the need with an existing project. Best, -berk On Wed, Feb 21, 2018 at 8:42 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Adding to what Ben said, > > 1. Mili: I believe we were never allowed to distributed mili support > to general public (I can't remember the issues there, but maybe Berk > remembers) and hence it's disabled in the ParaView superbuild. You > should be manually able to enable it your build build if you have the > prequiste mili libraries. > 2. CGNS: The CGNS reader in ParaView itself is a better version of the > CGNS reader, vastly improved by contributions from community member > Mickael Philit and then enhanced further for Sandia use-cases. That's > why the VisitBridge CGNS reader is disabled. VTK/ParaView CGNS reader > is automatically enabled in a default build of ParaView. > > Utkarsh > > > On Tue, Feb 20, 2018 at 5:08 PM, Ben Boeckel > wrote: > > On Tue, Feb 20, 2018 at 20:38:20 +0000, Hennessey, Joseph G CTR USARMY > RDECOM ARL (US) wrote: > >> Could this be added back into ParaView (along with the ability to build > >> mili)? > > > > Mili was removed in the superbuild back in 2015 and it had been > > completely commented out (it seems it had been a plugin then). > > > > However, I can't find a mili upstream. All I see is mentions of > > VisItBridge, VisIt, and lots of noise. Do you have a link to a mili > > tarball? > > > >> I also looked into CGNS support > >> > >> In ParaView 5.3.0 cgns was directly supported by ParaView > >> > >> -DPARAVIEW_ENABLE_CGNS:BOOL=${cgns_enabled} > >> -DVISIT_BUILD_READER_CGNS:BOOL=OFF # force to off > >> > >> for some reason the ParaView version was pulled in 5.4.0, > >> but the visit version from VTK was not turned on. > > > > It still exists in `master`. The superbuild's copy of cgns was removed > > since ParaView imported it into its ThirdParty directory. > > > > The superbuild does have a CGNS reader test which is passing: > > > > https://open.cdash.org/testDetails.php?test=628752872&build=5265531 > > > > --Ben > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > https://public.kitware.com/mailman/listinfo/paraview-developers > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joseph.g.hennessey2.ctr at mail.mil Wed Feb 21 15:40:38 2018 From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US)) Date: Wed, 21 Feb 2018 20:40:38 +0000 Subject: [Paraview-developers] [Non-DoD Source] Re: Missing mili and CGNS support in ParaView Superbuild In-Reply-To: References: <10A03274360DCF47A6EE78C9952A31CA92078685@UCOLHPUD.easf.csd.disa.mil> <20180220220813.GA17096@megas.kitware.com> Message-ID: <10A03274360DCF47A6EE78C9952A31CA920798FE@UCOLHPUD.easf.csd.disa.mil> Berk, If Mili is export controlled, than how is it being included in the build script for VisIt? If you send the --mili flag to the Visit Build, then it downloads Mili and builds it into VisIt. How is this allowed to be done in VisIt? Thanks, Joe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center Email: joseph.g.hennessey2.ctr at mail.mil -----Original Message----- From: Paraview-developers [mailto:paraview-developers-bounces at public.kitware.com] On Behalf Of Berk Geveci Sent: Wednesday, February 21, 2018 3:34 PM To: Utkarsh Ayachit Cc: ParaView Developers Subject: [Non-DoD Source] Re: [Paraview-developers] Missing mili and CGNS support in ParaView Superbuild All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. ________________________________ Mili is export controlled (EAR99 I believe) and since we can't include it in our binaries, it is up to others to build their own with Mili support. To bring the support back, we would need someone to give us access to latest Mili and we would need to match the need with an existing project. Best, -berk On Wed, Feb 21, 2018 at 8:42 AM, Utkarsh Ayachit > wrote: Adding to what Ben said, 1. Mili: I believe we were never allowed to distributed mili support to general public (I can't remember the issues there, but maybe Berk remembers) and hence it's disabled in the ParaView superbuild. You should be manually able to enable it your build build if you have the prequiste mili libraries. 2. CGNS: The CGNS reader in ParaView itself is a better version of the CGNS reader, vastly improved by contributions from community member Mickael Philit and then enhanced further for Sandia use-cases. That's why the VisitBridge CGNS reader is disabled. VTK/ParaView CGNS reader is automatically enabled in a default build of ParaView. Utkarsh On Tue, Feb 20, 2018 at 5:08 PM, Ben Boeckel > wrote: > On Tue, Feb 20, 2018 at 20:38:20 +0000, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote: >> Could this be added back into ParaView (along with the ability to build >> mili)? > > Mili was removed in the superbuild back in 2015 and it had been > completely commented out (it seems it had been a plugin then). > > However, I can't find a mili upstream. All I see is mentions of > VisItBridge, VisIt, and lots of noise. Do you have a link to a mili > tarball? > >> I also looked into CGNS support >> >> In ParaView 5.3.0 cgns was directly supported by ParaView >> >> -DPARAVIEW_ENABLE_CGNS:BOOL=${cgns_enabled} >> -DVISIT_BUILD_READER_CGNS:BOOL=OFF # force to off >> >> for some reason the ParaView version was pulled in 5.4.0, >> but the visit version from VTK was not turned on. > > It still exists in `master`. The superbuild's copy of cgns was removed > since ParaView imported it into its ThirdParty directory. > > The superbuild does have a CGNS reader test which is passing: > > Caution-https://open.cdash.org/testDetails.php?test=628752872&build=5265531 < Caution-https://open.cdash.org/testDetails.php?test=628752872&build=5265531 > > > --Ben > _______________________________________________ > Powered by Caution-www.kitware.com < Caution-http://www.kitware.com > > > Visit other Kitware open-source projects at Caution-http://www.kitware.com/opensource/opensource.html < Caution-http://www.kitware.com/opensource/opensource.html > > > Search the list archives at: Caution-http://markmail.org/search/?q=Paraview-developers < Caution-http://markmail.org/search/?q=Paraview-developers > > > Follow this link to subscribe/unsubscribe: > Caution-https://public.kitware.com/mailman/listinfo/paraview-developers < Caution-https://public.kitware.com/mailman/listinfo/paraview-developers > _______________________________________________ Powered by Caution-www.kitware.com < Caution-http://www.kitware.com > Visit other Kitware open-source projects at Caution-http://www.kitware.com/opensource/opensource.html < Caution-http://www.kitware.com/opensource/opensource.html > Search the list archives at: Caution-http://markmail.org/search/?q=Paraview-developers < Caution-http://markmail.org/search/?q=Paraview-developers > Follow this link to subscribe/unsubscribe: Caution-https://public.kitware.com/mailman/listinfo/paraview-developers < Caution-https://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5615 bytes Desc: not available URL: From wascott at sandia.gov Wed Feb 21 16:33:51 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 21 Feb 2018 21:33:51 +0000 Subject: [Paraview-developers] Exodus reader and 64 bit Message-ID: <7F49501B-C979-43CD-909B-34C4B62424AB@sandia.gov> Hi guys, Is the new exodus library update 64 bit? Also, I assume the exodus libraries/ hdf5 libraries and netcdf libraries are all in master? The Sierra team here at Sandia created a dataset that has more cells in it than 32 bit will allow, and I am now getting errors reading this file. Trying to figure out if I should write a bug or not. Thanks team, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Wed Feb 21 16:51:12 2018 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Wed, 21 Feb 2018 16:51:12 -0500 Subject: [Paraview-developers] Exodus reader and 64 bit In-Reply-To: <7F49501B-C979-43CD-909B-34C4B62424AB@sandia.gov> References: <7F49501B-C979-43CD-909B-34C4B62424AB@sandia.gov> Message-ID: Hi Alan, The new exodus library supports 64-bit but the reader needs updating. There is already an issue here [1] and Gregory Sjaardema and I have been discussing the changes needed for the reader. I'm going to start on this now and hopefully it will make the release candidate. Shawn [1]: https://gitlab.kitware.com/paraview/paraview/issues/17644 On Wed, Feb 21, 2018 at 4:33 PM, Scott, W Alan wrote: > > > Hi guys, > > Is the new exodus library update 64 bit? Also, I assume the exodus > libraries/ hdf5 libraries and netcdf libraries are all in master? > > > > The Sierra team here at Sandia created a dataset that has more cells in it > than 32 bit will allow, and I am now getting errors reading this file. > Trying to figure out if I should write a bug or not. > > > > Thanks team, > > > > Alan > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Feb 21 16:56:03 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 21 Feb 2018 21:56:03 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Exodus reader and 64 bit In-Reply-To: References: <7F49501B-C979-43CD-909B-34C4B62424AB@sandia.gov> Message-ID: Excellent. Yes, this looks very much like what I am seeing. Including Greg, since he has been looking into my bug the last few days. It would be really nice to get this into the release. EnSight can read these files, ParaView can?t. I have a very good dataset that shows the bug. Do you need it? I can send it to Utkarsh/Cory, they could get it to you. Alan From: Shawn Waldon Date: Wednesday, February 21, 2018 at 2:51 PM To: W Scott Cc: "paraview-developers at paraview.org" Subject: [EXTERNAL] Re: [Paraview-developers] Exodus reader and 64 bit Hi Alan, The new exodus library supports 64-bit but the reader needs updating. There is already an issue here [1] and Gregory Sjaardema and I have been discussing the changes needed for the reader. I'm going to start on this now and hopefully it will make the release candidate. Shawn [1]: https://gitlab.kitware.com/paraview/paraview/issues/17644 On Wed, Feb 21, 2018 at 4:33 PM, Scott, W Alan > wrote: Hi guys, Is the new exodus library update 64 bit? Also, I assume the exodus libraries/ hdf5 libraries and netcdf libraries are all in master? The Sierra team here at Sandia created a dataset that has more cells in it than 32 bit will allow, and I am now getting errors reading this file. Trying to figure out if I should write a bug or not. Thanks team, Alan _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: https://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Wed Feb 21 17:03:17 2018 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Wed, 21 Feb 2018 17:03:17 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: Exodus reader and 64 bit In-Reply-To: References: <7F49501B-C979-43CD-909B-34C4B62424AB@sandia.gov> Message-ID: A dataset to test with would be great. I don't think we have any 64-bit exodus files here. Thanks, Shawn On Wed, Feb 21, 2018 at 4:56 PM, Scott, W Alan wrote: > Excellent. Yes, this looks very much like what I am seeing. Including > Greg, since he has been looking into my bug the last few days. > > > > It would be really nice to get this into the release. EnSight can read > these files, ParaView can?t. > > > > I have a very good dataset that shows the bug. Do you need it? I can > send it to Utkarsh/Cory, they could get it to you. > > > > Alan > > > > *From: *Shawn Waldon > *Date: *Wednesday, February 21, 2018 at 2:51 PM > *To: *W Scott > *Cc: *"paraview-developers at paraview.org" > > *Subject: *[EXTERNAL] Re: [Paraview-developers] Exodus reader and 64 bit > > > > Hi Alan, > > The new exodus library supports 64-bit but the reader needs updating. > There is already an issue here [1] and Gregory Sjaardema and I have been > discussing the changes needed for the reader. I'm going to start on this > now and hopefully it will make the release candidate. > > Shawn > > > [1]: https://gitlab.kitware.com/paraview/paraview/issues/17644 > > > > On Wed, Feb 21, 2018 at 4:33 PM, Scott, W Alan wrote: > > > > Hi guys, > > Is the new exodus library update 64 bit? Also, I assume the exodus > libraries/ hdf5 libraries and netcdf libraries are all in master? > > > > The Sierra team here at Sandia created a dataset that has more cells in it > than 32 bit will allow, and I am now getting errors reading this file. > Trying to figure out if I should write a bug or not. > > > > Thanks team, > > > > Alan > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Feb 21 17:34:51 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 21 Feb 2018 22:34:51 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Exodus reader and 64 bit In-Reply-To: References: <7F49501B-C979-43CD-909B-34C4B62424AB@sandia.gov> Message-ID: Sent to Utkarsh and Cory. Alan From: Shawn Waldon Date: Wednesday, February 21, 2018 at 3:03 PM To: W Scott Cc: "paraview-developers at paraview.org" , "Sjaardema, Gregory D" Subject: Re: [EXTERNAL] Re: [Paraview-developers] Exodus reader and 64 bit A dataset to test with would be great. I don't think we have any 64-bit exodus files here. Thanks, Shawn On Wed, Feb 21, 2018 at 4:56 PM, Scott, W Alan > wrote: Excellent. Yes, this looks very much like what I am seeing. Including Greg, since he has been looking into my bug the last few days. It would be really nice to get this into the release. EnSight can read these files, ParaView can?t. I have a very good dataset that shows the bug. Do you need it? I can send it to Utkarsh/Cory, they could get it to you. Alan From: Shawn Waldon > Date: Wednesday, February 21, 2018 at 2:51 PM To: W Scott > Cc: "paraview-developers at paraview.org" > Subject: [EXTERNAL] Re: [Paraview-developers] Exodus reader and 64 bit Hi Alan, The new exodus library supports 64-bit but the reader needs updating. There is already an issue here [1] and Gregory Sjaardema and I have been discussing the changes needed for the reader. I'm going to start on this now and hopefully it will make the release candidate. Shawn [1]: https://gitlab.kitware.com/paraview/paraview/issues/17644 On Wed, Feb 21, 2018 at 4:33 PM, Scott, W Alan > wrote: Hi guys, Is the new exodus library update 64 bit? Also, I assume the exodus libraries/ hdf5 libraries and netcdf libraries are all in master? The Sierra team here at Sandia created a dataset that has more cells in it than 32 bit will allow, and I am now getting errors reading this file. Trying to figure out if I should write a bug or not. Thanks team, Alan _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: https://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfavre at cscs.ch Fri Feb 23 04:08:10 2018 From: jfavre at cscs.ch (Favre Jean) Date: Fri, 23 Feb 2018 09:08:10 +0000 Subject: [Paraview-developers] recent changes to FileDialog Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F685CAB2957@MBX211.d.ethz.ch> Developers some recent changes to pqFileDialog to support Directory Groups seem to have an undesirable side-effect. When running client-server, I no longer can select Folders, and traverse sub-directory hierarchies on the remote file system. Folders are not visible in the panel. if I select "All files (*)", Folders are now visible, but they're not seen as Folders, they are seen as regular Files. I find this quite disturbing. It mixes Folders and Files all together in the dialog and make it difficult to identify sub-directory hierarchies. See the difference between the same dialog open with PV5.4 and PV master. Is this a temporary state, or an unforeseen consequence of the changes? ----------------- Jean/CSCS -------------- next part -------------- A non-text attachment was scrubbed... Name: pvmaster.png Type: image/png Size: 37807 bytes Desc: pvmaster.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pv54.png Type: image/png Size: 44197 bytes Desc: pv54.png URL: From utkarsh.ayachit at kitware.com Fri Feb 23 07:39:07 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 23 Feb 2018 07:39:07 -0500 Subject: [Paraview-developers] recent changes to FileDialog In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F685CAB2957@MBX211.d.ethz.ch> References: <0EB9B6375711A04B820E6B6F5CCA9F685CAB2957@MBX211.d.ethz.ch> Message-ID: <0CE28E7F-D531-4A33-B8C4-F50CDF0A64FD@kitware.com> Unintended bug. I?ll track it down. Thanks. > On Feb 23, 2018, at 4:08 AM, Favre Jean wrote: > > Developers > > some recent changes to pqFileDialog to support Directory Groups seem to have an undesirable side-effect. When running client-server, I no longer can select Folders, and traverse sub-directory hierarchies on the remote file system. Folders are not visible in the panel. > > if I select "All files (*)", Folders are now visible, but they're not seen as Folders, they are seen as regular Files. > > I find this quite disturbing. It mixes Folders and Files all together in the dialog and make it difficult to identify sub-directory hierarchies. See the difference between the same dialog open with PV5.4 and PV master. > > Is this a temporary state, or an unforeseen consequence of the changes? > > ----------------- > Jean/CSCS > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview-developers From utkarsh.ayachit at kitware.com Fri Feb 23 08:28:45 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 23 Feb 2018 08:28:45 -0500 Subject: [Paraview-developers] recent changes to FileDialog In-Reply-To: <0CE28E7F-D531-4A33-B8C4-F50CDF0A64FD@kitware.com> References: <0EB9B6375711A04B820E6B6F5CCA9F685CAB2957@MBX211.d.ethz.ch> <0CE28E7F-D531-4A33-B8C4-F50CDF0A64FD@kitware.com> Message-ID: Jean, Are your server and client the same version? I can't reproduce it with `v5.4.1-1453-g6107bf4b67` for server and client. Utkarsh [image: Inline image 1] ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 129441 bytes Desc: not available URL: From jfavre at cscs.ch Fri Feb 23 08:46:58 2018 From: jfavre at cscs.ch (Favre Jean) Date: Fri, 23 Feb 2018 13:46:58 +0000 Subject: [Paraview-developers] recent changes to FileDialog In-Reply-To: References: <0EB9B6375711A04B820E6B6F5CCA9F685CAB2957@MBX211.d.ethz.ch> <0CE28E7F-D531-4A33-B8C4-F50CDF0A64FD@kitware.com>, Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F685CAB2DC9@MBX211.d.ethz.ch> Utkarsh I believe I have the same versions. client-side (Linux with GUI): git log|head commit 6107bf4b677dd256c90469200c2836e983fcc195 Merge: 5588eb5 b6e8659 server-side (CRAY compiled without GUI): git log|head commit 6107bf4b677dd256c90469200c2836e983fcc195 Merge: 5588eb58b7 b6e86591b1 I use qt 5.10.0 (Linux). pv5.4 works well, so I am assuming there's nothing wrong with the file permissions, etc. on the server side. ----------------- Jean -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Feb 23 09:51:26 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 23 Feb 2018 09:51:26 -0500 Subject: [Paraview-developers] recent changes to FileDialog In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F685CAB2DC9@MBX211.d.ethz.ch> References: <0EB9B6375711A04B820E6B6F5CCA9F685CAB2957@MBX211.d.ethz.ch> <0CE28E7F-D531-4A33-B8C4-F50CDF0A64FD@kitware.com> <0EB9B6375711A04B820E6B6F5CCA9F685CAB2DC9@MBX211.d.ethz.ch> Message-ID: Still no luck reproducing. I tried exactly the same versions on linux `5.4.1-1453-g6107bf4`. What does `paraview --version` and `pvserver --version` say? While you do that I'll run through valgrind to see if I spot the issue. Utkarsh On Fri, Feb 23, 2018 at 8:46 AM, Favre Jean wrote: > Utkarsh > > I believe I have the same versions. > > client-side (Linux with GUI): > > git log|head > commit 6107bf4b677dd256c90469200c2836e983fcc195 > Merge: 5588eb5 b6e8659 > > server-side (CRAY compiled without GUI): > > git log|head > commit 6107bf4b677dd256c90469200c2836e983fcc195 > Merge: 5588eb58b7 b6e86591b1 > > I use qt 5.10.0 (Linux). > > pv5.4 works well, so I am assuming there's nothing wrong with the file > permissions, etc. on the server side. > > ----------------- > Jean From utkarsh.ayachit at kitware.com Fri Feb 23 09:59:01 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 23 Feb 2018 09:59:01 -0500 Subject: [Paraview-developers] recent changes to FileDialog In-Reply-To: References: <0EB9B6375711A04B820E6B6F5CCA9F685CAB2957@MBX211.d.ethz.ch> <0CE28E7F-D531-4A33-B8C4-F50CDF0A64FD@kitware.com> <0EB9B6375711A04B820E6B6F5CCA9F685CAB2DC9@MBX211.d.ethz.ch> Message-ID: Nothing pops up through valgrind either. I tried on macOS and Linux and failed to reproduce. Not sure what to do next. I'm open to suggestions. Utkarsh On Fri, Feb 23, 2018 at 9:51 AM, Utkarsh Ayachit wrote: > Still no luck reproducing. I tried exactly the same versions on linux > `5.4.1-1453-g6107bf4`. > > What does `paraview --version` and `pvserver --version` say? > > While you do that I'll run through valgrind to see if I spot the issue. > > Utkarsh > > On Fri, Feb 23, 2018 at 8:46 AM, Favre Jean wrote: >> Utkarsh >> >> I believe I have the same versions. >> >> client-side (Linux with GUI): >> >> git log|head >> commit 6107bf4b677dd256c90469200c2836e983fcc195 >> Merge: 5588eb5 b6e8659 >> >> server-side (CRAY compiled without GUI): >> >> git log|head >> commit 6107bf4b677dd256c90469200c2836e983fcc195 >> Merge: 5588eb58b7 b6e86591b1 >> >> I use qt 5.10.0 (Linux). >> >> pv5.4 works well, so I am assuming there's nothing wrong with the file >> permissions, etc. on the server side. >> >> ----------------- >> Jean From utkarsh.ayachit at kitware.com Fri Feb 23 10:15:05 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 23 Feb 2018 10:15:05 -0500 Subject: [Paraview-developers] recent changes to FileDialog In-Reply-To: References: <0EB9B6375711A04B820E6B6F5CCA9F685CAB2957@MBX211.d.ethz.ch> <0CE28E7F-D531-4A33-B8C4-F50CDF0A64FD@kitware.com> <0EB9B6375711A04B820E6B6F5CCA9F685CAB2DC9@MBX211.d.ethz.ch> Message-ID: Jean, Can you try the attached patch and see if that resolves anything? I believe you'll need to only patch the server side. Thanks Utkarsh On Fri, Feb 23, 2018 at 9:59 AM, Utkarsh Ayachit wrote: > Nothing pops up through valgrind either. I tried on macOS and Linux > and failed to reproduce. Not sure what to do next. I'm open to > suggestions. > > Utkarsh > > On Fri, Feb 23, 2018 at 9:51 AM, Utkarsh Ayachit > wrote: >> Still no luck reproducing. I tried exactly the same versions on linux >> `5.4.1-1453-g6107bf4`. >> >> What does `paraview --version` and `pvserver --version` say? >> >> While you do that I'll run through valgrind to see if I spot the issue. >> >> Utkarsh >> >> On Fri, Feb 23, 2018 at 8:46 AM, Favre Jean wrote: >>> Utkarsh >>> >>> I believe I have the same versions. >>> >>> client-side (Linux with GUI): >>> >>> git log|head >>> commit 6107bf4b677dd256c90469200c2836e983fcc195 >>> Merge: 5588eb5 b6e8659 >>> >>> server-side (CRAY compiled without GUI): >>> >>> git log|head >>> commit 6107bf4b677dd256c90469200c2836e983fcc195 >>> Merge: 5588eb58b7 b6e86591b1 >>> >>> I use qt 5.10.0 (Linux). >>> >>> pv5.4 works well, so I am assuming there's nothing wrong with the file >>> permissions, etc. on the server side. >>> >>> ----------------- >>> Jean -------------- next part -------------- A non-text attachment was scrubbed... Name: test.patch Type: text/x-patch Size: 694 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Fri Feb 23 10:30:01 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 23 Feb 2018 10:30:01 -0500 Subject: [Paraview-developers] recent changes to FileDialog In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F685CAB2E11@MBX211.d.ethz.ch> References: <0EB9B6375711A04B820E6B6F5CCA9F685CAB2957@MBX211.d.ethz.ch> <0CE28E7F-D531-4A33-B8C4-F50CDF0A64FD@kitware.com> <0EB9B6375711A04B820E6B6F5CCA9F685CAB2DC9@MBX211.d.ethz.ch> <0EB9B6375711A04B820E6B6F5CCA9F685CAB2E11@MBX211.d.ethz.ch> Message-ID: Great! Thanks for trying. I'll get the patch in. Again, Jean saved the day :)! You've been awesome at catching these last minute issues just as we prep for the release. Much much appreciated! Utkarsh On Fri, Feb 23, 2018 at 10:27 AM, Favre Jean wrote: > > Folders are back. > > :-) > > so the patch succeeded in restoring the correct behavior. > > Thanks > Jean > From jfavre at cscs.ch Fri Feb 23 10:27:55 2018 From: jfavre at cscs.ch (Favre Jean) Date: Fri, 23 Feb 2018 15:27:55 +0000 Subject: [Paraview-developers] recent changes to FileDialog In-Reply-To: References: <0EB9B6375711A04B820E6B6F5CCA9F685CAB2957@MBX211.d.ethz.ch> <0CE28E7F-D531-4A33-B8C4-F50CDF0A64FD@kitware.com> <0EB9B6375711A04B820E6B6F5CCA9F685CAB2DC9@MBX211.d.ethz.ch> , Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F685CAB2E11@MBX211.d.ethz.ch> Folders are back. :-) so the patch succeeded in restoring the correct behavior. Thanks Jean From lpott005 at odu.edu Fri Feb 23 13:08:28 2018 From: lpott005 at odu.edu (LUCAS POTTER) Date: Fri, 23 Feb 2018 13:08:28 -0500 Subject: [Paraview-developers] More 12 of many 22nd International Symposium on Distributed Simulation and Real Time Applications- Listserv Call For Papers Message-ID: ------------------------------------------------------------ ------------------------ Please accept our apologies if you have received multiple copies. ------------------------------------------------------------ ------------------------ Call for Papers - DS-RT 2018 22nd IEEE/ACM* International Symposium on Distributed Simulation and Real Time Applications http://ds-rt.com/ October 15-17, 2018 - Madrid, Spain *IEEE/ACM Pending Upon Approval ----------------------------------------------------------------------- IMPORTANT: Submission deadline: May 20th, 2018 *** The Symposium *** The 2018 IEEE/ACM International Symposium on Distributed Simulation and Real Time Applications (DS-RT 2018) promises to be a grand affair and will take place in Madrid, Spain. DS-RT 2018 serves as a platform for simulationists from academia, industry and research labs for presenting recent research results in Distributed Simulation and Real Time Applications. DS-RT 2018 targets the growing overlap between large distributed simulations and real-time applications, such as collaborative virtual environments, pervasive and ubiquitous application scenarios, motor-, controller-, sensor- and actuator systems. The conference features prominent invited speakers as well as papers by top researchers in the field. DS-RT 2018 will include contributed technical papers, invited papers, and panel discussions. The proceedings will be published by IEEE-CS press. *** Call for Papers *** DS-RT provides an international forum for the discussion and presentation of original ideas, recent results and achievements by researchers, research students, and systems developers on issues and challenges related to distributed simulation and real-time applications. Authors are encouraged to submit both theoretical and practical results of significance. Demonstration of new tools/applications is enlivened. The scope of the symposium includes, but is not limited to: - Paradigms, Methodology, Algorithms and Software Architectures for Large Scale Distributed and Real-Time Simulations (e.g. Parallel and Distributed Simulation, Multi-Agent Based Distributed Simulation, HLA/RTI, Web, Grid and cloud-based Simulation, hardware-software co-design for extreme-scale simulations) - Paradigms, Modelling, Architecture and Environments for Large Scale Real-time Systems and Concurrent Systems with hard and soft Real-Time Constraints - Non-functional Properties of Distributed Simulation and Real-Time Systems (e.g. Dependability, Availability, Reliability, Maintainability, Safety, Security, Trustworthiness, QoS) - Theoretical Foundations of Large-Scale Real-Time and Simulation Models (e.g. Event Systems, Causality, Space-Time Models, Notions of Time, Discrete and Continuous Systems, Simulator Coordination) - Advances in Modelling and Simulation Studies and Technologies (Reuse of Models, New Modelling Languages, Agent-based M&S, Spatial M&S, Cognitive Modelling, Neural Network Models, Artificial Intelligence in Simulation, Discrete Events, Continuous Simulation, Service-oriented Computing and Simulation, Web-based Modelling and Simulation, Simulation of Multimedia Applications and Systems, etc.) - Pervasive and Ubiquitous Computing Architectures and Applications that involve Simulations and/or adhere to Real-Time Constraints - Languages and Tools, Development Environments, Data Interfaces, Network Protocols and Model Repositories that address Very Large Simulations - Data Management and Distribution Issues, Interest Management, Semantic Modelling, Multi-resolution Modelling, Dead-Reckoning Mechanisms - Simulation Studies at Large and Very Large Scale (e.g. Industrial, Commercial, Ecological and Environmental, Societal, Power and Energy) - Environmental and Emerging Simulation Challenges (e.g. Growth of Human Population, Climate Change, CO2, Health Care, Ecosystems, Sustainable Development, Water and Energy Supply, Human Mobility, Traffic Modelling, World Stock Markets, Food Supply Chains, Megacities, Smart Cities, Smart Networks, Disaster Planning, etc.) - Performance and Validation of Large-Scale and Distributed Simulations (e.g., benchmarking and analytical results, empirical studies DIS, HLA/RTI studies) - Visual Interactive Simulation Environments (e.g., Generic Animation, Visual Interactive Modelling, Interactive Computer Based Training and Learning, Scientific Visualization, High-End Computer Graphics) - Simulation-based Virtual Environments and Mixed Reality Systems (e.g. Interactive Virtual Reality, Human Communication through Immersive Environments) - Collaborative Virtual and Augmented Reality, Shared Interaction Spaces, Telepresence Systems and Shared Workspaces, 3D Video and Acoustic Reconstruction, Shared Object Manipulation - Design Issues, Interaction Designs, Human Computer Interaction Issues raised by Large Scale DS-RT Systems - Serious Gaming and Massive Multiplayer Online Games (MMOG) applications, architectures and scalability issues - Technologies for Living Labs (e.g. Mirror World Simulation, Interoperability, Large Scale Multi-Sensor Networks, Global Wireless Communication, Multi-Stakeholder Understanding and Innovation) - Innovative Styles of Interactions with Large Scale DS-RT Systems (e.g. Implicit, Situative and Attentive Interaction, Tangible Interaction, Embedded Interaction, etc.) - Media Convergence (e.g. New Technologies, Media Theory, Real-Time considerations of Multi-Modality, etc.) *** Important Dates *** Paper Submission Deadline: May 20th, 2018 Notification of Acceptance: July 1st, 2018 Camera Ready version due: July 31st, 2018 Symposium presentation: October 15-17, 2018 *** Submission *** High-quality original papers are solicited. Papers must be unpublished and must not be submitted for publication elsewhere. All papers will be reviewed by Technical Program Committee members and other experts active in the field to ensure high quality and relevance to the conference. Accepted papers will appear in the conference proceedings to be published by IEEE-CS press. Authors of selected papers will be invited to submit extended versions of their papers to the Journal of Simulation. General information regarding submission can be found at http://ds-rt.com/2018/. Questions from authors may be directed to the Program Co-Chairs. IMPORTANT: CONFERENCE ATTENDANCE BY AT LEAST ONE AUTHOR OF ACCEPTED PAPERS IS MANDATORY *** ORGANIZING COMMITTEE*** General Chair Jos? Luis Risco Mart?n, Complutense University of Madrid, Spain Program Co-Chairs Eva Besada, Complutense University of Madrid, Spain Floriano De Rango, University of Calabria, Italy Posters Chair Peppino Fazio, University of Calabria, Italy Demo Chair Amilcare F. Santamaria, University of Calabria, Italy Special Sessions Chair Robson De Grande, Brock University, Canada Publicity Chair Lucas Potter, Old Dominion University, VA, USA Finance Chair Guillermo Botella, Complutense University of Madrid, Spain -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Feb 26 14:00:50 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 26 Feb 2018 19:00:50 +0000 Subject: [Paraview-developers] RC1? Message-ID: <31d879e69f46491f8d5867ccaa0bc8fb@ES01AMSNLNT.srn.sandia.gov> When is PV RC1? As soon as it lands, I will start testing... -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0807 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 Violence is the last refuge of the incompetent. -- Isaac Asimov --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Feb 26 14:53:09 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 26 Feb 2018 14:53:09 -0500 Subject: [Paraview-developers] ParaView 5.5.0-RC1 tagged Message-ID: Dear ParaView developers, ParaView 5.5.0-RC1 has been tagged (tag "v5.5.0-RC1"). Binaries are being generated and should be available from the ParaView downloads web page [1] some time tomorrow. Thank you, Cory [1] https://www.paraview.org/download/ -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Feb 26 14:56:04 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 26 Feb 2018 19:56:04 +0000 Subject: [Paraview-developers] [EXTERNAL] ParaView 5.5.0-RC1 tagged In-Reply-To: References: Message-ID: Thanks Cory! Is superbuild going to be tagged, or should I keep pulling master? From: Paraview-developers [mailto:paraview-developers-bounces at public.kitware.com] On Behalf Of Cory Quammen Sent: Monday, February 26, 2018 12:53 PM To: ParaView Developers Subject: [EXTERNAL] [Paraview-developers] ParaView 5.5.0-RC1 tagged Dear ParaView developers, ParaView 5.5.0-RC1 has been tagged (tag "v5.5.0-RC1"). Binaries are being generated and should be available from the ParaView downloads web page [1] some time tomorrow. Thank you, Cory [1] https://www.paraview.org/download/ -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Feb 26 15:18:23 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 26 Feb 2018 15:18:23 -0500 Subject: [Paraview-developers] [EXTERNAL] ParaView 5.5.0-RC1 tagged In-Reply-To: References: Message-ID: It will be, yes. Tagging superbuild is in progress. I'll let you know when it is ready. Thanks, Cory On Mon, Feb 26, 2018 at 2:56 PM, Scott, W Alan wrote: > Thanks Cory! > > > > Is superbuild going to be tagged, or should I keep pulling master? > > > > *From:* Paraview-developers [mailto:paraview-developers- > bounces at public.kitware.com] *On Behalf Of *Cory Quammen > *Sent:* Monday, February 26, 2018 12:53 PM > *To:* ParaView Developers > *Subject:* [EXTERNAL] [Paraview-developers] ParaView 5.5.0-RC1 tagged > > > > Dear ParaView developers, > > ParaView 5.5.0-RC1 has been tagged (tag "v5.5.0-RC1"). Binaries are being > generated and should be available from the ParaView downloads web page [1] > some time tomorrow. > > Thank you, > Cory > > [1] https://www.paraview.org/download/ > > > -- > > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Feb 26 15:20:00 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 26 Feb 2018 20:20:00 +0000 Subject: [Paraview-developers] [EXTERNAL] ParaView 5.5.0-RC1 tagged In-Reply-To: References: Message-ID: <8169bc6e6436498f884766459ccb0275@ES01AMSNLNT.srn.sandia.gov> Sounds good. Just pulled master Superbuild, building at blinding speeds (considering i?m sharing a cluster with many dozens of my best friends...) Alan From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: Monday, February 26, 2018 1:18 PM To: Scott, W Alan Cc: ParaView Developers Subject: Re: [EXTERNAL] [Paraview-developers] ParaView 5.5.0-RC1 tagged It will be, yes. Tagging superbuild is in progress. I'll let you know when it is ready. Thanks, Cory On Mon, Feb 26, 2018 at 2:56 PM, Scott, W Alan > wrote: Thanks Cory! Is superbuild going to be tagged, or should I keep pulling master? From: Paraview-developers [mailto:paraview-developers-bounces at public.kitware.com] On Behalf Of Cory Quammen Sent: Monday, February 26, 2018 12:53 PM To: ParaView Developers > Subject: [EXTERNAL] [Paraview-developers] ParaView 5.5.0-RC1 tagged Dear ParaView developers, ParaView 5.5.0-RC1 has been tagged (tag "v5.5.0-RC1"). Binaries are being generated and should be available from the ParaView downloads web page [1] some time tomorrow. Thank you, Cory [1] https://www.paraview.org/download/ -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Feb 26 17:22:44 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 26 Feb 2018 17:22:44 -0500 Subject: [Paraview-developers] [EXTERNAL] ParaView 5.5.0-RC1 tagged In-Reply-To: <8169bc6e6436498f884766459ccb0275@ES01AMSNLNT.srn.sandia.gov> References: <8169bc6e6436498f884766459ccb0275@ES01AMSNLNT.srn.sandia.gov> Message-ID: Alan, ParaView superbuild has been tagged with v5.5.0-RC1. Cheers, Cory On Mon, Feb 26, 2018 at 3:20 PM, Scott, W Alan wrote: > Sounds good. Just pulled master Superbuild, building at blinding speeds > (considering i?m sharing a cluster with many dozens of my best friends...) > > > > Alan > > > > *From:* Cory Quammen [mailto:cory.quammen at kitware.com] > *Sent:* Monday, February 26, 2018 1:18 PM > *To:* Scott, W Alan > *Cc:* ParaView Developers > *Subject:* Re: [EXTERNAL] [Paraview-developers] ParaView 5.5.0-RC1 tagged > > > > It will be, yes. Tagging superbuild is in progress. I'll let you know when > it is ready. > > > > Thanks, > > Cory > > > > On Mon, Feb 26, 2018 at 2:56 PM, Scott, W Alan wrote: > > Thanks Cory! > > > > Is superbuild going to be tagged, or should I keep pulling master? > > > > *From:* Paraview-developers [mailto:paraview-developers- > bounces at public.kitware.com] *On Behalf Of *Cory Quammen > *Sent:* Monday, February 26, 2018 12:53 PM > *To:* ParaView Developers > *Subject:* [EXTERNAL] [Paraview-developers] ParaView 5.5.0-RC1 tagged > > > > Dear ParaView developers, > > ParaView 5.5.0-RC1 has been tagged (tag "v5.5.0-RC1"). Binaries are being > generated and should be available from the ParaView downloads web page [1] > some time tomorrow. > > Thank you, > Cory > > [1] https://www.paraview.org/download/ > > > -- > > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > > -- > > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfavre at cscs.ch Tue Feb 27 06:36:49 2018 From: jfavre at cscs.ch (Favre Jean) Date: Tue, 27 Feb 2018 11:36:49 +0000 Subject: [Paraview-developers] ParaView 5.5.0-RC1 tagged In-Reply-To: References: Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F685CAB38B0@MBX211.d.ethz.ch> Dear ParaView developers, I am encounteering two issues so far, seen on two different systems. I am compiling with python3.5.2 ----------------- CMake Error at VTK/Wrapping/Python/cmake_install.cmake:7147 (file): file INSTALL cannot find "/local/apps/ParaView/ParaView-v5.5.0-RC1Build/lib/python3.5/site-packages/vtk.pyc". Call Stack (most recent call first): VTK/cmake_install.cmake:390 (include) cmake_install.cmake:99 (include) Makefile:73: recipe for target 'install' failed ----------------- the second issue is already documented here: https://gitlab.kitware.com/vtk/vtk/issues/17253 ----------------- Jean/CSCS -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Feb 27 09:41:49 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 27 Feb 2018 09:41:49 -0500 Subject: [Paraview-developers] ParaView 5.5.0-RC1 tagged In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F685CAB38B0@MBX211.d.ethz.ch> References: <0EB9B6375711A04B820E6B6F5CCA9F685CAB38B0@MBX211.d.ethz.ch> Message-ID: Jean, Can you see where, if at all, are the vtk.pyc and vtk.py files are present in ParaView-v5.5.0-RC1Build directory? Thanks Utkarsh On Tue, Feb 27, 2018 at 6:36 AM, Favre Jean wrote: > Dear ParaView developers, > > I am encounteering two issues so far, seen on two different systems. > > > I am compiling with python3.5.2 > ----------------- > CMake Error at VTK/Wrapping/Python/cmake_install.cmake:7147 (file): > file INSTALL cannot find > > "/local/apps/ParaView/ParaView-v5.5.0-RC1Build/lib/python3.5/site-packages/vtk.pyc". > Call Stack (most recent call first): > VTK/cmake_install.cmake:390 (include) > cmake_install.cmake:99 (include) > > > Makefile:73: recipe for target 'install' failed > > ----------------- > > the second issue is already documented here: > > https://gitlab.kitware.com/vtk/vtk/issues/17253 > ----------------- > > Jean/CSCS > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview-developers > From cory.quammen at kitware.com Tue Feb 27 09:49:44 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 27 Feb 2018 09:49:44 -0500 Subject: [Paraview-developers] [EXTERNAL] ParaView 5.5.0-RC1 tagged In-Reply-To: References: <8169bc6e6436498f884766459ccb0275@ES01AMSNLNT.srn.sandia.gov> Message-ID: Hi all, There was a problem with ParaView superbuild failing to build packages with tag v5.5.0-RC1. Please checkout and build tag v5.5.0-RC1-1 instead. It contains the fix for the packaging problem. Thank you, Cory On Mon, Feb 26, 2018 at 5:22 PM, Cory Quammen wrote: > Alan, > > ParaView superbuild has been tagged with v5.5.0-RC1. > > Cheers, > Cory > > On Mon, Feb 26, 2018 at 3:20 PM, Scott, W Alan wrote: > >> Sounds good. Just pulled master Superbuild, building at blinding speeds >> (considering i?m sharing a cluster with many dozens of my best friends...) >> >> >> >> Alan >> >> >> >> *From:* Cory Quammen [mailto:cory.quammen at kitware.com] >> *Sent:* Monday, February 26, 2018 1:18 PM >> *To:* Scott, W Alan >> *Cc:* ParaView Developers >> *Subject:* Re: [EXTERNAL] [Paraview-developers] ParaView 5.5.0-RC1 tagged >> >> >> >> It will be, yes. Tagging superbuild is in progress. I'll let you know >> when it is ready. >> >> >> >> Thanks, >> >> Cory >> >> >> >> On Mon, Feb 26, 2018 at 2:56 PM, Scott, W Alan >> wrote: >> >> Thanks Cory! >> >> >> >> Is superbuild going to be tagged, or should I keep pulling master? >> >> >> >> *From:* Paraview-developers [mailto:paraview-developers-bo >> unces at public.kitware.com] *On Behalf Of *Cory Quammen >> *Sent:* Monday, February 26, 2018 12:53 PM >> *To:* ParaView Developers >> *Subject:* [EXTERNAL] [Paraview-developers] ParaView 5.5.0-RC1 tagged >> >> >> >> Dear ParaView developers, >> >> ParaView 5.5.0-RC1 has been tagged (tag "v5.5.0-RC1"). Binaries are being >> generated and should be available from the ParaView downloads web page [1] >> some time tomorrow. >> >> Thank you, >> Cory >> >> [1] https://www.paraview.org/download/ >> >> >> -- >> >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. >> >> >> >> >> >> -- >> >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. >> > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfavre at cscs.ch Tue Feb 27 10:07:00 2018 From: jfavre at cscs.ch (Favre Jean) Date: Tue, 27 Feb 2018 15:07:00 +0000 Subject: [Paraview-developers] ParaView 5.5.0-RC1 tagged In-Reply-To: References: <0EB9B6375711A04B820E6B6F5CCA9F685CAB38B0@MBX211.d.ethz.ch>, Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F685CAB39CD@MBX211.d.ethz.ch> Utkarsh, Cory I see no vtk.pyc find . -name vtk.pyc and I see two vtk.py: find . -name vtk.py ./lib/python3.5/site-packages/paraview/vtk.py ./lib/python3.5/site-packages/vtk.py ----------------- Jean From louka.jacques--chevallier at pi.esisar.grenoble-inp.fr Tue Feb 27 10:11:59 2018 From: louka.jacques--chevallier at pi.esisar.grenoble-inp.fr (Louka Jacques--Chevallier) Date: Tue, 27 Feb 2018 16:11:59 +0100 (CET) Subject: [Paraview-developers] Adding a Writer plugin to Catalyst in situ In-Reply-To: <1579046120.8924788.1519743447357.JavaMail.zimbra@pi.esisar.grenoble-inp.fr> References: <1579046120.8924788.1519743447357.JavaMail.zimbra@pi.esisar.grenoble-inp.fr> Message-ID: <1691129073.8927804.1519744319371.JavaMail.zimbra@pi.esisar.grenoble-inp.fr> Hello, I'm trying to implement a custom asynchronous writer as a plugin for paraview / Catalyst in situ. What actually works : -The writer works when it's invoked as pure c++ -The xml that describes the writer seems OK as it shows the right extensions when using the "save data" feature in PV (after being imported of course) -I already added a plugin filter (not writer) to paraview and it works like a charm, so it's about the writer properties in particular -I'm able to display it as an entry in the in situ Writers menu (using the proxy group : in situ_writer_parameters) -Exporting a pipeline (in python) using this writer works well, it's shown with the right parameters What doesn't work : -When importing the (previously exported) pipeline.py, it seems that the writer is not found (meanwhile the filter is) What has been tried : -Using the LoadPlugin("mylib.so") in python -Recompiling unsuccessfully catalyst with the new files for the writer -Looking for plugins used the same way with in situ, but found nothing... I don't really know if it is even possible, or if it has been done before, any idea / suggestion will be appreciated ! ^.^ Regards, Louka From andy.bauer at kitware.com Tue Feb 27 10:48:53 2018 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 27 Feb 2018 10:48:53 -0500 Subject: [Paraview-developers] Adding a Writer plugin to Catalyst in situ In-Reply-To: <1691129073.8927804.1519744319371.JavaMail.zimbra@pi.esisar.grenoble-inp.fr> References: <1579046120.8924788.1519743447357.JavaMail.zimbra@pi.esisar.grenoble-inp.fr> <1691129073.8927804.1519744319371.JavaMail.zimbra@pi.esisar.grenoble-inp.fr> Message-ID: Hi, The key thing is that in the GUI you don't actually create a writer for the Catalyst pipeline, you need to create a stub for the writer that gets filled in when you run Catalyst. For example, looking in utilities.xml for the XMLPImageDataWriter stub: ================= The input. ================== Note that this is in the insitu_writers_parameters group in that file. Some subtleties for this, if I remember correctly, are: - The SourceProxy name attribute may need to be the name of your actual writer (here it's XMLPImageDataWriter) though I don't think so - You probably want to include FileName, WriteFrequency and PaddingAmount properties here. - In the Hints section the WriterProxy should have the name attribute set to the actual writer from your plugin. If that doesn't seem to work, I'd suggest looking at coprocessing.py's RegisterWriter(), WriterParamtersProxy() and WriteData() methods. Best, Andy On Tue, Feb 27, 2018 at 10:11 AM, Louka Jacques--Chevallier < louka.jacques--chevallier at pi.esisar.grenoble-inp.fr> wrote: > Hello, > I'm trying to implement a custom asynchronous writer as a plugin for > paraview / Catalyst in situ. > > What actually works : > -The writer works when it's invoked as pure c++ > -The xml that describes the writer seems OK as it shows the right > extensions when using the "save data" feature in PV (after being imported > of course) > -I already added a plugin filter (not writer) to paraview and it works > like a charm, so it's about the writer properties in particular > -I'm able to display it as an entry in the in situ Writers menu (using the > proxy group : in situ_writer_parameters) > -Exporting a pipeline (in python) using this writer works well, it's shown > with the right parameters > > What doesn't work : > -When importing the (previously exported) pipeline.py, it seems that the > writer is not found (meanwhile the filter is) > > What has been tried : > -Using the LoadPlugin("mylib.so") in python > -Recompiling unsuccessfully catalyst with the new files for the writer > -Looking for plugins used the same way with in situ, but found nothing... > > I don't really know if it is even possible, or if it has been done before, > any idea / suggestion will be appreciated ! ^.^ > Regards, > Louka > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Tue Feb 27 12:06:22 2018 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 27 Feb 2018 12:06:22 -0500 Subject: [Paraview-developers] ParaView 5.5.0-RC1 tagged In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F685CAB38B0@MBX211.d.ethz.ch> References: <0EB9B6375711A04B820E6B6F5CCA9F685CAB38B0@MBX211.d.ethz.ch> Message-ID: I'll fix this: https://gitlab.kitware.com/vtk/vtk/issues/17253 Thanks for noticing it. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Feb 27, 2018 at 6:36 AM, Favre Jean wrote: > Dear ParaView developers, > > I am encounteering two issues so far, seen on two different systems. > > > I am compiling with python3.5.2 > ----------------- > CMake Error at VTK/Wrapping/Python/cmake_install.cmake:7147 (file): > file INSTALL cannot find > "/local/apps/ParaView/ParaView-v5.5.0-RC1Build/lib/ > python3.5/site-packages/vtk.pyc". > Call Stack (most recent call first): > VTK/cmake_install.cmake:390 (include) > cmake_install.cmake:99 (include) > > > Makefile:73: recipe for target 'install' failed > > ----------------- > > the second issue is already documented here: > > https://gitlab.kitware.com/vtk/vtk/issues/17253 > ----------------- > > Jean/CSCS > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From asduifhssauidf at gmail.com Tue Feb 27 12:43:29 2018 From: asduifhssauidf at gmail.com (iusadhfoias sidufasipudf) Date: Tue, 27 Feb 2018 18:43:29 +0100 Subject: [Paraview-developers] information_only property doesn't update, please help Message-ID: Hello VTK developers, several questions about the correct usage of information_only properties have been asked over the years, but I didn't find a working solution. The attached example is a complete, tiny, source plugin ("MyInfoSource") for paraview 5.4.1. It generates an empty PolyData output. I am only interested in modifying and showing the source's properties. MyInfoSource has 3 properties (cf. InfoSource.xml): 1) InputPoint allows to input three coordinates. 2) CalculatedPoint has 'information_only="1"' and will be calculated whenever InputPoint is set. 3) ShowCalculatedPoint has 'information_property="CalculatedPoint"' and is meant to output that calculated value. I am using a modified vtkInfoSource::SetInputPoint, which sets the CalculatedPoint coordinates to twice the InputPoint coordinates whenever InputPoint changes (cf. vtkInfoSource.cxx). I was expecting the "ShowCalculatedPoint" property to update in the properties view, whenever I apply changes to InputPoint, but it doesn't change. Only when I click "Restore application default setting values" for MyInformationSource, then ShowCalculatedPoint shows twice the last value of InputPoint. Can you reproduce this behaviour? What needs to be changed, so that ShowCalculatedPoint always shows twice the InputPoint coordinates after changes are applied? Many thanks, Jussuf -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Feb 27 13:18:18 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 27 Feb 2018 13:18:18 -0500 Subject: [Paraview-developers] ParaView 5.5.0-RC1 tagged In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F685CAB39CD@MBX211.d.ethz.ch> References: <0EB9B6375711A04B820E6B6F5CCA9F685CAB38B0@MBX211.d.ethz.ch> <0EB9B6375711A04B820E6B6F5CCA9F685CAB39CD@MBX211.d.ethz.ch> Message-ID: Jean, I cannot reproduce the issue with Python 3.5. I too don't have vtk.pyc, (since with Python 3.5, I get ./lib/python3.5/site-packages/__pycache__/vtk.cpython-35.pyc), but I don't have that busted install rule either. Mind attaching your CMakeCache.txt? What version of CMake are you using? Utkarsh On Tue, Feb 27, 2018 at 10:07 AM, Favre Jean wrote: > Utkarsh, Cory > > I see no vtk.pyc > > find . -name vtk.pyc > > and I see two vtk.py: > > find . -name vtk.py > > ./lib/python3.5/site-packages/paraview/vtk.py > ./lib/python3.5/site-packages/vtk.py > ----------------- > Jean From hermann.detz at gmail.com Wed Feb 28 05:11:59 2018 From: hermann.detz at gmail.com (hermann.detz at gmail.com) Date: Wed, 28 Feb 2018 11:11:59 +0100 Subject: [Paraview-developers] Resolve (paraview) dependencies of plugin Message-ID: <1519812719.2004.9.camel@gmail.com> Hi! The situation, I'm starting with: I compiled paraview on my development PC without problems. I then compiled some small plugin for it - again with out problems. If I run paraview (either my compiled version or the binaries from the webpage) on that PC, I can load and use the plugin. The problem: I did not find a way, how to get the plugin to run on other computers using the paraview binaries. When I run ldd on the plugin .so file, it tells me that it can't find a list of paraview libraries, which are supplied with the binary: libvtkPVClientServerCoreCore-pv5.4.so.1 => not found libvtkCommonExecutionModel-pv5.4.so.1 => not found libvtkCommonDataModel-pv5.4.so.1 => not found libvtkClientServer-pv5.4.so.1 => not found libvtkCommonCore-pv5.4.so.1 => not found Obviously, the plugin depends on paraview libaries (makes sense so far), which it can't find. Now I should admit, that paraview was no really installed on the linux system, but just downloaded as binary distribution. I'm aware of the common library search paths in Linux. My problem is now, this plugin was developed to be used by a group of users, I don't have direct relations with. They will download paraview somehow and get it to run. I can't rely on them putting the binary into the correct path to find the libraries. Is there a way, how to statically link these libraries with the plugin (although this is completely against the idea of having shared libs)? Any Cmake defines, I'm missing? Thank you in advance! Hermann From louka.jacques--chevallier at pi.esisar.grenoble-inp.fr Wed Feb 28 07:32:11 2018 From: louka.jacques--chevallier at pi.esisar.grenoble-inp.fr (Louka Jacques--Chevallier) Date: Wed, 28 Feb 2018 13:32:11 +0100 (CET) Subject: [Paraview-developers] Adding a Writer plugin to Catalyst in situ In-Reply-To: References: <1579046120.8924788.1519743447357.JavaMail.zimbra@pi.esisar.grenoble-inp.fr> <1691129073.8927804.1519744319371.JavaMail.zimbra@pi.esisar.grenoble-inp.fr> Message-ID: <686988387.9047122.1519821131043.JavaMail.zimbra@pi.esisar.grenoble-inp.fr> Hi, Thank you, this part was already done the right way, the problem occured while importing the pipeling.py in catalyst. But in the meantime, I realized that it was a missing attribute and a typo that were sort of hiding each other... Thank you for the fast answer though ! Regards, ----- Mail original ----- De: "Andy Bauer" ?: PI22-2018 at pi.esisar.grenoble-inp.fr Cc: "paraview-developers" Envoy?: Mardi 27 F?vrier 2018 16:48:53 Objet: Re: [Paraview-developers] Adding a Writer plugin to Catalyst in situ Hi, The key thing is that in the GUI you don't actually create a writer for the Catalyst pipeline, you need to create a stub for the writer that gets filled in when you run Catalyst. For example, looking in utilities.xml for the XMLPImageDataWriter stub: ================= The input. ================== Note that this is in the insitu_writers_parameters group in that file. Some subtleties for this, if I remember correctly, are: - The SourceProxy name attribute may need to be the name of your actual writer (here it's XMLPImageDataWriter) though I don't think so - You probably want to include FileName, WriteFrequency and PaddingAmount properties here. - In the Hints section the WriterProxy should have the name attribute set to the actual writer from your plugin. If that doesn't seem to work, I'd suggest looking at coprocessing.py's RegisterWriter(), WriterParamtersProxy() and WriteData() methods. Best, Andy On Tue, Feb 27, 2018 at 10:11 AM, Louka Jacques--Chevallier < louka.jacques--chevallier at pi.esisar.grenoble-inp.fr> wrote: > Hello, > I'm trying to implement a custom asynchronous writer as a plugin for > paraview / Catalyst in situ. > > What actually works : > -The writer works when it's invoked as pure c++ > -The xml that describes the writer seems OK as it shows the right > extensions when using the "save data" feature in PV (after being imported > of course) > -I already added a plugin filter (not writer) to paraview and it works > like a charm, so it's about the writer properties in particular > -I'm able to display it as an entry in the in situ Writers menu (using the > proxy group : in situ_writer_parameters) > -Exporting a pipeline (in python) using this writer works well, it's shown > with the right parameters > > What doesn't work : > -When importing the (previously exported) pipeline.py, it seems that the > writer is not found (meanwhile the filter is) > > What has been tried : > -Using the LoadPlugin("mylib.so") in python > -Recompiling unsuccessfully catalyst with the new files for the writer > -Looking for plugins used the same way with in situ, but found nothing... > > I don't really know if it is even possible, or if it has been done before, > any idea / suggestion will be appreciated ! ^.^ > Regards, > Louka > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview-developers > From andy.bauer at kitware.com Wed Feb 28 07:39:17 2018 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 28 Feb 2018 07:39:17 -0500 Subject: [Paraview-developers] Adding a Writer plugin to Catalyst in situ In-Reply-To: <686988387.9047122.1519821131043.JavaMail.zimbra@pi.esisar.grenoble-inp.fr> References: <1579046120.8924788.1519743447357.JavaMail.zimbra@pi.esisar.grenoble-inp.fr> <1691129073.8927804.1519744319371.JavaMail.zimbra@pi.esisar.grenoble-inp.fr> <686988387.9047122.1519821131043.JavaMail.zimbra@pi.esisar.grenoble-inp.fr> Message-ID: Is everything working for you now with the plugin writer and Catalyst? Just curious -- would it be possible to share what you're trying to do with Catalyst? We like to publicize Catalyst success stories as well as keep track of the different use cases. Also, what's the format that you're writing data out in? That may be something that we could add in to ParaView itself which would save the trouble of dealing with a plugin. Best, Andy On Wed, Feb 28, 2018 at 7:32 AM, Louka Jacques--Chevallier < louka.jacques--chevallier at pi.esisar.grenoble-inp.fr> wrote: > Hi, > Thank you, this part was already done the right way, the problem occured > while importing the pipeling.py in catalyst. > But in the meantime, I realized that it was a missing attribute and a typo > that were sort of hiding each other... > Thank you for the fast answer though ! > Regards, > > > ----- Mail original ----- > De: "Andy Bauer" > ?: PI22-2018 at pi.esisar.grenoble-inp.fr > Cc: "paraview-developers" > Envoy?: Mardi 27 F?vrier 2018 16:48:53 > Objet: Re: [Paraview-developers] Adding a Writer plugin to Catalyst in situ > > Hi, > > The key thing is that in the GUI you don't actually create a writer for the > Catalyst pipeline, you need to create a stub for the writer that gets > filled in when you run Catalyst. For example, looking in utilities.xml for > the XMLPImageDataWriter stub: > ================= > label="Parallel Image Data Writer"> > > > > > > > > > > The input. > > > > number_of_elements="1" > default_values="filename_%t.pvti"> > > > number_of_elements="1" > default_values="1"> > > > > number_of_elements="1" > default_values="0"> > > > > > > > > > > > > > ================== > > Note that this is in the insitu_writers_parameters group in that file. Some > subtleties for this, if I remember correctly, are: > > - The SourceProxy name attribute may need to be the name of your actual > writer (here it's XMLPImageDataWriter) though I don't think so > - You probably want to include FileName, WriteFrequency and > PaddingAmount properties here. > - In the Hints section the WriterProxy should have the name attribute > set to the actual writer from your plugin. > > If that doesn't seem to work, I'd suggest looking at coprocessing.py's > RegisterWriter(), WriterParamtersProxy() and WriteData() methods. > > Best, > > Andy > > > > On Tue, Feb 27, 2018 at 10:11 AM, Louka Jacques--Chevallier < > louka.jacques--chevallier at pi.esisar.grenoble-inp.fr> wrote: > > > Hello, > > I'm trying to implement a custom asynchronous writer as a plugin for > > paraview / Catalyst in situ. > > > > What actually works : > > -The writer works when it's invoked as pure c++ > > -The xml that describes the writer seems OK as it shows the right > > extensions when using the "save data" feature in PV (after being imported > > of course) > > -I already added a plugin filter (not writer) to paraview and it works > > like a charm, so it's about the writer properties in particular > > -I'm able to display it as an entry in the in situ Writers menu (using > the > > proxy group : in situ_writer_parameters) > > -Exporting a pipeline (in python) using this writer works well, it's > shown > > with the right parameters > > > > What doesn't work : > > -When importing the (previously exported) pipeline.py, it seems that the > > writer is not found (meanwhile the filter is) > > > > What has been tried : > > -Using the LoadPlugin("mylib.so") in python > > -Recompiling unsuccessfully catalyst with the new files for the writer > > -Looking for plugins used the same way with in situ, but found nothing... > > > > I don't really know if it is even possible, or if it has been done > before, > > any idea / suggestion will be appreciated ! ^.^ > > Regards, > > Louka > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at http://www.kitware.com/ > > opensource/opensource.html > > > > Search the list archives at: http://markmail.org/search/?q= > > Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > https://public.kitware.com/mailman/listinfo/paraview-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From louka.jacques--chevallier at pi.esisar.grenoble-inp.fr Wed Feb 28 09:44:41 2018 From: louka.jacques--chevallier at pi.esisar.grenoble-inp.fr (Louka Jacques--Chevallier) Date: Wed, 28 Feb 2018 15:44:41 +0100 (CET) Subject: [Paraview-developers] Adding a Writer plugin to Catalyst in situ In-Reply-To: References: <1579046120.8924788.1519743447357.JavaMail.zimbra@pi.esisar.grenoble-inp.fr> <1691129073.8927804.1519744319371.JavaMail.zimbra@pi.esisar.grenoble-inp.fr> <686988387.9047122.1519821131043.JavaMail.zimbra@pi.esisar.grenoble-inp.fr> Message-ID: <1644338774.9064701.1519829081073.JavaMail.zimbra@pi.esisar.grenoble-inp.fr> Well, everything is working (or wip), but it's quite hard to understand at first, the user guide is clean, but to me, it lacks examples and details. I would like to share the project, but I can't as I'm currently a student working for a company (internship-like) to fullfill my engineering degree. The project is confidential. (We are three working on the PV-Catalyst part, so debugging goes quite fast) I still can give you few informations : We are writing a PV Custom app and using it with Catalyst. The writer is used to send data asynchronously (new thread) on the network (for supervision protocols). And... It works (Yay !), no dead end on this side. Best, Louka ----- Mail original ----- De: "Andy Bauer" ?: PI22-2018 at pi.esisar.grenoble-inp.fr Cc: "paraview-developers" Envoy?: Mercredi 28 F?vrier 2018 13:39:17 Objet: Re: [Paraview-developers] Adding a Writer plugin to Catalyst in situ Is everything working for you now with the plugin writer and Catalyst? Just curious -- would it be possible to share what you're trying to do with Catalyst? We like to publicize Catalyst success stories as well as keep track of the different use cases. Also, what's the format that you're writing data out in? That may be something that we could add in to ParaView itself which would save the trouble of dealing with a plugin. Best, Andy On Wed, Feb 28, 2018 at 7:32 AM, Louka Jacques--Chevallier < louka.jacques--chevallier at pi.esisar.grenoble-inp.fr> wrote: > Hi, > Thank you, this part was already done the right way, the problem occured > while importing the pipeling.py in catalyst. > But in the meantime, I realized that it was a missing attribute and a typo > that were sort of hiding each other... > Thank you for the fast answer though ! > Regards, > > > ----- Mail original ----- > De: "Andy Bauer" > ?: PI22-2018 at pi.esisar.grenoble-inp.fr > Cc: "paraview-developers" > Envoy?: Mardi 27 F?vrier 2018 16:48:53 > Objet: Re: [Paraview-developers] Adding a Writer plugin to Catalyst in situ > > Hi, > > The key thing is that in the GUI you don't actually create a writer for the > Catalyst pipeline, you need to create a stub for the writer that gets > filled in when you run Catalyst. For example, looking in utilities.xml for > the XMLPImageDataWriter stub: > ================= > label="Parallel Image Data Writer"> > > > > > > > > > > The input. > > > > number_of_elements="1" > default_values="filename_%t.pvti"> > > > number_of_elements="1" > default_values="1"> > > > > number_of_elements="1" > default_values="0"> > > > > > > > > > > > > > ================== > > Note that this is in the insitu_writers_parameters group in that file. Some > subtleties for this, if I remember correctly, are: > > - The SourceProxy name attribute may need to be the name of your actual > writer (here it's XMLPImageDataWriter) though I don't think so > - You probably want to include FileName, WriteFrequency and > PaddingAmount properties here. > - In the Hints section the WriterProxy should have the name attribute > set to the actual writer from your plugin. > > If that doesn't seem to work, I'd suggest looking at coprocessing.py's > RegisterWriter(), WriterParamtersProxy() and WriteData() methods. > > Best, > > Andy > > > > On Tue, Feb 27, 2018 at 10:11 AM, Louka Jacques--Chevallier < > louka.jacques--chevallier at pi.esisar.grenoble-inp.fr> wrote: > > > Hello, > > I'm trying to implement a custom asynchronous writer as a plugin for > > paraview / Catalyst in situ. > > > > What actually works : > > -The writer works when it's invoked as pure c++ > > -The xml that describes the writer seems OK as it shows the right > > extensions when using the "save data" feature in PV (after being imported > > of course) > > -I already added a plugin filter (not writer) to paraview and it works > > like a charm, so it's about the writer properties in particular > > -I'm able to display it as an entry in the in situ Writers menu (using > the > > proxy group : in situ_writer_parameters) > > -Exporting a pipeline (in python) using this writer works well, it's > shown > > with the right parameters > > > > What doesn't work : > > -When importing the (previously exported) pipeline.py, it seems that the > > writer is not found (meanwhile the filter is) > > > > What has been tried : > > -Using the LoadPlugin("mylib.so") in python > > -Recompiling unsuccessfully catalyst with the new files for the writer > > -Looking for plugins used the same way with in situ, but found nothing... > > > > I don't really know if it is even possible, or if it has been done > before, > > any idea / suggestion will be appreciated ! ^.^ > > Regards, > > Louka > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at http://www.kitware.com/ > > opensource/opensource.html > > > > Search the list archives at: http://markmail.org/search/?q= > > Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > https://public.kitware.com/mailman/listinfo/paraview-developers > > > From cory.quammen at kitware.com Wed Feb 28 10:33:14 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 28 Feb 2018 10:33:14 -0500 Subject: [Paraview-developers] ParaView 5.5.0-RC1 tagged In-Reply-To: References: Message-ID: Hi folks, Due to several issues identified with 5.5.0-RC1, we are going to skip releasing the 5.5.0-RC1 binaries and go directly to 5.5.0-RC2 later this week. Thanks, Cory On Mon, Feb 26, 2018 at 2:53 PM, Cory Quammen wrote: > Dear ParaView developers, > > ParaView 5.5.0-RC1 has been tagged (tag "v5.5.0-RC1"). Binaries are being > generated and should be available from the ParaView downloads web page [1] > some time tomorrow. > > Thank you, > Cory > > [1] https://www.paraview.org/download/ > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Wed Feb 28 10:33:30 2018 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 28 Feb 2018 10:33:30 -0500 Subject: [Paraview-developers] Resolve (paraview) dependencies of plugin In-Reply-To: <1519812719.2004.9.camel@gmail.com> References: <1519812719.2004.9.camel@gmail.com> Message-ID: <20180228153330.GA14933@megas.kitware.com> On Wed, Feb 28, 2018 at 11:11:59 +0100, hermann.detz at gmail.com wrote: > libvtkPVClientServerCoreCore-pv5.4.so.1 => not found > libvtkCommonExecutionModel-pv5.4.so.1 => not found > libvtkCommonDataModel-pv5.4.so.1 => not found > libvtkClientServer-pv5.4.so.1 => not found > libvtkCommonCore-pv5.4.so.1 => not found > > Obviously, the plugin depends on paraview libaries (makes sense so > far), which it can't find. Now I should admit, that paraview was no > really installed on the linux system, but just downloaded as binary > distribution. I'm aware of the common library search paths in Linux. My > problem is now, this plugin was developed to be used by a group of > users, I don't have direct relations with. They will download paraview > somehow and get it to run. I can't rely on them putting the binary into > the correct path to find the libraries. > > Is there a way, how to statically link these libraries with the plugin > (although this is completely against the idea of having shared libs)? > Any Cmake defines, I'm missing? Using static libraries wouldn't work since you'd then have two copies of important statics. Instead, since these libraries are intended to be provided by the loading executable, you can use `install_name_tool` to rename the references to have `@executable_path/../Libraries/` as a prefix. This will tell the application to look relative to the binary's location for these libraries. Something like this: install_name_tool -change libvtkPVClientServerCoreCore-pv5.4.so.1 @executable_path/../Libraries/libvtkPVClientServerCoreCore-pv5.4.so.1 for each ParaView-provided library. Any libraries the plugin is supposed to come with can use `@loader_path/` and move with the plugin. --Ben From dave.demarle at kitware.com Wed Feb 28 11:19:23 2018 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 28 Feb 2018 11:19:23 -0500 Subject: [Paraview-developers] how to tag VTK, PV and PVSB changes destined for 5.5.0.RC2? Message-ID: Hey Gang, but mostly Corey, How should we be flagging our changes to ensure that they get into the next release? thanks David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Wed Feb 28 11:36:29 2018 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 28 Feb 2018 11:36:29 -0500 Subject: [Paraview-developers] how to tag VTK, PV and PVSB changes destined for 5.5.0.RC2? In-Reply-To: References: Message-ID: <20180228163629.GA1759@megas.kitware.com> On Wed, Feb 28, 2018 at 11:19:23 -0500, David E DeMarle wrote: > How should we be flagging our changes to ensure that they get into the next > release? Mark them as being backported to the relevant branch in the description of the MR (at the end; they work just like the `Do:` commands): VTK: Backport: paraview/release ParaView and the superbuild: Backport: release --Ben From ben.boeckel at kitware.com Wed Feb 28 11:52:43 2018 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 28 Feb 2018 11:52:43 -0500 Subject: [Paraview-developers] how to tag VTK, PV and PVSB changes destined for 5.5.0.RC2? In-Reply-To: <20180228163629.GA1759@megas.kitware.com> References: <20180228163629.GA1759@megas.kitware.com> Message-ID: <20180228165243.GA16306@megas.kitware.com> On Wed, Feb 28, 2018 at 11:36:29 -0500, Ben Boeckel wrote: > VTK: > > Backport: paraview/release There's no milestone for this, but CC'ing at least Cory would be good. > ParaView and the superbuild: > > Backport: release There's the 5.5 milestone here. --Ben From cory.quammen at kitware.com Wed Feb 28 12:00:02 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 28 Feb 2018 12:00:02 -0500 Subject: [Paraview-developers] how to tag VTK, PV and PVSB changes destined for 5.5.0.RC2? In-Reply-To: <20180228163629.GA1759@megas.kitware.com> References: <20180228163629.GA1759@megas.kitware.com> Message-ID: On Wed, Feb 28, 2018 at 11:36 AM, Ben Boeckel wrote: > On Wed, Feb 28, 2018 at 11:19:23 -0500, David E DeMarle wrote: > > How should we be flagging our changes to ensure that they get into the > next > > release? > > Mark them as being backported to the relevant branch in the description > of the MR (at the end; they work just like the `Do:` commands): > > VTK: > > Backport: paraview/release > Also make sure you base your VTK changes off VTK commit 9f073177 or earlier. The robot will check to make sure you have done this. > > ParaView and the superbuild: > > Backport: release > Please also base your ParaView changes off of the release branch. Again, the robot will check. Cory > > --Ben > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Feb 28 20:48:45 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 1 Mar 2018 01:48:45 +0000 Subject: [Paraview-developers] command that shows time left on clusters Message-ID: <5a6b8cec488d4cbe998e9df5352de922@ES01AMSNLNT.srn.sandia.gov> What is the command line that has ParaView start putting the time remaining on an external server in the Pipeline Browser? Where is this documented? Thanks, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0807 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 Violence is the last refuge of the incompetent. -- Isaac Asimov --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Feb 28 21:48:26 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 28 Feb 2018 21:48:26 -0500 Subject: [Paraview-developers] command that shows time left on clusters In-Reply-To: <5a6b8cec488d4cbe998e9df5352de922@ES01AMSNLNT.srn.sandia.gov> References: <5a6b8cec488d4cbe998e9df5352de922@ES01AMSNLNT.srn.sandia.gov> Message-ID: Alan, This is an option for pvserver, documented in `pvserver --help`: $ pvserver --help [lots of options] --timeout=opt Time (in minutes) since connecting with a client after which the server may timeout. The client typically shows warning messages before the server times out. --use-offscreen-rendering Render offscreen on the satellite processes. This option only works with software rendering or mangled Mesa on Unix. --version -V Give the version number and exit. For an hour timeout, use: $ pvserver --timeout=60 - Cory On Wed, Feb 28, 2018 at 8:48 PM, Scott, W Alan wrote: > What is the command line that has ParaView start putting the time > remaining on an external server in the Pipeline Browser? Where is this > documented? > > > > Thanks, > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0807 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > > > Violence is the last refuge of the incompetent. -- Isaac Asimov > > --------------------------------------------------------- > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview-developers > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Feb 28 22:26:57 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 28 Feb 2018 22:26:57 -0500 Subject: [Paraview-developers] information_only property doesn't update, please help In-Reply-To: References: Message-ID: Hi, I think you forgot to attach your small example. Could you do so? Thanks, Cory On Tue, Feb 27, 2018 at 12:43 PM, iusadhfoias sidufasipudf < asduifhssauidf at gmail.com> wrote: > Hello VTK developers, > several questions about the correct usage of information_only properties > have been asked over the years, but I didn't find a working solution. > > The attached example is a complete, tiny, source plugin ("MyInfoSource") > for paraview 5.4.1. It generates an empty PolyData output. I am only > interested in modifying and showing the source's properties. > > MyInfoSource has 3 properties (cf. InfoSource.xml): > 1) InputPoint allows to input three coordinates. > 2) CalculatedPoint has 'information_only="1"' and will be calculated > whenever InputPoint is set. > 3) ShowCalculatedPoint has 'information_property="CalculatedPoint"' and > is meant to output that calculated value. > > I am using a modified vtkInfoSource::SetInputPoint, which sets the > CalculatedPoint coordinates to twice the InputPoint coordinates whenever > InputPoint changes (cf. vtkInfoSource.cxx). > > I was expecting the "ShowCalculatedPoint" property to update in the > properties view, whenever I apply changes to InputPoint, but it doesn't > change. Only when I click "Restore application default setting values" for > MyInformationSource, then ShowCalculatedPoint shows twice the last value of > InputPoint. > > Can you reproduce this behaviour? > What needs to be changed, so that ShowCalculatedPoint always shows twice > the InputPoint coordinates after changes are applied? > > Many thanks, > Jussuf > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview-developers > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: