From rajphysics.mon at gmail.com Mon Jun 1 04:48:12 2015 From: rajphysics.mon at gmail.com (Raj Kumar Manna) Date: Mon, 1 Jun 2015 14:18:12 +0530 Subject: [Paraview] Latex preamble (bold math ) in paraview Message-ID: Hi, I want to use bold math like $\bm{x/a}$ in Paraview text. Is it possible to inclue latex preamble like we do in matplotlib plt.rc('text', usetex=True) plt.rcParams['text.latex.preamble']=[r"\usepackage{bm}"] Is there any other way to include bold math? Thanks Raj -- ################################################################## Raj Kumar Manna Complex Fluid & Biological Physics Lab IIT Madras Ph. No. 8144637401 alternate email: raj at physics.iitm.ac.in #################################################################### -------------- next part -------------- An HTML attachment was scrubbed... URL: From cws105 at mun.ca Mon Jun 1 09:18:02 2015 From: cws105 at mun.ca (Stanbridge, Christopher William) Date: Mon, 1 Jun 2015 10:48:02 -0230 Subject: [Paraview] In order to run ParaView in client/server mode... Message-ID: Hi ParaViewers, In order to run ParaView in client/server mode (without Mesa), is it necessary to already have one of your user accounts logged into the server end? Cheers, Christopher Stanbridge -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Mon Jun 1 09:44:15 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Mon, 1 Jun 2015 09:44:15 -0400 Subject: [Paraview] Latex preamble (bold math ) in paraview In-Reply-To: References: Message-ID: Does this help? http://www.kitware.com/blog/home/post/509 On Mon, Jun 1, 2015 at 4:48 AM, Raj Kumar Manna wrote: > Hi, > > I want to use bold math like $\bm{x/a}$ in Paraview text. Is it possible > to inclue latex preamble like we do in matplotlib > > plt.rc('text', usetex=True) > plt.rcParams['text.latex.preamble']=[r"\usepackage{bm}"] > > > Is there any other way to include bold math? > > Thanks > Raj > > > -- > ################################################################## > Raj Kumar Manna > Complex Fluid & Biological Physics Lab > IIT Madras > > Ph. No. 8144637401 > > alternate email: raj at physics.iitm.ac.in > #################################################################### > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rajphysics.mon at gmail.com Mon Jun 1 10:06:57 2015 From: rajphysics.mon at gmail.com (Raj Kumar Manna) Date: Mon, 1 Jun 2015 19:36:57 +0530 Subject: [Paraview] Latex preamble (bold math ) in paraview In-Reply-To: References: Message-ID: In paraview text, ${x/a}$ gives the latex font but $\bm{x/a}$ does not work. Whereas in matplotlib we can set the latex preamble like I mentioned. Raj On Mon, Jun 1, 2015 at 7:14 PM, Dan Lipsa wrote: > Does this help? > > http://www.kitware.com/blog/home/post/509 > > > On Mon, Jun 1, 2015 at 4:48 AM, Raj Kumar Manna > wrote: > >> Hi, >> >> I want to use bold math like $\bm{x/a}$ in Paraview text. Is it possible >> to inclue latex preamble like we do in matplotlib >> >> plt.rc('text', usetex=True) >> plt.rcParams['text.latex.preamble']=[r"\usepackage{bm}"] >> >> >> Is there any other way to include bold math? >> >> Thanks >> Raj >> >> >> -- >> ################################################################## >> Raj Kumar Manna >> Complex Fluid & Biological Physics Lab >> IIT Madras >> >> Ph. No. 8144637401 >> >> alternate email: raj at physics.iitm.ac.in >> #################################################################### >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -- ################################################################## Raj Kumar Manna Complex Fluid & Biological Physics Lab IIT Madras Ph. No. 8144637401 alternate email: raj at physics.iitm.ac.in #################################################################### -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Mon Jun 1 10:15:03 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Mon, 1 Jun 2015 10:15:03 -0400 Subject: [Paraview] Latex preamble (bold math ) in paraview In-Reply-To: References: Message-ID: Try using \bf instead of \bm. On Mon, Jun 1, 2015 at 10:06 AM, Raj Kumar Manna wrote: > In paraview text, ${x/a}$ gives the latex font but $\bm{x/a}$ does not > work. Whereas in matplotlib we can set the latex preamble like I mentioned. > > Raj > > On Mon, Jun 1, 2015 at 7:14 PM, Dan Lipsa wrote: > >> Does this help? >> >> http://www.kitware.com/blog/home/post/509 >> >> >> On Mon, Jun 1, 2015 at 4:48 AM, Raj Kumar Manna > > wrote: >> >>> Hi, >>> >>> I want to use bold math like $\bm{x/a}$ in Paraview text. Is it possible >>> to inclue latex preamble like we do in matplotlib >>> >>> plt.rc('text', usetex=True) >>> plt.rcParams['text.latex.preamble']=[r"\usepackage{bm}"] >>> >>> >>> Is there any other way to include bold math? >>> >>> Thanks >>> Raj >>> >>> >>> -- >>> ################################################################## >>> Raj Kumar Manna >>> Complex Fluid & Biological Physics Lab >>> IIT Madras >>> >>> Ph. No. 8144637401 >>> >>> alternate email: raj at physics.iitm.ac.in >>> #################################################################### >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > > > -- > ################################################################## > Raj Kumar Manna > Complex Fluid & Biological Physics Lab > IIT Madras > > Ph. No. 8144637401 > > alternate email: raj at physics.iitm.ac.in > #################################################################### > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Mon Jun 1 10:49:40 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Mon, 1 Jun 2015 10:49:40 -0400 Subject: [Paraview] Latex preamble (bold math ) in paraview In-Reply-To: References: Message-ID: \mathbf also works. See http://tex.stackexchange.com/questions/595/how-can-i-get-bold-math-symbols second answer. On Mon, Jun 1, 2015 at 10:15 AM, Dan Lipsa wrote: > Try using \bf instead of \bm. > > On Mon, Jun 1, 2015 at 10:06 AM, Raj Kumar Manna > wrote: > >> In paraview text, ${x/a}$ gives the latex font but $\bm{x/a}$ does not >> work. Whereas in matplotlib we can set the latex preamble like I mentioned. >> >> Raj >> >> On Mon, Jun 1, 2015 at 7:14 PM, Dan Lipsa wrote: >> >>> Does this help? >>> >>> http://www.kitware.com/blog/home/post/509 >>> >>> >>> On Mon, Jun 1, 2015 at 4:48 AM, Raj Kumar Manna < >>> rajphysics.mon at gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I want to use bold math like $\bm{x/a}$ in Paraview text. Is it >>>> possible to inclue latex preamble like we do in matplotlib >>>> >>>> plt.rc('text', usetex=True) >>>> plt.rcParams['text.latex.preamble']=[r"\usepackage{bm}"] >>>> >>>> >>>> Is there any other way to include bold math? >>>> >>>> Thanks >>>> Raj >>>> >>>> >>>> -- >>>> ################################################################## >>>> Raj Kumar Manna >>>> Complex Fluid & Biological Physics Lab >>>> IIT Madras >>>> >>>> Ph. No. 8144637401 >>>> >>>> alternate email: raj at physics.iitm.ac.in >>>> #################################################################### >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> >> >> -- >> ################################################################## >> Raj Kumar Manna >> Complex Fluid & Biological Physics Lab >> IIT Madras >> >> Ph. No. 8144637401 >> >> alternate email: raj at physics.iitm.ac.in >> #################################################################### >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Jun 1 10:55:13 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 01 Jun 2015 14:55:13 +0000 Subject: [Paraview] In order to run ParaView in client/server mode... In-Reply-To: References: Message-ID: No, but accessing the Xserver on the server side may require you to work with the administrator. See this thread for some info: http://public.kitware.com/pipermail/paraview-developers/2015-May/003784.html Utkarsh On Mon, Jun 1, 2015 at 9:18 AM Stanbridge, Christopher William < cws105 at mun.ca> wrote: > Hi ParaViewers, > > In order to run ParaView in client/server mode (without Mesa), is it > necessary to already have one of your user accounts logged into the server > end? > > Cheers, > Christopher Stanbridge > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Mon Jun 1 12:02:18 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Mon, 1 Jun 2015 12:02:18 -0400 Subject: [Paraview] IEEE Supercomputing 2015 - Kitware wants your images and videos! Message-ID: Greetings VTK and ParaView communities, We at Kitware are searching for interesting images and videos to show in our booth at this year's Supercomputing conference . For a sample of what we demonstrated before, check out 2013 and 2014 highlights. In conjunction with SC15, and again with your permission, we would also like to add your visualizations to the galleries on paraview.org or vtk.org. So, if you've made some great looking visualizations recently with VTK and ParaView, are able to share them, and want us to show them off, please send me an email so I can discuss the details with you in person. Videos should ideally be 1920x1080 pixels for HD display, and still visualizations should be 150ppi when scaled to 100%. For the attribution, we will need at a minimum your name, a title or brief caption, and the acknowledgement as you would like it to appear. Finally, if you happen to be going to the conference and would like a forum to present your work at, please let me know so we can schedule your presentation in our booth. thanks, and I hope to see many of you at SuperComputing! David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rajphysics.mon at gmail.com Mon Jun 1 12:35:35 2015 From: rajphysics.mon at gmail.com (Raj Kumar Manna) Date: Mon, 1 Jun 2015 22:05:35 +0530 Subject: [Paraview] Latex preamble (bold math ) in paraview In-Reply-To: References: Message-ID: I have seen the answer before But \mathbf does not give the latex bold font, it just gives bold font without the latex font. I would prefer font of \boldmath or \bm. Thanks for your help. Raj On Mon, Jun 1, 2015 at 8:19 PM, Dan Lipsa wrote: > \mathbf also works. > > See > http://tex.stackexchange.com/questions/595/how-can-i-get-bold-math-symbols > second answer. > > On Mon, Jun 1, 2015 at 10:15 AM, Dan Lipsa wrote: > >> Try using \bf instead of \bm. >> >> On Mon, Jun 1, 2015 at 10:06 AM, Raj Kumar Manna < >> rajphysics.mon at gmail.com> wrote: >> >>> In paraview text, ${x/a}$ gives the latex font but $\bm{x/a}$ does not >>> work. Whereas in matplotlib we can set the latex preamble like I mentioned. >>> >>> Raj >>> >>> On Mon, Jun 1, 2015 at 7:14 PM, Dan Lipsa wrote: >>> >>>> Does this help? >>>> >>>> http://www.kitware.com/blog/home/post/509 >>>> >>>> >>>> On Mon, Jun 1, 2015 at 4:48 AM, Raj Kumar Manna < >>>> rajphysics.mon at gmail.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> I want to use bold math like $\bm{x/a}$ in Paraview text. Is it >>>>> possible to inclue latex preamble like we do in matplotlib >>>>> >>>>> plt.rc('text', usetex=True) >>>>> plt.rcParams['text.latex.preamble']=[r"\usepackage{bm}"] >>>>> >>>>> >>>>> Is there any other way to include bold math? >>>>> >>>>> Thanks >>>>> Raj >>>>> >>>>> >>>>> -- >>>>> ################################################################## >>>>> Raj Kumar Manna >>>>> Complex Fluid & Biological Physics Lab >>>>> IIT Madras >>>>> >>>>> Ph. No. 8144637401 >>>>> >>>>> alternate email: raj at physics.iitm.ac.in >>>>> #################################################################### >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >>> >>> -- >>> ################################################################## >>> Raj Kumar Manna >>> Complex Fluid & Biological Physics Lab >>> IIT Madras >>> >>> Ph. No. 8144637401 >>> >>> alternate email: raj at physics.iitm.ac.in >>> #################################################################### >>> >> >> > -- ################################################################## Raj Kumar Manna Complex Fluid & Biological Physics Lab IIT Madras Ph. No. 8144637401 alternate email: raj at physics.iitm.ac.in #################################################################### -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.lonie at kitware.com Mon Jun 1 12:50:29 2015 From: david.lonie at kitware.com (David Lonie) Date: Mon, 1 Jun 2015 12:50:29 -0400 Subject: [Paraview] Latex preamble (bold math ) in paraview In-Reply-To: References: Message-ID: On Mon, Jun 1, 2015 at 12:35 PM, Raj Kumar Manna wrote: > I have seen the answer > before > But \mathbf does not give the latex bold font, it just gives bold font > without the latex font. I would prefer font of \boldmath or \bm. Thanks for > your help. > It is not possible to load additional packages or set the matplotlib latex preamble at this time. Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From kevin.dean at decisionsciencescorp.com Mon Jun 1 15:57:59 2015 From: kevin.dean at decisionsciencescorp.com (Dean, Kevin) Date: Mon, 1 Jun 2015 12:57:59 -0700 Subject: [Paraview] pvserver Message-ID: Hey, How's it going? I am currently trying to figure out how to acquire real-time image reconstruction updates across a cluster configuration. I have several reader (plugins) that convert from my types to vtk types. I have also utilized pvserver minimally; but should it be able to read/handle data that is being published to a specified port? Also, I will probably have to create a communication layer that handles CoreDX DDS communication. Would it be proper to create this layer as a plugin or do I need to link it to some pvserver backend? Thanks again! Kevin E. Dean -- This email and its contents are confidential. If you are not the intended recipient, please do not disclose or use the information within this email or its attachments. If you have received this email in error, please report the error to the sender by return email and delete this communication from your records. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jm.lucas at gantha.com Tue Jun 2 02:54:17 2015 From: jm.lucas at gantha.com (Jean-Michel) Date: Tue, 2 Jun 2015 08:54:17 +0200 Subject: [Paraview] Import h5py in python shell In-Reply-To: References: <55647c01.e5e7b60a.36dc.ffffdd49SMTPIN_ADDED_BROKEN@mx.google.com> Message-ID: <000901d09d00$f26c9eb0$d745dc10$@lucas@gantha.com> Thank you for your answer Utkarsh. Unfortunately, the h5py installer for Windows does not find the Python installation packaged with ParaView in my registry, so I cannot install it in ParaView. Jean-Michel De : Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Envoy? : vendredi 29 mai 2015 20:00 ? : Jean-Michel; paraview at paraview.org Objet : Re: [Paraview] Import h5py in python shell ParaView packages its own Python. You'll either need to build ParaView from source using the Python installation you have or install h5py in the Python packaged with ParaView. Utkarsh On Tue, May 26, 2015 at 9:58 AM Jean-Michel wrote: Dear all, I am currently trying to use the h5py module in the Python Shell in ParaView 4.3.1 (64 bits). On my system, h5py comes from my installation of python-xy and works fine outside of ParaView. I tried to import the module by providing the path to the package, using mainly two methods: - append the path to the package with sys.path.append before doing the import - import the module using the imp package and providing the full path to imp.load_source However, both methods failed to load h5py, returing the following error : "ImportError: DLL load failed: %1 is not a valid win32 application". Thank you for your help. Jean-Michel _____ Image supprim?e par l'exp?diteur. Avast logo L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le logiciel antivirus Avast. www.avast.com _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview --- L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le logiciel antivirus Avast. http://www.avast.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD000.jpg Type: image/jpeg Size: 823 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Tue Jun 2 10:27:03 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 02 Jun 2015 14:27:03 +0000 Subject: [Paraview] Import h5py in python shell In-Reply-To: <556d531e.0e47c20a.b521.37a2SMTPIN_ADDED_BROKEN@mx.google.com> References: <55647c01.e5e7b60a.36dc.ffffdd49SMTPIN_ADDED_BROKEN@mx.google.com> <556d531e.0e47c20a.b521.37a2SMTPIN_ADDED_BROKEN@mx.google.com> Message-ID: Another trick to try (no guarantees :) ) is to install Python 2.7.2 (64bit) and then install h5py for this installation of Python. Then, try loading h5py from pvpython. You'll need to extend the sys.path variable to find the installed modules. Utkarsh On Tue, Jun 2, 2015 at 2:54 AM Jean-Michel wrote: > Thank you for your answer Utkarsh. > > > > Unfortunately, the h5py installer for Windows does not find the Python > installation packaged with ParaView in my registry, so I cannot install it > in ParaView. > > > > Jean-Michel > > > > *De :* Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > *Envoy? :* vendredi 29 mai 2015 20:00 > *? :* Jean-Michel; paraview at paraview.org > *Objet :* Re: [Paraview] Import h5py in python shell > > > > ParaView packages its own Python. You'll either need to build ParaView > from source using the Python installation you have or install h5py in the > Python packaged with ParaView. > > > > Utkarsh > > > > On Tue, May 26, 2015 at 9:58 AM Jean-Michel wrote: > > Dear all, > > > > I am currently trying to use the h5py module in the Python Shell in > ParaView 4.3.1 (64 bits). On my system, h5py comes from my installation of > python-xy and works fine outside of ParaView. > > > > I tried to import the module by providing the path to the package, using > mainly two methods: > > - append the path to the package with sys.path.append before doing the > import > > - import the module using the imp package and providing the full path to > imp.load_source > > However, both methods failed to load h5py, returing the following error : > "ImportError: DLL load failed: %1 is not a valid win32 application". > > > > Thank you for your help. > > > > Jean-Michel > > > ------------------------------ > > [image: Image supprim?e par l'exp?diteur. Avast logo] > > > L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le > logiciel antivirus Avast. > www.avast.com > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > ------------------------------ > [image: Avast logo] > > L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le > logiciel antivirus Avast. > www.avast.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD000.jpg Type: image/jpeg Size: 823 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD000.jpg Type: image/jpeg Size: 823 bytes Desc: not available URL: From jm.lucas at gantha.com Tue Jun 2 10:56:09 2015 From: jm.lucas at gantha.com (Jean-Michel) Date: Tue, 2 Jun 2015 16:56:09 +0200 Subject: [Paraview] Import h5py in python shell In-Reply-To: References: <55647c01.e5e7b60a.36dc.ffffdd49SMTPIN_ADDED_BROKEN@mx.google.com> <556d531e.0e47c20a.b521.37a2SMTPIN_ADDED_BROKEN@mx.google.com> Message-ID: <002301d09d44$43736f80$ca5a4e80$@lucas@gantha.com> Thanks again Utkarsh. However, trying to load the installed h5py from pvpython (after appending the path in the sys.path) gives me the same error I ran into in ParaView's python shell: from h5py import _errors ImportError: DLL load failed: %1 is not a valid win32 application Jean-Michel De : Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Envoy? : mardi 2 juin 2015 16:27 ? : Jean-Michel; paraview at paraview.org Objet : Re: [Paraview] Import h5py in python shell Another trick to try (no guarantees :) ) is to install Python 2.7.2 (64bit) and then install h5py for this installation of Python. Then, try loading h5py from pvpython. You'll need to extend the sys.path variable to find the installed modules. Utkarsh On Tue, Jun 2, 2015 at 2:54 AM Jean-Michel wrote: Thank you for your answer Utkarsh. Unfortunately, the h5py installer for Windows does not find the Python installation packaged with ParaView in my registry, so I cannot install it in ParaView. Jean-Michel De : Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Envoy? : vendredi 29 mai 2015 20:00 ? : Jean-Michel; paraview at paraview.org Objet : Re: [Paraview] Import h5py in python shell ParaView packages its own Python. You'll either need to build ParaView from source using the Python installation you have or install h5py in the Python packaged with ParaView. Utkarsh On Tue, May 26, 2015 at 9:58 AM Jean-Michel wrote: Dear all, I am currently trying to use the h5py module in the Python Shell in ParaView 4.3.1 (64 bits). On my system, h5py comes from my installation of python-xy and works fine outside of ParaView. I tried to import the module by providing the path to the package, using mainly two methods: - append the path to the package with sys.path.append before doing the import - import the module using the imp package and providing the full path to imp.load_source However, both methods failed to load h5py, returing the following error : "ImportError: DLL load failed: %1 is not a valid win32 application". Thank you for your help. Jean-Michel _____ Image supprim?e par l'exp?diteur. Avast logo L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le logiciel antivirus Avast. www.avast.com _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview _____ Image supprim?e par l'exp?diteur. Avast logo L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le logiciel antivirus Avast. www.avast.com --- L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le logiciel antivirus Avast. http://www.avast.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD000.jpg Type: image/jpeg Size: 823 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Tue Jun 2 11:27:13 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 02 Jun 2015 15:27:13 +0000 Subject: [Paraview] Import h5py in python shell In-Reply-To: <556dc40b.41f2c20a.34ea.ffffc368SMTPIN_ADDED_BROKEN@mx.google.com> References: <55647c01.e5e7b60a.36dc.ffffdd49SMTPIN_ADDED_BROKEN@mx.google.com> <556d531e.0e47c20a.b521.37a2SMTPIN_ADDED_BROKEN@mx.google.com> <556dc40b.41f2c20a.34ea.ffffc368SMTPIN_ADDED_BROKEN@mx.google.com> Message-ID: Maybe try setting the PATH such that it finds the DLLs it's trying to loads -- it's a Hail Mary, but why not :). On Tue, Jun 2, 2015 at 10:56 AM Jean-Michel wrote: > Thanks again Utkarsh. > > > > However, trying to load the installed h5py from pvpython (after appending > the path in the sys.path) gives me the same error I ran into in ParaView's > python shell: > > > > from h5py import _errors > > ImportError: DLL load failed: %1 is not a valid win32 application > > > > Jean-Michel > > > > *De :* Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > *Envoy? :* mardi 2 juin 2015 16:27 > > > *? :* Jean-Michel; paraview at paraview.org > *Objet :* Re: [Paraview] Import h5py in python shell > > > > Another trick to try (no guarantees :) ) is to install Python 2.7.2 > (64bit) and then install h5py for this installation of Python. Then, try > loading h5py from pvpython. You'll need to extend the sys.path variable to > find the installed modules. > > > > Utkarsh > > > > On Tue, Jun 2, 2015 at 2:54 AM Jean-Michel wrote: > > Thank you for your answer Utkarsh. > > > > Unfortunately, the h5py installer for Windows does not find the Python > installation packaged with ParaView in my registry, so I cannot install it > in ParaView. > > > > Jean-Michel > > > > *De :* Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > *Envoy? :* vendredi 29 mai 2015 20:00 > *? :* Jean-Michel; paraview at paraview.org > *Objet :* Re: [Paraview] Import h5py in python shell > > > > ParaView packages its own Python. You'll either need to build ParaView > from source using the Python installation you have or install h5py in the > Python packaged with ParaView. > > > > Utkarsh > > > > On Tue, May 26, 2015 at 9:58 AM Jean-Michel wrote: > > Dear all, > > > > I am currently trying to use the h5py module in the Python Shell in > ParaView 4.3.1 (64 bits). On my system, h5py comes from my installation of > python-xy and works fine outside of ParaView. > > > > I tried to import the module by providing the path to the package, using > mainly two methods: > > - append the path to the package with sys.path.append before doing the > import > > - import the module using the imp package and providing the full path to > imp.load_source > > However, both methods failed to load h5py, returing the following error : > "ImportError: DLL load failed: %1 is not a valid win32 application". > > > > Thank you for your help. > > > > Jean-Michel > > > ------------------------------ > > [image: Image supprim?e par l'exp?diteur. Avast logo] > > > L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le > logiciel antivirus Avast. > www.avast.com > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > ------------------------------ > > [image: Image supprim?e par l'exp?diteur. Avast logo] > > > L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le > logiciel antivirus Avast. > www.avast.com > > > > > > ------------------------------ > [image: Avast logo] > > L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le > logiciel antivirus Avast. > www.avast.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD000.jpg Type: image/jpeg Size: 823 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD000.jpg Type: image/jpeg Size: 823 bytes Desc: not available URL: From berk.geveci at kitware.com Tue Jun 2 15:46:49 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Tue, 2 Jun 2015 15:46:49 -0400 Subject: [Paraview] Call For Papers: LDAV 2015, The 5th IEEE Symposium on Large Data Analysis and Visualization Message-ID: Subject: Call For Papers: LDAV 2015, The 5th IEEE Symposium on Large Data Analysis and Visualization LDAV 2015 The 5th IEEE Symposium on Large Data Analysis and Visualization, co-located with IEEE VIS 2015, October 25-26, 2015, Chicago, Illinois, USA http://www.ldav.org/ Contact: papers at ldav.org Modern large-scale scientific simulations, sensor networks, and experiments are generating enormous datasets, with some projects approaching the multiple exabyte range in the near term. Managing and analyzing large data in order to transform it into insight is critical for a variety of disciplines including climate science, nuclear physics, security, materials design, transportation, and urban planning. This is currently referred to as the Big Data Challenge. The tools and approaches needed to mine, analyze, and visualize data at extreme scales can be fully realized only if we have end-to-end solutions, which demands collective, interdisciplinary efforts. The 5th IEEE Large Scale Data Analysis and Visualization (LDAV) symposium, to be held in conjunction with IEEE VIS 2015, is specifically targeting possible end-to-end solutions. The LDAV symposium will bring together domain scientists, data analysts, visualization researchers, users, designers and artists, to foster common ground for solving both near- and long-term problems. Scope: We are looking for original research contributions on a broad-range of topics related to collection, analysis, manipulation or visualization of large-scale data. We also welcome position papers on these topics. Topics of interest include, but are not limited to: * Data collection, management and curation * Innovative approaches combining information visualization, visual analytics, and scientific visualization * Streaming methods for analysis, collection and visualization * Novel, extreme or innovative methods for understanding and interacting with data * Advanced hardware for data handling or visualization * Distributed, parallel or multi-threaded approaches * MapReduce-based and database-related methods, algorithms or approaches * Hierarchical data storage, retrieval or rendering * Collaboration or co-design of data analysis with domain scientists * Topics in cognitive issues specific to manipulating and understanding large data * Application case studies * Industry solutions for big data * End-to-end system solutions Submission Instructions: Submitted manuscripts may not exceed 8 pages. The manuscripts can be 4-8 pages, with the authors determining length based on the content. The manuscripts should be formatted according to guidelines from IEEE VGTC. Submission site note: Go to the submission site ( https://precisionconference.com/~vgtc), log in, go to 'new submissions', and select 'LDAV 2015 Papers'. Proceedings: The proceedings of the symposium will be published together with the VIS proceedings and via the IEEE Xplore Digital Library. Best Paper: The LDAV Program Committee will present a Best Paper award to the authors whose submission is deemed the strongest according to the reviewing criteria. This award will be announced in conjunction with VIS 2015. Important Dates: (Please note the abstract and paper deadlines are firm and no extensions will be granted). Abstract Deadline (firm): June 17, 2015 Paper Submission (firm): June 24, 2015 11:59 PM (AOE) Author Notification: August 13, 2015 Camera-Ready Deadline: August 21, 2015 -------------- next part -------------- An HTML attachment was scrubbed... URL: From b.gazanion at gantha.com Wed Jun 3 06:15:21 2015 From: b.gazanion at gantha.com (Bertrand Gazanion) Date: Wed, 3 Jun 2015 12:15:21 +0200 Subject: [Paraview] Delete data and free memory with the python shell Message-ID: <000501d09de6$34e20150$9ea603f0$@gazanion@gantha.com> Dear all, I have problems understanding how to delete data from paraview using the python shell. The method I am using is the following : #-- delete everything but the sources for f in GetSources().values(): print f if f.GetProperty("Input") is not None: Delete(f) #-- delete the sources for f in GetSources().values(): print f Delete(f) Using this method, the pipeline browser is correctly emptied. However, the memory monitors of ParaView and of the OS show that the amount of RAM used by ParaView has not changed. Could you explain me what I'm missing ? Thanks, Bertrand --- L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le logiciel antivirus Avast. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: From jm.lucas at gantha.com Wed Jun 3 09:28:21 2015 From: jm.lucas at gantha.com (Jean-Michel) Date: Wed, 3 Jun 2015 15:28:21 +0200 Subject: [Paraview] Import h5py in python shell In-Reply-To: References: <55647c01.e5e7b60a.36dc.ffffdd49SMTPIN_ADDED_BROKEN@mx.google.com> <556d531e.0e47c20a.b521.37a2SMTPIN_ADDED_BROKEN@mx.google.com> <556dc40b.41f2c20a.34ea.ffffc368SMTPIN_ADDED_BROKEN@mx.google.com> Message-ID: <000b01d09e01$29cd4a20$7d67de60$@lucas@gantha.com> As it turns out, my python installation is 32 bits, which I wasn't aware of (checked it with platform.architecture). Loading h5py in the python shell from ParaView 32 bits works fine after extending sys.path. Anyway, thank you very much for your help. Jean-Michel De : Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Envoy? : mardi 2 juin 2015 17:27 ? : Jean-Michel; paraview at paraview.org Objet : Re: [Paraview] Import h5py in python shell Maybe try setting the PATH such that it finds the DLLs it's trying to loads -- it's a Hail Mary, but why not :). On Tue, Jun 2, 2015 at 10:56 AM Jean-Michel wrote: Thanks again Utkarsh. However, trying to load the installed h5py from pvpython (after appending the path in the sys.path) gives me the same error I ran into in ParaView's python shell: from h5py import _errors ImportError: DLL load failed: %1 is not a valid win32 application Jean-Michel De : Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Envoy? : mardi 2 juin 2015 16:27 ? : Jean-Michel; paraview at paraview.org Objet : Re: [Paraview] Import h5py in python shell Another trick to try (no guarantees :) ) is to install Python 2.7.2 (64bit) and then install h5py for this installation of Python. Then, try loading h5py from pvpython. You'll need to extend the sys.path variable to find the installed modules. Utkarsh On Tue, Jun 2, 2015 at 2:54 AM Jean-Michel wrote: Thank you for your answer Utkarsh. Unfortunately, the h5py installer for Windows does not find the Python installation packaged with ParaView in my registry, so I cannot install it in ParaView. Jean-Michel De : Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Envoy? : vendredi 29 mai 2015 20:00 ? : Jean-Michel; paraview at paraview.org Objet : Re: [Paraview] Import h5py in python shell ParaView packages its own Python. You'll either need to build ParaView from source using the Python installation you have or install h5py in the Python packaged with ParaView. Utkarsh On Tue, May 26, 2015 at 9:58 AM Jean-Michel wrote: Dear all, I am currently trying to use the h5py module in the Python Shell in ParaView 4.3.1 (64 bits). On my system, h5py comes from my installation of python-xy and works fine outside of ParaView. I tried to import the module by providing the path to the package, using mainly two methods: - append the path to the package with sys.path.append before doing the import - import the module using the imp package and providing the full path to imp.load_source However, both methods failed to load h5py, returing the following error : "ImportError: DLL load failed: %1 is not a valid win32 application". Thank you for your help. Jean-Michel _____ Image supprim?e par l'exp?diteur. Avast logo L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le logiciel antivirus Avast. www.avast.com _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview _____ Image supprim?e par l'exp?diteur. Avast logo L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le logiciel antivirus Avast. www.avast.com _____ Image supprim?e par l'exp?diteur. Avast logo L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le logiciel antivirus Avast. www.avast.com --- L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le logiciel antivirus Avast. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD000.jpg Type: image/jpeg Size: 823 bytes Desc: not available URL: From adlinds3 at ncsu.edu Wed Jun 3 13:23:13 2015 From: adlinds3 at ncsu.edu (Alex Lindsay) Date: Wed, 03 Jun 2015 10:23:13 -0700 Subject: [Paraview] Viewing data from multiple times on an xy-plot Message-ID: <556F3801.3020909@ncsu.edu> Hi all, Is it possible to display data from one variable for multiple time steps on one xy-plot? Obviously I can play the default animation that's created when I open the file; that's one way to see how the variable changes with time. But I'm interested in being able to look at multiple time points on one static plot. Alex From utkarsh.ayachit at kitware.com Wed Jun 3 13:37:02 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 03 Jun 2015 17:37:02 +0000 Subject: [Paraview] Viewing data from multiple times on an xy-plot In-Reply-To: <556F3801.3020909@ncsu.edu> References: <556F3801.3020909@ncsu.edu> Message-ID: Not in the same view, but the "Comparative" versions of the line/bar chart views allow you see multiple timesteps side by side. You can use the "Comparative View Inspector" to add "Time" as the parameter to compare and then setup the timestep values of interest for each of the views. Utkarsh On Wed, Jun 3, 2015 at 1:23 PM Alex Lindsay wrote: > Hi all, > > Is it possible to display data from one variable for multiple time steps > on one xy-plot? Obviously I can play the default animation that's > created when I open the file; that's one way to see how the variable > changes with time. But I'm interested in being able to look at multiple > time points on one static plot. > > Alex > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From adlinds3 at ncsu.edu Wed Jun 3 13:58:23 2015 From: adlinds3 at ncsu.edu (Alex Lindsay) Date: Wed, 03 Jun 2015 10:58:23 -0700 Subject: [Paraview] Viewing data from multiple times on an xy-plot In-Reply-To: References: <556F3801.3020909@ncsu.edu> Message-ID: <556F403F.7050603@ncsu.edu> I'm getting a segmentation fault when I click on "Line Chart View (Comparative)". Is this is a problem anyone else has had in the past? Any quick suggestions? On 06/03/2015 10:37 AM, Utkarsh Ayachit wrote: > Not in the same view, but the "Comparative" versions of the line/bar > chart views allow you see multiple timesteps side by side. You can use > the "Comparative View Inspector" to add "Time" as the parameter to > compare and then setup the timestep values of interest for each of the > views. > > Utkarsh > > On Wed, Jun 3, 2015 at 1:23 PM Alex Lindsay > wrote: > > Hi all, > > Is it possible to display data from one variable for multiple time > steps > on one xy-plot? Obviously I can play the default animation that's > created when I open the file; that's one way to see how the variable > changes with time. But I'm interested in being able to look at > multiple > time points on one static plot. > > Alex > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From goebbert at vr.rwth-aachen.de Thu Jun 4 07:07:58 2015 From: goebbert at vr.rwth-aachen.de (=?iso-8859-1?Q?G=F6bbert=2C_Jens_Henrik?=) Date: Thu, 4 Jun 2015 11:07:58 +0000 Subject: [Paraview] save 'Surface LIC' as texture Message-ID: <0AD08F7A7F420048BE6681638DF90D8136BA0D24@MBX-W2.rwth-ad.de> Hello everyone, I am using ParaView for some time now and love its representation of vector fields on surfaces by 'SurfaceLIC' (http://www.paraview.org/Wiki/ParaView/Line_Integral_Convolution). Beyond that, lots of other representations of scientific data are of course simply great .... I would like to save this textures and the geometrie (incl. texture coordinates) of the surface to view it later in our own OpenGL virtual reality application (or Blender). ParaView can load textures (http://www.paraview.org/Wiki/ParaView:Texture), but how can I save them ? Does anyone has an idea ... including source code modifications, which might make things like that possible. Best, Jens Henrik -------------- next part -------------- An HTML attachment was scrubbed... URL: From aleksejs.fomins at lspr.ch Thu Jun 4 07:17:29 2015 From: aleksejs.fomins at lspr.ch (Aleksejs Fomins) Date: Thu, 04 Jun 2015 13:17:29 +0200 Subject: [Paraview] Optimizing time-step write time for FEM code Message-ID: <557033C9.1030708@lspr.ch> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear Paraview, I am thinking of optimizing our time-animation, as writing it takes a lot of time. We use both VTK and PVTU/VTU formats to write our data. At the moment, we write complete mesh + vector field for each time step, thus creating a series of files. An obvious optimization would be to write the geometry only once, and for every time step only to write the field. Could you suggest if this is possible, and, if yes, a nice way to do this. Kind regards, Aleksejs Fomins PhD student at EPF Lausanne, Nanooptics & Metallurgy Lab Software Engineer at LSPR AG, Zurich -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJVcDPJAAoJEDkNM7UOEwMZXhYQAKs5dbc8hbh+oEN3ed7H7Qwy yro8f//ue3JZg98sjOvZwFbOqw2EHgznC949t3it0UvzfQriSTJVkKpWNC/I8tht Kuox2njDN1FA+3QIFJN8G65UMOt7MkeiPp3dQePU+LgofjyJsvESxhsqaa4MVPrl eA3rP8UCgxJ9r+I9D26br1oIJ7S8NpXnRH6AEODcDAD8uoDG4YzAMsWb3hvVCiJ1 ZBdMLdfWL21PWxvLkxYt6gn1FEaK5jWxOt3AyWFbaS4XgJeTSxgQh2++Y9F5ILPR AwWScpOM+GiHyvXurFqUEASYrWPFMTGia3BiQ2eD12dPJLxuGeLKf1GdRfbzNRix pNDqoYqHw8DuOPhhCgk+4OQ1TvcKrKPm5DWUMJqu0E8b8Wih+ZCZHcbo52r4C2Ks 4ecsp2XqmwifNe3bRFwZYQjn0xNPJV/i/E2PEwNpPtWRfziZxfRC6IVMoNJLzQeL I9cqXIFWaTJpb9ZlnrgZuCrgm4++KEZ24/17eHt92vIbXrD2RW4BxbR095/TIqTv h0xoKjr82ty1BeT0JNEfXFrE0v6FUr9yPW8p5CZ+hfcKvZk6FvGcPQj4nsukPFXW +Qvl+avb9QmY71S1TwXKw2Y1YMQu5rscZJ7NMoa4W65qHgFZnw6dA+KUkMGY5k7R fvD7QyFX4LC3SmkUppqB =Ld2h -----END PGP SIGNATURE----- From thomas.oliveira at gmail.com Thu Jun 4 09:44:28 2015 From: thomas.oliveira at gmail.com (Thomas Oliveira) Date: Thu, 4 Jun 2015 14:44:28 +0100 Subject: [Paraview] Fwd: Problems in rendering when raw image is resized In-Reply-To: References: Message-ID: Dear Utkarsh, The solution you provided for the 2nd problem worked. Regarding the 1st problem, it has disappeared when I upgraded from 4.1.0 to 4.3.1. Thank you again, Thomas Oliveira On Sat, May 30, 2015 at 2:51 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > I am not entirely sure what 1 is. However, for 2, try changing the "Scalar > Opacity Unit Distance" from the "Properties" panel. ParaView will set it to > a value based on the data spacing after the first "Apply". If you change > the spacing after that, you can use the "Reset using current data values" > button next the option on the "Properties" panel to recompute using the > current data values. > > Utkarsh > > On Tue, May 26, 2015 at 7:29 AM Thomas Oliveira > wrote: > >> Hi, >> >> I have two problems that happen when setting the size of the voxels of a >> raw image. >> Do you have any idea about it, please? >> >> 1) When I import a 3D raw image, if I set the data spacing, i.e., the >> size of each voxel, to 1,1,1, I can correctly visualize and rotate the >> image. However, if I set the voxel size to the values I need >> (5.549E-6,5.549E-6,5.549E-6), the image is rendered as if clipped when >> turned to certain angles (please see picture thisShouldBeCuboid.png >> attached). >> >> 2) Another problem for the same image is that, if the data spacing is set >> to 1,1,1, I get a certain contrast between grey and white (size1.png). If >> it it set to 0.1,0.1,0.1, the grey color becomes whiter (size01.png). >> Finally, when it is set to the correct small size, it is completely white. >> >> Thank you for your help, >> >> Thomas Oliveira >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at seoaachen.de Thu Jun 4 10:59:06 2015 From: info at seoaachen.de (Daniel Zuidinga) Date: Thu, 04 Jun 2015 16:59:06 +0200 Subject: [Paraview] Paraviewweb and gpu Message-ID: <557067BA.60000@seoaachen.de> Hello, makes it a difference in performance if the webgl renderer is used on the clien is used and the server uses software instead gpu renderer? regards From scott.wittenburg at kitware.com Thu Jun 4 11:41:34 2015 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Thu, 4 Jun 2015 09:41:34 -0600 Subject: [Paraview] Paraviewweb and gpu In-Reply-To: <557067BA.60000@seoaachen.de> References: <557067BA.60000@seoaachen.de> Message-ID: Hi Daniel, Yes, there can be a difference in performance. When using local rendering in the paraviewweb client (either webgl or VGL, which is also based on webgl), the server delivers the geometry to the client to be rendered locally. This can be much faster as long as the geometry is not too large. In this case, it would not matter whether the server used software rendering instead of the GPU. Just be aware that this approach will not work when the geometry gets too large to fit in the client GPU memory all at once. Cheers, Scott On Thu, Jun 4, 2015 at 8:59 AM, Daniel Zuidinga wrote: > Hello, > > makes it a difference in performance if the webgl renderer is used on the > clien is used and the server uses software instead gpu renderer? > > regards > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Thu Jun 4 11:45:17 2015 From: burlen.loring at gmail.com (Burlen Loring) Date: Thu, 04 Jun 2015 08:45:17 -0700 Subject: [Paraview] save 'Surface LIC' as texture In-Reply-To: <0AD08F7A7F420048BE6681638DF90D8136BA0D24@MBX-W2.rwth-ad.de> References: <0AD08F7A7F420048BE6681638DF90D8136BA0D24@MBX-W2.rwth-ad.de> Message-ID: <5570728D.3060800@gmail.com> I think it could be done if you're willing to hack into PV. There is already some mechanism in there for sucking textures back from the gpu and writing them to disk for debugging. It's not exactly what you need but at least will illustrate pulling data from GPU. a potential issue with this idea is that the result from the LIC is very view dependent, you may be restricted to use same view settings in your app/blender. maybe better just to write the LIC shader in blender. On 06/04/2015 04:07 AM, G?bbert, Jens Henrik wrote: > Hello everyone, > > I am using ParaView for some time now and love its representation of > vector fields on surfaces by > 'SurfaceLIC' > (http://www.paraview.org/Wiki/ParaView/Line_Integral_Convolution). > > Beyond that, lots of other representations of scientific data are of > course simply great .... > > I would like to save this textures and the geometrie (incl. texture > coordinates) of the surface > to view it later in our own OpenGL virtual reality application (or > Blender). > > ParaView can load textures > (http://www.paraview.org/Wiki/ParaView:Texture), > but how can I save them ? > > Does anyone has an idea ... including source code modifications, which > might make things like that possible. > > Best, > Jens Henrik > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephen at orsatti.org Thu Jun 4 13:51:33 2015 From: stephen at orsatti.org (Stephen Orsatti) Date: Thu, 04 Jun 2015 17:51:33 +0000 Subject: [Paraview] Bulk conversion Message-ID: I am trying to convert multiple *.vtk files to *.stl files. Basically an object sequence (ie: surface_0001.vtk, surface_0002.vtk, etc...) Is there a way to automate this with Python. I've looked and looked and I can't find a way to do this. Please help. -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Thu Jun 4 14:24:13 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 4 Jun 2015 14:24:13 -0400 Subject: [Paraview] Bulk conversion In-Reply-To: References: Message-ID: Have you looked at ParaView's Python trace functionality? Information on that is at http://www.paraview.org/Wiki/Python_GUI_Tools. The idea is that you can create a Python script and then run pvpython or pvbatch to do what you want. Regards, Andy On Thu, Jun 4, 2015 at 1:51 PM, Stephen Orsatti wrote: > I am trying to convert multiple *.vtk files to *.stl files. Basically an > object sequence (ie: surface_0001.vtk, surface_0002.vtk, etc...) Is there a > way to automate this with Python. I've looked and looked and I can't find > a way to do this. Please help. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephen at orsatti.org Thu Jun 4 15:09:20 2015 From: stephen at orsatti.org (Stephen Orsatti) Date: Thu, 04 Jun 2015 19:09:20 +0000 Subject: [Paraview] Bulk conversion In-Reply-To: References: Message-ID: Hi Andy, Thanks for the info! Trace helped me to see how to import and export, but the thing I can't figure out is how to increment import and increment export. Blessings! "For what will it profit a man if he gains the whole world, and loses his own soul?" -Jesus Christ On Thu, Jun 4, 2015 at 1:24 PM, Andy Bauer wrote: > Have you looked at ParaView's Python trace functionality? Information on > that is at http://www.paraview.org/Wiki/Python_GUI_Tools. The idea is > that you can create a Python script and then run pvpython or pvbatch to do > what you want. > > Regards, > Andy > > On Thu, Jun 4, 2015 at 1:51 PM, Stephen Orsatti > wrote: > >> I am trying to convert multiple *.vtk files to *.stl files. Basically an >> object sequence (ie: surface_0001.vtk, surface_0002.vtk, etc...) Is there a >> way to automate this with Python. I've looked and looked and I can't find >> a way to do this. Please help. >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Jun 4 15:38:01 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 4 Jun 2015 19:38:01 +0000 Subject: [Paraview] FW: (ParaView) Length of a Spline (INC000001156537) In-Reply-To: <691061815.1538831433440039426.JavaMail.itsmprod@AS423SNLNT> References: <691061815.1538831433440039426.JavaMail.itsmprod@AS423SNLNT> Message-ID: <3939180caf304124b6e0d4b193444c8f@ES01AMSNLNT.srn.sandia.gov> A question from a customer: Hello, I'm wondering if ParaView has the capability to return the length of a curve or spline. Ideally, I would like to draw a spline on my geometry, and ParaView return the nodes that most closely resemble that spline. Then, I would like to plot the length of the spline vs. time. I guess this would be similar to the "plot over time" filter, just over a curved line instead. Thanks for the help. John Thanks, Alan From andy.bauer at kitware.com Thu Jun 4 15:59:44 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 4 Jun 2015 15:59:44 -0400 Subject: [Paraview] FW: (ParaView) Length of a Spline (INC000001156537) In-Reply-To: <3939180caf304124b6e0d4b193444c8f@ES01AMSNLNT.srn.sandia.gov> References: <691061815.1538831433440039426.JavaMail.itsmprod@AS423SNLNT> <3939180caf304124b6e0d4b193444c8f@ES01AMSNLNT.srn.sandia.gov> Message-ID: The Integrate Variables filter should work for that. I tested with Wavelet->Slice->Slice (with a different normal) ->Integrative Variables and got the expected value of 20 in the cell data length array. On Thu, Jun 4, 2015 at 3:38 PM, Scott, W Alan wrote: > A question from a customer: > > > > Hello, > > I'm wondering if ParaView has the capability to return the length of a > curve or spline. Ideally, I would like to draw a spline on my geometry, > and ParaView return the nodes that most closely resemble that spline. > Then, I would like to plot the length of the spline vs. time. I guess this > would be similar to the "plot over time" filter, just over a curved line > instead. > > Thanks for the help. > > John > > > Thanks, > > Alan > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From goebbert at vr.rwth-aachen.de Fri Jun 5 04:34:46 2015 From: goebbert at vr.rwth-aachen.de (=?iso-8859-1?Q?G=F6bbert=2C_Jens_Henrik?=) Date: Fri, 5 Jun 2015 08:34:46 +0000 Subject: [Paraview] save 'Surface LIC' as texture In-Reply-To: <5570728D.3060800@gmail.com> References: <0AD08F7A7F420048BE6681638DF90D8136BA0D24@MBX-W2.rwth-ad.de>, <5570728D.3060800@gmail.com> Message-ID: <0AD08F7A7F420048BE6681638DF90D8136BA148C@MBX-W2.rwth-ad.de> Hi Burlen, thanks for your answer. But somehow bad news for me :) I will try to add this feature than - it might help others, too. Can you give me some more hints where I can find this mechanism for sucking textures back from the gpu and perhaps even how to use it for debugging? Best Jens Henrik ________________________________ From: Burlen Loring [burlen.loring at gmail.com] Sent: Thursday, June 04, 2015 5:45 PM To: G?bbert, Jens Henrik; paraview at paraview.org Subject: Re: [Paraview] save 'Surface LIC' as texture I think it could be done if you're willing to hack into PV. There is already some mechanism in there for sucking textures back from the gpu and writing them to disk for debugging. It's not exactly what you need but at least will illustrate pulling data from GPU. a potential issue with this idea is that the result from the LIC is very view dependent, you may be restricted to use same view settings in your app/blender. maybe better just to write the LIC shader in blender. On 06/04/2015 04:07 AM, G?bbert, Jens Henrik wrote: Hello everyone, I am using ParaView for some time now and love its representation of vector fields on surfaces by 'SurfaceLIC' (http://www.paraview.org/Wiki/ParaView/Line_Integral_Convolution). Beyond that, lots of other representations of scientific data are of course simply great .... I would like to save this textures and the geometrie (incl. texture coordinates) of the surface to view it later in our own OpenGL virtual reality application (or Blender). ParaView can load textures (http://www.paraview.org/Wiki/ParaView:Texture), but how can I save them ? Does anyone has an idea ... including source code modifications, which might make things like that possible. Best, Jens Henrik _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Fri Jun 5 12:03:08 2015 From: burlen.loring at gmail.com (Burlen Loring) Date: Fri, 05 Jun 2015 09:03:08 -0700 Subject: [Paraview] save 'Surface LIC' as texture In-Reply-To: <0AD08F7A7F420048BE6681638DF90D8136BA148C@MBX-W2.rwth-ad.de> References: <0AD08F7A7F420048BE6681638DF90D8136BA0D24@MBX-W2.rwth-ad.de>, <5570728D.3060800@gmail.com> <0AD08F7A7F420048BE6681638DF90D8136BA148C@MBX-W2.rwth-ad.de> Message-ID: <5571C83C.2010003@gmail.com> cd into VTK/Rendering/OpenGL and grep for vtkTextureIO::Write, you'll find all the spots I was saving textures. There are some preprocessor macros to enable it. Good luck. On 6/5/2015 1:34 AM, G?bbert, Jens Henrik wrote: > Hi Burlen, > > thanks for your answer. > But somehow bad news for me :) > > I will try to add this feature than - it might help others, too. > Can you give me some more hints where I can find this mechanism for > sucking textures back from the gpu > and perhaps even how to use it for debugging? > > Best > Jens Henrik > > ------------------------------------------------------------------------ > *From:* Burlen Loring [burlen.loring at gmail.com] > *Sent:* Thursday, June 04, 2015 5:45 PM > *To:* G?bbert, Jens Henrik; paraview at paraview.org > *Subject:* Re: [Paraview] save 'Surface LIC' as texture > > I think it could be done if you're willing to hack into PV. There is > already some mechanism in there for sucking textures back from the gpu > and writing them to disk for debugging. It's not exactly what you need > but at least will illustrate pulling data from GPU. > > a potential issue with this idea is that the result from the LIC is > very view dependent, you may be restricted to use same view settings > in your app/blender. maybe better just to write the LIC shader in blender. > > On 06/04/2015 04:07 AM, G?bbert, Jens Henrik wrote: >> Hello everyone, >> >> I am using ParaView for some time now and love its representation of >> vector fields on surfaces by >> 'SurfaceLIC' >> (http://www.paraview.org/Wiki/ParaView/Line_Integral_Convolution). >> >> Beyond that, lots of other representations of scientific data are of >> course simply great .... >> >> I would like to save this textures and the geometrie (incl. texture >> coordinates) of the surface >> to view it later in our own OpenGL virtual reality application (or >> Blender). >> >> ParaView can load textures >> (http://www.paraview.org/Wiki/ParaView:Texture), >> but how can I save them ? >> >> Does anyone has an idea ... including source code modifications, >> which might make things like that possible. >> >> Best, >> Jens Henrik >> >> >> >> _______________________________________________ >> Powered bywww.kitware.com >> >> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >> >> Search the list archives at:http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pa at letnes.com Sat Jun 6 07:47:56 2015 From: pa at letnes.com (Paul Anton Letnes) Date: Sat, 6 Jun 2015 13:47:56 +0200 Subject: [Paraview] paraview for a "new" application Message-ID: Hi, fellow paraviewers! I?ve spent some time playing with tutorials and user manuals, and so far I?m impressed with what paraview can do. I am working on a specialized structural engineering program that, mainly, performs simulations of pipes with circular cross sections. Each pipe is split into nodes and 1D elements, and results are reported at points (or, less commonly, elements) along the pipe. Some results are reported once per cross section; e.g, the tension in the pipe has a single value for the entire cross section. Other results, e.g. plastic strain, is reported for a number of points along the circumference of the pipe (say, 5-50 points), for each of the cross sections. The results can be either ?snapshots? or time series. After what I?ve seen from the paraview documentation, possible approaches include: 1. Create a paraview plugin to read our current in-house file format. 2. Directly write output files in an already supported format. 3. Write pvpython scripts that perform the conversion on the fly. Approach 1 is probably a lot of work and the file format is not of interest to anyone else (optimally, I?d like to replace it), so this seems less attractive. Approach 3 is probably less user-friendly for our users. The second approach seems sensible, but the paraview documentation does not give many examples of how to do this. Optimally, I?d like to write a hdf5-based format (xdmf? netcdf? raw hdf5?) directly from Fortran, but I haven?t found documentation on how to do this. Using hdf5 seems attractive as it?s so widely supported by e.g. matlab, python, and other postprocessing tools used in the industry. Getting a single results database would simplify a lot of workflows! What would you guys do? Cheers Paul From teojgor at gmail.com Sat Jun 6 08:40:24 2015 From: teojgor at gmail.com (Teo Ioannis) Date: Sat, 6 Jun 2015 15:40:24 +0300 Subject: [Paraview] Xdmf Sample Files Message-ID: I would like to use the xdmf file format combined with hdf5 in order to output results of a finite element simulation with multiple timesteps. Can anyone supply any sample files for doing so? Is there a tutorial or a starting point to look? Thank you very much in advance. Theofilos Manitaras -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at bpi.cam.ac.uk Sat Jun 6 09:42:00 2015 From: chris at bpi.cam.ac.uk (Chris Richardson) Date: Sat, 06 Jun 2015 14:42:00 +0100 Subject: [Paraview] Xdmf Sample Files In-Reply-To: Message-ID: <234863aa-1d1a-4ace-bb8a-0378d21533e7@email.android.com> This is implemented in FEniCS (www.fenicsproject.org). I can post an example output, if that is useful... On 6 Jun 2015 13:40, Teo Ioannis wrote: > > I would like to use the xdmf file format combined with hdf5 in order to output results of a finite element simulation with multiple timesteps. Can anyone supply any sample files for doing so? Is there a tutorial or a starting point to look? Thank you very much in advance. > > Theofilos Manitaras From dan.lipsa at kitware.com Sat Jun 6 22:07:52 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Sun, 07 Jun 2015 02:07:52 +0000 Subject: [Paraview] paraview for a "new" application In-Reply-To: References: Message-ID: Hi Paul, Indeed #2 makes sense, especially if you want to change the in-house format. To write the file (from the simulation) it seems to me you should checkout https://www.hdfgroup.org/HDF5/doc/fortran/index.html I don't see why ParaView would be used in that process. Am I missing something? Dan On Sat, Jun 6, 2015 at 8:04 AM Paul Anton Letnes wrote: > Hi, fellow paraviewers! > > I?ve spent some time playing with tutorials and user manuals, and so far > I?m impressed with what paraview can do. > > I am working on a specialized structural engineering program that, mainly, > performs simulations of pipes with circular cross sections. Each pipe is > split into nodes and 1D elements, and results are reported at points (or, > less commonly, elements) along the pipe. > > Some results are reported once per cross section; e.g, the tension in the > pipe has a single value for the entire cross section. Other results, e.g. > plastic strain, is reported for a number of points along the circumference > of the pipe (say, 5-50 points), for each of the cross sections. The results > can be either ?snapshots? or time series. > > After what I?ve seen from the paraview documentation, possible approaches > include: > 1. Create a paraview plugin to read our current in-house file format. > 2. Directly write output files in an already supported format. > 3. Write pvpython scripts that perform the conversion on the fly. > > Approach 1 is probably a lot of work and the file format is not of > interest to anyone else (optimally, I?d like to replace it), so this seems > less attractive. Approach 3 is probably less user-friendly for our users. > > The second approach seems sensible, but the paraview documentation does > not give many examples of how to do this. Optimally, I?d like to write a > hdf5-based format (xdmf? netcdf? raw hdf5?) directly from Fortran, but I > haven?t found documentation on how to do this. Using hdf5 seems attractive > as it?s so widely supported by e.g. matlab, python, and other > postprocessing tools used in the industry. Getting a single results > database would simplify a lot of workflows! > > What would you guys do? > > Cheers > Paul > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From haonrolyat at gmail.com Sat Jun 6 23:44:44 2015 From: haonrolyat at gmail.com (Noah Taylor) Date: Sat, 6 Jun 2015 21:44:44 -0600 Subject: [Paraview] ParaView 4.0.1 Not Compiling for Python, MPI, Llvm Message-ID: Hello, I've been trying to compile this for a couple of weeks now but am running into some unknown troubles. My build gets to ~50% and kicks out an error as follows: collect2: error: ld returned 1 exit status make[2]: *** [lib/libvtkRenderingOpenGL-pv4.0.so.1] Error 1 make[1]: *** [VTK/Rendering/OpenGL/CMakeFiles/vtkRenderingOpenGL.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... I tried locating the libvtkRenderingOpenGL-pv4.0.so.1 and it wasn't anywhere on my machine and I have googled this library but I cannot find a solution. My ccmake options are as follows (I'm just trying to compile on a ubuntu aws node): BUILD_DOCUMENTATION OFF BUILD_EXAMPLES OFF BUILD_SHARED_LIBS ON BUILD_TESTING ON CMAKE_BUILD_TYPE Debug CMAKE_INSTALL_PREFIX /usr/local GMVReader_GMVREAD_LIB_DIR /mnt/ParaView-v4.0.1-source/Utilities/VisItBridge/databases/GMV GMVReader_SKIP_DATARANGE_CALCU OFF MPI_C_INCLUDE_PATH /usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi MPI_C_LIBRARIES /usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so PARAVIEW_BUILD_QT_GUI OFF PARAVIEW_DATA_ROOT PARAVIEW_DATA_ROOT-NOTFOUND PARAVIEW_ENABLE_CATALYST ON PARAVIEW_ENABLE_FFMPEG OFF PARAVIEW_ENABLE_PYTHON ON PARAVIEW_ENABLE_QT_SUPPORT OFF PARAVIEW_INSTALL_DEVELOPMENT_F OFF PARAVIEW_USE_MPI ON PARAVIEW_USE_PISTON OFF PARAVIEW_USE_VISITBRIDGE OFF VTK_Group_Tk OFF XDMF_USE_BZIP2 OFF XDMF_USE_GZIP OFF Do I need to specifiy a path somewhere? comment something out somewhere? Turn on another option in the CMake options? Any help would be appreciated :) Noah -------------- next part -------------- An HTML attachment was scrubbed... URL: From pa at letnes.com Sun Jun 7 04:26:53 2015 From: pa at letnes.com (Paul Anton Letnes) Date: Sun, 7 Jun 2015 10:26:53 +0200 Subject: [Paraview] paraview for a "new" application In-Reply-To: References: Message-ID: <280CD6CF-2E16-4390-8670-89A006311356@letnes.com> Hi Dan! I?m familiar with the HDF5 library and documentation, but thanks anyway for the link. I don?t see how I can have ParaView read and understand HDF5 files. That is, there are several readers (e.g. H5Nimrod) that use HDF5 as the underlying format, but I don?t see how to get paraview to understand which arrays are coordinates (nodes?), which are results, etc. for my application. Perhaps I should stress again that I have limited experience with ParaView, and since the supported file formats and possibilities seem endless, I have trouble getting an overview of sensible choices. My preference for hdf5 is partly due to other software in my organization supporting this format, and my own familiarity with it. Paul > On 7. jun. 2015, at 04.07, Dan Lipsa wrote: > > Hi Paul, > Indeed #2 makes sense, especially if you want to change the in-house format. To write the file (from the simulation) it seems to me you should checkout > > https://www.hdfgroup.org/HDF5/doc/fortran/index.html > > I don't see why ParaView would be used in that process. Am I missing something? > Dan > > > > On Sat, Jun 6, 2015 at 8:04 AM Paul Anton Letnes wrote: > Hi, fellow paraviewers! > > I?ve spent some time playing with tutorials and user manuals, and so far I?m impressed with what paraview can do. > > I am working on a specialized structural engineering program that, mainly, performs simulations of pipes with circular cross sections. Each pipe is split into nodes and 1D elements, and results are reported at points (or, less commonly, elements) along the pipe. > > Some results are reported once per cross section; e.g, the tension in the pipe has a single value for the entire cross section. Other results, e.g. plastic strain, is reported for a number of points along the circumference of the pipe (say, 5-50 points), for each of the cross sections. The results can be either ?snapshots? or time series. > > After what I?ve seen from the paraview documentation, possible approaches include: > 1. Create a paraview plugin to read our current in-house file format. > 2. Directly write output files in an already supported format. > 3. Write pvpython scripts that perform the conversion on the fly. > > Approach 1 is probably a lot of work and the file format is not of interest to anyone else (optimally, I?d like to replace it), so this seems less attractive. Approach 3 is probably less user-friendly for our users. > > The second approach seems sensible, but the paraview documentation does not give many examples of how to do this. Optimally, I?d like to write a hdf5-based format (xdmf? netcdf? raw hdf5?) directly from Fortran, but I haven?t found documentation on how to do this. Using hdf5 seems attractive as it?s so widely supported by e.g. matlab, python, and other postprocessing tools used in the industry. Getting a single results database would simplify a lot of workflows! > > What would you guys do? > > Cheers > Paul > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From goebbert at vr.rwth-aachen.de Sun Jun 7 15:21:45 2015 From: goebbert at vr.rwth-aachen.de (=?iso-8859-1?Q?G=F6bbert=2C_Jens_Henrik?=) Date: Sun, 7 Jun 2015 19:21:45 +0000 Subject: [Paraview] save 'Surface LIC' as texture In-Reply-To: <5571C83C.2010003@gmail.com> References: <0AD08F7A7F420048BE6681638DF90D8136BA0D24@MBX-W2.rwth-ad.de>, <5570728D.3060800@gmail.com> <0AD08F7A7F420048BE6681638DF90D8136BA148C@MBX-W2.rwth-ad.de>, <5571C83C.2010003@gmail.com> Message-ID: <0AD08F7A7F420048BE6681638DF90D8136BA2E30@MBX-W2.rwth-ad.de> Hi Burlen, thanks a lot. I found the spots. Best Jens Henrik P.S: if someone else searches for them, look here: https://gitlab.kitware.com/vtk/vtk/blob/master/Rendering/LIC/vtkSurfaceLICPainter.cxx line 2693 ________________________________ From: Burlen Loring [burlen.loring at gmail.com] Sent: Friday, June 05, 2015 6:03 PM To: G?bbert, Jens Henrik; paraview at paraview.org Subject: Re: [Paraview] save 'Surface LIC' as texture cd into VTK/Rendering/OpenGL and grep for vtkTextureIO::Write, you'll find all the spots I was saving textures. There are some preprocessor macros to enable it. Good luck. On 6/5/2015 1:34 AM, G?bbert, Jens Henrik wrote: Hi Burlen, thanks for your answer. But somehow bad news for me :) I will try to add this feature than - it might help others, too. Can you give me some more hints where I can find this mechanism for sucking textures back from the gpu and perhaps even how to use it for debugging? Best Jens Henrik ________________________________ From: Burlen Loring [burlen.loring at gmail.com] Sent: Thursday, June 04, 2015 5:45 PM To: G?bbert, Jens Henrik; paraview at paraview.org Subject: Re: [Paraview] save 'Surface LIC' as texture I think it could be done if you're willing to hack into PV. There is already some mechanism in there for sucking textures back from the gpu and writing them to disk for debugging. It's not exactly what you need but at least will illustrate pulling data from GPU. a potential issue with this idea is that the result from the LIC is very view dependent, you may be restricted to use same view settings in your app/blender. maybe better just to write the LIC shader in blender. On 06/04/2015 04:07 AM, G?bbert, Jens Henrik wrote: Hello everyone, I am using ParaView for some time now and love its representation of vector fields on surfaces by 'SurfaceLIC' (http://www.paraview.org/Wiki/ParaView/Line_Integral_Convolution). Beyond that, lots of other representations of scientific data are of course simply great .... I would like to save this textures and the geometrie (incl. texture coordinates) of the surface to view it later in our own OpenGL virtual reality application (or Blender). ParaView can load textures (http://www.paraview.org/Wiki/ParaView:Texture), but how can I save them ? Does anyone has an idea ... including source code modifications, which might make things like that possible. Best, Jens Henrik _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Sun Jun 7 15:40:31 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Sun, 07 Jun 2015 19:40:31 +0000 Subject: [Paraview] paraview for a "new" application In-Reply-To: <280CD6CF-2E16-4390-8670-89A006311356@letnes.com> References: <280CD6CF-2E16-4390-8670-89A006311356@letnes.com> Message-ID: You are right, ParaView does not read hdf5 directly but rather hdf5 based formats (hdf5 + additional info): both netcdf and xdmf have readers. You can get a list of all readers supported by your ParaView installation using Help in ParaView. Additional readers can be enabled with compile time options. You can write Xdmf data using vtkXdmfWriter or vtkXdm3Writer (you'll have to link with the VTK library). These writers have tests which is a good way to see an example of how to use the class. You can also take a look at the VTK XML based formats: vtkXMLPolyDataWriter, vtkXMLImageDataWriter, vtkXMLUnstructuredGridWriter/Reader. Probably you could write data with a library that comes with that format and then read it with ParaView. Do you need parallel writing/reading? Dan On Sun, Jun 7, 2015 at 4:26 AM Paul Anton Letnes wrote: > Hi Dan! > > I?m familiar with the HDF5 library and documentation, but thanks anyway > for the link. > > I don?t see how I can have ParaView read and understand HDF5 files. That > is, there are several readers (e.g. H5Nimrod) that use HDF5 as the > underlying format, but I don?t see how to get paraview to understand which > arrays are coordinates (nodes?), which are results, etc. for my application. > > Perhaps I should stress again that I have limited experience with > ParaView, and since the supported file formats and possibilities seem > endless, I have trouble getting an overview of sensible choices. > > My preference for hdf5 is partly due to other software in my organization > supporting this format, and my own familiarity with it. > > Paul > > > On 7. jun. 2015, at 04.07, Dan Lipsa wrote: > > > > Hi Paul, > > Indeed #2 makes sense, especially if you want to change the in-house > format. To write the file (from the simulation) it seems to me you should > checkout > > > > https://www.hdfgroup.org/HDF5/doc/fortran/index.html > > > > I don't see why ParaView would be used in that process. Am I missing > something? > > Dan > > > > > > > > On Sat, Jun 6, 2015 at 8:04 AM Paul Anton Letnes wrote: > > Hi, fellow paraviewers! > > > > I?ve spent some time playing with tutorials and user manuals, and so far > I?m impressed with what paraview can do. > > > > I am working on a specialized structural engineering program that, > mainly, performs simulations of pipes with circular cross sections. Each > pipe is split into nodes and 1D elements, and results are reported at > points (or, less commonly, elements) along the pipe. > > > > Some results are reported once per cross section; e.g, the tension in > the pipe has a single value for the entire cross section. Other results, > e.g. plastic strain, is reported for a number of points along the > circumference of the pipe (say, 5-50 points), for each of the cross > sections. The results can be either ?snapshots? or time series. > > > > After what I?ve seen from the paraview documentation, possible > approaches include: > > 1. Create a paraview plugin to read our current in-house file format. > > 2. Directly write output files in an already supported format. > > 3. Write pvpython scripts that perform the conversion on the fly. > > > > Approach 1 is probably a lot of work and the file format is not of > interest to anyone else (optimally, I?d like to replace it), so this seems > less attractive. Approach 3 is probably less user-friendly for our users. > > > > The second approach seems sensible, but the paraview documentation does > not give many examples of how to do this. Optimally, I?d like to write a > hdf5-based format (xdmf? netcdf? raw hdf5?) directly from Fortran, but I > haven?t found documentation on how to do this. Using hdf5 seems attractive > as it?s so widely supported by e.g. matlab, python, and other > postprocessing tools used in the industry. Getting a single results > database would simplify a lot of workflows! > > > > What would you guys do? > > > > Cheers > > Paul > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dkxls23 at gmail.com Mon Jun 8 05:27:18 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Mon, 08 Jun 2015 12:27:18 +0300 Subject: [Paraview] paraview for a "new" application In-Reply-To: References: <280CD6CF-2E16-4390-8670-89A006311356@letnes.com> Message-ID: <55755FF6.9060901@gmail.com> Hi Paul, as you and Dan already stated, the HDF5 format is a very good choice to write out large datasets. I usually write the HDF5 files directly from my simulation codes and generate a XDMF file afterwards. The actual XDMF file contains just the meta data in XML format [1] and this can be tailored to your application/dataset (I use python with h5py and xml.etree to do this). Hence, my simulation codes (written in C++) only depend on the HDF5 libraries. Eventually, this will enable you to store your data in a robust, flexible and portable file format. For more complex setups I would also consider using the VTK libraries to handle the data IO as Dan suggested. -Armin [1] http://www.xdmf.org/index.php/XDMF_Model_and_Format On 06/07/2015 10:40 PM, Dan Lipsa wrote: > You are right, ParaView does not read hdf5 directly but rather hdf5 > based formats (hdf5 + additional info): both netcdf and xdmf have readers. > You can get a list of all readers supported by your ParaView > installation using Help in ParaView. Additional readers can be enabled with > compile time options. > > You can write Xdmf data using vtkXdmfWriter or vtkXdm3Writer (you'll > have to link with the VTK library). These writers have tests which is a > good way to see an example of how to use the class. You can also take a > look at the VTK XML based formats: vtkXMLPolyDataWriter, > vtkXMLImageDataWriter, vtkXMLUnstructuredGridWriter/Reader. Probably you > could write data with a library that comes with that format and then > read it with ParaView. > > Do you need parallel writing/reading? > > Dan > > > > > On Sun, Jun 7, 2015 at 4:26 AM Paul Anton Letnes > wrote: > > Hi Dan! > > I?m familiar with the HDF5 library and documentation, but thanks > anyway for the link. > > I don?t see how I can have ParaView read and understand HDF5 files. > That is, there are several readers (e.g. H5Nimrod) that use HDF5 as > the underlying format, but I don?t see how to get paraview to > understand which arrays are coordinates (nodes?), which are results, > etc. for my application. > > Perhaps I should stress again that I have limited experience with > ParaView, and since the supported file formats and possibilities > seem endless, I have trouble getting an overview of sensible choices. > > My preference for hdf5 is partly due to other software in my > organization supporting this format, and my own familiarity with it. > > Paul > > > On 7. jun. 2015, at 04.07, Dan Lipsa > wrote: > > > > Hi Paul, > > Indeed #2 makes sense, especially if you want to change the > in-house format. To write the file (from the simulation) it seems to > me you should checkout > > > > https://www.hdfgroup.org/HDF5/doc/fortran/index.html > > > > I don't see why ParaView would be used in that process. Am I > missing something? > > Dan > > > > > > > > On Sat, Jun 6, 2015 at 8:04 AM Paul Anton Letnes > wrote: > > Hi, fellow paraviewers! > > > > I?ve spent some time playing with tutorials and user manuals, and > so far I?m impressed with what paraview can do. > > > > I am working on a specialized structural engineering program > that, mainly, performs simulations of pipes with circular cross > sections. Each pipe is split into nodes and 1D elements, and results > are reported at points (or, less commonly, elements) along the pipe. > > > > Some results are reported once per cross section; e.g, the > tension in the pipe has a single value for the entire cross section. > Other results, e.g. plastic strain, is reported for a number of > points along the circumference of the pipe (say, 5-50 points), for > each of the cross sections. The results can be either ?snapshots? or > time series. > > > > After what I?ve seen from the paraview documentation, possible > approaches include: > > 1. Create a paraview plugin to read our current in-house file format. > > 2. Directly write output files in an already supported format. > > 3. Write pvpython scripts that perform the conversion on the fly. > > > > Approach 1 is probably a lot of work and the file format is not > of interest to anyone else (optimally, I?d like to replace it), so > this seems less attractive. Approach 3 is probably less > user-friendly for our users. > > > > The second approach seems sensible, but the paraview > documentation does not give many examples of how to do this. > Optimally, I?d like to write a hdf5-based format (xdmf? netcdf? raw > hdf5?) directly from Fortran, but I haven?t found documentation on > how to do this. Using hdf5 seems attractive as it?s so widely > supported by e.g. matlab, python, and other postprocessing tools > used in the industry. Getting a single results database would > simplify a lot of workflows! > > > > What would you guys do? > > > > Cheers > > Paul > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From stefano.zaghi at gmail.com Mon Jun 8 05:49:30 2015 From: stefano.zaghi at gmail.com (Stefano Zaghi) Date: Mon, 8 Jun 2015 11:49:30 +0200 Subject: [Paraview] paraview for a "new" application In-Reply-To: <55755FF6.9060901@gmail.com> References: <280CD6CF-2E16-4390-8670-89A006311356@letnes.com> <55755FF6.9060901@gmail.com> Message-ID: Hi all, another possibility is to write your Fortran data directly into VTK files format. I develop a KISS library in pure Fortran for IO of Fortran data into VTK standard: see https://github.com/szaghi/Lib_VTK_IO The exporters are almost complete. The importers are under developing by a power collaborator https://github.com/victorsndvg/Lib_VTK_IO this work will be merged very soon into the main branch. Summarizing, Lib_VTK_IO is + Lib_VTK_IO is a pure Fortran library to write and read data conforming the VTK standard; + Lib_VTK_IO is Fortran 2003+ standard compliant; + Lib_VTK_IO supports parallel architectures by means OpenMP and MPI paradigms; + Lib_VTK_IO supports ascii, binary and base64 file formats; + Lib_VTK_IO is a Free, Open Source Project. My best regards Stefano Zaghi Ph.D. Aerospace Engineer Research Scientist, Dept. of Computational Hydrodynamics at *CNR-INSEAN* *p*: +39 0650299260 | *m*: +39 3497730036 | *e*: stefano.zaghi at gmail.com Codes Showcase *OFF* Open source Finite volumes Fluid dynamics code *Lib_VTK_IO * Fortran library to write and read data conforming the VTK standard *FLAP* Fortran command Line Arguments Parser for poor men *BeFoR64 * Base64 encoding/decoding library for FoRtran poor men *FiNeR * Fortran INI ParseR and generator for FoRtran poor men *IR_Precision * Fortran (standard 2003) module to develop portable codes *FoBis.py* Fortran Building System for poor men *PreForM.py * Preprocessor for Fortran poor men *MaTiSSe.py* Markdown To Impressive Scientific Slides On Mon, Jun 8, 2015 at 11:27 AM, Armin Wehrfritz wrote: > Hi Paul, > > as you and Dan already stated, the HDF5 format is a very good choice to > write out large datasets. > > I usually write the HDF5 files directly from my simulation codes and > generate a XDMF file afterwards. > The actual XDMF file contains just the meta data in XML format [1] and > this can be tailored to your application/dataset (I use python with h5py > and xml.etree to do this). > Hence, my simulation codes (written in C++) only depend on the HDF5 > libraries. > > Eventually, this will enable you to store your data in a robust, flexible > and portable file format. > > For more complex setups I would also consider using the VTK libraries to > handle the data IO as Dan suggested. > > -Armin > > [1] http://www.xdmf.org/index.php/XDMF_Model_and_Format > > > > > On 06/07/2015 10:40 PM, Dan Lipsa wrote: > >> You are right, ParaView does not read hdf5 directly but rather hdf5 >> based formats (hdf5 + additional info): both netcdf and xdmf have >> readers. >> You can get a list of all readers supported by your ParaView >> installation using Help in ParaView. Additional readers can be enabled >> with >> compile time options. >> >> You can write Xdmf data using vtkXdmfWriter or vtkXdm3Writer (you'll >> have to link with the VTK library). These writers have tests which is a >> good way to see an example of how to use the class. You can also take a >> look at the VTK XML based formats: vtkXMLPolyDataWriter, >> vtkXMLImageDataWriter, vtkXMLUnstructuredGridWriter/Reader. Probably you >> could write data with a library that comes with that format and then >> read it with ParaView. >> >> Do you need parallel writing/reading? >> >> Dan >> >> >> >> >> On Sun, Jun 7, 2015 at 4:26 AM Paul Anton Letnes > > wrote: >> >> Hi Dan! >> >> I?m familiar with the HDF5 library and documentation, but thanks >> anyway for the link. >> >> I don?t see how I can have ParaView read and understand HDF5 files. >> That is, there are several readers (e.g. H5Nimrod) that use HDF5 as >> the underlying format, but I don?t see how to get paraview to >> understand which arrays are coordinates (nodes?), which are results, >> etc. for my application. >> >> Perhaps I should stress again that I have limited experience with >> ParaView, and since the supported file formats and possibilities >> seem endless, I have trouble getting an overview of sensible choices. >> >> My preference for hdf5 is partly due to other software in my >> organization supporting this format, and my own familiarity with it. >> >> Paul >> >> > On 7. jun. 2015, at 04.07, Dan Lipsa > > wrote: >> > >> > Hi Paul, >> > Indeed #2 makes sense, especially if you want to change the >> in-house format. To write the file (from the simulation) it seems to >> me you should checkout >> > >> > https://www.hdfgroup.org/HDF5/doc/fortran/index.html >> > >> > I don't see why ParaView would be used in that process. Am I >> missing something? >> > Dan >> > >> > >> > >> > On Sat, Jun 6, 2015 at 8:04 AM Paul Anton Letnes > > wrote: >> > Hi, fellow paraviewers! >> > >> > I?ve spent some time playing with tutorials and user manuals, and >> so far I?m impressed with what paraview can do. >> > >> > I am working on a specialized structural engineering program >> that, mainly, performs simulations of pipes with circular cross >> sections. Each pipe is split into nodes and 1D elements, and results >> are reported at points (or, less commonly, elements) along the pipe. >> > >> > Some results are reported once per cross section; e.g, the >> tension in the pipe has a single value for the entire cross section. >> Other results, e.g. plastic strain, is reported for a number of >> points along the circumference of the pipe (say, 5-50 points), for >> each of the cross sections. The results can be either ?snapshots? or >> time series. >> > >> > After what I?ve seen from the paraview documentation, possible >> approaches include: >> > 1. Create a paraview plugin to read our current in-house file >> format. >> > 2. Directly write output files in an already supported format. >> > 3. Write pvpython scripts that perform the conversion on the fly. >> > >> > Approach 1 is probably a lot of work and the file format is not >> of interest to anyone else (optimally, I?d like to replace it), so >> this seems less attractive. Approach 3 is probably less >> user-friendly for our users. >> > >> > The second approach seems sensible, but the paraview >> documentation does not give many examples of how to do this. >> Optimally, I?d like to write a hdf5-based format (xdmf? netcdf? raw >> hdf5?) directly from Fortran, but I haven?t found documentation on >> how to do this. Using hdf5 seems attractive as it?s so widely >> supported by e.g. matlab, python, and other postprocessing tools >> used in the industry. Getting a single results database would >> simplify a lot of workflows! >> > >> > What would you guys do? >> > >> > Cheers >> > Paul >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> > >> > Search the list archives at: >> http://markmail.org/search/?q=ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From peter at peterheppel.com Mon Jun 8 04:41:47 2015 From: peter at peterheppel.com (Peter) Date: Mon, 08 Jun 2015 10:41:47 +0200 Subject: [Paraview] pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0 Message-ID: <2472eac00192db409732acc78488eb55@peterheppel.com> Hello Here's a ParaView Catalyst problem that may be related to bug (0027323). O/S is ubuntu 14.04 lts - 64 bit I'd like to connect to a Catalyst-enabled simulation, so first I'm running the example code. I do this: 1) download ParaView-v4.3.1-source and build. The ccmake settings are below. 2) download ParaViewCatalystExampleCode-master and build. The ccmake settings are below. 3) run ctest in ParaViewCatalystExampleCode-master/Build - 100% pass 4) run paraview (Build/bin/paraview &), menu Catalyst>Connect -take port 22222 dismiss the Ready for Catalyst connections dialog 4) in any of the ParaViewCatalystExampleCode-master scripts, I change coprocessor.EnableLiveVisualization to (True) and run the test. paraview crashes with Invalid output port : pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0 (...ParaView-v4.3.1-source/Qt/Core/pqPipelineSource.cxx:240, pqOutputPort* pqPipelineSource::getOutputPort(int) const) I've tried with different port numbers, with PV built as debug, as release, with qt4, with qt5, with and without the intel compiler environment( because it supplies its own MPI) Any suggestions, anyone? Thanks ccmake screen for ParaViewCatalystExampleCode-master ----------------------------------------------------- BUILD TESTING ON CMAKE_BUILD_TYPE Release CMAKE_INSTALL_PREFIX /usr/local ParaView_DIR /home/r3/software/ParaView-v4.3.1-source/Build QT_QMAKE_EXECUTABLE /usr/bin/qmake-qt4 Qt5Core_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Core Qt5Gui_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui USE_CATALYST ON ccmake screen for ParaView-v4.3.1-source ----------------------------------------- BUILD_DOCUMENTATION OFF BUILD_EXAMPLES ON BUILD_SHARED_LIBS ON BUILD_TESTING ON BUILD_USER_DEFINED_LIBS OFF CMAKE_BUILD_TYPE Release CMAKE_INSTALL_PREFIX /usr/local CTEST_TEST_TIMEOUT 3600 GMVReader_GMVREAD_LIB_DIR /home/r3/software/ParaView-v4.3.1-source/Utilities/VisItBridge/databases/GMV GMVReader_SKIP_DATARANGE_CALCU OFF MPI_C_INCLUDE_PATH /usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi MPI_C_LIBRARIES /usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so PARAVIEW_BUILD_QT_GUI ON PARAVIEW_ENABLE_CATALYST ON PARAVIEW_ENABLE_FFMPEG OFF PARAVIEW_ENABLE_PYTHON ON PARAVIEW_INSTALL_DEVELOPMENT_F OFF PARAVIEW_USE_DAX OFF PARAVIEW_USE_MPI ON PARAVIEW_USE_PISTON OFF PARAVIEW_USE_UNIFIED_BINDINGS OFF PARAVIEW_USE_VISITBRIDGE OFF Qt5Core_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Core Qt5Designer_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Designer Qt5Gui_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui Qt5Help_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Help Qt5Network_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Network Qt5PrintSupport_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5PrintSupport Qt5Test_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Test Qt5UiTools_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5UiTools Qt5Widgets_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Widgets Qt5Xml_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Xml SURFACELIC_PLUGIN_TESTING ON VTK_PYTHON_VERSION 2 VTK_RENDERING_BACKEND OpenGL VTK_SMP_IMPLEMENTATION_TYPE Sequential VTK_USE_LARGE_DATA OFF XDMF_USE_BZIP2 OFF XDMF_USE_GZIP OFF -- Peter Heppel 35/37 Rue de Locmalo 56290 Port-Louis France +33 6 81 30 76 52 cell +33 2 97 82 19 30 USA +1 773 280 8142 Skype: peterheppel From u.utku.turuncoglu at be.itu.edu.tr Mon Jun 8 06:45:02 2015 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Mon, 8 Jun 2015 13:45:02 +0300 (EEST) Subject: [Paraview] pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0 In-Reply-To: <2472eac00192db409732acc78488eb55@peterheppel.com> References: <2472eac00192db409732acc78488eb55@peterheppel.com> Message-ID: <60384.88.235.36.106.1433760302.squirrel@webmail.be.itu.edu.tr> Hi, I have also same problem in Mac OS 10.10 + python (framework) + OpenMPI (compiled with gnu compilers). I compiled both ParaView 4.3.1 and also 4.2.0 from the source but after running Catalyst Examples i am getting same port error. I might help to found the source of the problem. Regards, --ufuk > Hello > > Here's a ParaView Catalyst problem that may be related to bug (0027323). > O/S is ubuntu 14.04 lts - 64 bit > I'd like to connect to a Catalyst-enabled simulation, so first I'm > running the example code. > > > I do this: > 1) download ParaView-v4.3.1-source and build. The ccmake settings are > below. > 2) download ParaViewCatalystExampleCode-master and build. The ccmake > settings are below. > > 3) run ctest in ParaViewCatalystExampleCode-master/Build - 100% pass > > 4) run paraview (Build/bin/paraview &), > menu Catalyst>Connect -take port 22222 > dismiss the Ready for Catalyst connections dialog > > 4) in any of the ParaViewCatalystExampleCode-master scripts, I change > coprocessor.EnableLiveVisualization to (True) and run the test. > > paraview crashes with > Invalid output port : pqPipelineSource::getOutputPort( 0 ). Available > number of output ports: 0 > (...ParaView-v4.3.1-source/Qt/Core/pqPipelineSource.cxx:240, > pqOutputPort* pqPipelineSource::getOutputPort(int) const) > > > I've tried with different port numbers, with PV built as debug, as > release, with qt4, with qt5, with and without the intel compiler > environment( because it supplies its own MPI) > > Any suggestions, anyone? > > Thanks > > > > ccmake screen for ParaViewCatalystExampleCode-master > ----------------------------------------------------- > BUILD TESTING ON > CMAKE_BUILD_TYPE Release > CMAKE_INSTALL_PREFIX /usr/local > ParaView_DIR > /home/r3/software/ParaView-v4.3.1-source/Build > QT_QMAKE_EXECUTABLE /usr/bin/qmake-qt4 > Qt5Core_DIR > /usr/lib/x86_64-linux-gnu/cmake/Qt5Core > Qt5Gui_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui > USE_CATALYST ON > > > ccmake screen for ParaView-v4.3.1-source > ----------------------------------------- > > BUILD_DOCUMENTATION OFF > BUILD_EXAMPLES ON > BUILD_SHARED_LIBS ON > BUILD_TESTING ON > BUILD_USER_DEFINED_LIBS OFF > CMAKE_BUILD_TYPE Release > CMAKE_INSTALL_PREFIX /usr/local > CTEST_TEST_TIMEOUT 3600 > GMVReader_GMVREAD_LIB_DIR > /home/r3/software/ParaView-v4.3.1-source/Utilities/VisItBridge/databases/GMV > GMVReader_SKIP_DATARANGE_CALCU OFF > MPI_C_INCLUDE_PATH > /usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi > MPI_C_LIBRARIES > /usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so > PARAVIEW_BUILD_QT_GUI ON > PARAVIEW_ENABLE_CATALYST ON > PARAVIEW_ENABLE_FFMPEG OFF > PARAVIEW_ENABLE_PYTHON ON > PARAVIEW_INSTALL_DEVELOPMENT_F OFF > PARAVIEW_USE_DAX OFF > PARAVIEW_USE_MPI ON > PARAVIEW_USE_PISTON OFF > PARAVIEW_USE_UNIFIED_BINDINGS OFF > PARAVIEW_USE_VISITBRIDGE OFF > Qt5Core_DIR > /usr/lib/x86_64-linux-gnu/cmake/Qt5Core > Qt5Designer_DIR > /usr/lib/x86_64-linux-gnu/cmake/Qt5Designer > Qt5Gui_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui > Qt5Help_DIR > /usr/lib/x86_64-linux-gnu/cmake/Qt5Help > Qt5Network_DIR > /usr/lib/x86_64-linux-gnu/cmake/Qt5Network > Qt5PrintSupport_DIR > /usr/lib/x86_64-linux-gnu/cmake/Qt5PrintSupport > Qt5Test_DIR > /usr/lib/x86_64-linux-gnu/cmake/Qt5Test > Qt5UiTools_DIR > /usr/lib/x86_64-linux-gnu/cmake/Qt5UiTools > Qt5Widgets_DIR > /usr/lib/x86_64-linux-gnu/cmake/Qt5Widgets > Qt5Xml_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Xml > SURFACELIC_PLUGIN_TESTING ON > VTK_PYTHON_VERSION 2 > VTK_RENDERING_BACKEND OpenGL > VTK_SMP_IMPLEMENTATION_TYPE Sequential > VTK_USE_LARGE_DATA OFF > XDMF_USE_BZIP2 OFF > XDMF_USE_GZIP OFF > > -- > Peter Heppel > 35/37 Rue de Locmalo > 56290 Port-Louis > France > +33 6 81 30 76 52 cell > +33 2 97 82 19 30 > USA +1 773 280 8142 > Skype: peterheppel > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From chris at bpi.cam.ac.uk Mon Jun 8 07:06:47 2015 From: chris at bpi.cam.ac.uk (Chris Richardson) Date: Mon, 08 Jun 2015 12:06:47 +0100 Subject: [Paraview] Xdmf Sample Files Message-ID: <11d3ad76aae1222b4e431d6d6072f398@cam.ac.uk> On 06/06/2015 14:47, Teo Ioannis wrote: > An example output would be very helpful. > Here is an example with 10 time-steps, on a fixed triangular mesh. a.h5:/Mesh/0/topology a.h5:/Mesh/0/coordinates a.h5:/VisualisationVector/0 a.h5:/Mesh/0/topology a.h5:/Mesh/0/coordinates a.h5:/VisualisationVector/1 a.h5:/Mesh/0/topology a.h5:/Mesh/0/coordinates a.h5:/VisualisationVector/2 a.h5:/Mesh/0/topology a.h5:/Mesh/0/coordinates a.h5:/VisualisationVector/3 a.h5:/Mesh/0/topology a.h5:/Mesh/0/coordinates a.h5:/VisualisationVector/4 a.h5:/Mesh/0/topology a.h5:/Mesh/0/coordinates a.h5:/VisualisationVector/5 a.h5:/Mesh/0/topology a.h5:/Mesh/0/coordinates a.h5:/VisualisationVector/6 a.h5:/Mesh/0/topology a.h5:/Mesh/0/coordinates a.h5:/VisualisationVector/7 a.h5:/Mesh/0/topology a.h5:/Mesh/0/coordinates a.h5:/VisualisationVector/8 a.h5:/Mesh/0/topology a.h5:/Mesh/0/coordinates a.h5:/VisualisationVector/9 -- Chris Richardson BP Institute Madingley Road Cambridge CB3 0EZ From dkxls23 at gmail.com Mon Jun 8 07:46:20 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Mon, 08 Jun 2015 14:46:20 +0300 Subject: [Paraview] Xdmf Sample Files In-Reply-To: <234863aa-1d1a-4ace-bb8a-0378d21533e7@email.android.com> References: <234863aa-1d1a-4ace-bb8a-0378d21533e7@email.android.com> Message-ID: <5575808C.7060508@gmail.com> I posted some XDMF examples earlier on the mailing-list, see e.g. the attachments in these two mails: http://public.kitware.com/pipermail/paraview/2015-March/033566.html http://public.kitware.com/pipermail/paraview/2015-March/033568.html -Armin On 06/06/2015 04:42 PM, Chris Richardson wrote: > This is implemented in FEniCS (www.fenicsproject.org). I can post an example output, if that is useful... > > On 6 Jun 2015 13:40, Teo Ioannis wrote: >> >> I would like to use the xdmf file format combined with hdf5 in order to output results of a finite element simulation with multiple timesteps. Can anyone supply any sample files for doing so? Is there a tutorial or a starting point to look? Thank you very much in advance. >> >> Theofilos Manitaras > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From scott.wittenburg at kitware.com Mon Jun 8 11:41:00 2015 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Mon, 8 Jun 2015 09:41:00 -0600 Subject: [Paraview] ParaView 4.0.1 Not Compiling for Python, MPI, Llvm In-Reply-To: References: Message-ID: Hi Noah, I don't see the specific link error message in your email, but it seems possible it could be related to your graphics environment. We often have to compile ParaView on amazon EC2 instances when setting up ParaViewWeb, and some of the guides for that may end up being useful to you, specifically: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/graphics_on_ec2_g2 and http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ubuntu_14_04 Cheers, Scott On Sat, Jun 6, 2015 at 9:44 PM, Noah Taylor wrote: > Hello, > > I've been trying to compile this for a couple of weeks now but am running > into some unknown troubles. My build gets to ~50% and kicks out an error as > follows: > > collect2: error: ld returned 1 exit status > make[2]: *** [lib/libvtkRenderingOpenGL-pv4.0.so.1] Error 1 > make[1]: *** [VTK/Rendering/OpenGL/CMakeFiles/vtkRenderingOpenGL.dir/all] > Error 2 > make[1]: *** Waiting for unfinished jobs.... > > I tried locating the libvtkRenderingOpenGL-pv4.0.so.1 and it wasn't > anywhere on my machine and I have googled this library but I cannot find a > solution. > > My ccmake options are as follows (I'm just trying to compile on a ubuntu > aws node): > > BUILD_DOCUMENTATION OFF > > BUILD_EXAMPLES OFF > > BUILD_SHARED_LIBS ON > > BUILD_TESTING ON > > CMAKE_BUILD_TYPE Debug > > CMAKE_INSTALL_PREFIX /usr/local > > GMVReader_GMVREAD_LIB_DIR > /mnt/ParaView-v4.0.1-source/Utilities/VisItBridge/databases/GMV > > GMVReader_SKIP_DATARANGE_CALCU OFF > > MPI_C_INCLUDE_PATH > /usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi > > MPI_C_LIBRARIES > /usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so > > > PARAVIEW_BUILD_QT_GUI OFF > > PARAVIEW_DATA_ROOT PARAVIEW_DATA_ROOT-NOTFOUND > > PARAVIEW_ENABLE_CATALYST ON > > PARAVIEW_ENABLE_FFMPEG OFF > > PARAVIEW_ENABLE_PYTHON ON > > PARAVIEW_ENABLE_QT_SUPPORT OFF > > PARAVIEW_INSTALL_DEVELOPMENT_F OFF > > PARAVIEW_USE_MPI ON > > PARAVIEW_USE_PISTON OFF > > PARAVIEW_USE_VISITBRIDGE OFF > > VTK_Group_Tk OFF > > XDMF_USE_BZIP2 OFF > > XDMF_USE_GZIP OFF > > Do I need to specifiy a path somewhere? comment something out somewhere? > Turn on another option in the CMake options? > > Any help would be appreciated :) > > Noah > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mexas at bris.ac.uk Mon Jun 8 19:39:39 2015 From: mexas at bris.ac.uk (Anton Shterenlikht) Date: Tue, 9 Jun 2015 00:39:39 +0100 (BST) Subject: [Paraview] python changes 4.0/4.1 to 4.3? Message-ID: <201506082339.t58NddUv065709@mech-as222.men.bris.ac.uk> I've a script that used to work ok on 4.0 and 4.1, but now something is wrong with the colours. Has anything changed between 4.0/4.1 to 4.3 to make DataRepresentation3.DiffuseColor = [1.0, 1.0, 0.0] not understood? The full script: ######################################################################72 # Adjust these parameters ext1 = 220 # data extent along 1 ext2 = 220 # data extent along 2 ext3 = 220 # data extent along 3 ffile = "zf5.raw" # fracture file gfile = "zg0.raw" # grain file imsize1 = 1000 # size, in pixels, of the resulting image along 1 imsize2 = 1000 # size, in pixels, of the resulting image along 2 # End of adjustable parameters ######################################################################72 # define the centre of rotation (cor) cor1 = 0.5 * ext1 cor2 = 0.5 * ext2 cor3 = 0.5 * ext3 from paraview.simple import * # the extents start from zero, so need to lower # the upper extents by 1 cracks = ImageReader( FilePrefix= ffile ) cracks.DataExtent=[ 0, ext1-1, 0, ext2-1, 0, ext3-1 ] cracks.DataByteOrder = 'LittleEndian' cracks.DataScalarType = 'int' RenderView1 = GetRenderView() DataRepresentation1 = Show() DataRepresentation1.Representation = 'Outline' DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5] # grain boundaries, cell state 2 Threshold1 = Threshold() Threshold1.Scalars = ['POINTS', 'ImageFile'] Threshold1.ThresholdRange = [ 2, 2 ] Threshold1.AllScalars = 0 DataRepresentation2 = Show() DataRepresentation2.ScalarOpacityUnitDistance = 1.0 DataRepresentation2.SelectionPointFieldDataArrayName = 'ImageFile' DataRepresentation2.DiffuseColor = [ 1, 0, 1 ] camera = GetActiveCamera() camera.SetViewUp(-1,0,0) camera.Azimuth(30) camera.Elevation(30) RenderView1.ResetCamera() # gradient background colour RenderView1.UseGradientBackground = 1 RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117] RenderView1.Background = [0.3215686274509804, 0.3411764705882353, 0.43137254901960786] RenderView1.CenterAxesVisibility = 0 RenderView1.OrientationAxesVisibility = 1 RenderView1.CenterOfRotation = [ cor1, cor2, cor3 ] RenderView1.CameraFocalPoint = [ cor1, cor2, cor3 ] RenderView1.ViewSize = [ imsize1, imsize2 ] RenderView1.CameraViewAngle = 30 # do all crack states from the main dataset SetActiveSource( cracks ) # (100) cracks cracks100 = Threshold() cracks100.Scalars = ['POINTS', 'ImageFile'] cracks100.ThresholdRange = [ 0, 0 ] cracks100.AllScalars = 0 DataRepresentation3 = Show() DataRepresentation3.ScalarOpacityUnitDistance = 1.0 DataRepresentation3.SelectionPointFieldDataArrayName = 'ImageFile' DataRepresentation3.DiffuseColor = [1.0, 1.0, 0.0] # (110) cracks SetActiveSource( cracks ) cracks110 = Threshold() cracks110.Scalars = ['POINTS', 'ImageFile'] cracks110.ThresholdRange = [ -1, -1 ] cracks110.AllScalars = 0 DataRepresentation4 = Show() DataRepresentation4.ScalarOpacityUnitDistance = 1.0 DataRepresentation4.SelectionPointFieldDataArrayName = 'ImageFile' DataRepresentation4.DiffuseColor = [0.0, 1.0, 0.5] # 1 is to show, 0 not to show # data2 is GB # data3 is cracks # data4 is grains microstructure DataRepresentation2.Opacity = 0.1 WriteImage( "crgb.png" ) DataRepresentation2.Opacity = 1 DataRepresentation3.Visibility = 0 WriteImage( "gb.png" ) DataRepresentation2.Visibility = 0 DataRepresentation3.Visibility = 1 WriteImage( "cr.png" ) RenderView1.ResetCamera() Render() **** Is there anything wrong in this script for 4.3? Many thanks Anton From haonrolyat at gmail.com Tue Jun 9 00:32:00 2015 From: haonrolyat at gmail.com (Noah Taylor) Date: Mon, 8 Jun 2015 22:32:00 -0600 Subject: [Paraview] ParaView 4.0.1 Not Compiling for Python, MPI, Llvm In-Reply-To: References: Message-ID: Scott, Thank you very much! The documentation looks to be well written. Cheers, Noah On Mon, Jun 8, 2015 at 9:41 AM, Scott Wittenburg < scott.wittenburg at kitware.com> wrote: > Hi Noah, > > I don't see the specific link error message in your email, but it seems > possible it could be related to your graphics environment. We often have > to compile ParaView on amazon EC2 instances when setting up ParaViewWeb, > and some of the guides for that may end up being useful to you, > specifically: > > > http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/graphics_on_ec2_g2 > > and > > > http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ubuntu_14_04 > > Cheers, > Scott > > > On Sat, Jun 6, 2015 at 9:44 PM, Noah Taylor wrote: > >> Hello, >> >> I've been trying to compile this for a couple of weeks now but am running >> into some unknown troubles. My build gets to ~50% and kicks out an error as >> follows: >> >> collect2: error: ld returned 1 exit status >> make[2]: *** [lib/libvtkRenderingOpenGL-pv4.0.so.1] Error 1 >> make[1]: *** [VTK/Rendering/OpenGL/CMakeFiles/vtkRenderingOpenGL.dir/all] >> Error 2 >> make[1]: *** Waiting for unfinished jobs.... >> >> I tried locating the libvtkRenderingOpenGL-pv4.0.so.1 and it wasn't >> anywhere on my machine and I have googled this library but I cannot find a >> solution. >> >> My ccmake options are as follows (I'm just trying to compile on a ubuntu >> aws node): >> >> BUILD_DOCUMENTATION OFF >> >> BUILD_EXAMPLES OFF >> >> BUILD_SHARED_LIBS ON >> >> BUILD_TESTING ON >> >> CMAKE_BUILD_TYPE Debug >> >> CMAKE_INSTALL_PREFIX /usr/local >> >> GMVReader_GMVREAD_LIB_DIR >> /mnt/ParaView-v4.0.1-source/Utilities/VisItBridge/databases/GMV >> >> GMVReader_SKIP_DATARANGE_CALCU OFF >> >> MPI_C_INCLUDE_PATH >> /usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi >> >> MPI_C_LIBRARIES >> /usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so >> >> >> PARAVIEW_BUILD_QT_GUI OFF >> >> PARAVIEW_DATA_ROOT PARAVIEW_DATA_ROOT-NOTFOUND >> >> PARAVIEW_ENABLE_CATALYST ON >> >> PARAVIEW_ENABLE_FFMPEG OFF >> >> PARAVIEW_ENABLE_PYTHON ON >> >> PARAVIEW_ENABLE_QT_SUPPORT OFF >> >> PARAVIEW_INSTALL_DEVELOPMENT_F OFF >> >> PARAVIEW_USE_MPI ON >> >> PARAVIEW_USE_PISTON OFF >> >> PARAVIEW_USE_VISITBRIDGE OFF >> >> VTK_Group_Tk OFF >> >> XDMF_USE_BZIP2 OFF >> >> XDMF_USE_GZIP OFF >> >> Do I need to specifiy a path somewhere? comment something out somewhere? >> Turn on another option in the CMake options? >> >> Any help would be appreciated :) >> >> Noah >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lian.gan at durham.ac.uk Tue Jun 9 05:14:19 2015 From: lian.gan at durham.ac.uk (Lian Gan) Date: Tue, 9 Jun 2015 10:14:19 +0100 Subject: [Paraview] load ensight gold ASCII format data Message-ID: <5576AE6B.2070008@durham.ac.uk> Hello there, I'm new to this list. I have a question about paraview plotting ensight gold ascii format data. Following the ensight manual, I generated the .case file, .geo file and some variable files using MATLAB. The format should be correct, since paraview successfully loads the case file and recognizes the variables and their data range, so i think this implies that the .case file links to the variable files successfully. The problem is that nothing can be plotted, e.g. isosurface and slice. The data set is a simple rectilinear 3D structured grid with both scalar and vector stored on each node. I have some experience of paraview. When I convert the above mentioned data set to vtk ascii format, everything works fine. Can anyone point a direction to solve this problem please? Did I miss anything, or anything different when plotting vtk and ensight gold format data? Many thanks in advance. Best, Lian From lukas.drinkt.thee at gmail.com Tue Jun 9 06:07:32 2015 From: lukas.drinkt.thee at gmail.com (Lukas van de Wiel) Date: Tue, 9 Jun 2015 12:07:32 +0200 Subject: [Paraview] bugreport Message-ID: Dear all, Paraview segfaults when multiple data sets have the same name. While this is a mistake by the user, IMHO it should be handled a bit more gracefully than a segfault. Found in Paraview 3.14.1, 64 bits, running on linux For example, the following file of two data sets on the unit tetrahedron, both names 'test123', causes a segfault. Change one of the names and everything runs well. 0.1 0.2 0.3 0.4 1.0 2.0 3.0 4.0 0 0 0 0 0 1 0 1 0 1 0 0 0 1 2 3 4 10 Best wishes, Lukas -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Jun 9 08:57:07 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 09 Jun 2015 12:57:07 +0000 Subject: [Paraview] python changes 4.0/4.1 to 4.3? In-Reply-To: <201506082339.t58NddUv065709@mech-as222.men.bris.ac.uk> References: <201506082339.t58NddUv065709@mech-as222.men.bris.ac.uk> Message-ID: Anton, DiffuseColor still exists. Can you post the full error message that you're getting? If you can share the dataset you're using to test this script, that'll be even better! Utkarsh On Mon, Jun 8, 2015 at 7:39 PM Anton Shterenlikht wrote: > I've a script that used to work ok on 4.0 and 4.1, > but now something is wrong with the colours. > Has anything changed between 4.0/4.1 to 4.3 to make > > DataRepresentation3.DiffuseColor = [1.0, 1.0, 0.0] > > not understood? > > > The full script: > > ######################################################################72 > # Adjust these parameters > ext1 = 220 # data extent along 1 > ext2 = 220 # data extent along 2 > ext3 = 220 # data extent along 3 > ffile = "zf5.raw" # fracture file > gfile = "zg0.raw" # grain file > imsize1 = 1000 # size, in pixels, of the resulting image along 1 > imsize2 = 1000 # size, in pixels, of the resulting image along 2 > > # End of adjustable parameters > ######################################################################72 > > # define the centre of rotation (cor) > cor1 = 0.5 * ext1 > cor2 = 0.5 * ext2 > cor3 = 0.5 * ext3 > > from paraview.simple import * > > # the extents start from zero, so need to lower > # the upper extents by 1 > cracks = ImageReader( FilePrefix= ffile ) > cracks.DataExtent=[ 0, ext1-1, 0, ext2-1, 0, ext3-1 ] > cracks.DataByteOrder = 'LittleEndian' > cracks.DataScalarType = 'int' > > RenderView1 = GetRenderView() > DataRepresentation1 = Show() > > DataRepresentation1.Representation = 'Outline' > DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5] > > # grain boundaries, cell state 2 > > Threshold1 = Threshold() > Threshold1.Scalars = ['POINTS', 'ImageFile'] > Threshold1.ThresholdRange = [ 2, 2 ] > Threshold1.AllScalars = 0 > > DataRepresentation2 = Show() > DataRepresentation2.ScalarOpacityUnitDistance = 1.0 > DataRepresentation2.SelectionPointFieldDataArrayName = 'ImageFile' > DataRepresentation2.DiffuseColor = [ 1, 0, 1 ] > > camera = GetActiveCamera() > camera.SetViewUp(-1,0,0) > camera.Azimuth(30) > camera.Elevation(30) > > RenderView1.ResetCamera() > > # gradient background colour > RenderView1.UseGradientBackground = 1 > RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117] > RenderView1.Background = [0.3215686274509804, 0.3411764705882353, > 0.43137254901960786] > > RenderView1.CenterAxesVisibility = 0 > RenderView1.OrientationAxesVisibility = 1 > RenderView1.CenterOfRotation = [ cor1, cor2, cor3 ] > RenderView1.CameraFocalPoint = [ cor1, cor2, cor3 ] > RenderView1.ViewSize = [ imsize1, imsize2 ] > RenderView1.CameraViewAngle = 30 > > # do all crack states from the main dataset > SetActiveSource( cracks ) > > # (100) cracks > cracks100 = Threshold() > cracks100.Scalars = ['POINTS', 'ImageFile'] > cracks100.ThresholdRange = [ 0, 0 ] > cracks100.AllScalars = 0 > > DataRepresentation3 = Show() > DataRepresentation3.ScalarOpacityUnitDistance = 1.0 > DataRepresentation3.SelectionPointFieldDataArrayName = 'ImageFile' > DataRepresentation3.DiffuseColor = [1.0, 1.0, 0.0] > > # (110) cracks > SetActiveSource( cracks ) > cracks110 = Threshold() > cracks110.Scalars = ['POINTS', 'ImageFile'] > cracks110.ThresholdRange = [ -1, -1 ] > cracks110.AllScalars = 0 > > DataRepresentation4 = Show() > DataRepresentation4.ScalarOpacityUnitDistance = 1.0 > DataRepresentation4.SelectionPointFieldDataArrayName = 'ImageFile' > DataRepresentation4.DiffuseColor = [0.0, 1.0, 0.5] > > # 1 is to show, 0 not to show > # data2 is GB > # data3 is cracks > # data4 is grains microstructure > > DataRepresentation2.Opacity = 0.1 > WriteImage( "crgb.png" ) > > DataRepresentation2.Opacity = 1 > DataRepresentation3.Visibility = 0 > WriteImage( "gb.png" ) > > DataRepresentation2.Visibility = 0 > DataRepresentation3.Visibility = 1 > WriteImage( "cr.png" ) > > RenderView1.ResetCamera() > > Render() > > > **** > > Is there anything wrong in this script for 4.3? > > Many thanks > > Anton > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Jun 9 09:34:16 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 9 Jun 2015 09:34:16 -0400 Subject: [Paraview] bugreport In-Reply-To: References: Message-ID: Lukas, Thanks for reporting the crash. I confirmed it, and it is happening in VTK. I filed a VTK bug report which is located here: http://www.vtk.org/Bug/view.php?id=15525 Thanks, Cory On Tue, Jun 9, 2015 at 6:07 AM, Lukas van de Wiel wrote: > Dear all, > > Paraview segfaults when multiple data sets have the same name. > > While this is a mistake by the user, IMHO it should be handled a bit more > gracefully than a segfault. > > Found in Paraview 3.14.1, 64 bits, running on linux > > > For example, the following file of two data sets on the unit tetrahedron, > both names 'test123', causes a segfault. Change one of the names and > everything runs well. > > > > > > > > 0.1 0.2 0.3 0.4 > > > 1.0 2.0 3.0 4.0 > > > > > 0 0 0 0 0 1 0 1 0 1 0 0 > > > > > 0 1 2 3 > > > 4 > > > 10 > > > > > > > > Best wishes, > > Lukas > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen R&D Engineer Kitware, Inc. From jiaoliqing at gmail.com Tue Jun 9 11:13:17 2015 From: jiaoliqing at gmail.com (Liqing Jiao) Date: Tue, 9 Jun 2015 17:13:17 +0200 Subject: [Paraview] A problem about plotting beach balls in Paraview Message-ID: Dear all, I have a problem to plot beach balls in Paraview: I open the "cracks.4.vtu" file in Paraview. The file is attached. Then I use Glyph to plot a sphere, and the radius of sphere is "cracksize". I use Glyphs to plot two arrows and two circles. The purple arrow is the arrow of "normalF". The purple circle is perpendicular to the purple arrow. The yellow arrow is the arrow of "shearF". The yellow circle is perpendiclar to the yellow arrow. So, here we have one sphere and two conjugate circles through the center of sphere as in the "Paraview plot.png" in the attachment. Our purpose to divide the sphere into four quarters. and color two of them in blue as the "Beach ball.png" (attached) shows. Based on the panel provided by Paraview, I have no idea to make it. Could you please help me figure it out? Thank you very much. Note: "cracksize", "normalF", and "shearF" are from data in "cracks.4.vtu". Cheers, Liqing -- *********************************************** Liqing Jiao Phd candidate Earth Observatory of Singapore Nanyang Technological University Block N2-01a-15, 50 Nanyang Avenue, Singapore 639798 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Paraview plot.png Type: image/png Size: 303843 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Beach ball.png Type: image/png Size: 62213 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cracks.4.vtu Type: application/octet-stream Size: 3502 bytes Desc: not available URL: From mexas at bris.ac.uk Tue Jun 9 14:40:16 2015 From: mexas at bris.ac.uk (Anton Shterenlikht) Date: Tue, 9 Jun 2015 19:40:16 +0100 Subject: [Paraview] python changes 4.0/4.1 to 4.3? In-Reply-To: References: <201506082339.t58NddUv065709@mech-as222.men.bris.ac.uk> Message-ID: There is no error, just instead of the requested colours: DataRepresentation2.DiffuseColor = [ 1, 0, 1 ] <- purple DataRepresentation3.DiffuseColor = [1.0, 1.0, 0.0] <- yellow DataRepresentation4.DiffuseColor = [0.0, 1.0, 0.5] <- greenish I get red and blue. The colours I had with pv 4.0/4.1 can be seen here: http://eis.bris.ac.uk/~mexas/cgpack/201502res/cr.png http://eis.bris.ac.uk/~mexas/cgpack/201503res/gb.png The colours I'm getting now with 4.3 (with the same script) can be seen here: http://eis.bris.ac.uk/~mexas/cgpack/201506res/cr.png http://eis.bris.ac.uk/~mexas/cgpack/201506res/gb.png The 2 data files I used are: http://eis.bris.ac.uk/~mexas/zg0.raw http://eis.bris.ac.uk/~mexas/zf5.raw The files are raw binary, 40MB each. I might have done something really stupid, in which case I apologise for wasting your time. Thanks for your help Anton On 09/06/2015, Utkarsh Ayachit wrote: > Anton, > > DiffuseColor still exists. Can you post the full error message that you're > getting? If you can share the dataset you're using to test this script, > that'll be even better! > > Utkarsh > > > On Mon, Jun 8, 2015 at 7:39 PM Anton Shterenlikht wrote: > >> I've a script that used to work ok on 4.0 and 4.1, >> but now something is wrong with the colours. >> Has anything changed between 4.0/4.1 to 4.3 to make >> >> DataRepresentation3.DiffuseColor = [1.0, 1.0, 0.0] >> >> not understood? >> >> >> The full script: >> >> ######################################################################72 >> # Adjust these parameters >> ext1 = 220 # data extent along 1 >> ext2 = 220 # data extent along 2 >> ext3 = 220 # data extent along 3 >> ffile = "zf5.raw" # fracture file >> gfile = "zg0.raw" # grain file >> imsize1 = 1000 # size, in pixels, of the resulting image along 1 >> imsize2 = 1000 # size, in pixels, of the resulting image along 2 >> >> # End of adjustable parameters >> ######################################################################72 >> >> # define the centre of rotation (cor) >> cor1 = 0.5 * ext1 >> cor2 = 0.5 * ext2 >> cor3 = 0.5 * ext3 >> >> from paraview.simple import * >> >> # the extents start from zero, so need to lower >> # the upper extents by 1 >> cracks = ImageReader( FilePrefix= ffile ) >> cracks.DataExtent=[ 0, ext1-1, 0, ext2-1, 0, ext3-1 ] >> cracks.DataByteOrder = 'LittleEndian' >> cracks.DataScalarType = 'int' >> >> RenderView1 = GetRenderView() >> DataRepresentation1 = Show() >> >> DataRepresentation1.Representation = 'Outline' >> DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5] >> >> # grain boundaries, cell state 2 >> >> Threshold1 = Threshold() >> Threshold1.Scalars = ['POINTS', 'ImageFile'] >> Threshold1.ThresholdRange = [ 2, 2 ] >> Threshold1.AllScalars = 0 >> >> DataRepresentation2 = Show() >> DataRepresentation2.ScalarOpacityUnitDistance = 1.0 >> DataRepresentation2.SelectionPointFieldDataArrayName = 'ImageFile' >> DataRepresentation2.DiffuseColor = [ 1, 0, 1 ] >> >> camera = GetActiveCamera() >> camera.SetViewUp(-1,0,0) >> camera.Azimuth(30) >> camera.Elevation(30) >> >> RenderView1.ResetCamera() >> >> # gradient background colour >> RenderView1.UseGradientBackground = 1 >> RenderView1.Background2 = [0.0, 0.0, 0.16470588235294117] >> RenderView1.Background = [0.3215686274509804, 0.3411764705882353, >> 0.43137254901960786] >> >> RenderView1.CenterAxesVisibility = 0 >> RenderView1.OrientationAxesVisibility = 1 >> RenderView1.CenterOfRotation = [ cor1, cor2, cor3 ] >> RenderView1.CameraFocalPoint = [ cor1, cor2, cor3 ] >> RenderView1.ViewSize = [ imsize1, imsize2 ] >> RenderView1.CameraViewAngle = 30 >> >> # do all crack states from the main dataset >> SetActiveSource( cracks ) >> >> # (100) cracks >> cracks100 = Threshold() >> cracks100.Scalars = ['POINTS', 'ImageFile'] >> cracks100.ThresholdRange = [ 0, 0 ] >> cracks100.AllScalars = 0 >> >> DataRepresentation3 = Show() >> DataRepresentation3.ScalarOpacityUnitDistance = 1.0 >> DataRepresentation3.SelectionPointFieldDataArrayName = 'ImageFile' >> DataRepresentation3.DiffuseColor = [1.0, 1.0, 0.0] >> >> # (110) cracks >> SetActiveSource( cracks ) >> cracks110 = Threshold() >> cracks110.Scalars = ['POINTS', 'ImageFile'] >> cracks110.ThresholdRange = [ -1, -1 ] >> cracks110.AllScalars = 0 >> >> DataRepresentation4 = Show() >> DataRepresentation4.ScalarOpacityUnitDistance = 1.0 >> DataRepresentation4.SelectionPointFieldDataArrayName = 'ImageFile' >> DataRepresentation4.DiffuseColor = [0.0, 1.0, 0.5] >> >> # 1 is to show, 0 not to show >> # data2 is GB >> # data3 is cracks >> # data4 is grains microstructure >> >> DataRepresentation2.Opacity = 0.1 >> WriteImage( "crgb.png" ) >> >> DataRepresentation2.Opacity = 1 >> DataRepresentation3.Visibility = 0 >> WriteImage( "gb.png" ) >> >> DataRepresentation2.Visibility = 0 >> DataRepresentation3.Visibility = 1 >> WriteImage( "cr.png" ) >> >> RenderView1.ResetCamera() >> >> Render() >> >> >> **** >> >> Is there anything wrong in this script for 4.3? >> >> Many thanks >> >> Anton >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > From jeffrey.c.becker at nasa.gov Tue Jun 9 20:22:35 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Tue, 9 Jun 2015 17:22:35 -0700 Subject: [Paraview] pvserver segfault Message-ID: <5577834B.5050408@nasa.gov> Hi. I'm running pvserver on a GPU server, and a client on my desktop. After starting X on the server, I'm running pvserver as follows, and then connect to it from the client $ mpirun -np 1 /usr/bin/env DISPLAY=:0 /u/jcbecker/ParaView-4.3.1-Linux-64bit/bin/pvserver --client-host=pfe20 --use-offscreen-rendering Waiting for client... Connection URL: cs://r219i0n0:11111 Accepting connection(s): r219i0n0:11111 Client connected. I open a 1.6GB unstructured (.vtu) grid file, and hit apply. After the file is read, and some time passes, I get SIGSEGV and I see the following backtrace in gdb. Please advise on what's wrong, and how to fix. Thanks. -jeff (gdb) bt #0 0x00002aaab0bb92a8 in memcpy () from /lib64/libc.so.6 #1 0x00002aaac3128a70 in ?? () from /usr/lib64/libnvidia-glcore.so.340.65 #2 0x00002aaac327e2a1 in ?? () from /usr/lib64/libnvidia-glcore.so.340.65 #3 0x00002aaac328006e in ?? () from /usr/lib64/libnvidia-glcore.so.340.65 #4 0x00002aaaba0e4197 in vtkOpenGLDisplayListPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #5 0x00002aaaba0e06a1 in vtkOpenGLClipPlanesPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #6 0x00002aaaba122e2a in vtkOpenGLScalarsToColorsPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #7 0x00002aaaba12fdb4 in vtkPainterPolyDataMapper::RenderPiece(vtkRenderer*, vtkActor*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #8 0x00002aaaac4ad93f in vtkPolyDataMapper::Render(vtkRenderer*, vtkActor*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #9 0x00002aaaba0dcd08 in vtkOpenGLActor::Render(vtkRenderer*, vtkMapper*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #10 0x00002aaab4f1630b in vtkPVLODActor::Render(vtkRenderer*, vtkMapper*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 #11 0x00002aaab4f16157 in vtkPVLODActor::RenderOpaqueGeometry(vtkViewport*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 #12 0x00002aaaac4b9464 in vtkRenderer::UpdateGeometry() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #13 0x00002aaab4f0a751 in vtkPVDefaultPass::Render(vtkRenderState const*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 #14 0x00002aaaba0ae35b in vtkCameraPass::Render(vtkRenderState const*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #15 0x00002aaaba1206c0 in vtkOpenGLRenderer::DeviceRender() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #16 0x00002aaaac4bb18d in vtkRenderer::Render() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #17 0x00002aaaac4b8429 in vtkRendererCollection::Render() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #18 0x00002aaaac4c2202 in vtkRenderWindow::DoStereoRender() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #19 0x00002aaaac4c2119 in vtkRenderWindow::DoFDRender() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #20 0x00002aaaac4c31a3 in vtkRenderWindow::DoAARender() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #21 0x00002aaaac4bf7fe in vtkRenderWindow::Render() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #22 0x00002aaaba1ae7ae in vtkXOpenGLRenderWindow::Render() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #23 0x00002aaab3b7597f in vtkPVRenderView::Render(bool, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreRendering-pv4.3.so.1 #24 0x00002aaab3b7069c in vtkPVRenderView::StillRender() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreRendering-pv4.3.so.1 #25 0x00002aaaab493665 in vtkPVRenderViewCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerManagerApplication-pv4.3.so.1 #26 0x00002aaaadb005e0 in vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so.1 #27 0x00002aaaadb05393 in vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so.1 #28 0x00002aaaadb03832 in vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so.1 #29 0x00002aaaadb03ced in vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so.1 #30 0x00002aaaabd8dcec in vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 #31 0x00002aaaabd8d958 in vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 #32 0x00002aaaabd8c203 in vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 #33 0x00002aaaabd98591 in vtkPVSessionServer::OnClientServerMessageRMI(void*, int) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 #34 0x00002aaaae2cc463 in vtkMultiProcessController::ProcessRMI(int, void*, int, int) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkParallelCore-pv4.3.so.1 #35 0x00002aaaae2cc7df in vtkMultiProcessController::ProcessRMIs(int, int) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkParallelCore-pv4.3.so.1 #36 0x00002aaaabfa5ec6 in vtkTCPNetworkAccessManager::ProcessEventsInternal(unsigned long, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreCore-pv4.3.so.1 #37 0x00000000004019f6 in RealMain(int, char**, vtkProcessModule::ProcessTypes) () #38 0x0000000000401a3e in main () From utkarsh.ayachit at kitware.com Tue Jun 9 21:54:30 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 10 Jun 2015 01:54:30 +0000 Subject: [Paraview] pvserver segfault In-Reply-To: <5577834B.5050408@nasa.gov> References: <5577834B.5050408@nasa.gov> Message-ID: Can you try turning off "Display Lists"? It's an option under the Settings (Render View tab) dialog. You'll need to restart ParaView after making this change. I suspect the graphics driver is giving up while building a large display list. Display lists will be a thing of the past once we update the rendering backend in the next release of ParaView, FYI. Utkarsh On Tue, Jun 9, 2015 at 8:23 PM Jeff Becker wrote: > Hi. I'm running pvserver on a GPU server, and a client on my desktop. > After starting X on the server, I'm running pvserver as follows, and > then connect to it from the client > > $ mpirun -np 1 /usr/bin/env DISPLAY=:0 > /u/jcbecker/ParaView-4.3.1-Linux-64bit/bin/pvserver --client-host=pfe20 > --use-offscreen-rendering > Waiting for client... > Connection URL: cs://r219i0n0:11111 > Accepting connection(s): r219i0n0:11111 > Client connected. > > I open a 1.6GB unstructured (.vtu) grid file, and hit apply. After the > file is read, and some time passes, I get SIGSEGV and I see the > following backtrace in gdb. Please advise on what's wrong, and how to > fix. Thanks. > > -jeff > > (gdb) bt > #0 0x00002aaab0bb92a8 in memcpy () from /lib64/libc.so.6 > #1 0x00002aaac3128a70 in ?? () from /usr/lib64/libnvidia-glcore.so.340.65 > #2 0x00002aaac327e2a1 in ?? () from /usr/lib64/libnvidia-glcore.so.340.65 > #3 0x00002aaac328006e in ?? () from /usr/lib64/libnvidia-glcore.so.340.65 > #4 0x00002aaaba0e4197 in > vtkOpenGLDisplayListPainter::RenderInternal(vtkRenderer*, vtkActor*, > unsigned long, bool) () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #5 0x00002aaaba0e06a1 in > vtkOpenGLClipPlanesPainter::RenderInternal(vtkRenderer*, vtkActor*, > unsigned long, bool) () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #6 0x00002aaaba122e2a in > vtkOpenGLScalarsToColorsPainter::RenderInternal(vtkRenderer*, vtkActor*, > unsigned long, bool) () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #7 0x00002aaaba12fdb4 in > vtkPainterPolyDataMapper::RenderPiece(vtkRenderer*, vtkActor*) () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #8 0x00002aaaac4ad93f in vtkPolyDataMapper::Render(vtkRenderer*, > vtkActor*) () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #9 0x00002aaaba0dcd08 in vtkOpenGLActor::Render(vtkRenderer*, > vtkMapper*) () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #10 0x00002aaab4f1630b in vtkPVLODActor::Render(vtkRenderer*, vtkMapper*) > () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 > #11 0x00002aaab4f16157 in > vtkPVLODActor::RenderOpaqueGeometry(vtkViewport*) () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 > #12 0x00002aaaac4b9464 in vtkRenderer::UpdateGeometry() () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #13 0x00002aaab4f0a751 in vtkPVDefaultPass::Render(vtkRenderState const*) > () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 > #14 0x00002aaaba0ae35b in vtkCameraPass::Render(vtkRenderState const*) () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #15 0x00002aaaba1206c0 in vtkOpenGLRenderer::DeviceRender() () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #16 0x00002aaaac4bb18d in vtkRenderer::Render() () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #17 0x00002aaaac4b8429 in vtkRendererCollection::Render() () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #18 0x00002aaaac4c2202 in vtkRenderWindow::DoStereoRender() () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #19 0x00002aaaac4c2119 in vtkRenderWindow::DoFDRender() () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #20 0x00002aaaac4c31a3 in vtkRenderWindow::DoAARender() () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #21 0x00002aaaac4bf7fe in vtkRenderWindow::Render() () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #22 0x00002aaaba1ae7ae in vtkXOpenGLRenderWindow::Render() () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #23 0x00002aaab3b7597f in vtkPVRenderView::Render(bool, bool) () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreRendering-pv4.3.so.1 > #24 0x00002aaab3b7069c in vtkPVRenderView::StillRender() () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreRendering-pv4.3.so.1 > #25 0x00002aaaab493665 in > vtkPVRenderViewCommand(vtkClientServerInterpreter*, vtkObjectBase*, char > const*, vtkClientServerStream const&, vtkClientServerStream&, void*) () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerManagerApplication-pv4.3.so.1 > #26 0x00002aaaadb005e0 in > vtkClientServerInterpreter::CallCommandFunction(char const*, > vtkObjectBase*, char const*, vtkClientServerStream const&, > vtkClientServerStream&) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/ > libvtkClientServer-pv4.3.so.1 > #27 0x00002aaaadb05393 in > vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream > const&, int) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/ > libvtkClientServer-pv4.3.so.1 > #28 0x00002aaaadb03832 in > vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream > const&, int) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/ > libvtkClientServer-pv4.3.so.1 > #29 0x00002aaaadb03ced in > vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/ > libvtkClientServer-pv4.3.so.1 > #30 0x00002aaaabd8dcec in > vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, > bool) () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 > #31 0x00002aaaabd8d958 in vtkPVSessionCore::ExecuteStream(unsigned int, > vtkClientServerStream const&, bool) () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 > #32 0x00002aaaabd8c203 in vtkPVSessionBase::ExecuteStream(unsigned int, > vtkClientServerStream const&, bool) () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 > #33 0x00002aaaabd98591 in > vtkPVSessionServer::OnClientServerMessageRMI(void*, int) () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 > #34 0x00002aaaae2cc463 in vtkMultiProcessController::ProcessRMI(int, > void*, int, int) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/ > libvtkParallelCore-pv4.3.so.1 > #35 0x00002aaaae2cc7df in vtkMultiProcessController::ProcessRMIs(int, > int) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/ > libvtkParallelCore-pv4.3.so.1 > #36 0x00002aaaabfa5ec6 in > vtkTCPNetworkAccessManager::ProcessEventsInternal(unsigned long, bool) () > from > > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreCore-pv4.3.so.1 > #37 0x00000000004019f6 in RealMain(int, char**, > vtkProcessModule::ProcessTypes) > () > #38 0x0000000000401a3e in main () > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nenadus at gmail.com Wed Jun 10 03:25:53 2015 From: nenadus at gmail.com (Nenad Vujicic) Date: Wed, 10 Jun 2015 09:25:53 +0200 Subject: [Paraview] Troubles with exporting selection labels from current ParaView render view In-Reply-To: References: Message-ID: Dear Utkarsh, I'm sorry for delay, I was out of home for a while. Yes, I think this will help. Thank you very much for your help! Nenad. On Sat, May 30, 2015 at 4:10 PM, Utkarsh Ayachit wrote: > Nenad, > > DataLabelRepresentation is a subproxy of the GeometryRepresentation and that > has been the case since as long as I remember. That means that when you > iterate over representations in the view, you'll never see a separate > DataLabelRepresentation proxy. Each source proxy has a GetSelectionOutput > method that you can use to get the source proxy which is doing the > "extracting" tasks to extract selected points. To see if the source proxy > has a "selection" set, you can use the vtkSMSourceProxy::GetSelectionInput() > method. > > Hope that helps. > Utkarsh > > On Fri, May 22, 2015 at 7:15 AM Nenad Vujicic wrote: >> >> Utkarsh, >> >> Thank you very much for answers about creating and initializing >> DataLabelRepresentation. Now my source plugin works perfectly. >> >> But, my exporting plugin (my first message) is still unable to export >> labels which I get when try selecting several points. Here is what I >> do: >> >> 1. Create Sphere and apply Elevation filter on it (I turn OFF 3d widget), >> 2. I select several points and in Selection Manager I select Elevation >> for Point Labels, >> 3. In following code snippet I get only 2 message boxes (one of Sphere >> and one for Elevation - both GeometryRepresentation),, but, there is >> no DataLabelRepresentation. >> 4. I know how to extract labels parameters at this level (Selection* >> parameters from representation), but not set of points over which are >> generated labels, >> >> // for all sources >> for(i = 0; i < sources.size(); i++) >> { >> // get source >> pqPipelineSource* source = sources.at(i); >> >> // for every source's output port, process it >> for(output_port = 0; output_port < >> source->getNumberOfOutputPorts(); output_port++) >> { >> // traverse all representations >> for(j = 0; j < source->getRepresentations(output_port, >> active_view).count(); j++) >> { >> QMessageBox::about(NULL, "", >> GetCurrentSourceRepresentationSMName()); >> } >> } >> } >> >> Should I try to catch >> pqSelectionManager::selectionChanged(pqOutputPort*) to get data >> structure over which are points which I can compare with data >> structures extracted from vtkRenderWindow to generate labels? >> >> Thanks for help in advance! >> >> Nenad. >> >> On Mon, May 18, 2015 at 3:49 PM, Utkarsh Ayachit >> wrote: >> >> - Strange 1: I don't have anymore instance in >> >> DataLabelRepresentation for Elevation pipeline source (btw, during >> >> this traversing I get only one actor), >> > >> > I don't follow. DataLableRepresentation is indeed created for every >> > representation shown in the render view. >> > >> > >> >> - Strange 2: When I traverse vtkRenderer's actors, I get 2 actors >> >> (sphere mesh and actor with selected points), but, I'm unable to >> >> connect selection label properties (which are tied with Elevation >> >> pipeline source actor - sphere mesh) and mesh with selected points / >> >> cells. >> > >> > Remember that label actors are added to the 2D / non-composited >> > renderer, not the same as the 3D renderer. Which renderer are you >> > looking at? >> > >> >> Q1: How to identify actor from vtkRenderer which contains selection >> >> points / cells and get selection properties from this actor or >> >> >> >> Q2: How to identify actor from pqPipeline source on which are selected >> >> points and how from appropriate representations to get actor which >> >> contains selected points / cells? >> > >> > Neither of these are really supported. Look at >> > vtkSelectionRepresentation. If you can think of ways of "tagging" the >> > actors added by the representations used internally by this class, I >> > am all ears. From peter at peterheppel.com Wed Jun 10 11:38:20 2015 From: peter at peterheppel.com (Peter) Date: Wed, 10 Jun 2015 17:38:20 +0200 Subject: [Paraview] pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0 Message-ID: <10e5a92c2de8b3c9c685221b8c714f86@peterheppel.com> Hello I just built the current Paraview development version and got the same error on running the Catalyst examples. Paraview declined the connection gracefully when the client was built with a different VTK version, so I suspect the issue isnt related to the socket handshake, but rather that it only occurs after the socket connection is successful. P -- Peter Heppel 35/37 Rue de Locmalo 56290 Port-Louis France +33 6 81 30 76 52 cell +33 2 97 82 19 30 USA +1 773 280 8142 Skype: peterheppel -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffrey.c.becker at nasa.gov Wed Jun 10 13:13:30 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Wed, 10 Jun 2015 10:13:30 -0700 Subject: [Paraview] pvserver segfault In-Reply-To: References: <5577834B.5050408@nasa.gov> Message-ID: <5578703A.7070503@nasa.gov> On 06/09/2015 06:54 PM, Utkarsh Ayachit wrote: > Can you try turning off "Display Lists"? It's an option under the > Settings (Render View tab) dialog. You'll need to restart ParaView > after making this change. I suspect the graphics driver is giving up > while building a large display list. Display lists will be a thing of > the past once we update the rendering backend in the next release of > ParaView, FYI. That works. Now, I'll try running several pvservers (each on a different GPU node) in hopes of speeding up interactivity. I'm assuming the file gets read on the first one, and it splits up the grid among all the servers? Thanks. -jeff > > Utkarsh > > On Tue, Jun 9, 2015 at 8:23 PM Jeff Becker > wrote: > > Hi. I'm running pvserver on a GPU server, and a client on my desktop. > After starting X on the server, I'm running pvserver as follows, and > then connect to it from the client > > $ mpirun -np 1 /usr/bin/env DISPLAY=:0 > /u/jcbecker/ParaView-4.3.1-Linux-64bit/bin/pvserver > --client-host=pfe20 > --use-offscreen-rendering > Waiting for client... > Connection URL: cs://r219i0n0:11111 > Accepting connection(s): r219i0n0:11111 > Client connected. > > I open a 1.6GB unstructured (.vtu) grid file, and hit apply. After the > file is read, and some time passes, I get SIGSEGV and I see the > following backtrace in gdb. Please advise on what's wrong, and how to > fix. Thanks. > > -jeff > > (gdb) bt > #0 0x00002aaab0bb92a8 in memcpy () from /lib64/libc.so.6 > #1 0x00002aaac3128a70 in ?? () from > /usr/lib64/libnvidia-glcore.so.340.65 > #2 0x00002aaac327e2a1 in ?? () from > /usr/lib64/libnvidia-glcore.so.340.65 > #3 0x00002aaac328006e in ?? () from > /usr/lib64/libnvidia-glcore.so.340.65 > #4 0x00002aaaba0e4197 in > vtkOpenGLDisplayListPainter::RenderInternal(vtkRenderer*, vtkActor*, > unsigned long, bool) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #5 0x00002aaaba0e06a1 in > vtkOpenGLClipPlanesPainter::RenderInternal(vtkRenderer*, vtkActor*, > unsigned long, bool) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #6 0x00002aaaba122e2a in > vtkOpenGLScalarsToColorsPainter::RenderInternal(vtkRenderer*, > vtkActor*, > unsigned long, bool) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #7 0x00002aaaba12fdb4 in > vtkPainterPolyDataMapper::RenderPiece(vtkRenderer*, vtkActor*) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #8 0x00002aaaac4ad93f in vtkPolyDataMapper::Render(vtkRenderer*, > vtkActor*) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #9 0x00002aaaba0dcd08 in vtkOpenGLActor::Render(vtkRenderer*, > vtkMapper*) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #10 0x00002aaab4f1630b in vtkPVLODActor::Render(vtkRenderer*, > vtkMapper*) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 > #11 0x00002aaab4f16157 in > vtkPVLODActor::RenderOpaqueGeometry(vtkViewport*) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 > #12 0x00002aaaac4b9464 in vtkRenderer::UpdateGeometry() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #13 0x00002aaab4f0a751 in vtkPVDefaultPass::Render(vtkRenderState > const*) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 > #14 0x00002aaaba0ae35b in vtkCameraPass::Render(vtkRenderState > const*) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #15 0x00002aaaba1206c0 in vtkOpenGLRenderer::DeviceRender() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #16 0x00002aaaac4bb18d in vtkRenderer::Render() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #17 0x00002aaaac4b8429 in vtkRendererCollection::Render() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #18 0x00002aaaac4c2202 in vtkRenderWindow::DoStereoRender() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #19 0x00002aaaac4c2119 in vtkRenderWindow::DoFDRender() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #20 0x00002aaaac4c31a3 in vtkRenderWindow::DoAARender() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #21 0x00002aaaac4bf7fe in vtkRenderWindow::Render() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #22 0x00002aaaba1ae7ae in vtkXOpenGLRenderWindow::Render() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #23 0x00002aaab3b7597f in vtkPVRenderView::Render(bool, bool) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreRendering-pv4.3.so.1 > #24 0x00002aaab3b7069c in vtkPVRenderView::StillRender() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreRendering-pv4.3.so.1 > #25 0x00002aaaab493665 in > vtkPVRenderViewCommand(vtkClientServerInterpreter*, > vtkObjectBase*, char > const*, vtkClientServerStream const&, vtkClientServerStream&, > void*) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerManagerApplication-pv4.3.so.1 > #26 0x00002aaaadb005e0 in > vtkClientServerInterpreter::CallCommandFunction(char const*, > vtkObjectBase*, char const*, vtkClientServerStream const&, > vtkClientServerStream&) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so > .1 > #27 0x00002aaaadb05393 in > vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream > const&, int) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so > .1 > #28 0x00002aaaadb03832 in > vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream > const&, int) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so > .1 > #29 0x00002aaaadb03ced in > vtkClientServerInterpreter::ProcessStream(vtkClientServerStream > const&) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so > .1 > #30 0x00002aaaabd8dcec in > vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, > bool) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 > #31 0x00002aaaabd8d958 in vtkPVSessionCore::ExecuteStream(unsigned > int, > vtkClientServerStream const&, bool) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 > #32 0x00002aaaabd8c203 in vtkPVSessionBase::ExecuteStream(unsigned > int, > vtkClientServerStream const&, bool) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 > #33 0x00002aaaabd98591 in > vtkPVSessionServer::OnClientServerMessageRMI(void*, int) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 > #34 0x00002aaaae2cc463 in vtkMultiProcessController::ProcessRMI(int, > void*, int, int) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkParallelCore-pv4.3.so > .1 > #35 0x00002aaaae2cc7df in vtkMultiProcessController::ProcessRMIs(int, > int) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkParallelCore-pv4.3.so > .1 > #36 0x00002aaaabfa5ec6 in > vtkTCPNetworkAccessManager::ProcessEventsInternal(unsigned long, > bool) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreCore-pv4.3.so.1 > #37 0x00000000004019f6 in RealMain(int, char**, > vtkProcessModule::ProcessTypes) > () > #38 0x0000000000401a3e in main () > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Jun 10 13:16:25 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 10 Jun 2015 13:16:25 -0400 Subject: [Paraview] pvserver segfault In-Reply-To: <5578703A.7070503@nasa.gov> References: <5577834B.5050408@nasa.gov> <5578703A.7070503@nasa.gov> Message-ID: On Wed, Jun 10, 2015 at 1:13 PM, Jeff Becker wrote: > I'm assuming the file gets read on the first one, and it splits up the > grid among all the servers? It is up to the specific reader class to decide what to do so who exactly reads what depends on the file type. If the data is not well distributed, apply the D3 filter to make paraview repartition the read in data amongst the processors. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffrey.c.becker at nasa.gov Wed Jun 10 13:29:34 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Wed, 10 Jun 2015 10:29:34 -0700 Subject: [Paraview] pvserver segfault In-Reply-To: References: <5577834B.5050408@nasa.gov> <5578703A.7070503@nasa.gov> Message-ID: <557873FE.4080908@nasa.gov> On 06/10/2015 10:16 AM, David E DeMarle wrote: > > On Wed, Jun 10, 2015 at 1:13 PM, Jeff Becker > > wrote: > > I'm assuming the file gets read on the first one, and it splits up > the grid among all the servers? > > > It is up to the specific reader class to decide what to do so who > exactly reads what depends on the file type. If the data is not well > distributed, apply the D3 filter to make paraview repartition the read > in data amongst the processors. I did the following to start a single pvserver on each of two hosts: $ mpirun r219i0n0,r219i0n1 -np 1 /usr/bin/env DISPLAY=:0 /u/jcbecker/ParaView-4.3.1-Linux-64bit/bin/pvserver --client-host=pfe20 --use-offscreen-rendering After I connected to the first pvserver, and opened the file, I tried to apply the D3 filter, but it was grayed out. -jeff > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Jun 10 13:30:31 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 10 Jun 2015 17:30:31 +0000 Subject: [Paraview] pvserver segfault In-Reply-To: <557873FE.4080908@nasa.gov> References: <5577834B.5050408@nasa.gov> <5578703A.7070503@nasa.gov> <557873FE.4080908@nasa.gov> Message-ID: Jeff, D3 is available only when there's more than 1 MPI rank. There's no need to do any load balancing with just 1 rank. Utkarsh On Wed, Jun 10, 2015 at 1:29 PM Jeff Becker wrote: > On 06/10/2015 10:16 AM, David E DeMarle wrote: > > > On Wed, Jun 10, 2015 at 1:13 PM, Jeff Becker > wrote: > >> I'm assuming the file gets read on the first one, and it splits up the >> grid among all the servers? > > > It is up to the specific reader class to decide what to do so who exactly > reads what depends on the file type. If the data is not well distributed, > apply the D3 filter to make paraview repartition the read in data amongst > the processors. > > > I did the following to start a single pvserver on each of two hosts: > > $ mpirun r219i0n0,r219i0n1 -np 1 /usr/bin/env DISPLAY=:0 > /u/jcbecker/ParaView-4.3.1-Linux-64bit/bin/pvserver --client-host=pfe20 > --use-offscreen-rendering > > After I connected to the first pvserver, and opened the file, I tried to > apply the D3 filter, but it was grayed out. > > > -jeff > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffrey.c.becker at nasa.gov Wed Jun 10 13:33:39 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Wed, 10 Jun 2015 10:33:39 -0700 Subject: [Paraview] pvserver segfault In-Reply-To: References: <5577834B.5050408@nasa.gov> <5578703A.7070503@nasa.gov> <557873FE.4080908@nasa.gov> Message-ID: <557874F3.9080101@nasa.gov> On 06/10/2015 10:30 AM, Utkarsh Ayachit wrote: > Jeff, > > D3 is available only when there's more than 1 MPI rank. There's no > need to do any load balancing with just 1 rank. But I'm using 1 rank on each of two nodes (r219i0n0,r219i0n1) -jeff > > Utkarsh > > On Wed, Jun 10, 2015 at 1:29 PM Jeff Becker > wrote: > > On 06/10/2015 10:16 AM, David E DeMarle wrote: >> >> On Wed, Jun 10, 2015 at 1:13 PM, Jeff Becker >> > wrote: >> >> I'm assuming the file gets read on the first one, and it >> splits up the grid among all the servers? >> >> >> It is up to the specific reader class to decide what to do so who >> exactly reads what depends on the file type. If the data is not >> well distributed, apply the D3 filter to make paraview >> repartition the read in data amongst the processors. > > I did the following to start a single pvserver on each of two hosts: > > $ mpirun r219i0n0,r219i0n1 -np 1 /usr/bin/env DISPLAY=:0 > /u/jcbecker/ParaView-4.3.1-Linux-64bit/bin/pvserver > --client-host=pfe20 --use-offscreen-rendering > > After I connected to the first pvserver, and opened the file, I > tried to apply the D3 filter, but it was grayed out. > > > -jeff > >> >> David E DeMarle >> Kitware, Inc. >> R&D Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Jun 10 13:34:35 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 10 Jun 2015 13:34:35 -0400 Subject: [Paraview] pvserver segfault In-Reply-To: References: <5577834B.5050408@nasa.gov> <5578703A.7070503@nasa.gov> <557873FE.4080908@nasa.gov> Message-ID: In general a greyed out filter means that one of its input preconditions is not satisfied. In this case D3 needs more than 1 rank, but if the input was a structured data set instead of an unstructured one then that would disable it too. In windows and linux there should be text in the bottom left of the app that explains when you mouse over a disabled filter. Otherwise you have to look at the help for the filter in question and figure it out. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Jun 10, 2015 at 1:30 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Jeff, > > D3 is available only when there's more than 1 MPI rank. There's no need to > do any load balancing with just 1 rank. > > Utkarsh > > On Wed, Jun 10, 2015 at 1:29 PM Jeff Becker > wrote: > >> On 06/10/2015 10:16 AM, David E DeMarle wrote: >> >> >> On Wed, Jun 10, 2015 at 1:13 PM, Jeff Becker >> wrote: >> >>> I'm assuming the file gets read on the first one, and it splits up the >>> grid among all the servers? >> >> >> It is up to the specific reader class to decide what to do so who exactly >> reads what depends on the file type. If the data is not well distributed, >> apply the D3 filter to make paraview repartition the read in data amongst >> the processors. >> >> >> I did the following to start a single pvserver on each of two hosts: >> >> $ mpirun r219i0n0,r219i0n1 -np 1 /usr/bin/env DISPLAY=:0 >> /u/jcbecker/ParaView-4.3.1-Linux-64bit/bin/pvserver --client-host=pfe20 >> --use-offscreen-rendering >> >> After I connected to the first pvserver, and opened the file, I tried to >> apply the D3 filter, but it was grayed out. >> >> >> -jeff >> >> >> David E DeMarle >> Kitware, Inc. >> R&D Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Jun 10 13:35:55 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 10 Jun 2015 13:35:55 -0400 Subject: [Paraview] pvserver segfault In-Reply-To: References: <5577834B.5050408@nasa.gov> <5578703A.7070503@nasa.gov> <557873FE.4080908@nasa.gov> Message-ID: "mpirun r219i0n0,r219i0n1 -np 1?" should be "mpirun r219i0n0,r219i0n1 -np 2..." no? David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Jun 10, 2015 at 1:34 PM, David E DeMarle wrote: > In general a greyed out filter means that one of its input preconditions > is not satisfied. In this case D3 needs more than 1 rank, but if the input > was a structured data set instead of an unstructured one then that would > disable it too. > > In windows and linux there should be text in the bottom left of the app > that explains when you mouse over a disabled filter. Otherwise you have to > look at the help for the filter in question and figure it out. > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Wed, Jun 10, 2015 at 1:30 PM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> Jeff, >> >> D3 is available only when there's more than 1 MPI rank. There's no need >> to do any load balancing with just 1 rank. >> >> Utkarsh >> >> On Wed, Jun 10, 2015 at 1:29 PM Jeff Becker >> wrote: >> >>> On 06/10/2015 10:16 AM, David E DeMarle wrote: >>> >>> >>> On Wed, Jun 10, 2015 at 1:13 PM, Jeff Becker >>> wrote: >>> >>>> I'm assuming the file gets read on the first one, and it splits up the >>>> grid among all the servers? >>> >>> >>> It is up to the specific reader class to decide what to do so who >>> exactly reads what depends on the file type. If the data is not well >>> distributed, apply the D3 filter to make paraview repartition the read in >>> data amongst the processors. >>> >>> >>> I did the following to start a single pvserver on each of two hosts: >>> >>> $ mpirun r219i0n0,r219i0n1 -np 1 /usr/bin/env DISPLAY=:0 >>> /u/jcbecker/ParaView-4.3.1-Linux-64bit/bin/pvserver --client-host=pfe20 >>> --use-offscreen-rendering >>> >>> After I connected to the first pvserver, and opened the file, I tried to >>> apply the D3 filter, but it was grayed out. >>> >>> >>> -jeff >>> >>> >>> David E DeMarle >>> Kitware, Inc. >>> R&D Engineer >>> 21 Corporate Drive >>> Clifton Park, NY 12065-8662 >>> Phone: 518-881-4909 >>> >>> >>> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Jun 10 13:47:52 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 10 Jun 2015 17:47:52 +0000 Subject: [Paraview] pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0 In-Reply-To: <10e5a92c2de8b3c9c685221b8c714f86@peterheppel.com> References: <10e5a92c2de8b3c9c685221b8c714f86@peterheppel.com> Message-ID: I am not sure I follow what's happening here. Can you provide details on what you're doing here please? Thanks. Utkarsh On Wed, Jun 10, 2015 at 11:38 AM Peter wrote: > Hello > > I just built the current Paraview development version and got the same > error on running the Catalyst examples. > > Paraview declined the connection gracefully when the client was built with > a different VTK version, so I suspect the issue isnt related to the socket > handshake, but rather that it only occurs after the socket connection is > successful. > > P > > > > -- > Peter Heppel > 35/37 Rue de Locmalo > 56290 Port-Louis > France > +33 6 81 30 76 52 cell > +33 2 97 82 19 30 > USA +1 773 280 8142 > Skype: peterheppel > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffrey.c.becker at nasa.gov Wed Jun 10 14:00:37 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Wed, 10 Jun 2015 11:00:37 -0700 Subject: [Paraview] Selecting volume rendering causes output to vanish Message-ID: <55787B45.4000606@nasa.gov> Hi. I have an unstructured grid file that opens and displays in Surface Rendering mode. If I switch to Volume Rendering, I don't see any output. Any ideas? Thanks. -jeff From burlen.loring at gmail.com Wed Jun 10 14:06:01 2015 From: burlen.loring at gmail.com (Burlen Loring) Date: Wed, 10 Jun 2015 11:06:01 -0700 Subject: [Paraview] Selecting volume rendering causes output to vanish In-Reply-To: <55787B45.4000606@nasa.gov> References: <55787B45.4000606@nasa.gov> Message-ID: <55787C89.5080409@gmail.com> 2 things to try: set the remote render threshold to zero, and if that doesn't get it to show up, change the mapper to Bunyk ray cast. One of those usually works depending on what the cause of the issue is. On 06/10/2015 11:00 AM, Jeff Becker wrote: > Hi. I have an unstructured grid file that opens and displays in > Surface Rendering mode. If I switch to Volume Rendering, I don't see > any output. Any ideas? > > Thanks. > > -jeff > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From aashish.chaudhary at kitware.com Wed Jun 10 14:07:24 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Wed, 10 Jun 2015 14:07:24 -0400 Subject: [Paraview] Selecting volume rendering causes output to vanish In-Reply-To: <55787C89.5080409@gmail.com> References: <55787B45.4000606@nasa.gov> <55787C89.5080409@gmail.com> Message-ID: What version of ParaView you are using? Also, OpenGL or OpenGL2 backend? Any information on Hardware might be helpful as well. - aashish On Wed, Jun 10, 2015 at 2:06 PM, Burlen Loring wrote: > 2 things to try: set the remote render threshold to zero, and if that > doesn't get it to show up, change the mapper to Bunyk ray cast. One of > those usually works depending on what the cause of the issue is. > > > On 06/10/2015 11:00 AM, Jeff Becker wrote: > >> Hi. I have an unstructured grid file that opens and displays in Surface >> Rendering mode. If I switch to Volume Rendering, I don't see any output. >> Any ideas? >> >> Thanks. >> >> -jeff >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffrey.c.becker at nasa.gov Wed Jun 10 14:27:14 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Wed, 10 Jun 2015 11:27:14 -0700 Subject: [Paraview] Selecting volume rendering causes output to vanish In-Reply-To: <55787C89.5080409@gmail.com> References: <55787B45.4000606@nasa.gov> <55787C89.5080409@gmail.com> Message-ID: <55788182.4040206@nasa.gov> On 06/10/2015 11:06 AM, Burlen Loring wrote: > 2 things to try: set the remote render threshold to zero, and if that > doesn't get it to show up, change the mapper to Bunyk ray cast. One > of those usually works depending on what the cause of the issue is. I have both of those set - no luck. BTW, this is ParaView 4.3.1 on an NVIDIA backend. glxinfo shows: $ glxinfo | head -30 name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: NVIDIA Corporation server glx version string: 1.4 server glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile, GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness, GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, GLX_ARB_multisample, GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB, GLX_NV_multisample_coverage client glx vendor string: NVIDIA Corporation client glx version string: 1.4 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync, GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_buffer_age, GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float, GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB, GLX_NV_present_video, GLX_NV_copy_image, GLX_NV_multisample_coverage, GLX_NV_video_capture, GLX_EXT_create_context_es_profile, GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness, GLX_NV_delay_before_swap, GLX_EXT_stereo_tree > > On 06/10/2015 11:00 AM, Jeff Becker wrote: >> Hi. I have an unstructured grid file that opens and displays in >> Surface Rendering mode. If I switch to Volume Rendering, I don't see >> any output. Any ideas? >> >> Thanks. >> >> -jeff >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > From aashish.chaudhary at kitware.com Wed Jun 10 14:30:46 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Wed, 10 Jun 2015 14:30:46 -0400 Subject: [Paraview] Selecting volume rendering causes output to vanish In-Reply-To: <55788182.4040206@nasa.gov> References: <55787B45.4000606@nasa.gov> <55787C89.5080409@gmail.com> <55788182.4040206@nasa.gov> Message-ID: Can you send the entire output of glxinfo? - Aashish On Wed, Jun 10, 2015 at 2:27 PM, Jeff Becker wrote: > On 06/10/2015 11:06 AM, Burlen Loring wrote: > >> 2 things to try: set the remote render threshold to zero, and if that >> doesn't get it to show up, change the mapper to Bunyk ray cast. One of >> those usually works depending on what the cause of the issue is. >> > > I have both of those set - no luck. BTW, this is ParaView 4.3.1 on an > NVIDIA backend. glxinfo shows: > > $ glxinfo | head -30 > name of display: :0.0 > display: :0 screen: 0 > direct rendering: Yes > server glx vendor string: NVIDIA Corporation > server glx version string: 1.4 > server glx extensions: > GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, > GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, > GLX_EXT_swap_control, GLX_EXT_swap_control_tear, > GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, > GLX_ARB_create_context, > GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile, > GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness, > GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, GLX_ARB_multisample, > GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB, > GLX_NV_multisample_coverage > client glx vendor string: NVIDIA Corporation > client glx version string: 1.4 > client glx extensions: > GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info, > GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync, > GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, > GLX_SGIX_pbuffer, > GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, > GLX_EXT_buffer_age, GLX_ARB_create_context, > GLX_ARB_create_context_profile, GLX_NV_float_buffer, > GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float, > GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB, > GLX_NV_present_video, GLX_NV_copy_image, GLX_NV_multisample_coverage, > GLX_NV_video_capture, GLX_EXT_create_context_es_profile, > GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness, > GLX_NV_delay_before_swap, GLX_EXT_stereo_tree > > > >> On 06/10/2015 11:00 AM, Jeff Becker wrote: >> >>> Hi. I have an unstructured grid file that opens and displays in Surface >>> Rendering mode. If I switch to Volume Rendering, I don't see any output. >>> Any ideas? >>> >>> Thanks. >>> >>> -jeff >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >> >> > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Wed Jun 10 14:46:52 2015 From: burlen.loring at gmail.com (Burlen Loring) Date: Wed, 10 Jun 2015 11:46:52 -0700 Subject: [Paraview] Selecting volume rendering causes output to vanish In-Reply-To: <55788182.4040206@nasa.gov> References: <55787B45.4000606@nasa.gov> <55787C89.5080409@gmail.com> <55788182.4040206@nasa.gov> Message-ID: <5578861C.4060407@gmail.com> Hmm. If Bunyk ray cast doesn't work some thing strange is going on as that is a software(non gpu) algorithm and should always work. Can you get anything to show up using a small test data? For example create a wavelet source and apply a threshold (use default values) to convert to unstructured data. If that works maybe something with your input data, or size of it. On 06/10/2015 11:27 AM, Jeff Becker wrote: > On 06/10/2015 11:06 AM, Burlen Loring wrote: >> 2 things to try: set the remote render threshold to zero, and if that >> doesn't get it to show up, change the mapper to Bunyk ray cast. One >> of those usually works depending on what the cause of the issue is. > > I have both of those set - no luck. BTW, this is ParaView 4.3.1 on an > NVIDIA backend. glxinfo shows: > > $ glxinfo | head -30 > name of display: :0.0 > display: :0 screen: 0 > direct rendering: Yes > server glx vendor string: NVIDIA Corporation > server glx version string: 1.4 > server glx extensions: > GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, > GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, > GLX_EXT_swap_control, GLX_EXT_swap_control_tear, > GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, > GLX_ARB_create_context, > GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile, > GLX_EXT_create_context_es2_profile, > GLX_ARB_create_context_robustness, > GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, GLX_ARB_multisample, > GLX_NV_float_buffer, GLX_ARB_fbconfig_float, > GLX_EXT_framebuffer_sRGB, > GLX_NV_multisample_coverage > client glx vendor string: NVIDIA Corporation > client glx version string: 1.4 > client glx extensions: > GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info, > GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync, > GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, > GLX_SGIX_pbuffer, > GLX_SGI_swap_control, GLX_EXT_swap_control, > GLX_EXT_swap_control_tear, > GLX_EXT_buffer_age, GLX_ARB_create_context, > GLX_ARB_create_context_profile, GLX_NV_float_buffer, > GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float, > GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB, > GLX_NV_present_video, GLX_NV_copy_image, GLX_NV_multisample_coverage, > GLX_NV_video_capture, GLX_EXT_create_context_es_profile, > GLX_EXT_create_context_es2_profile, > GLX_ARB_create_context_robustness, > GLX_NV_delay_before_swap, GLX_EXT_stereo_tree > >> >> On 06/10/2015 11:00 AM, Jeff Becker wrote: >>> Hi. I have an unstructured grid file that opens and displays in >>> Surface Rendering mode. If I switch to Volume Rendering, I don't see >>> any output. Any ideas? >>> >>> Thanks. >>> >>> -jeff >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> > From jeffrey.c.becker at nasa.gov Wed Jun 10 14:49:10 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Wed, 10 Jun 2015 11:49:10 -0700 Subject: [Paraview] Selecting volume rendering causes output to vanish In-Reply-To: <5578861C.4060407@gmail.com> References: <55787B45.4000606@nasa.gov> <55787C89.5080409@gmail.com> <55788182.4040206@nasa.gov> <5578861C.4060407@gmail.com> Message-ID: <557886A6.5080606@nasa.gov> On 06/10/2015 11:46 AM, Burlen Loring wrote: > Hmm. If Bunyk ray cast doesn't work some thing strange is going on as > that is a software(non gpu) algorithm and should always work. > > Can you get anything to show up using a small test data? For example > create a wavelet source and apply a threshold (use default values) to > convert to unstructured data. If that works maybe something with your > input data, or size of it. It's a 500 by 500 by 500 grid of floats - is that too big? > > On 06/10/2015 11:27 AM, Jeff Becker wrote: >> On 06/10/2015 11:06 AM, Burlen Loring wrote: >>> 2 things to try: set the remote render threshold to zero, and if >>> that doesn't get it to show up, change the mapper to Bunyk ray >>> cast. One of those usually works depending on what the cause of the >>> issue is. >> >> I have both of those set - no luck. BTW, this is ParaView 4.3.1 on an >> NVIDIA backend. glxinfo shows: >> >> $ glxinfo | head -30 >> name of display: :0.0 >> display: :0 screen: 0 >> direct rendering: Yes >> server glx vendor string: NVIDIA Corporation >> server glx version string: 1.4 >> server glx extensions: >> GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, >> GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, >> GLX_EXT_swap_control, GLX_EXT_swap_control_tear, >> GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, >> GLX_ARB_create_context, >> GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile, >> GLX_EXT_create_context_es2_profile, >> GLX_ARB_create_context_robustness, >> GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, GLX_ARB_multisample, >> GLX_NV_float_buffer, GLX_ARB_fbconfig_float, >> GLX_EXT_framebuffer_sRGB, >> GLX_NV_multisample_coverage >> client glx vendor string: NVIDIA Corporation >> client glx version string: 1.4 >> client glx extensions: >> GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info, >> GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync, >> GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, >> GLX_SGIX_pbuffer, >> GLX_SGI_swap_control, GLX_EXT_swap_control, >> GLX_EXT_swap_control_tear, >> GLX_EXT_buffer_age, GLX_ARB_create_context, >> GLX_ARB_create_context_profile, GLX_NV_float_buffer, >> GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float, >> GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB, >> GLX_NV_present_video, GLX_NV_copy_image, >> GLX_NV_multisample_coverage, >> GLX_NV_video_capture, GLX_EXT_create_context_es_profile, >> GLX_EXT_create_context_es2_profile, >> GLX_ARB_create_context_robustness, >> GLX_NV_delay_before_swap, GLX_EXT_stereo_tree >> >>> >>> On 06/10/2015 11:00 AM, Jeff Becker wrote: >>>> Hi. I have an unstructured grid file that opens and displays in >>>> Surface Rendering mode. If I switch to Volume Rendering, I don't >>>> see any output. Any ideas? >>>> >>>> Thanks. >>>> >>>> -jeff >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>> >> > From aashish.chaudhary at kitware.com Wed Jun 10 14:58:26 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Wed, 10 Jun 2015 14:58:26 -0400 Subject: [Paraview] Selecting volume rendering causes output to vanish In-Reply-To: <557886A6.5080606@nasa.gov> References: <55787B45.4000606@nasa.gov> <55787C89.5080409@gmail.com> <55788182.4040206@nasa.gov> <5578861C.4060407@gmail.com> <557886A6.5080606@nasa.gov> Message-ID: No, I don't think so. It would be nice if you can try Burlen suggestion to see if it works for built in datasets / sources. - Aashish On Wed, Jun 10, 2015 at 2:49 PM, Jeff Becker wrote: > On 06/10/2015 11:46 AM, Burlen Loring wrote: > >> Hmm. If Bunyk ray cast doesn't work some thing strange is going on as >> that is a software(non gpu) algorithm and should always work. >> >> Can you get anything to show up using a small test data? For example >> create a wavelet source and apply a threshold (use default values) to >> convert to unstructured data. If that works maybe something with your input >> data, or size of it. >> > > It's a 500 by 500 by 500 grid of floats - is that too big? > > >> On 06/10/2015 11:27 AM, Jeff Becker wrote: >> >>> On 06/10/2015 11:06 AM, Burlen Loring wrote: >>> >>>> 2 things to try: set the remote render threshold to zero, and if that >>>> doesn't get it to show up, change the mapper to Bunyk ray cast. One of >>>> those usually works depending on what the cause of the issue is. >>>> >>> >>> I have both of those set - no luck. BTW, this is ParaView 4.3.1 on an >>> NVIDIA backend. glxinfo shows: >>> >>> $ glxinfo | head -30 >>> name of display: :0.0 >>> display: :0 screen: 0 >>> direct rendering: Yes >>> server glx vendor string: NVIDIA Corporation >>> server glx version string: 1.4 >>> server glx extensions: >>> GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, >>> GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, >>> GLX_EXT_swap_control, GLX_EXT_swap_control_tear, >>> GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, >>> GLX_ARB_create_context, >>> GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile, >>> GLX_EXT_create_context_es2_profile, >>> GLX_ARB_create_context_robustness, >>> GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, GLX_ARB_multisample, >>> GLX_NV_float_buffer, GLX_ARB_fbconfig_float, >>> GLX_EXT_framebuffer_sRGB, >>> GLX_NV_multisample_coverage >>> client glx vendor string: NVIDIA Corporation >>> client glx version string: 1.4 >>> client glx extensions: >>> GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info, >>> GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync, >>> GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, >>> GLX_SGIX_pbuffer, >>> GLX_SGI_swap_control, GLX_EXT_swap_control, >>> GLX_EXT_swap_control_tear, >>> GLX_EXT_buffer_age, GLX_ARB_create_context, >>> GLX_ARB_create_context_profile, GLX_NV_float_buffer, >>> GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float, >>> GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB, >>> GLX_NV_present_video, GLX_NV_copy_image, GLX_NV_multisample_coverage, >>> GLX_NV_video_capture, GLX_EXT_create_context_es_profile, >>> GLX_EXT_create_context_es2_profile, >>> GLX_ARB_create_context_robustness, >>> GLX_NV_delay_before_swap, GLX_EXT_stereo_tree >>> >>> >>>> On 06/10/2015 11:00 AM, Jeff Becker wrote: >>>> >>>>> Hi. I have an unstructured grid file that opens and displays in >>>>> Surface Rendering mode. If I switch to Volume Rendering, I don't see any >>>>> output. Any ideas? >>>>> >>>>> Thanks. >>>>> >>>>> -jeff >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>> >>>> >>> >> > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Jun 10 15:03:38 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 10 Jun 2015 15:03:38 -0400 Subject: [Paraview] Selecting volume rendering causes output to vanish In-Reply-To: References: <55787B45.4000606@nasa.gov> <55787C89.5080409@gmail.com> <55788182.4040206@nasa.gov> <5578861C.4060407@gmail.com> <557886A6.5080606@nasa.gov> Message-ID: Probably the content isn't amenable to volume rendering. To be so, the unstructured grid has to have volumetric cells in it (tets, voxels, etc). If it just has polys or lines or points in it, they won't appear. You'll have to resample of splat onto the data onto a volumetric grid in that case. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Jun 10, 2015 at 2:58 PM, Aashish Chaudhary < aashish.chaudhary at kitware.com> wrote: > No, I don't think so. It would be nice if you can try Burlen suggestion to > see if it works for built in datasets / sources. > > - Aashish > > On Wed, Jun 10, 2015 at 2:49 PM, Jeff Becker > wrote: > >> On 06/10/2015 11:46 AM, Burlen Loring wrote: >> >>> Hmm. If Bunyk ray cast doesn't work some thing strange is going on as >>> that is a software(non gpu) algorithm and should always work. >>> >>> Can you get anything to show up using a small test data? For example >>> create a wavelet source and apply a threshold (use default values) to >>> convert to unstructured data. If that works maybe something with your input >>> data, or size of it. >>> >> >> It's a 500 by 500 by 500 grid of floats - is that too big? >> >> >>> On 06/10/2015 11:27 AM, Jeff Becker wrote: >>> >>>> On 06/10/2015 11:06 AM, Burlen Loring wrote: >>>> >>>>> 2 things to try: set the remote render threshold to zero, and if that >>>>> doesn't get it to show up, change the mapper to Bunyk ray cast. One of >>>>> those usually works depending on what the cause of the issue is. >>>>> >>>> >>>> I have both of those set - no luck. BTW, this is ParaView 4.3.1 on an >>>> NVIDIA backend. glxinfo shows: >>>> >>>> $ glxinfo | head -30 >>>> name of display: :0.0 >>>> display: :0 screen: 0 >>>> direct rendering: Yes >>>> server glx vendor string: NVIDIA Corporation >>>> server glx version string: 1.4 >>>> server glx extensions: >>>> GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, >>>> GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, >>>> GLX_EXT_swap_control, GLX_EXT_swap_control_tear, >>>> GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, >>>> GLX_ARB_create_context, >>>> GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile, >>>> GLX_EXT_create_context_es2_profile, >>>> GLX_ARB_create_context_robustness, >>>> GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, GLX_ARB_multisample, >>>> GLX_NV_float_buffer, GLX_ARB_fbconfig_float, >>>> GLX_EXT_framebuffer_sRGB, >>>> GLX_NV_multisample_coverage >>>> client glx vendor string: NVIDIA Corporation >>>> client glx version string: 1.4 >>>> client glx extensions: >>>> GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info, >>>> GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync, >>>> GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, >>>> GLX_SGIX_pbuffer, >>>> GLX_SGI_swap_control, GLX_EXT_swap_control, >>>> GLX_EXT_swap_control_tear, >>>> GLX_EXT_buffer_age, GLX_ARB_create_context, >>>> GLX_ARB_create_context_profile, GLX_NV_float_buffer, >>>> GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float, >>>> GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB, >>>> GLX_NV_present_video, GLX_NV_copy_image, >>>> GLX_NV_multisample_coverage, >>>> GLX_NV_video_capture, GLX_EXT_create_context_es_profile, >>>> GLX_EXT_create_context_es2_profile, >>>> GLX_ARB_create_context_robustness, >>>> GLX_NV_delay_before_swap, GLX_EXT_stereo_tree >>>> >>>> >>>>> On 06/10/2015 11:00 AM, Jeff Becker wrote: >>>>> >>>>>> Hi. I have an unstructured grid file that opens and displays in >>>>>> Surface Rendering mode. If I switch to Volume Rendering, I don't see any >>>>>> output. Any ideas? >>>>>> >>>>>> Thanks. >>>>>> >>>>>> -jeff >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>> >>>>> >>>> >>> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > > > -- > > > > *| Aashish Chaudhary | Technical Leader | Kitware Inc. * > *| http://www.kitware.com/company/team/chaudhary.html > * > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Wed Jun 10 15:22:34 2015 From: burlen.loring at gmail.com (Burlen Loring) Date: Wed, 10 Jun 2015 12:22:34 -0700 Subject: [Paraview] Selecting volume rendering causes output to vanish In-Reply-To: References: <55787B45.4000606@nasa.gov> <55787C89.5080409@gmail.com> <55788182.4040206@nasa.gov> <5578861C.4060407@gmail.com> <557886A6.5080606@nasa.gov> Message-ID: <55788E7A.3090406@gmail.com> 500^3 should not be an issue. Still worth seeing if you can get the test data from wavelet source to display as a sanity check. Another thing that occasionally occurs, if the there is one or two extremely large outlying values in your dataset (say from writing random unitialized memory), the default transfer function makes the dataset invisible. Would be worth checking the range of your data and experimenting with transfer function as well. On 06/10/2015 12:03 PM, David E DeMarle wrote: > Probably the content isn't amenable to volume rendering. To be so, the > unstructured grid has to have volumetric cells in it (tets, voxels, > etc). If it just has polys or lines or points in it, they won't > appear. You'll have to resample of splat onto the data onto a > volumetric grid in that case. > > > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Wed, Jun 10, 2015 at 2:58 PM, Aashish Chaudhary > > > wrote: > > No, I don't think so. It would be nice if you can try Burlen > suggestion to see if it works for built in datasets / sources. > > - Aashish > > On Wed, Jun 10, 2015 at 2:49 PM, Jeff Becker > > wrote: > > On 06/10/2015 11:46 AM, Burlen Loring wrote: > > Hmm. If Bunyk ray cast doesn't work some thing strange is > going on as that is a software(non gpu) algorithm and > should always work. > > Can you get anything to show up using a small test data? > For example create a wavelet source and apply a threshold > (use default values) to convert to unstructured data. If > that works maybe something with your input data, or size > of it. > > > It's a 500 by 500 by 500 grid of floats - is that too big? > > > On 06/10/2015 11:27 AM, Jeff Becker wrote: > > On 06/10/2015 11:06 AM, Burlen Loring wrote: > > 2 things to try: set the remote render threshold > to zero, and if that doesn't get it to show up, > change the mapper to Bunyk ray cast. One of those > usually works depending on what the cause of the > issue is. > > > I have both of those set - no luck. BTW, this is > ParaView 4.3.1 on an NVIDIA backend. glxinfo shows: > > $ glxinfo | head -30 > name of display: :0.0 > display: :0 screen: 0 > direct rendering: Yes > server glx vendor string: NVIDIA Corporation > server glx version string: 1.4 > server glx extensions: > GLX_EXT_visual_info, GLX_EXT_visual_rating, > GLX_SGIX_fbconfig, > GLX_SGIX_pbuffer, GLX_SGI_video_sync, > GLX_SGI_swap_control, > GLX_EXT_swap_control, GLX_EXT_swap_control_tear, > GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, > GLX_ARB_create_context, > GLX_ARB_create_context_profile, > GLX_EXT_create_context_es_profile, > GLX_EXT_create_context_es2_profile, > GLX_ARB_create_context_robustness, > GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, > GLX_ARB_multisample, > GLX_NV_float_buffer, GLX_ARB_fbconfig_float, > GLX_EXT_framebuffer_sRGB, > GLX_NV_multisample_coverage > client glx vendor string: NVIDIA Corporation > client glx version string: 1.4 > client glx extensions: > GLX_ARB_get_proc_address, GLX_ARB_multisample, > GLX_EXT_visual_info, > GLX_EXT_visual_rating, GLX_EXT_import_context, > GLX_SGI_video_sync, > GLX_NV_swap_group, GLX_NV_video_out, > GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, > GLX_SGI_swap_control, GLX_EXT_swap_control, > GLX_EXT_swap_control_tear, > GLX_EXT_buffer_age, GLX_ARB_create_context, > GLX_ARB_create_context_profile, GLX_NV_float_buffer, > GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float, > GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB, > GLX_NV_present_video, GLX_NV_copy_image, > GLX_NV_multisample_coverage, > GLX_NV_video_capture, > GLX_EXT_create_context_es_profile, > GLX_EXT_create_context_es2_profile, > GLX_ARB_create_context_robustness, > GLX_NV_delay_before_swap, GLX_EXT_stereo_tree > > > On 06/10/2015 11:00 AM, Jeff Becker wrote: > > Hi. I have an unstructured grid file that > opens and displays in Surface Rendering mode. > If I switch to Volume Rendering, I don't see > any output. Any ideas? > > Thanks. > > -jeff > _______________________________________________ > Powered by www.kitware.com > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the > ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: > http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: > http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > -- > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. > / > /| http://www.kitware.com/company/team/chaudhary.html/ > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Jun 10 15:24:13 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 10 Jun 2015 19:24:13 +0000 Subject: [Paraview] [EXTERNAL] Re: Selecting volume rendering causes output to vanish References: <55787B45.4000606@nasa.gov> <55787C89.5080409@gmail.com> <55788182.4040206@nasa.gov> <5578861C.4060407@gmail.com> <557886A6.5080606@nasa.gov> Message-ID: <319d2dd8abd240f9bfb732bc2b11f1f5@ES01AMSNLNT.srn.sandia.gov> I tried this with an attachment, it was too big. Here is the e-mail without the attachment. Alan From: Scott, W Alan Sent: Wednesday, June 10, 2015 1:07 PM To: 'Aashish Chaudhary'; Jeff Becker Cc: ParaView Subject: RE: [EXTERNAL] Re: [Paraview] Selecting volume rendering causes output to vanish I believe I have seen this before when the config files get messed up. Here is what I just did, and the image that results: (Sorry if I missed your already having tried this in this e-mail thread) ? rm files in ~/.config/ParaView. (You can also just run ParaView with ?don?t load config files? mode.) ? ./paraview (make sure you are running the version of ParaView you think you are). (if you want to not load config files, use ./paraview ?dr) ? Sources/ Wavelet. Apply. (It will show outline mode) ? Change Outline to Volume. (ParaView will automagically change the variable used to RTData). Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Aashish Chaudhary Sent: Wednesday, June 10, 2015 12:58 PM To: Jeff Becker Cc: ParaView Subject: [EXTERNAL] Re: [Paraview] Selecting volume rendering causes output to vanish No, I don't think so. It would be nice if you can try Burlen suggestion to see if it works for built in datasets / sources. - Aashish On Wed, Jun 10, 2015 at 2:49 PM, Jeff Becker > wrote: On 06/10/2015 11:46 AM, Burlen Loring wrote: Hmm. If Bunyk ray cast doesn't work some thing strange is going on as that is a software(non gpu) algorithm and should always work. Can you get anything to show up using a small test data? For example create a wavelet source and apply a threshold (use default values) to convert to unstructured data. If that works maybe something with your input data, or size of it. It's a 500 by 500 by 500 grid of floats - is that too big? On 06/10/2015 11:27 AM, Jeff Becker wrote: On 06/10/2015 11:06 AM, Burlen Loring wrote: 2 things to try: set the remote render threshold to zero, and if that doesn't get it to show up, change the mapper to Bunyk ray cast. One of those usually works depending on what the cause of the issue is. I have both of those set - no luck. BTW, this is ParaView 4.3.1 on an NVIDIA backend. glxinfo shows: $ glxinfo | head -30 name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: NVIDIA Corporation server glx version string: 1.4 server glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile, GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness, GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, GLX_ARB_multisample, GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB, GLX_NV_multisample_coverage client glx vendor string: NVIDIA Corporation client glx version string: 1.4 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync, GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_buffer_age, GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float, GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB, GLX_NV_present_video, GLX_NV_copy_image, GLX_NV_multisample_coverage, GLX_NV_video_capture, GLX_EXT_create_context_es_profile, GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness, GLX_NV_delay_before_swap, GLX_EXT_stereo_tree On 06/10/2015 11:00 AM, Jeff Becker wrote: Hi. I have an unstructured grid file that opens and displays in Surface Rendering mode. If I switch to Volume Rendering, I don't see any output. Any ideas? Thanks. -jeff _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From haonrolyat at gmail.com Wed Jun 10 15:34:30 2015 From: haonrolyat at gmail.com (Noah Taylor) Date: Wed, 10 Jun 2015 13:34:30 -0600 Subject: [Paraview] ParaView 4.0.1 Not Compiling for Python, MPI, Llvm In-Reply-To: References: Message-ID: Scott, I have setup a GPU instance and am trying to use the instructions give but when I use X or glxinfo when the Display is pointed to 0.0, I get an erro that says couldn't open display :0.0. Did anybody else run into this problem on the GPU AWS node? Noah On Mon, Jun 8, 2015 at 10:32 PM, Noah Taylor wrote: > Scott, > > Thank you very much! The documentation looks to be well written. > > Cheers, > Noah > > On Mon, Jun 8, 2015 at 9:41 AM, Scott Wittenburg < > scott.wittenburg at kitware.com> wrote: > >> Hi Noah, >> >> I don't see the specific link error message in your email, but it >> seems possible it could be related to your graphics environment. We often >> have to compile ParaView on amazon EC2 instances when setting up >> ParaViewWeb, and some of the guides for that may end up being useful to >> you, specifically: >> >> >> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/graphics_on_ec2_g2 >> >> and >> >> >> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ubuntu_14_04 >> >> Cheers, >> Scott >> >> >> On Sat, Jun 6, 2015 at 9:44 PM, Noah Taylor wrote: >> >>> Hello, >>> >>> I've been trying to compile this for a couple of weeks now but am >>> running into some unknown troubles. My build gets to ~50% and kicks out an >>> error as follows: >>> >>> collect2: error: ld returned 1 exit status >>> make[2]: *** [lib/libvtkRenderingOpenGL-pv4.0.so.1] Error 1 >>> make[1]: *** >>> [VTK/Rendering/OpenGL/CMakeFiles/vtkRenderingOpenGL.dir/all] Error 2 >>> make[1]: *** Waiting for unfinished jobs.... >>> >>> I tried locating the libvtkRenderingOpenGL-pv4.0.so.1 and it wasn't >>> anywhere on my machine and I have googled this library but I cannot find a >>> solution. >>> >>> My ccmake options are as follows (I'm just trying to compile on a ubuntu >>> aws node): >>> >>> BUILD_DOCUMENTATION OFF >>> >>> BUILD_EXAMPLES OFF >>> >>> BUILD_SHARED_LIBS ON >>> >>> BUILD_TESTING ON >>> >>> CMAKE_BUILD_TYPE Debug >>> >>> CMAKE_INSTALL_PREFIX /usr/local >>> >>> GMVReader_GMVREAD_LIB_DIR >>> /mnt/ParaView-v4.0.1-source/Utilities/VisItBridge/databases/GMV >>> >>> GMVReader_SKIP_DATARANGE_CALCU OFF >>> >>> MPI_C_INCLUDE_PATH >>> /usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi >>> >>> MPI_C_LIBRARIES >>> /usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so >>> >>> >>> PARAVIEW_BUILD_QT_GUI OFF >>> >>> PARAVIEW_DATA_ROOT PARAVIEW_DATA_ROOT-NOTFOUND >>> >>> PARAVIEW_ENABLE_CATALYST ON >>> >>> PARAVIEW_ENABLE_FFMPEG OFF >>> >>> PARAVIEW_ENABLE_PYTHON ON >>> >>> PARAVIEW_ENABLE_QT_SUPPORT OFF >>> >>> PARAVIEW_INSTALL_DEVELOPMENT_F OFF >>> >>> PARAVIEW_USE_MPI ON >>> >>> PARAVIEW_USE_PISTON OFF >>> >>> PARAVIEW_USE_VISITBRIDGE OFF >>> >>> VTK_Group_Tk OFF >>> >>> XDMF_USE_BZIP2 OFF >>> >>> XDMF_USE_GZIP OFF >>> >>> Do I need to specifiy a path somewhere? comment something out somewhere? >>> Turn on another option in the CMake options? >>> >>> Any help would be appreciated :) >>> >>> Noah >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.wittenburg at kitware.com Wed Jun 10 15:41:12 2015 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Wed, 10 Jun 2015 13:41:12 -0600 Subject: [Paraview] ParaView 4.0.1 Not Compiling for Python, MPI, Llvm In-Reply-To: References: Message-ID: Hi Noah, Those first few instructions kind of test whether you need to do any of the rest. You won't be able to run X until you have completed the instructions in one of the sections beneath the "Introduction". Pick the section that most closely resembles the image you're working with and go through those instructions before attempting to run X or glxinfo. Hope this helps. Scott On Wed, Jun 10, 2015 at 1:34 PM, Noah Taylor wrote: > Scott, > > I have setup a GPU instance and am trying to use the instructions give but > when I use X or glxinfo when the Display is pointed to 0.0, I get an erro > that says couldn't open display :0.0. Did anybody else run into this > problem on the GPU AWS node? > > > Noah > > On Mon, Jun 8, 2015 at 10:32 PM, Noah Taylor wrote: > >> Scott, >> >> Thank you very much! The documentation looks to be well written. >> >> Cheers, >> Noah >> >> On Mon, Jun 8, 2015 at 9:41 AM, Scott Wittenburg < >> scott.wittenburg at kitware.com> wrote: >> >>> Hi Noah, >>> >>> I don't see the specific link error message in your email, but it >>> seems possible it could be related to your graphics environment. We often >>> have to compile ParaView on amazon EC2 instances when setting up >>> ParaViewWeb, and some of the guides for that may end up being useful to >>> you, specifically: >>> >>> >>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/graphics_on_ec2_g2 >>> >>> and >>> >>> >>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ubuntu_14_04 >>> >>> Cheers, >>> Scott >>> >>> >>> On Sat, Jun 6, 2015 at 9:44 PM, Noah Taylor >>> wrote: >>> >>>> Hello, >>>> >>>> I've been trying to compile this for a couple of weeks now but am >>>> running into some unknown troubles. My build gets to ~50% and kicks out an >>>> error as follows: >>>> >>>> collect2: error: ld returned 1 exit status >>>> make[2]: *** [lib/libvtkRenderingOpenGL-pv4.0.so.1] Error 1 >>>> make[1]: *** >>>> [VTK/Rendering/OpenGL/CMakeFiles/vtkRenderingOpenGL.dir/all] Error 2 >>>> make[1]: *** Waiting for unfinished jobs.... >>>> >>>> I tried locating the libvtkRenderingOpenGL-pv4.0.so.1 and it wasn't >>>> anywhere on my machine and I have googled this library but I cannot find a >>>> solution. >>>> >>>> My ccmake options are as follows (I'm just trying to compile on a >>>> ubuntu aws node): >>>> >>>> BUILD_DOCUMENTATION OFF >>>> >>>> BUILD_EXAMPLES OFF >>>> >>>> BUILD_SHARED_LIBS ON >>>> >>>> BUILD_TESTING ON >>>> >>>> CMAKE_BUILD_TYPE Debug >>>> >>>> CMAKE_INSTALL_PREFIX /usr/local >>>> >>>> GMVReader_GMVREAD_LIB_DIR >>>> /mnt/ParaView-v4.0.1-source/Utilities/VisItBridge/databases/GMV >>>> >>>> GMVReader_SKIP_DATARANGE_CALCU OFF >>>> >>>> MPI_C_INCLUDE_PATH >>>> /usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi >>>> >>>> MPI_C_LIBRARIES >>>> /usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so >>>> >>>> >>>> PARAVIEW_BUILD_QT_GUI OFF >>>> >>>> PARAVIEW_DATA_ROOT PARAVIEW_DATA_ROOT-NOTFOUND >>>> >>>> PARAVIEW_ENABLE_CATALYST ON >>>> >>>> PARAVIEW_ENABLE_FFMPEG OFF >>>> >>>> PARAVIEW_ENABLE_PYTHON ON >>>> >>>> PARAVIEW_ENABLE_QT_SUPPORT OFF >>>> >>>> PARAVIEW_INSTALL_DEVELOPMENT_F OFF >>>> >>>> PARAVIEW_USE_MPI ON >>>> >>>> PARAVIEW_USE_PISTON OFF >>>> >>>> PARAVIEW_USE_VISITBRIDGE OFF >>>> >>>> VTK_Group_Tk OFF >>>> >>>> XDMF_USE_BZIP2 OFF >>>> >>>> XDMF_USE_GZIP OFF >>>> >>>> Do I need to specifiy a path somewhere? comment something out >>>> somewhere? Turn on another option in the CMake options? >>>> >>>> Any help would be appreciated :) >>>> >>>> Noah >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.wittenburg at kitware.com Wed Jun 10 16:40:46 2015 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Wed, 10 Jun 2015 14:40:46 -0600 Subject: [Paraview] ParaView 4.0.1 Not Compiling for Python, MPI, Llvm In-Reply-To: References: Message-ID: I am responding to the paraview users list so other folks can benefit from the discussion... On Wed, Jun 10, 2015 at 2:11 PM, Vishnubharathi T wrote: > Dear Scott Wittenburg, > I am learning Paraview by myself. I couldnt find many pdfs for learning. > The ParaView guide is freely available as a pdf: http://www.paraview.org/paraview-guide/ The ParaView wiki is also a good resource: http://www.paraview.org/Wiki/ParaView > I would like to learn about the things(options) that are marked in > attachment. Please help me in understanding the meaning of those in > addition to using to using those options. Or where shall I get those > information? > > 1. (eg, texture coordinates, Normals, cellNormals,) and > In the image you have shared, those things are the variables available in the data you selected. > 2. The options under SOURCES option. > See the guide linked above, page 5 begins the discussion of sources. Hope this helps, Scott > On Wed, Jun 10, 2015 at 9:41 PM, Scott Wittenburg < > scott.wittenburg at kitware.com> wrote: > >> Hi Noah, >> >> Those first few instructions kind of test whether you need to do any >> of the rest. You won't be able to run X until you have completed the >> instructions in one of the sections beneath the "Introduction". Pick the >> section that most closely resembles the image you're working with and go >> through those instructions before attempting to run X or glxinfo. >> >> Hope this helps. >> Scott >> >> On Wed, Jun 10, 2015 at 1:34 PM, Noah Taylor >> wrote: >> >>> Scott, >>> >>> I have setup a GPU instance and am trying to use the instructions give >>> but when I use X or glxinfo when the Display is pointed to 0.0, I get an >>> erro that says couldn't open display :0.0. Did anybody else run into this >>> problem on the GPU AWS node? >>> >>> >>> Noah >>> >>> On Mon, Jun 8, 2015 at 10:32 PM, Noah Taylor >>> wrote: >>> >>>> Scott, >>>> >>>> Thank you very much! The documentation looks to be well written. >>>> >>>> Cheers, >>>> Noah >>>> >>>> On Mon, Jun 8, 2015 at 9:41 AM, Scott Wittenburg < >>>> scott.wittenburg at kitware.com> wrote: >>>> >>>>> Hi Noah, >>>>> >>>>> I don't see the specific link error message in your email, but it >>>>> seems possible it could be related to your graphics environment. We often >>>>> have to compile ParaView on amazon EC2 instances when setting up >>>>> ParaViewWeb, and some of the guides for that may end up being useful to >>>>> you, specifically: >>>>> >>>>> >>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/graphics_on_ec2_g2 >>>>> >>>>> and >>>>> >>>>> >>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ubuntu_14_04 >>>>> >>>>> Cheers, >>>>> Scott >>>>> >>>>> >>>>> On Sat, Jun 6, 2015 at 9:44 PM, Noah Taylor >>>>> wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> I've been trying to compile this for a couple of weeks now but am >>>>>> running into some unknown troubles. My build gets to ~50% and kicks out an >>>>>> error as follows: >>>>>> >>>>>> collect2: error: ld returned 1 exit status >>>>>> make[2]: *** [lib/libvtkRenderingOpenGL-pv4.0.so.1] Error 1 >>>>>> make[1]: *** >>>>>> [VTK/Rendering/OpenGL/CMakeFiles/vtkRenderingOpenGL.dir/all] Error 2 >>>>>> make[1]: *** Waiting for unfinished jobs.... >>>>>> >>>>>> I tried locating the libvtkRenderingOpenGL-pv4.0.so.1 and it wasn't >>>>>> anywhere on my machine and I have googled this library but I cannot find a >>>>>> solution. >>>>>> >>>>>> My ccmake options are as follows (I'm just trying to compile on a >>>>>> ubuntu aws node): >>>>>> >>>>>> BUILD_DOCUMENTATION OFF >>>>>> >>>>>> BUILD_EXAMPLES OFF >>>>>> >>>>>> BUILD_SHARED_LIBS ON >>>>>> >>>>>> BUILD_TESTING ON >>>>>> >>>>>> CMAKE_BUILD_TYPE Debug >>>>>> >>>>>> CMAKE_INSTALL_PREFIX /usr/local >>>>>> >>>>>> GMVReader_GMVREAD_LIB_DIR >>>>>> /mnt/ParaView-v4.0.1-source/Utilities/VisItBridge/databases/GMV >>>>>> >>>>>> GMVReader_SKIP_DATARANGE_CALCU OFF >>>>>> >>>>>> MPI_C_INCLUDE_PATH >>>>>> /usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi >>>>>> >>>>>> MPI_C_LIBRARIES >>>>>> /usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so >>>>>> >>>>>> >>>>>> PARAVIEW_BUILD_QT_GUI OFF >>>>>> >>>>>> PARAVIEW_DATA_ROOT PARAVIEW_DATA_ROOT-NOTFOUND >>>>>> >>>>>> PARAVIEW_ENABLE_CATALYST ON >>>>>> >>>>>> PARAVIEW_ENABLE_FFMPEG OFF >>>>>> >>>>>> PARAVIEW_ENABLE_PYTHON ON >>>>>> >>>>>> PARAVIEW_ENABLE_QT_SUPPORT OFF >>>>>> >>>>>> PARAVIEW_INSTALL_DEVELOPMENT_F OFF >>>>>> >>>>>> PARAVIEW_USE_MPI ON >>>>>> >>>>>> PARAVIEW_USE_PISTON OFF >>>>>> >>>>>> PARAVIEW_USE_VISITBRIDGE OFF >>>>>> >>>>>> VTK_Group_Tk OFF >>>>>> >>>>>> XDMF_USE_BZIP2 OFF >>>>>> >>>>>> XDMF_USE_GZIP OFF >>>>>> >>>>>> Do I need to specifiy a path somewhere? comment something out >>>>>> somewhere? Turn on another option in the CMake options? >>>>>> >>>>>> Any help would be appreciated :) >>>>>> >>>>>> Noah >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>> >>>> >>> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffrey.c.becker at nasa.gov Wed Jun 10 17:15:16 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Wed, 10 Jun 2015 14:15:16 -0700 Subject: [Paraview] Selecting volume rendering causes output to vanish In-Reply-To: References: <55787B45.4000606@nasa.gov> <55787C89.5080409@gmail.com> <55788182.4040206@nasa.gov> <5578861C.4060407@gmail.com> <557886A6.5080606@nasa.gov> Message-ID: <5578A8E4.90703@nasa.gov> On 06/10/2015 12:03 PM, David E DeMarle wrote: > Probably the content isn't amenable to volume rendering. To be so, the > unstructured grid has to have volumetric cells in it (tets, voxels, > etc). If it just has polys or lines or points in it, they won't > appear. You'll have to resample of splat onto the data onto a > volumetric grid in that case. That's it! I created an unstructured grid of points from a data file using VTK. I'll see about resampling to volumetric grid. Thanks. -jeff > > > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Wed, Jun 10, 2015 at 2:58 PM, Aashish Chaudhary > > > wrote: > > No, I don't think so. It would be nice if you can try Burlen > suggestion to see if it works for built in datasets / sources. > > - Aashish > > On Wed, Jun 10, 2015 at 2:49 PM, Jeff Becker > > wrote: > > On 06/10/2015 11:46 AM, Burlen Loring wrote: > > Hmm. If Bunyk ray cast doesn't work some thing strange is > going on as that is a software(non gpu) algorithm and > should always work. > > Can you get anything to show up using a small test data? > For example create a wavelet source and apply a threshold > (use default values) to convert to unstructured data. If > that works maybe something with your input data, or size > of it. > > > It's a 500 by 500 by 500 grid of floats - is that too big? > > > On 06/10/2015 11:27 AM, Jeff Becker wrote: > > On 06/10/2015 11:06 AM, Burlen Loring wrote: > > 2 things to try: set the remote render threshold > to zero, and if that doesn't get it to show up, > change the mapper to Bunyk ray cast. One of those > usually works depending on what the cause of the > issue is. > > > I have both of those set - no luck. BTW, this is > ParaView 4.3.1 on an NVIDIA backend. glxinfo shows: > > $ glxinfo | head -30 > name of display: :0.0 > display: :0 screen: 0 > direct rendering: Yes > server glx vendor string: NVIDIA Corporation > server glx version string: 1.4 > server glx extensions: > GLX_EXT_visual_info, GLX_EXT_visual_rating, > GLX_SGIX_fbconfig, > GLX_SGIX_pbuffer, GLX_SGI_video_sync, > GLX_SGI_swap_control, > GLX_EXT_swap_control, GLX_EXT_swap_control_tear, > GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, > GLX_ARB_create_context, > GLX_ARB_create_context_profile, > GLX_EXT_create_context_es_profile, > GLX_EXT_create_context_es2_profile, > GLX_ARB_create_context_robustness, > GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, > GLX_ARB_multisample, > GLX_NV_float_buffer, GLX_ARB_fbconfig_float, > GLX_EXT_framebuffer_sRGB, > GLX_NV_multisample_coverage > client glx vendor string: NVIDIA Corporation > client glx version string: 1.4 > client glx extensions: > GLX_ARB_get_proc_address, GLX_ARB_multisample, > GLX_EXT_visual_info, > GLX_EXT_visual_rating, GLX_EXT_import_context, > GLX_SGI_video_sync, > GLX_NV_swap_group, GLX_NV_video_out, > GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, > GLX_SGI_swap_control, GLX_EXT_swap_control, > GLX_EXT_swap_control_tear, > GLX_EXT_buffer_age, GLX_ARB_create_context, > GLX_ARB_create_context_profile, GLX_NV_float_buffer, > GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float, > GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB, > GLX_NV_present_video, GLX_NV_copy_image, > GLX_NV_multisample_coverage, > GLX_NV_video_capture, > GLX_EXT_create_context_es_profile, > GLX_EXT_create_context_es2_profile, > GLX_ARB_create_context_robustness, > GLX_NV_delay_before_swap, GLX_EXT_stereo_tree > > > On 06/10/2015 11:00 AM, Jeff Becker wrote: > > Hi. I have an unstructured grid file that > opens and displays in Surface Rendering mode. > If I switch to Volume Rendering, I don't see > any output. Any ideas? > > Thanks. > > -jeff > _______________________________________________ > Powered by www.kitware.com > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the > ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: > http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: > http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > -- > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. > / > /| http://www.kitware.com/company/team/chaudhary.html/ > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From biddisco at cscs.ch Wed Jun 10 17:40:08 2015 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Wed, 10 Jun 2015 21:40:08 +0000 Subject: [Paraview] Info about AMR datasets/structures Message-ID: Dear list, I would like to generate some AMR data structures from custom data and filters, but I?m having trouble locating information about the format/relationships of AMR blocks. The wiki contains old outdated references to the heirarchicalbox structures and not to the overlapping and non overlapping AMR formats. Specifically, I?d like to know if each level of AMR boxes must always have a fixed refinement level wrt to the level above, or whether I can refine arbitrarily (i.e. Have a root box of resolution x and sub boxes with different subdivision ratios at the same level). Also, the overlapping AMR dataset examples I?ve looked at seem to use an oct tree style decomposition where each node must be subdivided along mid planes, can I use a pure BSPtree where every node is subdivided along any axis at any point on the axis and still maintain a non overlapping amr dataset? The vtkAMRInformation documentation consists only of Refinement ratio between AMR levels Grid spacing for each level The file block index for each block parent child information, if requested But does the refinement ratio have to be constant for each level? Most of the paraview filters appear to be greyed out for vtkNonOverlappingAMR data, whereas the Overlapping appears to have support for certain operations like contouring and slicing ? is it the case that only nonoverlapping datasets are supported for these operations. If there is detailed info anywhere, could someone please send me a link. Thanks JB -------------- next part -------------- An HTML attachment was scrubbed... URL: From haonrolyat at gmail.com Wed Jun 10 17:57:54 2015 From: haonrolyat at gmail.com (Noah Taylor) Date: Wed, 10 Jun 2015 15:57:54 -0600 Subject: [Paraview] ParaView 4.0.1 Not Compiling for Python, MPI, Llvm In-Reply-To: References: Message-ID: Scott, Ah, sorry about that. I was thinking that with GPU instances it was something small and seeing the mesa libraries threw me off but I followed the steps below and was able to get my paraview referencing the x server. Thanks alot! Just as an FYI for those that are novices like me, I had to do an additional step that may be intuitive for most that are familiar with x server but I needed to run vncserver and then export my DISPLAY to the master.1. When I try to just run X without doing this with it pointed to the 0.0 it will give me an error when I try and call glxinfo. After running vncserver and switching it to the master.1, I am able to run x and paraview tools :) Noah On Wed, Jun 10, 2015 at 2:40 PM, Scott Wittenburg < scott.wittenburg at kitware.com> wrote: > I am responding to the paraview users list so other folks can benefit from > the discussion... > > On Wed, Jun 10, 2015 at 2:11 PM, Vishnubharathi T < > vishnu2bharathi at gmail.com> wrote: > >> Dear Scott Wittenburg, >> I am learning Paraview by myself. I couldnt find many pdfs for learning. >> > > The ParaView guide is freely available as a pdf: > > http://www.paraview.org/paraview-guide/ > > The ParaView wiki is also a good resource: > > http://www.paraview.org/Wiki/ParaView > > >> I would like to learn about the things(options) that are marked in >> attachment. Please help me in understanding the meaning of those in >> addition to using to using those options. Or where shall I get those >> information? >> >> 1. (eg, texture coordinates, Normals, cellNormals,) and >> > > In the image you have shared, those things are the variables available in > the data you selected. > > >> 2. The options under SOURCES option. >> > > See the guide linked above, page 5 begins the discussion of sources. > > Hope this helps, > Scott > > > >> On Wed, Jun 10, 2015 at 9:41 PM, Scott Wittenburg < >> scott.wittenburg at kitware.com> wrote: >> >>> Hi Noah, >>> >>> Those first few instructions kind of test whether you need to do any >>> of the rest. You won't be able to run X until you have completed the >>> instructions in one of the sections beneath the "Introduction". Pick the >>> section that most closely resembles the image you're working with and go >>> through those instructions before attempting to run X or glxinfo. >>> >>> Hope this helps. >>> Scott >>> >>> On Wed, Jun 10, 2015 at 1:34 PM, Noah Taylor >>> wrote: >>> >>>> Scott, >>>> >>>> I have setup a GPU instance and am trying to use the instructions give >>>> but when I use X or glxinfo when the Display is pointed to 0.0, I get an >>>> erro that says couldn't open display :0.0. Did anybody else run into this >>>> problem on the GPU AWS node? >>>> >>>> >>>> Noah >>>> >>>> On Mon, Jun 8, 2015 at 10:32 PM, Noah Taylor >>>> wrote: >>>> >>>>> Scott, >>>>> >>>>> Thank you very much! The documentation looks to be well written. >>>>> >>>>> Cheers, >>>>> Noah >>>>> >>>>> On Mon, Jun 8, 2015 at 9:41 AM, Scott Wittenburg < >>>>> scott.wittenburg at kitware.com> wrote: >>>>> >>>>>> Hi Noah, >>>>>> >>>>>> I don't see the specific link error message in your email, but it >>>>>> seems possible it could be related to your graphics environment. We often >>>>>> have to compile ParaView on amazon EC2 instances when setting up >>>>>> ParaViewWeb, and some of the guides for that may end up being useful to >>>>>> you, specifically: >>>>>> >>>>>> >>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/graphics_on_ec2_g2 >>>>>> >>>>>> and >>>>>> >>>>>> >>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ubuntu_14_04 >>>>>> >>>>>> Cheers, >>>>>> Scott >>>>>> >>>>>> >>>>>> On Sat, Jun 6, 2015 at 9:44 PM, Noah Taylor >>>>>> wrote: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> I've been trying to compile this for a couple of weeks now but am >>>>>>> running into some unknown troubles. My build gets to ~50% and kicks out an >>>>>>> error as follows: >>>>>>> >>>>>>> collect2: error: ld returned 1 exit status >>>>>>> make[2]: *** [lib/libvtkRenderingOpenGL-pv4.0.so.1] Error 1 >>>>>>> make[1]: *** >>>>>>> [VTK/Rendering/OpenGL/CMakeFiles/vtkRenderingOpenGL.dir/all] Error 2 >>>>>>> make[1]: *** Waiting for unfinished jobs.... >>>>>>> >>>>>>> I tried locating the libvtkRenderingOpenGL-pv4.0.so.1 and it wasn't >>>>>>> anywhere on my machine and I have googled this library but I cannot find a >>>>>>> solution. >>>>>>> >>>>>>> My ccmake options are as follows (I'm just trying to compile on a >>>>>>> ubuntu aws node): >>>>>>> >>>>>>> BUILD_DOCUMENTATION OFF >>>>>>> >>>>>>> BUILD_EXAMPLES OFF >>>>>>> >>>>>>> BUILD_SHARED_LIBS ON >>>>>>> >>>>>>> BUILD_TESTING ON >>>>>>> >>>>>>> CMAKE_BUILD_TYPE Debug >>>>>>> >>>>>>> CMAKE_INSTALL_PREFIX /usr/local >>>>>>> >>>>>>> GMVReader_GMVREAD_LIB_DIR >>>>>>> /mnt/ParaView-v4.0.1-source/Utilities/VisItBridge/databases/GMV >>>>>>> >>>>>>> GMVReader_SKIP_DATARANGE_CALCU OFF >>>>>>> >>>>>>> MPI_C_INCLUDE_PATH >>>>>>> /usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi >>>>>>> >>>>>>> MPI_C_LIBRARIES >>>>>>> /usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so >>>>>>> >>>>>>> >>>>>>> PARAVIEW_BUILD_QT_GUI OFF >>>>>>> >>>>>>> PARAVIEW_DATA_ROOT PARAVIEW_DATA_ROOT-NOTFOUND >>>>>>> >>>>>>> PARAVIEW_ENABLE_CATALYST ON >>>>>>> >>>>>>> PARAVIEW_ENABLE_FFMPEG OFF >>>>>>> >>>>>>> PARAVIEW_ENABLE_PYTHON ON >>>>>>> >>>>>>> PARAVIEW_ENABLE_QT_SUPPORT OFF >>>>>>> >>>>>>> PARAVIEW_INSTALL_DEVELOPMENT_F OFF >>>>>>> >>>>>>> PARAVIEW_USE_MPI ON >>>>>>> >>>>>>> PARAVIEW_USE_PISTON OFF >>>>>>> >>>>>>> PARAVIEW_USE_VISITBRIDGE OFF >>>>>>> >>>>>>> VTK_Group_Tk OFF >>>>>>> >>>>>>> XDMF_USE_BZIP2 OFF >>>>>>> >>>>>>> XDMF_USE_GZIP OFF >>>>>>> >>>>>>> Do I need to specifiy a path somewhere? comment something out >>>>>>> somewhere? Turn on another option in the CMake options? >>>>>>> >>>>>>> Any help would be appreciated :) >>>>>>> >>>>>>> Noah >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at >>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>> http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.wittenburg at kitware.com Wed Jun 10 18:07:51 2015 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Wed, 10 Jun 2015 16:07:51 -0600 Subject: [Paraview] ParaView 4.0.1 Not Compiling for Python, MPI, Llvm In-Reply-To: References: Message-ID: Hi Noah, Since you were setting up on an EC2 instance, I was imagining that you would be running pvserver over there and connecting to it with the client running on your desktop. But I guess you are running the client gui on the EC2 machine, and this is why you need vncserver? Just curious. I'm glad you have had some success, though. Cheers, Scott On Wed, Jun 10, 2015 at 3:57 PM, Noah Taylor wrote: > Scott, > > Ah, sorry about that. I was thinking that with GPU instances it was > something small and seeing the mesa libraries threw me off but I followed > the steps below and was able to get my paraview referencing the x server. > Thanks alot! Just as an FYI for those that are novices like me, I had to do > an additional step that may be intuitive for most that are familiar with x > server but I needed to run vncserver and then export my DISPLAY to the > master.1. When I try to just run X without doing this with it pointed to > the 0.0 it will give me an error when I try and call glxinfo. After running > vncserver and switching it to the master.1, I am able to run x and paraview > tools :) > > Noah > > On Wed, Jun 10, 2015 at 2:40 PM, Scott Wittenburg < > scott.wittenburg at kitware.com> wrote: > >> I am responding to the paraview users list so other folks can benefit >> from the discussion... >> >> On Wed, Jun 10, 2015 at 2:11 PM, Vishnubharathi T < >> vishnu2bharathi at gmail.com> wrote: >> >>> Dear Scott Wittenburg, >>> I am learning Paraview by myself. I couldnt find many pdfs for learning. >>> >> >> The ParaView guide is freely available as a pdf: >> >> http://www.paraview.org/paraview-guide/ >> >> The ParaView wiki is also a good resource: >> >> http://www.paraview.org/Wiki/ParaView >> >> >>> I would like to learn about the things(options) that are marked in >>> attachment. Please help me in understanding the meaning of those in >>> addition to using to using those options. Or where shall I get those >>> information? >>> >>> 1. (eg, texture coordinates, Normals, cellNormals,) and >>> >> >> In the image you have shared, those things are the variables available in >> the data you selected. >> >> >>> 2. The options under SOURCES option. >>> >> >> See the guide linked above, page 5 begins the discussion of sources. >> >> Hope this helps, >> Scott >> >> >> >>> On Wed, Jun 10, 2015 at 9:41 PM, Scott Wittenburg < >>> scott.wittenburg at kitware.com> wrote: >>> >>>> Hi Noah, >>>> >>>> Those first few instructions kind of test whether you need to do any >>>> of the rest. You won't be able to run X until you have completed the >>>> instructions in one of the sections beneath the "Introduction". Pick the >>>> section that most closely resembles the image you're working with and go >>>> through those instructions before attempting to run X or glxinfo. >>>> >>>> Hope this helps. >>>> Scott >>>> >>>> On Wed, Jun 10, 2015 at 1:34 PM, Noah Taylor >>>> wrote: >>>> >>>>> Scott, >>>>> >>>>> I have setup a GPU instance and am trying to use the instructions give >>>>> but when I use X or glxinfo when the Display is pointed to 0.0, I get an >>>>> erro that says couldn't open display :0.0. Did anybody else run into this >>>>> problem on the GPU AWS node? >>>>> >>>>> >>>>> Noah >>>>> >>>>> On Mon, Jun 8, 2015 at 10:32 PM, Noah Taylor >>>>> wrote: >>>>> >>>>>> Scott, >>>>>> >>>>>> Thank you very much! The documentation looks to be well written. >>>>>> >>>>>> Cheers, >>>>>> Noah >>>>>> >>>>>> On Mon, Jun 8, 2015 at 9:41 AM, Scott Wittenburg < >>>>>> scott.wittenburg at kitware.com> wrote: >>>>>> >>>>>>> Hi Noah, >>>>>>> >>>>>>> I don't see the specific link error message in your email, but it >>>>>>> seems possible it could be related to your graphics environment. We often >>>>>>> have to compile ParaView on amazon EC2 instances when setting up >>>>>>> ParaViewWeb, and some of the guides for that may end up being useful to >>>>>>> you, specifically: >>>>>>> >>>>>>> >>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/graphics_on_ec2_g2 >>>>>>> >>>>>>> and >>>>>>> >>>>>>> >>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ubuntu_14_04 >>>>>>> >>>>>>> Cheers, >>>>>>> Scott >>>>>>> >>>>>>> >>>>>>> On Sat, Jun 6, 2015 at 9:44 PM, Noah Taylor >>>>>>> wrote: >>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> I've been trying to compile this for a couple of weeks now but am >>>>>>>> running into some unknown troubles. My build gets to ~50% and kicks out an >>>>>>>> error as follows: >>>>>>>> >>>>>>>> collect2: error: ld returned 1 exit status >>>>>>>> make[2]: *** [lib/libvtkRenderingOpenGL-pv4.0.so.1] Error 1 >>>>>>>> make[1]: *** >>>>>>>> [VTK/Rendering/OpenGL/CMakeFiles/vtkRenderingOpenGL.dir/all] Error 2 >>>>>>>> make[1]: *** Waiting for unfinished jobs.... >>>>>>>> >>>>>>>> I tried locating the libvtkRenderingOpenGL-pv4.0.so.1 and it wasn't >>>>>>>> anywhere on my machine and I have googled this library but I cannot find a >>>>>>>> solution. >>>>>>>> >>>>>>>> My ccmake options are as follows (I'm just trying to compile on a >>>>>>>> ubuntu aws node): >>>>>>>> >>>>>>>> BUILD_DOCUMENTATION OFF >>>>>>>> >>>>>>>> BUILD_EXAMPLES OFF >>>>>>>> >>>>>>>> BUILD_SHARED_LIBS ON >>>>>>>> >>>>>>>> BUILD_TESTING ON >>>>>>>> >>>>>>>> CMAKE_BUILD_TYPE Debug >>>>>>>> >>>>>>>> CMAKE_INSTALL_PREFIX /usr/local >>>>>>>> >>>>>>>> GMVReader_GMVREAD_LIB_DIR >>>>>>>> /mnt/ParaView-v4.0.1-source/Utilities/VisItBridge/databases/GMV >>>>>>>> >>>>>>>> GMVReader_SKIP_DATARANGE_CALCU OFF >>>>>>>> >>>>>>>> MPI_C_INCLUDE_PATH >>>>>>>> /usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi >>>>>>>> >>>>>>>> MPI_C_LIBRARIES >>>>>>>> /usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so >>>>>>>> >>>>>>>> >>>>>>>> PARAVIEW_BUILD_QT_GUI OFF >>>>>>>> >>>>>>>> PARAVIEW_DATA_ROOT PARAVIEW_DATA_ROOT-NOTFOUND >>>>>>>> >>>>>>>> PARAVIEW_ENABLE_CATALYST ON >>>>>>>> >>>>>>>> PARAVIEW_ENABLE_FFMPEG OFF >>>>>>>> >>>>>>>> PARAVIEW_ENABLE_PYTHON ON >>>>>>>> >>>>>>>> PARAVIEW_ENABLE_QT_SUPPORT OFF >>>>>>>> >>>>>>>> PARAVIEW_INSTALL_DEVELOPMENT_F OFF >>>>>>>> >>>>>>>> PARAVIEW_USE_MPI ON >>>>>>>> >>>>>>>> PARAVIEW_USE_PISTON OFF >>>>>>>> >>>>>>>> PARAVIEW_USE_VISITBRIDGE OFF >>>>>>>> >>>>>>>> VTK_Group_Tk OFF >>>>>>>> >>>>>>>> XDMF_USE_BZIP2 OFF >>>>>>>> >>>>>>>> XDMF_USE_GZIP OFF >>>>>>>> >>>>>>>> Do I need to specifiy a path somewhere? comment something out >>>>>>>> somewhere? Turn on another option in the CMake options? >>>>>>>> >>>>>>>> Any help would be appreciated :) >>>>>>>> >>>>>>>> Noah >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Powered by www.kitware.com >>>>>>>> >>>>>>>> Visit other Kitware open-source projects at >>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>> >>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>> >>>>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>>>> >>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From haonrolyat at gmail.com Wed Jun 10 18:27:39 2015 From: haonrolyat at gmail.com (Noah Taylor) Date: Wed, 10 Jun 2015 16:27:39 -0600 Subject: [Paraview] ParaView 4.0.1 Not Compiling for Python, MPI, Llvm In-Reply-To: References: Message-ID: Scott, It may be that I could be bettering how I use ParaView. What I am doing is basically extracting frames as PNGs from a number of timesteps so I can perform some post processing on said frames on the same node. The product I am creating is a time machine - like these here. http://timemachine.cmucreatelab.org/wiki/Main_Page - I am basically just taking advantage of the rendering capabilities of ParaView to get my hd images :) The ending product just let's me through it on a server somewhere that is a pretty light load to share. But ParaView Web looks promising too, I might have to do some comparisons Thanks! Noah On Wed, Jun 10, 2015 at 4:07 PM, Scott Wittenburg < scott.wittenburg at kitware.com> wrote: > Hi Noah, > > Since you were setting up on an EC2 instance, I was imagining that you > would be running pvserver over there and connecting to it with the client > running on your desktop. But I guess you are running the client gui on the > EC2 machine, and this is why you need vncserver? Just curious. > > I'm glad you have had some success, though. > > Cheers, > Scott > > On Wed, Jun 10, 2015 at 3:57 PM, Noah Taylor wrote: > >> Scott, >> >> Ah, sorry about that. I was thinking that with GPU instances it was >> something small and seeing the mesa libraries threw me off but I followed >> the steps below and was able to get my paraview referencing the x server. >> Thanks alot! Just as an FYI for those that are novices like me, I had to do >> an additional step that may be intuitive for most that are familiar with x >> server but I needed to run vncserver and then export my DISPLAY to the >> master.1. When I try to just run X without doing this with it pointed to >> the 0.0 it will give me an error when I try and call glxinfo. After running >> vncserver and switching it to the master.1, I am able to run x and paraview >> tools :) >> >> Noah >> >> On Wed, Jun 10, 2015 at 2:40 PM, Scott Wittenburg < >> scott.wittenburg at kitware.com> wrote: >> >>> I am responding to the paraview users list so other folks can benefit >>> from the discussion... >>> >>> On Wed, Jun 10, 2015 at 2:11 PM, Vishnubharathi T < >>> vishnu2bharathi at gmail.com> wrote: >>> >>>> Dear Scott Wittenburg, >>>> I am learning Paraview by myself. I couldnt find many pdfs for learning. >>>> >>> >>> The ParaView guide is freely available as a pdf: >>> >>> http://www.paraview.org/paraview-guide/ >>> >>> The ParaView wiki is also a good resource: >>> >>> http://www.paraview.org/Wiki/ParaView >>> >>> >>>> I would like to learn about the things(options) that are marked in >>>> attachment. Please help me in understanding the meaning of those in >>>> addition to using to using those options. Or where shall I get those >>>> information? >>>> >>>> 1. (eg, texture coordinates, Normals, cellNormals,) and >>>> >>> >>> In the image you have shared, those things are the variables available >>> in the data you selected. >>> >>> >>>> 2. The options under SOURCES option. >>>> >>> >>> See the guide linked above, page 5 begins the discussion of sources. >>> >>> Hope this helps, >>> Scott >>> >>> >>> >>>> On Wed, Jun 10, 2015 at 9:41 PM, Scott Wittenburg < >>>> scott.wittenburg at kitware.com> wrote: >>>> >>>>> Hi Noah, >>>>> >>>>> Those first few instructions kind of test whether you need to do >>>>> any of the rest. You won't be able to run X until you have completed the >>>>> instructions in one of the sections beneath the "Introduction". Pick the >>>>> section that most closely resembles the image you're working with and go >>>>> through those instructions before attempting to run X or glxinfo. >>>>> >>>>> Hope this helps. >>>>> Scott >>>>> >>>>> On Wed, Jun 10, 2015 at 1:34 PM, Noah Taylor >>>>> wrote: >>>>> >>>>>> Scott, >>>>>> >>>>>> I have setup a GPU instance and am trying to use the instructions >>>>>> give but when I use X or glxinfo when the Display is pointed to 0.0, I get >>>>>> an erro that says couldn't open display :0.0. Did anybody else run into >>>>>> this problem on the GPU AWS node? >>>>>> >>>>>> >>>>>> Noah >>>>>> >>>>>> On Mon, Jun 8, 2015 at 10:32 PM, Noah Taylor >>>>>> wrote: >>>>>> >>>>>>> Scott, >>>>>>> >>>>>>> Thank you very much! The documentation looks to be well written. >>>>>>> >>>>>>> Cheers, >>>>>>> Noah >>>>>>> >>>>>>> On Mon, Jun 8, 2015 at 9:41 AM, Scott Wittenburg < >>>>>>> scott.wittenburg at kitware.com> wrote: >>>>>>> >>>>>>>> Hi Noah, >>>>>>>> >>>>>>>> I don't see the specific link error message in your email, but >>>>>>>> it seems possible it could be related to your graphics environment. We >>>>>>>> often have to compile ParaView on amazon EC2 instances when setting up >>>>>>>> ParaViewWeb, and some of the guides for that may end up being useful to >>>>>>>> you, specifically: >>>>>>>> >>>>>>>> >>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/graphics_on_ec2_g2 >>>>>>>> >>>>>>>> and >>>>>>>> >>>>>>>> >>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ubuntu_14_04 >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Scott >>>>>>>> >>>>>>>> >>>>>>>> On Sat, Jun 6, 2015 at 9:44 PM, Noah Taylor >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> I've been trying to compile this for a couple of weeks now but am >>>>>>>>> running into some unknown troubles. My build gets to ~50% and kicks out an >>>>>>>>> error as follows: >>>>>>>>> >>>>>>>>> collect2: error: ld returned 1 exit status >>>>>>>>> make[2]: *** [lib/libvtkRenderingOpenGL-pv4.0.so.1] Error 1 >>>>>>>>> make[1]: *** >>>>>>>>> [VTK/Rendering/OpenGL/CMakeFiles/vtkRenderingOpenGL.dir/all] Error 2 >>>>>>>>> make[1]: *** Waiting for unfinished jobs.... >>>>>>>>> >>>>>>>>> I tried locating the libvtkRenderingOpenGL-pv4.0.so.1 and it >>>>>>>>> wasn't anywhere on my machine and I have googled this library but I cannot >>>>>>>>> find a solution. >>>>>>>>> >>>>>>>>> My ccmake options are as follows (I'm just trying to compile on a >>>>>>>>> ubuntu aws node): >>>>>>>>> >>>>>>>>> BUILD_DOCUMENTATION OFF >>>>>>>>> >>>>>>>>> BUILD_EXAMPLES OFF >>>>>>>>> >>>>>>>>> BUILD_SHARED_LIBS ON >>>>>>>>> >>>>>>>>> BUILD_TESTING ON >>>>>>>>> >>>>>>>>> CMAKE_BUILD_TYPE Debug >>>>>>>>> >>>>>>>>> CMAKE_INSTALL_PREFIX /usr/local >>>>>>>>> >>>>>>>>> GMVReader_GMVREAD_LIB_DIR >>>>>>>>> /mnt/ParaView-v4.0.1-source/Utilities/VisItBridge/databases/GMV >>>>>>>>> >>>>>>>>> GMVReader_SKIP_DATARANGE_CALCU OFF >>>>>>>>> >>>>>>>>> MPI_C_INCLUDE_PATH >>>>>>>>> /usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi >>>>>>>>> >>>>>>>>> MPI_C_LIBRARIES >>>>>>>>> /usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so >>>>>>>>> >>>>>>>>> >>>>>>>>> PARAVIEW_BUILD_QT_GUI OFF >>>>>>>>> >>>>>>>>> PARAVIEW_DATA_ROOT PARAVIEW_DATA_ROOT-NOTFOUND >>>>>>>>> >>>>>>>>> PARAVIEW_ENABLE_CATALYST ON >>>>>>>>> >>>>>>>>> PARAVIEW_ENABLE_FFMPEG OFF >>>>>>>>> >>>>>>>>> PARAVIEW_ENABLE_PYTHON ON >>>>>>>>> >>>>>>>>> PARAVIEW_ENABLE_QT_SUPPORT OFF >>>>>>>>> >>>>>>>>> PARAVIEW_INSTALL_DEVELOPMENT_F OFF >>>>>>>>> >>>>>>>>> PARAVIEW_USE_MPI ON >>>>>>>>> >>>>>>>>> PARAVIEW_USE_PISTON OFF >>>>>>>>> >>>>>>>>> PARAVIEW_USE_VISITBRIDGE OFF >>>>>>>>> >>>>>>>>> VTK_Group_Tk OFF >>>>>>>>> >>>>>>>>> XDMF_USE_BZIP2 OFF >>>>>>>>> >>>>>>>>> XDMF_USE_GZIP OFF >>>>>>>>> >>>>>>>>> Do I need to specifiy a path somewhere? comment something out >>>>>>>>> somewhere? Turn on another option in the CMake options? >>>>>>>>> >>>>>>>>> Any help would be appreciated :) >>>>>>>>> >>>>>>>>> Noah >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Powered by www.kitware.com >>>>>>>>> >>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>> >>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>> >>>>>>>>> Search the list archives at: >>>>>>>>> http://markmail.org/search/?q=ParaView >>>>>>>>> >>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mickey.phy at gmail.com Thu Jun 11 01:36:37 2015 From: mickey.phy at gmail.com (Mickael Philit) Date: Thu, 11 Jun 2015 07:36:37 +0200 Subject: [Paraview] ParaView 4.4 ?? In-Reply-To: References: Message-ID: <55791E65.9000105@gmail.com> Dear all, I just came across this interesting webpage: http://www.paraview.org/ParaView/index.php/ParaView_4.4_Deliverables and I would like to know if there is a release schedule for ParaView 4.4. Best regards Mickael From peter at peterheppel.com Thu Jun 11 03:47:47 2015 From: peter at peterheppel.com (Peter) Date: Thu, 11 Jun 2015 09:47:47 +0200 Subject: [Paraview] pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0 In-Reply-To: <8ffe6ff4c603830a8089781471107b9f@peterheppel.com> References: <10e5a92c2de8b3c9c685221b8c714f86@peterheppel.com> <8ffe6ff4c603830a8089781471107b9f@peterheppel.com> Message-ID: <25c2c4707d72b431ff2193f54a94aed8@peterheppel.com> Hello, I've made some progress, but its not the complete answer. To make the Catalyst examples display in Paraview, you have to go Paraview>Catalyst>Connect AFTER the client has initialized Catalyst. You also have to turn OFF the file write in the catalyst script. Try the following changes (I tested CxxFullExample) 1) In FEDriver.cxx, after the call to FEAdaptor::Initialize() , add something like std::cout<<"Please connect in Paraview"< Thanks for replying. Take a look at > > http://public.kitware.com/pipermail/paraview/2015-June/034283.html > > Briefly, > > Paraview segfaults with the above error message when I run any of the tests in ParaViewCatalystExampleCode-master with _coprocessor.EnableLiveVisualization(True). _They all pass when this flag is False. I've tested with V4.3.1 and with yesterday's development version. There's another user - U.UTKU.TURUNCOGLU AT BE.ITU.EDU.TR u.utku.turuncoglu at be.itu.edu.tr who has a similar problem on a different O/S. > > Are the tests in ParaViewCatalystExampleCode-master known to run OK with _coprocessor.EnableLiveVisualization(True)? _ Or is that not the only change needed to make these clients connect? > > If we are running ParaViewCatalystExampleCode-master correctly we'd appreciate your advice on where to start looking for a bug. > > best regards > > Peter > > --- > Peter Heppel > 35/37 Rue de Locmalo > 56290 Port-Louis > France > +33 6 81 30 76 52 cell > +33 2 97 82 19 30 > USA +1 773 280 8142 > Skype: peterheppel > > On 2015-06-10 19:47, Utkarsh Ayachit wrote: > I am not sure I follow what's happening here. Can you provide details on what you're doing here please? Thanks. > > Utkarsh > > On Wed, Jun 10, 2015 at 11:38 AM Peter wrote: > > Hello > > I just built the current Paraview development version and got the same error on running the Catalyst examples. > > Paraview declined the connection gracefully when the client was built with a different VTK version, so I suspect the issue isnt related to the socket handshake, but rather that it only occurs after the socket connection is successful. > > P > > -- > Peter Heppel > 35/37 Rue de Locmalo > 56290 Port-Louis > France > +33 6 81 30 76 52 cell > +33 2 97 82 19 30 > USA +1 773 280 8142 > Skype: peterheppel > _______________________________________________ > Powered by www.kitware.com [1] > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html [2] > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView [3] > > Search the list archives at: http://markmail.org/search/?q=ParaView [4] > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview [5] Links: ------ [1] http://www.kitware.com [2] http://www.kitware.com/opensource/opensource.html [3] http://paraview.org/Wiki/ParaView [4] http://markmail.org/search/?q=ParaView [5] http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Thu Jun 11 04:10:30 2015 From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE)) Date: Thu, 11 Jun 2015 11:10:30 +0300 Subject: [Paraview] pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0 In-Reply-To: <25c2c4707d72b431ff2193f54a94aed8@peterheppel.com> References: <10e5a92c2de8b3c9c685221b8c714f86@peterheppel.com> <8ffe6ff4c603830a8089781471107b9f@peterheppel.com> <25c2c4707d72b431ff2193f54a94aed8@peterheppel.com> Message-ID: <55794276.8090101@be.itu.edu.tr> Hi Peter, I followed your steps in Paraview 4.2 (compiled under MacOS 10.10.3) and as you mentioned, i could see the pipeline in the pipeline browser. I also decrease to time step (from 100 to 3) to test the code. After finishing the time step loop the ParaView gives following error, ERROR: In /Users/turuncu/Qsync/progs/paraview-4.2.0/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 735,vtkSocketCommunicator (0x7fd4837cd120): Could not send tag. ERROR: In /Users/turuncu/Qsync/progs/paraview-4.2.0/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 812,vtkSocketCommunicator (0x7fd4837cd120): Could not receive tag. 8013 ERROR: In /Users/turuncu/Qsync/progs/paraview-4.2.0/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 812,vtkSocketCommunicator (0x7fd4837cd120): Could not receive tag. 1 ERROR: In /Users/turuncu/Qsync/progs/paraview-4.2.0/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 812,vtkSocketCommunicator (0x7fd483a02280): Could not receive tag. 1 In this case, the code is also compiled with ParaView 4.2. So, there is no any version issue. By the way, it is necessary to add follow code to include section #include #include to make cout, endl and sleep function available. --ufuk On 11/06/15 10:47, Peter wrote: > > Hello, > > I've made some progress, but its not the complete answer. > > To make the Catalyst examples display in Paraview, you have to go > Paraview>Catalyst>Connect AFTER the client has initialized Catalyst. > You also have to turn OFF the file write in the catalyst script. > > Try the following changes (I tested CxxFullExample) > > 1) In FEDriver.cxx, after the call to FEAdaptor::Initialize() , add > something like > > std::cout<<"Please connect in Paraview"< > sleep(20); > > I also put a 'sleep(1)' into the timestep loop to give more time to > manipulate paraview. > > 2) In feslicescript.py, you remove the calls to > coprocessor.CreateWriter and change EnableLiveVisualization to True). > > Now, the test sequence is: > > 1) start Paraview. DONT connect Catalyst. > > 2) run the CxxFullExample with (path)feslicecinema.py as argument .( > To find out the exact command, go ctest --verbose) > > 3) When you see "Please connect in Paraview", in the Catalyst menu > you go 'Connect' and dismiss the dialogs which follow. > > You'll see some changes in the pipeline browser. Paraview can see > some data but doesnt render it until after the end of the > timestepping. Would you like to look at that? > > Cheers > > --- > Peter Heppel > 35/37 Rue de Locmalo > 56290 Port-Louis > France > +33 6 81 30 76 52 cell > +33 2 97 82 19 30 > USA +1 773 280 8142 > Skype: peterheppel > > On 2015-06-10 22:54, Peter wrote: > >> Thanks for replying. Take a look at >> >> http://public.kitware.com/pipermail/paraview/2015-June/034283.html >> >> Briefly, >> >> Paraview segfaults with the above error message when I run any of the >> tests in ParaViewCatalystExampleCode-master with >> /coprocessor.EnableLiveVisualization(True). /They all pass when this >> flag is False. I've tested with V4.3.1 and with yesterday's >> development version. There's another user - *u.utku.turuncoglu at >> be.itu.edu.tr* u.utku.turuncoglu at be.itu.edu.tr >> who >> has a similar problem on a different O/S. >> >> Are the tests in ParaViewCatalystExampleCode-master known to run OK >> with /coprocessor.EnableLiveVisualization(True)? / Or is that not the >> only change needed to make these clients connect? >> >> If we are running ParaViewCatalystExampleCode-master correctly we'd >> appreciate your advice on where to start looking for a bug. >> >> best regards >> >> Peter >> >> --- >> Peter Heppel >> 35/37 Rue de Locmalo >> 56290 Port-Louis >> France >> +33 6 81 30 76 52 cell >> +33 2 97 82 19 30 >> USA +1 773 280 8142 >> Skype: peterheppel >> >> On 2015-06-10 19:47, Utkarsh Ayachit wrote: >> >> I am not sure I follow what's happening here. Can you provide >> details on what you're doing here please? Thanks. >> Utkarsh >> >> On Wed, Jun 10, 2015 at 11:38 AM Peter > > wrote: >> >> Hello >> >> I just built the current Paraview development version and got >> the same error on running the Catalyst examples. >> >> Paraview declined the connection gracefully when the client >> was built with a different VTK version, so I suspect the >> issue isnt related to the socket handshake, but rather that >> it only occurs after the socket connection is successful. >> >> P >> >> -- >> Peter Heppel >> 35/37 Rue de Locmalo >> 56290 Port-Louis >> France >> +33 6 81 30 76 52 cell >> +33 2 97 82 19 30 >> USA +1 773 280 8142 >> Skype: peterheppel >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: >> http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From peter at peterheppel.com Thu Jun 11 04:28:41 2015 From: peter at peterheppel.com (Peter) Date: Thu, 11 Jun 2015 10:28:41 +0200 Subject: [Paraview] pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0 In-Reply-To: <55794276.8090101@be.itu.edu.tr> References: <10e5a92c2de8b3c9c685221b8c714f86@peterheppel.com> <8ffe6ff4c603830a8089781471107b9f@peterheppel.com> <25c2c4707d72b431ff2193f54a94aed8@peterheppel.com> <55794276.8090101@be.itu.edu.tr> Message-ID: <6aa01707e399bbef2b76bf91f58b7ddd@peterheppel.com> Hi Ufuk, Good. You get the same result as me. I think the error messages start after the timestep loop has finished. The good news is that Paraview handles the termination of the client without crashing. Can you find out how to get Paraview to render each timestep? I guess to implement this in our simulations we'll have to put a 'system("paraview --script=something") ; in our code just after the FEAdaptor::Initialize() call. The script would connect Catalyst. Cheers --- Peter Heppel 35/37 Rue de Locmalo 56290 Port-Louis France +33 6 81 30 76 52 cell +33 2 97 82 19 30 USA +1 773 280 8142 Skype: peterheppel On 2015-06-11 10:10, Ufuk Utku Turuncoglu (BE) wrote: > Hi Peter, > > I followed your steps in Paraview 4.2 (compiled under MacOS 10.10.3) and as you mentioned, i could see the pipeline in the pipeline browser. I also decrease to time step (from 100 to 3) to test the code. After finishing the time step loop the ParaView gives following error, > > ERROR: In /Users/turuncu/Qsync/progs/paraview-4.2.0/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 735,vtkSocketCommunicator (0x7fd4837cd120): Could not send tag. > > ERROR: In /Users/turuncu/Qsync/progs/paraview-4.2.0/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 812,vtkSocketCommunicator (0x7fd4837cd120): Could not receive tag. 8013 > > ERROR: In /Users/turuncu/Qsync/progs/paraview-4.2.0/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 812,vtkSocketCommunicator (0x7fd4837cd120): Could not receive tag. 1 > > ERROR: In /Users/turuncu/Qsync/progs/paraview-4.2.0/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 812,vtkSocketCommunicator (0x7fd483a02280): Could not receive tag. 1 > > In this case, the code is also compiled with ParaView 4.2. So, there is no any version issue. > > By the way, it is necessary to add follow code to include section > > #include > #include > > to make cout, endl and sleep function available. > > --ufuk > > On 11/06/15 10:47, Peter wrote: > > Hello, > > I've made some progress, but its not the complete answer. > > To make the Catalyst examples display in Paraview, you have to go Paraview>Catalyst>Connect AFTER the client has initialized Catalyst. > You also have to turn OFF the file write in the catalyst script. > > Try the following changes (I tested CxxFullExample) > > 1) In FEDriver.cxx, after the call to FEAdaptor::Initialize() , add something like > > std::cout<<"Please connect in Paraview"< > sleep(20); > > I also put a 'sleep(1)' into the timestep loop to give more time to manipulate paraview. > > 2) In feslicescript.py, you remove the calls to coprocessor.CreateWriter and change EnableLiveVisualization to True). > > Now, the test sequence is: > > 1) start Paraview. DONT connect Catalyst. > > 2) run the CxxFullExample with (path)feslicecinema.py as argument .( To find out the exact command, go ctest --verbose) > > 3) When you see "Please connect in Paraview", in the Catalyst menu you go 'Connect' and dismiss the dialogs which follow. > > You'll see some changes in the pipeline browser. Paraview can see some data but doesnt render it until after the end of the timestepping. Would you like to look at that? > > Cheers > > --- > Peter Heppel > 35/37 Rue de Locmalo > 56290 Port-Louis > France > +33 6 81 30 76 52 cell > +33 2 97 82 19 30 > USA +1 773 280 8142 > Skype: peterheppel > > On 2015-06-10 22:54, Peter wrote: > > Thanks for replying. Take a look at > > http://public.kitware.com/pipermail/paraview/2015-June/034283.html [1] > > Briefly, > > Paraview segfaults with the above error message when I run any of the tests in ParaViewCatalystExampleCode-master with _coprocessor.EnableLiveVisualization(True). _They all pass when this flag is False. I've tested with V4.3.1 and with yesterday's development version. There's another user - U.UTKU.TURUNCOGLU AT BE.ITU.EDU.TR u.utku.turuncoglu at be.itu.edu.tr who has a similar problem on a different O/S. > > Are the tests in ParaViewCatalystExampleCode-master known to run OK with _coprocessor.EnableLiveVisualization(True)? _ Or is that not the only change needed to make these clients connect? > > If we are running ParaViewCatalystExampleCode-master correctly we'd appreciate your advice on where to start looking for a bug. > > best regards > > Peter > > --- > Peter Heppel > 35/37 Rue de Locmalo > 56290 Port-Louis > France > +33 6 81 30 76 52 cell > +33 2 97 82 19 30 > USA +1 773 280 8142 > Skype: peterheppel > > On 2015-06-10 19:47, Utkarsh Ayachit wrote: > I am not sure I follow what's happening here. Can you provide details on what you're doing here please? Thanks. > > Utkarsh > > On Wed, Jun 10, 2015 at 11:38 AM Peter wrote: > > Hello > > I just built the current Paraview development version and got the same error on running the Catalyst examples. > > Paraview declined the connection gracefully when the client was built with a different VTK version, so I suspect the issue isnt related to the socket handshake, but rather that it only occurs after the socket connection is successful. > > P > > -- > Peter Heppel > 35/37 Rue de Locmalo > 56290 Port-Louis > France > +33 6 81 30 76 52 cell > +33 2 97 82 19 30 > USA +1 773 280 8142 > Skype: peterheppel > _______________________________________________ > Powered by www.kitware.com [2] > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html [3] > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView [4] > > Search the list archives at: http://markmail.org/search/?q=ParaView [5] > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview [6] Links: ------ [1] http://public.kitware.com/pipermail/paraview/2015-June/034283.html [2] http://www.kitware.com [3] http://www.kitware.com/opensource/opensource.html [4] http://paraview.org/Wiki/ParaView [5] http://markmail.org/search/?q=ParaView [6] http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Thu Jun 11 04:36:40 2015 From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE)) Date: Thu, 11 Jun 2015 11:36:40 +0300 Subject: [Paraview] pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0 In-Reply-To: <6aa01707e399bbef2b76bf91f58b7ddd@peterheppel.com> References: <10e5a92c2de8b3c9c685221b8c714f86@peterheppel.com> <8ffe6ff4c603830a8089781471107b9f@peterheppel.com> <25c2c4707d72b431ff2193f54a94aed8@peterheppel.com> <55794276.8090101@be.itu.edu.tr> <6aa01707e399bbef2b76bf91f58b7ddd@peterheppel.com> Message-ID: <55794898.5060104@be.itu.edu.tr> Actually, that must be handled by the Python script without any modification in the source code (C++). As i know, the C++ code is just responsible for data conversion between model code and the ParaView to create VTK data representation of actual data but in some reason, the ParaView does not update (or render) the data between the time steps. There could be a call in ParaView Python API to force ParaView to render data. Following code from SampleScripts/feslicescript.py freqs = {'input': [10, 100]} coprocessor.SetUpdateFrequencies(freqs) might be related with it but i am not sure. Any idea? --ufuk On 11/06/15 11:28, Peter wrote: > > Hi Ufuk, > > Good. You get the same result as me. I think the error messages start > after the timestep loop has finished. The good news is that Paraview > handles the termination of the client without crashing. > > Can you find out how to get Paraview to render each timestep? > > I guess to implement this in our simulations we'll have to put a > 'system("paraview --script=something") ; in our code just after the > FEAdaptor::Initialize() call. The script would connect Catalyst. > > Cheers > > --- > Peter Heppel > 35/37 Rue de Locmalo > 56290 Port-Louis > France > +33 6 81 30 76 52 cell > +33 2 97 82 19 30 > USA +1 773 280 8142 > Skype: peterheppel > > On 2015-06-11 10:10, Ufuk Utku Turuncoglu (BE) wrote: > >> Hi Peter, >> >> I followed your steps in Paraview 4.2 (compiled under MacOS 10.10.3) >> and as you mentioned, i could see the pipeline in the pipeline >> browser. I also decrease to time step (from 100 to 3) to test the >> code. After finishing the time step loop the ParaView gives following >> error, >> >> ERROR: In >> /Users/turuncu/Qsync/progs/paraview-4.2.0/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, >> line 735,vtkSocketCommunicator (0x7fd4837cd120): Could not send tag. >> >> ERROR: In >> /Users/turuncu/Qsync/progs/paraview-4.2.0/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, >> line 812,vtkSocketCommunicator (0x7fd4837cd120): Could not receive >> tag. 8013 >> >> ERROR: In >> /Users/turuncu/Qsync/progs/paraview-4.2.0/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, >> line 812,vtkSocketCommunicator (0x7fd4837cd120): Could not receive tag. 1 >> >> ERROR: In >> /Users/turuncu/Qsync/progs/paraview-4.2.0/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, >> line 812,vtkSocketCommunicator (0x7fd483a02280): Could not receive tag. 1 >> >> In this case, the code is also compiled with ParaView 4.2. So, there >> is no any version issue. >> >> By the way, it is necessary to add follow code to include section >> >> #include >> #include >> >> to make cout, endl and sleep function available. >> >> --ufuk >> >> On 11/06/15 10:47, Peter wrote: >>> >>> Hello, >>> >>> I've made some progress, but its not the complete answer. >>> >>> To make the Catalyst examples display in Paraview, you have to go >>> Paraview>Catalyst>Connect AFTER the client has initialized Catalyst. >>> You also have to turn OFF the file write in the catalyst script. >>> >>> Try the following changes (I tested CxxFullExample) >>> >>> 1) In FEDriver.cxx, after the call to FEAdaptor::Initialize() , add >>> something like >>> >>> std::cout<<"Please connect in Paraview"<>> >>> sleep(20); >>> >>> I also put a 'sleep(1)' into the timestep loop to give more time to >>> manipulate paraview. >>> >>> 2) In feslicescript.py, you remove the calls to >>> coprocessor.CreateWriter and change EnableLiveVisualization to True). >>> >>> Now, the test sequence is: >>> >>> 1) start Paraview. DONT connect Catalyst. >>> >>> 2) run the CxxFullExample with (path)feslicecinema.py as argument .( >>> To find out the exact command, go ctest --verbose) >>> >>> 3) When you see "Please connect in Paraview", in the Catalyst menu >>> you go 'Connect' and dismiss the dialogs which follow. >>> >>> You'll see some changes in the pipeline browser. Paraview can see >>> some data but doesnt render it until after the end of the >>> timestepping. Would you like to look at that? >>> >>> Cheers >>> >>> --- >>> Peter Heppel >>> 35/37 Rue de Locmalo >>> 56290 Port-Louis >>> France >>> +33 6 81 30 76 52 cell >>> +33 2 97 82 19 30 >>> USA +1 773 280 8142 >>> Skype: peterheppel >>> >>> On 2015-06-10 22:54, Peter wrote: >>> >>> Thanks for replying. Take a look at >>> >>> http://public.kitware.com/pipermail/paraview/2015-June/034283.html >>> >>> Briefly, >>> >>> Paraview segfaults with the above error message when I run any >>> of the tests in ParaViewCatalystExampleCode-master with >>> /coprocessor.EnableLiveVisualization(True). /They all pass when >>> this flag is False. I've tested with V4.3.1 and with >>> yesterday's development version. There's another user - >>> *u.utku.turuncoglu at be.itu.edu.tr* u.utku.turuncoglu at >>> be.itu.edu.tr >>> who >>> has a similar problem on a different O/S. >>> >>> Are the tests in ParaViewCatalystExampleCode-master known to >>> run OK with /coprocessor.EnableLiveVisualization(True)? / Or is >>> that not the only change needed to make these clients connect? >>> >>> If we are running ParaViewCatalystExampleCode-master correctly >>> we'd appreciate your advice on where to start looking for a bug. >>> >>> best regards >>> >>> Peter >>> >>> --- >>> Peter Heppel >>> 35/37 Rue de Locmalo >>> 56290 Port-Louis >>> France >>> +33 6 81 30 76 52 cell >>> +33 2 97 82 19 30 >>> USA +1 773 280 8142 >>> Skype: peterheppel >>> >>> On 2015-06-10 19:47, Utkarsh Ayachit wrote: >>> >>> I am not sure I follow what's happening here. Can you >>> provide details on what you're doing here please? Thanks. >>> Utkarsh >>> >>> On Wed, Jun 10, 2015 at 11:38 AM Peter >>> > wrote: >>> >>> Hello >>> >>> I just built the current Paraview development version >>> and got the same error on running the Catalyst examples. >>> >>> Paraview declined the connection gracefully when the >>> client was built with a different VTK version, so I >>> suspect the issue isnt related to the socket handshake, >>> but rather that it only occurs after the socket >>> connection is successful. >>> >>> P >>> >>> -- >>> Peter Heppel >>> 35/37 Rue de Locmalo >>> 56290 Port-Louis >>> France >>> +33 6 81 30 76 52 cell >>> +33 2 97 82 19 30 >>> USA +1 773 280 8142 >>> Skype: peterheppel >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView >>> Wiki at: http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: >>> http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From eleonorapiersanti at yahoo.it Thu Jun 11 07:02:11 2015 From: eleonorapiersanti at yahoo.it (Eleonora Piersanti) Date: Thu, 11 Jun 2015 11:02:11 +0000 (UTC) Subject: [Paraview] Is it possible to scale a velocity field in paraview by a scalar and to sum the two velocity field too? Message-ID: <546092384.1656465.1434020531384.JavaMail.yahoo@mail.yahoo.com> I have two velocity field coming from an eigenproblem. One corresponds to the real part of the eigenvector and one to the imaginary part.Since I would normalize the phase I need to scale them and to sum them in some way. Is it possible to do it directly with paraview? Kind regards,Eleonora -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Jun 11 10:08:37 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 11 Jun 2015 10:08:37 -0400 Subject: [Paraview] Is it possible to scale a velocity field in paraview by a scalar and to sum the two velocity field too? In-Reply-To: <546092384.1656465.1434020531384.JavaMail.yahoo@mail.yahoo.com> References: <546092384.1656465.1434020531384.JavaMail.yahoo@mail.yahoo.com> Message-ID: Sure, check out the calculator, or better yet the python calculator filter. Section 5.8 in the new paraview guide. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Jun 11, 2015 at 7:02 AM, Eleonora Piersanti < eleonorapiersanti at yahoo.it> wrote: > I have two velocity field coming from an eigenproblem. One corresponds to > the real part of the eigenvector and one to the imaginary part. > Since I would normalize the phase I need to scale them and to sum them in > some way. Is it possible to do it directly with paraview? > > Kind regards, > Eleonora > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From eleonorapiersanti at yahoo.it Thu Jun 11 11:02:25 2015 From: eleonorapiersanti at yahoo.it (Eleonora Piersanti) Date: Thu, 11 Jun 2015 15:02:25 +0000 (UTC) Subject: [Paraview] Is it possible to scale a velocity field in paraview by a scalar and to sum the two velocity field too? In-Reply-To: References: Message-ID: <992510717.1970053.1434034945684.JavaMail.yahoo@mail.yahoo.com> Thank you. And what about summing two vectors? Il Gioved? 11 Giugno 2015 16:08, David E DeMarle ha scritto: Sure, check out the calculator, or better yet the python calculator filter. Section 5.8 in the new paraview guide. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Jun 11, 2015 at 7:02 AM, Eleonora Piersanti wrote: I have two velocity field coming from an eigenproblem. One corresponds to the real part of the eigenvector and one to the imaginary part.Since I would normalize the phase I need to scale them and to sum them in some way. Is it possible to do it directly with paraview? Kind regards,Eleonora _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffrey.c.becker at nasa.gov Thu Jun 11 13:52:32 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Thu, 11 Jun 2015 10:52:32 -0700 Subject: [Paraview] Selecting volume rendering causes output to vanish In-Reply-To: <5578A8E4.90703@nasa.gov> References: <55787B45.4000606@nasa.gov> <55787C89.5080409@gmail.com> <55788182.4040206@nasa.gov> <5578861C.4060407@gmail.com> <557886A6.5080606@nasa.gov> <5578A8E4.90703@nasa.gov> Message-ID: <5579CAE0.9030403@nasa.gov> On 06/10/2015 02:15 PM, Jeff Becker wrote: > On 06/10/2015 12:03 PM, David E DeMarle wrote: >> Probably the content isn't amenable to volume rendering. To be so, >> the unstructured grid has to have volumetric cells in it (tets, >> voxels, etc). If it just has polys or lines or points in it, they >> won't appear. You'll have to resample of splat onto the data onto a >> volumetric grid in that case. > > That's it! I created an unstructured grid of points from a data file > using VTK. I'll see about resampling to volumetric grid. Thanks. > After opening my file, and hitting apply to get it on the screen,I tried using ParaView's Delaunay 3D filter, and got the following: $ mpirun -np 1 /usr/bin/env DISPLAY=:0 /u/jcbecker/ParaView-4.3.1-Linux-64bit/bin/pvserver --client-host=pfe23 --use-offscreen-rendering Waiting for client... Connection URL: cs://maia34:11111 Accepting connection(s): maia34:11111 Client connected. terminate called after throwing an instance of 'St9bad_alloc' what(): std::bad_alloc This server has 64GB memory. Output from glxinfo is below: name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: NVIDIA Corporation server glx version string: 1.4 server glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile, GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness, GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, GLX_ARB_multisample, GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB, GLX_NV_multisample_coverage client glx vendor string: NVIDIA Corporation client glx version string: 1.4 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync, GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_buffer_age, GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float, GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB, GLX_NV_present_video, GLX_NV_copy_image, GLX_NV_multisample_coverage, GLX_NV_video_capture, GLX_EXT_create_context_es_profile, GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness, GLX_NV_delay_before_swap, GLX_EXT_stereo_tree GLX extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile, GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness, GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, GLX_ARB_multisample, GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB, GLX_NV_multisample_coverage, GLX_ARB_get_proc_address OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: Tesla K40m/PCIe/SSE2 OpenGL version string: 4.4.0 NVIDIA 340.65 OpenGL extensions: GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture, GL_ARB_arrays_of_arrays, GL_ARB_base_instance, GL_ARB_bindless_texture, GL_ARB_blend_func_extended, GL_ARB_buffer_storage, GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_color_buffer_float, GL_ARB_compatibility, GL_ARB_compressed_texture_pixel_storage, GL_ARB_conservative_depth, GL_ARB_compute_shader, GL_ARB_compute_variable_group_size, GL_ARB_copy_buffer, GL_ARB_copy_image, GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_indirect, GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, GL_ARB_enhanced_layouts, GL_ARB_ES2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_explicit_attrib_location, GL_ARB_explicit_uniform_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_layer_viewport, GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader, GL_ARB_framebuffer_no_attachments, GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, GL_ARB_geometry_shader4, GL_ARB_get_program_binary, GL_ARB_gpu_shader5, GL_ARB_gpu_shader_fp64, GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_imaging, GL_ARB_indirect_parameters, GL_ARB_instanced_arrays, GL_ARB_internalformat_query, GL_ARB_internalformat_query2, GL_ARB_invalidate_subdata, GL_ARB_map_buffer_alignment, GL_ARB_map_buffer_range, GL_ARB_multi_bind, GL_ARB_multi_draw_indirect, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_occlusion_query2, GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_program_interface_query, GL_ARB_provoking_vertex, GL_ARB_robust_buffer_access_behavior, GL_ARB_robustness, GL_ARB_sample_shading, GL_ARB_sampler_objects, GL_ARB_seamless_cube_map, GL_ARB_seamless_cubemap_per_texture, GL_ARB_separate_shader_objects, GL_ARB_shader_atomic_counters, GL_ARB_shader_bit_encoding, GL_ARB_shader_draw_parameters, GL_ARB_shader_group_vote, GL_ARB_shader_image_load_store, GL_ARB_shader_image_size, GL_ARB_shader_objects, GL_ARB_shader_precision, GL_ARB_query_buffer_object, GL_ARB_shader_storage_buffer_object, GL_ARB_shader_subroutine, GL_ARB_shader_texture_lod, GL_ARB_shading_language_100, GL_ARB_shading_language_420pack, GL_ARB_shading_language_include, GL_ARB_shading_language_packing, GL_ARB_shadow, GL_ARB_sparse_texture, GL_ARB_stencil_texturing, GL_ARB_sync, GL_ARB_tessellation_shader, GL_ARB_texture_border_clamp, GL_ARB_texture_buffer_object, GL_ARB_texture_buffer_object_rgb32, GL_ARB_texture_buffer_range, GL_ARB_texture_compression, GL_ARB_texture_compression_bptc, GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map, GL_ARB_texture_cube_map_array, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_float, GL_ARB_texture_gather, GL_ARB_texture_mirror_clamp_to_edge, GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_levels, GL_ARB_texture_query_lod, GL_ARB_texture_rectangle, GL_ARB_texture_rg, GL_ARB_texture_rgb10_a2ui, GL_ARB_texture_stencil8, GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, GL_ARB_texture_swizzle, GL_ARB_texture_view, GL_ARB_timer_query, GL_ARB_transform_feedback2, GL_ARB_transform_feedback3, GL_ARB_transform_feedback_instanced, GL_ARB_transpose_matrix, GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, GL_ARB_vertex_attrib_64bit, GL_ARB_vertex_attrib_binding, GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ARB_vertex_type_10f_11f_11f_rev, GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_viewport_array, GL_ARB_window_pos, GL_ATI_draw_buffers, GL_ATI_texture_float, GL_ATI_texture_mirror_once, GL_S3_s3tc, GL_EXT_texture_env_add, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_bindable_uniform, GL_EXT_blend_color, GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_compiled_vertex_array, GL_EXT_Cg_shader, GL_EXT_depth_bounds_test, GL_EXT_direct_state_access, GL_EXT_draw_buffers2, GL_EXT_draw_instanced, GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, GL_EXTX_framebuffer_mixed_formats, GL_EXT_framebuffer_multisample_blit_scaled, GL_EXT_framebuffer_object, GL_EXT_framebuffer_sRGB, GL_EXT_geometry_shader4, GL_EXT_gpu_program_parameters, GL_EXT_gpu_shader4, GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, GL_EXT_packed_float, GL_EXT_packed_pixels, GL_EXT_pixel_buffer_object, GL_EXT_point_parameters, GL_EXT_provoking_vertex, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_shader_objects, GL_EXT_separate_specular_color, GL_EXT_shader_image_load_store, GL_EXT_shader_integer_mix, GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_texture3D, GL_EXT_texture_array, GL_EXT_texture_buffer_object, GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_latc, GL_EXT_texture_compression_rgtc, GL_EXT_texture_compression_s3tc, GL_EXT_texture_cube_map, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, GL_EXT_texture_lod, GL_EXT_texture_lod_bias, GL_EXT_texture_mirror_clamp, GL_EXT_texture_object, GL_EXT_texture_shared_exponent, GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, GL_EXT_texture_storage, GL_EXT_texture_swizzle, GL_EXT_timer_query, GL_EXT_transform_feedback2, GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, GL_EXT_vertex_attrib_64bit, GL_EXT_x11_sync_object, GL_EXT_import_sync_object, GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat, GL_KHR_debug, GL_KTX_buffer_region, GL_NV_bindless_multi_draw_indirect, GL_NV_bindless_multi_draw_indirect_count, GL_NV_bindless_texture, GL_NV_blend_equation_advanced, GL_NV_blend_square, GL_NV_compute_program5, GL_NV_conditional_render, GL_NV_copy_depth_to_color, GL_NV_copy_image, GL_NV_depth_buffer_float, GL_NV_depth_clamp, GL_NV_draw_texture, GL_NV_ES1_1_compatibility, GL_NV_ES3_1_compatibility, GL_NV_explicit_multisample, GL_NV_fence, GL_NV_float_buffer, GL_NV_fog_distance, GL_NV_fragment_program, GL_NV_fragment_program_option, GL_NV_fragment_program2, GL_NV_framebuffer_multisample_coverage, GL_NV_geometry_shader4, GL_NV_gpu_program4, GL_NV_gpu_program4_1, GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended, GL_NV_gpu_program_fp64, GL_NV_gpu_shader5, GL_NV_half_float, GL_NV_light_max_exponent, GL_NV_multisample_coverage, GL_NV_multisample_filter_hint, GL_NV_occlusion_query, GL_NV_packed_depth_stencil, GL_NV_parameter_buffer_object, GL_NV_parameter_buffer_object2, GL_NV_path_rendering, GL_NV_pixel_data_range, GL_NV_point_sprite, GL_NV_primitive_restart, GL_NV_register_combiners, GL_NV_register_combiners2, GL_NV_shader_atomic_counters, GL_NV_shader_atomic_float, GL_NV_shader_atomic_int64, GL_NV_shader_buffer_load, GL_NV_shader_storage_buffer_object, GL_NV_texgen_reflection, GL_NV_texture_barrier, GL_NV_texture_compression_vtc, GL_NV_texture_env_combine4, GL_NV_texture_expand_normal, GL_NV_texture_multisample, GL_NV_texture_rectangle, GL_NV_texture_shader, GL_NV_texture_shader2, GL_NV_texture_shader3, GL_NV_transform_feedback, GL_NV_transform_feedback2, GL_NV_vdpau_interop, GL_NV_vertex_array_range, GL_NV_vertex_array_range2, GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory, GL_NV_vertex_program, GL_NV_vertex_program1_1, GL_NV_vertex_program2, GL_NV_vertex_program2_option, GL_NV_vertex_program3, GL_NVX_conditional_render, GL_NVX_gpu_memory_info, GL_NVX_nvenc_interop, GL_NV_shader_thread_group, GL_NV_shader_thread_shuffle, GL_KHR_blend_equation_advanced, GL_SGIS_generate_mipmap, GL_SGIS_texture_lod, GL_SGIX_depth_texture, GL_SGIX_shadow, GL_SUN_slice_accum glu version: 1.3 glu extensions: GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat ---------------------------------------------------------------------- 0x21 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 0 0 None 0x22 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 0 0 None 0x24 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 0 0 None 0x25 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 0 0 None 0x26 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 0 0 None 0x27 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 0 0 None 0x28 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 0 0 None 0x29 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 0 0 None 0x2a 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 0 0 None 0x2b 24 tc 0 24 0 r y . 8 8 8 0 4 0 0 16 16 16 16 0 0 None 0x2c 24 tc 0 32 0 r y . 8 8 8 8 4 0 0 16 16 16 16 0 0 None 0x2d 24 tc 0 24 0 r . . 8 8 8 0 4 0 0 16 16 16 16 0 0 None 0x2e 24 tc 0 32 0 r . . 8 8 8 8 4 0 0 16 16 16 16 0 0 None 0x2f 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon 0x30 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon 0x31 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon 0x32 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon 0x33 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon 0x34 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon 0x35 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon 0x36 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon 0x37 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon 0x38 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon 0x39 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon 0x3a 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon 0x3b 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon 0x3c 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon 0x3d 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon 0x3e 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon 0x3f 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x40 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x41 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x42 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x43 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x44 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x45 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x46 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x47 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x48 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x49 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x4a 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x4b 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x4c 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x4d 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x4e 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x4f 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x50 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x51 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x52 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x53 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x54 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x55 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x56 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x57 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x58 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x59 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x5a 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x5b 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x5c 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x5d 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x5e 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x5f 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x60 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x61 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x62 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x63 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x64 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x65 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x66 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x67 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon 0x68 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon 0x69 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon 0x6a 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon 0x6b 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon 0x6c 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon 0x6d 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon 0x6e 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon 0x6f 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 0 0 None 0x70 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 0 0 None 0x71 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 0 0 None 0x72 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 0 0 None 0x73 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 0 0 None 0x74 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 0 0 None 0x75 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 0 0 None 0x76 24 dc 0 24 0 r y . 8 8 8 0 4 0 0 16 16 16 16 0 0 None 0x77 24 dc 0 32 0 r y . 8 8 8 8 4 0 0 16 16 16 16 0 0 None 0x78 24 dc 0 24 0 r . . 8 8 8 0 4 0 0 16 16 16 16 0 0 None 0x79 24 dc 0 32 0 r . . 8 8 8 8 4 0 0 16 16 16 16 0 0 None 0x7a 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon 0x7b 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon 0x7c 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon 0x7d 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon 0x7e 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon 0x7f 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon 0x80 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon 0x81 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon 0x82 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon 0x83 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon 0x84 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon 0x85 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon 0x86 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon 0x87 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon 0x88 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon 0x89 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon 0x8a 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x8b 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x8c 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x8d 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x8e 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x8f 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x90 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x91 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x92 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x93 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x94 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x95 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x96 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x97 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x98 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x99 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x9a 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x9b 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x9c 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x9d 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x9e 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x9f 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0xa0 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0xa1 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0xa2 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0xa3 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0xa4 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0xa5 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0xa6 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0xa7 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0xa8 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0xa9 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0xaa 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0xab 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0xac 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0xad 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0xae 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0xaf 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0xb0 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0xb1 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0xb2 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon 0xb3 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon 0xb4 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon 0xb5 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon 0xb6 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon 0xb7 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon 0xb8 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon 0xb9 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon 0x23 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 0 0 None 0xba 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 0 0 None 0xbb 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 0 0 None 0xbc 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 0 0 None 0xbd 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 0 0 None 0xbe 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 0 0 None 0xbf 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 0 0 None 0xc0 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 0 0 None 0xc1 32 tc 0 24 0 r y . 8 8 8 0 4 0 0 16 16 16 16 0 0 None 0xc2 32 tc 0 32 0 r y . 8 8 8 8 4 0 0 16 16 16 16 0 0 None 0xc3 32 tc 0 24 0 r . . 8 8 8 0 4 0 0 16 16 16 16 0 0 None 0xc4 32 tc 0 32 0 r . . 8 8 8 8 4 0 0 16 16 16 16 0 0 None 0xc5 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon 0xc6 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon 0xc7 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon 0xc8 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon 0xc9 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon 0xca 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon 0xcb 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon 0xcc 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon 0xcd 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon 0xce 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon 0xcf 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon 0xd0 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon 0xd1 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon 0xd2 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon 0xd3 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon 0xd4 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon 0xd5 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0xd6 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0xd7 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0xd8 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0xd9 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0xda 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0xdb 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0xdc 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0xdd 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0xde 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0xdf 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0xe0 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0xe1 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0xe2 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0xe3 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0xe4 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0xe5 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0xe6 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0xe7 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0xe8 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0xe9 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0xea 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0xeb 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0xec 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0xed 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0xee 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0xef 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0xf0 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0xf1 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0xf2 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0xf3 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0xf4 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0xf5 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0xf6 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0xf7 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0xf8 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0xf9 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0xfa 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0xfb 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0xfc 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0xfd 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon 0xfe 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon 0xff 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon 0x100 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon 0x101 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon 0x102 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon 0x103 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon 0x104 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon display: :0 screen: 1 direct rendering: Yes server glx vendor string: NVIDIA Corporation server glx version string: 1.4 server glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile, GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness, GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, GLX_ARB_multisample, GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB, GLX_NV_multisample_coverage client glx vendor string: NVIDIA Corporation client glx version string: 1.4 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync, GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_buffer_age, GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float, GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB, GLX_NV_present_video, GLX_NV_copy_image, GLX_NV_multisample_coverage, GLX_NV_video_capture, GLX_EXT_create_context_es_profile, GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness, GLX_NV_delay_before_swap, GLX_EXT_stereo_tree GLX extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile, GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness, GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, GLX_ARB_multisample, GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB, GLX_NV_multisample_coverage, GLX_ARB_get_proc_address OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: Tesla K40m/PCIe/SSE2 OpenGL version string: 4.4.0 NVIDIA 340.65 OpenGL extensions: GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture, GL_ARB_arrays_of_arrays, GL_ARB_base_instance, GL_ARB_bindless_texture, GL_ARB_blend_func_extended, GL_ARB_buffer_storage, GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_color_buffer_float, GL_ARB_compatibility, GL_ARB_compressed_texture_pixel_storage, GL_ARB_conservative_depth, GL_ARB_compute_shader, GL_ARB_compute_variable_group_size, GL_ARB_copy_buffer, GL_ARB_copy_image, GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_indirect, GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, GL_ARB_enhanced_layouts, GL_ARB_ES2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_explicit_attrib_location, GL_ARB_explicit_uniform_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_layer_viewport, GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader, GL_ARB_framebuffer_no_attachments, GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, GL_ARB_geometry_shader4, GL_ARB_get_program_binary, GL_ARB_gpu_shader5, GL_ARB_gpu_shader_fp64, GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_imaging, GL_ARB_indirect_parameters, GL_ARB_instanced_arrays, GL_ARB_internalformat_query, GL_ARB_internalformat_query2, GL_ARB_invalidate_subdata, GL_ARB_map_buffer_alignment, GL_ARB_map_buffer_range, GL_ARB_multi_bind, GL_ARB_multi_draw_indirect, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_occlusion_query2, GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_program_interface_query, GL_ARB_provoking_vertex, GL_ARB_robust_buffer_access_behavior, GL_ARB_robustness, GL_ARB_sample_shading, GL_ARB_sampler_objects, GL_ARB_seamless_cube_map, GL_ARB_seamless_cubemap_per_texture, GL_ARB_separate_shader_objects, GL_ARB_shader_atomic_counters, GL_ARB_shader_bit_encoding, GL_ARB_shader_draw_parameters, GL_ARB_shader_group_vote, GL_ARB_shader_image_load_store, GL_ARB_shader_image_size, GL_ARB_shader_objects, GL_ARB_shader_precision, GL_ARB_query_buffer_object, GL_ARB_shader_storage_buffer_object, GL_ARB_shader_subroutine, GL_ARB_shader_texture_lod, GL_ARB_shading_language_100, GL_ARB_shading_language_420pack, GL_ARB_shading_language_include, GL_ARB_shading_language_packing, GL_ARB_shadow, GL_ARB_sparse_texture, GL_ARB_stencil_texturing, GL_ARB_sync, GL_ARB_tessellation_shader, GL_ARB_texture_border_clamp, GL_ARB_texture_buffer_object, GL_ARB_texture_buffer_object_rgb32, GL_ARB_texture_buffer_range, GL_ARB_texture_compression, GL_ARB_texture_compression_bptc, GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map, GL_ARB_texture_cube_map_array, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_float, GL_ARB_texture_gather, GL_ARB_texture_mirror_clamp_to_edge, GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_levels, GL_ARB_texture_query_lod, GL_ARB_texture_rectangle, GL_ARB_texture_rg, GL_ARB_texture_rgb10_a2ui, GL_ARB_texture_stencil8, GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, GL_ARB_texture_swizzle, GL_ARB_texture_view, GL_ARB_timer_query, GL_ARB_transform_feedback2, GL_ARB_transform_feedback3, GL_ARB_transform_feedback_instanced, GL_ARB_transpose_matrix, GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, GL_ARB_vertex_attrib_64bit, GL_ARB_vertex_attrib_binding, GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ARB_vertex_type_10f_11f_11f_rev, GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_viewport_array, GL_ARB_window_pos, GL_ATI_draw_buffers, GL_ATI_texture_float, GL_ATI_texture_mirror_once, GL_S3_s3tc, GL_EXT_texture_env_add, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_bindable_uniform, GL_EXT_blend_color, GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_compiled_vertex_array, GL_EXT_Cg_shader, GL_EXT_depth_bounds_test, GL_EXT_direct_state_access, GL_EXT_draw_buffers2, GL_EXT_draw_instanced, GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, GL_EXTX_framebuffer_mixed_formats, GL_EXT_framebuffer_multisample_blit_scaled, GL_EXT_framebuffer_object, GL_EXT_framebuffer_sRGB, GL_EXT_geometry_shader4, GL_EXT_gpu_program_parameters, GL_EXT_gpu_shader4, GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, GL_EXT_packed_float, GL_EXT_packed_pixels, GL_EXT_pixel_buffer_object, GL_EXT_point_parameters, GL_EXT_provoking_vertex, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_shader_objects, GL_EXT_separate_specular_color, GL_EXT_shader_image_load_store, GL_EXT_shader_integer_mix, GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_texture3D, GL_EXT_texture_array, GL_EXT_texture_buffer_object, GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_latc, GL_EXT_texture_compression_rgtc, GL_EXT_texture_compression_s3tc, GL_EXT_texture_cube_map, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, GL_EXT_texture_lod, GL_EXT_texture_lod_bias, GL_EXT_texture_mirror_clamp, GL_EXT_texture_object, GL_EXT_texture_shared_exponent, GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, GL_EXT_texture_storage, GL_EXT_texture_swizzle, GL_EXT_timer_query, GL_EXT_transform_feedback2, GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, GL_EXT_vertex_attrib_64bit, GL_EXT_x11_sync_object, GL_EXT_import_sync_object, GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat, GL_KHR_debug, GL_KTX_buffer_region, GL_NV_bindless_multi_draw_indirect, GL_NV_bindless_multi_draw_indirect_count, GL_NV_bindless_texture, GL_NV_blend_equation_advanced, GL_NV_blend_square, GL_NV_compute_program5, GL_NV_conditional_render, GL_NV_copy_depth_to_color, GL_NV_copy_image, GL_NV_depth_buffer_float, GL_NV_depth_clamp, GL_NV_draw_texture, GL_NV_ES1_1_compatibility, GL_NV_ES3_1_compatibility, GL_NV_explicit_multisample, GL_NV_fence, GL_NV_float_buffer, GL_NV_fog_distance, GL_NV_fragment_program, GL_NV_fragment_program_option, GL_NV_fragment_program2, GL_NV_framebuffer_multisample_coverage, GL_NV_geometry_shader4, GL_NV_gpu_program4, GL_NV_gpu_program4_1, GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended, GL_NV_gpu_program_fp64, GL_NV_gpu_shader5, GL_NV_half_float, GL_NV_light_max_exponent, GL_NV_multisample_coverage, GL_NV_multisample_filter_hint, GL_NV_occlusion_query, GL_NV_packed_depth_stencil, GL_NV_parameter_buffer_object, GL_NV_parameter_buffer_object2, GL_NV_path_rendering, GL_NV_pixel_data_range, GL_NV_point_sprite, GL_NV_primitive_restart, GL_NV_register_combiners, GL_NV_register_combiners2, GL_NV_shader_atomic_counters, GL_NV_shader_atomic_float, GL_NV_shader_atomic_int64, GL_NV_shader_buffer_load, GL_NV_shader_storage_buffer_object, GL_NV_texgen_reflection, GL_NV_texture_barrier, GL_NV_texture_compression_vtc, GL_NV_texture_env_combine4, GL_NV_texture_expand_normal, GL_NV_texture_multisample, GL_NV_texture_rectangle, GL_NV_texture_shader, GL_NV_texture_shader2, GL_NV_texture_shader3, GL_NV_transform_feedback, GL_NV_transform_feedback2, GL_NV_vdpau_interop, GL_NV_vertex_array_range, GL_NV_vertex_array_range2, GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory, GL_NV_vertex_program, GL_NV_vertex_program1_1, GL_NV_vertex_program2, GL_NV_vertex_program2_option, GL_NV_vertex_program3, GL_NVX_conditional_render, GL_NVX_gpu_memory_info, GL_NVX_nvenc_interop, GL_NV_shader_thread_group, GL_NV_shader_thread_shuffle, GL_KHR_blend_equation_advanced, GL_SGIS_generate_mipmap, GL_SGIS_texture_lod, GL_SGIX_depth_texture, GL_SGIX_shadow, GL_SUN_slice_accum glu version: 1.3 glu extensions: GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat ---------------------------------------------------------------------- 0x274 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 0 0 None 0x275 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 0 0 None 0x277 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 0 0 None 0x278 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 0 0 None 0x279 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 0 0 None 0x27a 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 0 0 None 0x27b 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 0 0 None 0x27c 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 0 0 None 0x27d 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 0 0 None 0x27e 24 tc 0 24 0 r y . 8 8 8 0 4 0 0 16 16 16 16 0 0 None 0x27f 24 tc 0 32 0 r y . 8 8 8 8 4 0 0 16 16 16 16 0 0 None 0x280 24 tc 0 24 0 r . . 8 8 8 0 4 0 0 16 16 16 16 0 0 None 0x281 24 tc 0 32 0 r . . 8 8 8 8 4 0 0 16 16 16 16 0 0 None 0x282 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon 0x283 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon 0x284 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon 0x285 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon 0x286 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon 0x287 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon 0x288 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon 0x289 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon 0x28a 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon 0x28b 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon 0x28c 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon 0x28d 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon 0x28e 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon 0x28f 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon 0x290 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon 0x291 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon 0x292 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x293 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x294 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x295 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x296 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x297 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x298 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x299 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x29a 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x29b 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x29c 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x29d 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x29e 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x29f 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x2a0 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x2a1 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x2a2 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x2a3 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x2a4 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x2a5 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x2a6 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x2a7 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x2a8 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x2a9 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x2aa 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x2ab 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x2ac 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x2ad 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x2ae 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x2af 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x2b0 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x2b1 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x2b2 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x2b3 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x2b4 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x2b5 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x2b6 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x2b7 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x2b8 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x2b9 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x2ba 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon 0x2bb 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon 0x2bc 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon 0x2bd 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon 0x2be 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon 0x2bf 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon 0x2c0 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon 0x2c1 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon 0x2c2 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 0 0 None 0x2c3 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 0 0 None 0x2c4 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 0 0 None 0x2c5 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 0 0 None 0x2c6 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 0 0 None 0x2c7 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 0 0 None 0x2c8 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 0 0 None 0x2c9 24 dc 0 24 0 r y . 8 8 8 0 4 0 0 16 16 16 16 0 0 None 0x2ca 24 dc 0 32 0 r y . 8 8 8 8 4 0 0 16 16 16 16 0 0 None 0x2cb 24 dc 0 24 0 r . . 8 8 8 0 4 0 0 16 16 16 16 0 0 None 0x2cc 24 dc 0 32 0 r . . 8 8 8 8 4 0 0 16 16 16 16 0 0 None 0x2cd 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon 0x2ce 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon 0x2cf 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon 0x2d0 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon 0x2d1 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon 0x2d2 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon 0x2d3 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon 0x2d4 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon 0x2d5 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon 0x2d6 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon 0x2d7 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon 0x2d8 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon 0x2d9 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon 0x2da 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon 0x2db 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon 0x2dc 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon 0x2dd 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x2de 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x2df 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x2e0 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x2e1 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x2e2 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x2e3 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x2e4 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x2e5 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x2e6 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x2e7 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x2e8 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x2e9 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x2ea 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x2eb 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x2ec 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x2ed 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x2ee 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x2ef 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x2f0 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x2f1 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x2f2 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x2f3 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x2f4 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x2f5 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x2f6 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x2f7 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x2f8 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x2f9 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x2fa 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x2fb 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x2fc 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x2fd 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x2fe 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x2ff 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x300 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x301 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x302 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x303 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x304 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x305 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon 0x306 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon 0x307 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon 0x308 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon 0x309 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon 0x30a 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon 0x30b 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon 0x30c 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon 0x276 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 0 0 None 0x30d 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 0 0 None 0x30e 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 0 0 None 0x30f 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 0 0 None 0x310 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 0 0 None 0x311 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 0 0 None 0x312 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 0 0 None 0x313 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 0 0 None 0x314 32 tc 0 24 0 r y . 8 8 8 0 4 0 0 16 16 16 16 0 0 None 0x315 32 tc 0 32 0 r y . 8 8 8 8 4 0 0 16 16 16 16 0 0 None 0x316 32 tc 0 24 0 r . . 8 8 8 0 4 0 0 16 16 16 16 0 0 None 0x317 32 tc 0 32 0 r . . 8 8 8 8 4 0 0 16 16 16 16 0 0 None 0x318 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon 0x319 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon 0x31a 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon 0x31b 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon 0x31c 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon 0x31d 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon 0x31e 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon 0x31f 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon 0x320 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon 0x321 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon 0x322 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon 0x323 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon 0x324 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon 0x325 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon 0x326 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon 0x327 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon 0x328 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x329 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x32a 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x32b 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x32c 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x32d 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x32e 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x32f 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x330 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x331 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x332 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x333 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x334 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x335 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x336 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x337 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x338 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x339 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x33a 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x33b 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x33c 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x33d 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x33e 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon 0x33f 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon 0x340 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x341 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon 0x342 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x343 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon 0x344 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x345 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x346 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x347 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x348 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x349 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x34a 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon 0x34b 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon 0x34c 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x34d 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon 0x34e 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x34f 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon 0x350 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon 0x351 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon 0x352 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon 0x353 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon 0x354 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon 0x355 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon 0x356 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon 0x357 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon > -jeff >> >> >> >> >> David E DeMarle >> Kitware, Inc. >> R&D Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 >> >> On Wed, Jun 10, 2015 at 2:58 PM, Aashish Chaudhary >> > > wrote: >> >> No, I don't think so. It would be nice if you can try Burlen >> suggestion to see if it works for built in datasets / sources. >> >> - Aashish >> >> On Wed, Jun 10, 2015 at 2:49 PM, Jeff Becker >> > wrote: >> >> On 06/10/2015 11:46 AM, Burlen Loring wrote: >> >> Hmm. If Bunyk ray cast doesn't work some thing strange is >> going on as that is a software(non gpu) algorithm and >> should always work. >> >> Can you get anything to show up using a small test data? >> For example create a wavelet source and apply a threshold >> (use default values) to convert to unstructured data. If >> that works maybe something with your input data, or size >> of it. >> >> >> It's a 500 by 500 by 500 grid of floats - is that too big? >> >> >> On 06/10/2015 11:27 AM, Jeff Becker wrote: >> >> On 06/10/2015 11:06 AM, Burlen Loring wrote: >> >> 2 things to try: set the remote render threshold >> to zero, and if that doesn't get it to show up, >> change the mapper to Bunyk ray cast. One of >> those usually works depending on what the cause >> of the issue is. >> >> >> I have both of those set - no luck. BTW, this is >> ParaView 4.3.1 on an NVIDIA backend. glxinfo shows: >> >> $ glxinfo | head -30 >> name of display: :0.0 >> display: :0 screen: 0 >> direct rendering: Yes >> server glx vendor string: NVIDIA Corporation >> server glx version string: 1.4 >> server glx extensions: >> GLX_EXT_visual_info, GLX_EXT_visual_rating, >> GLX_SGIX_fbconfig, >> GLX_SGIX_pbuffer, GLX_SGI_video_sync, >> GLX_SGI_swap_control, >> GLX_EXT_swap_control, GLX_EXT_swap_control_tear, >> GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, >> GLX_ARB_create_context, >> GLX_ARB_create_context_profile, >> GLX_EXT_create_context_es_profile, >> GLX_EXT_create_context_es2_profile, >> GLX_ARB_create_context_robustness, >> GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, >> GLX_ARB_multisample, >> GLX_NV_float_buffer, GLX_ARB_fbconfig_float, >> GLX_EXT_framebuffer_sRGB, >> GLX_NV_multisample_coverage >> client glx vendor string: NVIDIA Corporation >> client glx version string: 1.4 >> client glx extensions: >> GLX_ARB_get_proc_address, GLX_ARB_multisample, >> GLX_EXT_visual_info, >> GLX_EXT_visual_rating, GLX_EXT_import_context, >> GLX_SGI_video_sync, >> GLX_NV_swap_group, GLX_NV_video_out, >> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, >> GLX_SGI_swap_control, GLX_EXT_swap_control, >> GLX_EXT_swap_control_tear, >> GLX_EXT_buffer_age, GLX_ARB_create_context, >> GLX_ARB_create_context_profile, GLX_NV_float_buffer, >> GLX_ARB_fbconfig_float, >> GLX_EXT_fbconfig_packed_float, >> GLX_EXT_texture_from_pixmap, >> GLX_EXT_framebuffer_sRGB, >> GLX_NV_present_video, GLX_NV_copy_image, >> GLX_NV_multisample_coverage, >> GLX_NV_video_capture, >> GLX_EXT_create_context_es_profile, >> GLX_EXT_create_context_es2_profile, >> GLX_ARB_create_context_robustness, >> GLX_NV_delay_before_swap, GLX_EXT_stereo_tree >> >> >> On 06/10/2015 11:00 AM, Jeff Becker wrote: >> >> Hi. I have an unstructured grid file that >> opens and displays in Surface Rendering mode. >> If I switch to Volume Rendering, I don't see >> any output. Any ideas? >> >> Thanks. >> >> -jeff >> _______________________________________________ >> Powered by www.kitware.com >> >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the >> ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: >> http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: >> http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> >> -- >> /| Aashish Chaudhary >> | Technical Leader >> | Kitware Inc. >> / >> /| http://www.kitware.com/company/team/chaudhary.html/ >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Thu Jun 11 15:52:11 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Thu, 11 Jun 2015 15:52:11 -0400 Subject: [Paraview] Info about AMR datasets/structures In-Reply-To: References: Message-ID: Hi John, There is some info here: http://www.kitware.com/source/home/post/32 It doesn't answer all the questions you asked but it is a decent reference. vtkOverlappingAMR implements a somewhat strict Berger-Colella style AMR hierarchy: * Refinement ratio across levels is constant * Each block at levels > 0 need to be covered 100% by one parent block of previous level * Some other restriction about what happens at the boundary that I forget So it won't do what you want. You can directly use vtkUniformGridAMR, which does not impose any restrictions. Most filters should work for this class - there just wouldn't be any specialized filters such as the dual-grid contour / clip ones for the vtkOverlappingAMR. Best, -berk On Wed, Jun 10, 2015 at 5:40 PM, Biddiscombe, John A. wrote: > Dear list, > > I would like to generate some AMR data structures from custom data and > filters, but I?m having trouble locating information about the > format/relationships of AMR blocks. The wiki contains old outdated > references to the heirarchicalbox structures and not to the overlapping and > non overlapping AMR formats. > > Specifically, I?d like to know if each level of AMR boxes must always > have a fixed refinement level wrt to the level above, or whether I can > refine arbitrarily (i.e. Have a root box of resolution x and sub boxes with > different subdivision ratios at the same level). Also, the overlapping AMR > dataset examples I?ve looked at seem to use an oct tree style decomposition > where each node must be subdivided along mid planes, can I use a pure > BSPtree where every node is subdivided along any axis at any point on the > axis and still maintain a non overlapping amr dataset? > > The vtkAMRInformation documentation consists only of > > Refinement ratio between AMR levels > Grid spacing for each level > The file block index for each block > parent child information, if requested > > > But does the refinement ratio have to be constant for each level? > Most of the paraview filters appear to be greyed out for > vtkNonOverlappingAMR data, whereas the Overlapping appears to have support > for certain operations like contouring and slicing ? is it the case that > only nonoverlapping datasets are supported for these operations. > > If there is detailed info anywhere, could someone please send me a link. > > Thanks > > JB > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Thu Jun 11 16:05:09 2015 From: burlen.loring at gmail.com (Burlen Loring) Date: Thu, 11 Jun 2015 13:05:09 -0700 Subject: [Paraview] Selecting volume rendering causes output to vanish In-Reply-To: <5579CAE0.9030403@nasa.gov> References: <55787B45.4000606@nasa.gov> <55787C89.5080409@gmail.com> <55788182.4040206@nasa.gov> <5578861C.4060407@gmail.com> <557886A6.5080606@nasa.gov> <5578A8E4.90703@nasa.gov> <5579CAE0.9030403@nasa.gov> Message-ID: <5579E9F5.4050206@gmail.com> you ran out of memory. You may need more than 1 node, and a parallel file format. You mentioned that you had a grid of 500 x 500 points. You could save a lot of memory by using vtkImageData, vtkRectilinearMesh or vtkStructuredGrid if your data is amenable to one of those. On 06/11/2015 10:52 AM, Jeff Becker wrote: > On 06/10/2015 02:15 PM, Jeff Becker wrote: >> On 06/10/2015 12:03 PM, David E DeMarle wrote: >>> Probably the content isn't amenable to volume rendering. To be so, >>> the unstructured grid has to have volumetric cells in it (tets, >>> voxels, etc). If it just has polys or lines or points in it, they >>> won't appear. You'll have to resample of splat onto the data onto a >>> volumetric grid in that case. >> >> That's it! I created an unstructured grid of points from a data file >> using VTK. I'll see about resampling to volumetric grid. Thanks. >> > > After opening my file, and hitting apply to get it on the screen,I > tried using ParaView's Delaunay 3D filter, and got the following: > > $ mpirun -np 1 /usr/bin/env DISPLAY=:0 > /u/jcbecker/ParaView-4.3.1-Linux-64bit/bin/pvserver > --client-host=pfe23 --use-offscreen-rendering > Waiting for client... > Connection URL: cs://maia34:11111 > Accepting connection(s): maia34:11111 > Client connected. > terminate called after throwing an instance of 'St9bad_alloc' > what(): std::bad_alloc > > This server has 64GB memory. Output from glxinfo is below: > > name of display: :0.0 > display: :0 screen: 0 > direct rendering: Yes > server glx vendor string: NVIDIA Corporation > server glx version string: 1.4 > server glx extensions: > GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, > GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, > GLX_EXT_swap_control, GLX_EXT_swap_control_tear, > GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, > GLX_ARB_create_context, > GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile, > GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness, > GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, GLX_ARB_multisample, > GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB, > GLX_NV_multisample_coverage > client glx vendor string: NVIDIA Corporation > client glx version string: 1.4 > client glx extensions: > GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info, > GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync, > GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, > GLX_SGIX_pbuffer, > GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, > GLX_EXT_buffer_age, GLX_ARB_create_context, > GLX_ARB_create_context_profile, GLX_NV_float_buffer, > GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float, > GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB, > GLX_NV_present_video, GLX_NV_copy_image, GLX_NV_multisample_coverage, > GLX_NV_video_capture, GLX_EXT_create_context_es_profile, > GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness, > GLX_NV_delay_before_swap, GLX_EXT_stereo_tree > GLX extensions: > GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, > GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, > GLX_EXT_swap_control, GLX_EXT_swap_control_tear, > GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, > GLX_ARB_create_context, > GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile, > GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness, > GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, GLX_ARB_multisample, > GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB, > GLX_NV_multisample_coverage, GLX_ARB_get_proc_address > OpenGL vendor string: NVIDIA Corporation > OpenGL renderer string: Tesla K40m/PCIe/SSE2 > OpenGL version string: 4.4.0 NVIDIA 340.65 > OpenGL extensions: > GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture, > GL_ARB_arrays_of_arrays, GL_ARB_base_instance, > GL_ARB_bindless_texture, > GL_ARB_blend_func_extended, GL_ARB_buffer_storage, > GL_ARB_clear_buffer_object, GL_ARB_clear_texture, > GL_ARB_color_buffer_float, GL_ARB_compatibility, > GL_ARB_compressed_texture_pixel_storage, GL_ARB_conservative_depth, > GL_ARB_compute_shader, GL_ARB_compute_variable_group_size, > GL_ARB_copy_buffer, GL_ARB_copy_image, GL_ARB_debug_output, > GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_depth_texture, > GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_indirect, > GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, > GL_ARB_enhanced_layouts, GL_ARB_ES2_compatibility, > GL_ARB_ES3_compatibility, GL_ARB_explicit_attrib_location, > GL_ARB_explicit_uniform_location, GL_ARB_fragment_coord_conventions, > GL_ARB_fragment_layer_viewport, GL_ARB_fragment_program, > GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader, > GL_ARB_framebuffer_no_attachments, GL_ARB_framebuffer_object, > GL_ARB_framebuffer_sRGB, GL_ARB_geometry_shader4, > GL_ARB_get_program_binary, GL_ARB_gpu_shader5, GL_ARB_gpu_shader_fp64, > GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_imaging, > GL_ARB_indirect_parameters, GL_ARB_instanced_arrays, > GL_ARB_internalformat_query, GL_ARB_internalformat_query2, > GL_ARB_invalidate_subdata, GL_ARB_map_buffer_alignment, > GL_ARB_map_buffer_range, GL_ARB_multi_bind, > GL_ARB_multi_draw_indirect, > GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, > GL_ARB_occlusion_query2, GL_ARB_pixel_buffer_object, > GL_ARB_point_parameters, GL_ARB_point_sprite, > GL_ARB_program_interface_query, GL_ARB_provoking_vertex, > GL_ARB_robust_buffer_access_behavior, GL_ARB_robustness, > GL_ARB_sample_shading, GL_ARB_sampler_objects, > GL_ARB_seamless_cube_map, > GL_ARB_seamless_cubemap_per_texture, GL_ARB_separate_shader_objects, > GL_ARB_shader_atomic_counters, GL_ARB_shader_bit_encoding, > GL_ARB_shader_draw_parameters, GL_ARB_shader_group_vote, > GL_ARB_shader_image_load_store, GL_ARB_shader_image_size, > GL_ARB_shader_objects, GL_ARB_shader_precision, > GL_ARB_query_buffer_object, GL_ARB_shader_storage_buffer_object, > GL_ARB_shader_subroutine, GL_ARB_shader_texture_lod, > GL_ARB_shading_language_100, GL_ARB_shading_language_420pack, > GL_ARB_shading_language_include, GL_ARB_shading_language_packing, > GL_ARB_shadow, GL_ARB_sparse_texture, GL_ARB_stencil_texturing, > GL_ARB_sync, GL_ARB_tessellation_shader, GL_ARB_texture_border_clamp, > GL_ARB_texture_buffer_object, GL_ARB_texture_buffer_object_rgb32, > GL_ARB_texture_buffer_range, GL_ARB_texture_compression, > GL_ARB_texture_compression_bptc, GL_ARB_texture_compression_rgtc, > GL_ARB_texture_cube_map, GL_ARB_texture_cube_map_array, > GL_ARB_texture_env_add, GL_ARB_texture_env_combine, > GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, > GL_ARB_texture_float, GL_ARB_texture_gather, > GL_ARB_texture_mirror_clamp_to_edge, GL_ARB_texture_mirrored_repeat, > GL_ARB_texture_multisample, GL_ARB_texture_non_power_of_two, > GL_ARB_texture_query_levels, GL_ARB_texture_query_lod, > GL_ARB_texture_rectangle, GL_ARB_texture_rg, > GL_ARB_texture_rgb10_a2ui, > GL_ARB_texture_stencil8, GL_ARB_texture_storage, > GL_ARB_texture_storage_multisample, GL_ARB_texture_swizzle, > GL_ARB_texture_view, GL_ARB_timer_query, GL_ARB_transform_feedback2, > GL_ARB_transform_feedback3, GL_ARB_transform_feedback_instanced, > GL_ARB_transpose_matrix, GL_ARB_uniform_buffer_object, > GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, > GL_ARB_vertex_attrib_64bit, GL_ARB_vertex_attrib_binding, > GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, > GL_ARB_vertex_shader, > GL_ARB_vertex_type_10f_11f_11f_rev, GL_ARB_vertex_type_2_10_10_10_rev, > GL_ARB_viewport_array, GL_ARB_window_pos, GL_ATI_draw_buffers, > GL_ATI_texture_float, GL_ATI_texture_mirror_once, GL_S3_s3tc, > GL_EXT_texture_env_add, GL_EXT_abgr, GL_EXT_bgra, > GL_EXT_bindable_uniform, GL_EXT_blend_color, > GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate, > GL_EXT_blend_minmax, GL_EXT_blend_subtract, > GL_EXT_compiled_vertex_array, > GL_EXT_Cg_shader, GL_EXT_depth_bounds_test, > GL_EXT_direct_state_access, > GL_EXT_draw_buffers2, GL_EXT_draw_instanced, > GL_EXT_draw_range_elements, > GL_EXT_fog_coord, GL_EXT_framebuffer_blit, > GL_EXT_framebuffer_multisample, > GL_EXTX_framebuffer_mixed_formats, > GL_EXT_framebuffer_multisample_blit_scaled, GL_EXT_framebuffer_object, > GL_EXT_framebuffer_sRGB, GL_EXT_geometry_shader4, > GL_EXT_gpu_program_parameters, GL_EXT_gpu_shader4, > GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, > GL_EXT_packed_float, GL_EXT_packed_pixels, GL_EXT_pixel_buffer_object, > GL_EXT_point_parameters, GL_EXT_provoking_vertex, > GL_EXT_rescale_normal, > GL_EXT_secondary_color, GL_EXT_separate_shader_objects, > GL_EXT_separate_specular_color, GL_EXT_shader_image_load_store, > GL_EXT_shader_integer_mix, GL_EXT_shadow_funcs, > GL_EXT_stencil_two_side, > GL_EXT_stencil_wrap, GL_EXT_texture3D, GL_EXT_texture_array, > GL_EXT_texture_buffer_object, GL_EXT_texture_compression_dxt1, > GL_EXT_texture_compression_latc, GL_EXT_texture_compression_rgtc, > GL_EXT_texture_compression_s3tc, GL_EXT_texture_cube_map, > GL_EXT_texture_edge_clamp, GL_EXT_texture_env_combine, > GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic, > GL_EXT_texture_integer, GL_EXT_texture_lod, GL_EXT_texture_lod_bias, > GL_EXT_texture_mirror_clamp, GL_EXT_texture_object, > GL_EXT_texture_shared_exponent, GL_EXT_texture_sRGB, > GL_EXT_texture_sRGB_decode, GL_EXT_texture_storage, > GL_EXT_texture_swizzle, GL_EXT_timer_query, > GL_EXT_transform_feedback2, > GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, > GL_EXT_vertex_attrib_64bit, > GL_EXT_x11_sync_object, GL_EXT_import_sync_object, > GL_IBM_rasterpos_clip, > GL_IBM_texture_mirrored_repeat, GL_KHR_debug, GL_KTX_buffer_region, > GL_NV_bindless_multi_draw_indirect, > GL_NV_bindless_multi_draw_indirect_count, GL_NV_bindless_texture, > GL_NV_blend_equation_advanced, GL_NV_blend_square, > GL_NV_compute_program5, > GL_NV_conditional_render, GL_NV_copy_depth_to_color, GL_NV_copy_image, > GL_NV_depth_buffer_float, GL_NV_depth_clamp, GL_NV_draw_texture, > GL_NV_ES1_1_compatibility, GL_NV_ES3_1_compatibility, > GL_NV_explicit_multisample, GL_NV_fence, GL_NV_float_buffer, > GL_NV_fog_distance, GL_NV_fragment_program, > GL_NV_fragment_program_option, > GL_NV_fragment_program2, GL_NV_framebuffer_multisample_coverage, > GL_NV_geometry_shader4, GL_NV_gpu_program4, GL_NV_gpu_program4_1, > GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended, > GL_NV_gpu_program_fp64, GL_NV_gpu_shader5, GL_NV_half_float, > GL_NV_light_max_exponent, GL_NV_multisample_coverage, > GL_NV_multisample_filter_hint, GL_NV_occlusion_query, > GL_NV_packed_depth_stencil, GL_NV_parameter_buffer_object, > GL_NV_parameter_buffer_object2, GL_NV_path_rendering, > GL_NV_pixel_data_range, GL_NV_point_sprite, GL_NV_primitive_restart, > GL_NV_register_combiners, GL_NV_register_combiners2, > GL_NV_shader_atomic_counters, GL_NV_shader_atomic_float, > GL_NV_shader_atomic_int64, GL_NV_shader_buffer_load, > GL_NV_shader_storage_buffer_object, GL_NV_texgen_reflection, > GL_NV_texture_barrier, GL_NV_texture_compression_vtc, > GL_NV_texture_env_combine4, GL_NV_texture_expand_normal, > GL_NV_texture_multisample, GL_NV_texture_rectangle, > GL_NV_texture_shader, > GL_NV_texture_shader2, GL_NV_texture_shader3, > GL_NV_transform_feedback, > GL_NV_transform_feedback2, GL_NV_vdpau_interop, > GL_NV_vertex_array_range, > GL_NV_vertex_array_range2, GL_NV_vertex_attrib_integer_64bit, > GL_NV_vertex_buffer_unified_memory, GL_NV_vertex_program, > GL_NV_vertex_program1_1, GL_NV_vertex_program2, > GL_NV_vertex_program2_option, GL_NV_vertex_program3, > GL_NVX_conditional_render, GL_NVX_gpu_memory_info, > GL_NVX_nvenc_interop, > GL_NV_shader_thread_group, GL_NV_shader_thread_shuffle, > GL_KHR_blend_equation_advanced, GL_SGIS_generate_mipmap, > GL_SGIS_texture_lod, GL_SGIX_depth_texture, GL_SGIX_shadow, > GL_SUN_slice_accum > glu version: 1.3 > glu extensions: > GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess > > visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav > id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat > ---------------------------------------------------------------------- > 0x21 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 0 0 None > 0x22 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 0 0 None > 0x24 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 0 0 None > 0x25 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 0 0 None > 0x26 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 0 0 None > 0x27 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 0 0 None > 0x28 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 0 0 None > 0x29 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 0 0 None > 0x2a 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 0 0 None > 0x2b 24 tc 0 24 0 r y . 8 8 8 0 4 0 0 16 16 16 16 0 0 None > 0x2c 24 tc 0 32 0 r y . 8 8 8 8 4 0 0 16 16 16 16 0 0 None > 0x2d 24 tc 0 24 0 r . . 8 8 8 0 4 0 0 16 16 16 16 0 0 None > 0x2e 24 tc 0 32 0 r . . 8 8 8 8 4 0 0 16 16 16 16 0 0 None > 0x2f 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon > 0x30 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon > 0x31 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon > 0x32 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon > 0x33 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon > 0x34 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon > 0x35 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon > 0x36 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon > 0x37 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon > 0x38 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon > 0x39 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon > 0x3a 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon > 0x3b 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon > 0x3c 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon > 0x3d 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon > 0x3e 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon > 0x3f 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x40 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x41 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x42 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x43 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x44 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x45 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x46 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x47 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x48 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x49 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x4a 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x4b 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x4c 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x4d 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x4e 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x4f 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x50 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x51 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x52 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x53 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x54 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x55 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x56 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x57 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x58 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x59 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x5a 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x5b 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x5c 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x5d 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x5e 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x5f 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x60 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x61 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x62 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x63 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x64 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x65 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x66 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x67 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon > 0x68 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon > 0x69 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon > 0x6a 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon > 0x6b 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon > 0x6c 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon > 0x6d 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon > 0x6e 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon > 0x6f 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 0 0 None > 0x70 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 0 0 None > 0x71 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 0 0 None > 0x72 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 0 0 None > 0x73 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 0 0 None > 0x74 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 0 0 None > 0x75 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 0 0 None > 0x76 24 dc 0 24 0 r y . 8 8 8 0 4 0 0 16 16 16 16 0 0 None > 0x77 24 dc 0 32 0 r y . 8 8 8 8 4 0 0 16 16 16 16 0 0 None > 0x78 24 dc 0 24 0 r . . 8 8 8 0 4 0 0 16 16 16 16 0 0 None > 0x79 24 dc 0 32 0 r . . 8 8 8 8 4 0 0 16 16 16 16 0 0 None > 0x7a 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon > 0x7b 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon > 0x7c 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon > 0x7d 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon > 0x7e 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon > 0x7f 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon > 0x80 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon > 0x81 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon > 0x82 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon > 0x83 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon > 0x84 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon > 0x85 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon > 0x86 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon > 0x87 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon > 0x88 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon > 0x89 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon > 0x8a 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x8b 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x8c 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x8d 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x8e 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x8f 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x90 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x91 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x92 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x93 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x94 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x95 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x96 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x97 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x98 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x99 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x9a 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x9b 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x9c 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x9d 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x9e 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x9f 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0xa0 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0xa1 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0xa2 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0xa3 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0xa4 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0xa5 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0xa6 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0xa7 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0xa8 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0xa9 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0xaa 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0xab 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0xac 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0xad 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0xae 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0xaf 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0xb0 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0xb1 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0xb2 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon > 0xb3 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon > 0xb4 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon > 0xb5 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon > 0xb6 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon > 0xb7 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon > 0xb8 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon > 0xb9 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon > 0x23 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 0 0 None > 0xba 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 0 0 None > 0xbb 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 0 0 None > 0xbc 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 0 0 None > 0xbd 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 0 0 None > 0xbe 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 0 0 None > 0xbf 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 0 0 None > 0xc0 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 0 0 None > 0xc1 32 tc 0 24 0 r y . 8 8 8 0 4 0 0 16 16 16 16 0 0 None > 0xc2 32 tc 0 32 0 r y . 8 8 8 8 4 0 0 16 16 16 16 0 0 None > 0xc3 32 tc 0 24 0 r . . 8 8 8 0 4 0 0 16 16 16 16 0 0 None > 0xc4 32 tc 0 32 0 r . . 8 8 8 8 4 0 0 16 16 16 16 0 0 None > 0xc5 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon > 0xc6 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon > 0xc7 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon > 0xc8 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon > 0xc9 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon > 0xca 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon > 0xcb 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon > 0xcc 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon > 0xcd 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon > 0xce 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon > 0xcf 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon > 0xd0 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon > 0xd1 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon > 0xd2 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon > 0xd3 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon > 0xd4 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon > 0xd5 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0xd6 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0xd7 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0xd8 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0xd9 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0xda 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0xdb 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0xdc 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0xdd 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0xde 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0xdf 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0xe0 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0xe1 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0xe2 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0xe3 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0xe4 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0xe5 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0xe6 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0xe7 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0xe8 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0xe9 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0xea 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0xeb 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0xec 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0xed 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0xee 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0xef 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0xf0 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0xf1 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0xf2 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0xf3 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0xf4 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0xf5 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0xf6 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0xf7 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0xf8 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0xf9 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0xfa 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0xfb 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0xfc 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0xfd 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon > 0xfe 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon > 0xff 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon > 0x100 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon > 0x101 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon > 0x102 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon > 0x103 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon > 0x104 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon > > > display: :0 screen: 1 > direct rendering: Yes > server glx vendor string: NVIDIA Corporation > server glx version string: 1.4 > server glx extensions: > GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, > GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, > GLX_EXT_swap_control, GLX_EXT_swap_control_tear, > GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, > GLX_ARB_create_context, > GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile, > GLX_EXT_create_context_es2_profile, > GLX_ARB_create_context_robustness, > GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, GLX_ARB_multisample, > GLX_NV_float_buffer, GLX_ARB_fbconfig_float, > GLX_EXT_framebuffer_sRGB, > GLX_NV_multisample_coverage > client glx vendor string: NVIDIA Corporation > client glx version string: 1.4 > client glx extensions: > GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info, > GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync, > GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, > GLX_SGIX_pbuffer, > GLX_SGI_swap_control, GLX_EXT_swap_control, > GLX_EXT_swap_control_tear, > GLX_EXT_buffer_age, GLX_ARB_create_context, > GLX_ARB_create_context_profile, GLX_NV_float_buffer, > GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float, > GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB, > GLX_NV_present_video, GLX_NV_copy_image, GLX_NV_multisample_coverage, > GLX_NV_video_capture, GLX_EXT_create_context_es_profile, > GLX_EXT_create_context_es2_profile, > GLX_ARB_create_context_robustness, > GLX_NV_delay_before_swap, GLX_EXT_stereo_tree > GLX extensions: > GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, > GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, > GLX_EXT_swap_control, GLX_EXT_swap_control_tear, > GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, > GLX_ARB_create_context, > GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile, > GLX_EXT_create_context_es2_profile, > GLX_ARB_create_context_robustness, > GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, GLX_ARB_multisample, > GLX_NV_float_buffer, GLX_ARB_fbconfig_float, > GLX_EXT_framebuffer_sRGB, > GLX_NV_multisample_coverage, GLX_ARB_get_proc_address > OpenGL vendor string: NVIDIA Corporation > OpenGL renderer string: Tesla K40m/PCIe/SSE2 > OpenGL version string: 4.4.0 NVIDIA 340.65 > OpenGL extensions: > GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture, > GL_ARB_arrays_of_arrays, GL_ARB_base_instance, > GL_ARB_bindless_texture, > GL_ARB_blend_func_extended, GL_ARB_buffer_storage, > GL_ARB_clear_buffer_object, GL_ARB_clear_texture, > GL_ARB_color_buffer_float, GL_ARB_compatibility, > GL_ARB_compressed_texture_pixel_storage, GL_ARB_conservative_depth, > GL_ARB_compute_shader, GL_ARB_compute_variable_group_size, > GL_ARB_copy_buffer, GL_ARB_copy_image, GL_ARB_debug_output, > GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_depth_texture, > GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_indirect, > GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, > GL_ARB_enhanced_layouts, GL_ARB_ES2_compatibility, > GL_ARB_ES3_compatibility, GL_ARB_explicit_attrib_location, > GL_ARB_explicit_uniform_location, GL_ARB_fragment_coord_conventions, > GL_ARB_fragment_layer_viewport, GL_ARB_fragment_program, > GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader, > GL_ARB_framebuffer_no_attachments, GL_ARB_framebuffer_object, > GL_ARB_framebuffer_sRGB, GL_ARB_geometry_shader4, > GL_ARB_get_program_binary, GL_ARB_gpu_shader5, > GL_ARB_gpu_shader_fp64, > GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_imaging, > GL_ARB_indirect_parameters, GL_ARB_instanced_arrays, > GL_ARB_internalformat_query, GL_ARB_internalformat_query2, > GL_ARB_invalidate_subdata, GL_ARB_map_buffer_alignment, > GL_ARB_map_buffer_range, GL_ARB_multi_bind, > GL_ARB_multi_draw_indirect, > GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, > GL_ARB_occlusion_query2, GL_ARB_pixel_buffer_object, > GL_ARB_point_parameters, GL_ARB_point_sprite, > GL_ARB_program_interface_query, GL_ARB_provoking_vertex, > GL_ARB_robust_buffer_access_behavior, GL_ARB_robustness, > GL_ARB_sample_shading, GL_ARB_sampler_objects, > GL_ARB_seamless_cube_map, > GL_ARB_seamless_cubemap_per_texture, GL_ARB_separate_shader_objects, > GL_ARB_shader_atomic_counters, GL_ARB_shader_bit_encoding, > GL_ARB_shader_draw_parameters, GL_ARB_shader_group_vote, > GL_ARB_shader_image_load_store, GL_ARB_shader_image_size, > GL_ARB_shader_objects, GL_ARB_shader_precision, > GL_ARB_query_buffer_object, GL_ARB_shader_storage_buffer_object, > GL_ARB_shader_subroutine, GL_ARB_shader_texture_lod, > GL_ARB_shading_language_100, GL_ARB_shading_language_420pack, > GL_ARB_shading_language_include, GL_ARB_shading_language_packing, > GL_ARB_shadow, GL_ARB_sparse_texture, GL_ARB_stencil_texturing, > GL_ARB_sync, GL_ARB_tessellation_shader, GL_ARB_texture_border_clamp, > GL_ARB_texture_buffer_object, GL_ARB_texture_buffer_object_rgb32, > GL_ARB_texture_buffer_range, GL_ARB_texture_compression, > GL_ARB_texture_compression_bptc, GL_ARB_texture_compression_rgtc, > GL_ARB_texture_cube_map, GL_ARB_texture_cube_map_array, > GL_ARB_texture_env_add, GL_ARB_texture_env_combine, > GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, > GL_ARB_texture_float, GL_ARB_texture_gather, > GL_ARB_texture_mirror_clamp_to_edge, GL_ARB_texture_mirrored_repeat, > GL_ARB_texture_multisample, GL_ARB_texture_non_power_of_two, > GL_ARB_texture_query_levels, GL_ARB_texture_query_lod, > GL_ARB_texture_rectangle, GL_ARB_texture_rg, > GL_ARB_texture_rgb10_a2ui, > GL_ARB_texture_stencil8, GL_ARB_texture_storage, > GL_ARB_texture_storage_multisample, GL_ARB_texture_swizzle, > GL_ARB_texture_view, GL_ARB_timer_query, GL_ARB_transform_feedback2, > GL_ARB_transform_feedback3, GL_ARB_transform_feedback_instanced, > GL_ARB_transpose_matrix, GL_ARB_uniform_buffer_object, > GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, > GL_ARB_vertex_attrib_64bit, GL_ARB_vertex_attrib_binding, > GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, > GL_ARB_vertex_shader, > GL_ARB_vertex_type_10f_11f_11f_rev, > GL_ARB_vertex_type_2_10_10_10_rev, > GL_ARB_viewport_array, GL_ARB_window_pos, GL_ATI_draw_buffers, > GL_ATI_texture_float, GL_ATI_texture_mirror_once, GL_S3_s3tc, > GL_EXT_texture_env_add, GL_EXT_abgr, GL_EXT_bgra, > GL_EXT_bindable_uniform, GL_EXT_blend_color, > GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate, > GL_EXT_blend_minmax, GL_EXT_blend_subtract, > GL_EXT_compiled_vertex_array, > GL_EXT_Cg_shader, GL_EXT_depth_bounds_test, > GL_EXT_direct_state_access, > GL_EXT_draw_buffers2, GL_EXT_draw_instanced, > GL_EXT_draw_range_elements, > GL_EXT_fog_coord, GL_EXT_framebuffer_blit, > GL_EXT_framebuffer_multisample, > GL_EXTX_framebuffer_mixed_formats, > GL_EXT_framebuffer_multisample_blit_scaled, > GL_EXT_framebuffer_object, > GL_EXT_framebuffer_sRGB, GL_EXT_geometry_shader4, > GL_EXT_gpu_program_parameters, GL_EXT_gpu_shader4, > GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, > GL_EXT_packed_float, GL_EXT_packed_pixels, > GL_EXT_pixel_buffer_object, > GL_EXT_point_parameters, GL_EXT_provoking_vertex, > GL_EXT_rescale_normal, > GL_EXT_secondary_color, GL_EXT_separate_shader_objects, > GL_EXT_separate_specular_color, GL_EXT_shader_image_load_store, > GL_EXT_shader_integer_mix, GL_EXT_shadow_funcs, > GL_EXT_stencil_two_side, > GL_EXT_stencil_wrap, GL_EXT_texture3D, GL_EXT_texture_array, > GL_EXT_texture_buffer_object, GL_EXT_texture_compression_dxt1, > GL_EXT_texture_compression_latc, GL_EXT_texture_compression_rgtc, > GL_EXT_texture_compression_s3tc, GL_EXT_texture_cube_map, > GL_EXT_texture_edge_clamp, GL_EXT_texture_env_combine, > GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic, > GL_EXT_texture_integer, GL_EXT_texture_lod, GL_EXT_texture_lod_bias, > GL_EXT_texture_mirror_clamp, GL_EXT_texture_object, > GL_EXT_texture_shared_exponent, GL_EXT_texture_sRGB, > GL_EXT_texture_sRGB_decode, GL_EXT_texture_storage, > GL_EXT_texture_swizzle, GL_EXT_timer_query, > GL_EXT_transform_feedback2, > GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, > GL_EXT_vertex_attrib_64bit, > GL_EXT_x11_sync_object, GL_EXT_import_sync_object, > GL_IBM_rasterpos_clip, > GL_IBM_texture_mirrored_repeat, GL_KHR_debug, GL_KTX_buffer_region, > GL_NV_bindless_multi_draw_indirect, > GL_NV_bindless_multi_draw_indirect_count, GL_NV_bindless_texture, > GL_NV_blend_equation_advanced, GL_NV_blend_square, > GL_NV_compute_program5, > GL_NV_conditional_render, GL_NV_copy_depth_to_color, > GL_NV_copy_image, > GL_NV_depth_buffer_float, GL_NV_depth_clamp, GL_NV_draw_texture, > GL_NV_ES1_1_compatibility, GL_NV_ES3_1_compatibility, > GL_NV_explicit_multisample, GL_NV_fence, GL_NV_float_buffer, > GL_NV_fog_distance, GL_NV_fragment_program, > GL_NV_fragment_program_option, > GL_NV_fragment_program2, GL_NV_framebuffer_multisample_coverage, > GL_NV_geometry_shader4, GL_NV_gpu_program4, GL_NV_gpu_program4_1, > GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended, > GL_NV_gpu_program_fp64, GL_NV_gpu_shader5, GL_NV_half_float, > GL_NV_light_max_exponent, GL_NV_multisample_coverage, > GL_NV_multisample_filter_hint, GL_NV_occlusion_query, > GL_NV_packed_depth_stencil, GL_NV_parameter_buffer_object, > GL_NV_parameter_buffer_object2, GL_NV_path_rendering, > GL_NV_pixel_data_range, GL_NV_point_sprite, GL_NV_primitive_restart, > GL_NV_register_combiners, GL_NV_register_combiners2, > GL_NV_shader_atomic_counters, GL_NV_shader_atomic_float, > GL_NV_shader_atomic_int64, GL_NV_shader_buffer_load, > GL_NV_shader_storage_buffer_object, GL_NV_texgen_reflection, > GL_NV_texture_barrier, GL_NV_texture_compression_vtc, > GL_NV_texture_env_combine4, GL_NV_texture_expand_normal, > GL_NV_texture_multisample, GL_NV_texture_rectangle, > GL_NV_texture_shader, > GL_NV_texture_shader2, GL_NV_texture_shader3, > GL_NV_transform_feedback, > GL_NV_transform_feedback2, GL_NV_vdpau_interop, > GL_NV_vertex_array_range, > GL_NV_vertex_array_range2, GL_NV_vertex_attrib_integer_64bit, > GL_NV_vertex_buffer_unified_memory, GL_NV_vertex_program, > GL_NV_vertex_program1_1, GL_NV_vertex_program2, > GL_NV_vertex_program2_option, GL_NV_vertex_program3, > GL_NVX_conditional_render, GL_NVX_gpu_memory_info, > GL_NVX_nvenc_interop, > GL_NV_shader_thread_group, GL_NV_shader_thread_shuffle, > GL_KHR_blend_equation_advanced, GL_SGIS_generate_mipmap, > GL_SGIS_texture_lod, GL_SGIX_depth_texture, GL_SGIX_shadow, > GL_SUN_slice_accum > glu version: 1.3 > glu extensions: > GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess > > visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav > id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat > ---------------------------------------------------------------------- > 0x274 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 0 0 None > 0x275 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 0 0 None > 0x277 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 0 0 None > 0x278 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 0 0 None > 0x279 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 0 0 None > 0x27a 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 0 0 None > 0x27b 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 0 0 None > 0x27c 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 0 0 None > 0x27d 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 0 0 None > 0x27e 24 tc 0 24 0 r y . 8 8 8 0 4 0 0 16 16 16 16 0 0 None > 0x27f 24 tc 0 32 0 r y . 8 8 8 8 4 0 0 16 16 16 16 0 0 None > 0x280 24 tc 0 24 0 r . . 8 8 8 0 4 0 0 16 16 16 16 0 0 None > 0x281 24 tc 0 32 0 r . . 8 8 8 8 4 0 0 16 16 16 16 0 0 None > 0x282 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon > 0x283 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon > 0x284 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon > 0x285 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon > 0x286 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon > 0x287 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon > 0x288 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon > 0x289 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon > 0x28a 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon > 0x28b 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon > 0x28c 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon > 0x28d 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon > 0x28e 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon > 0x28f 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon > 0x290 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon > 0x291 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon > 0x292 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x293 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x294 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x295 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x296 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x297 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x298 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x299 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x29a 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x29b 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x29c 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x29d 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x29e 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x29f 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x2a0 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x2a1 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x2a2 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x2a3 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x2a4 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x2a5 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x2a6 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x2a7 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x2a8 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x2a9 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x2aa 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x2ab 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x2ac 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x2ad 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x2ae 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x2af 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x2b0 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x2b1 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x2b2 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x2b3 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x2b4 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x2b5 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x2b6 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x2b7 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x2b8 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x2b9 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x2ba 24 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon > 0x2bb 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon > 0x2bc 24 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon > 0x2bd 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon > 0x2be 24 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon > 0x2bf 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon > 0x2c0 24 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon > 0x2c1 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon > 0x2c2 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 0 0 None > 0x2c3 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 0 0 None > 0x2c4 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 0 0 None > 0x2c5 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 0 0 None > 0x2c6 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 0 0 None > 0x2c7 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 0 0 None > 0x2c8 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 0 0 None > 0x2c9 24 dc 0 24 0 r y . 8 8 8 0 4 0 0 16 16 16 16 0 0 None > 0x2ca 24 dc 0 32 0 r y . 8 8 8 8 4 0 0 16 16 16 16 0 0 None > 0x2cb 24 dc 0 24 0 r . . 8 8 8 0 4 0 0 16 16 16 16 0 0 None > 0x2cc 24 dc 0 32 0 r . . 8 8 8 8 4 0 0 16 16 16 16 0 0 None > 0x2cd 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon > 0x2ce 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon > 0x2cf 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon > 0x2d0 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon > 0x2d1 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon > 0x2d2 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon > 0x2d3 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon > 0x2d4 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon > 0x2d5 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon > 0x2d6 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon > 0x2d7 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon > 0x2d8 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon > 0x2d9 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon > 0x2da 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon > 0x2db 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon > 0x2dc 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon > 0x2dd 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x2de 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x2df 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x2e0 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x2e1 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x2e2 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x2e3 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x2e4 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x2e5 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x2e6 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x2e7 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x2e8 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x2e9 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x2ea 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x2eb 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x2ec 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x2ed 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x2ee 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x2ef 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x2f0 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x2f1 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x2f2 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x2f3 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x2f4 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x2f5 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x2f6 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x2f7 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x2f8 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x2f9 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x2fa 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x2fb 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x2fc 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x2fd 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x2fe 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x2ff 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x300 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x301 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x302 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x303 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x304 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x305 24 dc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon > 0x306 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon > 0x307 24 dc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon > 0x308 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon > 0x309 24 dc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon > 0x30a 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon > 0x30b 24 dc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon > 0x30c 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon > 0x276 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 0 0 None > 0x30d 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 0 0 None > 0x30e 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 0 0 None > 0x30f 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 0 0 None > 0x310 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 0 0 None > 0x311 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 0 0 None > 0x312 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 0 0 None > 0x313 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 0 0 None > 0x314 32 tc 0 24 0 r y . 8 8 8 0 4 0 0 16 16 16 16 0 0 None > 0x315 32 tc 0 32 0 r y . 8 8 8 8 4 0 0 16 16 16 16 0 0 None > 0x316 32 tc 0 24 0 r . . 8 8 8 0 4 0 0 16 16 16 16 0 0 None > 0x317 32 tc 0 32 0 r . . 8 8 8 8 4 0 0 16 16 16 16 0 0 None > 0x318 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon > 0x319 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon > 0x31a 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon > 0x31b 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon > 0x31c 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon > 0x31d 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon > 0x31e 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon > 0x31f 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon > 0x320 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon > 0x321 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon > 0x322 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon > 0x323 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon > 0x324 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon > 0x325 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon > 0x326 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon > 0x327 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon > 0x328 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x329 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x32a 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x32b 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x32c 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x32d 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x32e 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x32f 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x330 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x331 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x332 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x333 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x334 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x335 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x336 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x337 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x338 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x339 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x33a 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x33b 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x33c 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x33d 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x33e 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 8 1 Ncon > 0x33f 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 8 1 Ncon > 0x340 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x341 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 16 1 Ncon > 0x342 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x343 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 16 1 Ncon > 0x344 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x345 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x346 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x347 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x348 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x349 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x34a 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 8 1 Ncon > 0x34b 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 8 1 Ncon > 0x34c 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x34d 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 16 1 Ncon > 0x34e 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x34f 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 16 1 Ncon > 0x350 32 tc 0 24 0 r y . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon > 0x351 32 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon > 0x352 32 tc 0 24 0 r . . 8 8 8 0 4 24 0 16 16 16 16 32 1 Ncon > 0x353 32 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 32 1 Ncon > 0x354 32 tc 0 24 0 r y . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon > 0x355 32 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon > 0x356 32 tc 0 24 0 r . . 8 8 8 0 4 24 8 16 16 16 16 32 1 Ncon > 0x357 32 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 32 1 Ncon > >> -jeff >>> >>> >>> >>> >>> David E DeMarle >>> Kitware, Inc. >>> R&D Engineer >>> 21 Corporate Drive >>> Clifton Park, NY 12065-8662 >>> Phone: 518-881-4909 >>> >>> On Wed, Jun 10, 2015 at 2:58 PM, Aashish Chaudhary >>> >> > wrote: >>> >>> No, I don't think so. It would be nice if you can try Burlen >>> suggestion to see if it works for built in datasets / sources. >>> >>> - Aashish >>> >>> On Wed, Jun 10, 2015 at 2:49 PM, Jeff Becker >>> > >>> wrote: >>> >>> On 06/10/2015 11:46 AM, Burlen Loring wrote: >>> >>> Hmm. If Bunyk ray cast doesn't work some thing strange >>> is going on as that is a software(non gpu) algorithm and >>> should always work. >>> >>> Can you get anything to show up using a small test data? >>> For example create a wavelet source and apply a >>> threshold (use default values) to convert to >>> unstructured data. If that works maybe something with >>> your input data, or size of it. >>> >>> >>> It's a 500 by 500 by 500 grid of floats - is that too big? >>> >>> >>> On 06/10/2015 11:27 AM, Jeff Becker wrote: >>> >>> On 06/10/2015 11:06 AM, Burlen Loring wrote: >>> >>> 2 things to try: set the remote render threshold >>> to zero, and if that doesn't get it to show up, >>> change the mapper to Bunyk ray cast. One of >>> those usually works depending on what the cause >>> of the issue is. >>> >>> >>> I have both of those set - no luck. BTW, this is >>> ParaView 4.3.1 on an NVIDIA backend. glxinfo shows: >>> >>> $ glxinfo | head -30 >>> name of display: :0.0 >>> display: :0 screen: 0 >>> direct rendering: Yes >>> server glx vendor string: NVIDIA Corporation >>> server glx version string: 1.4 >>> server glx extensions: >>> GLX_EXT_visual_info, GLX_EXT_visual_rating, >>> GLX_SGIX_fbconfig, >>> GLX_SGIX_pbuffer, GLX_SGI_video_sync, >>> GLX_SGI_swap_control, >>> GLX_EXT_swap_control, GLX_EXT_swap_control_tear, >>> GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, >>> GLX_ARB_create_context, >>> GLX_ARB_create_context_profile, >>> GLX_EXT_create_context_es_profile, >>> GLX_EXT_create_context_es2_profile, >>> GLX_ARB_create_context_robustness, >>> GLX_NV_delay_before_swap, GLX_EXT_stereo_tree, >>> GLX_ARB_multisample, >>> GLX_NV_float_buffer, GLX_ARB_fbconfig_float, >>> GLX_EXT_framebuffer_sRGB, >>> GLX_NV_multisample_coverage >>> client glx vendor string: NVIDIA Corporation >>> client glx version string: 1.4 >>> client glx extensions: >>> GLX_ARB_get_proc_address, GLX_ARB_multisample, >>> GLX_EXT_visual_info, >>> GLX_EXT_visual_rating, GLX_EXT_import_context, >>> GLX_SGI_video_sync, >>> GLX_NV_swap_group, GLX_NV_video_out, >>> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, >>> GLX_SGI_swap_control, GLX_EXT_swap_control, >>> GLX_EXT_swap_control_tear, >>> GLX_EXT_buffer_age, GLX_ARB_create_context, >>> GLX_ARB_create_context_profile, GLX_NV_float_buffer, >>> GLX_ARB_fbconfig_float, >>> GLX_EXT_fbconfig_packed_float, >>> GLX_EXT_texture_from_pixmap, >>> GLX_EXT_framebuffer_sRGB, >>> GLX_NV_present_video, GLX_NV_copy_image, >>> GLX_NV_multisample_coverage, >>> GLX_NV_video_capture, >>> GLX_EXT_create_context_es_profile, >>> GLX_EXT_create_context_es2_profile, >>> GLX_ARB_create_context_robustness, >>> GLX_NV_delay_before_swap, GLX_EXT_stereo_tree >>> >>> >>> On 06/10/2015 11:00 AM, Jeff Becker wrote: >>> >>> Hi. I have an unstructured grid file that >>> opens and displays in Surface Rendering >>> mode. If I switch to Volume Rendering, I >>> don't see any output. Any ideas? >>> >>> Thanks. >>> >>> -jeff >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the >>> ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: >>> http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki >>> at: http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: >>> http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >>> >>> >>> -- >>> /| Aashish Chaudhary >>> | Technical Leader >>> | Kitware Inc. >>> / >>> /| http://www.kitware.com/company/team/chaudhary.html/ >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> >> >> >> _______________________________________________ >> Powered bywww.kitware.com >> >> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >> >> Search the list archives at:http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From houssen at ipgp.fr Fri Jun 12 09:54:20 2015 From: houssen at ipgp.fr (houssen) Date: Fri, 12 Jun 2015 15:54:20 +0200 Subject: [Paraview] =?utf-8?q?How_to_plug_into_paraview_his_own_writer_=3F?= Message-ID: <8370b86533b1d1d9902620adc98b054a@imap.ipgp.fr> I followed 2 tutorials (http://www.itk.org/Wiki/ParaView/Plugin_HowTo#Writing_Plugins, http://www.kitware.com/media/html/WritingAParaViewReaderPlug-in.html) but I feel like I missed some steps : this is not working. I need to "catch" data (I can see in 2D/3D paraview viewer) to write them into a specific file format. I am looking for the minimal (simplest) way to do this : the only writer input is the file name, then I would like to understand how to "get data from" paraview (from inside a vtk object I guess ?), then I just will have to do the easy part which is to write data to a specific format. My understanding is that, first I need a CMakeLists.txt like : ~> more CMakeLists.txt FIND_PACKAGE ( ParaView REQUIRED ) INCLUDE ( ${PARAVIEW_USE_FILE} ) ADD_PARAVIEW_PLUGIN ( myWriter "1.0" SERVER_MANAGER_XML myWriter.xml SERVER_MANAGER_SOURCES myWriter.cpp ) In the same directory, I need a (minimal) myWriter.xml file that looks like : ~> more myWrite.xml My understanding is that somehow the xml subscribes my for a specific callback I am called back on the "save data" button is cliked in the GUI. Still, in this same directory, I have myWriter.cpp and myWriter.hpp : how to implement them ? 1. The myWriter class must define and implement a SetFileName method because of the xml tag in myWriter.xml : right ? wrong ? This is the file name (including file path) one sets in the GUI : right ? wrong ? 2. myWriter is supposed to derive from another class : which one ? where to find it ? 3. How the myWriter implementation will "catch" data in paraview ? Which method to override / re-implement ? When I am called from paraview (triggered by the click on "save data" button), I guess I am called on a specific method "myWriter::cbMethod ( vtkXXX * pDataInParaviewViewer )" What is this method ? Also, at this step, I export PV_PLUGIN_PATH=/mnt/users/houssen/Documents/solve-rel/paraview. When I run paraview and use the "save data" button I get this : Generic Warning: In /.../Programs/ParaView/ParaView-v4.3.1-source/ParaViewCore/ServerManager/Core/vtkSMWriterFactory.cxx, line 135 writers : myWriter has no input property. ... But I have an tag in the xml : what's wrong ? Can somebody help me on this ? Franck Note : I run Ubuntu and paraview-4.3 From vishnu2bharathi at gmail.com Fri Jun 12 10:23:46 2015 From: vishnu2bharathi at gmail.com (Vishnubharathi T) Date: Fri, 12 Jun 2015 16:23:46 +0200 Subject: [Paraview] Filters in paraview Message-ID: Dear Paraviewer's, Learning paraview by following paraview-guide( http://www.paraview.org/paraview-guide/). I understood how to follow and implement a filter. But, I didnt understood the following below. Please could you help me in this regard. I searched many places in internet but couldnt find answers for these nor I could find tutorial videos for this. 1. I have been going through filters in paraview. I counldnt understand the Data arrays namely *points, cells, field data arrays.* 1.2 What is meant by Dataset in paraview(few examples for data set?) 2.Partial arrays- What is meant by this? couldnt get what that meant. (practical example for partial array data set) 3. Mapping Data- How it affects the cell normals time line gap? any example for this? 4. Calculator Filter: When can we use it & whats the function of this filter? Below are the terms I saw in properties tab of Calculator Filter: What if refers to? 1. Scalars & Vectors in Property option 2. Attribute mode: Point data, cell data [Example for above will be helpful in learning, In pdf I see how to use it, but what its actual meaning I couldnt understand] 5.Plot over Line Filter: Requiremnt- we need arrays and attribute type to use this. what is meant by *arrays here*. I know arrays as a parameter holding large values, but can you give me an example here. 6.Extract subset Filter & Append Dataset Filter: for both these, I can implement by following tutorial pdf. What it actually does I couldnt understand. Please help in this. 7.Threshold Filter: For this we selects scalars and specify range. Can you give me some practical example to understand? Datatype used: Point data & cell data( example for these data types) 8.What are seed points? what are Point Cloud & Line source? These I could see in Stream Trace Filter(checked the pdf and dist_out_ref.ex2 file) but couldnt understand what that disk_out_ref.ex2 file actually is? PS: share any material/source for the above points. Previously referred sites: http://www.paraview.org/paraview-guide/ http://www.paraview.org/Wiki/ParaView -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Fri Jun 12 12:02:56 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Fri, 12 Jun 2015 16:02:56 +0000 Subject: [Paraview] Filters in paraview In-Reply-To: References: Message-ID: Also checkout ParaView Tutorial http://www.paraview.org/tutorials/ ParaView Catalyst user guide has a section on VTK datatypes (section 3.3) http://www.paraview.org/files/catalyst/docs/ParaViewCatalystUsersGuide_v2.pdf For a comprehensive study of VTK and visualization check out VTK User's Guide and/or The Visualization Toolkit. These are printed books. Dan On Fri, Jun 12, 2015 at 10:23 AM Vishnubharathi T wrote: > Dear Paraviewer's, > > Learning paraview by following paraview-guide( > http://www.paraview.org/paraview-guide/). I understood how to follow > and implement a filter. But, I didnt understood the following below. > Please could you help me in this regard. I searched many places in internet > but couldnt find answers for these nor I could find tutorial videos for > this. > > > 1. I have been going through filters in paraview. I counldnt understand > the Data arrays namely *points, cells, field data arrays.* > > 1.2 What is meant by Dataset in paraview(few examples for data set?) > > 2.Partial arrays- What is meant by this? couldnt get what that meant. > (practical example for partial array data set) > > 3. Mapping Data- How it affects the cell normals time line gap? any > example for this? > > 4. Calculator Filter: When can we use it & whats the function of this > filter? > Below are the terms I saw in properties tab of Calculator > Filter: What if refers to? > 1. Scalars & Vectors in Property option > 2. Attribute mode: Point data, cell data > > [Example for above will be helpful in learning, In pdf I see how to use > it, but what its actual meaning I couldnt understand] > > 5.Plot over Line Filter: Requiremnt- we need arrays and attribute type to > use this. what is meant by *arrays here*. I know arrays as a parameter > holding large values, but can you give me an example here. > > 6.Extract subset Filter & Append Dataset Filter: for both these, I can > implement by following tutorial pdf. What it actually does I couldnt > understand. Please help in this. > > 7.Threshold Filter: For this we selects scalars and specify range. Can > you give me some practical example to understand? > Datatype used: Point data & cell data( example for these data types) > > 8.What are seed points? what are Point Cloud & Line source? These I > could see in Stream Trace Filter(checked the pdf and dist_out_ref.ex2 file) > but couldnt understand what that disk_out_ref.ex2 file actually is? > > PS: share any material/source for the above points. > > Previously referred sites: > > http://www.paraview.org/paraview-guide/ > > http://www.paraview.org/Wiki/ParaView > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffrey.c.becker at nasa.gov Fri Jun 12 18:27:40 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Fri, 12 Jun 2015 15:27:40 -0700 Subject: [Paraview] Selecting volume rendering causes output to vanish In-Reply-To: <5579E9F5.4050206@gmail.com> References: <55787B45.4000606@nasa.gov> <55787C89.5080409@gmail.com> <55788182.4040206@nasa.gov> <5578861C.4060407@gmail.com> <557886A6.5080606@nasa.gov> <5578A8E4.90703@nasa.gov> <5579CAE0.9030403@nasa.gov> <5579E9F5.4050206@gmail.com> Message-ID: <557B5CDC.8090804@nasa.gov> On 06/11/2015 01:05 PM, Burlen Loring wrote: > you ran out of memory. > > You may need more than 1 node, and a parallel file format. > > You mentioned that you had a grid of 500 x 500 points. You could save > a lot of memory by using vtkImageData, vtkRectilinearMesh or > vtkStructuredGrid if your data is amenable to one of those. I switched to using vtkStructuredGrid. However, after reading the file in ParaView, and attempting to volume render I get the seg. fault in pvserver below. I am creating my grid in python as follows (steinmesh contains the grid coordinates): import os import numpy as np import steinmesh as mesh import itertools import vtk from vtk.util import numpy_support in_fname='/nobackupp9/pmoran/stein/mhd48-1/dat/mhd48h1new_670.8.dat' out_fname='/nobackup/jcbecker/steinBmag.vts' f = open(in_fname,"rb") bx = 6 npoints = mesh.MX*mesh.MY*mesh.MZ f.seek(bx*npoints*np.dtype('f4').itemsize,os.SEEK_SET) steinbmag = np.square(np.fromfile(f,dtype=np.dtype('f4'),count=npoints)) steinbmag += np.square(np.fromfile(f,dtype=np.dtype('f4'),count=npoints)) steinbmag += np.square(np.fromfile(f,dtype=np.dtype('f4'),count=npoints)) steinbmag = np.sqrt(steinbmag) f.close() grid = [x for x in itertools.product(mesh.xcoords, mesh.ycoords, mesh.zcoords)] pcoords = vtk.vtkDoubleArray() pcoords.SetNumberOfComponents(3) pcoords.SetNumberOfTuples(npoints) for i in range(npoints): pcoords.SetTuple3(*((i,) + grid[i])) pts = vtk.vtkPoints() pts.SetData(pcoords) sgrid = vtk.vtkStructuredGrid() sgrid.SetDimensions(mesh.MX,mesh.MY,mesh.MZ) sgrid.SetPoints(pts) bmagV = numpy_support.numpy_to_vtk(steinbmag,deep=True) bmagV.SetName('B field magnitude') sgrid.GetPointData().SetScalars(bmagV) writer = vtk.vtkXMLStructuredGridWriter() writer.SetFileName(out_fname) writer.SetInputData(sgrid) writer.SetDataModeToBinary() writer.Write() Can anyone see what's wrong? Thanks. -jeff Program received signal SIGSEGV, Segmentation fault. 0x00002aaaafb1c327 in vtkDataArrayTemplate::GetValue(long long) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkCommonCore-pv4.3.so.1 (gdb) bt #0 0x00002aaaafb1c327 in vtkDataArrayTemplate::GetValue(long long) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkCommonCore-pv4.3.so.1 #1 0x00002aaaae991d71 in vtkCellArray::GetMaxCellSize() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkCommonDataModel-pv4.3.so.1 #2 0x00002aaaac44dde9 in vtkCellCenterDepthSort::ComputeCellCenters() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #3 0x00002aaaac44e593 in vtkCellCenterDepthSort::InitTraversal() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #4 0x00002aaab82fc2dd in vtkOpenGLProjectedTetrahedraMapper::ProjectTetrahedra(vtkRenderer*, vtkVolume*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingVolumeOpenGL-pv4.3.so.1 #5 0x00002aaab82f7997 in vtkOpenGLProjectedTetrahedraMapper::Render(vtkRenderer*, vtkVolume*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingVolumeOpenGL-pv4.3.so.1 #6 0x00002aaaac4d0118 in vtkVolume::RenderVolumetricGeometry(vtkViewport*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #7 0x00002aaaac4e1198 in vtkLODProp3D::RenderVolumetricGeometry(vtkViewport*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #8 0x00002aaab4f3a4eb in vtkPVLODVolume::RenderVolumetricGeometry(vtkViewport*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 #9 0x00002aaaac4b94ee in vtkRenderer::UpdateGeometry() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #10 0x00002aaab4f2d751 in vtkPVDefaultPass::Render(vtkRenderState const*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 #11 0x00002aaaba0d135b in vtkCameraPass::Render(vtkRenderState const*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #12 0x00002aaaba1436c0 in vtkOpenGLRenderer::DeviceRender() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #13 0x00002aaaac4bb18d in vtkRenderer::Render() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #14 0x00002aaaac4b8429 in vtkRendererCollection::Render() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #15 0x00002aaaac4c2202 in vtkRenderWindow::DoStereoRender() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #16 0x00002aaaac4c2119 in vtkRenderWindow::DoFDRender() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #17 0x00002aaaac4c31a3 in vtkRenderWindow::DoAARender() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #18 0x00002aaaac4bf7fe in vtkRenderWindow::Render() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #19 0x00002aaaba1d17ae in vtkXOpenGLRenderWindow::Render() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #20 0x00002aaab3b9897f in vtkPVRenderView::Render(bool, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreRendering-pv4.3.so.1 #21 0x00002aaab3b9369c in vtkPVRenderView::StillRender() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreRendering-pv4.3.so.1 #22 0x00002aaaab493665 in vtkPVRenderViewCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerManagerApplication-pv4.3.so.1 #23 0x00002aaaadb005e0 in vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so.1 #24 0x00002aaaadb05393 in vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so.1 #25 0x00002aaaadb03832 in vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so.1 #26 0x00002aaaadb03ced in vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so.1 #27 0x00002aaaabd8dcec in vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 #28 0x00002aaaabd8d958 in vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 #29 0x00002aaaabd8c203 in vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 #30 0x00002aaaabd98591 in vtkPVSessionServer::OnClientServerMessageRMI(void*, int) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 #31 0x00002aaaae2cc463 in vtkMultiProcessController::ProcessRMI(int, void*, int, int) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkParallelCore-pv4.3.so.1 #32 0x00002aaaae2cc7df in vtkMultiProcessController::ProcessRMIs(int, int) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkParallelCore-pv4.3.so.1 #33 0x00002aaaabfa5ec6 in vtkTCPNetworkAccessManager::ProcessEventsInternal(unsigned long, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreCore-pv4.3.so.1 #34 0x00000000004019f6 in RealMain(int, char**, vtkProcessModule::ProcessTypes) () #35 0x0000000000401a3e in main () -------------- next part -------------- An HTML attachment was scrubbed... URL: From pa at letnes.com Sat Jun 13 04:46:00 2015 From: pa at letnes.com (Paul Anton Letnes) Date: Sat, 13 Jun 2015 10:46:00 +0200 Subject: [Paraview] paraview for a "new" application In-Reply-To: References: <280CD6CF-2E16-4390-8670-89A006311356@letnes.com> <55755FF6.9060901@gmail.com> Message-ID: Stefano (and others), I?ve seen some of your efforts posted on github. I have to say I commend your efforts; the open source Fortran community is too small. I will investigate several of your libraries recently, especially after you modified the licensing terms to be very liberal. Even though VTK is probably the ?right? format to use, I am reluctant to introduce yet another file format into the fray (our code already has too many IMHO). That being said, it?s a relatively standard format that should stand the test of time. Your library appears to solve the issue of writing the data to disk, at least. Best regards, Paul > On 8. jun. 2015, at 11.49, Stefano Zaghi wrote: > > Hi all, > > another possibility is to write your Fortran data directly into VTK files format. > > I develop a KISS library in pure Fortran for IO of Fortran data into VTK standard: see https://github.com/szaghi/Lib_VTK_IO > > The exporters are almost complete. The importers are under developing by a power collaborator https://github.com/victorsndvg/Lib_VTK_IO this work will be merged very soon into the main branch. > > Summarizing, Lib_VTK_IO is > > + Lib_VTK_IO is a pure Fortran library to write and read data conforming the VTK standard; > + Lib_VTK_IO is Fortran 2003+ standard compliant; > + Lib_VTK_IO supports parallel architectures by means OpenMP and MPI paradigms; > + Lib_VTK_IO supports ascii, binary and base64 file formats; > + Lib_VTK_IO is a Free, Open Source Project. > > My best regards > > Stefano Zaghi Ph.D. Aerospace Engineer > > Research Scientist, Dept. of Computational Hydrodynamics at CNR-INSEAN > p: +39 0650299260 | m: +39 3497730036 | e: stefano.zaghi at gmail.com > > Codes Showcase > OFF Open source Finite volumes Fluid dynamics code > Lib_VTK_IO Fortran library to write and read data conforming the VTK standard > FLAP Fortran command Line Arguments Parser for poor men > BeFoR64 Base64 encoding/decoding library for FoRtran poor men > FiNeR Fortran INI ParseR and generator for FoRtran poor men > IR_Precision Fortran (standard 2003) module to develop portable codes > FoBis.py Fortran Building System for poor men > PreForM.py Preprocessor for Fortran poor men > MaTiSSe.py Markdown To Impressive Scientific Slides > > > On Mon, Jun 8, 2015 at 11:27 AM, Armin Wehrfritz wrote: > Hi Paul, > > as you and Dan already stated, the HDF5 format is a very good choice to write out large datasets. > > I usually write the HDF5 files directly from my simulation codes and generate a XDMF file afterwards. > The actual XDMF file contains just the meta data in XML format [1] and this can be tailored to your application/dataset (I use python with h5py and xml.etree to do this). > Hence, my simulation codes (written in C++) only depend on the HDF5 libraries. > > Eventually, this will enable you to store your data in a robust, flexible and portable file format. > > For more complex setups I would also consider using the VTK libraries to handle the data IO as Dan suggested. > > -Armin > > [1] http://www.xdmf.org/index.php/XDMF_Model_and_Format > > > > > On 06/07/2015 10:40 PM, Dan Lipsa wrote: > You are right, ParaView does not read hdf5 directly but rather hdf5 > based formats (hdf5 + additional info): both netcdf and xdmf have readers. > You can get a list of all readers supported by your ParaView > installation using Help in ParaView. Additional readers can be enabled with > compile time options. > > You can write Xdmf data using vtkXdmfWriter or vtkXdm3Writer (you'll > have to link with the VTK library). These writers have tests which is a > good way to see an example of how to use the class. You can also take a > look at the VTK XML based formats: vtkXMLPolyDataWriter, > vtkXMLImageDataWriter, vtkXMLUnstructuredGridWriter/Reader. Probably you > could write data with a library that comes with that format and then > read it with ParaView. > > Do you need parallel writing/reading? > > Dan > > > > > On Sun, Jun 7, 2015 at 4:26 AM Paul Anton Letnes > wrote: > > Hi Dan! > > I?m familiar with the HDF5 library and documentation, but thanks > anyway for the link. > > I don?t see how I can have ParaView read and understand HDF5 files. > That is, there are several readers (e.g. H5Nimrod) that use HDF5 as > the underlying format, but I don?t see how to get paraview to > understand which arrays are coordinates (nodes?), which are results, > etc. for my application. > > Perhaps I should stress again that I have limited experience with > ParaView, and since the supported file formats and possibilities > seem endless, I have trouble getting an overview of sensible choices. > > My preference for hdf5 is partly due to other software in my > organization supporting this format, and my own familiarity with it. > > Paul > > > On 7. jun. 2015, at 04.07, Dan Lipsa > wrote: > > > > Hi Paul, > > Indeed #2 makes sense, especially if you want to change the > in-house format. To write the file (from the simulation) it seems to > me you should checkout > > > > https://www.hdfgroup.org/HDF5/doc/fortran/index.html > > > > I don't see why ParaView would be used in that process. Am I > missing something? > > Dan > > > > > > > > On Sat, Jun 6, 2015 at 8:04 AM Paul Anton Letnes > wrote: > > Hi, fellow paraviewers! > > > > I?ve spent some time playing with tutorials and user manuals, and > so far I?m impressed with what paraview can do. > > > > I am working on a specialized structural engineering program > that, mainly, performs simulations of pipes with circular cross > sections. Each pipe is split into nodes and 1D elements, and results > are reported at points (or, less commonly, elements) along the pipe. > > > > Some results are reported once per cross section; e.g, the > tension in the pipe has a single value for the entire cross section. > Other results, e.g. plastic strain, is reported for a number of > points along the circumference of the pipe (say, 5-50 points), for > each of the cross sections. The results can be either ?snapshots? or > time series. > > > > After what I?ve seen from the paraview documentation, possible > approaches include: > > 1. Create a paraview plugin to read our current in-house file format. > > 2. Directly write output files in an already supported format. > > 3. Write pvpython scripts that perform the conversion on the fly. > > > > Approach 1 is probably a lot of work and the file format is not > of interest to anyone else (optimally, I?d like to replace it), so > this seems less attractive. Approach 3 is probably less > user-friendly for our users. > > > > The second approach seems sensible, but the paraview > documentation does not give many examples of how to do this. > Optimally, I?d like to write a hdf5-based format (xdmf? netcdf? raw > hdf5?) directly from Fortran, but I haven?t found documentation on > how to do this. Using hdf5 seems attractive as it?s so widely > supported by e.g. matlab, python, and other postprocessing tools > used in the industry. Getting a single results database would > simplify a lot of workflows! > > > > What would you guys do? > > > > Cheers > > Paul > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From houssen at ipgp.fr Sat Jun 13 10:54:28 2015 From: houssen at ipgp.fr (houssen) Date: Sat, 13 Jun 2015 16:54:28 +0200 Subject: [Paraview] =?utf-8?q?Fwd=3A_How_to_plug_into_paraview_his_own_wri?= =?utf-8?q?ter_=3F?= Message-ID: <86347d91c723cd90b081325c08b678ec@imap.ipgp.fr> I followed 2 writer examples (cpp, hpp) : Xdmf writer and OpenFOAM writer. Complexity is high, still difficult to extract basic needs out of them. Question 1 : how to write myWriter.xml ? 1.1. seems I must set in myWriter.xml. Does this means I will also have to implement myWriter::SetInputConnection ? 1.2. seems I must set in myWriter.xml. Does this means I will also have to implement myWriter::SetFileName ? I am correct ? Question 2 : how to implement a vtk object ? From here http://www.vtk.org/Wiki/VTK/Examples/Developers/vtkObject, it seems that 2.1. in myWriter.cpp, I need to have : #include "vtkObjectFactory.h" // vtkStandardNewMacro vtkStandardNewMacro ( myWriter ); // use vtkStandardNewMacro : 1 only allowed constructor, omit the copy constructor and operator= + suppress copy constructor and operator= 2.2 in myWriter.hpp, I need to derive from a vtkObject this way (like XdmfWriter.cpp does) : class myWriter : public vtkDataObjectAlgorithm { public: static myWriter * New (); // Needed to be plugged into paraview vtkTypeMacro ( myWriter, vtkDataObjectAlgorithm ); // Needed to be plugged into paraview + suppress copy constructor and operator= Am I correct ? Question 3 : in myWriter.cpp, on which method I am supposed to be called back (to get focus back) when I click the "save data" button ? Here, how can I get data to be saved (data that I can see in paraview viewer before to click the save button - I guess this data will be a vtk*). Finally, myWriter.xml seems OK. myWriter.*pp compile OK. Paraview finds myWriter.xml at run time (exporting PV_PLUGIN_PATH) and loads libmywriter.so without problem. I see the writer in the "save data" GUI (drop down list with different save formats). I save with myWriter, I get a (basic) GUI with file name only (no extra parameter) : I crash when I click "OK, save" with this error message : ERROR: In /.../ParaView-v4.3.1-source/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, line 307 vtkSIWriterProxy (0x30143d0): Failed to create myWriter. Aborting for debugging purposes. vtkSIWriterProxy does this at line 303 : vtkObjectBase* obj = this->Interpreter->NewInstance(className); but obj is NULL. I get obj is NULL because I missed something in myWriter implementation : what did I miss ? Can somebody help ? Or even get me some clue ? FH -------- Message original -------- Objet: How to plug into paraview his own writer ? Date: 2015-06-12 15:54 De: houssen ?: I followed 2 tutorials (http://www.itk.org/Wiki/ParaView/Plugin_HowTo#Writing_Plugins, http://www.kitware.com/media/html/WritingAParaViewReaderPlug-in.html) but I feel like I missed some steps : this is not working. I need to "catch" data (I can see in 2D/3D paraview viewer) to write them into a specific file format. I am looking for the minimal (simplest) way to do this : the only writer input is the file name, then I would like to understand how to "get data from" paraview (from inside a vtk object I guess ?), then I just will have to do the easy part which is to write data to a specific format. My understanding is that, first I need a CMakeLists.txt like : ~> more CMakeLists.txt FIND_PACKAGE ( ParaView REQUIRED ) INCLUDE ( ${PARAVIEW_USE_FILE} ) ADD_PARAVIEW_PLUGIN ( myWriter "1.0" SERVER_MANAGER_XML myWriter.xml SERVER_MANAGER_SOURCES myWriter.cpp ) In the same directory, I need a (minimal) myWriter.xml file that looks like : ~> more myWrite.xml My understanding is that somehow the xml subscribes my for a specific callback I am called back on the "save data" button is cliked in the GUI. Still, in this same directory, I have myWriter.cpp and myWriter.hpp : how to implement them ? 1. The myWriter class must define and implement a SetFileName method because of the xml tag in myWriter.xml : right ? wrong ? This is the file name (including file path) one sets in the GUI : right ? wrong ? 2. myWriter is supposed to derive from another class : which one ? where to find it ? 3. How the myWriter implementation will "catch" data in paraview ? Which method to override / re-implement ? When I am called from paraview (triggered by the click on "save data" button), I guess I am called on a specific method "myWriter::cbMethod ( vtkXXX * pDataInParaviewViewer )" What is this method ? Also, at this step, I export PV_PLUGIN_PATH=/mnt/users/houssen/Documents/solve-rel/paraview. When I run paraview and use the "save data" button I get this : Generic Warning: In /.../Programs/ParaView/ParaView-v4.3.1-source/ParaViewCore/ServerManager/Core/vtkSMWriterFactory.cxx, line 135 writers : myWriter has no input property. ... But I have an tag in the xml : what's wrong ? Can somebody help me on this ? Franck Note : I run Ubuntu and paraview-4.3 From burlen.loring at gmail.com Sat Jun 13 23:12:08 2015 From: burlen.loring at gmail.com (Burlen Loring) Date: Sat, 13 Jun 2015 20:12:08 -0700 Subject: [Paraview] Selecting volume rendering causes output to vanish In-Reply-To: <557B5CDC.8090804@nasa.gov> References: <55787B45.4000606@nasa.gov> <55787C89.5080409@gmail.com> <55788182.4040206@nasa.gov> <5578861C.4060407@gmail.com> <557886A6.5080606@nasa.gov> <5578A8E4.90703@nasa.gov> <5579CAE0.9030403@nasa.gov> <5579E9F5.4050206@gmail.com> <557B5CDC.8090804@nasa.gov> Message-ID: <557CF108.2080402@gmail.com> It's hard for me to say, I've never seen the stein mesh package, and googling doesn't turn anything up. Perhaps you could share the dataset itself? I'm sure someone here could quickly reproduce the issue and perhaps suggest a fix. On 6/12/2015 3:27 PM, Jeff Becker wrote: > On 06/11/2015 01:05 PM, Burlen Loring wrote: >> you ran out of memory. >> >> You may need more than 1 node, and a parallel file format. >> >> You mentioned that you had a grid of 500 x 500 points. You could save >> a lot of memory by using vtkImageData, vtkRectilinearMesh or >> vtkStructuredGrid if your data is amenable to one of those. > > I switched to using vtkStructuredGrid. However, after reading the file > in ParaView, and attempting to volume render I get the seg. fault in > pvserver below. I am creating my grid in python as follows (steinmesh > contains the grid coordinates): > > > import os > import numpy as np > import steinmesh as mesh > import itertools > import vtk > from vtk.util import numpy_support > > in_fname='/nobackupp9/pmoran/stein/mhd48-1/dat/mhd48h1new_670.8.dat' > out_fname='/nobackup/jcbecker/steinBmag.vts' > f = open(in_fname,"rb") > bx = 6 > npoints = mesh.MX*mesh.MY*mesh.MZ > f.seek(bx*npoints*np.dtype('f4').itemsize,os.SEEK_SET) > > steinbmag = np.square(np.fromfile(f,dtype=np.dtype('f4'),count=npoints)) > steinbmag += np.square(np.fromfile(f,dtype=np.dtype('f4'),count=npoints)) > steinbmag += np.square(np.fromfile(f,dtype=np.dtype('f4'),count=npoints)) > steinbmag = np.sqrt(steinbmag) > > f.close() > > grid = [x for x in itertools.product(mesh.xcoords, mesh.ycoords, > mesh.zcoords)] > > pcoords = vtk.vtkDoubleArray() > pcoords.SetNumberOfComponents(3) > pcoords.SetNumberOfTuples(npoints) > for i in range(npoints): > pcoords.SetTuple3(*((i,) + grid[i])) > pts = vtk.vtkPoints() > pts.SetData(pcoords) > > sgrid = vtk.vtkStructuredGrid() > sgrid.SetDimensions(mesh.MX,mesh.MY,mesh.MZ) > sgrid.SetPoints(pts) > > bmagV = numpy_support.numpy_to_vtk(steinbmag,deep=True) > bmagV.SetName('B field magnitude') > sgrid.GetPointData().SetScalars(bmagV) > > writer = vtk.vtkXMLStructuredGridWriter() > writer.SetFileName(out_fname) > writer.SetInputData(sgrid) > writer.SetDataModeToBinary() > writer.Write() > > Can anyone see what's wrong? Thanks. > > -jeff > > > Program received signal SIGSEGV, Segmentation fault. > 0x00002aaaafb1c327 in vtkDataArrayTemplate::GetValue(long > long) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkCommonCore-pv4.3.so.1 > (gdb) bt > #0 0x00002aaaafb1c327 in vtkDataArrayTemplate long>::GetValue(long long) > () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkCommonCore-pv4.3.so.1 > #1 0x00002aaaae991d71 in vtkCellArray::GetMaxCellSize() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkCommonDataModel-pv4.3.so.1 > #2 0x00002aaaac44dde9 in vtkCellCenterDepthSort::ComputeCellCenters() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #3 0x00002aaaac44e593 in vtkCellCenterDepthSort::InitTraversal() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #4 0x00002aaab82fc2dd in > vtkOpenGLProjectedTetrahedraMapper::ProjectTetrahedra(vtkRenderer*, > vtkVolume*) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingVolumeOpenGL-pv4.3.so.1 > #5 0x00002aaab82f7997 in > vtkOpenGLProjectedTetrahedraMapper::Render(vtkRenderer*, vtkVolume*) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingVolumeOpenGL-pv4.3.so.1 > #6 0x00002aaaac4d0118 in > vtkVolume::RenderVolumetricGeometry(vtkViewport*) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #7 0x00002aaaac4e1198 in > vtkLODProp3D::RenderVolumetricGeometry(vtkViewport*) > () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #8 0x00002aaab4f3a4eb in > vtkPVLODVolume::RenderVolumetricGeometry(vtkViewport*) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 > #9 0x00002aaaac4b94ee in vtkRenderer::UpdateGeometry() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #10 0x00002aaab4f2d751 in vtkPVDefaultPass::Render(vtkRenderState > const*) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 > #11 0x00002aaaba0d135b in vtkCameraPass::Render(vtkRenderState const*) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #12 0x00002aaaba1436c0 in vtkOpenGLRenderer::DeviceRender() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #13 0x00002aaaac4bb18d in vtkRenderer::Render() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #14 0x00002aaaac4b8429 in vtkRendererCollection::Render() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #15 0x00002aaaac4c2202 in vtkRenderWindow::DoStereoRender() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #16 0x00002aaaac4c2119 in vtkRenderWindow::DoFDRender() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #17 0x00002aaaac4c31a3 in vtkRenderWindow::DoAARender() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #18 0x00002aaaac4bf7fe in vtkRenderWindow::Render() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 > #19 0x00002aaaba1d17ae in vtkXOpenGLRenderWindow::Render() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 > #20 0x00002aaab3b9897f in vtkPVRenderView::Render(bool, bool) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreRendering-pv4.3.so.1 > #21 0x00002aaab3b9369c in vtkPVRenderView::StillRender() () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreRendering-pv4.3.so.1 > #22 0x00002aaaab493665 in > vtkPVRenderViewCommand(vtkClientServerInterpreter*, vtkObjectBase*, > char const*, vtkClientServerStream const&, vtkClientServerStream&, > void*) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerManagerApplication-pv4.3.so.1 > #23 0x00002aaaadb005e0 in > vtkClientServerInterpreter::CallCommandFunction(char const*, > vtkObjectBase*, char const*, vtkClientServerStream const&, > vtkClientServerStream&) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so.1 > #24 0x00002aaaadb05393 in > vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream > const&, int) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so.1 > #25 0x00002aaaadb03832 in > vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream > const&, int) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so.1 > #26 0x00002aaaadb03ced in > vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so.1 > #27 0x00002aaaabd8dcec in > vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, > bool) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 > #28 0x00002aaaabd8d958 in vtkPVSessionCore::ExecuteStream(unsigned > int, vtkClientServerStream const&, bool) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 > #29 0x00002aaaabd8c203 in vtkPVSessionBase::ExecuteStream(unsigned > int, vtkClientServerStream const&, bool) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 > #30 0x00002aaaabd98591 in > vtkPVSessionServer::OnClientServerMessageRMI(void*, int) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 > #31 0x00002aaaae2cc463 in vtkMultiProcessController::ProcessRMI(int, > void*, int, int) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkParallelCore-pv4.3.so.1 > #32 0x00002aaaae2cc7df in vtkMultiProcessController::ProcessRMIs(int, > int) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkParallelCore-pv4.3.so.1 > #33 0x00002aaaabfa5ec6 in > vtkTCPNetworkAccessManager::ProcessEventsInternal(unsigned long, bool) () > from > /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreCore-pv4.3.so.1 > #34 0x00000000004019f6 in RealMain(int, char**, > vtkProcessModule::ProcessTypes) > () > #35 0x0000000000401a3e in main () > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jtarn002 at ucr.edu Sun Jun 14 19:13:07 2015 From: jtarn002 at ucr.edu (Jennifer Mary Tarnowski) Date: Sun, 14 Jun 2015 16:13:07 -0700 Subject: [Paraview] Visualization error Message-ID: Hi, I'm receiving the following error when I try to visualize data that is saved in 10 time steps. ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/IO/XML/vtkXMLDataReader.cxx, line 434 vtkXMLUnstructuredGridReader (0x7faff494d5c0): Cannot read point data array "Displacement" from PointData in piece 0. The data array in the element may be too short. After about the 4th time step, I stop receiving the error and things like displacement, stress, etc. display properly. Is this a bug in ParaView or is there something I need to change in my settings somewhere to allow visualization of the first 3 time steps? Thanks, Jennifer -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffrey.c.becker at nasa.gov Mon Jun 15 11:31:58 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Mon, 15 Jun 2015 08:31:58 -0700 Subject: [Paraview] Selecting volume rendering causes output to vanish In-Reply-To: <557CF108.2080402@gmail.com> References: <55787B45.4000606@nasa.gov> <55787C89.5080409@gmail.com> <55788182.4040206@nasa.gov> <5578861C.4060407@gmail.com> <557886A6.5080606@nasa.gov> <5578A8E4.90703@nasa.gov> <5579CAE0.9030403@nasa.gov> <5579E9F5.4050206@gmail.com> <557B5CDC.8090804@nasa.gov> <557CF108.2080402@gmail.com> Message-ID: <557EEFEE.9050303@nasa.gov> On 06/13/2015 08:12 PM, Burlen Loring wrote: > It's hard for me to say, I've never seen the stein mesh package, and > googling doesn't turn anything up. Perhaps you could share the dataset > itself? I'm sure someone here could quickly reproduce the issue and > perhaps suggest a fix. I'll ask if I can share the data set, but it's half a terabyte in size! I only read it in a small part of it for this test, so I suppose I could splice that out. The stein mesh package is some python that I wrote to import the mesh coordinates. It's simply some data specified as follows: MX=504 MY=500 MZ=504 xcoords = [ 0.0000000000000000e+00, 9.5238097012042999e-02, 1.9047619402408600e-01, #... list of x coordinates ] ycoords = [ -5.5000001192092896e-01, -5.3477758169174194e-01, -5.1964950561523438e-01, #... list of y coordinates ] zcoords = [ 0.0000000000000000e+00, 9.5238097012042999e-02, 1.9047619402408600e-01, #... list of z coordinates ] Hopefully, that is enough to give you the information you need. Thanks. -jeff > > On 6/12/2015 3:27 PM, Jeff Becker wrote: >> On 06/11/2015 01:05 PM, Burlen Loring wrote: >>> you ran out of memory. >>> >>> You may need more than 1 node, and a parallel file format. >>> >>> You mentioned that you had a grid of 500 x 500 points. You could >>> save a lot of memory by using vtkImageData, vtkRectilinearMesh or >>> vtkStructuredGrid if your data is amenable to one of those. >> >> I switched to using vtkStructuredGrid. However, after reading the >> file in ParaView, and attempting to volume render I get the seg. >> fault in pvserver below. I am creating my grid in python as follows >> (steinmesh contains the grid coordinates): >> >> >> import os >> import numpy as np >> import steinmesh as mesh >> import itertools >> import vtk >> from vtk.util import numpy_support >> >> in_fname='/nobackupp9/pmoran/stein/mhd48-1/dat/mhd48h1new_670.8.dat' >> out_fname='/nobackup/jcbecker/steinBmag.vts' >> f = open(in_fname,"rb") >> bx = 6 >> npoints = mesh.MX*mesh.MY*mesh.MZ >> f.seek(bx*npoints*np.dtype('f4').itemsize,os.SEEK_SET) >> >> steinbmag = np.square(np.fromfile(f,dtype=np.dtype('f4'),count=npoints)) >> steinbmag += np.square(np.fromfile(f,dtype=np.dtype('f4'),count=npoints)) >> steinbmag += np.square(np.fromfile(f,dtype=np.dtype('f4'),count=npoints)) >> steinbmag = np.sqrt(steinbmag) >> >> f.close() >> >> grid = [x for x in itertools.product(mesh.xcoords, mesh.ycoords, >> mesh.zcoords)] >> >> pcoords = vtk.vtkDoubleArray() >> pcoords.SetNumberOfComponents(3) >> pcoords.SetNumberOfTuples(npoints) >> for i in range(npoints): >> pcoords.SetTuple3(*((i,) + grid[i])) >> pts = vtk.vtkPoints() >> pts.SetData(pcoords) >> >> sgrid = vtk.vtkStructuredGrid() >> sgrid.SetDimensions(mesh.MX,mesh.MY,mesh.MZ) >> sgrid.SetPoints(pts) >> >> bmagV = numpy_support.numpy_to_vtk(steinbmag,deep=True) >> bmagV.SetName('B field magnitude') >> sgrid.GetPointData().SetScalars(bmagV) >> >> writer = vtk.vtkXMLStructuredGridWriter() >> writer.SetFileName(out_fname) >> writer.SetInputData(sgrid) >> writer.SetDataModeToBinary() >> writer.Write() >> >> Can anyone see what's wrong? Thanks. >> >> -jeff >> >> >> Program received signal SIGSEGV, Segmentation fault. >> 0x00002aaaafb1c327 in vtkDataArrayTemplate::GetValue(long >> long) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkCommonCore-pv4.3.so.1 >> (gdb) bt >> #0 0x00002aaaafb1c327 in vtkDataArrayTemplate> long>::GetValue(long long) >> () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkCommonCore-pv4.3.so.1 >> #1 0x00002aaaae991d71 in vtkCellArray::GetMaxCellSize() () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkCommonDataModel-pv4.3.so.1 >> #2 0x00002aaaac44dde9 in vtkCellCenterDepthSort::ComputeCellCenters() () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 >> #3 0x00002aaaac44e593 in vtkCellCenterDepthSort::InitTraversal() () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 >> #4 0x00002aaab82fc2dd in >> vtkOpenGLProjectedTetrahedraMapper::ProjectTetrahedra(vtkRenderer*, >> vtkVolume*) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingVolumeOpenGL-pv4.3.so.1 >> #5 0x00002aaab82f7997 in >> vtkOpenGLProjectedTetrahedraMapper::Render(vtkRenderer*, vtkVolume*) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingVolumeOpenGL-pv4.3.so.1 >> #6 0x00002aaaac4d0118 in >> vtkVolume::RenderVolumetricGeometry(vtkViewport*) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 >> #7 0x00002aaaac4e1198 in >> vtkLODProp3D::RenderVolumetricGeometry(vtkViewport*) >> () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 >> #8 0x00002aaab4f3a4eb in >> vtkPVLODVolume::RenderVolumetricGeometry(vtkViewport*) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 >> #9 0x00002aaaac4b94ee in vtkRenderer::UpdateGeometry() () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 >> #10 0x00002aaab4f2d751 in vtkPVDefaultPass::Render(vtkRenderState >> const*) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 >> #11 0x00002aaaba0d135b in vtkCameraPass::Render(vtkRenderState const*) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 >> #12 0x00002aaaba1436c0 in vtkOpenGLRenderer::DeviceRender() () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 >> #13 0x00002aaaac4bb18d in vtkRenderer::Render() () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 >> #14 0x00002aaaac4b8429 in vtkRendererCollection::Render() () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 >> #15 0x00002aaaac4c2202 in vtkRenderWindow::DoStereoRender() () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 >> #16 0x00002aaaac4c2119 in vtkRenderWindow::DoFDRender() () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 >> #17 0x00002aaaac4c31a3 in vtkRenderWindow::DoAARender() () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 >> #18 0x00002aaaac4bf7fe in vtkRenderWindow::Render() () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 >> #19 0x00002aaaba1d17ae in vtkXOpenGLRenderWindow::Render() () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 >> #20 0x00002aaab3b9897f in vtkPVRenderView::Render(bool, bool) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreRendering-pv4.3.so.1 >> #21 0x00002aaab3b9369c in vtkPVRenderView::StillRender() () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreRendering-pv4.3.so.1 >> #22 0x00002aaaab493665 in >> vtkPVRenderViewCommand(vtkClientServerInterpreter*, vtkObjectBase*, >> char const*, vtkClientServerStream const&, vtkClientServerStream&, >> void*) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerManagerApplication-pv4.3.so.1 >> #23 0x00002aaaadb005e0 in >> vtkClientServerInterpreter::CallCommandFunction(char const*, >> vtkObjectBase*, char const*, vtkClientServerStream const&, >> vtkClientServerStream&) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so.1 >> #24 0x00002aaaadb05393 in >> vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, >> int) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so.1 >> #25 0x00002aaaadb03832 in >> vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream >> const&, int) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so.1 >> #26 0x00002aaaadb03ced in >> vtkClientServerInterpreter::ProcessStream(vtkClientServerStream >> const&) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkClientServer-pv4.3.so.1 >> #27 0x00002aaaabd8dcec in >> vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, >> bool) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 >> #28 0x00002aaaabd8d958 in vtkPVSessionCore::ExecuteStream(unsigned >> int, vtkClientServerStream const&, bool) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 >> #29 0x00002aaaabd8c203 in vtkPVSessionBase::ExecuteStream(unsigned >> int, vtkClientServerStream const&, bool) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 >> #30 0x00002aaaabd98591 in >> vtkPVSessionServer::OnClientServerMessageRMI(void*, int) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVServerImplementationCore-pv4.3.so.1 >> #31 0x00002aaaae2cc463 in vtkMultiProcessController::ProcessRMI(int, >> void*, int, int) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkParallelCore-pv4.3.so.1 >> #32 0x00002aaaae2cc7df in vtkMultiProcessController::ProcessRMIs(int, >> int) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkParallelCore-pv4.3.so.1 >> #33 0x00002aaaabfa5ec6 in >> vtkTCPNetworkAccessManager::ProcessEventsInternal(unsigned long, bool) () >> from >> /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVClientServerCoreCore-pv4.3.so.1 >> #34 0x00000000004019f6 in RealMain(int, char**, >> vtkProcessModule::ProcessTypes) >> () >> #35 0x0000000000401a3e in main () >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Mon Jun 15 14:48:52 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Mon, 15 Jun 2015 18:48:52 +0000 Subject: [Paraview] Visualization error In-Reply-To: References: Message-ID: Jennifer, It is quite possible that the files for time steps 0-2 specify a certain number of elements in the data array but the data array itself has fewer elements. You can see this by opening the file with a text editor. Can you share the file that produces the error? So the bug could be in program that writes those files. Dan On Sun, Jun 14, 2015 at 7:23 PM Jennifer Mary Tarnowski wrote: > Hi, > > I'm receiving the following error when I try to visualize data that is > saved in 10 time steps. > > ERROR: In > /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/IO/XML/vtkXMLDataReader.cxx, > line 434 > > vtkXMLUnstructuredGridReader (0x7faff494d5c0): Cannot read point data > array "Displacement" from PointData in piece 0. The data array in the > element may be too short. > > > After about the 4th time step, I stop receiving the error and things like > displacement, stress, etc. display properly. Is this a bug in ParaView or > is there something I need to change in my settings somewhere to allow > visualization of the first 3 time steps? > > > Thanks, > > > Jennifer > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Mon Jun 15 15:52:50 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Mon, 15 Jun 2015 19:52:50 +0000 Subject: [Paraview] Visualization error In-Reply-To: References: Message-ID: Yes, sure. Send me a link. On Mon, Jun 15, 2015 at 3:47 PM Jennifer Mary Tarnowski wrote: > Dan, > > The files are output from a finite element model and a file for each time > step is ~41 MB. My attachment size limit is 25 MB. Could I share it with > you through something like GoogleDrive? > > A cursory glance through the files with a text editor doesn't show any > significant differences between the time steps that are good and those that > throw the error. > > On Mon, Jun 15, 2015 at 11:48 AM, Dan Lipsa wrote: > >> Jennifer, >> It is quite possible that the files for time steps 0-2 specify a certain >> number of elements in the data array but the data array itself has fewer >> elements. You can see this by opening the file with a text editor. Can you >> share the file that produces the error? >> >> So the bug could be in program that writes those files. >> Dan >> >> >> On Sun, Jun 14, 2015 at 7:23 PM Jennifer Mary Tarnowski >> wrote: >> >>> Hi, >>> >>> I'm receiving the following error when I try to visualize data that is >>> saved in 10 time steps. >>> >>> ERROR: In >>> /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/IO/XML/vtkXMLDataReader.cxx, >>> line 434 >>> >>> vtkXMLUnstructuredGridReader (0x7faff494d5c0): Cannot read point data >>> array "Displacement" from PointData in piece 0. The data array in the >>> element may be too short. >>> >>> >>> After about the 4th time step, I stop receiving the error and things >>> like displacement, stress, etc. display properly. Is this a bug in >>> ParaView or is there something I need to change in my settings somewhere to >>> allow visualization of the first 3 time steps? >>> >>> >>> Thanks, >>> >>> >>> Jennifer >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jtarn002 at ucr.edu Mon Jun 15 15:47:33 2015 From: jtarn002 at ucr.edu (Jennifer Mary Tarnowski) Date: Mon, 15 Jun 2015 12:47:33 -0700 Subject: [Paraview] Visualization error In-Reply-To: References: Message-ID: Dan, The files are output from a finite element model and a file for each time step is ~41 MB. My attachment size limit is 25 MB. Could I share it with you through something like GoogleDrive? A cursory glance through the files with a text editor doesn't show any significant differences between the time steps that are good and those that throw the error. On Mon, Jun 15, 2015 at 11:48 AM, Dan Lipsa wrote: > Jennifer, > It is quite possible that the files for time steps 0-2 specify a certain > number of elements in the data array but the data array itself has fewer > elements. You can see this by opening the file with a text editor. Can you > share the file that produces the error? > > So the bug could be in program that writes those files. > Dan > > > On Sun, Jun 14, 2015 at 7:23 PM Jennifer Mary Tarnowski > wrote: > >> Hi, >> >> I'm receiving the following error when I try to visualize data that is >> saved in 10 time steps. >> >> ERROR: In >> /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/IO/XML/vtkXMLDataReader.cxx, >> line 434 >> >> vtkXMLUnstructuredGridReader (0x7faff494d5c0): Cannot read point data >> array "Displacement" from PointData in piece 0. The data array in the >> element may be too short. >> >> >> After about the 4th time step, I stop receiving the error and things >> like displacement, stress, etc. display properly. Is this a bug in >> ParaView or is there something I need to change in my settings somewhere to >> allow visualization of the first 3 time steps? >> >> >> Thanks, >> >> >> Jennifer >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Mon Jun 15 16:51:05 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Mon, 15 Jun 2015 20:51:05 +0000 Subject: [Paraview] Visualization error In-Reply-To: References: Message-ID: Hi Jennifer, The file for time step 0 does not have Displacement or other point arrays. If I rename time step 0 to vtu_ I can load the rest of the files fine in paraview. This is also reflected in the size of the files. The first one is 17MB, the rest around 40MB. Dan On Mon, Jun 15, 2015 at 3:52 PM Dan Lipsa wrote: > Yes, sure. Send me a link. > > On Mon, Jun 15, 2015 at 3:47 PM Jennifer Mary Tarnowski > wrote: > >> Dan, >> >> The files are output from a finite element model and a file for each time >> step is ~41 MB. My attachment size limit is 25 MB. Could I share it with >> you through something like GoogleDrive? >> >> A cursory glance through the files with a text editor doesn't show any >> significant differences between the time steps that are good and those that >> throw the error. >> >> On Mon, Jun 15, 2015 at 11:48 AM, Dan Lipsa >> wrote: >> >>> Jennifer, >>> It is quite possible that the files for time steps 0-2 specify a certain >>> number of elements in the data array but the data array itself has fewer >>> elements. You can see this by opening the file with a text editor. Can you >>> share the file that produces the error? >>> >>> So the bug could be in program that writes those files. >>> Dan >>> >>> >>> On Sun, Jun 14, 2015 at 7:23 PM Jennifer Mary Tarnowski < >>> jtarn002 at ucr.edu> wrote: >>> >>>> Hi, >>>> >>>> I'm receiving the following error when I try to visualize data that is >>>> saved in 10 time steps. >>>> >>>> ERROR: In >>>> /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/IO/XML/vtkXMLDataReader.cxx, >>>> line 434 >>>> >>>> vtkXMLUnstructuredGridReader (0x7faff494d5c0): Cannot read point data >>>> array "Displacement" from PointData in piece 0. The data array in the >>>> element may be too short. >>>> >>>> >>>> After about the 4th time step, I stop receiving the error and things >>>> like displacement, stress, etc. display properly. Is this a bug in >>>> ParaView or is there something I need to change in my settings somewhere to >>>> allow visualization of the first 3 time steps? >>>> >>>> >>>> Thanks, >>>> >>>> >>>> Jennifer >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From jtarn002 at ucr.edu Mon Jun 15 17:04:18 2015 From: jtarn002 at ucr.edu (Jennifer Mary Tarnowski) Date: Mon, 15 Jun 2015 14:04:18 -0700 Subject: [Paraview] Visualization error In-Reply-To: References: Message-ID: Hmm. I knew that time step 0 shouldn't have any info (based on how the model works). Didn't realize that the first file could affect how the others are read in. So perhaps if I don't read in time step 0, steps 2 and 3 will be okay too. Renaming the first file works too. Thank you! On Mon, Jun 15, 2015 at 1:51 PM, Dan Lipsa wrote: > Hi Jennifer, > The file for time step 0 does not have Displacement or other point arrays. > If I rename time step 0 to vtu_ I can load the rest of the files fine in > paraview. This is also reflected in the size of the files. The first one is > 17MB, the rest around 40MB. > Dan > > > > On Mon, Jun 15, 2015 at 3:52 PM Dan Lipsa wrote: > >> Yes, sure. Send me a link. >> >> On Mon, Jun 15, 2015 at 3:47 PM Jennifer Mary Tarnowski >> wrote: >> >>> Dan, >>> >>> The files are output from a finite element model and a file for each >>> time step is ~41 MB. My attachment size limit is 25 MB. Could I share it >>> with you through something like GoogleDrive? >>> >>> A cursory glance through the files with a text editor doesn't show any >>> significant differences between the time steps that are good and those that >>> throw the error. >>> >>> On Mon, Jun 15, 2015 at 11:48 AM, Dan Lipsa >>> wrote: >>> >>>> Jennifer, >>>> It is quite possible that the files for time steps 0-2 specify a >>>> certain number of elements in the data array but the data array itself has >>>> fewer elements. You can see this by opening the file with a text editor. >>>> Can you share the file that produces the error? >>>> >>>> So the bug could be in program that writes those files. >>>> Dan >>>> >>>> >>>> On Sun, Jun 14, 2015 at 7:23 PM Jennifer Mary Tarnowski < >>>> jtarn002 at ucr.edu> wrote: >>>> >>>>> Hi, >>>>> >>>>> I'm receiving the following error when I try to visualize data that is >>>>> saved in 10 time steps. >>>>> >>>>> ERROR: In >>>>> /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/IO/XML/vtkXMLDataReader.cxx, >>>>> line 434 >>>>> >>>>> vtkXMLUnstructuredGridReader (0x7faff494d5c0): Cannot read point data >>>>> array "Displacement" from PointData in piece 0. The data array in the >>>>> element may be too short. >>>>> >>>>> >>>>> After about the 4th time step, I stop receiving the error and things >>>>> like displacement, stress, etc. display properly. Is this a bug in >>>>> ParaView or is there something I need to change in my settings somewhere to >>>>> allow visualization of the first 3 time steps? >>>>> >>>>> >>>>> Thanks, >>>>> >>>>> >>>>> Jennifer >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Jun 15 21:45:10 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 16 Jun 2015 01:45:10 +0000 Subject: [Paraview] matplotlib Message-ID: <76cd2dd3bc04411092da12901759bf14@ES01AMSNLNT.srn.sandia.gov> I have a user that would like to use matplotlib to draw titles on 2d and 3d plots. Are there any examples around how to do this? Thanks! Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From vishnu2bharathi at gmail.com Tue Jun 16 05:47:08 2015 From: vishnu2bharathi at gmail.com (Vishnubharathi T) Date: Tue, 16 Jun 2015 11:47:08 +0200 Subject: [Paraview] Generating meshes in paraview Message-ID: Dear Paraviewer's, I applied triangulation filter for simple sources Cube, Cone etc., for getting stl format(ASCII). I could able to save it in stl format. How would we generate meshes in paraview? Is it possible to share some details or examples in generating meshes? few examples files to understand meshes in stl formats? with regards, bharathi CIT -------------- next part -------------- An HTML attachment was scrubbed... URL: From roeber at dkrz.de Tue Jun 16 08:53:18 2015 From: roeber at dkrz.de (=?windows-1252?Q?Niklas_R=F6ber?=) Date: Tue, 16 Jun 2015 14:53:18 +0200 Subject: [Paraview] OpenGL2 and ParaView 4.3.1 ... In-Reply-To: References: <88F95E89-085C-4D9F-B061-8E32BC94E9C3@tacc.utexas.edu> Message-ID: <55801C3E.4020805@dkrz.de> Hi, I do get ParaView with OpenGL2 compiled and running, even with some of the plugins. But it crashes quite quickly with the following error message: vtkSIProxy (0x5953890): Failed to create vtkHAVSVolumeMapper. Aborting for debugging purposes. Has anyone gotten ParaView really working with OpenGL2? The current volume rendering is beyond painfully slow ... Thanks, Niklas -- ______________________________________________ Niklas R?ber Deutsches Klimarechenzentrum GmbH Bundesstra?e 45a 20146 Hamburg, Germany email: roeber at dkrz.de phone: +49 (0)40 460094 283 fax: +49 (0)40 460094 270 web: http://www.dkrz.de/ ______________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4896 bytes Desc: S/MIME Cryptographic Signature URL: From Mark.Stock at nrel.gov Tue Jun 16 10:14:49 2015 From: Mark.Stock at nrel.gov (Stock, Mark) Date: Tue, 16 Jun 2015 14:14:49 +0000 Subject: [Paraview] OpenGL2 and ParaView 4.3.1 ... In-Reply-To: <55801C3E.4020805@dkrz.de> References: <88F95E89-085C-4D9F-B061-8E32BC94E9C3@tacc.utexas.edu> , <55801C3E.4020805@dkrz.de> Message-ID: <1434464088665.82542@nrel.gov> Niklas, The CMake command that builds a workable Paraview 4.3.1 with OpenGL2 backend for me is: cmake28 -DVTK_RENDERING_BACKEND=OpenGL2 -DQT_QMAKE_EXECUTABLE=/opt/qt/4.8.5/bin/qmake -DCMAKE_INSTALL_PREFIX=/opt/ParaView/ParaView-v4.3.1-OpenGL2 -DCMAKE_BUILD_TYPE=Release -DPARAVIEW_BUILD_PLUGIN_SciberQuestToolKit=OFF -DPARAVIEW_BUILD_PLUGIN_PointSprite=OFF -DPARAVIEW_BUILD_PLUGIN_EyeDomeLighting=OFF -DPARAVIEW_BUILD_PLUGIN_MobileRemoteControl=OFF -DPARAVIEW_BUILD_PLUGIN_SurfaceLIC=OFF -DPARAVIEW_BUILD_PLUGIN_UncertaintyRendering=OFF -DPARAVIEW_BUILD_PLUGIN_RGBZView=OFF (cmake28 because I'm on RHEL 6.5) I have not tried volume rendering yet, and it still seems to crash on some filters, but triangle mesh rendering is at least 20x faster. Can you turn off HAVS and just use the projected tetra method for volume viz? Mark ________________________________________ From: ParaView on behalf of Niklas R?ber Sent: Tuesday, June 16, 2015 6:53 AM To: paraview at paraview.org Subject: [Paraview] OpenGL2 and ParaView 4.3.1 ... Hi, I do get ParaView with OpenGL2 compiled and running, even with some of the plugins. But it crashes quite quickly with the following error message: vtkSIProxy (0x5953890): Failed to create vtkHAVSVolumeMapper. Aborting for debugging purposes. Has anyone gotten ParaView really working with OpenGL2? The current volume rendering is beyond painfully slow ... Thanks, Niklas -- ______________________________________________ Niklas R?ber Deutsches Klimarechenzentrum GmbH Bundesstra?e 45a 20146 Hamburg, Germany email: roeber at dkrz.de phone: +49 (0)40 460094 283 fax: +49 (0)40 460094 270 web: http://www.dkrz.de/ ______________________________________________ From cory.quammen at kitware.com Tue Jun 16 11:59:57 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 16 Jun 2015 11:59:57 -0400 Subject: [Paraview] matplotlib In-Reply-To: <76cd2dd3bc04411092da12901759bf14@ES01AMSNLNT.srn.sandia.gov> References: <76cd2dd3bc04411092da12901759bf14@ES01AMSNLNT.srn.sandia.gov> Message-ID: Hi Alan, Is there any particular feature of matplotlib you would like to use that the Text Source doesn't provide? Thanks, Cory On Mon, Jun 15, 2015 at 9:45 PM, Scott, W Alan wrote: > I have a user that would like to use matplotlib to draw titles on 2d and 3d > plots. Are there any examples around how to do this? > > Thanks! > > Alan > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen R&D Engineer Kitware, Inc. From kevin.dean at decisionsciencescorp.com Tue Jun 16 15:23:03 2015 From: kevin.dean at decisionsciencescorp.com (Dean, Kevin) Date: Tue, 16 Jun 2015 12:23:03 -0700 Subject: [Paraview] Update Request Data / Information Message-ID: Hey guys. I have a dilemma. I have a script that publishes some reconstruction image (which I then convert to vtkImageData) to a DDS port; and I have ParaView connecting to that within my properties plugin. However, I cannot figure out how to update request data when trying to render the image within the main window. Is there a way to figure out how I can update the data with vtkStreamingDemandDrivenPipeline from my image conversion function?? sorry if the explanation is vague. If you have any questions, I will gladly share what I can. Thanks guys!! Kevin E. Dean -- This email and its contents are confidential. If you are not the intended recipient, please do not disclose or use the information within this email or its attachments. If you have received this email in error, please report the error to the sender by return email and delete this communication from your records. -------------- next part -------------- An HTML attachment was scrubbed... URL: From felix.salazar at polymtl.ca Tue Jun 16 22:19:19 2015 From: felix.salazar at polymtl.ca (Felix Salazar) Date: Tue, 16 Jun 2015 22:19:19 -0400 Subject: [Paraview] PYTHONPATH environmental variable Message-ID: Hello community, I normally run my Paraview scripts in pvpython, so far without issues. But I got some problems using specific Python functions (multiprocess), and decided to switch to import paraview libraries directly within Python I set my PYTHONPATH variable to the installation library where the files are located. Got a few errors, and added more directories, progressively clearing and decreasing the number of errors, until a point where I'm getting this message *Error: Could not import vtkCommonComputationalGeometryPython* Traceback (most recent call last): File "/home/pissarro/fesal/Tools/zReattachment-NP.py", line 4, in except: from paraview.simple import * File "/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages/paraview/simple.py", line 41, in import servermanager File "/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages/paraview/servermanager.py", line 48, in import paraview, re, os, os.path, new, sys, atexit, vtk File "/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages/paraview/vtk/__init__.py", line 7, in from vtkCommonCorePython import * *ImportError: libvtkCommonCorePython27D-pv4.0.so.1: cannot open shared object file: No such file or directory* At this point my PYTHONPATH variable is: PYTHONPATH=*/apps/local-linux/paraview4.01/lib/paraview-4.0* :/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages/paraview/vtk:/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages:/apps/local-linux/paraview4.01/bin And the file libvtkCommonCorePython27D-pv4.0.so.1 is in */apps/local-linux/paraview4.01/lib/paraview-4.0/* Hence, that location is part of the path variable, but for some reason is not recognized. Is there any specific or recommended order to load these directories in the PYTHONPATH variable? Also, if I type help('modules') in a python console, I get this error message before the list of modules Please wait a moment while I gather a list of all available modules... Error: Could not import vtkCommonComputationalGeometryPython Thanks, ------------------------------------ *F?lix Salazar**felix.salazar at polymtl.ca * ?tudiant au doctorat - PhD Student *?cole Polytechnique de Montr?al* ------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From drweymouth at gmail.com Wed Jun 17 07:37:49 2015 From: drweymouth at gmail.com (Gabe Weymouth) Date: Wed, 17 Jun 2015 12:37:49 +0100 Subject: [Paraview] pvbatch camera In-Reply-To: References: Message-ID: Is there a way to set the default view to include all the data in batch mode? I can get this to work by calling Render() before writing an image, but I imagine there is a direct way to do this (perhaps with vtkCamera??). Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Wed Jun 17 10:19:45 2015 From: burlen.loring at gmail.com (Burlen Loring) Date: Wed, 17 Jun 2015 07:19:45 -0700 Subject: [Paraview] PYTHONPATH environmental variable In-Reply-To: References: Message-ID: <55818201.8000301@gmail.com> You also have to prepend the paths with the .so's to LD_LIBRARY_PATH before starting python. Burlen On 06/16/2015 07:19 PM, Felix Salazar wrote: > Hello community, > > I normally run my Paraview scripts in pvpython, so far without issues. > But I got some problems using specific Python functions > (multiprocess), and decided to switch to import paraview libraries > directly within Python > > I set my PYTHONPATH variable to the installation library where the > files are located. Got a few errors, and added more directories, > progressively clearing and decreasing the number of errors, until a > point where I'm getting this message > > *Error: Could not import vtkCommonComputationalGeometryPython* > Traceback (most recent call last): > File "/home/pissarro/fesal/Tools/zReattachment-NP.py", line 4, in > > except: from paraview.simple import * > File > "/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages/paraview/simple.py", > line 41, in > import servermanager > File > "/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages/paraview/servermanager.py", > line 48, in > import paraview, re, os, os.path, new, sys, atexit, vtk > File > "/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages/paraview/vtk/__init__.py", > line 7, in > from vtkCommonCorePython import * > *ImportError: libvtkCommonCorePython27D-pv4.0.so.1: cannot open shared > object file: No such file or directory* > > At this point my PYTHONPATH variable is: > > PYTHONPATH=*/apps/local-linux/paraview4.01/lib/paraview-4.0*:/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages/paraview/vtk:/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages:/apps/local-linux/paraview4.01/bin > > And the file libvtkCommonCorePython27D-pv4.0.so.1 is in > */apps/local-linux/paraview4.01/lib/paraview-4.0/* > > Hence, that location is part of the path variable, but for some reason > is not recognized. Is there any specific or recommended order to load > these directories in the PYTHONPATH variable? > > Also, if I type help('modules') in a python console, I get this error > message before the list of modules > > Please wait a moment while I gather a list of all available modules... > > Error: Could not import vtkCommonComputationalGeometryPython > > Thanks, > > ------------------------------------* > F?lix Salazar > */felix.salazar at polymtl.ca /* > *?tudiant au doctorat - PhD Student > /?cole Polytechnique de Montr?al/ > ------------------------------------ > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Wed Jun 17 10:22:45 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Wed, 17 Jun 2015 10:22:45 -0400 Subject: [Paraview] OpenGL2 and ParaView 4.3.1 ... In-Reply-To: <1434464088665.82542@nrel.gov> References: <88F95E89-085C-4D9F-B061-8E32BC94E9C3@tacc.utexas.edu> <55801C3E.4020805@dkrz.de> <1434464088665.82542@nrel.gov> Message-ID: Yes, We have paraview working* with OpenGL2 backend. In some cases you may run into bugs but its getting there. on vtkHAVSVolumeMapper, what SHA of ParaView you are using? We took care of this issue sometime back and I have not seen this error since then. Also, what dataset (format) you are using? Thanks, On Tue, Jun 16, 2015 at 10:14 AM, Stock, Mark wrote: > Niklas, > > The CMake command that builds a workable Paraview 4.3.1 with OpenGL2 > backend for me is: > > cmake28 -DVTK_RENDERING_BACKEND=OpenGL2 > -DQT_QMAKE_EXECUTABLE=/opt/qt/4.8.5/bin/qmake > -DCMAKE_INSTALL_PREFIX=/opt/ParaView/ParaView-v4.3.1-OpenGL2 > -DCMAKE_BUILD_TYPE=Release -DPARAVIEW_BUILD_PLUGIN_SciberQuestToolKit=OFF > -DPARAVIEW_BUILD_PLUGIN_PointSprite=OFF > -DPARAVIEW_BUILD_PLUGIN_EyeDomeLighting=OFF > -DPARAVIEW_BUILD_PLUGIN_MobileRemoteControl=OFF > -DPARAVIEW_BUILD_PLUGIN_SurfaceLIC=OFF > -DPARAVIEW_BUILD_PLUGIN_UncertaintyRendering=OFF > -DPARAVIEW_BUILD_PLUGIN_RGBZView=OFF > > (cmake28 because I'm on RHEL 6.5) > > I have not tried volume rendering yet, and it still seems to crash on some > filters, but triangle mesh rendering is at least 20x faster. Can you turn > off HAVS and just use the projected tetra method for volume viz? > > Mark > > ________________________________________ > From: ParaView on behalf of Niklas R?ber < > roeber at dkrz.de> > Sent: Tuesday, June 16, 2015 6:53 AM > To: paraview at paraview.org > Subject: [Paraview] OpenGL2 and ParaView 4.3.1 ... > > Hi, > > I do get ParaView with OpenGL2 compiled and running, even with some of > the plugins. But it crashes quite quickly with the following error message: > vtkSIProxy (0x5953890): Failed to create vtkHAVSVolumeMapper. > Aborting for debugging purposes. > > Has anyone gotten ParaView really working with OpenGL2? The current > volume rendering is beyond painfully slow ... > > Thanks, > Niklas > > -- > ______________________________________________ > > Niklas R?ber > Deutsches Klimarechenzentrum GmbH > Bundesstra?e 45a > 20146 Hamburg, Germany > > email: roeber at dkrz.de > phone: +49 (0)40 460094 283 > fax: +49 (0)40 460094 270 > web: http://www.dkrz.de/ > ______________________________________________ > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Jun 17 10:28:16 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 17 Jun 2015 14:28:16 +0000 Subject: [Paraview] OpenGL2 and ParaView 4.3.1 ... In-Reply-To: <55801C3E.4020805@dkrz.de> References: <88F95E89-085C-4D9F-B061-8E32BC94E9C3@tacc.utexas.edu> <55801C3E.4020805@dkrz.de> Message-ID: If you're keen on trying OpenGL2, I'd suggesting use git/master ParaView. A whole lot of fixes have gone in since 4.3.1. Utkarsh On Tue, Jun 16, 2015 at 9:01 AM Niklas R?ber wrote: > Hi, > > I do get ParaView with OpenGL2 compiled and running, even with some of > the plugins. But it crashes quite quickly with the following error message: > vtkSIProxy (0x5953890): Failed to create vtkHAVSVolumeMapper. > Aborting for debugging purposes. > > Has anyone gotten ParaView really working with OpenGL2? The current > volume rendering is beyond painfully slow ... > > Thanks, > Niklas > > -- > ______________________________________________ > > Niklas R?ber > Deutsches Klimarechenzentrum GmbH > Bundesstra?e 45a > 20146 Hamburg, Germany > > email: roeber at dkrz.de > phone: +49 (0)40 460094 283 > fax: +49 (0)40 460094 270 > web: http://www.dkrz.de/ > ______________________________________________ > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From felix.salazar at polymtl.ca Wed Jun 17 13:47:08 2015 From: felix.salazar at polymtl.ca (Felix Salazar) Date: Wed, 17 Jun 2015 13:47:08 -0400 Subject: [Paraview] PYTHONPATH environmental variable In-Reply-To: <55818201.8000301@gmail.com> References: <55818201.8000301@gmail.com> Message-ID: Tried it, but for some reason, it breaks python $ python Could not find platform independent libraries Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] ImportError: No module named site ------------------------------------ *F?lix Salazar**felix.salazar at polymtl.ca * ?tudiant au doctorat - PhD Student *?cole Polytechnique de Montr?al* * LADYF* Lab. de dynamique des fluides (514) 340 4711 ext 2489 Local: C-318.21.3 ------------------------------------ On Wed, Jun 17, 2015 at 10:19 AM, Burlen Loring wrote: > You also have to prepend the paths with the .so's to LD_LIBRARY_PATH > before starting python. > > Burlen > > > On 06/16/2015 07:19 PM, Felix Salazar wrote: > > Hello community, > > I normally run my Paraview scripts in pvpython, so far without issues. > But I got some problems using specific Python functions (multiprocess), and > decided to switch to import paraview libraries directly within Python > > I set my PYTHONPATH variable to the installation library where the files > are located. Got a few errors, and added more directories, progressively > clearing and decreasing the number of errors, until a point where I'm > getting this message > > *Error: Could not import vtkCommonComputationalGeometryPython* > Traceback (most recent call last): > File "/home/pissarro/fesal/Tools/zReattachment-NP.py", line 4, in > > except: from paraview.simple import * > File > "/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages/paraview/simple.py", > line 41, in > import servermanager > File > "/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages/paraview/servermanager.py", > line 48, in > import paraview, re, os, os.path, new, sys, atexit, vtk > File > "/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages/paraview/vtk/__init__.py", > line 7, in > from vtkCommonCorePython import * > *ImportError: libvtkCommonCorePython27D-pv4.0.so.1: cannot open shared > object file: No such file or directory* > > At this point my PYTHONPATH variable is: > > PYTHONPATH=*/apps/local-linux/paraview4.01/lib/paraview-4.0* > :/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages/paraview/vtk:/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages:/apps/local-linux/paraview4.01/bin > > And the file libvtkCommonCorePython27D-pv4.0.so.1 is in > */apps/local-linux/paraview4.01/lib/paraview-4.0/* > > Hence, that location is part of the path variable, but for some reason > is not recognized. Is there any specific or recommended order to load these > directories in the PYTHONPATH variable? > > Also, if I type help('modules') in a python console, I get this error > message before the list of modules > > Please wait a moment while I gather a list of all available modules... > > Error: Could not import vtkCommonComputationalGeometryPython > > Thanks, > > ------------------------------------ > > * F?lix Salazar **felix.salazar at polymtl.ca * > ?tudiant au doctorat - PhD Student > *?cole Polytechnique de Montr?al* > ------------------------------------ > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kevin.dean at decisionsciencescorp.com Wed Jun 17 15:55:06 2015 From: kevin.dean at decisionsciencescorp.com (Dean, Kevin) Date: Wed, 17 Jun 2015 12:55:06 -0700 Subject: [Paraview] Update Request Data / Information In-Reply-To: References: Message-ID: Ok, I figured out how to update the Pipeline. However, I now have another interesting problem. I can't see the volume view update automatically. I have to switch between Volume View and Outline View (for example) in order to see the updated image. Is there a way to update just the volume view? Thanks. Kevin E. Dean On Tue, Jun 16, 2015 at 12:23 PM, Dean, Kevin < kevin.dean at decisionsciencescorp.com> wrote: > Hey guys. > > I have a dilemma. > > I have a script that publishes some reconstruction image (which I then > convert to vtkImageData) to a DDS port; and I have ParaView connecting to > that within my properties plugin. > > However, I cannot figure out how to update request data when trying to > render the image within the main window. Is there a way to figure out how I > can update the data with vtkStreamingDemandDrivenPipeline from my image > conversion function?? > > sorry if the explanation is vague. If you have any questions, I will > gladly share what I can. > > Thanks guys!! > > Kevin E. Dean > -- This email and its contents are confidential. If you are not the intended recipient, please do not disclose or use the information within this email or its attachments. If you have received this email in error, please report the error to the sender by return email and delete this communication from your records. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Wed Jun 17 16:44:20 2015 From: bloring at lbl.gov (Burlen Loring) Date: Wed, 17 Jun 2015 13:44:20 -0700 Subject: [Paraview] PYTHONPATH environmental variable In-Reply-To: References: <55818201.8000301@gmail.com> Message-ID: <5581DC24.3060400@lbl.gov> are you by chance mixing two python installs? like one from a paraview binary you didn't build yourself, and your system python? On 06/17/2015 10:47 AM, Felix Salazar wrote: > Tried it, but for some reason, it breaks python > > $ python > Could not find platform independent libraries > Could not find platform dependent libraries > Consider setting $PYTHONHOME to [:] > ImportError: No module named site > > ------------------------------------* > F?lix Salazar > */felix.salazar at polymtl.ca /* > *?tudiant au doctorat - PhD Student > /?cole Polytechnique de Montr?al/ > /LADYF/ > //Lab. de dynamique des fluides > (514) 340 4711 ext 2489 > Local: C-318.21.3* > *------------------------------------ > > On Wed, Jun 17, 2015 at 10:19 AM, Burlen Loring > > wrote: > > You also have to prepend the paths with the .so's to > LD_LIBRARY_PATH before starting python. > > Burlen > > > On 06/16/2015 07:19 PM, Felix Salazar wrote: >> Hello community, >> >> I normally run my Paraview scripts in pvpython, so far without >> issues. But I got some problems using specific Python functions >> (multiprocess), and decided to switch to import paraview >> libraries directly within Python >> >> I set my PYTHONPATH variable to the installation library where >> the files are located. Got a few errors, and added more >> directories, progressively clearing and decreasing the number of >> errors, until a point where I'm getting this message >> >> *Error: Could not import vtkCommonComputationalGeometryPython* >> Traceback (most recent call last): >> File "/home/pissarro/fesal/Tools/zReattachment-NP.py", line 4, >> in >> except: from paraview.simple import * >> File >> "/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages/paraview/simple.py", >> line 41, in >> import servermanager >> File >> "/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages/paraview/servermanager.py", >> line 48, in >> import paraview, re, os, os.path, new, sys, atexit, vtk >> File >> "/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages/paraview/vtk/__init__.py", >> line 7, in >> from vtkCommonCorePython import * >> *ImportError: libvtkCommonCorePython27D-pv4.0.so.1: cannot open >> shared object file: No such file or directory* >> >> At this point my PYTHONPATH variable is: >> >> PYTHONPATH=*/apps/local-linux/paraview4.01/lib/paraview-4.0*:/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages/paraview/vtk:/apps/local-linux/paraview4.01/lib/paraview-4.0/site-packages:/apps/local-linux/paraview4.01/bin >> >> And the file libvtkCommonCorePython27D-pv4.0.so.1 is in >> */apps/local-linux/paraview4.01/lib/paraview-4.0/* >> >> Hence, that location is part of the path variable, but for some >> reason is not recognized. Is there any specific or recommended >> order to load these directories in the PYTHONPATH variable? >> >> Also, if I type help('modules') in a python console, I get this >> error message before the list of modules >> >> Please wait a moment while I gather a list of all available >> modules... >> >> Error: Could not import vtkCommonComputationalGeometryPython >> >> Thanks, >> >> ------------------------------------* >> F?lix Salazar >> */felix.salazar at polymtl.ca /* >> *?tudiant au doctorat - PhD Student >> /?cole Polytechnique de Montr?al/ >> ------------------------------------ >> >> >> _______________________________________________ >> Powered bywww.kitware.com >> >> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >> >> Search the list archives at:http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From G.D.Weymouth at soton.ac.uk Thu Jun 18 07:43:50 2015 From: G.D.Weymouth at soton.ac.uk (Gabe Weymouth) Date: Thu, 18 Jun 2015 12:43:50 +0100 Subject: [Paraview] Bug for vti in Paraview 4.3 Message-ID: I downloaded the newest stable build of paraview yesterday (upgrading from 4.1) so I could utilize the new features in pvpython (Screenshot, etc). Unfortunately, I ran into what appears to be a bug in the handling of clipping/opacity for vti files. I have a 2D field that ranges from -20 to 110 and I need to isolate the negative regions and discard the positive regions. I do this by clipping (type: scalar, value: 0, inside out). In the new version, this clips the entire field - nothing remains. An alternative method that smooths out the transition is to map the scalar from -2 to 2, setting zero opacity at 2. In the new version of paraview, this blanks out both the positive and negative values, leaving only the region between -2 to 2. A color map without opacity works as expected, and the legend shows the correct opacity behaviour. Playing around with the range of the transfer function, the negative values begin to blank out when the positive limit is set below 20. This would seem to indicate a bug in the application of the transfer function to the image grid surface render. If I repeat the tests using a vtr file and identical data, both clipping and opacity work as expected. I see the same results on my mac and linux workstation. *Gabriel D Weymouth* Southampton Marine and Maritime Institute Lecturer University of Southampton Boldrewood Campus, Building 176, Room 3029 Southampton, SO16 7QF, UK -------------- next part -------------- An HTML attachment was scrubbed... URL: From bbrust at emc-sq.com Thu Jun 18 07:45:52 2015 From: bbrust at emc-sq.com (Bud Brust) Date: Thu, 18 Jun 2015 11:45:52 +0000 Subject: [Paraview] Extracting Line chart data Message-ID: <22CAF6244B430349A0C545A43E351A5932DF5A54@MERCURY.emc-sq.com> When one makes a LineChartView of data plotted along a line in a 3D solid (for instance stress along a line cut through the solid) it can be viewed and each data point can be observed by running the cursor over the plot. Moreover, if I click the rectangular selection box in this chart it identifies the points. If I then click 'edit/finddata' I can see every point. However, if I want to extract the data to (say) copy and paste it in a spread sheet how is this done? I have been rummaging around the Paraview manual and trying different things but cannot seem to get it. Thanks, Bud -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Jun 18 08:48:56 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 18 Jun 2015 08:48:56 -0400 Subject: [Paraview] Extracting Line chart data In-Reply-To: <22CAF6244B430349A0C545A43E351A5932DF5A54@MERCURY.emc-sq.com> References: <22CAF6244B430349A0C545A43E351A5932DF5A54@MERCURY.emc-sq.com> Message-ID: On Thu, Jun 18, 2015 at 7:45 AM, Bud Brust wrote: > > > > Click on the plot filter in the pipeline browser to ensure that it is selected, then go to file->save data. Choose CSV. ok? David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rajphysics.mon at gmail.com Thu Jun 18 10:50:49 2015 From: rajphysics.mon at gmail.com (Raj Kumar Manna) Date: Thu, 18 Jun 2015 20:20:49 +0530 Subject: [Paraview] Surface LIC on a surface of a sphere Message-ID: Hi All, I am trying to get surface LIC on a surface of sphere. I could get surface lic on a plane using the following vtk data format: DATASET STRUCTURED_GRID DIMENSIONS nx ny nz POINTS N .... ... ... POINT_DATA VECTORS ... ... Could you please tell me what is the data format for the surface of a sphere? Thanks Raj -- ################################################################## Raj Kumar Manna Complex Fluid & Biological Physics Lab IIT Madras Ph. No. 8144637401 alternate email: raj at physics.iitm.ac.in #################################################################### -------------- next part -------------- An HTML attachment was scrubbed... URL: From yves.rogez at obs.ujf-grenoble.fr Thu Jun 18 12:39:42 2015 From: yves.rogez at obs.ujf-grenoble.fr (Yves Rogez) Date: Thu, 18 Jun 2015 18:39:42 +0200 Subject: [Paraview] pvpython with pvserver SelectionModel In-Reply-To: References: Message-ID: <5582F44E.1070907@obs.ujf-grenoble.fr> Hi, thank you for your answer, but I come back to this issue... I've made the test with different releases and I get the strict exact same version and path... I also rebuilt ParaView with strictly same python versions (2.7.6). The very strange thing is that with Paraview GUI shell it works but not with pvpython or pvbatch, only since v4.2.0... Any other idea ? Yves Le 26/04/2015 19:22, ?? a ?crit : > Hi, Yves Rogez > > I have encountered the same problem. And I think it is a problem about > the path. > > Please compare the python version and environment setting in different > releases : > > >>> import sys > >>> sys.version > >>> sys.path > > And I think there are some differences responsible for the segfault . > > Di CHENG > > Institute of Mechanics, Chinese Academy of Sciences > No.15 Beisihuanxi Road, Beijing (100190) > P. R. China > E-mail: chengdi at imech.ac.cn > > > > Message: 2 > Date: Sat, 25 Apr 2015 22:18:54 +0200 > From: Yves Rogez > > To: paraview at paraview.org > Subject: [Paraview] pvpython with pvserver SelectionModel > Message-ID: <553BF6AE.9070603 at obs.ujf-grenoble.fr > > > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hello, > > I've just compiled paraview on its last git master branch and I get a > strange segfault using pvpython with connection to a pvserver (no MPI, > on localhost, linux). This occurs for instance, when creating a simple > sphere with the following code: > > from paraview.simple import * > servermanager.Connect( "localhost" ) > s = Sphere() > > The strange thing is that under the ParaView GUI python shell all > works > well. > > I've made a little debugging and the error comes from > ParaViewCore/ServerManager/Core/vtkSMParaViewPipelineController.cxx:609 > (vtkSMParaViewPipelineController::RegisterPipelineProxy()) > the selmodel variable is NULL after > proxy->GetSessionProxyManager()->GetSelectionModel("ActiveSources") > > I recompiled on the > > * 4.3.1 release tag => same problem > * 4.1.0 release tag => all works fine > * 4.2.0 release tag => same problem > > Any idea ? > > Yves > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > -- Yves Rogez /CONSERT Operations Engineer/ *IPAG* /Institut de Plan?tologie et d'Astrophysique de Grenoble / Bat D de Physique - BP. 53 - 38041 Grenoble - FRANCE tel : +33 (0)4 76 63 52 80 lab : +33 (0)4 76 63 57 60 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bbrust at emc-sq.com Thu Jun 18 14:25:38 2015 From: bbrust at emc-sq.com (Bud Brust) Date: Thu, 18 Jun 2015 18:25:38 +0000 Subject: [Paraview] Extracting Line chart data In-Reply-To: References: <22CAF6244B430349A0C545A43E351A5932DF5A54@MERCURY.emc-sq.com> Message-ID: <22CAF6244B430349A0C545A43E351A5932DF5DEF@MERCURY.emc-sq.com> Thank you. Easy to do ? Bud Brust From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Thursday, June 18, 2015 8:49 AM To: Bud Brust Cc: paraview at paraview.org Subject: Re: [Paraview] Extracting Line chart data On Thu, Jun 18, 2015 at 7:45 AM, Bud Brust > wrote: Click on the plot filter in the pipeline browser to ensure that it is selected, then go to file->save data. Choose CSV. ok? David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Thu Jun 18 18:09:40 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Thu, 18 Jun 2015 18:09:40 -0400 Subject: [Paraview] Bug for vti in Paraview 4.3 In-Reply-To: References: Message-ID: Can you share the dataset with us? Best, -berk On Thu, Jun 18, 2015 at 7:43 AM, Gabe Weymouth wrote: > I downloaded the newest stable build of paraview yesterday (upgrading from > 4.1) so I could utilize the new features in pvpython (Screenshot, etc). > Unfortunately, I ran into what appears to be a bug in the handling of > clipping/opacity for vti files. > > I have a 2D field that ranges from -20 to 110 and I need to isolate the > negative regions and discard the positive regions. I do this by clipping > (type: scalar, value: 0, inside out). In the new version, this clips the > entire field - nothing remains. > > An alternative method that smooths out the transition is to map the scalar > from -2 to 2, setting zero opacity at 2. In the new version of paraview, > this blanks out both the positive and negative values, leaving only the > region between -2 to 2. A color map without opacity works as expected, and > the legend shows the correct opacity behaviour. > > Playing around with the range of the transfer function, the negative > values begin to blank out when the positive limit is set below 20. This > would seem to indicate a bug in the application of the transfer function to > the image grid surface render. > > If I repeat the tests using a vtr file and identical data, both clipping > and opacity work as expected. I see the same results on my mac and linux > workstation. > > > *Gabriel D Weymouth* > Southampton Marine and Maritime Institute Lecturer > University of Southampton > Boldrewood Campus, Building 176, Room 3029 > Southampton, SO16 7QF, UK > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Jun 18 21:18:26 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 18 Jun 2015 21:18:26 -0400 Subject: [Paraview] paraview for a "new" application In-Reply-To: References: <280CD6CF-2E16-4390-8670-89A006311356@letnes.com> <55755FF6.9060901@gmail.com> Message-ID: I vote for hdf5 backed xdmf. hdf5 is performant, widely adopted and there are many tools that understand it. The xdmf layer is, at least in concept, very lightweight (it is just text that translates the hdf5 arrays into something that VTK understands) and in the use cases its developers made it for, very performant. The problem with xdmf is that it is inconsistently developed and maintained by a few occasional developers. The good news is that: a) xdmf is open source and contributions in the form of code or documentation are invited b) dedicated support for xdmf if just a kitware support contrac t away c) no longer strictly necessary to get data into ParaView with. See Berk Geveci's excellent article on how to use python to directly ingest hdf5 data for example, or consider a newer high level interface to hdf5 backed data like netcdf4 or exodusII on top of netcdf4. hope that helps David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Sat, Jun 13, 2015 at 4:46 AM, Paul Anton Letnes wrote: > Stefano (and others), > > I?ve seen some of your efforts posted on github. I have to say I commend > your efforts; the open source Fortran community is too small. I will > investigate several of your libraries recently, especially after you > modified the licensing terms to be very liberal. > > Even though VTK is probably the ?right? format to use, I am reluctant to > introduce yet another file format into the fray (our code already has too > many IMHO). That being said, it?s a relatively standard format that should > stand the test of time. Your library appears to solve the issue of writing > the data to disk, at least. > > Best regards, > Paul > > > On 8. jun. 2015, at 11.49, Stefano Zaghi > wrote: > > > > Hi all, > > > > another possibility is to write your Fortran data directly into VTK > files format. > > > > I develop a KISS library in pure Fortran for IO of Fortran data into VTK > standard: see https://github.com/szaghi/Lib_VTK_IO > > > > The exporters are almost complete. The importers are under developing by > a power collaborator https://github.com/victorsndvg/Lib_VTK_IO this work > will be merged very soon into the main branch. > > > > Summarizing, Lib_VTK_IO is > > > > + Lib_VTK_IO is a pure Fortran library to write and read data conforming > the VTK standard; > > + Lib_VTK_IO is Fortran 2003+ standard compliant; > > + Lib_VTK_IO supports parallel architectures by means OpenMP and MPI > paradigms; > > + Lib_VTK_IO supports ascii, binary and base64 file formats; > > + Lib_VTK_IO is a Free, Open Source Project. > > > > My best regards > > > > Stefano Zaghi Ph.D. Aerospace Engineer > > > > Research Scientist, Dept. of Computational Hydrodynamics at CNR-INSEAN > > p: +39 0650299260 | m: +39 3497730036 | e: stefano.zaghi at gmail.com > > > > Codes Showcase > > OFF Open source Finite volumes Fluid dynamics code > > Lib_VTK_IO Fortran library to write and read data conforming the VTK > standard > > FLAP Fortran command Line Arguments Parser for poor men > > BeFoR64 Base64 encoding/decoding library for FoRtran poor men > > FiNeR Fortran INI ParseR and generator for FoRtran poor men > > IR_Precision Fortran (standard 2003) module to develop portable codes > > FoBis.py Fortran Building System for poor men > > PreForM.py Preprocessor for Fortran poor men > > MaTiSSe.py Markdown To Impressive Scientific Slides > > > > > > On Mon, Jun 8, 2015 at 11:27 AM, Armin Wehrfritz > wrote: > > Hi Paul, > > > > as you and Dan already stated, the HDF5 format is a very good choice to > write out large datasets. > > > > I usually write the HDF5 files directly from my simulation codes and > generate a XDMF file afterwards. > > The actual XDMF file contains just the meta data in XML format [1] and > this can be tailored to your application/dataset (I use python with h5py > and xml.etree to do this). > > Hence, my simulation codes (written in C++) only depend on the HDF5 > libraries. > > > > Eventually, this will enable you to store your data in a robust, > flexible and portable file format. > > > > For more complex setups I would also consider using the VTK libraries to > handle the data IO as Dan suggested. > > > > -Armin > > > > [1] http://www.xdmf.org/index.php/XDMF_Model_and_Format > > > > > > > > > > On 06/07/2015 10:40 PM, Dan Lipsa wrote: > > You are right, ParaView does not read hdf5 directly but rather hdf5 > > based formats (hdf5 + additional info): both netcdf and xdmf have > readers. > > You can get a list of all readers supported by your ParaView > > installation using Help in ParaView. Additional readers can be enabled > with > > compile time options. > > > > You can write Xdmf data using vtkXdmfWriter or vtkXdm3Writer (you'll > > have to link with the VTK library). These writers have tests which is a > > good way to see an example of how to use the class. You can also take a > > look at the VTK XML based formats: vtkXMLPolyDataWriter, > > vtkXMLImageDataWriter, vtkXMLUnstructuredGridWriter/Reader. Probably you > > could write data with a library that comes with that format and then > > read it with ParaView. > > > > Do you need parallel writing/reading? > > > > Dan > > > > > > > > > > On Sun, Jun 7, 2015 at 4:26 AM Paul Anton Letnes > > wrote: > > > > Hi Dan! > > > > I?m familiar with the HDF5 library and documentation, but thanks > > anyway for the link. > > > > I don?t see how I can have ParaView read and understand HDF5 files. > > That is, there are several readers (e.g. H5Nimrod) that use HDF5 as > > the underlying format, but I don?t see how to get paraview to > > understand which arrays are coordinates (nodes?), which are results, > > etc. for my application. > > > > Perhaps I should stress again that I have limited experience with > > ParaView, and since the supported file formats and possibilities > > seem endless, I have trouble getting an overview of sensible choices. > > > > My preference for hdf5 is partly due to other software in my > > organization supporting this format, and my own familiarity with it. > > > > Paul > > > > > On 7. jun. 2015, at 04.07, Dan Lipsa > > wrote: > > > > > > Hi Paul, > > > Indeed #2 makes sense, especially if you want to change the > > in-house format. To write the file (from the simulation) it seems to > > me you should checkout > > > > > > https://www.hdfgroup.org/HDF5/doc/fortran/index.html > > > > > > I don't see why ParaView would be used in that process. Am I > > missing something? > > > Dan > > > > > > > > > > > > On Sat, Jun 6, 2015 at 8:04 AM Paul Anton Letnes > > wrote: > > > Hi, fellow paraviewers! > > > > > > I?ve spent some time playing with tutorials and user manuals, and > > so far I?m impressed with what paraview can do. > > > > > > I am working on a specialized structural engineering program > > that, mainly, performs simulations of pipes with circular cross > > sections. Each pipe is split into nodes and 1D elements, and results > > are reported at points (or, less commonly, elements) along the pipe. > > > > > > Some results are reported once per cross section; e.g, the > > tension in the pipe has a single value for the entire cross section. > > Other results, e.g. plastic strain, is reported for a number of > > points along the circumference of the pipe (say, 5-50 points), for > > each of the cross sections. The results can be either ?snapshots? or > > time series. > > > > > > After what I?ve seen from the paraview documentation, possible > > approaches include: > > > 1. Create a paraview plugin to read our current in-house file > format. > > > 2. Directly write output files in an already supported format. > > > 3. Write pvpython scripts that perform the conversion on the fly. > > > > > > Approach 1 is probably a lot of work and the file format is not > > of interest to anyone else (optimally, I?d like to replace it), so > > this seems less attractive. Approach 3 is probably less > > user-friendly for our users. > > > > > > The second approach seems sensible, but the paraview > > documentation does not give many examples of how to do this. > > Optimally, I?d like to write a hdf5-based format (xdmf? netcdf? raw > > hdf5?) directly from Fortran, but I haven?t found documentation on > > how to do this. Using hdf5 seems attractive as it?s so widely > > supported by e.g. matlab, python, and other postprocessing tools > > used in the industry. Getting a single results database would > > simplify a lot of workflows! > > > > > > What would you guys do? > > > > > > Cheers > > > Paul > > > _______________________________________________ > > > Powered by www.kitware.com > > > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > > > Search the list archives at: > http://markmail.org/search/?q=ParaView > > > > > > Follow this link to subscribe/unsubscribe: > > > http://public.kitware.com/mailman/listinfo/paraview > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From timo.oster at ovgu.de Fri Jun 19 02:14:12 2015 From: timo.oster at ovgu.de (Timo Oster) Date: Fri, 19 Jun 2015 08:14:12 +0200 Subject: [Paraview] PYTHONPATH environmental variable Message-ID: <5583B334.6010105@ovgu.de> Hi Felix, I just happened upon the same problem yesterday. The solution was to add the directory with the vkt shared objects into the PYTHONPATH. Those are in .../site-packages/vtk. The .../site-packages/paraview/vtk is just a mirror that includes the libraries from the top-level vtk directory. Hope this helps. Regards, Timo From G.D.Weymouth at soton.ac.uk Fri Jun 19 05:31:14 2015 From: G.D.Weymouth at soton.ac.uk (Gabe Weymouth) Date: Fri, 19 Jun 2015 10:31:14 +0100 Subject: [Paraview] Bug for vti in Paraview 4.3 In-Reply-To: References: Message-ID: Ok, I've put a sample up on dropbox. Note that this uses the "format=append" - I'm not sure if the binary data will be readable if you're using a different system. ? sample.vti ? On Jun 18, 2015 11:10 PM, "Berk Geveci" wrote: > Can you share the dataset with us? > > Best, > -berk > > On Thu, Jun 18, 2015 at 7:43 AM, Gabe Weymouth > wrote: > I downloaded the newest stable build of paraview yesterday (upgrading from > 4.1) so I could utilize the new features in pvpython (Screenshot, etc). > Unfortunately, I ran into what appears to be a bug in the handling of > clipping/opacity for vti files. > > I have a 2D field that ranges from -20 to 110 and I need to isolate the > negative regions and discard the positive regions. I do this by clipping > (type: scalar, value: 0, inside out). In the new version, this clips the > entire field - nothing remains. > > An alternative method that smooths out the transition is to map the scalar > from -2 to 2, setting zero opacity at 2. In the new version of paraview, > this blanks out both the positive and negative values, leaving only the > region between -2 to 2. A color map without opacity works as expected, and > the legend shows the correct opacity behaviour. > > Playing around with the range of the transfer function, the negative > values begin to blank out when the positive limit is set below 20. This > would seem to indicate a bug in the application of the transfer function to > the image grid surface render. > > If I repeat the tests using a vtr file and identical data, both clipping > and opacity work as expected. I see the same results on my mac and linux > workstation. > > > Gabriel D Weymouth > Southampton Marine and Maritime Institute Lecturer > University of Southampton > Boldrewood Campus, Building 176, Room 3029 > Southampton, SO16 7QF, UK > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabian.nick at scai.fraunhofer.de Fri Jun 19 05:48:12 2015 From: fabian.nick at scai.fraunhofer.de (Fabian Nick) Date: Fri, 19 Jun 2015 11:48:12 +0200 Subject: [Paraview] Multiple csv files to time series Message-ID: <5583E55C.3060005@scai.fraunhofer.de> Hi all, I have multiple csv files with point-coordinates and (possibly multiple) data values attached to them, i.e. the rows look like xcoo ycoo zcoo data1 data2... Is there any possibility to display say 10 of those csv files in a "time" series in Paraview? The first three columns are the same for all files in the batch, although I suppose that doesn`t really matter... Thanks in advance, Fabian. From utkarsh.ayachit at kitware.com Fri Jun 19 09:56:45 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 19 Jun 2015 13:56:45 +0000 Subject: [Paraview] PYTHONPATH environmental variable In-Reply-To: <5583B334.6010105@ovgu.de> References: <5583B334.6010105@ovgu.de> Message-ID: I find it easier to figure this out by using pvpython and then doing the following: import sys print sys.path The path should have all the directories that need to be set in your PYTHONPATH. Utkarsh On Fri, Jun 19, 2015 at 2:15 AM Timo Oster wrote: > Hi Felix, > > I just happened upon the same problem yesterday. The solution was to add > the directory with the vkt shared objects into the PYTHONPATH. Those are > in .../site-packages/vtk. The .../site-packages/paraview/vtk is just a > mirror that includes the libraries from the top-level vtk directory. > > Hope this helps. > > Regards, > > Timo > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lyon at fnal.gov Fri Jun 19 12:26:39 2015 From: lyon at fnal.gov (Adam Lyon) Date: Fri, 19 Jun 2015 11:26:39 -0500 Subject: [Paraview] What is the "numpy way"? Message-ID: Hi all, I've been debugging a simulation of particle physics experiment -- I usually have the program make a csv file of some data to visualize (for example, x,y,z,time,Bx,By,Bz) where, e.g., Bx is a component of a magnetic field. I can read that file straight into ParaView with its text file reader, but I find it more convenient to run the csv file through a python script that makes a vtp file and I load that into ParaView. These files tend to be big, and having a compressed binary vtp file means that ParaView can read it very quickly (e.g. I parse csv file once with my script instead of loading it into ParaView to parse each time I open it). The examples in the documentation show how to use the vtk-numpy interface to make a vector of points and "dump" them into a vtkPoints object. For example, d = np.genfromtxt(fname, ...) # more arguments not shown for brevity coord = algs.make_vector(d["x"], d["y"], d["z"]) pts = vtk.vtkPoints() pts.SetData(dsa.numpyTovtkDataArray(coord, "Points")) That looks very nice and must be very efficient. I don't see an obvious way to do the same thing with point or cell data. So, for example, I have... numPts = pts.GetNumberOfPoints() bfield = vtk.vtkFloatArray() bfield.SetNumberOfComponents(3) bfield.SetNumberOfTuples(numPts) bfield.SetName("BField") for a in xrange(numPts): bfield.InsertTuple(a, [ d["Bx"][a], d["By"][a], d["Bz"][a] ]) polyData.GetPointData().AddArray(bfield) # polyData is a vtkPolyData object That loop and explicitly decomposing the "d" array to get at the magnetic field components looks "old fashioned" to me. What would be the "numpy way" to make that work? Thanks! -- Adam *------* *Adam L. Lyon* *Scientist; Associate Division Head for Systems for Scientific Applications* Scientific Computing Division & Muon g-2 Experiment Fermi National Accelerator Laboratory 630 840 5522 office www.fnal.gov lyon at fnal.gov Connect with us! Newsletter | Facebook | Twitter -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Jun 19 13:36:16 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 19 Jun 2015 13:36:16 -0400 Subject: [Paraview] What is the "numpy way"? In-Reply-To: References: Message-ID: Hi Adam, There are some utilities in VTK for converting back and forth from VTK arrays to numpy arrays. Here is an example of usage from within pvpython that should work: >>> import numpy as np >>> d = np.genfromtxt('/home/cory/sample.csv', skip_header=1, delimiter=',') >>> d array([[ 1., 2., 3.], [ 4., 5., 6.], [ 7., 8., 9.]]) >>> import vtk >>> import vtk.util.numpy_support as ns >>> vtk_array = ns.numpy_to_vtk(d, 1, vtk.VTK_FLOAT) >>> vtk_array (vtkFloatArray)0x7f76a9b92410 >>> vtk_array.GetNumberOfComponents() 3 >>> vtk_array.GetNumberOfTuples() 3L >>> vtk_array.GetTuple(0) (1.0, 2.0, 3.0) vtk_array is a vtkDoubleArray holding the values in the numpy array d. The 1 in the second argument means that the data should be deep copied into the VTK array - this is usually what you want unless you hold a reference to the numpy array d somewhere else in your code. I hope that helps. Best regards, Cory On Fri, Jun 19, 2015 at 12:26 PM, Adam Lyon wrote: > Hi all, I've been debugging a simulation of particle physics experiment -- I > usually have the program make a csv file of some data to visualize (for > example, x,y,z,time,Bx,By,Bz) where, e.g., Bx is a component of a magnetic > field. I can read that file straight into ParaView with its text file > reader, but I find it more convenient to run the csv file through a python > script that makes a vtp file and I load that into ParaView. These files tend > to be big, and having a compressed binary vtp file means that ParaView can > read it very quickly (e.g. I parse csv file once with my script instead of > loading it into ParaView to parse each time I open it). > > The examples in the documentation show how to use the vtk-numpy interface to > make a vector of points and "dump" them into a vtkPoints object. For > example, > > d = np.genfromtxt(fname, ...) # more arguments not shown for brevity > > coord = algs.make_vector(d["x"], d["y"], d["z"]) > pts = vtk.vtkPoints() > pts.SetData(dsa.numpyTovtkDataArray(coord, "Points")) > > That looks very nice and must be very efficient. > > I don't see an obvious way to do the same thing with point or cell data. So, > for example, I have... > > numPts = pts.GetNumberOfPoints() > bfield = vtk.vtkFloatArray() > bfield.SetNumberOfComponents(3) > bfield.SetNumberOfTuples(numPts) > bfield.SetName("BField") > > for a in xrange(numPts): > bfield.InsertTuple(a, [ d["Bx"][a], d["By"][a], d["Bz"][a] ]) > > polyData.GetPointData().AddArray(bfield) # polyData is a vtkPolyData object > > That loop and explicitly decomposing the "d" array to get at the magnetic > field components looks "old fashioned" to me. > > What would be the "numpy way" to make that work? Thanks! -- Adam > > ------ > > Adam L. Lyon > Scientist; Associate Division Head for Systems for Scientific Applications > > Scientific Computing Division & Muon g-2 Experiment > Fermi National Accelerator Laboratory > 630 840 5522 office > www.fnal.gov > lyon at fnal.gov > > Connect with us! > Newsletter | Facebook | Twitter > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen R&D Engineer Kitware, Inc. From fabian.nick at scai.fraunhofer.de Fri Jun 19 14:49:02 2015 From: fabian.nick at scai.fraunhofer.de (Fabian Nick) Date: Fri, 19 Jun 2015 20:49:02 +0200 (CEST) Subject: [Paraview] Multiple csv files to time series In-Reply-To: <5583E55C.3060005@scai.fraunhofer.de> References: <5583E55C.3060005@scai.fraunhofer.de> Message-ID: <280833482.271833.1434739742662.JavaMail.zimbra@scai.fraunhofer.de> Hi all, I found a solution: If the files are named foo.XXX - XXX being a consecutive numbering - then Paraview will detect it`s a sequence automatically and will group those files together in the 'Open' dialogue. Cheers, Fabian. ----- Original Message ----- > From: "Fabian Nick" scai.fraunhofer.de> > To: paraview at paraview.org > Sent: Friday, 19 June, 2015 11:48:12 > Subject: Multiple csv files to time series > Hi all, > > I have multiple csv files with point-coordinates and (possibly multiple) > data values attached to them, i.e. the rows look like > > xcoo ycoo zcoo data1 data2... > > Is there any possibility to display say 10 of those csv files in a > "time" series in Paraview? The first three columns are the same for all > files in the batch, although I suppose that doesn`t really matter... > > Thanks in advance, > Fabian. From lyon at fnal.gov Fri Jun 19 15:23:30 2015 From: lyon at fnal.gov (Adam Lyon) Date: Fri, 19 Jun 2015 14:23:30 -0500 Subject: [Paraview] What is the "numpy way"? In-Reply-To: References: Message-ID: Thanks Cory! That was very helpful. One subtlety - my np.genfromtxt has the names argument set, so that returns a structured numpy array. So I had to do, bfieldVtkArray = ns.numpy_to_vtk( d[ ["Bx", "By", "Bz"] ].view( (np.float,3) ), 1, vtk.VTK_FLOAT ) bfieldVtkArray.SetName("BField") That seems to work. The one-column arrays are a little easier. E.g., timeVtkArray = ns.numpy_to_vtk( d["time"].ravel(), 1, vtk.VTK_FLOAT) timeVtkArray.SetName("time") I have to do the .ravel() or else I get the "non-contiguous" error. Avoiding that old-fashioned loops seems to make it quite a bit faster too. Thanks again for the help! -- Adam *------* *Adam L. Lyon* *Scientist; Associate Division Head for Systems for Scientific Applications* Scientific Computing Division & Muon g-2 Experiment Fermi National Accelerator Laboratory 630 840 5522 office www.fnal.gov lyon at fnal.gov Connect with us! Newsletter | Facebook | Twitter On Fri, Jun 19, 2015 at 12:36 PM, Cory Quammen wrote: > Hi Adam, > > There are some utilities in VTK for converting back and forth from VTK > arrays to numpy arrays. Here is an example of usage from within > pvpython that should work: > > >>> import numpy as np > >>> d = np.genfromtxt('/home/cory/sample.csv', skip_header=1, > delimiter=',') > >>> d > array([[ 1., 2., 3.], > [ 4., 5., 6.], > [ 7., 8., 9.]]) > >>> import vtk > >>> import vtk.util.numpy_support as ns > >>> vtk_array = ns.numpy_to_vtk(d, 1, vtk.VTK_FLOAT) > >>> vtk_array > (vtkFloatArray)0x7f76a9b92410 > >>> vtk_array.GetNumberOfComponents() > 3 > >>> vtk_array.GetNumberOfTuples() > 3L > >>> vtk_array.GetTuple(0) > (1.0, 2.0, 3.0) > > vtk_array is a vtkDoubleArray holding the values in the numpy array d. > The 1 in the second argument means that the data should be deep copied > into the VTK array - this is usually what you want unless you hold a > reference to the numpy array d somewhere else in your code. > > I hope that helps. > > Best regards, > Cory > > On Fri, Jun 19, 2015 at 12:26 PM, Adam Lyon wrote: > > Hi all, I've been debugging a simulation of particle physics experiment > -- I > > usually have the program make a csv file of some data to visualize (for > > example, x,y,z,time,Bx,By,Bz) where, e.g., Bx is a component of a > magnetic > > field. I can read that file straight into ParaView with its text file > > reader, but I find it more convenient to run the csv file through a > python > > script that makes a vtp file and I load that into ParaView. These files > tend > > to be big, and having a compressed binary vtp file means that ParaView > can > > read it very quickly (e.g. I parse csv file once with my script instead > of > > loading it into ParaView to parse each time I open it). > > > > The examples in the documentation show how to use the vtk-numpy > interface to > > make a vector of points and "dump" them into a vtkPoints object. For > > example, > > > > d = np.genfromtxt(fname, ...) # more arguments not shown for brevity > > > > coord = algs.make_vector(d["x"], d["y"], d["z"]) > > pts = vtk.vtkPoints() > > pts.SetData(dsa.numpyTovtkDataArray(coord, "Points")) > > > > That looks very nice and must be very efficient. > > > > I don't see an obvious way to do the same thing with point or cell data. > So, > > for example, I have... > > > > numPts = pts.GetNumberOfPoints() > > bfield = vtk.vtkFloatArray() > > bfield.SetNumberOfComponents(3) > > bfield.SetNumberOfTuples(numPts) > > bfield.SetName("BField") > > > > for a in xrange(numPts): > > bfield.InsertTuple(a, [ d["Bx"][a], d["By"][a], d["Bz"][a] ]) > > > > polyData.GetPointData().AddArray(bfield) # polyData is a vtkPolyData > object > > > > That loop and explicitly decomposing the "d" array to get at the magnetic > > field components looks "old fashioned" to me. > > > > What would be the "numpy way" to make that work? Thanks! -- Adam > > > > ------ > > > > Adam L. Lyon > > Scientist; Associate Division Head for Systems for Scientific > Applications > > > > Scientific Computing Division & Muon g-2 Experiment > > Fermi National Accelerator Laboratory > > 630 840 5522 office > > www.fnal.gov > > lyon at fnal.gov > > > > Connect with us! > > Newsletter | Facebook | Twitter > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Jun 19 15:35:37 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 19 Jun 2015 15:35:37 -0400 Subject: [Paraview] What is the "numpy way"? In-Reply-To: References: Message-ID: Adam, Excellent! Thanks for sharing your modifications to make it work with your data. Best regards, Cory On Fri, Jun 19, 2015 at 3:23 PM, Adam Lyon wrote: > Thanks Cory! That was very helpful. One subtlety - my np.genfromtxt has the > names argument set, so that returns a structured numpy array. So I had to > do, > > bfieldVtkArray = ns.numpy_to_vtk( d[ ["Bx", "By", "Bz"] ].view( (np.float,3) > ), 1, vtk.VTK_FLOAT ) > bfieldVtkArray.SetName("BField") > > That seems to work. > > The one-column arrays are a little easier. E.g., > timeVtkArray = ns.numpy_to_vtk( d["time"].ravel(), 1, vtk.VTK_FLOAT) > timeVtkArray.SetName("time") > > I have to do the .ravel() or else I get the "non-contiguous" error. > > Avoiding that old-fashioned loops seems to make it quite a bit faster too. > > Thanks again for the help! -- Adam > > > > > > ------ > > Adam L. Lyon > Scientist; Associate Division Head for Systems for Scientific Applications > > Scientific Computing Division & Muon g-2 Experiment > Fermi National Accelerator Laboratory > 630 840 5522 office > www.fnal.gov > lyon at fnal.gov > > Connect with us! > Newsletter | Facebook | Twitter > > On Fri, Jun 19, 2015 at 12:36 PM, Cory Quammen > wrote: >> >> Hi Adam, >> >> There are some utilities in VTK for converting back and forth from VTK >> arrays to numpy arrays. Here is an example of usage from within >> pvpython that should work: >> >> >>> import numpy as np >> >>> d = np.genfromtxt('/home/cory/sample.csv', skip_header=1, >> >>> delimiter=',') >> >>> d >> array([[ 1., 2., 3.], >> [ 4., 5., 6.], >> [ 7., 8., 9.]]) >> >>> import vtk >> >>> import vtk.util.numpy_support as ns >> >>> vtk_array = ns.numpy_to_vtk(d, 1, vtk.VTK_FLOAT) >> >>> vtk_array >> (vtkFloatArray)0x7f76a9b92410 >> >>> vtk_array.GetNumberOfComponents() >> 3 >> >>> vtk_array.GetNumberOfTuples() >> 3L >> >>> vtk_array.GetTuple(0) >> (1.0, 2.0, 3.0) >> >> vtk_array is a vtkDoubleArray holding the values in the numpy array d. >> The 1 in the second argument means that the data should be deep copied >> into the VTK array - this is usually what you want unless you hold a >> reference to the numpy array d somewhere else in your code. >> >> I hope that helps. >> >> Best regards, >> Cory >> >> On Fri, Jun 19, 2015 at 12:26 PM, Adam Lyon wrote: >> > Hi all, I've been debugging a simulation of particle physics experiment >> > -- I >> > usually have the program make a csv file of some data to visualize (for >> > example, x,y,z,time,Bx,By,Bz) where, e.g., Bx is a component of a >> > magnetic >> > field. I can read that file straight into ParaView with its text file >> > reader, but I find it more convenient to run the csv file through a >> > python >> > script that makes a vtp file and I load that into ParaView. These files >> > tend >> > to be big, and having a compressed binary vtp file means that ParaView >> > can >> > read it very quickly (e.g. I parse csv file once with my script instead >> > of >> > loading it into ParaView to parse each time I open it). >> > >> > The examples in the documentation show how to use the vtk-numpy >> > interface to >> > make a vector of points and "dump" them into a vtkPoints object. For >> > example, >> > >> > d = np.genfromtxt(fname, ...) # more arguments not shown for brevity >> > >> > coord = algs.make_vector(d["x"], d["y"], d["z"]) >> > pts = vtk.vtkPoints() >> > pts.SetData(dsa.numpyTovtkDataArray(coord, "Points")) >> > >> > That looks very nice and must be very efficient. >> > >> > I don't see an obvious way to do the same thing with point or cell data. >> > So, >> > for example, I have... >> > >> > numPts = pts.GetNumberOfPoints() >> > bfield = vtk.vtkFloatArray() >> > bfield.SetNumberOfComponents(3) >> > bfield.SetNumberOfTuples(numPts) >> > bfield.SetName("BField") >> > >> > for a in xrange(numPts): >> > bfield.InsertTuple(a, [ d["Bx"][a], d["By"][a], d["Bz"][a] ]) >> > >> > polyData.GetPointData().AddArray(bfield) # polyData is a vtkPolyData >> > object >> > >> > That loop and explicitly decomposing the "d" array to get at the >> > magnetic >> > field components looks "old fashioned" to me. >> > >> > What would be the "numpy way" to make that work? Thanks! -- Adam >> > >> > ------ >> > >> > Adam L. Lyon >> > Scientist; Associate Division Head for Systems for Scientific >> > Applications >> > >> > Scientific Computing Division & Muon g-2 Experiment >> > Fermi National Accelerator Laboratory >> > 630 840 5522 office >> > www.fnal.gov >> > lyon at fnal.gov >> > >> > Connect with us! >> > Newsletter | Facebook | Twitter >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Search the list archives at: http://markmail.org/search/?q=ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > >> >> >> >> -- >> Cory Quammen >> R&D Engineer >> Kitware, Inc. > > -- Cory Quammen R&D Engineer Kitware, Inc. From u.utku.turuncoglu at be.itu.edu.tr Sat Jun 20 16:15:30 2015 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Sat, 20 Jun 2015 23:15:30 +0300 (EEST) Subject: [Paraview] co-processing script with two datasource ... Message-ID: <11972.140.105.47.80.1434831330.squirrel@webmail.be.itu.edu.tr> Hi, I am tying to run a ParaView pipeline that uses a dataset. In this case, the dataset has both three (time,y,x) and four (time,z,y,x) dimensional fields. In the pipeline, i am loading the same dataset twice (by changing dimensions in the properties window) to access different variables because i am using both 3 and 4 dimensional fields together to create final visualisation. Until, this point everything is fine and it works. Then, i am using co-processing plugin to export pipeline as Python script and wrote a driver to trigger visualisation pipeline (in Python). If i use only fields with 3 (or 4) dimension, then attached driver script works without any problem (driver_00.py) but if i use both 3 and 4 dimensional fields then i need to send two different dataset to DoCoProcessing routine but i could not make it work. I tried to create two different readers like following # read datasets reader1 = pvsimple.NetCDFReader(FileName=sys.argv[2]) reader1.Dimensions = '(zlev, iy, jx)' reader1.SphericalCoordinates = False reader2 = pvsimple.NetCDFReader(FileName=sys.argv[3]) reader2.Dimensions = '(iy, jx)' reader2.SphericalCoordinates = False then i tried to send both of them to coProcess dset1 = reader1.GetClientSideObject().GetOutputDataObject(0) dset2 = reader2.GetClientSideObject().GetOutputDataObject(0) coProcess(dset1, dset2, time, step, sys.argv[1]) by adding extra argument to the coProcess routine and run it as follows cpscript.RequestDataDescription(datadescription) inputdesc1 = datadescription.GetInputDescriptionByName("input") if inputdesc1.GetIfGridIsNecessary() == False: return inputdesc1.SetGrid(grid1) datadescription.AddInput("input1") inputdesc2 = datadescription.GetInputDescriptionByName("input1") if inputdesc2.GetIfGridIsNecessary() == False: return inputdesc2.SetGrid(grid2) cpscript.DoCoProcessing(datadescription) but it is not working. Somehow, i need to add information about the 3 and 4 dimensional fields to data description object. Right? Anyway, my question is that how could i send two different dataset to my visualisation pipeline (coproc_01.py). Thanks, Regards, --ufuk -------------- next part -------------- A non-text attachment was scrubbed... Name: driver_00.py Type: text/x-python-script Size: 1608 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: coproc_01.py Type: text/x-python-script Size: 11427 bytes Desc: not available URL: From vishnu2bharathi at gmail.com Sun Jun 21 10:21:58 2015 From: vishnu2bharathi at gmail.com (Vishnubharathi T) Date: Sun, 21 Jun 2015 16:21:58 +0200 Subject: [Paraview] applying triangulation filter for .inp and .prt file extensions Message-ID: Hi all, I have files with extension .inp(ansys file) and .prt(Unigraphics fiile) I wanted to open them in paraview and convert them into .stl formats after applying triangulation. When I tried opening .inp files. I got the following error: Warning: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\DataModel\vtkDataObject.cxx, line 522 vtkUnstructuredGrid (000000000D074F40): Attempted to ShallowCopy from null. ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\Utilities\VisItBridge\Library\VisItLib\visit_vtk\full\vtkUnstructuredGridRelevantPointsFilter.C, line 109 vtkUnstructuredGridRelevantPointsFilter (000000000EC565F0): No data to Operate On! Please help me with this. I have attached the files for reference. with regards, Bharathi -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: crank2.inp Type: application/octet-stream Size: 2005 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: test file.prt Type: application/unigraphics Size: 159744 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: xmas.inp Type: application/octet-stream Size: 632 bytes Desc: not available URL: From yves.rogez at obs.ujf-grenoble.fr Mon Jun 22 06:48:14 2015 From: yves.rogez at obs.ujf-grenoble.fr (Yves Rogez) Date: Mon, 22 Jun 2015 12:48:14 +0200 Subject: [Paraview] Normal glyph In-Reply-To: References: Message-ID: <5587E7EE.6080504@obs.ujf-grenoble.fr> First of all : please use the paraview mailing list. Your questions could help someone else. 1. change the number of sample points in filter properties 2. select your geometry file -> save data -> choose stl format Yves Le 22/06/2015 12:11, Vishnubharathi T a ?crit : > You should find the "normal glyph" filter in the menu. > > I have the impression that you have sent your message only to me and > not on the paraview mailing list (paraview at paraview.org > ). You should not use an existing topic > to send a different question, but create a new e-mail in order to keep > thread flows consistent. > > Regards, > > Yves > ------------------------------------------------------------------------------------- > > Hello Yves, > > Thanks for the Answer. > > I have few question, which I have stated in attached picture file. > Could you provide answers for that. > > With regards, > Vishnubharathi -- Yves Rogez /CONSERT Operations Engineer/ *IPAG* /Institut de Plan?tologie et d'Astrophysique de Grenoble / Bat D de Physique - BP. 53 - 38041 Grenoble - FRANCE tel : +33 (0)4 76 63 52 80 lab : +33 (0)4 76 63 57 60 -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Mon Jun 22 14:26:25 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 22 Jun 2015 14:26:25 -0400 Subject: [Paraview] co-processing script with two datasource ... In-Reply-To: <11972.140.105.47.80.1434831330.squirrel@webmail.be.itu.edu.tr> References: <11972.140.105.47.80.1434831330.squirrel@webmail.be.itu.edu.tr> Message-ID: I think you need inputdesc1 = datadescription.GetInputDescriptionByName("input") and datadescription.AddInput("input1") before you do cpscript.RequestDataDescription(datadescription). On Sat, Jun 20, 2015 at 4:15 PM, wrote: > Hi, > > I am tying to run a ParaView pipeline that uses a dataset. In this case, > the dataset has both three (time,y,x) and four (time,z,y,x) dimensional > fields. In the pipeline, i am loading the same dataset twice (by changing > dimensions in the properties window) to access different variables because > i am using both 3 and 4 dimensional fields together to create final > visualisation. Until, this point everything is fine and it works. > > Then, i am using co-processing plugin to export pipeline as Python script > and wrote a driver to trigger visualisation pipeline (in Python). If i use > only fields with 3 (or 4) dimension, then attached driver script works > without any problem (driver_00.py) but if i use both 3 and 4 dimensional > fields then i need to send two different dataset to DoCoProcessing routine > but i could not make it work. I tried to create two different readers like > following > > # read datasets > reader1 = pvsimple.NetCDFReader(FileName=sys.argv[2]) > reader1.Dimensions = '(zlev, iy, jx)' > reader1.SphericalCoordinates = False > reader2 = pvsimple.NetCDFReader(FileName=sys.argv[3]) > reader2.Dimensions = '(iy, jx)' > reader2.SphericalCoordinates = False > > then i tried to send both of them to coProcess > > dset1 = reader1.GetClientSideObject().GetOutputDataObject(0) > dset2 = reader2.GetClientSideObject().GetOutputDataObject(0) > > coProcess(dset1, dset2, time, step, sys.argv[1]) > > by adding extra argument to the coProcess routine and run it as follows > > cpscript.RequestDataDescription(datadescription) > inputdesc1 = datadescription.GetInputDescriptionByName("input") > if inputdesc1.GetIfGridIsNecessary() == False: > return > inputdesc1.SetGrid(grid1) > > datadescription.AddInput("input1") > inputdesc2 = datadescription.GetInputDescriptionByName("input1") > if inputdesc2.GetIfGridIsNecessary() == False: > return > inputdesc2.SetGrid(grid2) > > cpscript.DoCoProcessing(datadescription) > > but it is not working. Somehow, i need to add information about the 3 and > 4 dimensional fields to data description object. Right? Anyway, my > question is that how could i send two different dataset to my > visualisation pipeline (coproc_01.py). > > Thanks, > Regards, > > --ufuk > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.david.jones at gmail.com Mon Jun 22 14:32:32 2015 From: bruce.david.jones at gmail.com (Bruce Jones) Date: Mon, 22 Jun 2015 18:32:32 +0000 Subject: [Paraview] Plugin XML Format Specification Message-ID: Hi, I'm working on a custom plugin. I've managed to get the input parameters in the properties panel, and they appear to be working correctly. I would now like to split these properties into a couple of groups with a divider and title between, but I cannot see how this could be achieved. I have looked through the filters.xml in the paraview source, but cannot find a similar case, and I am unable to find any more details on the format specification that what is written on the plugin wiki page. Cheers, Bruce -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Jun 22 14:56:59 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 22 Jun 2015 18:56:59 +0000 Subject: [Paraview] Plugin XML Format Specification In-Reply-To: References: Message-ID: Bruce, Check the Properties Group information here: http://www.paraview.org/Wiki/ParaView/Properties_Panel#Property_Groups Utkarsh On Mon, Jun 22, 2015 at 2:32 PM Bruce Jones wrote: > Hi, > > I'm working on a custom plugin. I've managed to get the input parameters > in the properties panel, and they appear to be working correctly. I would > now like to split these properties into a couple of groups with a divider > and title between, but I cannot see how this could be achieved. I have > looked through the filters.xml in the paraview source, but cannot find a > similar case, and I am unable to find any more details on the format > specification that what is written on the plugin wiki page. > > Cheers, > Bruce > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.david.jones at gmail.com Mon Jun 22 14:59:11 2015 From: bruce.david.jones at gmail.com (Bruce Jones) Date: Mon, 22 Jun 2015 18:59:11 +0000 Subject: [Paraview] Plugin XML Format Specification In-Reply-To: References: Message-ID: Thanks Utkarsh this is exactly what I'm looking for. Cheers, Bruce On Mon, 22 Jun 2015 at 14:57 Utkarsh Ayachit wrote: > Bruce, > > Check the Properties Group information here: > http://www.paraview.org/Wiki/ParaView/Properties_Panel#Property_Groups > > Utkarsh > > On Mon, Jun 22, 2015 at 2:32 PM Bruce Jones > wrote: > >> Hi, >> >> I'm working on a custom plugin. I've managed to get the input parameters >> in the properties panel, and they appear to be working correctly. I would >> now like to split these properties into a couple of groups with a divider >> and title between, but I cannot see how this could be achieved. I have >> looked through the filters.xml in the paraview source, but cannot find a >> similar case, and I am unable to find any more details on the format >> specification that what is written on the plugin wiki page. >> >> Cheers, >> Bruce >> > _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Mon Jun 22 15:23:05 2015 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Mon, 22 Jun 2015 22:23:05 +0300 (EEST) Subject: [Paraview] co-processing script with two datasource ... In-Reply-To: References: <11972.140.105.47.80.1434831330.squirrel@webmail.be.itu.edu.tr> Message-ID: <37863.140.105.47.80.1435000985.squirrel@webmail.be.itu.edu.tr> Hi, Thanks for your help. The driver is running with following code, datadescription = vtkCoProcessorPython.vtkCPDataDescription() datadescription.SetTimeData(time, step) datadescription.AddInput("AtmData1") cpscript.RequestDataDescription(datadescription) inputdesc1 = datadescription.GetInputDescriptionByName("AtmData1") if inputdesc1.GetIfGridIsNecessary() == False: return inputdesc1.SetGrid(grid1) datadescription.AddInput("AtmData2") cpscript.RequestDataDescription(datadescription) inputdesc2 = datadescription.GetInputDescriptionByName("AtmData2") if inputdesc2.GetIfGridIsNecessary() == False: return inputdesc2.SetGrid(grid2) cpscript.DoCoProcessing(datadescription) So, i just need to replace input with AtmData1 and AtmData2 to match with coprocessing script. I think that the input port names must watch with the names with driver code. Thanks again, Regards, --ufuk From andy.bauer at kitware.com Tue Jun 23 00:14:14 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 23 Jun 2015 00:14:14 -0400 Subject: [Paraview] co-processing script with two datasource ... In-Reply-To: <37863.140.105.47.80.1435000985.squirrel@webmail.be.itu.edu.tr> References: <11972.140.105.47.80.1434831330.squirrel@webmail.be.itu.edu.tr> <37863.140.105.47.80.1435000985.squirrel@webmail.be.itu.edu.tr> Message-ID: Hi, You should look at the section on vtkCPDataDescription in the Catalyst User's Guide ( http://www.paraview.org/files/catalyst/docs/ParaViewCatalystUsersGuide_v2.pdf). You're adaptor code should look like: datadescription = vtkCoProcessorPython.vtkCPDataDescription() datadescription.SetTimeData(time, step) datadescription.AddInput("AtmData1") datadescription.AddInput("AtmData2") if cpscript.RequestDataDescription(datadescription) == 0: return inputdesc1 = datadescription.GetInputDescriptionByName("AtmData1") inputdesc2 = datadescription.GetInputDescriptionByName("AtmData2") if inputdesc1.GetIfGridIsNecessary() == True: inputdesc1.SetGrid(grid1) if inputdesc2.GetIfGridIsNecessary() == True: inputdesc2.SetGrid(grid2) cpscript.DoCoProcessing(datadescription) On Mon, Jun 22, 2015 at 3:23 PM, wrote: > Hi, > > Thanks for your help. The driver is running with following code, > > datadescription = vtkCoProcessorPython.vtkCPDataDescription() > datadescription.SetTimeData(time, step) > > datadescription.AddInput("AtmData1") > cpscript.RequestDataDescription(datadescription) > inputdesc1 = datadescription.GetInputDescriptionByName("AtmData1") > if inputdesc1.GetIfGridIsNecessary() == False: > return > inputdesc1.SetGrid(grid1) > > datadescription.AddInput("AtmData2") > cpscript.RequestDataDescription(datadescription) > inputdesc2 = datadescription.GetInputDescriptionByName("AtmData2") > if inputdesc2.GetIfGridIsNecessary() == False: > return > inputdesc2.SetGrid(grid2) > > cpscript.DoCoProcessing(datadescription) > > So, i just need to replace input with AtmData1 and AtmData2 to match with > coprocessing script. I think that the input port names must watch with the > names with driver code. > > Thanks again, > Regards, > > --ufuk > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmitry.ew at gmail.com Tue Jun 23 04:51:00 2015 From: dmitry.ew at gmail.com (Dmitry Grebennikov) Date: Tue, 23 Jun 2015 11:51:00 +0300 Subject: [Paraview] Fwd: Problem with opening Xdmf file in Paraview In-Reply-To: <55891CAA.7030803@gmail.com> References: <55891CAA.7030803@gmail.com> Message-ID: <55891DF4.3040105@gmail.com> An HTML attachment was scrubbed... URL: From victorsv at gmail.com Tue Jun 23 06:10:13 2015 From: victorsv at gmail.com (victor sv) Date: Tue, 23 Jun 2015 12:10:13 +0200 Subject: [Paraview] [Xdmf] Fwd: Problem with opening Xdmf file in Paraview In-Reply-To: <55891DF4.3040105@gmail.com> References: <55891CAA.7030803@gmail.com> <55891DF4.3040105@gmail.com> Message-ID: Hello Dmitry, I'm new with Xdmf and I don't know too many things... First of all I see that in the Xdmf file you are pointing to: data.h5:/data/topology/connectivity The group /data doesn't exist, it should be: data.h5:/topology/connectivity The same happens with the geometry group. After this it still not working... i propose to do small tests modifing the Xdmf file manually to see only the mesh, then some fields and finaly a time sequence. An start point could be: > > > > > > NumberType="UInt">data.h5:/topology/connectivity > > > NumberType="Float">data.h5:/geometry/nodes > > > > > Using tools like h5ls or h5dump you can watch the internal structure of the .h5 file, the datatypes, etc. etc. In order to check the coherence between H5 file and Xdmf metadata. I hope it helps. Best regards, V?ctor. 2015-06-23 10:51 GMT+02:00 Dmitry Grebennikov : > > I'm resending this message without sending files because of size-limit. > Here are the links to them: > https://www.dropbox.com/s/pe9bmeq7ula673z/data.h5?dl=0 > https://www.dropbox.com/s/nh1569inxqy7xol/data.xdmf?dl=0 > > Thanks. > > -------- Forwarded Message -------- Subject: Problem with opening Xdmf > file in Paraview Date: Tue, 23 Jun 2015 11:45:30 +0300 From: Dmitry > Grebennikov To: > xdmf at lists.kitware.com, paraview at paraview.org > > Hi there! > > Please, could you help me to figure out what is the problem with opening > of my Xdmf file in Paraview? > The Xdmf file and corresponding HDF file (3Mb) with data are attached. > > I generated Xdmf file to view results of my test simulation with > time-varying data on the constant tetrahedral mesh. > I can't understand is there any problems with Xdmf file (or HDF)? > When I try to open it in Paraview, the following error occurs: > > > ERROR: In > /home/coincoin/build/paraview/src/ParaView-v4.3.1-source/VTK/IO/Xdmf2/vtkXdmfReader.cxx, > line 409 > > vtkXdmfReader (0x4d42470): Failed to read data. > > ERROR: In > /home/coincoin/build/paraview/src/ParaView-v4.3.1-source/VTK/Common/ExecutionModel/vtkExecutive.cxx, > line 784 > > vtkPVCompositeDataPipeline (0x4d81ae0): Algorithm > vtkFileSeriesReader(0x5e9f3f0) returned failure for request: vtkInformation > (0x4e1fab0) > > Debug: Off > > Modified Time: 165132 > > Reference Count: 1 > > Registered Events: (none) > > Request: REQUEST_DATA > > FROM_OUTPUT_PORT: 0 > > ALGORITHM_AFTER_FORWARD: 1 > > FORWARD_DIRECTION: 0 > > > If someone would be so kind to try to figure out what's the problem, I'll > be very thankful! > > Thanks in advance! > Dmitry > > > > > _______________________________________________ > Xdmf mailing list > Xdmf at lists.kitware.com > http://www.kitware.com/cgi-bin/mailman/listinfo/xdmf > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmitry.ew at gmail.com Tue Jun 23 06:22:46 2015 From: dmitry.ew at gmail.com (Dmitry Grebennikov) Date: Tue, 23 Jun 2015 13:22:46 +0300 Subject: [Paraview] [Xdmf] Fwd: Problem with opening Xdmf file in Paraview In-Reply-To: References: <55891CAA.7030803@gmail.com> <55891DF4.3040105@gmail.com> Message-ID: <55893376.6050000@gmail.com> Hello, thanks, you're right! I didn't notice this misprint. However, now, with proper path to topology and geometry, the Paraview crashes with segfault after clicking on Apply button! On 23.06.2015 13:10, victor sv wrote: > Hello Dmitry, > > I'm new with Xdmf and I don't know too many things... > > First of all I see that in the Xdmf file you are pointing to: > data.h5:/data/topology/connectivity > > The group /data doesn't exist, it should be: > data.h5:/topology/connectivity > > The same happens with the geometry group. From victorsv at gmail.com Tue Jun 23 07:35:56 2015 From: victorsv at gmail.com (victor sv) Date: Tue, 23 Jun 2015 13:35:56 +0200 Subject: [Paraview] [Xdmf] Fwd: Problem with opening Xdmf file in Paraview In-Reply-To: <55893376.6050000@gmail.com> References: <55891CAA.7030803@gmail.com> <55891DF4.3040105@gmail.com> <55893376.6050000@gmail.com> Message-ID: Hello, it also crash for me too. What API are you using to save the data? The signature for DataItem using Xdmf2 is as follows (e.g): testoutput.h5:Data0 The datatype when you writes h5ls -v data.h5/topology/connectivities is "Native long" and with /gemetry/nodes is "Native double". I didn't understand what this means, but are you sure that you are mantaining the coherence related with datatypes between both Xdmf and H5 files? V?ctor. 2015-06-23 12:22 GMT+02:00 Dmitry Grebennikov : > Hello, thanks, you're right! > I didn't notice this misprint. > > However, now, with proper path to topology and geometry, the Paraview > crashes with segfault after clicking on Apply button! > > > > On 23.06.2015 13:10, victor sv wrote: > >> Hello Dmitry, >> >> I'm new with Xdmf and I don't know too many things... >> >> First of all I see that in the Xdmf file you are pointing to: >> data.h5:/data/topology/connectivity >> >> The group /data doesn't exist, it should be: >> data.h5:/topology/connectivity >> >> The same happens with the geometry group. >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfavre at cscs.ch Tue Jun 23 08:10:42 2015 From: jfavre at cscs.ch (Favre Jean) Date: Tue, 23 Jun 2015 12:10:42 +0000 Subject: [Paraview] [Xdmf] Fwd: Problem with opening Xdmf file in Paraview In-Reply-To: References: <55891CAA.7030803@gmail.com> <55891DF4.3040105@gmail.com> <55893376.6050000@gmail.com>, Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F6841F03679@MBX111.d.ethz.ch> you have one error in the definition of the topology. the first line wrongly defines the Dimensions as "54653 4" the correct syntax is: as in: data.h5:/topology/connectivity ----------------- Jean/CSCS -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmitry.ew at gmail.com Tue Jun 23 08:25:05 2015 From: dmitry.ew at gmail.com (Dmitry Grebennikov) Date: Tue, 23 Jun 2015 15:25:05 +0300 Subject: [Paraview] [Xdmf] Fwd: Problem with opening Xdmf file in Paraview In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F6841F03679@MBX111.d.ethz.ch> References: <55891CAA.7030803@gmail.com> <55891DF4.3040105@gmail.com> <55893376.6050000@gmail.com> <0EB9B6375711A04B820E6B6F5CCA9F6841F03679@MBX111.d.ethz.ch> Message-ID: <55895021.4060404@gmail.com> An HTML attachment was scrubbed... URL: From dmitry.ew at gmail.com Tue Jun 23 08:27:05 2015 From: dmitry.ew at gmail.com (Dmitry Grebennikov) Date: Tue, 23 Jun 2015 15:27:05 +0300 Subject: [Paraview] [Xdmf] Fwd: Problem with opening Xdmf file in Paraview In-Reply-To: <55895021.4060404@gmail.com> References: <55891CAA.7030803@gmail.com> <55891DF4.3040105@gmail.com> <55893376.6050000@gmail.com> <0EB9B6375711A04B820E6B6F5CCA9F6841F03679@MBX111.d.ethz.ch> <55895021.4060404@gmail.com> Message-ID: <55895099.9060409@gmail.com> An HTML attachment was scrubbed... URL: From sergi.mateo.bellido at gmail.com Tue Jun 23 08:55:17 2015 From: sergi.mateo.bellido at gmail.com (Sergi Mateo Bellido) Date: Tue, 23 Jun 2015 14:55:17 +0200 Subject: [Paraview] segfault playing a simulation Message-ID: <55895735.2030202@gmail.com> Hi, I'm trying to reproduce a simulation with ParaView 4.3.1 and it always crashes when I start it. You can find the backtrace below: ========================================================= Process id 6681 Caught SIGSEGV at 0x925b124 address not mapped to object Program Stack: WARNING: The stack trace will not use advanced capabilities because this is a release build. 0x7f54ce081d40 : ??? [(???) ???:-1] 0x7f54ce19caf6 : ??? [(???) ???:-1] 0x7f54cb123736 : vtkXMLPStructuredDataReader::CopySubExtent(int*, int*, long long*, int*, int*, long long*, int*, int*, vtkDataArray*, vtkDataArray*) [(libvtkIOXML-pv4.3.so.1) ???:-1] 0x7f54cb12389f : vtkXMLPStructuredDataReader::CopyArrayForPoints(vtkDataArray*, vtkDataArray*) [(libvtkIOXML-pv4.3.so.1) ???:-1] 0x7f54cb11cc1f : vtkXMLPDataReader::ReadPieceData() [(libvtkIOXML-pv4.3.so.1) ???:-1] 0x7f54cb11ca14 : vtkXMLPDataReader::ReadPieceData(int) [(libvtkIOXML-pv4.3.so.1) ???:-1] 0x7f54cb124d7a : vtkXMLPStructuredDataReader::ReadXMLData() [(libvtkIOXML-pv4.3.so.1) ???:-1] 0x7f54cb1280eb : vtkXMLReader::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) [(libvtkIOXML-pv4.3.so.1) ???:-1] 0x7f54cb1273b6 : vtkXMLReader::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) [(libvtkIOXML-pv4.3.so.1) ???:-1] 0x7f54cd6200f9 : vtkFileSeriesReader::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1] 0x7f54cd61f07f : vtkFileSeriesReader::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1] 0x7f54d2706204 : vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] 0x7f54d27016cc : vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] 0x7f54d2700201 : vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] 0x7f54d2704067 : vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] 0x7f54d271d959 : vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] 0x7f54d26fe387 : vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] 0x7f54d2704010 : vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] 0x7f54d271d959 : vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] 0x7f54d26fe387 : vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] 0x7f54d2704010 : vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] 0x7f54d271d959 : vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] 0x7f54d27035ae : vtkDemandDrivenPipeline::UpdateData(int) [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] 0x7f54d271e87f : vtkStreamingDemandDrivenPipeline::Update(int) [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] 0x7f54cd98fa7f : vtkPVDataRepresentation::ProcessViewRequest(vtkInformationRequestKey*, vtkInformation*, vtkInformation*) [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1] 0x7f54cd973d79 : vtkGeometryRepresentation::ProcessViewRequest(vtkInformationRequestKey*, vtkInformation*, vtkInformation*) [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1] 0x7f54cd975d71 : vtkGeometryRepresentationWithFaces::ProcessViewRequest(vtkInformationRequestKey*, vtkInformation*, vtkInformation*) [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1] 0x7f54cd9bd388 : vtkPVView::CallProcessViewRequest(vtkInformationRequestKey*, vtkInformation*, vtkInformationVector*) [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1] 0x7f54cd9bd552 : vtkPVView::Update() [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1] 0x7f54cd9acb78 : vtkPVRenderView::Update() [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1] 0x7f54d780ac30 : vtkPVRenderViewCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1] 0x7f54d4e135e0 : vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) [(libvtkClientServer-pv4.3.so.1) ???:-1] 0x7f54d4e18393 : vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1] 0x7f54d4e16832 : vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1] 0x7f54d4e16ced : vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) [(libvtkClientServer-pv4.3.so.1) ???:-1] 0x7f54d5b26cec : vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] 0x7f54d5b26958 : vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] 0x7f54d5b25203 : vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] 0x7f54cdcae44f : vtkSMViewProxy::Update() [(libvtkPVServerManagerRendering-pv4.3.so.1) ???:-1] 0x7f54cdf2f6f7 : vtkSMAnimationScene::TickInternal(double, double, double) [(libvtkPVAnimation-pv4.3.so.1) ???:-1] 0x7f54cf415cab : vtkAnimationCue::Tick(double, double, double) [(libvtkCommonCore-pv4.3.so.1) ???:-1] 0x7f54cdf23268 : vtkAnimationPlayer::Play() [(libvtkPVAnimation-pv4.3.so.1) ???:-1] 0x7f54d7851619 : vtkSMAnimationSceneCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1] 0x7f54d4e135e0 : vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) [(libvtkClientServer-pv4.3.so.1) ???:-1] 0x7f54d4e18393 : vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1] 0x7f54d4e16832 : vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1] 0x7f54d4e16ced : vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) [(libvtkClientServer-pv4.3.so.1) ???:-1] 0x7f54d5b436d4 : vtkSIProperty::ProcessMessage(vtkClientServerStream&) [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] 0x7f54d5b4377e : vtkSIProperty::Push(paraview_protobuf::Message*, int) [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] 0x7f54d5b4459e : vtkSIProxy::Push(paraview_protobuf::Message*) [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] 0x7f54d5b2884a : vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*) [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] 0x7f54d5b27484 : vtkPVSessionCore::PushState(paraview_protobuf::Message*) [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] 0x7f54d5b2514d : vtkPVSessionBase::PushState(paraview_protobuf::Message*) [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] 0x7f54d5d859b7 : vtkSMProxy::UpdateProperty(char const*, int) [(libvtkPVServerManagerCore-pv4.3.so.1) ???:-1] 0x7f54d6d8aa07 : pqVCRController::onPlay() [(libvtkpqComponents-pv4.3.so.1) ???:-1] 0x7f54cfa98258 : QMetaObject::activate(QObject*, QMetaObject const*, int, void**) [(libQtCore.so.4) ???:-1] 0x7f54d01102f2 : QAction::triggered(bool) [(libQtGui.so.4) ???:-1] 0x7f54d0111710 : QAction::activate(QAction::ActionEvent) [(libQtGui.so.4) ???:-1] 0x7f54d04fd514 : ??? [(???) ???:-1] 0x7f54d04fd7ab : QAbstractButton::mouseReleaseEvent(QMouseEvent*) [(libQtGui.so.4) ???:-1] 0x7f54d05d15ea : QToolButton::mouseReleaseEvent(QMouseEvent*) [(libQtGui.so.4) ???:-1] 0x7f54d0175ac1 : QWidget::event(QEvent*) [(libQtGui.so.4) ???:-1] 0x7f54d04fca3f : QAbstractButton::event(QEvent*) [(libQtGui.so.4) ???:-1] 0x7f54d05d422d : QToolButton::event(QEvent*) [(libQtGui.so.4) ???:-1] 0x7f54d011759e : QApplicationPrivate::notify_helper(QObject*, QEvent*) [(libQtGui.so.4) ???:-1] 0x7f54d011e533 : QApplication::notify(QObject*, QEvent*) [(libQtGui.so.4) ???:-1] 0x7f54cfa802f3 : QCoreApplication::notifyInternal(QObject*, QEvent*) [(libQtCore.so.4) ???:-1] 0x7f54d011a656 : QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) [(libQtGui.so.4) ???:-1] 0x7f54d019ca94 : ??? [(???) ???:-1] 0x7f54d019b877 : QApplication::x11ProcessEvent(_XEvent*) [(libQtGui.so.4) ???:-1] 0x7f54d01c4805 : ??? [(???) ???:-1] 0x7f54cfa7f375 : QEventLoop::processEvents(QFlags) [(libQtCore.so.4) ???:-1] 0x7f54cfa7f748 : QEventLoop::exec(QFlags) [(libQtCore.so.4) ???:-1] 0x7f54cfa8414b : QCoreApplication::exec() [(libQtCore.so.4) ???:-1] 0x407785 : main [(paraview) ???:-1] 0x7f54ce06cec5 : __libc_start_main [(libc.so.6) ???:-1] 0x4074da : QMainWindow::event(QEvent*) [(paraview) ???:-1] ========================================================= Thanks, Sergi Mateo sergi.mateo.bellido at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rcrocker at uvm.edu Tue Jun 23 19:37:21 2015 From: rcrocker at uvm.edu (Ryan Crocker) Date: Tue, 23 Jun 2015 16:37:21 -0700 Subject: [Paraview] Changing the "solid color" to white for screenshots and exporting Message-ID: <5E9FE600-EDB4-49C5-B800-38816B8CA2CF@uvm.edu> Hi, I thought this would be straight forward but it does not seem to be. I want to basically just get a picture of my grid with no background and a few contours which are lines. To do this i?m trying to set the the color of the default ?Solid Color? to white. No matter what i do it?s always grey or off white in the view port and when i print it. I?ve come close by using wireframe but that makes my grid look weird (some lines are wider than others for some reason). Is there a way to do this with surface with edges? That representation of my grid actually looks like a grid. From logg at chalmers.se Thu Jun 25 02:18:02 2015 From: logg at chalmers.se (Anders Logg) Date: Thu, 25 Jun 2015 06:18:02 +0000 Subject: [Paraview] Visualize density (a galaxy of stars) Message-ID: I want to visualize a galaxy computed as a 3D scalar mass distribution (density). I have tried a couple of different options, direct rendering of the field as a volume and by using the isovolume filter. In the first case the result is a quite blurry image which makes it difficult to see the shape of the galaxy. In the second case the resulting shape depends quite heavily on which value I pick for the isovolume. Does anyone know of a better option to try? Thanks -- Anders -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Jun 25 09:42:25 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 25 Jun 2015 13:42:25 +0000 Subject: [Paraview] Executive Not calling RequestData In-Reply-To: References: Message-ID: RequestData doesn't get called unless the pipeline determines that something has changed. This is at core of VTK's demand driven execution pipeline. You may want to checkout Berk's blog ( http://www.kitware.com/blog/home/post/831) about how you can use `CONTINUE_EXECUTING` key for "streaming". Utkarsh On Wed, Jun 24, 2015 at 2:32 PM Dean, Kevin < kevin.dean at decisionsciencescorp.com> wrote: > I was wondering if anyone has run into this problem before. I am streaming > vtkPolyData objects into ParaView, but for some reason (after my > UpdatePipeline function is called), the executive does not call RequestData > upon an Update command. Could there be any reasons for this? > > Here is my snippet: > > *void* *VTKPolyDataObjectsDDSReader::UpdateMyPipeline*(vtkPolyData* > poly_data) > { > // DEBUG: > // printf("%s\n", __PRETTY_FUNCTION__); > > VTKPolyDataObjectsDDSReader::*UpdateInformation*(); > vtkStreamingDemandDrivenPipeline* executive = > vtkStreamingDemandDrivenPipeline::*SafeDownCast*( > VTKPolyDataObjectsDDSReader::*GetExecutive*()); > > *if* (!executive) > { > *return*; > } > > *this*->poly_data = poly_data; > > *for* (*int* i = 0; i < *this*->poly_data->*GetNumberOfPieces*(); i++) > { > executive->*SetUpdateExtent*(0, i, *this*->poly_data-> > *GetNumberOfPieces*(), 0); > VTKPolyDataObjectsDDSReader::*Update*(); > } > } > > Any help is appreciated! Thanks guys. > > Kevin E. Dean > > P.S. - also attached is a screenshot of what some of the output looks like. > > This email and its contents are confidential. If you are not the intended > recipient, please do not disclose or use the information within this email > or its attachments. If you have received this email in error, please report > the error to the sender by return email and delete this communication from > your records. -------------- next part -------------- An HTML attachment was scrubbed... URL: From psavidge0 at gmail.com Thu Jun 25 14:58:18 2015 From: psavidge0 at gmail.com (patrick savidge) Date: Thu, 25 Jun 2015 11:58:18 -0700 Subject: [Paraview] Trouble plotting variables Message-ID: Hi Everyone, I am fairly new to paraview and am having a little difficulty. I have a simulation of an elastic bar undergoing a body force and I want to plot it's particle displacement as a function of time. I have followed many tutorials, but my plot does not show any data. The simulation which I'm trying to do this for is found here: https://drive.google.com/file/d/0B8yl7RuERTNjR3FiZFhPNWVaOTA/view?usp=sharing Unlike many simulations I have seen run by Paraview, mine object is not a solid body but rather a collection of node points. Could this be why the plot is not working? Thank you for your help! Patrick Savidge -- Patrick Savidge University of California, Berkeley Mechanical Engineering, 2017 psavidge0 at gmail.com (951)5536642 -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Jun 25 16:33:54 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 25 Jun 2015 20:33:54 +0000 Subject: [Paraview] [EXTERNAL] Trouble plotting variables In-Reply-To: References: Message-ID: Patrick, I believe you are having multiple problems with your dataset. Here is what i found: ? Your dataset appears to be good. It is a bunch of points (nodes) (cell type vertex). It displays well. Read in all of the data, hit apply. Go to the last time step, then color by Displacement (point). You see you have displacement data in your bar. You can actually see this displacement. Go back to time step 0, then in the properties tab, change Displacement Magnitude to 1000000 (one million). Go to last timestep. (We had to do this because your displacement is tiny in relationship to the length of the bar itself.) To see the length of the bar, Properties tab, Show Axes. ? It is difficult, but you can plot a point over time. The trick is you need to select one point. Zoom is your friend here. I rolled the beam around until I could see one point at the bottom. Then, Select Points On (little icon upper left of the 3d window), and rubber band select a point. Now, Filters/ Data Analysis/ Plot Selection Over Time. You see gobs of plots. Properties tab, slide down, Series Parameters. turn off the plots you don?t want. I used only displacement magnitude. You see your displacement. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of patrick savidge Sent: Thursday, June 25, 2015 12:58 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] Trouble plotting variables Hi Everyone, I am fairly new to paraview and am having a little difficulty. I have a simulation of an elastic bar undergoing a body force and I want to plot it's particle displacement as a function of time. I have followed many tutorials, but my plot does not show any data. The simulation which I'm trying to do this for is found here: https://drive.google.com/file/d/0B8yl7RuERTNjR3FiZFhPNWVaOTA/view?usp=sharing Unlike many simulations I have seen run by Paraview, mine object is not a solid body but rather a collection of node points. Could this be why the plot is not working? Thank you for your help! Patrick Savidge -- Patrick Savidge University of California, Berkeley Mechanical Engineering, 2017 psavidge0 at gmail.com (951)5536642 -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Jun 25 17:47:43 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 25 Jun 2015 21:47:43 +0000 Subject: [Paraview] [EXTERNAL] Trouble plotting variables In-Reply-To: References: Message-ID: Keeping this thread on the list, so others can see my answer and/or correct me. :-) I am pretty sure you have only points, but not 3d cells. Thus, the lines don?t go through any of your data. You want a dataset that is solid to do this with. Download the ParaView data from the Kitware website, load in either can.exo or disk_out_ref.exo and try that. You can also try plot over line for Sources/ Wavelet. Alan From: patrick savidge [mailto:psavidge0 at gmail.com] Sent: Thursday, June 25, 2015 3:44 PM To: Scott, W Alan Subject: Re: [EXTERNAL] [Paraview] Trouble plotting variables Alan, Thank you for your help! I have one more question. Do you have any idea why the "plot over line" does not output data for me? I'm trying to use it to plot displacement over the length of the bar. Patrick On Thu, Jun 25, 2015 at 1:33 PM, Scott, W Alan > wrote: Patrick, I believe you are having multiple problems with your dataset. Here is what i found: ? Your dataset appears to be good. It is a bunch of points (nodes) (cell type vertex). It displays well. Read in all of the data, hit apply. Go to the last time step, then color by Displacement (point). You see you have displacement data in your bar. You can actually see this displacement. Go back to time step 0, then in the properties tab, change Displacement Magnitude to 1000000 (one million). Go to last timestep. (We had to do this because your displacement is tiny in relationship to the length of the bar itself.) To see the length of the bar, Properties tab, Show Axes. ? It is difficult, but you can plot a point over time. The trick is you need to select one point. Zoom is your friend here. I rolled the beam around until I could see one point at the bottom. Then, Select Points On (little icon upper left of the 3d window), and rubber band select a point. Now, Filters/ Data Analysis/ Plot Selection Over Time. You see gobs of plots. Properties tab, slide down, Series Parameters. turn off the plots you don?t want. I used only displacement magnitude. You see your displacement. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of patrick savidge Sent: Thursday, June 25, 2015 12:58 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] Trouble plotting variables Hi Everyone, I am fairly new to paraview and am having a little difficulty. I have a simulation of an elastic bar undergoing a body force and I want to plot it's particle displacement as a function of time. I have followed many tutorials, but my plot does not show any data. The simulation which I'm trying to do this for is found here: https://drive.google.com/file/d/0B8yl7RuERTNjR3FiZFhPNWVaOTA/view?usp=sharing Unlike many simulations I have seen run by Paraview, mine object is not a solid body but rather a collection of node points. Could this be why the plot is not working? Thank you for your help! Patrick Savidge -- Patrick Savidge University of California, Berkeley Mechanical Engineering, 2017 psavidge0 at gmail.com (951)5536642 -- Patrick Savidge University of California, Berkeley Mechanical Engineering, 2017 psavidge0 at gmail.com (951)5536642 -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Thu Jun 25 20:15:45 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Thu, 25 Jun 2015 20:15:45 -0400 Subject: [Paraview] Visualize density (a galaxy of stars) In-Reply-To: References: Message-ID: Hi Anders, If you could share some data or at least pictures, we might be able to help better. Best, -berk On Thu, Jun 25, 2015 at 2:18 AM, Anders Logg wrote: > I want to visualize a galaxy computed as a 3D scalar mass distribution > (density). > I have tried a couple of different options, direct rendering of the field > as a volume and by using the isovolume filter. In the first case the result > is a quite blurry image which makes it difficult to see the shape of the > galaxy. In the second case the resulting shape depends quite heavily on > which value I pick for the isovolume. > Does anyone know of a better option to try? > Thanks > -- > Anders > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From logg at chalmers.se Fri Jun 26 03:36:34 2015 From: logg at chalmers.se (Anders Logg) Date: Fri, 26 Jun 2015 07:36:34 +0000 Subject: [Paraview] Visualize density (a galaxy of stars) In-Reply-To: References: Message-ID: Sure! http://www.math.chalmers.se/~logg/tmp/torus.vtu.gz Ideally I would like to visualize this as a glowing torus-shaped galaxy in empty space. PS: A friend tipped me to visualize the data as a point cloud instead so I'm currently experimenting with sampling the density data to form a point cloud (outside of ParaView). This might be a better alternative than visualizing the density directly. -- Anders fre 26 juni 2015 kl 02:16 skrev Berk Geveci : > Hi Anders, > > If you could share some data or at least pictures, we might be able to > help better. > > Best, > -berk > > On Thu, Jun 25, 2015 at 2:18 AM, Anders Logg wrote: > >> I want to visualize a galaxy computed as a 3D scalar mass distribution >> (density). >> I have tried a couple of different options, direct rendering of the field >> as a volume and by using the isovolume filter. In the first case the result >> is a quite blurry image which makes it difficult to see the shape of the >> galaxy. In the second case the resulting shape depends quite heavily on >> which value I pick for the isovolume. >> Does anyone know of a better option to try? >> Thanks >> -- >> Anders >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at bpi.cam.ac.uk Fri Jun 26 04:15:34 2015 From: chris at bpi.cam.ac.uk (Chris Richardson) Date: Fri, 26 Jun 2015 09:15:34 +0100 Subject: [Paraview] Visualize density (a galaxy of stars) In-Reply-To: References: Message-ID: <0aae2421fe8830dccc8b1aa51cd70dcd@cam.ac.uk> On 26/06/2015 08:36, Anders Logg wrote: > Sure! > > http://www.math.chalmers.se/~logg/tmp/torus.vtu.gz [6] > > Ideally I would like to visualize this as a glowing torus-shaped > galaxy in empty space. > > PS: A friend tipped me to visualize the data as a point cloud instead > so I'm currently experimenting with sampling the density data to form > a point cloud (outside of ParaView). This might be a better > alternative than visualizing the density directly. > You could also try contouring it at different levels, and turning opacity to ~0.5 or so. Chris From u.utku.turuncoglu at be.itu.edu.tr Fri Jun 26 05:58:45 2015 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Fri, 26 Jun 2015 12:58:45 +0300 (EEST) Subject: [Paraview] problem in defining vtkStructuredGrid in MPI Message-ID: <35434.140.105.47.80.1435312725.squirrel@webmail.be.itu.edu.tr> Hi, I am trying to create structured grid in an MPI application and i am using following C++ code to implement it extern "C" void createstgrid_(double* y, double* x, int* nxstart, int* nxend, int* nystart, int* nyend, int* nx, int* ny, int* nz, int* mpiSize, int* mpiRank) { // // Create structured grid // vtkSmartPointer sg = vtkSmartPointer::New(); sg->SetExtent (*nxstart-1, *nxend-1, *nystart-1, *nyend-1, 0, 0); // // Create data structure to store grid coordinates // int pnx = ((*nxend)-(*nxstart))+1; int pny = ((*nyend)-(*nystart))+1; vtkSmartPointer points = vtkSmartPointer::New(); // // Insert grid coordinate data as points // k = 0; for (int j = 0; j < pny; j++) { for (int i = 0; i < pnx; i++) { points->InsertPoint(k, x[i+j*pnx], y[i+j*pnx], 0); k = k+1; } } sg->SetPoints(points); // // Set grid // vtkCPPythonAdaptorAPI::GetCoProcessorData()->GetInputDescriptionByName("input")->SetGrid(sg); vtkCPPythonAdaptorAPI::GetCoProcessorData()->GetInputDescriptionByName("input")->SetWholeExtent(0, *nx-1, 0, *ny-1, 0, 0); } so, when i run the code with grid writer, it creates the individual file (*.vts) for each processor and one extra for the combination (*.pvts). Anyway, the individual files looks fine in Paraview but if i open the file with pvts extension, i am getting following error, ERROR: In /Users/turuncu/Qsync/progs/paraview-4.3.1/src/VTK/IO/XML/vtkXMLPStructuredDataReader.cxx, line 461 vtkXMLPStructuredGridReader (0x7f961c0910a0): No available piece provides data for the following extents: 0 140 0 1 0 0 0 1 1 58 0 0 0 140 58 59 0 0 0 1 59 114 0 0 71 72 1 58 0 0 71 72 59 114 0 0 The UpdateExtent cannot be filled. What is the meaning of this message? It means that some of the grid data (or points) are not filled by the code. I also check the loop in the C++ code and print out the number of points for each processor 0 number of points = 4118 1 number of points = 4047 2 number of points = 4060 3 number of points = 3990 and the total is 16215, which is consistent with the size of the grid but if i check the individual vts files from the Paraview, the files shows different number of points for each file 0 number of points = 4118 1 number of points = 3976 2 number of points = 4002 3 number of points = 3864 So, only first file matchs with the C++ code but others not. I am not sure what is happening in there and if you have any suggestion that will be great. Anyway, in this case i did not use vtkMultiBlockDataSet but after having correct representation of the grid, i am planing use SetBlock method of vtkMultiBlockDataSet to assign decomposition elements as individual blocks. Regards, --ufuk From lukasz.paluszek at airbus.com Fri Jun 26 06:32:40 2015 From: lukasz.paluszek at airbus.com (Paluszek, Lukasz) Date: Fri, 26 Jun 2015 10:32:40 +0000 Subject: [Paraview] Visualize density (a galaxy of stars) In-Reply-To: <3378_1435306540_558D0A2C_3378_6994_15_0aae2421fe8830dccc8b1aa51cd70dcd@cam.ac.uk> References: <3378_1435306540_558D0A2C_3378_6994_15_0aae2421fe8830dccc8b1aa51cd70dcd@cam.ac.uk> Message-ID: Hello Anders, I don't know what your expectations as to how sharp the image should be are, but your data set is too coarse to obtain a sharper rendering. What I suggest is that you either refine your mesh or you resample your data onto a finer vti image and then do the volume rendering. I have attached a picture with your original galaxy and a resampled one, perhaps this is what you are looking for. I must admit though, that the left image looks more "Hubble-like" :-). Regards, Lukasz ?ukasz Paluszek Airbus Helicopters Aerodynamics Department (ETGA) 86607 Donauw?rth Germany Tel.: +49 (90) 671 8231 Fax.: +49 (90) 671 9122 Lukasz.Paluszek at airbus.com -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Chris Richardson Sent: 26 June 2015 10:16 To: Anders Logg Cc: ParaView Mailing List Subject: Re: [Paraview] Visualize density (a galaxy of stars) On 26/06/2015 08:36, Anders Logg wrote: > Sure! > > http://www.math.chalmers.se/~logg/tmp/torus.vtu.gz [6] > > Ideally I would like to visualize this as a glowing torus-shaped > galaxy in empty space. > > PS: A friend tipped me to visualize the data as a point cloud instead > so I'm currently experimenting with sampling the density data to form > a point cloud (outside of ParaView). This might be a better > alternative than visualizing the density directly. > You could also try contouring it at different levels, and turning opacity to ~0.5 or so. Chris _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. AIRBUS HELICOPTERS DEUTSCHLAND GmbH Sitz der Gesellschaft / Registered Office: Donauw?rth Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508 Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: Guillaume Faury Gesch?ftsf?hrung / Board of Management: Dr. Wolfgang Schoder, Vorsitzender / CEO; Johannes Kleidorfer; Dr. Klaus Przemeck; Oliver Schenzle; Martin Sch?bel; Stefan Thom? CONFIDENTIALITY NOTICE This communication and the information it contains is intended for the addressee ( s ) named above and for no other persons or organizations. It is confidential and may be legally privileged and protected by law. The unauthorized use, copying or disclosure of this communication or any part of it is prohibited and may be unlawful. If you have received this communication in error, kindly notify us by return e-mail and discard and/or delete the communication. Thank you very much. It is possible for e-mails to be intercepted or affected by viruses. Whilst we maintain virus checks on our e-mails, we accept no liability for viruses or other material which might be introduced with this message. -------------- next part -------------- A non-text attachment was scrubbed... Name: galaxy.jpg Type: image/jpeg Size: 230685 bytes Desc: galaxy.jpg URL: From logg at chalmers.se Fri Jun 26 07:31:33 2015 From: logg at chalmers.se (Anders Logg) Date: Fri, 26 Jun 2015 11:31:33 +0000 Subject: [Paraview] Visualize density (a galaxy of stars) In-Reply-To: References: <3378_1435306540_558D0A2C_3378_6994_15_0aae2421fe8830dccc8b1aa51cd70dcd@cam.ac.uk> Message-ID: Thanks for the good suggestions! I ended up going with the point cloud option. I'm very happy how it turned out: http://www.math.chalmers.se/~logg/tmp/vp_torus.avi Again, special thanks to Chris for pointing me to this option. -- Anders fre 26 juni 2015 kl 12:32 skrev Paluszek, Lukasz : > Hello Anders, > > I don't know what your expectations as to how sharp the image should be > are, but your data set is too coarse to obtain a sharper rendering. What I > suggest is that you either refine your mesh or you resample your data onto > a finer vti image and then do the volume rendering. I have attached a > picture with your original galaxy and a resampled one, perhaps this is what > you are looking for. I must admit though, that the left image looks more > "Hubble-like" :-). > > Regards, > Lukasz > > > > > > ?ukasz Paluszek > Airbus Helicopters > Aerodynamics Department (ETGA) > 86607 Donauw?rth > Germany > Tel.: +49 (90) 671 8231 > Fax.: +49 (90) 671 9122 > Lukasz.Paluszek at airbus.com > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Chris > Richardson > Sent: 26 June 2015 10:16 > To: Anders Logg > Cc: ParaView Mailing List > Subject: Re: [Paraview] Visualize density (a galaxy of stars) > > On 26/06/2015 08:36, Anders Logg wrote: > > Sure! > > > > http://www.math.chalmers.se/~logg/tmp/torus.vtu.gz [6] > > > > Ideally I would like to visualize this as a glowing torus-shaped > > galaxy in empty space. > > > > PS: A friend tipped me to visualize the data as a point cloud instead > > so I'm currently experimenting with sampling the density data to form > > a point cloud (outside of ParaView). This might be a better > > alternative than visualizing the density directly. > > > > You could also try contouring it at different levels, and turning opacity > to ~0.5 or so. > > Chris > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > This mail has originated outside your organization, either from an > external partner or the Global Internet. > Keep this in mind if you answer this message. > > > AIRBUS HELICOPTERS DEUTSCHLAND GmbH > Sitz der Gesellschaft / Registered Office: Donauw?rth > Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508 > Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: > Guillaume Faury > Gesch?ftsf?hrung / Board of Management: > Dr. Wolfgang Schoder, Vorsitzender / CEO; Johannes Kleidorfer; Dr. Klaus > Przemeck; Oliver Schenzle; Martin Sch?bel; Stefan Thom? > > > CONFIDENTIALITY NOTICE > > This communication and the information it contains is intended for the > addressee ( s ) named above and for no other persons or organizations. > It is confidential and may be legally privileged and protected by law. The > unauthorized use, copying or disclosure of this communication > or any part of it is prohibited and may be unlawful. > If you have received this communication in error, kindly notify us by > return e-mail and discard and/or delete the communication. > Thank you very much. > It is possible for e-mails to be intercepted or affected by viruses. > Whilst we maintain virus checks on our e-mails, we accept no liability for > viruses > or other material which might be introduced with this message. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Fri Jun 26 09:35:03 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Fri, 26 Jun 2015 09:35:03 -0400 Subject: [Paraview] problem in defining vtkStructuredGrid in MPI In-Reply-To: <35434.140.105.47.80.1435312725.squirrel@webmail.be.itu.edu.tr> References: <35434.140.105.47.80.1435312725.squirrel@webmail.be.itu.edu.tr> Message-ID: Do you have a node partitioning of your grid? If you do you really need a cell partitioning of the grid which will have multiple points a the partition overlap. Can you share your data? On Fri, Jun 26, 2015 at 5:58 AM, wrote: > Hi, > > I am trying to create structured grid in an MPI application and i am using > following C++ code to implement it > > extern "C" void createstgrid_(double* y, double* x, > int* nxstart, int* nxend, int* nystart, int* > nyend, > int* nx, int* ny, int* nz, int* mpiSize, > int* mpiRank) { > // > // Create structured grid > // > vtkSmartPointer sg = > vtkSmartPointer::New(); > sg->SetExtent (*nxstart-1, *nxend-1, *nystart-1, *nyend-1, 0, 0); > > // > // Create data structure to store grid coordinates > // > int pnx = ((*nxend)-(*nxstart))+1; > int pny = ((*nyend)-(*nystart))+1; > vtkSmartPointer points = vtkSmartPointer::New(); > > // > // Insert grid coordinate data as points > // > k = 0; > for (int j = 0; j < pny; j++) { > for (int i = 0; i < pnx; i++) { > points->InsertPoint(k, x[i+j*pnx], y[i+j*pnx], 0); > k = k+1; > } > } > sg->SetPoints(points); > > // > // Set grid > // > > vtkCPPythonAdaptorAPI::GetCoProcessorData()->GetInputDescriptionByName("input")->SetGrid(sg); > > vtkCPPythonAdaptorAPI::GetCoProcessorData()->GetInputDescriptionByName("input")->SetWholeExtent(0, > *nx-1, 0, *ny-1, 0, 0); > } > > so, when i run the code with grid writer, it creates the individual file > (*.vts) for each processor and one extra for the combination (*.pvts). > Anyway, the individual files looks fine in Paraview but if i open the file > with pvts extension, i am getting following error, > > ERROR: In > > /Users/turuncu/Qsync/progs/paraview-4.3.1/src/VTK/IO/XML/vtkXMLPStructuredDataReader.cxx, > line 461 > vtkXMLPStructuredGridReader (0x7f961c0910a0): No available piece provides > data for the following extents: > 0 140 0 1 0 0 > 0 1 1 58 0 0 > 0 140 58 59 0 0 > 0 1 59 114 0 0 > 71 72 1 58 0 0 > 71 72 59 114 0 0 > > The UpdateExtent cannot be filled. > > What is the meaning of this message? It means that some of the grid data > (or points) are not filled by the code. I also check the loop in the C++ > code and print out the number of points for each processor > > 0 number of points = 4118 > 1 number of points = 4047 > 2 number of points = 4060 > 3 number of points = 3990 > > and the total is 16215, which is consistent with the size of the grid but > if i check the individual vts files from the Paraview, the files shows > different number of points for each file > > 0 number of points = 4118 > 1 number of points = 3976 > 2 number of points = 4002 > 3 number of points = 3864 > > So, only first file matchs with the C++ code but others not. I am not sure > what is happening in there and if you have any suggestion that will be > great. > > Anyway, in this case i did not use vtkMultiBlockDataSet but after having > correct representation of the grid, i am planing use SetBlock method of > vtkMultiBlockDataSet to assign decomposition elements as individual > blocks. > > Regards, > > --ufuk > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Fri Jun 26 09:56:51 2015 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Fri, 26 Jun 2015 16:56:51 +0300 (EEST) Subject: [Paraview] problem in defining vtkStructuredGrid in MPI In-Reply-To: References: <35434.140.105.47.80.1435312725.squirrel@webmail.be.itu.edu.tr> Message-ID: <26352.140.105.47.80.1435327011.squirrel@webmail.be.itu.edu.tr> Hi, Thanks for your help. Actually, every processor has its own data and i am just using the interior regions (so, it does not overlap, no ghost or halo regions). Anyway, after my initial mail, i changed the SetExtent part of the code as sg->SetExtent (*nxstart-2, *nxend-2, *nystart-2, *nyend-2, 0, 0); because it was starting from 1 in each direction, now it starts from zero. This modification fixes the mismatch problem in the number of points comes from Paraview and seen in the C++ code. On the other hand, the Paraview still complains about the following extents (seems that the inner boundary of the 2 x 2 decomposition elements, like ghost region). 0 140 57 58 0 0 70 71 0 57 0 0 70 71 58 114 0 0 You can find the data in the attached file (data_00.tar.gz). Then, i tried to put the individual parts of the structured grid into the vtkMultiBlockDataSet using following code // // Create multi block grid // vtkMultiBlockDataSet* grid = vtkMultiBlockDataSet::New (); grid->SetNumberOfBlocks(*mpiSize); grid->SetBlock (*mpiRank, sg.GetPointer()); and write the grid information to the file (data_01.tar.gz). In this case, Paraview could open the *.vtm file without any message. So, i could not be sure about the grid. It seems fine if i look at multi block data file (vtm) but not in pvts file. Regards, --ufuk > Do you have a node partitioning of your grid? If you do you really need a > cell partitioning of the grid which will have multiple points a the > partition overlap. > > Can you share your data? > > On Fri, Jun 26, 2015 at 5:58 AM, wrote: > >> Hi, >> >> I am trying to create structured grid in an MPI application and i am >> using >> following C++ code to implement it >> >> extern "C" void createstgrid_(double* y, double* x, >> int* nxstart, int* nxend, int* nystart, >> int* >> nyend, >> int* nx, int* ny, int* nz, int* mpiSize, >> int* mpiRank) { >> // >> // Create structured grid >> // >> vtkSmartPointer sg = >> vtkSmartPointer::New(); >> sg->SetExtent (*nxstart-1, *nxend-1, *nystart-1, *nyend-1, 0, 0); >> >> // >> // Create data structure to store grid coordinates >> // >> int pnx = ((*nxend)-(*nxstart))+1; >> int pny = ((*nyend)-(*nystart))+1; >> vtkSmartPointer points = vtkSmartPointer::New(); >> >> // >> // Insert grid coordinate data as points >> // >> k = 0; >> for (int j = 0; j < pny; j++) { >> for (int i = 0; i < pnx; i++) { >> points->InsertPoint(k, x[i+j*pnx], y[i+j*pnx], 0); >> k = k+1; >> } >> } >> sg->SetPoints(points); >> >> // >> // Set grid >> // >> >> vtkCPPythonAdaptorAPI::GetCoProcessorData()->GetInputDescriptionByName("input")->SetGrid(sg); >> >> vtkCPPythonAdaptorAPI::GetCoProcessorData()->GetInputDescriptionByName("input")->SetWholeExtent(0, >> *nx-1, 0, *ny-1, 0, 0); >> } >> >> so, when i run the code with grid writer, it creates the individual file >> (*.vts) for each processor and one extra for the combination (*.pvts). >> Anyway, the individual files looks fine in Paraview but if i open the >> file >> with pvts extension, i am getting following error, >> >> ERROR: In >> >> /Users/turuncu/Qsync/progs/paraview-4.3.1/src/VTK/IO/XML/vtkXMLPStructuredDataReader.cxx, >> line 461 >> vtkXMLPStructuredGridReader (0x7f961c0910a0): No available piece >> provides >> data for the following extents: >> 0 140 0 1 0 0 >> 0 1 1 58 0 0 >> 0 140 58 59 0 0 >> 0 1 59 114 0 0 >> 71 72 1 58 0 0 >> 71 72 59 114 0 0 >> >> The UpdateExtent cannot be filled. >> >> What is the meaning of this message? It means that some of the grid data >> (or points) are not filled by the code. I also check the loop in the C++ >> code and print out the number of points for each processor >> >> 0 number of points = 4118 >> 1 number of points = 4047 >> 2 number of points = 4060 >> 3 number of points = 3990 >> >> and the total is 16215, which is consistent with the size of the grid >> but >> if i check the individual vts files from the Paraview, the files shows >> different number of points for each file >> >> 0 number of points = 4118 >> 1 number of points = 3976 >> 2 number of points = 4002 >> 3 number of points = 3864 >> >> So, only first file matchs with the C++ code but others not. I am not >> sure >> what is happening in there and if you have any suggestion that will be >> great. >> >> Anyway, in this case i did not use vtkMultiBlockDataSet but after having >> correct representation of the grid, i am planing use SetBlock method of >> vtkMultiBlockDataSet to assign decomposition elements as individual >> blocks. >> >> Regards, >> >> --ufuk >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: data_00.tar.gz Type: application/x-gzip Size: 140779 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: data_01.tar.gz Type: application/x-gzip Size: 140728 bytes Desc: not available URL: From andy.bauer at kitware.com Fri Jun 26 10:55:32 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Fri, 26 Jun 2015 10:55:32 -0400 Subject: [Paraview] problem in defining vtkStructuredGrid in MPI In-Reply-To: <26352.140.105.47.80.1435327011.squirrel@webmail.be.itu.edu.tr> References: <35434.140.105.47.80.1435312725.squirrel@webmail.be.itu.edu.tr> <26352.140.105.47.80.1435327011.squirrel@webmail.be.itu.edu.tr> Message-ID: If the output of the vtm is what you're looking for you won't be able to do that with the parallel XML structured grid writer because you have a node partition (i.e. nodes are uniquely assigned to a process and in this case no other process has that node). Thus the missing cells at the partition boundary are causing you problems with the pvts reader. With the multiblock data set my suggestion is to make the first block in that be a vtkMultiPieceDataSet and then add each process's structured grid as a piece to that. Then when you load it into ParaView it will behave much more uniformly. On Fri, Jun 26, 2015 at 9:56 AM, wrote: > Hi, > > Thanks for your help. Actually, every processor has its own data and i am > just using the interior regions (so, it does not overlap, no ghost or halo > regions). Anyway, after my initial mail, i changed the SetExtent part of > the code as > > sg->SetExtent (*nxstart-2, *nxend-2, *nystart-2, *nyend-2, 0, 0); > > because it was starting from 1 in each direction, now it starts from zero. > This modification fixes the mismatch problem in the number of points comes > from Paraview and seen in the C++ code. On the other hand, the Paraview > still complains about the following extents (seems that the inner boundary > of the 2 x 2 decomposition elements, like ghost region). > > 0 140 57 58 0 0 > 70 71 0 57 0 0 > 70 71 58 114 0 0 > > You can find the data in the attached file (data_00.tar.gz). > > Then, i tried to put the individual parts of the structured grid into the > vtkMultiBlockDataSet using following code > > // > // Create multi block grid > // > vtkMultiBlockDataSet* grid = vtkMultiBlockDataSet::New (); > grid->SetNumberOfBlocks(*mpiSize); > grid->SetBlock (*mpiRank, sg.GetPointer()); > > and write the grid information to the file (data_01.tar.gz). In this case, > Paraview could open the *.vtm file without any message. So, i could not be > sure about the grid. It seems fine if i look at multi block data file > (vtm) but not in pvts file. > > Regards, > > --ufuk > > > > Do you have a node partitioning of your grid? If you do you really need a > > cell partitioning of the grid which will have multiple points a the > > partition overlap. > > > > Can you share your data? > > > > On Fri, Jun 26, 2015 at 5:58 AM, > wrote: > > > >> Hi, > >> > >> I am trying to create structured grid in an MPI application and i am > >> using > >> following C++ code to implement it > >> > >> extern "C" void createstgrid_(double* y, double* x, > >> int* nxstart, int* nxend, int* nystart, > >> int* > >> nyend, > >> int* nx, int* ny, int* nz, int* mpiSize, > >> int* mpiRank) { > >> // > >> // Create structured grid > >> // > >> vtkSmartPointer sg = > >> vtkSmartPointer::New(); > >> sg->SetExtent (*nxstart-1, *nxend-1, *nystart-1, *nyend-1, 0, 0); > >> > >> // > >> // Create data structure to store grid coordinates > >> // > >> int pnx = ((*nxend)-(*nxstart))+1; > >> int pny = ((*nyend)-(*nystart))+1; > >> vtkSmartPointer points = vtkSmartPointer::New(); > >> > >> // > >> // Insert grid coordinate data as points > >> // > >> k = 0; > >> for (int j = 0; j < pny; j++) { > >> for (int i = 0; i < pnx; i++) { > >> points->InsertPoint(k, x[i+j*pnx], y[i+j*pnx], 0); > >> k = k+1; > >> } > >> } > >> sg->SetPoints(points); > >> > >> // > >> // Set grid > >> // > >> > >> > vtkCPPythonAdaptorAPI::GetCoProcessorData()->GetInputDescriptionByName("input")->SetGrid(sg); > >> > >> > vtkCPPythonAdaptorAPI::GetCoProcessorData()->GetInputDescriptionByName("input")->SetWholeExtent(0, > >> *nx-1, 0, *ny-1, 0, 0); > >> } > >> > >> so, when i run the code with grid writer, it creates the individual file > >> (*.vts) for each processor and one extra for the combination (*.pvts). > >> Anyway, the individual files looks fine in Paraview but if i open the > >> file > >> with pvts extension, i am getting following error, > >> > >> ERROR: In > >> > >> > /Users/turuncu/Qsync/progs/paraview-4.3.1/src/VTK/IO/XML/vtkXMLPStructuredDataReader.cxx, > >> line 461 > >> vtkXMLPStructuredGridReader (0x7f961c0910a0): No available piece > >> provides > >> data for the following extents: > >> 0 140 0 1 0 0 > >> 0 1 1 58 0 0 > >> 0 140 58 59 0 0 > >> 0 1 59 114 0 0 > >> 71 72 1 58 0 0 > >> 71 72 59 114 0 0 > >> > >> The UpdateExtent cannot be filled. > >> > >> What is the meaning of this message? It means that some of the grid data > >> (or points) are not filled by the code. I also check the loop in the C++ > >> code and print out the number of points for each processor > >> > >> 0 number of points = 4118 > >> 1 number of points = 4047 > >> 2 number of points = 4060 > >> 3 number of points = 3990 > >> > >> and the total is 16215, which is consistent with the size of the grid > >> but > >> if i check the individual vts files from the Paraview, the files shows > >> different number of points for each file > >> > >> 0 number of points = 4118 > >> 1 number of points = 3976 > >> 2 number of points = 4002 > >> 3 number of points = 3864 > >> > >> So, only first file matchs with the C++ code but others not. I am not > >> sure > >> what is happening in there and if you have any suggestion that will be > >> great. > >> > >> Anyway, in this case i did not use vtkMultiBlockDataSet but after having > >> correct representation of the grid, i am planing use SetBlock method of > >> vtkMultiBlockDataSet to assign decomposition elements as individual > >> blocks. > >> > >> Regards, > >> > >> --ufuk > >> > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > >> http://www.kitware.com/opensource/opensource.html > >> > >> Please keep messages on-topic and check the ParaView Wiki at: > >> http://paraview.org/Wiki/ParaView > >> > >> Search the list archives at: http://markmail.org/search/?q=ParaView > >> > >> Follow this link to subscribe/unsubscribe: > >> http://public.kitware.com/mailman/listinfo/paraview > >> > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Fri Jun 26 13:11:08 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 26 Jun 2015 17:11:08 +0000 Subject: [Paraview] [EXTERNAL] Re: Visualize density (a galaxy of stars) In-Reply-To: References: <3378_1435306540_558D0A2C_3378_6994_15_0aae2421fe8830dccc8b1aa51cd70dcd@cam.ac.uk> Message-ID: Very nice. I don?t think it will improve on what you are doing, but you may want to try adding a glyph filter. Then, change the glyph type to sphere, and make the spheres really small. You could then color the spheres by velocity or star age or star size or ... You could also make the spheres larger and/or smaller depending on a variable (star temperature?) Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Anders Logg Sent: Friday, June 26, 2015 5:32 AM To: Paluszek, Lukasz Cc: ParaView Mailing List Subject: [EXTERNAL] Re: [Paraview] Visualize density (a galaxy of stars) Thanks for the good suggestions! I ended up going with the point cloud option. I'm very happy how it turned out: http://www.math.chalmers.se/~logg/tmp/vp_torus.avi Again, special thanks to Chris for pointing me to this option. -- Anders fre 26 juni 2015 kl 12:32 skrev Paluszek, Lukasz >: Hello Anders, I don't know what your expectations as to how sharp the image should be are, but your data set is too coarse to obtain a sharper rendering. What I suggest is that you either refine your mesh or you resample your data onto a finer vti image and then do the volume rendering. I have attached a picture with your original galaxy and a resampled one, perhaps this is what you are looking for. I must admit though, that the left image looks more "Hubble-like" :-). Regards, Lukasz ?ukasz Paluszek Airbus Helicopters Aerodynamics Department (ETGA) 86607 Donauw?rth Germany Tel.: +49 (90) 671 8231 Fax.: +49 (90) 671 9122 Lukasz.Paluszek at airbus.com -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Chris Richardson Sent: 26 June 2015 10:16 To: Anders Logg Cc: ParaView Mailing List Subject: Re: [Paraview] Visualize density (a galaxy of stars) On 26/06/2015 08:36, Anders Logg wrote: > Sure! > > http://www.math.chalmers.se/~logg/tmp/torus.vtu.gz [6] > > Ideally I would like to visualize this as a glowing torus-shaped > galaxy in empty space. > > PS: A friend tipped me to visualize the data as a point cloud instead > so I'm currently experimenting with sampling the density data to form > a point cloud (outside of ParaView). This might be a better > alternative than visualizing the density directly. > You could also try contouring it at different levels, and turning opacity to ~0.5 or so. Chris _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. AIRBUS HELICOPTERS DEUTSCHLAND GmbH Sitz der Gesellschaft / Registered Office: Donauw?rth Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508 Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: Guillaume Faury Gesch?ftsf?hrung / Board of Management: Dr. Wolfgang Schoder, Vorsitzender / CEO; Johannes Kleidorfer; Dr. Klaus Przemeck; Oliver Schenzle; Martin Sch?bel; Stefan Thom? CONFIDENTIALITY NOTICE This communication and the information it contains is intended for the addressee ( s ) named above and for no other persons or organizations. It is confidential and may be legally privileged and protected by law. The unauthorized use, copying or disclosure of this communication or any part of it is prohibited and may be unlawful. If you have received this communication in error, kindly notify us by return e-mail and discard and/or delete the communication. Thank you very much. It is possible for e-mails to be intercepted or affected by viruses. Whilst we maintain virus checks on our e-mails, we accept no liability for viruses or other material which might be introduced with this message. -------------- next part -------------- An HTML attachment was scrubbed... URL: From logg at chalmers.se Fri Jun 26 13:22:00 2015 From: logg at chalmers.se (Anders Logg) Date: Fri, 26 Jun 2015 17:22:00 +0000 Subject: [Paraview] [EXTERNAL] Re: Visualize density (a galaxy of stars) In-Reply-To: <43776b57fc4f4eec8856313450fdea74@liara.ita.chalmers.se> References: <3378_1435306540_558D0A2C_3378_6994_15_0aae2421fe8830dccc8b1aa51cd70dcd@cam.ac.uk> <43776b57fc4f4eec8856313450fdea74@liara.ita.chalmers.se> Message-ID: Good idea, I tried it just now. It didn't seem to improve much over the 1-pixel dots I used before but this technique may come in handy later - thanks! -- Anders fre 26 juni 2015 kl 19:11 skrev Scott, W Alan : > Very nice. > > > > I don?t think it will improve on what you are doing, but you may want to > try adding a glyph filter. Then, change the glyph type to sphere, and make > the spheres really small. You could then color the spheres by velocity or > star age or star size or ... You could also make the spheres larger and/or > smaller depending on a variable (star temperature?) > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *Anders > Logg > *Sent:* Friday, June 26, 2015 5:32 AM > *To:* Paluszek, Lukasz > *Cc:* ParaView Mailing List > *Subject:* [EXTERNAL] Re: [Paraview] Visualize density (a galaxy of stars) > > > > Thanks for the good suggestions! I ended up going with the point cloud > option. I'm very happy how it turned out: > > > > http://www.math.chalmers.se/~logg/tmp/vp_torus.avi > > > > Again, special thanks to Chris for pointing me to this option. > > > > -- > > Anders > > > > fre 26 juni 2015 kl 12:32 skrev Paluszek, Lukasz < > lukasz.paluszek at airbus.com>: > > Hello Anders, > > I don't know what your expectations as to how sharp the image should be > are, but your data set is too coarse to obtain a sharper rendering. What I > suggest is that you either refine your mesh or you resample your data onto > a finer vti image and then do the volume rendering. I have attached a > picture with your original galaxy and a resampled one, perhaps this is what > you are looking for. I must admit though, that the left image looks more > "Hubble-like" :-). > > Regards, > Lukasz > > > > > > ?ukasz Paluszek > Airbus Helicopters > Aerodynamics Department (ETGA) > 86607 Donauw?rth > Germany > Tel.: +49 (90) 671 8231 > Fax.: +49 (90) 671 9122 > Lukasz.Paluszek at airbus.com > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Chris > Richardson > Sent: 26 June 2015 10:16 > To: Anders Logg > Cc: ParaView Mailing List > Subject: Re: [Paraview] Visualize density (a galaxy of stars) > > On 26/06/2015 08:36, Anders Logg wrote: > > Sure! > > > > http://www.math.chalmers.se/~logg/tmp/torus.vtu.gz [6] > > > > Ideally I would like to visualize this as a glowing torus-shaped > > galaxy in empty space. > > > > PS: A friend tipped me to visualize the data as a point cloud instead > > so I'm currently experimenting with sampling the density data to form > > a point cloud (outside of ParaView). This might be a better > > alternative than visualizing the density directly. > > > > You could also try contouring it at different levels, and turning opacity > to ~0.5 or so. > > Chris > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > This mail has originated outside your organization, either from an > external partner or the Global Internet. > Keep this in mind if you answer this message. > > > AIRBUS HELICOPTERS DEUTSCHLAND GmbH > Sitz der Gesellschaft / Registered Office: Donauw?rth > Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508 > Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: > Guillaume Faury > Gesch?ftsf?hrung / Board of Management: > Dr. Wolfgang Schoder, Vorsitzender / CEO; Johannes Kleidorfer; Dr. Klaus > Przemeck; Oliver Schenzle; Martin Sch?bel; Stefan Thom? > > > CONFIDENTIALITY NOTICE > > This communication and the information it contains is intended for the > addressee ( s ) named above and for no other persons or organizations. > It is confidential and may be legally privileged and protected by law. The > unauthorized use, copying or disclosure of this communication > or any part of it is prohibited and may be unlawful. > If you have received this communication in error, kindly notify us by > return e-mail and discard and/or delete the communication. > Thank you very much. > It is possible for e-mails to be intercepted or affected by viruses. > Whilst we maintain virus checks on our e-mails, we accept no liability for > viruses > or other material which might be introduced with this message. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Fri Jun 26 14:50:47 2015 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Fri, 26 Jun 2015 21:50:47 +0300 (EEST) Subject: [Paraview] problem in defining vtkStructuredGrid in MPI In-Reply-To: References: <35434.140.105.47.80.1435312725.squirrel@webmail.be.itu.edu.tr> <26352.140.105.47.80.1435327011.squirrel@webmail.be.itu.edu.tr> Message-ID: <33263.5.170.210.33.1435344647.squirrel@webmail.be.itu.edu.tr> Hi, Thanks for your suggestion. I did it as follows, vtkMultiBlockDataSet* grid = vtkMultiBlockDataSet::New(); vtkNew mpds; mpds->SetNumberOfPieces(*mpiSize); mpds->SetPiece(*mpiRank, sg.GetPointer()); grid->SetNumberOfBlocks(1); grid->SetBlock(0, mpds.GetPointer()); so, there is one block that has each partition in a vtkMultiPieceDataSet. Thanks again. Regards, --ufuk > If the output of the vtm is what you're looking for you won't be able to > do > that with the parallel XML structured grid writer because you have a node > partition (i.e. nodes are uniquely assigned to a process and in this case > no other process has that node). Thus the missing cells at the partition > boundary are causing you problems with the pvts reader. > > With the multiblock data set my suggestion is to make the first block in > that be a vtkMultiPieceDataSet and then add each process's structured grid > as a piece to that. Then when you load it into ParaView it will behave > much > more uniformly. > > > > On Fri, Jun 26, 2015 at 9:56 AM, wrote: > >> Hi, >> >> Thanks for your help. Actually, every processor has its own data and i >> am >> just using the interior regions (so, it does not overlap, no ghost or >> halo >> regions). Anyway, after my initial mail, i changed the SetExtent part of >> the code as >> >> sg->SetExtent (*nxstart-2, *nxend-2, *nystart-2, *nyend-2, 0, 0); >> >> because it was starting from 1 in each direction, now it starts from >> zero. >> This modification fixes the mismatch problem in the number of points >> comes >> from Paraview and seen in the C++ code. On the other hand, the Paraview >> still complains about the following extents (seems that the inner >> boundary >> of the 2 x 2 decomposition elements, like ghost region). >> >> 0 140 57 58 0 0 >> 70 71 0 57 0 0 >> 70 71 58 114 0 0 >> >> You can find the data in the attached file (data_00.tar.gz). >> >> Then, i tried to put the individual parts of the structured grid into >> the >> vtkMultiBlockDataSet using following code >> >> // >> // Create multi block grid >> // >> vtkMultiBlockDataSet* grid = vtkMultiBlockDataSet::New (); >> grid->SetNumberOfBlocks(*mpiSize); >> grid->SetBlock (*mpiRank, sg.GetPointer()); >> >> and write the grid information to the file (data_01.tar.gz). In this >> case, >> Paraview could open the *.vtm file without any message. So, i could not >> be >> sure about the grid. It seems fine if i look at multi block data file >> (vtm) but not in pvts file. >> >> Regards, >> >> --ufuk >> >> >> > Do you have a node partitioning of your grid? If you do you really >> need a >> > cell partitioning of the grid which will have multiple points a the >> > partition overlap. >> > >> > Can you share your data? >> > >> > On Fri, Jun 26, 2015 at 5:58 AM, >> wrote: >> > >> >> Hi, >> >> >> >> I am trying to create structured grid in an MPI application and i am >> >> using >> >> following C++ code to implement it >> >> >> >> extern "C" void createstgrid_(double* y, double* x, >> >> int* nxstart, int* nxend, int* nystart, >> >> int* >> >> nyend, >> >> int* nx, int* ny, int* nz, int* >> mpiSize, >> >> int* mpiRank) { >> >> // >> >> // Create structured grid >> >> // >> >> vtkSmartPointer sg = >> >> vtkSmartPointer::New(); >> >> sg->SetExtent (*nxstart-1, *nxend-1, *nystart-1, *nyend-1, 0, 0); >> >> >> >> // >> >> // Create data structure to store grid coordinates >> >> // >> >> int pnx = ((*nxend)-(*nxstart))+1; >> >> int pny = ((*nyend)-(*nystart))+1; >> >> vtkSmartPointer points = >> vtkSmartPointer::New(); >> >> >> >> // >> >> // Insert grid coordinate data as points >> >> // >> >> k = 0; >> >> for (int j = 0; j < pny; j++) { >> >> for (int i = 0; i < pnx; i++) { >> >> points->InsertPoint(k, x[i+j*pnx], y[i+j*pnx], 0); >> >> k = k+1; >> >> } >> >> } >> >> sg->SetPoints(points); >> >> >> >> // >> >> // Set grid >> >> // >> >> >> >> >> vtkCPPythonAdaptorAPI::GetCoProcessorData()->GetInputDescriptionByName("input")->SetGrid(sg); >> >> >> >> >> vtkCPPythonAdaptorAPI::GetCoProcessorData()->GetInputDescriptionByName("input")->SetWholeExtent(0, >> >> *nx-1, 0, *ny-1, 0, 0); >> >> } >> >> >> >> so, when i run the code with grid writer, it creates the individual >> file >> >> (*.vts) for each processor and one extra for the combination >> (*.pvts). >> >> Anyway, the individual files looks fine in Paraview but if i open the >> >> file >> >> with pvts extension, i am getting following error, >> >> >> >> ERROR: In >> >> >> >> >> /Users/turuncu/Qsync/progs/paraview-4.3.1/src/VTK/IO/XML/vtkXMLPStructuredDataReader.cxx, >> >> line 461 >> >> vtkXMLPStructuredGridReader (0x7f961c0910a0): No available piece >> >> provides >> >> data for the following extents: >> >> 0 140 0 1 0 0 >> >> 0 1 1 58 0 0 >> >> 0 140 58 59 0 0 >> >> 0 1 59 114 0 0 >> >> 71 72 1 58 0 0 >> >> 71 72 59 114 0 0 >> >> >> >> The UpdateExtent cannot be filled. >> >> >> >> What is the meaning of this message? It means that some of the grid >> data >> >> (or points) are not filled by the code. I also check the loop in the >> C++ >> >> code and print out the number of points for each processor >> >> >> >> 0 number of points = 4118 >> >> 1 number of points = 4047 >> >> 2 number of points = 4060 >> >> 3 number of points = 3990 >> >> >> >> and the total is 16215, which is consistent with the size of the grid >> >> but >> >> if i check the individual vts files from the Paraview, the files >> shows >> >> different number of points for each file >> >> >> >> 0 number of points = 4118 >> >> 1 number of points = 3976 >> >> 2 number of points = 4002 >> >> 3 number of points = 3864 >> >> >> >> So, only first file matchs with the C++ code but others not. I am not >> >> sure >> >> what is happening in there and if you have any suggestion that will >> be >> >> great. >> >> >> >> Anyway, in this case i did not use vtkMultiBlockDataSet but after >> having >> >> correct representation of the grid, i am planing use SetBlock method >> of >> >> vtkMultiBlockDataSet to assign decomposition elements as individual >> >> blocks. >> >> >> >> Regards, >> >> >> >> --ufuk >> >> >> >> _______________________________________________ >> >> Powered by www.kitware.com >> >> >> >> Visit other Kitware open-source projects at >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> Please keep messages on-topic and check the ParaView Wiki at: >> >> http://paraview.org/Wiki/ParaView >> >> >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> > >> > From wascott at sandia.gov Fri Jun 26 19:57:34 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 26 Jun 2015 23:57:34 +0000 Subject: [Paraview] [EXTERNAL] ParaView 4.4 ?? In-Reply-To: <55791E65.9000105@gmail.com> References: <55791E65.9000105@gmail.com> Message-ID: <315228b31d3b4c18977cc849ac5b5431@ES01AMSNLNT.srn.sandia.gov> Michael, I am cleaning up e-mails, and found yours. I don't think it was answered. Currently the ParaView/Kitware team are working on the next release. This release should go out late this summer (but looking at the bug list, could be very early fall). Kitware is working to update OpenGL - if this back end work is ready for the release, it will very likely be named ParaView 5.0. If it doesn't get in, the release will be called ParaView 4.4. Utkarsh's excellent posts on the Kitware blog will give you an idea what is coming. Two new features that my users consider "game changing" (and I can't wait to mention) are the ability to select nearest point (no need to rubber band select) and interactive selection (allowing you to turn on cell or point labels, and see the data in real time without mouse and keyboard clicks). This will be a nice, powerful release. Alan -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Mickael Philit Sent: Wednesday, June 10, 2015 11:37 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] ParaView 4.4 ?? Dear all, I just came across this interesting webpage: http://www.paraview.org/ParaView/index.php/ParaView_4.4_Deliverables and I would like to know if there is a release schedule for ParaView 4.4. Best regards Mickael _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From hahnse at ornl.gov Mon Jun 29 18:06:10 2015 From: hahnse at ornl.gov (Hahn, Steven E.) Date: Mon, 29 Jun 2015 22:06:10 +0000 Subject: [Paraview] Volume rendering on OS X with Nvidia graphics card In-Reply-To: References: Message-ID: I am observing some odd results with volume rendering using ParaView 4.3.1 and ParaView master on OS X machines with NVIDIA graphics cards including a Geforce 650m in a macbook pro and a Quadro K5000 in a mac pro. On the mac pro, changing between the NVIDIA web driver and OS X default driver has no effect. 1) After loading a vtkImageData file and selecting the volume representation and the GPU based volume rendering mode, the image disappears. The other volume rendering modes show the image correctly. I also tried building ParaView master with the OpenGL2 rendering backend and in that case the GPU based volume rendering mode displays only some of the surfaces (2-4, the exact number depends on the camera position) and not the entire volume. 2) I also tried loading a small vtkStructuredGrid (attached) into ParaView master built with the OpenGL2 rendering backend and get the warning below. There are substantial artifacts that are not present when the OpenGL rendering backend is used. These artifacts don't appear when I load the same file in ParaView 4.3.1 or ParaView master build with the OpenGL rendering backend. Warning: In ../VTK/Rendering/VolumeOpenGL2/vtkOpenGLProjectedTetrahedraMapper.cxx, line 151 vtkOpenGLProjectedTetrahedraMapper (0x7fdc49d3a140): Missing FBO support. The algorithm may produce visual artifacts. I tried running glxinfo and under OpenGL extensions it does list GL_ARB_framebuffer_object, GL_ARB_draw_buffers and GL_ARB_texture_float. VTK, however, doesn't appear to be detecting this. Sincerely, Steven Hahn -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: hexagonal_cell.vts Type: application/octet-stream Size: 7385 bytes Desc: hexagonal_cell.vts URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: volume_rendering.jpg Type: image/jpeg Size: 49273 bytes Desc: volume_rendering.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: volume_rendering_artifacts.jpg Type: image/jpeg Size: 56260 bytes Desc: volume_rendering_artifacts.jpg URL: From cory.quammen at kitware.com Mon Jun 29 23:00:46 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 29 Jun 2015 23:00:46 -0400 Subject: [Paraview] [Paraview-developers] Volume calculation cloud points In-Reply-To: <1435587620865-3852.post@n6.nabble.com> References: <1435587620865-3852.post@n6.nabble.com> Message-ID: Hi Laura, Delaunay 3D should give you what you want in terms of volume of the convex hull of the points. How do you know the volumes and distances are not correct? What are you expecting and what are you getting? By the way, this is a question more appropriate for the ParaView Users list, so I have replied to it instead of the ParaView Developers list. Thanks, Cory On Mon, Jun 29, 2015 at 10:20 AM, Laura Masse wrote: > Hi all, > > I have a doubt about distances and volumes with my 3d image and I hope > anyone can help me. > > My 3d image is composed by about 8000 points, the shape is more or less > like > a half sphere, (see image below) > > I would like to calculate the volume, so If I apply the "Delaunay3D" and > "integrated variables" Filters the volume I get is not correct. > > In the same way if I try to measure distances with the Source Ruler the > distances I get are wrong. > > I think I'm doing something wrong but I don?t know what. > > Anyone knows some method to do this ? > > Advanced thanks > > < > http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/file/n3852/Imagen1.jpg > > > > > > -- > View this message in context: > http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/Volume-calculation-cloud-points-tp3852.html > Sent from the The Unofficial ParaView Developers Forum mailing list > archive at Nabble.com. > _______________________________________________ > 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 > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Jun 30 00:08:00 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 30 Jun 2015 00:08:00 -0400 Subject: [Paraview] Fwd: How to plug into paraview his own writer ? In-Reply-To: <86347d91c723cd90b081325c08b678ec@imap.ipgp.fr> References: <86347d91c723cd90b081325c08b678ec@imap.ipgp.fr> Message-ID: Hi Franck, It looks like you've been making progress, so I'll answer your questions from your second email. > Question 1 : how to write myWriter.xml ? > > 1.1. seems I must set name="Input"> in myWriter.xml. Does this means I will also have to > implement myWriter::SetInputConnection ? > No. Your writer will inherit from subclass of vtkAlgorithm, the class that defines "SetInputConnection", and you should not need to override it. XdmfWriter inherits from vtkDataObjectAlgorithm, which itself inherits vtkAlgorithm. > > 1.2. seems I must set command="SetFileName"> in myWriter.xml. Does this means I will also have to > implement myWriter::SetFileName ? > Yes, like vtkXdmfWriter. > Question 2 : how to implement a vtk object ? From here > http://www.vtk.org/Wiki/VTK/Examples/Developers/vtkObject, it seems that > > 2.1. in myWriter.cpp, I need to have : > #include "vtkObjectFactory.h" // vtkStandardNewMacro > vtkStandardNewMacro ( myWriter ); // use vtkStandardNewMacro : 1 only > allowed constructor, omit the copy constructor and operator= > + suppress copy constructor and operator= > Yes. 2.2 in myWriter.hpp, I need to derive from a vtkObject this way (like > XdmfWriter.cpp does) : > class myWriter : public vtkDataObjectAlgorithm { > public: > static myWriter * New (); // Needed to be plugged into paraview > vtkTypeMacro ( myWriter, vtkDataObjectAlgorithm ); // Needed to be > plugged into paraview > + suppress copy constructor and operator= > > Am I correct ? > Yes. Question 3 : in myWriter.cpp, on which method I am supposed to be called > back (to get focus back) when I click the "save data" button ? Here, how > can I get data to be saved (data that I can see in paraview viewer before > to click the save button - I guess this data will be a vtk*). > In ParaView, when you choose, File -> Save Data, the data from the selected Pipeline Browser object will be saved. This will have some kind of data type, e.g., vtkImageData, vtkPolyData, etc. What kind of data type would you like your writer to support? The data should be available in the member function myWriter::RequestData(). This is where you should write your data. Finally, myWriter.xml seems OK. myWriter.*pp compile OK. Paraview finds > myWriter.xml at run time (exporting PV_PLUGIN_PATH) and loads > libmywriter.so without problem. I see the writer in the "save data" GUI > (drop down list with different save formats). I save with myWriter, I get a > (basic) GUI with file name only (no extra parameter) : I crash when I click > "OK, save" with this error message : > ERROR: In > /.../ParaView-v4.3.1-source/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, > line 307 > vtkSIWriterProxy (0x30143d0): Failed to create myWriter. Aborting for > debugging purposes. > > vtkSIWriterProxy does this at line 303 : > vtkObjectBase* obj = this->Interpreter->NewInstance(className); > but obj is NULL. > > I get obj is NULL because I missed something in myWriter implementation : > what did I miss ? > Are you running pvserver separately and connecting to it with the client? If so, make sure PV_PLUGIN_PATH is defined in the environment in which pvserver is run. Have you tried to load your plugin through the Tools -> Manage Plugins... dialog? I hope that helps get you further in writing your data files. Thanks, Cory > > Can somebody help ? Or even get me some clue ? > > FH > > -------- Message original -------- > Objet: How to plug into paraview his own writer ? > Date: 2015-06-12 15:54 > De: houssen > ?: > > > I followed 2 tutorials ( > http://www.itk.org/Wiki/ParaView/Plugin_HowTo#Writing_Plugins, > http://www.kitware.com/media/html/WritingAParaViewReaderPlug-in.html) but > I feel like I missed some steps : this is not working. > > I need to "catch" data (I can see in 2D/3D paraview viewer) to write them > into a specific file format. I am looking for the minimal (simplest) way to > do this : the only writer input is the file name, then I would like to > understand how to "get data from" paraview (from inside a vtk object I > guess ?), then I just will have to do the easy part which is to write data > to a specific format. > > My understanding is that, first I need a CMakeLists.txt like : > ~> more CMakeLists.txt > FIND_PACKAGE ( ParaView REQUIRED ) > INCLUDE ( ${PARAVIEW_USE_FILE} ) > ADD_PARAVIEW_PLUGIN ( myWriter "1.0" SERVER_MANAGER_XML myWriter.xml > SERVER_MANAGER_SOURCES myWriter.cpp ) > > In the same directory, I need a (minimal) myWriter.xml file that looks > like : > ~> more myWrite.xml > > > > > > number_of_elements="1"/> > > > > > > > > My understanding is that somehow the xml subscribes my for a specific > callback I am called back on the "save data" button is cliked in the GUI. > > Still, in this same directory, I have myWriter.cpp and myWriter.hpp : > how to implement them ? > 1. The myWriter class must define and implement a SetFileName method > because of the xml tag in myWriter.xml : right ? > wrong ? > This is the file name (including file path) one sets in the GUI : right > ? wrong ? > 2. myWriter is supposed to derive from another class : which one ? where > to find it ? > 3. How the myWriter implementation will "catch" data in paraview ? Which > method to override / re-implement ? > When I am called from paraview (triggered by the click on "save data" > button), I guess I am called on a specific method "myWriter::cbMethod ( > vtkXXX * pDataInParaviewViewer )" > What is this method ? > > Also, at this step, I export > PV_PLUGIN_PATH=/mnt/users/houssen/Documents/solve-rel/paraview. When I run > paraview and use the "save data" button I get this : > Generic Warning: In > /.../Programs/ParaView/ParaView-v4.3.1-source/ParaViewCore/ServerManager/Core/vtkSMWriterFactory.cxx, > line 135 > writers : myWriter has no input property. > ... But I have an tag in the xml : what's wrong ? > > Can somebody help me on this ? > > Franck > > Note : I run Ubuntu and paraview-4.3 > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Jun 30 00:20:09 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 30 Jun 2015 00:20:09 -0400 Subject: [Paraview] Changing the "solid color" to white for screenshots and exporting In-Reply-To: <5E9FE600-EDB4-49C5-B800-38816B8CA2CF@uvm.edu> References: <5E9FE600-EDB4-49C5-B800-38816B8CA2CF@uvm.edu> Message-ID: Ryan, I thought this would be straight forward but it does not seem to be. I > want to basically just get a picture of my grid with no background and a > few contours which are lines. To do this i?m trying to set the the color > of the default ?Solid Color? to white. No matter what i do it?s always > grey or off white in the view port and when i print it. When you set your object to white, it is still being rendered with lighting, hence the gray surface. > I?ve come close by using wireframe but that makes my grid look weird (some > lines are wider than others for some reason). Is there a way to do this > with surface with edges? That representation of my grid actually looks > like a grid. > In Wireframe representation, you all the lines should be the same width. If that's not the case, it is a bug. Can you post a picture showing the different line widths? Thanks, Cory > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Jun 30 00:21:16 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 30 Jun 2015 00:21:16 -0400 Subject: [Paraview] segfault playing a simulation In-Reply-To: <55895735.2030202@gmail.com> References: <55895735.2030202@gmail.com> Message-ID: Hi Sergi, Could you clarify when you are seeing this crash? Is it right when starting ParaView or when first loading a data set? Thanks, Cory On Tue, Jun 23, 2015 at 8:55 AM, Sergi Mateo Bellido < sergi.mateo.bellido at gmail.com> wrote: > Hi, > > I'm trying to reproduce a simulation with ParaView 4.3.1 and it always > crashes when I start it. You can find the backtrace below: > > ========================================================= > Process id 6681 Caught SIGSEGV at 0x925b124 address not mapped to object > Program Stack: > WARNING: The stack trace will not use advanced capabilities because this > is a release build. > 0x7f54ce081d40 : ??? [(???) ???:-1] > 0x7f54ce19caf6 : ??? [(???) ???:-1] > 0x7f54cb123736 : vtkXMLPStructuredDataReader::CopySubExtent(int*, int*, > long long*, int*, int*, long long*, int*, int*, vtkDataArray*, > vtkDataArray*) [(libvtkIOXML-pv4.3.so.1) ???:-1] > 0x7f54cb12389f : > vtkXMLPStructuredDataReader::CopyArrayForPoints(vtkDataArray*, > vtkDataArray*) [(libvtkIOXML-pv4.3.so.1) ???:-1] > 0x7f54cb11cc1f : vtkXMLPDataReader::ReadPieceData() > [(libvtkIOXML-pv4.3.so.1) ???:-1] > 0x7f54cb11ca14 : vtkXMLPDataReader::ReadPieceData(int) > [(libvtkIOXML-pv4.3.so.1) ???:-1] > 0x7f54cb124d7a : vtkXMLPStructuredDataReader::ReadXMLData() > [(libvtkIOXML-pv4.3.so.1) ???:-1] > 0x7f54cb1280eb : vtkXMLReader::RequestData(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) [(libvtkIOXML-pv4.3.so.1) > ???:-1] > 0x7f54cb1273b6 : vtkXMLReader::ProcessRequest(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) [(libvtkIOXML-pv4.3.so.1) > ???:-1] > 0x7f54cd6200f9 : vtkFileSeriesReader::RequestData(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) > [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1] > 0x7f54cd61f07f : vtkFileSeriesReader::ProcessRequest(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) > [(libvtkPVVTKExtensionsDefault-pv4.3.so.1) ???:-1] > 0x7f54d2706204 : vtkExecutive::CallAlgorithm(vtkInformation*, int, > vtkInformationVector**, vtkInformationVector*) > [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] > 0x7f54d27016cc : vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) > [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] > 0x7f54d2700201 : vtkCompositeDataPipeline::ExecuteData(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) > [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] > 0x7f54d2704067 : vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) > [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] > 0x7f54d271d959 : > vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) > [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] > 0x7f54d26fe387 : > vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) > [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] > 0x7f54d2704010 : vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) > [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] > 0x7f54d271d959 : > vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) > [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] > 0x7f54d26fe387 : > vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) > [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] > 0x7f54d2704010 : vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) > [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] > 0x7f54d271d959 : > vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) > [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] > 0x7f54d27035ae : vtkDemandDrivenPipeline::UpdateData(int) > [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] > 0x7f54d271e87f : vtkStreamingDemandDrivenPipeline::Update(int) > [(libvtkCommonExecutionModel-pv4.3.so.1) ???:-1] > 0x7f54cd98fa7f : > vtkPVDataRepresentation::ProcessViewRequest(vtkInformationRequestKey*, > vtkInformation*, vtkInformation*) > [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1] > 0x7f54cd973d79 : > vtkGeometryRepresentation::ProcessViewRequest(vtkInformationRequestKey*, > vtkInformation*, vtkInformation*) > [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1] > 0x7f54cd975d71 : > vtkGeometryRepresentationWithFaces::ProcessViewRequest(vtkInformationRequestKey*, > vtkInformation*, vtkInformation*) > [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1] > 0x7f54cd9bd388 : > vtkPVView::CallProcessViewRequest(vtkInformationRequestKey*, > vtkInformation*, vtkInformationVector*) > [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1] > 0x7f54cd9bd552 : vtkPVView::Update() > [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1] > 0x7f54cd9acb78 : vtkPVRenderView::Update() > [(libvtkPVClientServerCoreRendering-pv4.3.so.1) ???:-1] > 0x7f54d780ac30 : vtkPVRenderViewCommand(vtkClientServerInterpreter*, > vtkObjectBase*, char const*, vtkClientServerStream const&, > vtkClientServerStream&, void*) > [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1] > 0x7f54d4e135e0 : vtkClientServerInterpreter::CallCommandFunction(char > const*, vtkObjectBase*, char const*, vtkClientServerStream const&, > vtkClientServerStream&) [(libvtkClientServer-pv4.3.so.1) ???:-1] > 0x7f54d4e18393 : > vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream > const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1] > 0x7f54d4e16832 : > vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, > int) [(libvtkClientServer-pv4.3.so.1) ???:-1] > 0x7f54d4e16ced : > vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) > [(libvtkClientServer-pv4.3.so.1) ???:-1] > 0x7f54d5b26cec : > vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) > [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] > 0x7f54d5b26958 : vtkPVSessionCore::ExecuteStream(unsigned int, > vtkClientServerStream const&, bool) > [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] > 0x7f54d5b25203 : vtkPVSessionBase::ExecuteStream(unsigned int, > vtkClientServerStream const&, bool) > [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] > 0x7f54cdcae44f : vtkSMViewProxy::Update() > [(libvtkPVServerManagerRendering-pv4.3.so.1) ???:-1] > 0x7f54cdf2f6f7 : vtkSMAnimationScene::TickInternal(double, double, double) > [(libvtkPVAnimation-pv4.3.so.1) ???:-1] > 0x7f54cf415cab : vtkAnimationCue::Tick(double, double, double) > [(libvtkCommonCore-pv4.3.so.1) ???:-1] > 0x7f54cdf23268 : vtkAnimationPlayer::Play() > [(libvtkPVAnimation-pv4.3.so.1) ???:-1] > 0x7f54d7851619 : vtkSMAnimationSceneCommand(vtkClientServerInterpreter*, > vtkObjectBase*, char const*, vtkClientServerStream const&, > vtkClientServerStream&, void*) > [(libvtkPVServerManagerApplication-pv4.3.so.1) ???:-1] > 0x7f54d4e135e0 : vtkClientServerInterpreter::CallCommandFunction(char > const*, vtkObjectBase*, char const*, vtkClientServerStream const&, > vtkClientServerStream&) [(libvtkClientServer-pv4.3.so.1) ???:-1] > 0x7f54d4e18393 : > vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream > const&, int) [(libvtkClientServer-pv4.3.so.1) ???:-1] > 0x7f54d4e16832 : > vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, > int) [(libvtkClientServer-pv4.3.so.1) ???:-1] > 0x7f54d4e16ced : > vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) > [(libvtkClientServer-pv4.3.so.1) ???:-1] > 0x7f54d5b436d4 : vtkSIProperty::ProcessMessage(vtkClientServerStream&) > [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] > 0x7f54d5b4377e : vtkSIProperty::Push(paraview_protobuf::Message*, int) > [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] > 0x7f54d5b4459e : vtkSIProxy::Push(paraview_protobuf::Message*) > [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] > 0x7f54d5b2884a : > vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*) > [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] > 0x7f54d5b27484 : vtkPVSessionCore::PushState(paraview_protobuf::Message*) > [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] > 0x7f54d5b2514d : vtkPVSessionBase::PushState(paraview_protobuf::Message*) > [(libvtkPVServerImplementationCore-pv4.3.so.1) ???:-1] > 0x7f54d5d859b7 : vtkSMProxy::UpdateProperty(char const*, int) > [(libvtkPVServerManagerCore-pv4.3.so.1) ???:-1] > 0x7f54d6d8aa07 : pqVCRController::onPlay() > [(libvtkpqComponents-pv4.3.so.1) ???:-1] > 0x7f54cfa98258 : QMetaObject::activate(QObject*, QMetaObject const*, int, > void**) [(libQtCore.so.4) ???:-1] > 0x7f54d01102f2 : QAction::triggered(bool) [(libQtGui.so.4) ???:-1] > 0x7f54d0111710 : QAction::activate(QAction::ActionEvent) [(libQtGui.so.4) > ???:-1] > 0x7f54d04fd514 : ??? [(???) ???:-1] > 0x7f54d04fd7ab : QAbstractButton::mouseReleaseEvent(QMouseEvent*) > [(libQtGui.so.4) ???:-1] > 0x7f54d05d15ea : QToolButton::mouseReleaseEvent(QMouseEvent*) > [(libQtGui.so.4) ???:-1] > 0x7f54d0175ac1 : QWidget::event(QEvent*) [(libQtGui.so.4) ???:-1] > 0x7f54d04fca3f : QAbstractButton::event(QEvent*) [(libQtGui.so.4) ???:-1] > 0x7f54d05d422d : QToolButton::event(QEvent*) [(libQtGui.so.4) ???:-1] > 0x7f54d011759e : QApplicationPrivate::notify_helper(QObject*, QEvent*) > [(libQtGui.so.4) ???:-1] > 0x7f54d011e533 : QApplication::notify(QObject*, QEvent*) [(libQtGui.so.4) > ???:-1] > 0x7f54cfa802f3 : QCoreApplication::notifyInternal(QObject*, QEvent*) > [(libQtCore.so.4) ???:-1] > 0x7f54d011a656 : QApplicationPrivate::sendMouseEvent(QWidget*, > QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) > [(libQtGui.so.4) ???:-1] > 0x7f54d019ca94 : ??? [(???) ???:-1] > 0x7f54d019b877 : QApplication::x11ProcessEvent(_XEvent*) [(libQtGui.so.4) > ???:-1] > 0x7f54d01c4805 : ??? [(???) ???:-1] > 0x7f54cfa7f375 : > QEventLoop::processEvents(QFlags) > [(libQtCore.so.4) ???:-1] > 0x7f54cfa7f748 : QEventLoop::exec(QFlags) > [(libQtCore.so.4) ???:-1] > 0x7f54cfa8414b : QCoreApplication::exec() [(libQtCore.so.4) ???:-1] > 0x407785 : main [(paraview) ???:-1] > 0x7f54ce06cec5 : __libc_start_main [(libc.so.6) ???:-1] > 0x4074da : QMainWindow::event(QEvent*) [(paraview) ???:-1] > ========================================================= > > Thanks, > > Sergi Mateo > sergi.mateo.bellido at gmail.com > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Jun 30 00:26:56 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 30 Jun 2015 00:26:56 -0400 Subject: [Paraview] applying triangulation filter for .inp and .prt file extensions In-Reply-To: References: Message-ID: Hi Bharathi, I'm not sure that ParaView can open these kinds of files. Cory On Sun, Jun 21, 2015 at 10:21 AM, Vishnubharathi T < vishnu2bharathi at gmail.com> wrote: > Hi all, > > I have files with extension .inp(ansys file) and .prt(Unigraphics fiile) > I wanted to open them in paraview and convert them into .stl formats after > applying triangulation. > > > When I tried opening .inp files. I got the following error: > > Warning: In > C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\DataModel\vtkDataObject.cxx, > line 522 > > vtkUnstructuredGrid (000000000D074F40): Attempted to ShallowCopy from null. > > > > ERROR: In > C:\DBD\pvs-x64\paraview\src\paraview\Utilities\VisItBridge\Library\VisItLib\visit_vtk\full\vtkUnstructuredGridRelevantPointsFilter.C, > line 109 > > vtkUnstructuredGridRelevantPointsFilter (000000000EC565F0): No data to > Operate On! > > > > Please help me with this. I have attached the files for reference. > > > with regards, > > Bharathi > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Tue Jun 30 08:32:11 2015 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Tue, 30 Jun 2015 15:32:11 +0300 (EEST) Subject: [Paraview] problem in defining vtkStructuredGrid in MPI In-Reply-To: <33263.5.170.210.33.1435344647.squirrel@webmail.be.itu.edu.tr> References: <35434.140.105.47.80.1435312725.squirrel@webmail.be.itu.edu.tr> <26352.140.105.47.80.1435327011.squirrel@webmail.be.itu.edu.tr> <33263.5.170.210.33.1435344647.squirrel@webmail.be.itu.edu.tr> Message-ID: <23601.140.105.47.80.1435667531.squirrel@webmail.be.itu.edu.tr> Hi Again, Now, i have some problem when i trying to create the visualisation. I created grid as it suggested. In this case, i have multi piece data (structured grid) inside of the single block. The grid can be seen in the attached plot (plot_grid.png).In this case, it seems correct and you could see the each element clearly. If i attach data to the grid using Paraview co-processing then i am getting output as it shown in the image_0.png. So, i have still see the gaps between the pieces even the grid defined correctly. Is it normal in this case? It might be the feature of multi piece dataset. Anyway, i would like to see the complete view of the field without any gap between the pieces (or decomposition elements). Is it possible to do that with the current setup? I might also need to add the overlap regions (among the decomposition elements) in the grid but i am not sure. Any suggestion might be helpful at this point. Best Regards, --ufuk > Hi, > > Thanks for your suggestion. I did it as follows, > > vtkMultiBlockDataSet* grid = vtkMultiBlockDataSet::New(); > vtkNew mpds; > mpds->SetNumberOfPieces(*mpiSize); > mpds->SetPiece(*mpiRank, sg.GetPointer()); > grid->SetNumberOfBlocks(1); > grid->SetBlock(0, mpds.GetPointer()); > > so, there is one block that has each partition in a vtkMultiPieceDataSet. > Thanks again. > > Regards, > > --ufuk > > >> If the output of the vtm is what you're looking for you won't be able to >> do >> that with the parallel XML structured grid writer because you have a >> node >> partition (i.e. nodes are uniquely assigned to a process and in this >> case >> no other process has that node). Thus the missing cells at the partition >> boundary are causing you problems with the pvts reader. >> >> With the multiblock data set my suggestion is to make the first block in >> that be a vtkMultiPieceDataSet and then add each process's structured >> grid >> as a piece to that. Then when you load it into ParaView it will behave >> much >> more uniformly. >> >> >> >> On Fri, Jun 26, 2015 at 9:56 AM, >> wrote: >> >>> Hi, >>> >>> Thanks for your help. Actually, every processor has its own data and i >>> am >>> just using the interior regions (so, it does not overlap, no ghost or >>> halo >>> regions). Anyway, after my initial mail, i changed the SetExtent part >>> of >>> the code as >>> >>> sg->SetExtent (*nxstart-2, *nxend-2, *nystart-2, *nyend-2, 0, 0); >>> >>> because it was starting from 1 in each direction, now it starts from >>> zero. >>> This modification fixes the mismatch problem in the number of points >>> comes >>> from Paraview and seen in the C++ code. On the other hand, the Paraview >>> still complains about the following extents (seems that the inner >>> boundary >>> of the 2 x 2 decomposition elements, like ghost region). >>> >>> 0 140 57 58 0 0 >>> 70 71 0 57 0 0 >>> 70 71 58 114 0 0 >>> >>> You can find the data in the attached file (data_00.tar.gz). >>> >>> Then, i tried to put the individual parts of the structured grid into >>> the >>> vtkMultiBlockDataSet using following code >>> >>> // >>> // Create multi block grid >>> // >>> vtkMultiBlockDataSet* grid = vtkMultiBlockDataSet::New (); >>> grid->SetNumberOfBlocks(*mpiSize); >>> grid->SetBlock (*mpiRank, sg.GetPointer()); >>> >>> and write the grid information to the file (data_01.tar.gz). In this >>> case, >>> Paraview could open the *.vtm file without any message. So, i could not >>> be >>> sure about the grid. It seems fine if i look at multi block data file >>> (vtm) but not in pvts file. >>> >>> Regards, >>> >>> --ufuk >>> >>> >>> > Do you have a node partitioning of your grid? If you do you really >>> need a >>> > cell partitioning of the grid which will have multiple points a the >>> > partition overlap. >>> > >>> > Can you share your data? >>> > >>> > On Fri, Jun 26, 2015 at 5:58 AM, >>> wrote: >>> > >>> >> Hi, >>> >> >>> >> I am trying to create structured grid in an MPI application and i am >>> >> using >>> >> following C++ code to implement it >>> >> >>> >> extern "C" void createstgrid_(double* y, double* x, >>> >> int* nxstart, int* nxend, int* >>> nystart, >>> >> int* >>> >> nyend, >>> >> int* nx, int* ny, int* nz, int* >>> mpiSize, >>> >> int* mpiRank) { >>> >> // >>> >> // Create structured grid >>> >> // >>> >> vtkSmartPointer sg = >>> >> vtkSmartPointer::New(); >>> >> sg->SetExtent (*nxstart-1, *nxend-1, *nystart-1, *nyend-1, 0, 0); >>> >> >>> >> // >>> >> // Create data structure to store grid coordinates >>> >> // >>> >> int pnx = ((*nxend)-(*nxstart))+1; >>> >> int pny = ((*nyend)-(*nystart))+1; >>> >> vtkSmartPointer points = >>> vtkSmartPointer::New(); >>> >> >>> >> // >>> >> // Insert grid coordinate data as points >>> >> // >>> >> k = 0; >>> >> for (int j = 0; j < pny; j++) { >>> >> for (int i = 0; i < pnx; i++) { >>> >> points->InsertPoint(k, x[i+j*pnx], y[i+j*pnx], 0); >>> >> k = k+1; >>> >> } >>> >> } >>> >> sg->SetPoints(points); >>> >> >>> >> // >>> >> // Set grid >>> >> // >>> >> >>> >> >>> vtkCPPythonAdaptorAPI::GetCoProcessorData()->GetInputDescriptionByName("input")->SetGrid(sg); >>> >> >>> >> >>> vtkCPPythonAdaptorAPI::GetCoProcessorData()->GetInputDescriptionByName("input")->SetWholeExtent(0, >>> >> *nx-1, 0, *ny-1, 0, 0); >>> >> } >>> >> >>> >> so, when i run the code with grid writer, it creates the individual >>> file >>> >> (*.vts) for each processor and one extra for the combination >>> (*.pvts). >>> >> Anyway, the individual files looks fine in Paraview but if i open >>> the >>> >> file >>> >> with pvts extension, i am getting following error, >>> >> >>> >> ERROR: In >>> >> >>> >> >>> /Users/turuncu/Qsync/progs/paraview-4.3.1/src/VTK/IO/XML/vtkXMLPStructuredDataReader.cxx, >>> >> line 461 >>> >> vtkXMLPStructuredGridReader (0x7f961c0910a0): No available piece >>> >> provides >>> >> data for the following extents: >>> >> 0 140 0 1 0 0 >>> >> 0 1 1 58 0 0 >>> >> 0 140 58 59 0 0 >>> >> 0 1 59 114 0 0 >>> >> 71 72 1 58 0 0 >>> >> 71 72 59 114 0 0 >>> >> >>> >> The UpdateExtent cannot be filled. >>> >> >>> >> What is the meaning of this message? It means that some of the grid >>> data >>> >> (or points) are not filled by the code. I also check the loop in the >>> C++ >>> >> code and print out the number of points for each processor >>> >> >>> >> 0 number of points = 4118 >>> >> 1 number of points = 4047 >>> >> 2 number of points = 4060 >>> >> 3 number of points = 3990 >>> >> >>> >> and the total is 16215, which is consistent with the size of the >>> grid >>> >> but >>> >> if i check the individual vts files from the Paraview, the files >>> shows >>> >> different number of points for each file >>> >> >>> >> 0 number of points = 4118 >>> >> 1 number of points = 3976 >>> >> 2 number of points = 4002 >>> >> 3 number of points = 3864 >>> >> >>> >> So, only first file matchs with the C++ code but others not. I am >>> not >>> >> sure >>> >> what is happening in there and if you have any suggestion that will >>> be >>> >> great. >>> >> >>> >> Anyway, in this case i did not use vtkMultiBlockDataSet but after >>> having >>> >> correct representation of the grid, i am planing use SetBlock method >>> of >>> >> vtkMultiBlockDataSet to assign decomposition elements as individual >>> >> blocks. >>> >> >>> >> Regards, >>> >> >>> >> --ufuk >>> >> >>> >> _______________________________________________ >>> >> Powered by www.kitware.com >>> >> >>> >> Visit other Kitware open-source projects at >>> >> http://www.kitware.com/opensource/opensource.html >>> >> >>> >> Please keep messages on-topic and check the ParaView Wiki at: >>> >> http://paraview.org/Wiki/ParaView >>> >> >>> >> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >> >>> >> Follow this link to subscribe/unsubscribe: >>> >> http://public.kitware.com/mailman/listinfo/paraview >>> >> >>> > >>> >> > > -------------- next part -------------- A non-text attachment was scrubbed... Name: plot_grid.png Type: image/png Size: 83665 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image_0.png Type: image/png Size: 19597 bytes Desc: not available URL: From pmidha3 at gatech.edu Tue Jun 30 10:37:53 2015 From: pmidha3 at gatech.edu (Prem Midha) Date: Tue, 30 Jun 2015 10:37:53 -0400 Subject: [Paraview] Particle Trace from PIV Data Message-ID: I am having trouble with ParaVIEW crashing when trying to view the results of a Particle Trace. It seems to compute without errors, however when I hit play, the program crashes. My input is a series of time-resolved discrete vector fields obtained from particle image velocimetry (PIV). I export the field into a series of csv files containing coordinates and velocities (x,y,z=0,u,v,w=0). Has anyone else had issues with this? Any help would be greatly appreciated! Thanks, Prem -------------- next part -------------- An HTML attachment was scrubbed... URL: From bak at lanl.gov Tue Jun 30 10:50:39 2015 From: bak at lanl.gov (Kashiwa, Bucky) Date: Tue, 30 Jun 2015 14:50:39 +0000 Subject: [Paraview] reading classic *.cosmo files in versions greater than 3 Message-ID: We have been very happily reading classical *.cosmo formatted datafiles using version 3.98.1, but when reading the same files in subsequent versions (4.0, 4.1, 4.2, 4.3) the data get read, but wrongly interpreted. I did the diff of the PCosmoReader.h between v3.98.1 and v4.3.1 which suggested to me that the last number in the cosmo data (called ?tag?) is now int64_t rather than integer. So if we write the cosmo data with type MPI_2INTEGER (~ fortran kind=SELECTED_INT_KIND(15)) then the data are read correctly by the v4.3.1 cosmo reader (without byte swap). If I select the ?Adaptive cosmo reader? from the reader list, it displays a button for the ?Tag Size? which can be 32-bit or 64-bit. This button does not appear on the ?Cosmology Files? choice from the reader list. Could it be that the build system is somehow failing to place the ?Tag Size? button on the ?Cosmology Files? Properties panel? If so, it would be wonderful to get it put there so that we can have the choice of Tag Size on the very useful .cosmo datafiles. If not, please let us know if we are stuck with a 64-bit Tag Size. Thanks very much. ======================================================================73 <>Bucky Kashiwa PhD, PE <> Post: MS B216, Los Alamos, NM 87545 <> <> Ofc: TA3-SM123-RM276 <>Email: bak at lanl.gov, kashiwa at qwest.net <> <>Voice: 505-667-8812 <> Fax: 505-665-5926 <> <> Home: 505-988-7332 <> Cell: 505-795-5581 <> =======================================================================73 From mvanmoer at illinois.edu Tue Jun 30 18:22:39 2015 From: mvanmoer at illinois.edu (Vanmoer, Mark W) Date: Tue, 30 Jun 2015 22:22:39 +0000 Subject: [Paraview] using pvbatch to write pvti/vti file sets Message-ID: <7F781841FF1E044388AFA42B70703A7A8A2116AE@CHIMBX6.ad.uillinois.edu> Hi ParaView, When using the client GUI, Save Data will write out a pvti/vti data set with a vti for each processor. When trying this with pvbatch I'm only getting a single vti. I'm calling the pvbatch with aprun -n 32 pvpython myscript.py which I think should generate 1 pvti and 32 vtis. This is using ParaView 4.1.0. myscript.py is a hack, I'm reading a pvti that's split into 8192 vtis and trying to re-write out fewer, say 32 or 64. This is part of troubleshooting what I think might be a lustre issue. # myscript.py try: paraview.simple except: from paraview.simple import * servermanager.Connect() reader = XMLPartitionedImageDataReader(FileName=['test-input.pvti']) writer = XMLPImageDataWriter() writer.Input = reader writer.CompressorType = 'ZLib' writer.FileName = 'test-output.pvti' writer.UpdatePipeline() Is what I want to do possible? If not, is there a recommended way to merge vtis? Mark From kevin.dean at decisionsciencescorp.com Tue Jun 30 19:22:44 2015 From: kevin.dean at decisionsciencescorp.com (Dean, Kevin) Date: Tue, 30 Jun 2015 16:22:44 -0700 Subject: [Paraview] Executive Not calling RequestData In-Reply-To: References: Message-ID: So I got a little further. Instead I used a multi block data set to load my polydata(s). When i update my pipeline, all the information gets transferred to ParaView except for the block data. I set up a writer that records the data, and that information is exactly the same as the streaming data (but it can actually render the blocks). So, I guess you could say I am perplexed, ha. Do you have any suggestions? Thanks Man! Kevin E. Dean here's the snippet: void MultiBlockDataSetDDSReader::UpdatePipeline(vtkMultiBlockDataSet* mb) { printf("%s\n", __PRETTY_FUNCTION__); MultiBlockDataSetDDSReader::UpdateInformation(); vtkStreamingDemandDrivenPipeline* executive = vtkStreamingDemandDrivenPipeline::SafeDownCast(MultiBlockDataSetDDSReader::GetExecutive()); this->multi_block = mb; for (int i = 0; i < this->multi_block->GetNumberOfBlocks(); i++) { executive->SetUpdateExtent(0, i, this->multi_block->GetNumberOfBlocks(), 0); MultiBlockDataSetDDSReader::Update(); } } and my request data: /*----------------------------------------------------------------------------*/ int MultiBlockDataSetDDSReader::RequestData( vtkInformation *vtkNotUsed(request), vtkInformationVector **inputVector, vtkInformationVector *outputVector) { printf("%s\n", __PRETTY_FUNCTION__); vtkInformation* outInfo = outputVector->GetInformationObject(0); vtkMultiBlockDataSet *output = vtkMultiBlockDataSet::GetData(outputVector); if (this->multi_block != NULL) { output->ShallowCopy(this->multi_block); vtkStreamingDemandDrivenPipeline::CONTINUE_EXECUTING(); } return 1; } On Fri, Jun 26, 2015 at 9:30 AM, Dean, Kevin < kevin.dean at decisionsciencescorp.com> wrote: > Ok, so I looked through this yesterday and tried implementing some of the > code. I now have the poly data information (# of cells, # of points, and > Bounds updating in ParaView) However, for poly data objects to be rendered > (and their data arrays to be copied to the output), is the best way to set > the update extents by: > > executive->SetUpdateExtent( vtkInformation *, int piece, int numPieces, > int ghostLevel ); > > I'm not that familiar with updating unstructured datasets. Image data is > simple because the extents are based off the size of the image. Also, for > understanding the description of "pieces", since they are subsets of > unstructured datasets, does a piece correspond to individual cells or other > information held within the poly data? And just one more question, is there > a good place to find an explanation of what is / how to set up a PRODUCER, > because I read that the producer determines what a piece means... > > Thanks for the help! > > Kevin > > On Thu, Jun 25, 2015 at 6:42 AM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> RequestData doesn't get called unless the pipeline determines that >> something has changed. This is at core of VTK's demand driven execution >> pipeline. You may want to checkout Berk's blog ( >> http://www.kitware.com/blog/home/post/831) about how you can use >> `CONTINUE_EXECUTING` key for "streaming". >> >> Utkarsh >> >> On Wed, Jun 24, 2015 at 2:32 PM Dean, Kevin < >> kevin.dean at decisionsciencescorp.com> wrote: >> >>> I was wondering if anyone has run into this problem before. I am >>> streaming vtkPolyData objects into ParaView, but for some reason (after my >>> UpdatePipeline function is called), the executive does not call RequestData >>> upon an Update command. Could there be any reasons for this? >>> >>> Here is my snippet: >>> >>> *void* *VTKPolyDataObjectsDDSReader::UpdateMyPipeline*(vtkPolyData* >>> poly_data) >>> { >>> // DEBUG: >>> // printf("%s\n", __PRETTY_FUNCTION__); >>> >>> VTKPolyDataObjectsDDSReader::*UpdateInformation*(); >>> vtkStreamingDemandDrivenPipeline* executive = >>> vtkStreamingDemandDrivenPipeline::*SafeDownCast*( >>> VTKPolyDataObjectsDDSReader::*GetExecutive*()); >>> >>> *if* (!executive) >>> { >>> *return*; >>> } >>> >>> *this*->poly_data = poly_data; >>> >>> *for* (*int* i = 0; i < *this*->poly_data->*GetNumberOfPieces*(); i++) >>> { >>> executive->*SetUpdateExtent*(0, i, *this*->poly_data-> >>> *GetNumberOfPieces*(), 0); >>> VTKPolyDataObjectsDDSReader::*Update*(); >>> } >>> } >>> >>> Any help is appreciated! Thanks guys. >>> >>> Kevin E. Dean >>> >>> P.S. - also attached is a screenshot of what some of the output looks >>> like. >>> >>> This email and its contents are confidential. If you are not the >>> intended recipient, please do not disclose or use the information within >>> this email or its attachments. If you have received this email in error, >>> please report the error to the sender by return email and delete this >>> communication from your records. >> >> > -- This email and its contents are confidential. If you are not the intended recipient, please do not disclose or use the information within this email or its attachments. If you have received this email in error, please report the error to the sender by return email and delete this communication from your records. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Information.png Type: image/png Size: 35928 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ReaderInformation.png Type: image/png Size: 167340 bytes Desc: not available URL: From kevin.dean at decisionsciencescorp.com Tue Jun 30 19:36:03 2015 From: kevin.dean at decisionsciencescorp.com (Dean, Kevin) Date: Tue, 30 Jun 2015 16:36:03 -0700 Subject: [Paraview] Executive Not calling RequestData In-Reply-To: References: Message-ID: Well, after moving the writer to my RequestData function, I found that the output is not properly copying the multi-block dataset for some reason. I have to try and figure that out... Kevin E. Dean On Tue, Jun 30, 2015 at 4:22 PM, Dean, Kevin < kevin.dean at decisionsciencescorp.com> wrote: > So I got a little further. Instead I used a multi block data set to load > my polydata(s). When i update my pipeline, all the information gets > transferred to ParaView except for the block data. I set up a writer that > records the data, and that information is exactly the same as the streaming > data (but it can actually render the blocks). So, I guess you could say I > am perplexed, ha. Do you have any suggestions? > > Thanks Man! > > Kevin E. Dean > > here's the snippet: > > void MultiBlockDataSetDDSReader::UpdatePipeline(vtkMultiBlockDataSet* mb) > { > printf("%s\n", __PRETTY_FUNCTION__); > > MultiBlockDataSetDDSReader::UpdateInformation(); > vtkStreamingDemandDrivenPipeline* executive = > vtkStreamingDemandDrivenPipeline::SafeDownCast(MultiBlockDataSetDDSReader::GetExecutive()); > > this->multi_block = mb; > > for (int i = 0; i < this->multi_block->GetNumberOfBlocks(); i++) > { > executive->SetUpdateExtent(0, i, > this->multi_block->GetNumberOfBlocks(), 0); > MultiBlockDataSetDDSReader::Update(); > } > } > > and my request data: > > /*----------------------------------------------------------------------------*/ > int MultiBlockDataSetDDSReader::RequestData( > vtkInformation *vtkNotUsed(request), > vtkInformationVector **inputVector, > vtkInformationVector *outputVector) > { > printf("%s\n", __PRETTY_FUNCTION__); > vtkInformation* outInfo = outputVector->GetInformationObject(0); > vtkMultiBlockDataSet *output = > vtkMultiBlockDataSet::GetData(outputVector); > > if (this->multi_block != NULL) > { > output->ShallowCopy(this->multi_block); > > vtkStreamingDemandDrivenPipeline::CONTINUE_EXECUTING(); > } > > return 1; > } > > On Fri, Jun 26, 2015 at 9:30 AM, Dean, Kevin < > kevin.dean at decisionsciencescorp.com> wrote: > >> Ok, so I looked through this yesterday and tried implementing some of the >> code. I now have the poly data information (# of cells, # of points, and >> Bounds updating in ParaView) However, for poly data objects to be rendered >> (and their data arrays to be copied to the output), is the best way to set >> the update extents by: >> >> executive->SetUpdateExtent( vtkInformation *, int piece, int numPieces, >> int ghostLevel ); >> >> I'm not that familiar with updating unstructured datasets. Image data is >> simple because the extents are based off the size of the image. Also, for >> understanding the description of "pieces", since they are subsets of >> unstructured datasets, does a piece correspond to individual cells or other >> information held within the poly data? And just one more question, is there >> a good place to find an explanation of what is / how to set up a PRODUCER, >> because I read that the producer determines what a piece means... >> >> Thanks for the help! >> >> Kevin >> >> On Thu, Jun 25, 2015 at 6:42 AM, Utkarsh Ayachit < >> utkarsh.ayachit at kitware.com> wrote: >> >>> RequestData doesn't get called unless the pipeline determines that >>> something has changed. This is at core of VTK's demand driven execution >>> pipeline. You may want to checkout Berk's blog ( >>> http://www.kitware.com/blog/home/post/831) about how you can use >>> `CONTINUE_EXECUTING` key for "streaming". >>> >>> Utkarsh >>> >>> On Wed, Jun 24, 2015 at 2:32 PM Dean, Kevin < >>> kevin.dean at decisionsciencescorp.com> wrote: >>> >>>> I was wondering if anyone has run into this problem before. I am >>>> streaming vtkPolyData objects into ParaView, but for some reason (after my >>>> UpdatePipeline function is called), the executive does not call RequestData >>>> upon an Update command. Could there be any reasons for this? >>>> >>>> Here is my snippet: >>>> >>>> *void* *VTKPolyDataObjectsDDSReader::UpdateMyPipeline*(vtkPolyData* >>>> poly_data) >>>> { >>>> // DEBUG: >>>> // printf("%s\n", __PRETTY_FUNCTION__); >>>> >>>> VTKPolyDataObjectsDDSReader::*UpdateInformation*(); >>>> vtkStreamingDemandDrivenPipeline* executive = >>>> vtkStreamingDemandDrivenPipeline::*SafeDownCast*( >>>> VTKPolyDataObjectsDDSReader::*GetExecutive*()); >>>> >>>> *if* (!executive) >>>> { >>>> *return*; >>>> } >>>> >>>> *this*->poly_data = poly_data; >>>> >>>> *for* (*int* i = 0; i < *this*->poly_data->*GetNumberOfPieces*(); >>>> i++) >>>> { >>>> executive->*SetUpdateExtent*(0, i, *this*->poly_data-> >>>> *GetNumberOfPieces*(), 0); >>>> VTKPolyDataObjectsDDSReader::*Update*(); >>>> } >>>> } >>>> >>>> Any help is appreciated! Thanks guys. >>>> >>>> Kevin E. Dean >>>> >>>> P.S. - also attached is a screenshot of what some of the output looks >>>> like. >>>> >>>> This email and its contents are confidential. If you are not the >>>> intended recipient, please do not disclose or use the information within >>>> this email or its attachments. If you have received this email in error, >>>> please report the error to the sender by return email and delete this >>>> communication from your records. >>> >>> >> > -- This email and its contents are confidential. If you are not the intended recipient, please do not disclose or use the information within this email or its attachments. If you have received this email in error, please report the error to the sender by return email and delete this communication from your records. -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Tue Jun 30 21:22:18 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 30 Jun 2015 21:22:18 -0400 Subject: [Paraview] using pvbatch to write pvti/vti file sets In-Reply-To: <7F781841FF1E044388AFA42B70703A7A8A2116AE@CHIMBX6.ad.uillinois.edu> References: <7F781841FF1E044388AFA42B70703A7A8A2116AE@CHIMBX6.ad.uillinois.edu> Message-ID: Hi Mark, Is that a typo or are you really using pvpython? You said "aprun -n 32 pvpython myscript.py". Otherwise I don't see anything that shouldn't work. Best, Andy On Tue, Jun 30, 2015 at 6:22 PM, Vanmoer, Mark W wrote: > Hi ParaView, > > When using the client GUI, Save Data will write out a pvti/vti data set > with a vti for each processor. When trying this with pvbatch I'm only > getting a single vti. I'm calling the pvbatch with > > aprun -n 32 pvpython myscript.py > > which I think should generate 1 pvti and 32 vtis. This is using ParaView > 4.1.0. > > myscript.py is a hack, I'm reading a pvti that's split into 8192 vtis and > trying to re-write out fewer, say 32 or 64. This is part of troubleshooting > what I think might be a lustre issue. > > # myscript.py > try: paraview.simple > except: from paraview.simple import * > servermanager.Connect() > reader = XMLPartitionedImageDataReader(FileName=['test-input.pvti']) > writer = XMLPImageDataWriter() > writer.Input = reader > writer.CompressorType = 'ZLib' > writer.FileName = 'test-output.pvti' > writer.UpdatePipeline() > > Is what I want to do possible? If not, is there a recommended way to merge > vtis? > Mark > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: