From cory.quammen at kitware.com Mon Jan 8 15:48:07 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 8 Jan 2018 15:48:07 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: Lets rename Layout? In-Reply-To: <316a93e460354b059c6431d4495eca0e@ES01AMSNLNT.srn.sandia.gov> References: <316a93e460354b059c6431d4495eca0e@ES01AMSNLNT.srn.sandia.gov> Message-ID: My 2 cents: If we want to quickly resolve the ambiguity between render view layouts and window layouts, how about we rename "Window Layout" to "Window Arrangement"? That would be simpler from an implementation perspective, and would solve the immediate confusion in the overloaded term "layout". I agree that "Layout" is not the greatest noun for a particular layout of render windows. However, Layout is deeply embedded in the source code, including Python traces (see paraview.simple functions GetLayout(), CreateLayout(), GetViewsInLayout(), etc.). If we renamed render view layouts to "canvases" or some other term, I would like to make the corresponding change in the source code as well.This isn't too hard, but requires taking steps to ensure backwards compatibility, update tests, and so on.... it's a little bigger fish to fry. What do you think? Thanks, Cory On Thu, Dec 14, 2017 at 7:47 PM, Scott, W Alan wrote: > My two favorites, so far, in order, are > > * Canvas > * View Pane > > Alan > >> -----Original Message----- >> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> Sent: Thursday, December 14, 2017 2:37 PM >> To: Scott, W Alan >> Cc: paraview-developers at paraview.org >> Subject: [EXTERNAL] Re: [Paraview-developers] Lets rename Layout? >> >> Another option: >> >> * View Pane >> >> >> >> On Thu, Dec 14, 2017 at 4:30 PM, Scott, W Alan wrote: >> > Ken and I have been trying to figure out nomenclature for the File/ >> > Load Window Layout. This is confusing with ?Layout?. We have >> > concluded that ?Layout? is the wrong name for the tab that shows at >> > the upper left of the 3d window. How about we rename it? Here were >> some ideas Ken came up with: >> > >> > >> > >> > View Group (nah) >> > >> > View Tab (nah) >> > >> > Multi-View (better) >> > >> > Canvas (My favorite) >> > >> > View Region (probably not). >> > >> > >> > >> > Thoughts? >> > >> > >> > >> > 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 >> > > _______________________________________________ > 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 -- Cory Quammen Staff R&D Engineer Kitware, Inc. From wascott at sandia.gov Mon Jan 8 17:12:59 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 8 Jan 2018 22:12:59 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Lets rename Layout? In-Reply-To: References: <316a93e460354b059c6431d4495eca0e@ES01AMSNLNT.srn.sandia.gov> Message-ID: Seems silly to add that much work, and stir-age to the code, if we can word smith around the issue. How about Save/ Load Renderview Size, or Save/Load Window drawable Size? > -----Original Message----- > From: Cory Quammen [mailto:cory.quammen at kitware.com] > Sent: Monday, January 8, 2018 1:48 PM > To: Scott, W Alan > Cc: Ayachit, Utkarsh (External Contacts) ; > paraview-developers at paraview.org > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Lets rename Layout? > > My 2 cents: > > If we want to quickly resolve the ambiguity between render view layouts and > window layouts, how about we rename "Window Layout" to "Window > Arrangement"? That would be simpler from an implementation perspective, > and would solve the immediate confusion in the overloaded term "layout". > > I agree that "Layout" is not the greatest noun for a particular layout of render > windows. However, Layout is deeply embedded in the source code, including > Python traces (see paraview.simple functions GetLayout(), CreateLayout(), > GetViewsInLayout(), etc.). If we renamed render view layouts to "canvases" > or some other term, I would like to make the corresponding change in the > source code as well.This isn't too hard, but requires taking steps to ensure > backwards compatibility, update tests, and so on.... it's a little bigger fish to > fry. > > What do you think? > > Thanks, > Cory > > On Thu, Dec 14, 2017 at 7:47 PM, Scott, W Alan wrote: > > My two favorites, so far, in order, are > > > > * Canvas > > * View Pane > > > > Alan > > > >> -----Original Message----- > >> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> Sent: Thursday, December 14, 2017 2:37 PM > >> To: Scott, W Alan > >> Cc: paraview-developers at paraview.org > >> Subject: [EXTERNAL] Re: [Paraview-developers] Lets rename Layout? > >> > >> Another option: > >> > >> * View Pane > >> > >> > >> > >> On Thu, Dec 14, 2017 at 4:30 PM, Scott, W Alan > wrote: > >> > Ken and I have been trying to figure out nomenclature for the File/ > >> > Load Window Layout. This is confusing with ?Layout?. We have > >> > concluded that ?Layout? is the wrong name for the tab that shows at > >> > the upper left of the 3d window. How about we rename it? Here > >> > were > >> some ideas Ken came up with: > >> > > >> > > >> > > >> > View Group (nah) > >> > > >> > View Tab (nah) > >> > > >> > Multi-View (better) > >> > > >> > Canvas (My favorite) > >> > > >> > View Region (probably not). > >> > > >> > > >> > > >> > Thoughts? > >> > > >> > > >> > > >> > 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 > >> > > > _______________________________________________ > > 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 > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. From cory.quammen at kitware.com Mon Jan 8 17:26:11 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 8 Jan 2018 17:26:11 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: Lets rename Layout? In-Reply-To: References: <316a93e460354b059c6431d4495eca0e@ES01AMSNLNT.srn.sandia.gov> Message-ID: My understanding is that "Save/Load Window Layout" refers to the layout and size of all the Qt windows in ParaView. That includes the Render View size, but also other things such as whether control panels are docked, where they are docked, and so on. Hence my suggestion for "Arrangement". I don't think "Renderview Size" or "Drawable Size" quite captures the full behavior of what these menu items do. On Mon, Jan 8, 2018 at 5:12 PM, Scott, W Alan wrote: > Seems silly to add that much work, and stir-age to the code, if we can word smith around the issue. > > How about Save/ Load Renderview Size, or Save/Load Window drawable Size? > > > >> -----Original Message----- >> From: Cory Quammen [mailto:cory.quammen at kitware.com] >> Sent: Monday, January 8, 2018 1:48 PM >> To: Scott, W Alan >> Cc: Ayachit, Utkarsh (External Contacts) ; >> paraview-developers at paraview.org >> Subject: Re: [Paraview-developers] [EXTERNAL] Re: Lets rename Layout? >> >> My 2 cents: >> >> If we want to quickly resolve the ambiguity between render view layouts and >> window layouts, how about we rename "Window Layout" to "Window >> Arrangement"? That would be simpler from an implementation perspective, >> and would solve the immediate confusion in the overloaded term "layout". >> >> I agree that "Layout" is not the greatest noun for a particular layout of render >> windows. However, Layout is deeply embedded in the source code, including >> Python traces (see paraview.simple functions GetLayout(), CreateLayout(), >> GetViewsInLayout(), etc.). If we renamed render view layouts to "canvases" >> or some other term, I would like to make the corresponding change in the >> source code as well.This isn't too hard, but requires taking steps to ensure >> backwards compatibility, update tests, and so on.... it's a little bigger fish to >> fry. >> >> What do you think? >> >> Thanks, >> Cory >> >> On Thu, Dec 14, 2017 at 7:47 PM, Scott, W Alan wrote: >> > My two favorites, so far, in order, are >> > >> > * Canvas >> > * View Pane >> > >> > Alan >> > >> >> -----Original Message----- >> >> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> Sent: Thursday, December 14, 2017 2:37 PM >> >> To: Scott, W Alan >> >> Cc: paraview-developers at paraview.org >> >> Subject: [EXTERNAL] Re: [Paraview-developers] Lets rename Layout? >> >> >> >> Another option: >> >> >> >> * View Pane >> >> >> >> >> >> >> >> On Thu, Dec 14, 2017 at 4:30 PM, Scott, W Alan >> wrote: >> >> > Ken and I have been trying to figure out nomenclature for the File/ >> >> > Load Window Layout. This is confusing with ?Layout?. We have >> >> > concluded that ?Layout? is the wrong name for the tab that shows at >> >> > the upper left of the 3d window. How about we rename it? Here >> >> > were >> >> some ideas Ken came up with: >> >> > >> >> > >> >> > >> >> > View Group (nah) >> >> > >> >> > View Tab (nah) >> >> > >> >> > Multi-View (better) >> >> > >> >> > Canvas (My favorite) >> >> > >> >> > View Region (probably not). >> >> > >> >> > >> >> > >> >> > Thoughts? >> >> > >> >> > >> >> > >> >> > 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 >> >> > >> > _______________________________________________ >> > 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 >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From wascott at sandia.gov Mon Jan 8 17:38:55 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 8 Jan 2018 22:38:55 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Lets rename Layout? In-Reply-To: References: <316a93e460354b059c6431d4495eca0e@ES01AMSNLNT.srn.sandia.gov> Message-ID: <0c69dac43f63484cab154fe1470f1fdd@ES01AMSNLNT.srn.sandia.gov> Let's go with your recommendation of save window arrangement? > -----Original Message----- > From: Cory Quammen [mailto:cory.quammen at kitware.com] > Sent: Monday, January 8, 2018 3:26 PM > To: Scott, W Alan > Cc: Ayachit, Utkarsh (External Contacts) ; > paraview-developers at paraview.org > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Lets rename Layout? > > My understanding is that "Save/Load Window Layout" refers to the layout > and size of all the Qt windows in ParaView. That includes the Render View > size, but also other things such as whether control panels are docked, where > they are docked, and so on. Hence my suggestion for "Arrangement". I don't > think "Renderview Size" or "Drawable Size" > quite captures the full behavior of what these menu items do. > > On Mon, Jan 8, 2018 at 5:12 PM, Scott, W Alan wrote: > > Seems silly to add that much work, and stir-age to the code, if we can word > smith around the issue. > > > > How about Save/ Load Renderview Size, or Save/Load Window drawable > Size? > > > > > > > >> -----Original Message----- > >> From: Cory Quammen [mailto:cory.quammen at kitware.com] > >> Sent: Monday, January 8, 2018 1:48 PM > >> To: Scott, W Alan > >> Cc: Ayachit, Utkarsh (External Contacts) > >> ; paraview-developers at paraview.org > >> Subject: Re: [Paraview-developers] [EXTERNAL] Re: Lets rename Layout? > >> > >> My 2 cents: > >> > >> If we want to quickly resolve the ambiguity between render view > >> layouts and window layouts, how about we rename "Window Layout" to > >> "Window Arrangement"? That would be simpler from an implementation > >> perspective, and would solve the immediate confusion in the overloaded > term "layout". > >> > >> I agree that "Layout" is not the greatest noun for a particular > >> layout of render windows. However, Layout is deeply embedded in the > >> source code, including Python traces (see paraview.simple functions > >> GetLayout(), CreateLayout(), GetViewsInLayout(), etc.). If we renamed > render view layouts to "canvases" > >> or some other term, I would like to make the corresponding change in > >> the source code as well.This isn't too hard, but requires taking > >> steps to ensure backwards compatibility, update tests, and so on.... > >> it's a little bigger fish to fry. > >> > >> What do you think? > >> > >> Thanks, > >> Cory > >> > >> On Thu, Dec 14, 2017 at 7:47 PM, Scott, W Alan > wrote: > >> > My two favorites, so far, in order, are > >> > > >> > * Canvas > >> > * View Pane > >> > > >> > Alan > >> > > >> >> -----Original Message----- > >> >> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> >> Sent: Thursday, December 14, 2017 2:37 PM > >> >> To: Scott, W Alan > >> >> Cc: paraview-developers at paraview.org > >> >> Subject: [EXTERNAL] Re: [Paraview-developers] Lets rename Layout? > >> >> > >> >> Another option: > >> >> > >> >> * View Pane > >> >> > >> >> > >> >> > >> >> On Thu, Dec 14, 2017 at 4:30 PM, Scott, W Alan > >> >> > >> wrote: > >> >> > Ken and I have been trying to figure out nomenclature for the > >> >> > File/ Load Window Layout. This is confusing with ?Layout?. We > >> >> > have concluded that ?Layout? is the wrong name for the tab that > >> >> > shows at the upper left of the 3d window. How about we rename > >> >> > it? Here were > >> >> some ideas Ken came up with: > >> >> > > >> >> > > >> >> > > >> >> > View Group (nah) > >> >> > > >> >> > View Tab (nah) > >> >> > > >> >> > Multi-View (better) > >> >> > > >> >> > Canvas (My favorite) > >> >> > > >> >> > View Region (probably not). > >> >> > > >> >> > > >> >> > > >> >> > Thoughts? > >> >> > > >> >> > > >> >> > > >> >> > 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 > >> >> > > >> > _______________________________________________ > >> > 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 > >> > >> > >> > >> -- > >> Cory Quammen > >> Staff R&D Engineer > >> Kitware, Inc. > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. From david.thompson at kitware.com Wed Jan 17 14:32:11 2018 From: david.thompson at kitware.com (David Thompson) Date: Wed, 17 Jan 2018 14:32:11 -0500 Subject: [Paraview-developers] QToolBar plugin for ParaView Message-ID: <769DAEAB-C5A7-418F-96BE-47997A804F84@kitware.com> Hi all, I'm working on a ParaView plugin that adds a toolbar. The problem is that the toolbar needs to hold a QWidget (a QComboBox), not a QAction. This doesn't seem supported by ParaView because it does not provide access to its QMainWindow and insists on creating menus/toolbars itself without giving the plugin access to them. I have a small change to the pqPluginActionGroupBehavior that will provide more flexibility (see below) and will submit a MR if people agree that it's the right way to go about things. The approach it takes is to check the QActionGroup defined in the plugin for a method named "customizeToolBar(QToolBar*)" and call it with the newly-constructed tool bar if the method exists. Any comments? Thanks, David PS. This change, plus the addition of an include for are all that's needed: @@ -108,7 +110,17 @@ void pqPluginActionGroupBehavior::addPluginInterface(QObject* iface) { QToolBar* tb = new QToolBar(splitName[1], mainWindow); tb->setObjectName(splitName[1]); - tb->addActions(agi->actionGroup()->actions()); + auto actionGroup = agi->actionGroup(); + tb->addActions(actionGroup->actions()); + // If the action group has a public slot named "customizeToolBar" that accepts + // a toolbar pointer, invoke that method so that custom widgets may be added. + if (actionGroup->metaObject()->indexOfSlot("customizeToolBar(QToolBar*)") >= 0) + { + QMetaObject::invokeMethod( + actionGroup, "customizeToolBar", + Qt::DirectConnection, + Q_ARG(QToolBar*, tb)); + } From utkarsh.ayachit at kitware.com Thu Jan 18 09:46:07 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 18 Jan 2018 09:46:07 -0500 Subject: [Paraview-developers] QToolBar plugin for ParaView In-Reply-To: <769DAEAB-C5A7-418F-96BE-47997A804F84@kitware.com> References: <769DAEAB-C5A7-418F-96BE-47997A804F84@kitware.com> Message-ID: Sure! Alternatively, we could just add a new plugin type to add a toolbar. I can see how it could be easier for some developers to just add custom QToolBar rather than doing the same via QActionGroup interface. Utkarsh On Wed, Jan 17, 2018 at 2:32 PM, David Thompson wrote: > Hi all, > > I'm working on a ParaView plugin that adds a toolbar. The problem is that the toolbar needs to hold a QWidget (a QComboBox), not a QAction. This doesn't seem supported by ParaView because it does not provide access to its QMainWindow and insists on creating menus/toolbars itself without giving the plugin access to them. > > I have a small change to the pqPluginActionGroupBehavior that will provide more flexibility (see below) and will submit a MR if people agree that it's the right way to go about things. The approach it takes is to check the QActionGroup defined in the plugin for a method named "customizeToolBar(QToolBar*)" and call it with the newly-constructed tool bar if the method exists. Any comments? > > Thanks, > David > > PS. This change, plus the addition of an include for are all that's needed: > > @@ -108,7 +110,17 @@ void pqPluginActionGroupBehavior::addPluginInterface(QObject* iface) > { > QToolBar* tb = new QToolBar(splitName[1], mainWindow); > tb->setObjectName(splitName[1]); > - tb->addActions(agi->actionGroup()->actions()); > + auto actionGroup = agi->actionGroup(); > + tb->addActions(actionGroup->actions()); > + // If the action group has a public slot named "customizeToolBar" that accepts > + // a toolbar pointer, invoke that method so that custom widgets may be added. > + if (actionGroup->metaObject()->indexOfSlot("customizeToolBar(QToolBar*)") >= 0) > + { > + QMetaObject::invokeMethod( > + actionGroup, "customizeToolBar", > + Qt::DirectConnection, > + Q_ARG(QToolBar*, tb)); > + } > > _______________________________________________ > 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 wascott at sandia.gov Thu Jan 18 13:20:52 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 18 Jan 2018 18:20:52 +0000 Subject: [Paraview-developers] Gitlab Message-ID: <956ed045525f44c9907f4fce25b7734e@ES01AMSNLNT.srn.sandia.gov> Is https://gitlab.kitware.com down? chama $ git clone https://gitlab.kitware.com/paraview/paraview-superbuild.git Cloning into 'paraview-superbuild'... fatal: unable to access 'https://gitlab.kitware.com/paraview/paraview-superbuild.git/': The requested URL returned error: 503 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 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Jan 18 13:27:57 2018 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 18 Jan 2018 13:27:57 -0500 Subject: [Paraview-developers] Gitlab In-Reply-To: <956ed045525f44c9907f4fce25b7734e@ES01AMSNLNT.srn.sandia.gov> References: <956ed045525f44c9907f4fce25b7734e@ES01AMSNLNT.srn.sandia.gov> Message-ID: Yes. Our guys are working on it. Apologies for the disruption. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 <(518)%20881-4909> On Thu, Jan 18, 2018 at 1:20 PM, Scott, W Alan wrote: > Is https://gitlab.kitware.com down? > > > > chama $ git clone https://gitlab.kitware.com/par > aview/paraview-superbuild.git > > Cloning into 'paraview-superbuild'... > > fatal: unable to access 'https://gitlab.kitware.com/pa > raview/paraview-superbuild.git/': The requested URL returned error: 503 > > > > 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/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 wascott at sandia.gov Thu Jan 18 13:29:01 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 18 Jan 2018 18:29:01 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Gitlab In-Reply-To: References: <956ed045525f44c9907f4fce25b7734e@ES01AMSNLNT.srn.sandia.gov> Message-ID: <77dd3942ce974a20a278efbaea4ffd9c@ES01AMSNLNT.srn.sandia.gov> No prob. In the future, maybe a little note to the developers list?..... :-) Alan From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Thursday, January 18, 2018 11:28 AM To: Scott, W Alan Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] Gitlab Yes. Our guys are working on it. Apologies for the disruption. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Jan 18, 2018 at 1:20 PM, Scott, W Alan > wrote: Is https://gitlab.kitware.com down? chama $ git clone https://gitlab.kitware.com/paraview/paraview-superbuild.git Cloning into 'paraview-superbuild'... fatal: unable to access 'https://gitlab.kitware.com/paraview/paraview-superbuild.git/': The requested URL returned error: 503 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Jan 18 13:35:39 2018 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 18 Jan 2018 13:35:39 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: Gitlab In-Reply-To: <77dd3942ce974a20a278efbaea4ffd9c@ES01AMSNLNT.srn.sandia.gov> References: <956ed045525f44c9907f4fce25b7734e@ES01AMSNLNT.srn.sandia.gov> <77dd3942ce974a20a278efbaea4ffd9c@ES01AMSNLNT.srn.sandia.gov> Message-ID: It was unexpected. I happened to notice just a minute before you did. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 <(518)%20881-4909> On Thu, Jan 18, 2018 at 1:29 PM, Scott, W Alan wrote: > No prob. In the future, maybe a little note to the developers list?..... > :-) > > > > Alan > > > > *From:* David E DeMarle [mailto:dave.demarle at kitware.com] > *Sent:* Thursday, January 18, 2018 11:28 AM > *To:* Scott, W Alan > *Cc:* paraview-developers at paraview.org > *Subject:* [EXTERNAL] Re: [Paraview-developers] Gitlab > > > > Yes. Our guys are working on it. Apologies for the disruption. > > > > > David E DeMarle > Kitware, Inc. > Principal Engineer > 21 Corporate Drive > > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 <(518)%20881-4909> > > > > On Thu, Jan 18, 2018 at 1:20 PM, Scott, W Alan wrote: > > Is https://gitlab.kitware.com down? > > > > chama $ git clone https://gitlab.kitware.com/par > aview/paraview-superbuild.git > > Cloning into 'paraview-superbuild'... > > fatal: unable to access 'https://gitlab.kitware.com/pa > raview/paraview-superbuild.git/': The requested URL returned error: 503 > > > > 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/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 david.thompson at kitware.com Thu Jan 18 13:36:42 2018 From: david.thompson at kitware.com (David Thompson) Date: Thu, 18 Jan 2018 13:36:42 -0500 Subject: [Paraview-developers] QToolBar plugin for ParaView In-Reply-To: References: <769DAEAB-C5A7-418F-96BE-47997A804F84@kitware.com> Message-ID: <4019A701-6222-4B9E-B4A4-3E98BA369505@kitware.com> Hi Utkarsh, > Sure! Alternatively, we could just add a new plugin type to add a > toolbar. I can see how it could be easier for some developers to just > add custom QToolBar rather than doing the same via QActionGroup > interface. I didn't see a good pattern that would expose the QMainWindow (which is what I really want) while also making QToolBar and such easy, so I've submitted an MR for the QActionGroup change[1]. Thanks, David [1]: https://gitlab.kitware.com/paraview/paraview/merge_requests/2165 From dave.demarle at kitware.com Thu Jan 18 16:53:10 2018 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 18 Jan 2018 16:53:10 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: Gitlab In-Reply-To: References: <956ed045525f44c9907f4fce25b7734e@ES01AMSNLNT.srn.sandia.gov> <77dd3942ce974a20a278efbaea4ffd9c@ES01AMSNLNT.srn.sandia.gov> Message-ID: Should be back up now. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Jan 18, 2018 at 1:35 PM, David E DeMarle wrote: > It was unexpected. I happened to notice just a minute before you did. > > David E DeMarle > Kitware, Inc. > Principal Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 <(518)%20881-4909> > > On Thu, Jan 18, 2018 at 1:29 PM, Scott, W Alan wrote: > >> No prob. In the future, maybe a little note to the developers >> list?..... :-) >> >> >> >> Alan >> >> >> >> *From:* David E DeMarle [mailto:dave.demarle at kitware.com] >> *Sent:* Thursday, January 18, 2018 11:28 AM >> *To:* Scott, W Alan >> *Cc:* paraview-developers at paraview.org >> *Subject:* [EXTERNAL] Re: [Paraview-developers] Gitlab >> >> >> >> Yes. Our guys are working on it. Apologies for the disruption. >> >> >> >> >> David E DeMarle >> Kitware, Inc. >> Principal Engineer >> 21 Corporate Drive >> >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 <(518)%20881-4909> >> >> >> >> On Thu, Jan 18, 2018 at 1:20 PM, Scott, W Alan >> wrote: >> >> Is https://gitlab.kitware.com down? >> >> >> >> chama $ git clone https://gitlab.kitware.com/par >> aview/paraview-superbuild.git >> >> Cloning into 'paraview-superbuild'... >> >> fatal: unable to access 'https://gitlab.kitware.com/pa >> raview/paraview-superbuild.git/': The requested URL returned error: 503 >> >> >> >> 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 >> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Jan 18 20:22:43 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 19 Jan 2018 01:22:43 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Gitlab In-Reply-To: References: <956ed045525f44c9907f4fce25b7734e@ES01AMSNLNT.srn.sandia.gov> <77dd3942ce974a20a278efbaea4ffd9c@ES01AMSNLNT.srn.sandia.gov> Message-ID: <538c50100d2744dea3f2647142ca268a@ES01AMSNLNT.srn.sandia.gov> Thanks David. I have seen weirdness?s today ? failures with builds that then work. I wonder if the gitlab.kitware.com site is being somewhat flaky today? Thanks again for working on this, Alan From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Thursday, January 18, 2018 2:53 PM To: Scott, W Alan Cc: paraview-developers at paraview.org Subject: Re: [EXTERNAL] Re: [Paraview-developers] Gitlab Should be back up now. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Jan 18, 2018 at 1:35 PM, David E DeMarle > wrote: It was unexpected. I happened to notice just a minute before you did. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Jan 18, 2018 at 1:29 PM, Scott, W Alan > wrote: No prob. In the future, maybe a little note to the developers list?..... :-) Alan From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Thursday, January 18, 2018 11:28 AM To: Scott, W Alan > Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] Gitlab Yes. Our guys are working on it. Apologies for the disruption. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Jan 18, 2018 at 1:20 PM, Scott, W Alan > wrote: Is https://gitlab.kitware.com down? chama $ git clone https://gitlab.kitware.com/paraview/paraview-superbuild.git Cloning into 'paraview-superbuild'... fatal: unable to access 'https://gitlab.kitware.com/paraview/paraview-superbuild.git/': The requested URL returned error: 503 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Jan 19 10:53:00 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 19 Jan 2018 10:53:00 -0500 Subject: [Paraview-developers] QToolBar plugin for ParaView In-Reply-To: <4019A701-6222-4B9E-B4A4-3E98BA369505@kitware.com> References: <769DAEAB-C5A7-418F-96BE-47997A804F84@kitware.com> <4019A701-6222-4B9E-B4A4-3E98BA369505@kitware.com> Message-ID: > > > I didn't see a good pattern that would expose the QMainWindow (which is > what I really want) while also making QToolBar and such easy, so I've > submitted an MR for the QActionGroup change[1]. > I am not sure I follow. Here a quick fix [2]. I've also updated the GUIToolBar example to demonstrate this. [2] https://gitlab.kitware.com/paraview/paraview/merge_requests/2168 -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.thompson at kitware.com Fri Jan 19 11:10:37 2018 From: david.thompson at kitware.com (David Thompson) Date: Fri, 19 Jan 2018 11:10:37 -0500 Subject: [Paraview-developers] QToolBar plugin for ParaView In-Reply-To: References: <769DAEAB-C5A7-418F-96BE-47997A804F84@kitware.com> <4019A701-6222-4B9E-B4A4-3E98BA369505@kitware.com> Message-ID: Hi Utkarsh, >> I didn't see a good pattern that would expose the QMainWindow (which is what I really want) while also making QToolBar and such easy, so I've submitted an MR for the QActionGroup change[1]. > > I am not sure I follow. If plugins were simply passed the QMainWindow then not only could you add toolbars and menus yourself, but you could do other things. One example is calling QMainWindow::setDockNestingEnabled(true). But I haven't seen a way to expose QMainWindow that makes the basic stuff (adding toolbars/menus) as simple as the existing PV plugins. > Here a quick fix [2]. I've also updated the GUIToolBar example to demonstrate this. > [2] https://gitlab.kitware.com/paraview/paraview/merge_requests/2168 That looks good to me, I'll close my MR. Thanks, David From cornelis.bockemuehl at gmail.com Mon Jan 22 10:08:08 2018 From: cornelis.bockemuehl at gmail.com (Cornelis =?ISO-8859-1?Q?Bockem=FChl?=) Date: Mon, 22 Jan 2018 16:08:08 +0100 Subject: [Paraview-developers] Animation: spreadsheet view not synchronized with table Message-ID: <1516633688.3263.28.camel@gmail.com> Hello, To me it looks like this could be either some omission from my side or a bug in ParaView, but in any case I would be interested in a solution first of all! I have written a filter that takes some input ports and produces 5 output ports - the first being an "unstructured grid" and the others are tables. In the server manager XML I used hints to make sure that the tables are not automatically opened at once (). This works nicely so far. Now the filter is producing a time series, step by step modifying the "unstructured grid", and some data written to the tables per period. What I see now is that the "unstructured grid" is doing what I expect: I can go up and down along the time axis and it always shows the proper graphical output. I can also capture the data in a spreadsheet, and this is also properly updated. Not so the additional tables! In this case they are updated ONCE and never again, so I can have different scenarios: - I add the filter and press apply. This would bring me to step 0 - with empty tables. If I open now a spreadsheet view and look at any of them this correct. But if I now press "play" and go from step to step, only the "unstructured grid" gets updated, not the spreadsheet view. - I can also add the filter, press apply and immediately also "play". With that I am at the last step, and opening a spreadsheet view for the tables gives me the full tables - again correct. But again: if I go back in time, the tables stay as they were initially (i.e. full). Now I prepared a demo case for this. It has just two tables, one being shown immediately and the second only "on demand". Indeed I could almost reproduce the behaviour: the first table does what is expected, but the second not. Only difference with my full case: the second table NEVER shows anything, no matter if I press the "play" button earlier or later! It is interesting to note that the "Information" panel shows the tables correctly, like: X rows, Y columns - even if the spreadsheet view is completely empty. Or showing much more! My question from the beginning is now: Is there something that I would have to do to trigger a spreadsheet view update or is this a bug that needs to be fixed? (Actually I hope for the first because then I can quickly apply the fix in my own software and I am fine!...) I am attaching a package with source code (h, cxx and xml files) plus a screenshot that illustrates the case where the second table shows some content only in the properties panel (left), but not in the spreadsheet view (right). With many thanks for any helpful hints - and kind regards, Cornelis -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: TestTablesWithTimes.tar.gz Type: application/x-compressed-tar Size: 115423 bytes Desc: not available URL: From cornelis.bockemuehl at gmail.com Mon Jan 22 10:28:19 2018 From: cornelis.bockemuehl at gmail.com (Cornelis =?ISO-8859-1?Q?Bockem=FChl?=) Date: Mon, 22 Jan 2018 16:28:19 +0100 Subject: [Paraview-developers] Animation: spreadsheet view not synchronized with table In-Reply-To: References: <1516633688.3263.28.camel@gmail.com> Message-ID: <1516634899.3263.30.camel@gmail.com> Yes, this works fine! But it is also only one output port: In my case I have the problems not on the first port (port 0) but only on additional ports - which is illustrated in my stripped down code example, and also in the screenshot. Best Regards, Cornelis Am Montag, den 22.01.2018, 16:19 +0100 schrieb Mathieu Westphal: > Hello Cornelis > > > I've tested quickly the supports of table and time steps and it seems to works great. > Here is how i tested it : > > - Download attached .csv files > > - open table..csv (colapsed time series of files), show in a spreasheet view > - click play > > Let me know if this works on your end. > > Best, > > Mathieu Westphal > > > > > > On Mon, Jan 22, 2018 at 4:08 PM, Cornelis Bockem?hl wrote: > > Hello, > > > > > > To me it looks like this could be either some omission from my side or a bug in ParaView, but in any case I would be interested in a solution first of all! > > > > > > > > > > > > I have written a filter that takes some input ports and produces 5 output ports - the first being an "unstructured grid" and the others are tables. In the server manager XML I used hints to make sure that the tables are not automatically opened at once (). This works nicely so far. > > > > > > > > Now the filter is producing a time series, step by step modifying the "unstructured grid", and some data written to the tables per period. > > > > > > > > > > What I see now is that the "unstructured grid" is doing what I expect: I can go up and down along the time axis and it always shows the proper graphical output. I can also capture the data in a spreadsheet, and this is also properly updated. > > > > > > Not so the additional tables! In this case they are updated ONCE and never again, so I can have different scenarios: > > > > > > > > > > > > - I add the filter and press apply. This would bring me to step 0 - with empty tables. If I open now a spreadsheet view and look at any of them this correct. But if I now press "play" and go from step to step, only the "unstructured grid" gets updated, not the spreadsheet view. > > > > > > > > > > > > - I can also add the filter, press apply and immediately also "play". With that I am at the last step, and opening a spreadsheet view for the tables gives me the full tables - again correct. But again: if I go back in time, the tables stay as they were initially (i.e. full). > > > > > > > > > > > > > > Now I prepared a demo case for this. It has just two tables, one being shown immediately and the second only "on demand". Indeed I could almost reproduce the behaviour: the first table does what is expected, but the second not. Only difference with my full case: the second table NEVER shows anything, no matter if I press the "play" button earlier or later! > > > > > > > > It is interesting to note that the "Information" panel shows the tables correctly, like: X rows, Y columns - even if the spreadsheet view is completely empty. Or showing much more! > > > > > > > > > > > > My question from the beginning is now: Is there something that I would have to do to trigger a spreadsheet view update or is this a bug that needs to be fixed? (Actually I hope for the first because then I can quickly apply the fix in my own software and I am fine!...) > > > > > > > > > > I am attaching a package with source code (h, cxx and xml files) plus a screenshot that illustrates the case where the second table shows some content only in the properties panel (left), but not in the spreadsheet view (right). > > > > With many thanks for any helpful hints - and kind regards, > > Cornelis > > > > > > _______________________________________________ > > > > 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 cornelis.bockemuehl at gmail.com Mon Jan 22 10:40:01 2018 From: cornelis.bockemuehl at gmail.com (Cornelis =?ISO-8859-1?Q?Bockem=FChl?=) Date: Mon, 22 Jan 2018 16:40:01 +0100 Subject: [Paraview-developers] Animation: spreadsheet view not synchronized with table In-Reply-To: References: <1516633688.3263.28.camel@gmail.com> Message-ID: <1516635601.3263.33.camel@gmail.com> Hello, I just see that in the RequestInformation function I am adding the steps and range info only to the information object that I receive through GetInformationObject(0), but then I am working also with the objects 1, 2, etc.: Maybe this is the thing that I should change?? I will immediately try this in my code... Regards, Cornelis Am Montag, den 22.01.2018, 16:19 +0100 schrieb Mathieu Westphal: > Hello Cornelis > > > I've tested quickly the supports of table and time steps and it seems to works great. > Here is how i tested it : > > - Download attached .csv files > > - open table..csv (colapsed time series of files), show in a spreasheet view > - click play > > Let me know if this works on your end. > > Best, > > Mathieu Westphal > > > > > > On Mon, Jan 22, 2018 at 4:08 PM, Cornelis Bockem?hl wrote: > > Hello, > > > > > > To me it looks like this could be either some omission from my side or a bug in ParaView, but in any case I would be interested in a solution first of all! > > > > > > > > > > > > I have written a filter that takes some input ports and produces 5 output ports - the first being an "unstructured grid" and the others are tables. In the server manager XML I used hints to make sure that the tables are not automatically opened at once (). This works nicely so far. > > > > > > > > Now the filter is producing a time series, step by step modifying the "unstructured grid", and some data written to the tables per period. > > > > > > > > > > What I see now is that the "unstructured grid" is doing what I expect: I can go up and down along the time axis and it always shows the proper graphical output. I can also capture the data in a spreadsheet, and this is also properly updated. > > > > > > Not so the additional tables! In this case they are updated ONCE and never again, so I can have different scenarios: > > > > > > > > > > > > - I add the filter and press apply. This would bring me to step 0 - with empty tables. If I open now a spreadsheet view and look at any of them this correct. But if I now press "play" and go from step to step, only the "unstructured grid" gets updated, not the spreadsheet view. > > > > > > > > > > > > - I can also add the filter, press apply and immediately also "play". With that I am at the last step, and opening a spreadsheet view for the tables gives me the full tables - again correct. But again: if I go back in time, the tables stay as they were initially (i.e. full). > > > > > > > > > > > > > > Now I prepared a demo case for this. It has just two tables, one being shown immediately and the second only "on demand". Indeed I could almost reproduce the behaviour: the first table does what is expected, but the second not. Only difference with my full case: the second table NEVER shows anything, no matter if I press the "play" button earlier or later! > > > > > > > > It is interesting to note that the "Information" panel shows the tables correctly, like: X rows, Y columns - even if the spreadsheet view is completely empty. Or showing much more! > > > > > > > > > > > > My question from the beginning is now: Is there something that I would have to do to trigger a spreadsheet view update or is this a bug that needs to be fixed? (Actually I hope for the first because then I can quickly apply the fix in my own software and I am fine!...) > > > > > > > > > > I am attaching a package with source code (h, cxx and xml files) plus a screenshot that illustrates the case where the second table shows some content only in the properties panel (left), but not in the spreadsheet view (right). > > > > With many thanks for any helpful hints - and kind regards, > > Cornelis > > > > > > _______________________________________________ > > > > 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 cornelis.bockemuehl at gmail.com Mon Jan 22 10:49:18 2018 From: cornelis.bockemuehl at gmail.com (Cornelis =?ISO-8859-1?Q?Bockem=FChl?=) Date: Mon, 22 Jan 2018 16:49:18 +0100 Subject: [Paraview-developers] Animation: spreadsheet view not synchronized with table In-Reply-To: References: <1516633688.3263.28.camel@gmail.com> Message-ID: <1516636158.3263.36.camel@gmail.com> ...and this was it indeed: changing the RequestInformation function in my strip-down example to the following solves the problem: int vtkTestTTSource::RequestInformation(vtkInformation* request, vtkInformationVector** inputVec tor, vtkInformationVector* outputVec tor) { if(!Superclass::RequestInformation(request, inputVector, outputVect or)) return 0; // tell the caller that we can provide time varying data and specify the range double tRange[] = {0., 1.}; // generate a vector with the steps - from 0 to numSteps Steps.resize(NumSteps + 1); for(int s = 0; s <= NumSteps; ++s) Steps[s] = (double)s / (double)NumSteps; // tell it to the information objects... for(int n = 0; n < 2; ++n) { vtkInformation* info = outputVector->GetInformationObject(n); info->Set(vtkStreamingDemandDrivenPipeline::TIME_RANGE(), tRange, 2); info->Set(vtkStreamingDemandDrivenPipeline::TIME_STEPS(), Steps.data(), Steps.size()); info->Set(CAN_HANDLE_PIECE_REQUEST(), 1); } return 1; } Sorry for all who wasted time for a problem that I have finally solved by my own! But still thanks for serving me as a "mirror" for the problem... With kind regards, Cornelis Am Montag, den 22.01.2018, 16:19 +0100 schrieb Mathieu Westphal: > Hello Cornelis > > > I've tested quickly the supports of table and time steps and it seems to works great. > Here is how i tested it : > > - Download attached .csv files > > - open table..csv (colapsed time series of files), show in a spreasheet view > - click play > > Let me know if this works on your end. > > Best, > > Mathieu Westphal > > > > > > On Mon, Jan 22, 2018 at 4:08 PM, Cornelis Bockem?hl wrote: > > Hello, > > > > > > To me it looks like this could be either some omission from my side or a bug in ParaView, but in any case I would be interested in a solution first of all! > > > > > > > > > > > > I have written a filter that takes some input ports and produces 5 output ports - the first being an "unstructured grid" and the others are tables. In the server manager XML I used hints to make sure that the tables are not automatically opened at once (). This works nicely so far. > > > > > > > > Now the filter is producing a time series, step by step modifying the "unstructured grid", and some data written to the tables per period. > > > > > > > > > > What I see now is that the "unstructured grid" is doing what I expect: I can go up and down along the time axis and it always shows the proper graphical output. I can also capture the data in a spreadsheet, and this is also properly updated. > > > > > > Not so the additional tables! In this case they are updated ONCE and never again, so I can have different scenarios: > > > > > > > > > > > > - I add the filter and press apply. This would bring me to step 0 - with empty tables. If I open now a spreadsheet view and look at any of them this correct. But if I now press "play" and go from step to step, only the "unstructured grid" gets updated, not the spreadsheet view. > > > > > > > > > > > > - I can also add the filter, press apply and immediately also "play". With that I am at the last step, and opening a spreadsheet view for the tables gives me the full tables - again correct. But again: if I go back in time, the tables stay as they were initially (i.e. full). > > > > > > > > > > > > > > Now I prepared a demo case for this. It has just two tables, one being shown immediately and the second only "on demand". Indeed I could almost reproduce the behaviour: the first table does what is expected, but the second not. Only difference with my full case: the second table NEVER shows anything, no matter if I press the "play" button earlier or later! > > > > > > > > It is interesting to note that the "Information" panel shows the tables correctly, like: X rows, Y columns - even if the spreadsheet view is completely empty. Or showing much more! > > > > > > > > > > > > My question from the beginning is now: Is there something that I would have to do to trigger a spreadsheet view update or is this a bug that needs to be fixed? (Actually I hope for the first because then I can quickly apply the fix in my own software and I am fine!...) > > > > > > > > > > I am attaching a package with source code (h, cxx and xml files) plus a screenshot that illustrates the case where the second table shows some content only in the properties panel (left), but not in the spreadsheet view (right). > > > > With many thanks for any helpful hints - and kind regards, > > Cornelis > > > > > > _______________________________________________ > > > > 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 wascott at sandia.gov Mon Jan 22 18:11:23 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 22 Jan 2018 23:11:23 +0000 Subject: [Paraview-developers] manual downloads Message-ID: <57d7ed882fd346cc884281932dbba9ba@ES01AMSNLNT.srn.sandia.gov> Hi guys, I am in the process of making a local build, where I cannot see the internet or Kitware git. I am downloading the dependencies manually from https://www.paraview.org/files/dependencies/. However, I was not able to find this documented on the SuperBuild website. Shouldn't it be documented on the SuperBuild website? 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 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Jan 22 19:21:50 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 22 Jan 2018 19:21:50 -0500 Subject: [Paraview-developers] manual downloads In-Reply-To: <57d7ed882fd346cc884281932dbba9ba@ES01AMSNLNT.srn.sandia.gov> References: <57d7ed882fd346cc884281932dbba9ba@ES01AMSNLNT.srn.sandia.gov> Message-ID: Alan, There is a section on assembling dependencies for offline builds: https://gitlab.kitware.com/paraview/paraview-superbuild#offline-builds Is that sufficient? Thanks, Cory On Mon, Jan 22, 2018 at 6:11 PM, Scott, W Alan wrote: > Hi guys, > > I am in the process of making a local build, where I cannot see the internet > or Kitware git. I am downloading the dependencies manually from > https://www.paraview.org/files/dependencies/. However, I was not able to > find this documented on the SuperBuild website. Shouldn?t it be documented > on the SuperBuild website? > > > > 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 > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From wascott at sandia.gov Mon Jan 22 19:36:13 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 23 Jan 2018 00:36:13 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: manual downloads In-Reply-To: References: <57d7ed882fd346cc884281932dbba9ba@ES01AMSNLNT.srn.sandia.gov> Message-ID: I sort of think not. If a user is on an isolated network (such as a company proprietary network, or classified network), all the user wants are the tarballs, and directions how to find same. He doesn't want to have to do another build from a machine that can see the internet. What normally happens, (and you could talk me into saying THIS is an acceptable solution) I find, is people start the build, fail on the build, then cut and paste what failed to a web browser. It would be nice to just know where that web page is, without having to go through the fail steps... Alan > -----Original Message----- > From: Cory Quammen [mailto:cory.quammen at kitware.com] > Sent: Monday, January 22, 2018 5:22 PM > To: Scott, W Alan > Cc: paraview-developers at paraview.org > Subject: [EXTERNAL] Re: [Paraview-developers] manual downloads > > Alan, > > There is a section on assembling dependencies for offline builds: > > https://gitlab.kitware.com/paraview/paraview-superbuild#offline-builds > > Is that sufficient? > > Thanks, > Cory > > On Mon, Jan 22, 2018 at 6:11 PM, Scott, W Alan > wrote: > > Hi guys, > > > > I am in the process of making a local build, where I cannot see the > > internet or Kitware git. I am downloading the dependencies manually > > from https://www.paraview.org/files/dependencies/. However, I was not > > able to find this documented on the SuperBuild website. Shouldn?t it > > be documented on the SuperBuild website? > > > > > > > > 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 > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. From utkarsh.ayachit at kitware.com Wed Jan 24 10:38:24 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 24 Jan 2018 10:38:24 -0500 Subject: [Paraview-developers] Updating to latest "master" (v5.4.1-1250-gaa11ae8) Message-ID: Folks, If you update to latest "master", please do a clean build to avoid running into issues with obsolete Python modules that were built in previous source versions. Thanks Utkarsh From cory.quammen at kitware.com Wed Jan 24 10:51:26 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 24 Jan 2018 10:51:26 -0500 Subject: [Paraview-developers] Updating to latest "master" (v5.4.1-1250-gaa11ae8) In-Reply-To: References: Message-ID: In addition, please note that some Python modules are no longer provided by ParaView and you may need to install them in the Python environment used by ParaView. The required modules are: * mpi4py - if you are building with PARAVIEW_ENABLE_PYTHON and PARAVIEW_USE_MPI. This is needed at CMake configuration time. * autobahn, twisted, and wslink - if you have PARAVIEW_ENABLE_WEB. If these are missing you will get a runtime error; you can install them after ParaView has been compiled if needed. Thanks, Cory On Wed, Jan 24, 2018 at 10:38 AM, Utkarsh Ayachit wrote: > Folks, > > If you update to latest "master", please do a clean build to avoid > running into issues with obsolete Python modules that were built in > previous source versions. > > Thanks > Utkarsh > _______________________________________________ > 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 -- Cory Quammen Staff R&D Engineer Kitware, Inc. From andy.bauer at kitware.com Wed Jan 24 10:54:37 2018 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 24 Jan 2018 10:54:37 -0500 Subject: [Paraview-developers] Updating to latest "master" (v5.4.1-1250-gaa11ae8) In-Reply-To: References: Message-ID: Has the superbuild been updated to optionally provide these python modules when building Python? On Wed, Jan 24, 2018 at 10:51 AM, Cory Quammen wrote: > In addition, please note that some Python modules are no longer > provided by ParaView and you may need to install them in the Python > environment used by ParaView. The required modules are: > > * mpi4py - if you are building with PARAVIEW_ENABLE_PYTHON and > PARAVIEW_USE_MPI. This is needed at CMake configuration time. > * autobahn, twisted, and wslink - if you have PARAVIEW_ENABLE_WEB. If > these are missing you will get a runtime error; you can install them > after ParaView has been compiled if needed. > > Thanks, > Cory > > > > On Wed, Jan 24, 2018 at 10:38 AM, Utkarsh Ayachit > wrote: > > Folks, > > > > If you update to latest "master", please do a clean build to avoid > > running into issues with obsolete Python modules that were built in > > previous source versions. > > > > Thanks > > Utkarsh > > _______________________________________________ > > 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 > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > _______________________________________________ > 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 wascott at sandia.gov Wed Jan 24 12:29:41 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 24 Jan 2018 17:29:41 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Updating to latest "master" (v5.4.1-1250-gaa11ae8) In-Reply-To: References: Message-ID: What Andy said. I?m just starting a Superbuild pull... Should I wait? Alan From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Andy Bauer Sent: Wednesday, January 24, 2018 8:55 AM To: Quammen, Cory (External Contacts) Cc: ParaView Developers Subject: [EXTERNAL] Re: [Paraview-developers] Updating to latest "master" (v5.4.1-1250-gaa11ae8) Has the superbuild been updated to optionally provide these python modules when building Python? On Wed, Jan 24, 2018 at 10:51 AM, Cory Quammen > wrote: In addition, please note that some Python modules are no longer provided by ParaView and you may need to install them in the Python environment used by ParaView. The required modules are: * mpi4py - if you are building with PARAVIEW_ENABLE_PYTHON and PARAVIEW_USE_MPI. This is needed at CMake configuration time. * autobahn, twisted, and wslink - if you have PARAVIEW_ENABLE_WEB. If these are missing you will get a runtime error; you can install them after ParaView has been compiled if needed. Thanks, Cory On Wed, Jan 24, 2018 at 10:38 AM, Utkarsh Ayachit > wrote: > Folks, > > If you update to latest "master", please do a clean build to avoid > running into issues with obsolete Python modules that were built in > previous source versions. > > Thanks > Utkarsh > _______________________________________________ > 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 -- Cory Quammen Staff R&D Engineer Kitware, Inc. _______________________________________________ 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 cory.quammen at kitware.com Wed Jan 24 12:48:29 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 24 Jan 2018 12:48:29 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: Updating to latest "master" (v5.4.1-1250-gaa11ae8) In-Reply-To: References: Message-ID: Alan and Andy, Superbuild has not been updated. I'll kick off a build and see what needs to be done, then let you know. Thanks, Cory On Wed, Jan 24, 2018 at 12:29 PM, Scott, W Alan wrote: > What Andy said. I?m just starting a Superbuild pull... Should I wait? > > > > Alan > > > > From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] > On Behalf Of Andy Bauer > Sent: Wednesday, January 24, 2018 8:55 AM > To: Quammen, Cory (External Contacts) > Cc: ParaView Developers > Subject: [EXTERNAL] Re: [Paraview-developers] Updating to latest "master" > (v5.4.1-1250-gaa11ae8) > > > > Has the superbuild been updated to optionally provide these python modules > when building Python? > > > > On Wed, Jan 24, 2018 at 10:51 AM, Cory Quammen > wrote: > > In addition, please note that some Python modules are no longer > provided by ParaView and you may need to install them in the Python > environment used by ParaView. The required modules are: > > * mpi4py - if you are building with PARAVIEW_ENABLE_PYTHON and > PARAVIEW_USE_MPI. This is needed at CMake configuration time. > * autobahn, twisted, and wslink - if you have PARAVIEW_ENABLE_WEB. If > these are missing you will get a runtime error; you can install them > after ParaView has been compiled if needed. > > Thanks, > Cory > > > > > On Wed, Jan 24, 2018 at 10:38 AM, Utkarsh Ayachit > wrote: >> Folks, >> >> If you update to latest "master", please do a clean build to avoid >> running into issues with obsolete Python modules that were built in >> previous source versions. >> >> Thanks >> Utkarsh >> _______________________________________________ >> 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 > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > _______________________________________________ > 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 > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From wascott at sandia.gov Wed Jan 24 12:50:19 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 24 Jan 2018 17:50:19 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Updating to latest "master" (v5.4.1-1250-gaa11ae8) In-Reply-To: References: Message-ID: <7ebeb4073d9a429297b71802936c796f@ES01AMSNLNT.srn.sandia.gov> Thanks. I assume that Superbuild will work on old clusters that don't have the mpi4py installed? Or, do I need my systems folks to install this? > -----Original Message----- > From: Cory Quammen [mailto:cory.quammen at kitware.com] > Sent: Wednesday, January 24, 2018 10:48 AM > To: Scott, W Alan > Cc: Bauer, Andy (External Contacts) ; ParaView > Developers > Subject: Re: [EXTERNAL] Re: [Paraview-developers] Updating to latest > "master" (v5.4.1-1250-gaa11ae8) > > Alan and Andy, > > Superbuild has not been updated. I'll kick off a build and see what needs to > be done, then let you know. > > Thanks, > Cory > > On Wed, Jan 24, 2018 at 12:29 PM, Scott, W Alan > wrote: > > What Andy said. I?m just starting a Superbuild pull... Should I wait? > > > > > > > > Alan > > > > > > > > From: Paraview-developers > > [mailto:paraview-developers-bounces at paraview.org] > > On Behalf Of Andy Bauer > > Sent: Wednesday, January 24, 2018 8:55 AM > > To: Quammen, Cory (External Contacts) > > Cc: ParaView Developers > > Subject: [EXTERNAL] Re: [Paraview-developers] Updating to latest > "master" > > (v5.4.1-1250-gaa11ae8) > > > > > > > > Has the superbuild been updated to optionally provide these python > > modules when building Python? > > > > > > > > On Wed, Jan 24, 2018 at 10:51 AM, Cory Quammen > > > > wrote: > > > > In addition, please note that some Python modules are no longer > > provided by ParaView and you may need to install them in the Python > > environment used by ParaView. The required modules are: > > > > * mpi4py - if you are building with PARAVIEW_ENABLE_PYTHON and > > PARAVIEW_USE_MPI. This is needed at CMake configuration time. > > * autobahn, twisted, and wslink - if you have PARAVIEW_ENABLE_WEB. If > > these are missing you will get a runtime error; you can install them > > after ParaView has been compiled if needed. > > > > Thanks, > > Cory > > > > > > > > > > On Wed, Jan 24, 2018 at 10:38 AM, Utkarsh Ayachit > > wrote: > >> Folks, > >> > >> If you update to latest "master", please do a clean build to avoid > >> running into issues with obsolete Python modules that were built in > >> previous source versions. > >> > >> Thanks > >> Utkarsh > >> _______________________________________________ > >> 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 > > > > > > -- > > Cory Quammen > > Staff R&D Engineer > > Kitware, Inc. > > > > _______________________________________________ > > 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 > > > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. From cory.quammen at kitware.com Wed Jan 24 13:01:00 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 24 Jan 2018 13:01:00 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: Updating to latest "master" (v5.4.1-1250-gaa11ae8) In-Reply-To: <7ebeb4073d9a429297b71802936c796f@ES01AMSNLNT.srn.sandia.gov> References: <7ebeb4073d9a429297b71802936c796f@ES01AMSNLNT.srn.sandia.gov> Message-ID: I believe superbuild will provide mpi4py. Let me test and let you know. On Wed, Jan 24, 2018 at 12:50 PM, Scott, W Alan wrote: > Thanks. I assume that Superbuild will work on old clusters that don't have the mpi4py installed? Or, do I need my systems folks to install this? > >> -----Original Message----- >> From: Cory Quammen [mailto:cory.quammen at kitware.com] >> Sent: Wednesday, January 24, 2018 10:48 AM >> To: Scott, W Alan >> Cc: Bauer, Andy (External Contacts) ; ParaView >> Developers >> Subject: Re: [EXTERNAL] Re: [Paraview-developers] Updating to latest >> "master" (v5.4.1-1250-gaa11ae8) >> >> Alan and Andy, >> >> Superbuild has not been updated. I'll kick off a build and see what needs to >> be done, then let you know. >> >> Thanks, >> Cory >> >> On Wed, Jan 24, 2018 at 12:29 PM, Scott, W Alan >> wrote: >> > What Andy said. I?m just starting a Superbuild pull... Should I wait? >> > >> > >> > >> > Alan >> > >> > >> > >> > From: Paraview-developers >> > [mailto:paraview-developers-bounces at paraview.org] >> > On Behalf Of Andy Bauer >> > Sent: Wednesday, January 24, 2018 8:55 AM >> > To: Quammen, Cory (External Contacts) >> > Cc: ParaView Developers >> > Subject: [EXTERNAL] Re: [Paraview-developers] Updating to latest >> "master" >> > (v5.4.1-1250-gaa11ae8) >> > >> > >> > >> > Has the superbuild been updated to optionally provide these python >> > modules when building Python? >> > >> > >> > >> > On Wed, Jan 24, 2018 at 10:51 AM, Cory Quammen >> > >> > wrote: >> > >> > In addition, please note that some Python modules are no longer >> > provided by ParaView and you may need to install them in the Python >> > environment used by ParaView. The required modules are: >> > >> > * mpi4py - if you are building with PARAVIEW_ENABLE_PYTHON and >> > PARAVIEW_USE_MPI. This is needed at CMake configuration time. >> > * autobahn, twisted, and wslink - if you have PARAVIEW_ENABLE_WEB. If >> > these are missing you will get a runtime error; you can install them >> > after ParaView has been compiled if needed. >> > >> > Thanks, >> > Cory >> > >> > >> > >> > >> > On Wed, Jan 24, 2018 at 10:38 AM, Utkarsh Ayachit >> > wrote: >> >> Folks, >> >> >> >> If you update to latest "master", please do a clean build to avoid >> >> running into issues with obsolete Python modules that were built in >> >> previous source versions. >> >> >> >> Thanks >> >> Utkarsh >> >> _______________________________________________ >> >> 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 >> > >> > >> > -- >> > Cory Quammen >> > Staff R&D Engineer >> > Kitware, Inc. >> > >> > _______________________________________________ >> > 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 >> > >> > >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From utkarsh.ayachit at kitware.com Wed Jan 24 13:55:02 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 24 Jan 2018 13:55:02 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: Updating to latest "master" (v5.4.1-1250-gaa11ae8) In-Reply-To: References: Message-ID: > Superbuild has not been updated. I'll kick off a build and see what > needs to be done, then let you know. Are you sure about that? I thought Ben had an MR updating Superbuild: https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/393/diffs From thomas_sgouros at brown.edu Wed Jan 24 15:02:16 2018 From: thomas_sgouros at brown.edu (Sgouros, Thomas) Date: Wed, 24 Jan 2018 15:02:16 -0500 Subject: [Paraview-developers] pvpython and force_offscreen_rendering on OS X Message-ID: Hello: The documentation seems ambiguous on the point, can anyone confirm for me how to get a version of pvpython that runs on OS X and supports the --force-offscreen-rendering option? My reading seems to imply that I will have to compile from the source, but I've been trying and failing to understand how to make the super-build process work. If someone can confirm for me that this is the way forward, I'd appreciate it. Also, when using the paraview-superbuild, when I try to install, I get this: CMake Error at /../paraview-superbuild/projects/apple/paraview.bundle.cmake:8 (message): Creating the Apple package without the GUI is not supported. To which superbuild option does this refer? Thank you, -Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Jan 24 15:36:09 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 24 Jan 2018 15:36:09 -0500 Subject: [Paraview-developers] pvpython and force_offscreen_rendering on OS X In-Reply-To: References: Message-ID: You can use `--force-offscreen-rendering` flag for standard ParaView builds on OsX when using pvpython/pvserver etc. It simply implies that there'll be no windows popped up for these command line executables. Note, ParaView still needs access to Cocoa to create OpenGL contexts for rendering. Utkarsh On Wed, Jan 24, 2018 at 3:02 PM, Sgouros, Thomas wrote: > Hello: > > The documentation seems ambiguous on the point, can anyone confirm for me > how to get a version of pvpython that runs on OS X and supports the > --force-offscreen-rendering option? > > My reading seems to imply that I will have to compile from the source, but > I've been trying and failing to understand how to make the super-build > process work. If someone can confirm for me that this is the way forward, > I'd appreciate it. > > Also, when using the paraview-superbuild, when I try to install, I get this: > > CMake Error at > /../paraview-superbuild/projects/apple/paraview.bundle.cmake:8 (message): > > Creating the Apple package without the GUI is not supported. > > To which superbuild option does this refer? > > Thank you, > > -Tom > > > _______________________________________________ > 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 Mark.Olesen at esi-group.com Wed Jan 24 15:38:52 2018 From: Mark.Olesen at esi-group.com (Mark Olesen) Date: Wed, 24 Jan 2018 21:38:52 +0100 Subject: [Paraview-developers] VTK xml formats with external geometry references Message-ID: 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 From thomas_sgouros at brown.edu Wed Jan 24 15:58:26 2018 From: thomas_sgouros at brown.edu (Sgouros, Thomas) Date: Wed, 24 Jan 2018 15:58:26 -0500 Subject: [Paraview-developers] pvpython and force_offscreen_rendering on OS X In-Reply-To: References: Message-ID: $ /Applications/ParaView-5.4.1.app/Contents/bin/pvpython --force-offscreen-rendering Got unknown argument: --force-offscreen-rendering What does "access to Cocoa" mean in this context? How would I go about giving it that access? All I could think of was to run the XQuartz server at the same time, but I don't see any way to tell pvpython to look there. Thank you, -Tom On Wed, Jan 24, 2018 at 3:36 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > You can use `--force-offscreen-rendering` flag for standard ParaView > builds on OsX when using pvpython/pvserver etc. It simply implies that > there'll be no windows popped up for these command line executables. > Note, ParaView still needs access to Cocoa to create OpenGL contexts > for rendering. > > Utkarsh > > On Wed, Jan 24, 2018 at 3:02 PM, Sgouros, Thomas > wrote: > > Hello: > > > > The documentation seems ambiguous on the point, can anyone confirm for me > > how to get a version of pvpython that runs on OS X and supports the > > --force-offscreen-rendering option? > > > > My reading seems to imply that I will have to compile from the source, > but > > I've been trying and failing to understand how to make the super-build > > process work. If someone can confirm for me that this is the way forward, > > I'd appreciate it. > > > > Also, when using the paraview-superbuild, when I try to install, I get > this: > > > > CMake Error at > > /../paraview-superbuild/projects/apple/paraview.bundle.cmake:8 > (message): > > > > Creating the Apple package without the GUI is not supported. > > > > To which superbuild option does this refer? > > > > Thank you, > > > > -Tom > > > > > > _______________________________________________ > > 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 Jan 24 16:02:52 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 24 Jan 2018 16:02:52 -0500 Subject: [Paraview-developers] pvpython and force_offscreen_rendering on OS X In-Reply-To: References: Message-ID: I misspoke. Not pvpython, the option is only available for pvserver, pvbatch and not pvpython. No, XQuartz is not it. If you're logged in, you have access to the Cocoa server. On Wed, Jan 24, 2018 at 3:58 PM, Sgouros, Thomas wrote: > $ /Applications/ParaView-5.4.1.app/Contents/bin/pvpython > --force-offscreen-rendering > Got unknown argument: --force-offscreen-rendering > > What does "access to Cocoa" mean in this context? How would I go about > giving it that access? All I could think of was to run the XQuartz server at > the same time, but I don't see any way to tell pvpython to look there. > > Thank you, > > -Tom > > On Wed, Jan 24, 2018 at 3:36 PM, Utkarsh Ayachit > wrote: >> >> You can use `--force-offscreen-rendering` flag for standard ParaView >> builds on OsX when using pvpython/pvserver etc. It simply implies that >> there'll be no windows popped up for these command line executables. >> Note, ParaView still needs access to Cocoa to create OpenGL contexts >> for rendering. >> >> Utkarsh >> >> On Wed, Jan 24, 2018 at 3:02 PM, Sgouros, Thomas >> wrote: >> > Hello: >> > >> > The documentation seems ambiguous on the point, can anyone confirm for >> > me >> > how to get a version of pvpython that runs on OS X and supports the >> > --force-offscreen-rendering option? >> > >> > My reading seems to imply that I will have to compile from the source, >> > but >> > I've been trying and failing to understand how to make the super-build >> > process work. If someone can confirm for me that this is the way >> > forward, >> > I'd appreciate it. >> > >> > Also, when using the paraview-superbuild, when I try to install, I get >> > this: >> > >> > CMake Error at >> > /../paraview-superbuild/projects/apple/paraview.bundle.cmake:8 >> > (message): >> > >> > Creating the Apple package without the GUI is not supported. >> > >> > To which superbuild option does this refer? >> > >> > Thank you, >> > >> > -Tom >> > >> > >> > _______________________________________________ >> > 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 thomas_sgouros at brown.edu Wed Jan 24 16:07:05 2018 From: thomas_sgouros at brown.edu (Sgouros, Thomas) Date: Wed, 24 Jan 2018 16:07:05 -0500 Subject: [Paraview-developers] pvpython and force_offscreen_rendering on OS X In-Reply-To: References: Message-ID: Thank you. I'm chasing this issue, actually. Perhaps I've misdiagnosed it? $ LightViz --paraview /Applications/ParaView-5.4.1.app --data ../mat-viz-mofTFF-90L-9.1lpm-100rpm =============================================================================== | Execute: | $ "/Applications/ParaView-5.4.1.app/Contents/bin/pvpython" | -dr | --force-offscreen-rendering | "/usr/local/lib/node_modules/light-viz/server/pvw-light-viz.py" | --content | "/usr/local/lib/node_modules/light-viz/dist" | --port | 8080 | --data | "../mat-viz-mofTFF-90L-9.1lpm-100rpm" =============================================================================== Got unknown argument: --force-offscreen-rendering On Wed, Jan 24, 2018 at 4:02 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > I misspoke. Not pvpython, the option is only available for pvserver, > pvbatch and not pvpython. > > No, XQuartz is not it. If you're logged in, you have access to the Cocoa > server. > > On Wed, Jan 24, 2018 at 3:58 PM, Sgouros, Thomas > wrote: > > $ /Applications/ParaView-5.4.1.app/Contents/bin/pvpython > > --force-offscreen-rendering > > Got unknown argument: --force-offscreen-rendering > > > > What does "access to Cocoa" mean in this context? How would I go about > > giving it that access? All I could think of was to run the XQuartz > server at > > the same time, but I don't see any way to tell pvpython to look there. > > > > Thank you, > > > > -Tom > > > > On Wed, Jan 24, 2018 at 3:36 PM, Utkarsh Ayachit > > wrote: > >> > >> You can use `--force-offscreen-rendering` flag for standard ParaView > >> builds on OsX when using pvpython/pvserver etc. It simply implies that > >> there'll be no windows popped up for these command line executables. > >> Note, ParaView still needs access to Cocoa to create OpenGL contexts > >> for rendering. > >> > >> Utkarsh > >> > >> On Wed, Jan 24, 2018 at 3:02 PM, Sgouros, Thomas > >> wrote: > >> > Hello: > >> > > >> > The documentation seems ambiguous on the point, can anyone confirm for > >> > me > >> > how to get a version of pvpython that runs on OS X and supports the > >> > --force-offscreen-rendering option? > >> > > >> > My reading seems to imply that I will have to compile from the source, > >> > but > >> > I've been trying and failing to understand how to make the super-build > >> > process work. If someone can confirm for me that this is the way > >> > forward, > >> > I'd appreciate it. > >> > > >> > Also, when using the paraview-superbuild, when I try to install, I get > >> > this: > >> > > >> > CMake Error at > >> > /../paraview-superbuild/projects/apple/paraview.bundle.cmake:8 > >> > (message): > >> > > >> > Creating the Apple package without the GUI is not supported. > >> > > >> > To which superbuild option does this refer? > >> > > >> > Thank you, > >> > > >> > -Tom > >> > > >> > > >> > _______________________________________________ > >> > 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 cory.quammen at kitware.com Wed Jan 24 16:11:29 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 24 Jan 2018 16:11:29 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: Updating to latest "master" (v5.4.1-1250-gaa11ae8) In-Reply-To: References: Message-ID: Good memory. Looks like he did. Looks like the superbuild dashboards are not updated to set ENABLE_pythonmpi4py, etc., to ON. On Wed, Jan 24, 2018 at 1:55 PM, Utkarsh Ayachit wrote: >> Superbuild has not been updated. I'll kick off a build and see what >> needs to be done, then let you know. > > > Are you sure about that? I thought Ben had an MR updating Superbuild: > https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/393/diffs -- Cory Quammen Staff R&D Engineer Kitware, Inc. From utkarsh.ayachit at kitware.com Wed Jan 24 16:16:18 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 24 Jan 2018 16:16:18 -0500 Subject: [Paraview-developers] pvpython and force_offscreen_rendering on OS X In-Reply-To: References: Message-ID: Okay, I misspoke again :). pvpython should indeed have this command line option. Maybe someone with access to a mac can see why this isn't working. I can try out on my home mac later tonight and get back to you if no one responds before then. On Wed, Jan 24, 2018 at 4:07 PM, Sgouros, Thomas wrote: > Thank you. I'm chasing this issue, actually. Perhaps I've misdiagnosed it? > > $ LightViz --paraview /Applications/ParaView-5.4.1.app --data > ../mat-viz-mofTFF-90L-9.1lpm-100rpm > > > =============================================================================== > > | Execute: > > | $ "/Applications/ParaView-5.4.1.app/Contents/bin/pvpython" > > | -dr > > | --force-offscreen-rendering > > | "/usr/local/lib/node_modules/light-viz/server/pvw-light-viz.py" > > | --content > > | "/usr/local/lib/node_modules/light-viz/dist" > > | --port > > | 8080 > > | --data > > | "../mat-viz-mofTFF-90L-9.1lpm-100rpm" > > =============================================================================== > > > Got unknown argument: --force-offscreen-rendering > > > > > > On Wed, Jan 24, 2018 at 4:02 PM, Utkarsh Ayachit > wrote: >> >> I misspoke. Not pvpython, the option is only available for pvserver, >> pvbatch and not pvpython. >> >> No, XQuartz is not it. If you're logged in, you have access to the Cocoa >> server. >> >> On Wed, Jan 24, 2018 at 3:58 PM, Sgouros, Thomas >> wrote: >> > $ /Applications/ParaView-5.4.1.app/Contents/bin/pvpython >> > --force-offscreen-rendering >> > Got unknown argument: --force-offscreen-rendering >> > >> > What does "access to Cocoa" mean in this context? How would I go about >> > giving it that access? All I could think of was to run the XQuartz >> > server at >> > the same time, but I don't see any way to tell pvpython to look there. >> > >> > Thank you, >> > >> > -Tom >> > >> > On Wed, Jan 24, 2018 at 3:36 PM, Utkarsh Ayachit >> > wrote: >> >> >> >> You can use `--force-offscreen-rendering` flag for standard ParaView >> >> builds on OsX when using pvpython/pvserver etc. It simply implies that >> >> there'll be no windows popped up for these command line executables. >> >> Note, ParaView still needs access to Cocoa to create OpenGL contexts >> >> for rendering. >> >> >> >> Utkarsh >> >> >> >> On Wed, Jan 24, 2018 at 3:02 PM, Sgouros, Thomas >> >> wrote: >> >> > Hello: >> >> > >> >> > The documentation seems ambiguous on the point, can anyone confirm >> >> > for >> >> > me >> >> > how to get a version of pvpython that runs on OS X and supports the >> >> > --force-offscreen-rendering option? >> >> > >> >> > My reading seems to imply that I will have to compile from the >> >> > source, >> >> > but >> >> > I've been trying and failing to understand how to make the >> >> > super-build >> >> > process work. If someone can confirm for me that this is the way >> >> > forward, >> >> > I'd appreciate it. >> >> > >> >> > Also, when using the paraview-superbuild, when I try to install, I >> >> > get >> >> > this: >> >> > >> >> > CMake Error at >> >> > /../paraview-superbuild/projects/apple/paraview.bundle.cmake:8 >> >> > (message): >> >> > >> >> > Creating the Apple package without the GUI is not supported. >> >> > >> >> > To which superbuild option does this refer? >> >> > >> >> > Thank you, >> >> > >> >> > -Tom >> >> > >> >> > >> >> > _______________________________________________ >> >> > 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 thomas_sgouros at brown.edu Wed Jan 24 16:23:37 2018 From: thomas_sgouros at brown.edu (Sgouros, Thomas) Date: Wed, 24 Jan 2018 16:23:37 -0500 Subject: [Paraview-developers] pvpython and force_offscreen_rendering on OS X In-Reply-To: References: Message-ID: On this page: https://www.paraview.org/ParaView/Doc/Nightly/www/cxx-doc/Offscreen.html There is this note: Currently, ParaView supports two distinct APIs that are available for headless operation: EGL and OSMesa (also called Offscreen Mesa). It must be noted that headless support is a rapidly evolving area and changes are expected in coming months. Modern H/W OpenGL implementations support EGL while S/W (or Mesa) supports OSMesa. One has to build ParaView with specific CMake flags changed to enable either of these APIs. Which headless API you choose in your build depends on which OpenGL implementation you plan to use. I thought this meant I should try to build Paraview from source. My original question had a second part about why my build wasn't working, but I'd also add that it's not clear how to find the OSMesa option through the superbuild process, either. Thank you, -Tom On Wed, Jan 24, 2018 at 4:16 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Okay, I misspoke again :). pvpython should indeed have this command > line option. Maybe someone with access to a mac can see why this isn't > working. I can try out on my home mac later tonight and get back to > you if no one responds before then. > > On Wed, Jan 24, 2018 at 4:07 PM, Sgouros, Thomas > wrote: > > Thank you. I'm chasing this issue, actually. Perhaps I've misdiagnosed > it? > > > > $ LightViz --paraview /Applications/ParaView-5.4.1.app --data > > ../mat-viz-mofTFF-90L-9.1lpm-100rpm > > > > > > ============================================================ > =================== > > > > | Execute: > > > > | $ "/Applications/ParaView-5.4.1.app/Contents/bin/pvpython" > > > > | -dr > > > > | --force-offscreen-rendering > > > > | "/usr/local/lib/node_modules/light-viz/server/pvw-light-viz.py" > > > > | --content > > > > | "/usr/local/lib/node_modules/light-viz/dist" > > > > | --port > > > > | 8080 > > > > | --data > > > > | "../mat-viz-mofTFF-90L-9.1lpm-100rpm" > > > > ============================================================ > =================== > > > > > > Got unknown argument: --force-offscreen-rendering > > > > > > > > > > > > On Wed, Jan 24, 2018 at 4:02 PM, Utkarsh Ayachit > > wrote: > >> > >> I misspoke. Not pvpython, the option is only available for pvserver, > >> pvbatch and not pvpython. > >> > >> No, XQuartz is not it. If you're logged in, you have access to the Cocoa > >> server. > >> > >> On Wed, Jan 24, 2018 at 3:58 PM, Sgouros, Thomas > >> wrote: > >> > $ /Applications/ParaView-5.4.1.app/Contents/bin/pvpython > >> > --force-offscreen-rendering > >> > Got unknown argument: --force-offscreen-rendering > >> > > >> > What does "access to Cocoa" mean in this context? How would I go about > >> > giving it that access? All I could think of was to run the XQuartz > >> > server at > >> > the same time, but I don't see any way to tell pvpython to look there. > >> > > >> > Thank you, > >> > > >> > -Tom > >> > > >> > On Wed, Jan 24, 2018 at 3:36 PM, Utkarsh Ayachit > >> > wrote: > >> >> > >> >> You can use `--force-offscreen-rendering` flag for standard ParaView > >> >> builds on OsX when using pvpython/pvserver etc. It simply implies > that > >> >> there'll be no windows popped up for these command line executables. > >> >> Note, ParaView still needs access to Cocoa to create OpenGL contexts > >> >> for rendering. > >> >> > >> >> Utkarsh > >> >> > >> >> On Wed, Jan 24, 2018 at 3:02 PM, Sgouros, Thomas > >> >> wrote: > >> >> > Hello: > >> >> > > >> >> > The documentation seems ambiguous on the point, can anyone confirm > >> >> > for > >> >> > me > >> >> > how to get a version of pvpython that runs on OS X and supports the > >> >> > --force-offscreen-rendering option? > >> >> > > >> >> > My reading seems to imply that I will have to compile from the > >> >> > source, > >> >> > but > >> >> > I've been trying and failing to understand how to make the > >> >> > super-build > >> >> > process work. If someone can confirm for me that this is the way > >> >> > forward, > >> >> > I'd appreciate it. > >> >> > > >> >> > Also, when using the paraview-superbuild, when I try to install, I > >> >> > get > >> >> > this: > >> >> > > >> >> > CMake Error at > >> >> > /../paraview-superbuild/projects/apple/paraview.bundle.cmake:8 > >> >> > (message): > >> >> > > >> >> > Creating the Apple package without the GUI is not supported. > >> >> > > >> >> > To which superbuild option does this refer? > >> >> > > >> >> > Thank you, > >> >> > > >> >> > -Tom > >> >> > > >> >> > > >> >> > _______________________________________________ > >> >> > 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 Jan 24 16:47:01 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 24 Jan 2018 16:47:01 -0500 Subject: [Paraview-developers] pvpython and force_offscreen_rendering on OS X In-Reply-To: References: Message-ID: Tom, The page also says: "In this page, we limit ourselves to a Linux-based system. On Windows and macOS, offscreen support is available, but true headless operation is currently not widely used and hence left out of this discussion." Thus, the page is mostly for Linux where people have options of using X or not. Utkarsh On Wed, Jan 24, 2018 at 4:23 PM, Sgouros, Thomas wrote: > On this page: > https://www.paraview.org/ParaView/Doc/Nightly/www/cxx-doc/Offscreen.html > > There is this note: > > Currently, ParaView supports two distinct APIs that are available for > headless operation: EGL and OSMesa (also called Offscreen Mesa). It must be > noted that headless support is a rapidly evolving area and changes are > expected in coming months. Modern H/W OpenGL implementations support EGL > while S/W (or Mesa) supports OSMesa. One has to build ParaView with specific > CMake flags changed to enable either of these APIs. Which headless API you > choose in your build depends on which OpenGL implementation you plan to use. > > I thought this meant I should try to build Paraview from source. My original > question had a second part about why my build wasn't working, but I'd also > add that it's not clear how to find the OSMesa option through the superbuild > process, either. > > Thank you, > > -Tom > > > On Wed, Jan 24, 2018 at 4:16 PM, Utkarsh Ayachit > wrote: >> >> Okay, I misspoke again :). pvpython should indeed have this command >> line option. Maybe someone with access to a mac can see why this isn't >> working. I can try out on my home mac later tonight and get back to >> you if no one responds before then. >> >> On Wed, Jan 24, 2018 at 4:07 PM, Sgouros, Thomas >> wrote: >> > Thank you. I'm chasing this issue, actually. Perhaps I've misdiagnosed >> > it? >> > >> > $ LightViz --paraview /Applications/ParaView-5.4.1.app --data >> > ../mat-viz-mofTFF-90L-9.1lpm-100rpm >> > >> > >> > >> > =============================================================================== >> > >> > | Execute: >> > >> > | $ "/Applications/ParaView-5.4.1.app/Contents/bin/pvpython" >> > >> > | -dr >> > >> > | --force-offscreen-rendering >> > >> > | "/usr/local/lib/node_modules/light-viz/server/pvw-light-viz.py" >> > >> > | --content >> > >> > | "/usr/local/lib/node_modules/light-viz/dist" >> > >> > | --port >> > >> > | 8080 >> > >> > | --data >> > >> > | "../mat-viz-mofTFF-90L-9.1lpm-100rpm" >> > >> > >> > =============================================================================== >> > >> > >> > Got unknown argument: --force-offscreen-rendering >> > >> > >> > >> > >> > >> > On Wed, Jan 24, 2018 at 4:02 PM, Utkarsh Ayachit >> > wrote: >> >> >> >> I misspoke. Not pvpython, the option is only available for pvserver, >> >> pvbatch and not pvpython. >> >> >> >> No, XQuartz is not it. If you're logged in, you have access to the >> >> Cocoa >> >> server. >> >> >> >> On Wed, Jan 24, 2018 at 3:58 PM, Sgouros, Thomas >> >> wrote: >> >> > $ /Applications/ParaView-5.4.1.app/Contents/bin/pvpython >> >> > --force-offscreen-rendering >> >> > Got unknown argument: --force-offscreen-rendering >> >> > >> >> > What does "access to Cocoa" mean in this context? How would I go >> >> > about >> >> > giving it that access? All I could think of was to run the XQuartz >> >> > server at >> >> > the same time, but I don't see any way to tell pvpython to look >> >> > there. >> >> > >> >> > Thank you, >> >> > >> >> > -Tom >> >> > >> >> > On Wed, Jan 24, 2018 at 3:36 PM, Utkarsh Ayachit >> >> > wrote: >> >> >> >> >> >> You can use `--force-offscreen-rendering` flag for standard ParaView >> >> >> builds on OsX when using pvpython/pvserver etc. It simply implies >> >> >> that >> >> >> there'll be no windows popped up for these command line executables. >> >> >> Note, ParaView still needs access to Cocoa to create OpenGL contexts >> >> >> for rendering. >> >> >> >> >> >> Utkarsh >> >> >> >> >> >> On Wed, Jan 24, 2018 at 3:02 PM, Sgouros, Thomas >> >> >> wrote: >> >> >> > Hello: >> >> >> > >> >> >> > The documentation seems ambiguous on the point, can anyone confirm >> >> >> > for >> >> >> > me >> >> >> > how to get a version of pvpython that runs on OS X and supports >> >> >> > the >> >> >> > --force-offscreen-rendering option? >> >> >> > >> >> >> > My reading seems to imply that I will have to compile from the >> >> >> > source, >> >> >> > but >> >> >> > I've been trying and failing to understand how to make the >> >> >> > super-build >> >> >> > process work. If someone can confirm for me that this is the way >> >> >> > forward, >> >> >> > I'd appreciate it. >> >> >> > >> >> >> > Also, when using the paraview-superbuild, when I try to install, I >> >> >> > get >> >> >> > this: >> >> >> > >> >> >> > CMake Error at >> >> >> > /../paraview-superbuild/projects/apple/paraview.bundle.cmake:8 >> >> >> > (message): >> >> >> > >> >> >> > Creating the Apple package without the GUI is not supported. >> >> >> > >> >> >> > To which superbuild option does this refer? >> >> >> > >> >> >> > Thank you, >> >> >> > >> >> >> > -Tom >> >> >> > >> >> >> > >> >> >> > _______________________________________________ >> >> >> > 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 thomas_sgouros at brown.edu Wed Jan 24 21:53:44 2018 From: thomas_sgouros at brown.edu (Sgouros, Thomas) Date: Wed, 24 Jan 2018 21:53:44 -0500 Subject: [Paraview-developers] pvpython and force_offscreen_rendering on OS X In-Reply-To: References: Message-ID: Sure, I didn't mean to seem accusatory. I have to develop a paraviewweb application and want to see if I could set up a prototype paraview server on my (mac) laptop for the convenience of developing. If I can't, I can't, but the text seemed to imply there was a possibility so I soldiered on until I got stuck. Thank you, -Tom On Wed, Jan 24, 2018 at 4:47 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Tom, > > The page also says: > > "In this page, we limit ourselves to a Linux-based system. On Windows > and macOS, offscreen support is available, but true headless operation > is currently not widely used and hence left out of this discussion." > > Thus, the page is mostly for Linux where people have options of using X or > not. > > Utkarsh > > > On Wed, Jan 24, 2018 at 4:23 PM, Sgouros, Thomas > wrote: > > On this page: > > https://www.paraview.org/ParaView/Doc/Nightly/www/cxx-doc/Offscreen.html > > > > There is this note: > > > > Currently, ParaView supports two distinct APIs that are available for > > headless operation: EGL and OSMesa (also called Offscreen Mesa). It must > be > > noted that headless support is a rapidly evolving area and changes are > > expected in coming months. Modern H/W OpenGL implementations support EGL > > while S/W (or Mesa) supports OSMesa. One has to build ParaView with > specific > > CMake flags changed to enable either of these APIs. Which headless API > you > > choose in your build depends on which OpenGL implementation you plan to > use. > > > > I thought this meant I should try to build Paraview from source. My > original > > question had a second part about why my build wasn't working, but I'd > also > > add that it's not clear how to find the OSMesa option through the > superbuild > > process, either. > > > > Thank you, > > > > -Tom > > > > > > On Wed, Jan 24, 2018 at 4:16 PM, Utkarsh Ayachit > > wrote: > >> > >> Okay, I misspoke again :). pvpython should indeed have this command > >> line option. Maybe someone with access to a mac can see why this isn't > >> working. I can try out on my home mac later tonight and get back to > >> you if no one responds before then. > >> > >> On Wed, Jan 24, 2018 at 4:07 PM, Sgouros, Thomas > >> wrote: > >> > Thank you. I'm chasing this issue, actually. Perhaps I've misdiagnosed > >> > it? > >> > > >> > $ LightViz --paraview /Applications/ParaView-5.4.1.app --data > >> > ../mat-viz-mofTFF-90L-9.1lpm-100rpm > >> > > >> > > >> > > >> > ============================================================ > =================== > >> > > >> > | Execute: > >> > > >> > | $ "/Applications/ParaView-5.4.1.app/Contents/bin/pvpython" > >> > > >> > | -dr > >> > > >> > | --force-offscreen-rendering > >> > > >> > | "/usr/local/lib/node_modules/light-viz/server/pvw-light-viz.py" > >> > > >> > | --content > >> > > >> > | "/usr/local/lib/node_modules/light-viz/dist" > >> > > >> > | --port > >> > > >> > | 8080 > >> > > >> > | --data > >> > > >> > | "../mat-viz-mofTFF-90L-9.1lpm-100rpm" > >> > > >> > > >> > ============================================================ > =================== > >> > > >> > > >> > Got unknown argument: --force-offscreen-rendering > >> > > >> > > >> > > >> > > >> > > >> > On Wed, Jan 24, 2018 at 4:02 PM, Utkarsh Ayachit > >> > wrote: > >> >> > >> >> I misspoke. Not pvpython, the option is only available for pvserver, > >> >> pvbatch and not pvpython. > >> >> > >> >> No, XQuartz is not it. If you're logged in, you have access to the > >> >> Cocoa > >> >> server. > >> >> > >> >> On Wed, Jan 24, 2018 at 3:58 PM, Sgouros, Thomas > >> >> wrote: > >> >> > $ /Applications/ParaView-5.4.1.app/Contents/bin/pvpython > >> >> > --force-offscreen-rendering > >> >> > Got unknown argument: --force-offscreen-rendering > >> >> > > >> >> > What does "access to Cocoa" mean in this context? How would I go > >> >> > about > >> >> > giving it that access? All I could think of was to run the XQuartz > >> >> > server at > >> >> > the same time, but I don't see any way to tell pvpython to look > >> >> > there. > >> >> > > >> >> > Thank you, > >> >> > > >> >> > -Tom > >> >> > > >> >> > On Wed, Jan 24, 2018 at 3:36 PM, Utkarsh Ayachit > >> >> > wrote: > >> >> >> > >> >> >> You can use `--force-offscreen-rendering` flag for standard > ParaView > >> >> >> builds on OsX when using pvpython/pvserver etc. It simply implies > >> >> >> that > >> >> >> there'll be no windows popped up for these command line > executables. > >> >> >> Note, ParaView still needs access to Cocoa to create OpenGL > contexts > >> >> >> for rendering. > >> >> >> > >> >> >> Utkarsh > >> >> >> > >> >> >> On Wed, Jan 24, 2018 at 3:02 PM, Sgouros, Thomas > >> >> >> wrote: > >> >> >> > Hello: > >> >> >> > > >> >> >> > The documentation seems ambiguous on the point, can anyone > confirm > >> >> >> > for > >> >> >> > me > >> >> >> > how to get a version of pvpython that runs on OS X and supports > >> >> >> > the > >> >> >> > --force-offscreen-rendering option? > >> >> >> > > >> >> >> > My reading seems to imply that I will have to compile from the > >> >> >> > source, > >> >> >> > but > >> >> >> > I've been trying and failing to understand how to make the > >> >> >> > super-build > >> >> >> > process work. If someone can confirm for me that this is the way > >> >> >> > forward, > >> >> >> > I'd appreciate it. > >> >> >> > > >> >> >> > Also, when using the paraview-superbuild, when I try to > install, I > >> >> >> > get > >> >> >> > this: > >> >> >> > > >> >> >> > CMake Error at > >> >> >> > /../paraview-superbuild/projects/apple/paraview.bundle.cmake:8 > >> >> >> > (message): > >> >> >> > > >> >> >> > Creating the Apple package without the GUI is not supported. > >> >> >> > > >> >> >> > To which superbuild option does this refer? > >> >> >> > > >> >> >> > Thank you, > >> >> >> > > >> >> >> > -Tom > >> >> >> > > >> >> >> > > >> >> >> > _______________________________________________ > >> >> >> > 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 sebastien.jourdain at kitware.com Wed Jan 24 22:50:13 2018 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 24 Jan 2018 20:50:13 -0700 Subject: [Paraview-developers] pvpython and force_offscreen_rendering on OS X In-Reply-To: References: Message-ID: <8534DEA2-0A0B-447B-8A5B-485AF2491B1D@kitware.com> Tom, I?m the main developer behind ParaViewWeb and I only develop on Mac. So you should be fine. :-) I?ll read the full thread now that I know you are focusing on PVW. Seb > On Jan 24, 2018, at 19:53, Sgouros, Thomas wrote: > > Sure, I didn't mean to seem accusatory. I have to develop a paraviewweb application and want to see if I could set up a prototype paraview server on my (mac) laptop for the convenience of developing. If I can't, I can't, but the text seemed to imply there was a possibility so I soldiered on until I got stuck. > > Thank you, > > -Tom > >> On Wed, Jan 24, 2018 at 4:47 PM, Utkarsh Ayachit wrote: >> Tom, >> >> The page also says: >> >> "In this page, we limit ourselves to a Linux-based system. On Windows >> and macOS, offscreen support is available, but true headless operation >> is currently not widely used and hence left out of this discussion." >> >> Thus, the page is mostly for Linux where people have options of using X or not. >> >> Utkarsh >> >> >> On Wed, Jan 24, 2018 at 4:23 PM, Sgouros, Thomas >> wrote: >> > On this page: >> > https://www.paraview.org/ParaView/Doc/Nightly/www/cxx-doc/Offscreen.html >> > >> > There is this note: >> > >> > Currently, ParaView supports two distinct APIs that are available for >> > headless operation: EGL and OSMesa (also called Offscreen Mesa). It must be >> > noted that headless support is a rapidly evolving area and changes are >> > expected in coming months. Modern H/W OpenGL implementations support EGL >> > while S/W (or Mesa) supports OSMesa. One has to build ParaView with specific >> > CMake flags changed to enable either of these APIs. Which headless API you >> > choose in your build depends on which OpenGL implementation you plan to use. >> > >> > I thought this meant I should try to build Paraview from source. My original >> > question had a second part about why my build wasn't working, but I'd also >> > add that it's not clear how to find the OSMesa option through the superbuild >> > process, either. >> > >> > Thank you, >> > >> > -Tom >> > >> > >> > On Wed, Jan 24, 2018 at 4:16 PM, Utkarsh Ayachit >> > wrote: >> >> >> >> Okay, I misspoke again :). pvpython should indeed have this command >> >> line option. Maybe someone with access to a mac can see why this isn't >> >> working. I can try out on my home mac later tonight and get back to >> >> you if no one responds before then. >> >> >> >> On Wed, Jan 24, 2018 at 4:07 PM, Sgouros, Thomas >> >> wrote: >> >> > Thank you. I'm chasing this issue, actually. Perhaps I've misdiagnosed >> >> > it? >> >> > >> >> > $ LightViz --paraview /Applications/ParaView-5.4.1.app --data >> >> > ../mat-viz-mofTFF-90L-9.1lpm-100rpm >> >> > >> >> > >> >> > >> >> > =============================================================================== >> >> > >> >> > | Execute: >> >> > >> >> > | $ "/Applications/ParaView-5.4.1.app/Contents/bin/pvpython" >> >> > >> >> > | -dr >> >> > >> >> > | --force-offscreen-rendering >> >> > >> >> > | "/usr/local/lib/node_modules/light-viz/server/pvw-light-viz.py" >> >> > >> >> > | --content >> >> > >> >> > | "/usr/local/lib/node_modules/light-viz/dist" >> >> > >> >> > | --port >> >> > >> >> > | 8080 >> >> > >> >> > | --data >> >> > >> >> > | "../mat-viz-mofTFF-90L-9.1lpm-100rpm" >> >> > >> >> > >> >> > =============================================================================== >> >> > >> >> > >> >> > Got unknown argument: --force-offscreen-rendering >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > On Wed, Jan 24, 2018 at 4:02 PM, Utkarsh Ayachit >> >> > wrote: >> >> >> >> >> >> I misspoke. Not pvpython, the option is only available for pvserver, >> >> >> pvbatch and not pvpython. >> >> >> >> >> >> No, XQuartz is not it. If you're logged in, you have access to the >> >> >> Cocoa >> >> >> server. >> >> >> >> >> >> On Wed, Jan 24, 2018 at 3:58 PM, Sgouros, Thomas >> >> >> wrote: >> >> >> > $ /Applications/ParaView-5.4.1.app/Contents/bin/pvpython >> >> >> > --force-offscreen-rendering >> >> >> > Got unknown argument: --force-offscreen-rendering >> >> >> > >> >> >> > What does "access to Cocoa" mean in this context? How would I go >> >> >> > about >> >> >> > giving it that access? All I could think of was to run the XQuartz >> >> >> > server at >> >> >> > the same time, but I don't see any way to tell pvpython to look >> >> >> > there. >> >> >> > >> >> >> > Thank you, >> >> >> > >> >> >> > -Tom >> >> >> > >> >> >> > On Wed, Jan 24, 2018 at 3:36 PM, Utkarsh Ayachit >> >> >> > wrote: >> >> >> >> >> >> >> >> You can use `--force-offscreen-rendering` flag for standard ParaView >> >> >> >> builds on OsX when using pvpython/pvserver etc. It simply implies >> >> >> >> that >> >> >> >> there'll be no windows popped up for these command line executables. >> >> >> >> Note, ParaView still needs access to Cocoa to create OpenGL contexts >> >> >> >> for rendering. >> >> >> >> >> >> >> >> Utkarsh >> >> >> >> >> >> >> >> On Wed, Jan 24, 2018 at 3:02 PM, Sgouros, Thomas >> >> >> >> wrote: >> >> >> >> > Hello: >> >> >> >> > >> >> >> >> > The documentation seems ambiguous on the point, can anyone confirm >> >> >> >> > for >> >> >> >> > me >> >> >> >> > how to get a version of pvpython that runs on OS X and supports >> >> >> >> > the >> >> >> >> > --force-offscreen-rendering option? >> >> >> >> > >> >> >> >> > My reading seems to imply that I will have to compile from the >> >> >> >> > source, >> >> >> >> > but >> >> >> >> > I've been trying and failing to understand how to make the >> >> >> >> > super-build >> >> >> >> > process work. If someone can confirm for me that this is the way >> >> >> >> > forward, >> >> >> >> > I'd appreciate it. >> >> >> >> > >> >> >> >> > Also, when using the paraview-superbuild, when I try to install, I >> >> >> >> > get >> >> >> >> > this: >> >> >> >> > >> >> >> >> > CMake Error at >> >> >> >> > /../paraview-superbuild/projects/apple/paraview.bundle.cmake:8 >> >> >> >> > (message): >> >> >> >> > >> >> >> >> > Creating the Apple package without the GUI is not supported. >> >> >> >> > >> >> >> >> > To which superbuild option does this refer? >> >> >> >> > >> >> >> >> > Thank you, >> >> >> >> > >> >> >> >> > -Tom >> >> >> >> > >> >> >> >> > >> >> >> >> > _______________________________________________ >> >> >> >> > 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 Jan 24 22:52:05 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 24 Jan 2018 22:52:05 -0500 Subject: [Paraview-developers] pvpython and force_offscreen_rendering on OS X In-Reply-To: References: Message-ID: On Wed, Jan 24, 2018 at 9:53 PM, Sgouros, Thomas wrote: > Sure, I didn't mean to seem accusatory. Oh no, I didn't take it as accusatory at all. I was just making sure you saw that as well. I often miss things on long pages as such. > I have to develop a paraviewweb > application and want to see if I could set up a prototype paraview server on > my (mac) laptop for the convenience of developing. If I can't, I can't, but > the text seemed to imply there was a possibility so I soldiered on until I > got stuck. So here's the deal: I had forgotten that `--force-offscreen-rendering` is not an option available in 5.4.1, it'll be available in upcoming release, or with a nighly build. I'll let Seb follow up on how to update the command line if you want to try with 5.4.1 release. Utkarsh From sebastien.jourdain at kitware.com Wed Jan 24 22:57:39 2018 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 24 Jan 2018 20:57:39 -0700 Subject: [Paraview-developers] pvpython and force_offscreen_rendering on OS X In-Reply-To: References: Message-ID: <0C61F573-3CD4-4110-8F51-0FDA8A56E3CF@kitware.com> I saw you were trying to use light-viz which has some code to force the offscreen rendering. But with the latest version of Paraview the way offscreen rendering works has changed and I?m not sure (can?t remember), if we updated light-viz to properly enable offscreen with the latest paraview. It is easy to fix, but I guess, I?ll have to look and maybe push a new version. Otherwise you should be able to use the binary distribution of ParaView without building it. Seb > On Jan 24, 2018, at 19:53, Sgouros, Thomas wrote: > > Sure, I didn't mean to seem accusatory. I have to develop a paraviewweb application and want to see if I could set up a prototype paraview server on my (mac) laptop for the convenience of developing. If I can't, I can't, but the text seemed to imply there was a possibility so I soldiered on until I got stuck. > > Thank you, > > -Tom > >> On Wed, Jan 24, 2018 at 4:47 PM, Utkarsh Ayachit wrote: >> Tom, >> >> The page also says: >> >> "In this page, we limit ourselves to a Linux-based system. On Windows >> and macOS, offscreen support is available, but true headless operation >> is currently not widely used and hence left out of this discussion." >> >> Thus, the page is mostly for Linux where people have options of using X or not. >> >> Utkarsh >> >> >> On Wed, Jan 24, 2018 at 4:23 PM, Sgouros, Thomas >> wrote: >> > On this page: >> > https://www.paraview.org/ParaView/Doc/Nightly/www/cxx-doc/Offscreen.html >> > >> > There is this note: >> > >> > Currently, ParaView supports two distinct APIs that are available for >> > headless operation: EGL and OSMesa (also called Offscreen Mesa). It must be >> > noted that headless support is a rapidly evolving area and changes are >> > expected in coming months. Modern H/W OpenGL implementations support EGL >> > while S/W (or Mesa) supports OSMesa. One has to build ParaView with specific >> > CMake flags changed to enable either of these APIs. Which headless API you >> > choose in your build depends on which OpenGL implementation you plan to use. >> > >> > I thought this meant I should try to build Paraview from source. My original >> > question had a second part about why my build wasn't working, but I'd also >> > add that it's not clear how to find the OSMesa option through the superbuild >> > process, either. >> > >> > Thank you, >> > >> > -Tom >> > >> > >> > On Wed, Jan 24, 2018 at 4:16 PM, Utkarsh Ayachit >> > wrote: >> >> >> >> Okay, I misspoke again :). pvpython should indeed have this command >> >> line option. Maybe someone with access to a mac can see why this isn't >> >> working. I can try out on my home mac later tonight and get back to >> >> you if no one responds before then. >> >> >> >> On Wed, Jan 24, 2018 at 4:07 PM, Sgouros, Thomas >> >> wrote: >> >> > Thank you. I'm chasing this issue, actually. Perhaps I've misdiagnosed >> >> > it? >> >> > >> >> > $ LightViz --paraview /Applications/ParaView-5.4.1.app --data >> >> > ../mat-viz-mofTFF-90L-9.1lpm-100rpm >> >> > >> >> > >> >> > >> >> > =============================================================================== >> >> > >> >> > | Execute: >> >> > >> >> > | $ "/Applications/ParaView-5.4.1.app/Contents/bin/pvpython" >> >> > >> >> > | -dr >> >> > >> >> > | --force-offscreen-rendering >> >> > >> >> > | "/usr/local/lib/node_modules/light-viz/server/pvw-light-viz.py" >> >> > >> >> > | --content >> >> > >> >> > | "/usr/local/lib/node_modules/light-viz/dist" >> >> > >> >> > | --port >> >> > >> >> > | 8080 >> >> > >> >> > | --data >> >> > >> >> > | "../mat-viz-mofTFF-90L-9.1lpm-100rpm" >> >> > >> >> > >> >> > =============================================================================== >> >> > >> >> > >> >> > Got unknown argument: --force-offscreen-rendering >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > On Wed, Jan 24, 2018 at 4:02 PM, Utkarsh Ayachit >> >> > wrote: >> >> >> >> >> >> I misspoke. Not pvpython, the option is only available for pvserver, >> >> >> pvbatch and not pvpython. >> >> >> >> >> >> No, XQuartz is not it. If you're logged in, you have access to the >> >> >> Cocoa >> >> >> server. >> >> >> >> >> >> On Wed, Jan 24, 2018 at 3:58 PM, Sgouros, Thomas >> >> >> wrote: >> >> >> > $ /Applications/ParaView-5.4.1.app/Contents/bin/pvpython >> >> >> > --force-offscreen-rendering >> >> >> > Got unknown argument: --force-offscreen-rendering >> >> >> > >> >> >> > What does "access to Cocoa" mean in this context? How would I go >> >> >> > about >> >> >> > giving it that access? All I could think of was to run the XQuartz >> >> >> > server at >> >> >> > the same time, but I don't see any way to tell pvpython to look >> >> >> > there. >> >> >> > >> >> >> > Thank you, >> >> >> > >> >> >> > -Tom >> >> >> > >> >> >> > On Wed, Jan 24, 2018 at 3:36 PM, Utkarsh Ayachit >> >> >> > wrote: >> >> >> >> >> >> >> >> You can use `--force-offscreen-rendering` flag for standard ParaView >> >> >> >> builds on OsX when using pvpython/pvserver etc. It simply implies >> >> >> >> that >> >> >> >> there'll be no windows popped up for these command line executables. >> >> >> >> Note, ParaView still needs access to Cocoa to create OpenGL contexts >> >> >> >> for rendering. >> >> >> >> >> >> >> >> Utkarsh >> >> >> >> >> >> >> >> On Wed, Jan 24, 2018 at 3:02 PM, Sgouros, Thomas >> >> >> >> wrote: >> >> >> >> > Hello: >> >> >> >> > >> >> >> >> > The documentation seems ambiguous on the point, can anyone confirm >> >> >> >> > for >> >> >> >> > me >> >> >> >> > how to get a version of pvpython that runs on OS X and supports >> >> >> >> > the >> >> >> >> > --force-offscreen-rendering option? >> >> >> >> > >> >> >> >> > My reading seems to imply that I will have to compile from the >> >> >> >> > source, >> >> >> >> > but >> >> >> >> > I've been trying and failing to understand how to make the >> >> >> >> > super-build >> >> >> >> > process work. If someone can confirm for me that this is the way >> >> >> >> > forward, >> >> >> >> > I'd appreciate it. >> >> >> >> > >> >> >> >> > Also, when using the paraview-superbuild, when I try to install, I >> >> >> >> > get >> >> >> >> > this: >> >> >> >> > >> >> >> >> > CMake Error at >> >> >> >> > /../paraview-superbuild/projects/apple/paraview.bundle.cmake:8 >> >> >> >> > (message): >> >> >> >> > >> >> >> >> > Creating the Apple package without the GUI is not supported. >> >> >> >> > >> >> >> >> > To which superbuild option does this refer? >> >> >> >> > >> >> >> >> > Thank you, >> >> >> >> > >> >> >> >> > -Tom >> >> >> >> > >> >> >> >> > >> >> >> >> > _______________________________________________ >> >> >> >> > 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 thomas_sgouros at brown.edu Thu Jan 25 08:40:50 2018 From: thomas_sgouros at brown.edu (Sgouros, Thomas) Date: Thu, 25 Jan 2018 08:40:50 -0500 Subject: [Paraview-developers] pvpython and force_offscreen_rendering on OS X In-Reply-To: <0C61F573-3CD4-4110-8F51-0FDA8A56E3CF@kitware.com> References: <0C61F573-3CD4-4110-8F51-0FDA8A56E3CF@kitware.com> Message-ID: Thank you, it would be lovely if you could check on that. From what I could read, the application I need to develop is probably only close to light-viz, but I figured that inspecting it and the infrastructure it sits on would be a good start. Please let me know how to get at a working version once you check it out. Incidentally, my goal is to create a web application with only a handful of visualization options for a fairly specific class of data. Light-viz is probably overkill, even if its description seemed fairly simple. If there's a better example I could start with for working with paraviewweb, I'd love to know what it is. Thank you! -Tom On Wed, Jan 24, 2018 at 10:57 PM, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > I saw you were trying to use light-viz which has some code to force the > offscreen rendering. But with the latest version of Paraview the way > offscreen rendering works has changed and I?m not sure (can?t remember), if > we updated light-viz to properly enable offscreen with the latest paraview. > It is easy to fix, but I guess, I?ll have to look and maybe push a new > version. > > Otherwise you should be able to use the binary distribution of ParaView > without building it. > > Seb > > On Jan 24, 2018, at 19:53, Sgouros, Thomas > wrote: > > Sure, I didn't mean to seem accusatory. I have to develop a paraviewweb > application and want to see if I could set up a prototype paraview server > on my (mac) laptop for the convenience of developing. If I can't, I can't, > but the text seemed to imply there was a possibility so I soldiered on > until I got stuck. > > Thank you, > > -Tom > > On Wed, Jan 24, 2018 at 4:47 PM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> Tom, >> >> The page also says: >> >> "In this page, we limit ourselves to a Linux-based system. On Windows >> and macOS, offscreen support is available, but true headless operation >> is currently not widely used and hence left out of this discussion." >> >> Thus, the page is mostly for Linux where people have options of using X >> or not. >> >> Utkarsh >> >> >> On Wed, Jan 24, 2018 at 4:23 PM, Sgouros, Thomas >> wrote: >> > On this page: >> > https://www.paraview.org/ParaView/Doc/Nightly/www/cxx-doc/ >> Offscreen.html >> > >> > There is this note: >> > >> > Currently, ParaView supports two distinct APIs that are available for >> > headless operation: EGL and OSMesa (also called Offscreen Mesa). It >> must be >> > noted that headless support is a rapidly evolving area and changes are >> > expected in coming months. Modern H/W OpenGL implementations support EGL >> > while S/W (or Mesa) supports OSMesa. One has to build ParaView with >> specific >> > CMake flags changed to enable either of these APIs. Which headless API >> you >> > choose in your build depends on which OpenGL implementation you plan to >> use. >> > >> > I thought this meant I should try to build Paraview from source. My >> original >> > question had a second part about why my build wasn't working, but I'd >> also >> > add that it's not clear how to find the OSMesa option through the >> superbuild >> > process, either. >> > >> > Thank you, >> > >> > -Tom >> > >> > >> > On Wed, Jan 24, 2018 at 4:16 PM, Utkarsh Ayachit >> > wrote: >> >> >> >> Okay, I misspoke again :). pvpython should indeed have this command >> >> line option. Maybe someone with access to a mac can see why this isn't >> >> working. I can try out on my home mac later tonight and get back to >> >> you if no one responds before then. >> >> >> >> On Wed, Jan 24, 2018 at 4:07 PM, Sgouros, Thomas >> >> wrote: >> >> > Thank you. I'm chasing this issue, actually. Perhaps I've >> misdiagnosed >> >> > it? >> >> > >> >> > $ LightViz --paraview /Applications/ParaView-5.4.1.app --data >> >> > ../mat-viz-mofTFF-90L-9.1lpm-100rpm >> >> > >> >> > >> >> > >> >> > ============================================================ >> =================== >> >> > >> >> > | Execute: >> >> > >> >> > | $ "/Applications/ParaView-5.4.1.app/Contents/bin/pvpython" >> >> > >> >> > | -dr >> >> > >> >> > | --force-offscreen-rendering >> >> > >> >> > | "/usr/local/lib/node_modules/light-viz/server/pvw-light-viz.py" >> >> > >> >> > | --content >> >> > >> >> > | "/usr/local/lib/node_modules/light-viz/dist" >> >> > >> >> > | --port >> >> > >> >> > | 8080 >> >> > >> >> > | --data >> >> > >> >> > | "../mat-viz-mofTFF-90L-9.1lpm-100rpm" >> >> > >> >> > >> >> > ============================================================ >> =================== >> >> > >> >> > >> >> > Got unknown argument: --force-offscreen-rendering >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > On Wed, Jan 24, 2018 at 4:02 PM, Utkarsh Ayachit >> >> > wrote: >> >> >> >> >> >> I misspoke. Not pvpython, the option is only available for pvserver, >> >> >> pvbatch and not pvpython. >> >> >> >> >> >> No, XQuartz is not it. If you're logged in, you have access to the >> >> >> Cocoa >> >> >> server. >> >> >> >> >> >> On Wed, Jan 24, 2018 at 3:58 PM, Sgouros, Thomas >> >> >> wrote: >> >> >> > $ /Applications/ParaView-5.4.1.app/Contents/bin/pvpython >> >> >> > --force-offscreen-rendering >> >> >> > Got unknown argument: --force-offscreen-rendering >> >> >> > >> >> >> > What does "access to Cocoa" mean in this context? How would I go >> >> >> > about >> >> >> > giving it that access? All I could think of was to run the XQuartz >> >> >> > server at >> >> >> > the same time, but I don't see any way to tell pvpython to look >> >> >> > there. >> >> >> > >> >> >> > Thank you, >> >> >> > >> >> >> > -Tom >> >> >> > >> >> >> > On Wed, Jan 24, 2018 at 3:36 PM, Utkarsh Ayachit >> >> >> > wrote: >> >> >> >> >> >> >> >> You can use `--force-offscreen-rendering` flag for standard >> ParaView >> >> >> >> builds on OsX when using pvpython/pvserver etc. It simply implies >> >> >> >> that >> >> >> >> there'll be no windows popped up for these command line >> executables. >> >> >> >> Note, ParaView still needs access to Cocoa to create OpenGL >> contexts >> >> >> >> for rendering. >> >> >> >> >> >> >> >> Utkarsh >> >> >> >> >> >> >> >> On Wed, Jan 24, 2018 at 3:02 PM, Sgouros, Thomas >> >> >> >> wrote: >> >> >> >> > Hello: >> >> >> >> > >> >> >> >> > The documentation seems ambiguous on the point, can anyone >> confirm >> >> >> >> > for >> >> >> >> > me >> >> >> >> > how to get a version of pvpython that runs on OS X and supports >> >> >> >> > the >> >> >> >> > --force-offscreen-rendering option? >> >> >> >> > >> >> >> >> > My reading seems to imply that I will have to compile from the >> >> >> >> > source, >> >> >> >> > but >> >> >> >> > I've been trying and failing to understand how to make the >> >> >> >> > super-build >> >> >> >> > process work. If someone can confirm for me that this is the >> way >> >> >> >> > forward, >> >> >> >> > I'd appreciate it. >> >> >> >> > >> >> >> >> > Also, when using the paraview-superbuild, when I try to >> install, I >> >> >> >> > get >> >> >> >> > this: >> >> >> >> > >> >> >> >> > CMake Error at >> >> >> >> > /../paraview-superbuild/projects/apple/paraview.bundle.cmake:8 >> >> >> >> > (message): >> >> >> >> > >> >> >> >> > Creating the Apple package without the GUI is not supported. >> >> >> >> > >> >> >> >> > To which superbuild option does this refer? >> >> >> >> > >> >> >> >> > Thank you, >> >> >> >> > >> >> >> >> > -Tom >> >> >> >> > >> >> >> >> > >> >> >> >> > _______________________________________________ >> >> >> >> > 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 sebastien.jourdain at kitware.com Thu Jan 25 10:00:09 2018 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 25 Jan 2018 08:00:09 -0700 Subject: [Paraview-developers] pvpython and force_offscreen_rendering on OS X In-Reply-To: References: <0C61F573-3CD4-4110-8F51-0FDA8A56E3CF@kitware.com> Message-ID: Visualizer is another one https://github.com/kitware/visualizer. Ok so the issue is that you are using the latest version of light-viz with an older version of ParaView. So to use light-viz with your ParaView 5.4.1 you will need to use the version 1.16.5 instead of 1.17.+. But the version of ParaView that you download from our web site already embed both Visualizer and LightViz that would work with it. Just at the package content. => https://kitware.github.io/paraviewweb/docs/architecture.html#Simplicity Regarding the offscreen part. If it is just for development you should skip that part or use a more recent ParaView to have that --force-offscreen-rendering. The new infrastructure is so much better specially on Mac where before it was buggy. You can download the latest ParaView with both light-viz and visualizer here: https://www.paraview.org/download/ Then change the version to "Nightly". Seb On Thu, Jan 25, 2018 at 6:40 AM, Sgouros, Thomas wrote: > Thank you, it would be lovely if you could check on that. From what I > could read, the application I need to develop is probably only close to > light-viz, but I figured that inspecting it and the infrastructure it sits > on would be a good start. Please let me know how to get at a working > version once you check it out. > > Incidentally, my goal is to create a web application with only a handful > of visualization options for a fairly specific class of data. Light-viz is > probably overkill, even if its description seemed fairly simple. If there's > a better example I could start with for working with paraviewweb, I'd love > to know what it is. > > Thank you! > > -Tom > > On Wed, Jan 24, 2018 at 10:57 PM, Sebastien Jourdain < > sebastien.jourdain at kitware.com> wrote: > >> I saw you were trying to use light-viz which has some code to force the >> offscreen rendering. But with the latest version of Paraview the way >> offscreen rendering works has changed and I?m not sure (can?t remember), if >> we updated light-viz to properly enable offscreen with the latest paraview. >> It is easy to fix, but I guess, I?ll have to look and maybe push a new >> version. >> >> Otherwise you should be able to use the binary distribution of ParaView >> without building it. >> >> Seb >> >> On Jan 24, 2018, at 19:53, Sgouros, Thomas >> wrote: >> >> Sure, I didn't mean to seem accusatory. I have to develop a paraviewweb >> application and want to see if I could set up a prototype paraview server >> on my (mac) laptop for the convenience of developing. If I can't, I can't, >> but the text seemed to imply there was a possibility so I soldiered on >> until I got stuck. >> >> Thank you, >> >> -Tom >> >> On Wed, Jan 24, 2018 at 4:47 PM, Utkarsh Ayachit < >> utkarsh.ayachit at kitware.com> wrote: >> >>> Tom, >>> >>> The page also says: >>> >>> "In this page, we limit ourselves to a Linux-based system. On Windows >>> and macOS, offscreen support is available, but true headless operation >>> is currently not widely used and hence left out of this discussion." >>> >>> Thus, the page is mostly for Linux where people have options of using X >>> or not. >>> >>> Utkarsh >>> >>> >>> On Wed, Jan 24, 2018 at 4:23 PM, Sgouros, Thomas >>> wrote: >>> > On this page: >>> > https://www.paraview.org/ParaView/Doc/Nightly/www/cxx-doc/Of >>> fscreen.html >>> > >>> > There is this note: >>> > >>> > Currently, ParaView supports two distinct APIs that are available for >>> > headless operation: EGL and OSMesa (also called Offscreen Mesa). It >>> must be >>> > noted that headless support is a rapidly evolving area and changes are >>> > expected in coming months. Modern H/W OpenGL implementations support >>> EGL >>> > while S/W (or Mesa) supports OSMesa. One has to build ParaView with >>> specific >>> > CMake flags changed to enable either of these APIs. Which headless API >>> you >>> > choose in your build depends on which OpenGL implementation you plan >>> to use. >>> > >>> > I thought this meant I should try to build Paraview from source. My >>> original >>> > question had a second part about why my build wasn't working, but I'd >>> also >>> > add that it's not clear how to find the OSMesa option through the >>> superbuild >>> > process, either. >>> > >>> > Thank you, >>> > >>> > -Tom >>> > >>> > >>> > On Wed, Jan 24, 2018 at 4:16 PM, Utkarsh Ayachit >>> > wrote: >>> >> >>> >> Okay, I misspoke again :). pvpython should indeed have this command >>> >> line option. Maybe someone with access to a mac can see why this isn't >>> >> working. I can try out on my home mac later tonight and get back to >>> >> you if no one responds before then. >>> >> >>> >> On Wed, Jan 24, 2018 at 4:07 PM, Sgouros, Thomas >>> >> wrote: >>> >> > Thank you. I'm chasing this issue, actually. Perhaps I've >>> misdiagnosed >>> >> > it? >>> >> > >>> >> > $ LightViz --paraview /Applications/ParaView-5.4.1.app --data >>> >> > ../mat-viz-mofTFF-90L-9.1lpm-100rpm >>> >> > >>> >> > >>> >> > >>> >> > ============================================================ >>> =================== >>> >> > >>> >> > | Execute: >>> >> > >>> >> > | $ "/Applications/ParaView-5.4.1.app/Contents/bin/pvpython" >>> >> > >>> >> > | -dr >>> >> > >>> >> > | --force-offscreen-rendering >>> >> > >>> >> > | "/usr/local/lib/node_modules/light-viz/server/pvw-light-viz.py" >>> >> > >>> >> > | --content >>> >> > >>> >> > | "/usr/local/lib/node_modules/light-viz/dist" >>> >> > >>> >> > | --port >>> >> > >>> >> > | 8080 >>> >> > >>> >> > | --data >>> >> > >>> >> > | "../mat-viz-mofTFF-90L-9.1lpm-100rpm" >>> >> > >>> >> > >>> >> > ============================================================ >>> =================== >>> >> > >>> >> > >>> >> > Got unknown argument: --force-offscreen-rendering >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > On Wed, Jan 24, 2018 at 4:02 PM, Utkarsh Ayachit >>> >> > wrote: >>> >> >> >>> >> >> I misspoke. Not pvpython, the option is only available for >>> pvserver, >>> >> >> pvbatch and not pvpython. >>> >> >> >>> >> >> No, XQuartz is not it. If you're logged in, you have access to the >>> >> >> Cocoa >>> >> >> server. >>> >> >> >>> >> >> On Wed, Jan 24, 2018 at 3:58 PM, Sgouros, Thomas >>> >> >> wrote: >>> >> >> > $ /Applications/ParaView-5.4.1.app/Contents/bin/pvpython >>> >> >> > --force-offscreen-rendering >>> >> >> > Got unknown argument: --force-offscreen-rendering >>> >> >> > >>> >> >> > What does "access to Cocoa" mean in this context? How would I go >>> >> >> > about >>> >> >> > giving it that access? All I could think of was to run the >>> XQuartz >>> >> >> > server at >>> >> >> > the same time, but I don't see any way to tell pvpython to look >>> >> >> > there. >>> >> >> > >>> >> >> > Thank you, >>> >> >> > >>> >> >> > -Tom >>> >> >> > >>> >> >> > On Wed, Jan 24, 2018 at 3:36 PM, Utkarsh Ayachit >>> >> >> > wrote: >>> >> >> >> >>> >> >> >> You can use `--force-offscreen-rendering` flag for standard >>> ParaView >>> >> >> >> builds on OsX when using pvpython/pvserver etc. It simply >>> implies >>> >> >> >> that >>> >> >> >> there'll be no windows popped up for these command line >>> executables. >>> >> >> >> Note, ParaView still needs access to Cocoa to create OpenGL >>> contexts >>> >> >> >> for rendering. >>> >> >> >> >>> >> >> >> Utkarsh >>> >> >> >> >>> >> >> >> On Wed, Jan 24, 2018 at 3:02 PM, Sgouros, Thomas >>> >> >> >> wrote: >>> >> >> >> > Hello: >>> >> >> >> > >>> >> >> >> > The documentation seems ambiguous on the point, can anyone >>> confirm >>> >> >> >> > for >>> >> >> >> > me >>> >> >> >> > how to get a version of pvpython that runs on OS X and >>> supports >>> >> >> >> > the >>> >> >> >> > --force-offscreen-rendering option? >>> >> >> >> > >>> >> >> >> > My reading seems to imply that I will have to compile from the >>> >> >> >> > source, >>> >> >> >> > but >>> >> >> >> > I've been trying and failing to understand how to make the >>> >> >> >> > super-build >>> >> >> >> > process work. If someone can confirm for me that this is the >>> way >>> >> >> >> > forward, >>> >> >> >> > I'd appreciate it. >>> >> >> >> > >>> >> >> >> > Also, when using the paraview-superbuild, when I try to >>> install, I >>> >> >> >> > get >>> >> >> >> > this: >>> >> >> >> > >>> >> >> >> > CMake Error at >>> >> >> >> > /../paraview-superbuild/projects/apple/paraview.bundle.cmake >>> :8 >>> >> >> >> > (message): >>> >> >> >> > >>> >> >> >> > Creating the Apple package without the GUI is not supported. >>> >> >> >> > >>> >> >> >> > To which superbuild option does this refer? >>> >> >> >> > >>> >> >> >> > Thank you, >>> >> >> >> > >>> >> >> >> > -Tom >>> >> >> >> > >>> >> >> >> > >>> >> >> >> > _______________________________________________ >>> >> >> >> > 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 kriolog at gmail.com Mon Jan 29 16:57:48 2018 From: kriolog at gmail.com (Maxim Torgonskiy) Date: Mon, 29 Jan 2018 16:57:48 -0500 Subject: [Paraview-developers] bug in pqPipelineFilter In-Reply-To: References: Message-ID: Hi Utkarsh, > There's was never meant to be any order matching between the VTK port numbers and input ports provided by pqPipelineFilter... If there's a convincing reason to preserve it, we can surely fix it, however. I finally found one. :) When I wrap my filter in a Paraview Custom filter, if I use a default wizard's name 'Input' it changes the input name and I can't search by name with pqPipelineFilter anymore. Regards, Maxim 2017-08-04 9:52 GMT-04:00 Maxim Torgonskiy : > Sounds convincing, I'll switch to named access. Thank you for the > clarification! > > Le 3 ao?t 2017 11:14, "Utkarsh Ayachit" a > ?crit : > > While the mismatch may be confusing, ParaView deliberately opted for > "named" access to the inputs since the proxy mechanism does provide ability > to hide/ignore/change input ports. For example, proxy may not even have > input properties for all input ports if some of them are optional. > > On Wed, Aug 2, 2017 at 6:19 PM, Maxim Torgonskiy > wrote: > >> Ok, I see. I just supposed that the order of ports is the same. Before, >> in my paraview plugin I used everywhere access by index (for both VTK and pqPipeline* >> parts) and now I should mix it with access by input name which is less >> consistent. >> >> Thanks, >> Maxim >> >> >> >> 2017-08-02 17:39 GMT-04:00 Utkarsh Ayachit : >> >>> There's was never meant to be any order matching between the VTK port >>> numbers and input ports provided by pqPipelineFilter. The latter indeed >>> used a map internally using the property name as the key for the map >>> (hence the change in order). >>> >>> If there's a convincing reason to preserve it, we can surely fix it, >>> however. >>> >>> Utkarsh >>> >>> On Wed, Aug 2, 2017 at 4:08 PM, Maxim Torgonskiy >>> wrote: >>> >>>> Hello, >>>> >>>> It seems that there's a bug in pqPipelineFilter::getInputPortName(int). >>>> I have a vtk filter which has 3 inputs and when I try to access the inputs >>>> with pqPipelineFilter the function getInputPortName doesn't respect their >>>> order: >>>> >>>> .xml : >>>> >>>> >>>> >>>> >>>> >>> name="Zero" >>>> port_index="0" >>>> command="SetInputConnection"> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> name="One" >>>> port_index="1" >>>> optional="1" >>>> command="SetInputConnection"> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> name="Two" >>>> port_index="2" >>>> optional="1" >>>> command="SetInputConnection"> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> .cxx : >>>> int Dummy::RequestData( >>>> vtkInformation *vtkNotUsed(info), >>>> vtkInformationVector **inputVector, >>>> vtkInformationVector *outputVector) >>>> { >>>> pqPipelineFilter* self_pqfilter = qobject_cast>>> >(pqActiveObjects::instance().activeSource()); >>>> Q_ASSERT(self_pqfilter); >>>> >>>> for(int i = 0; i < GetNumberOfInputPorts(); ++i) >>>> qDebug() << self_pqfilter->getInputPortName(i); >>>> >>>> return 1; >>>> } >>>> >>>> output : >>>> "One" >>>> "Two" >>>> "Zero" >>>> >>>> >>>> A minimal reproducible example is attached. >>>> >>>> Regards, >>>> Maxim >>>> >>>> >>>> _______________________________________________ >>>> 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: >>>> http://public.kitware.com/mailman/listinfo/paraview-developers >>>> >>>> >>> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Jan 30 08:26:34 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 30 Jan 2018 08:26:34 -0500 Subject: [Paraview-developers] bug in pqPipelineFilter In-Reply-To: References: Message-ID: Maxim, BTW, this has been changed in "master", see https://gitlab.kitware.com/paraview/paraview/merge_requests/2061 Utkarsh On Mon, Jan 29, 2018 at 4:57 PM, Maxim Torgonskiy wrote: > Hi Utkarsh, > >> There's was never meant to be any order matching between the VTK port >> numbers and input ports provided by pqPipelineFilter... If there's a >> convincing reason to preserve it, we can surely fix it, however. > I finally found one. :) When I wrap my filter in a Paraview Custom filter, > if I use a default wizard's name 'Input' it changes the input name and I > can't search by name with pqPipelineFilter anymore. > > Regards, > Maxim > > 2017-08-04 9:52 GMT-04:00 Maxim Torgonskiy : >> >> Sounds convincing, I'll switch to named access. Thank you for the >> clarification! >> >> Le 3 ao?t 2017 11:14, "Utkarsh Ayachit" a >> ?crit : >> >> While the mismatch may be confusing, ParaView deliberately opted for >> "named" access to the inputs since the proxy mechanism does provide ability >> to hide/ignore/change input ports. For example, proxy may not even have >> input properties for all input ports if some of them are optional. >> >> On Wed, Aug 2, 2017 at 6:19 PM, Maxim Torgonskiy >> wrote: >>> >>> Ok, I see. I just supposed that the order of ports is the same. Before, >>> in my paraview plugin I used everywhere access by index (for both VTK and >>> pqPipeline* parts) and now I should mix it with access by input name which >>> is less consistent. >>> >>> Thanks, >>> Maxim >>> >>> >>> >>> 2017-08-02 17:39 GMT-04:00 Utkarsh Ayachit : >>>> >>>> There's was never meant to be any order matching between the VTK port >>>> numbers and input ports provided by pqPipelineFilter. The latter indeed used >>>> a map internally using the property name as the key for the map (hence the >>>> change in order). >>>> >>>> If there's a convincing reason to preserve it, we can surely fix it, >>>> however. >>>> >>>> Utkarsh >>>> >>>> On Wed, Aug 2, 2017 at 4:08 PM, Maxim Torgonskiy >>>> wrote: >>>>> >>>>> Hello, >>>>> >>>>> It seems that there's a bug in pqPipelineFilter::getInputPortName(int). >>>>> I have a vtk filter which has 3 inputs and when I try to access the inputs >>>>> with pqPipelineFilter the function getInputPortName doesn't respect their >>>>> order: >>>>> >>>>> .xml : >>>>> >>>>> >>>>> >>>>> >>>>> >>>> name="Zero" >>>>> port_index="0" >>>>> command="SetInputConnection"> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> name="One" >>>>> port_index="1" >>>>> optional="1" >>>>> command="SetInputConnection"> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> name="Two" >>>>> port_index="2" >>>>> optional="1" >>>>> command="SetInputConnection"> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> .cxx : >>>>> int Dummy::RequestData( >>>>> vtkInformation *vtkNotUsed(info), >>>>> vtkInformationVector **inputVector, >>>>> vtkInformationVector *outputVector) >>>>> { >>>>> pqPipelineFilter* self_pqfilter = >>>>> qobject_cast(pqActiveObjects::instance().activeSource()); >>>>> Q_ASSERT(self_pqfilter); >>>>> >>>>> for(int i = 0; i < GetNumberOfInputPorts(); ++i) >>>>> qDebug() << self_pqfilter->getInputPortName(i); >>>>> >>>>> return 1; >>>>> } >>>>> >>>>> output : >>>>> "One" >>>>> "Two" >>>>> "Zero" >>>>> >>>>> >>>>> A minimal reproducible example is attached. >>>>> >>>>> Regards, >>>>> Maxim >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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: >>>>> http://public.kitware.com/mailman/listinfo/paraview-developers >>>>> >>>> >>> >> >> > From wascott at sandia.gov Tue Jan 30 13:22:01 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 30 Jan 2018 18:22:01 +0000 Subject: [Paraview-developers] New warning (error) Message-ID: <371f24fc03544f7ea32b6a402c7d995b@ES01AMSNLNT.srn.sandia.gov> 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 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Jan 30 13:40:06 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 30 Jan 2018 13:40:06 -0500 Subject: [Paraview-developers] New warning (error) In-Reply-To: <371f24fc03544f7ea32b6a402c7d995b@ES01AMSNLNT.srn.sandia.gov> References: <371f24fc03544f7ea32b6a402c7d995b@ES01AMSNLNT.srn.sandia.gov> Message-ID: 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 >