From utkarsh.ayachit at kitware.com Sun Mar 1 16:10:12 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 1 Mar 2015 16:10:12 -0500 Subject: [Paraview] Bug in redo camera/property link In-Reply-To: References: Message-ID: Federico, Thanks for offering to fix this issue. I think the problem here is that we don;t have an undo-element that can support undo/redoing link creations/deletions. A fix to overcome the problem would be to pqLinksModel::addCameraLink() to clear the undo-stack at the end of the operation, thus user can no longer undo/redo the link creation -- thus not cause a segfault. To add support for undo/redo, one needs to write a vtkSMUndoElement subclass that can be pushed on to the undo-stack with enough state information to know what it needs to do on undo and redo. For starters, every place a link is created, we can manually create this new undo-element subclass and initialize it and then push it on the undo stack. Check out the other subclasses of vtkSMUndoElement, they will make it clear what such a class needs to do. Utkarsh On Fri, Feb 27, 2015 at 3:21 AM, Federico Veronesi wrote: > Dear all, > > I found this bug on redo camera link (but it occours anytime I try to redo > a link) > > Add source to renderview > split layout > add source to renderview2 > link camera between the two views > UNDO the link > REDO the link > CRASH (on PV 4.2 debug) , view destroyed on PV 4.3.1 (release) > > I reported it on Mantis : http://www.paraview.org/Bug/view.php?id=15347 > > I found out that the problem rises because in vtkSMSessionProxyManager > when trying to load the state of the link the corresponding classname is > not stored in the message. > > If somebody can point me out where to look I'll be happy to help with the > fix. > Regards > > > -------------------------------- > Federico Veronesi, PhD > SCS s.r.l. - Via Parini 1, Casalecchio di Reno (BO) Italy > CINECA - Via Magnanelli 6/3, Casalecchio di Reno (BO) Italy > Phone: +39 051 6171624 > E-mail: f.veronesi at scsitaly.com > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From houssen at ipgp.fr Mon Mar 2 07:02:04 2015 From: houssen at ipgp.fr (houssen) Date: Mon, 02 Mar 2015 13:02:04 +0100 Subject: [Paraview] =?utf-8?q?How_to_check_for_duplicate_nodes_=3F?= Message-ID: <4c6f41747c5bf44c939a99a616443829@imap.ipgp.fr> Hello, I have data (nodes and cells like HEXA8) on screen (open xmdf data) : how to check for duplicate nodes ? Thanks, Franck From nenasantos at hotmail.com Mon Mar 2 07:10:58 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Mon, 2 Mar 2015 12:10:58 +0000 Subject: [Paraview] Annotate time filter - regard real time In-Reply-To: References: , , Message-ID: Dear paraview users,I have a question over the use of Annotate time filter in Paraview. I have a paraview script that read netcdf data which has time axis given as "days since 1970-01-0100:00" (Epoch Time). This gives problem if I want to show the real time of the data in the animation window. What I would like to have shown are the date as4-8-2003, 00:00 etc. and it shows big number like 19521, 19522. Does anyone have some idea how to solve the problem?Thanks a lot! Madalena -------------- next part -------------- An HTML attachment was scrubbed... URL: From mohammadtaghi.khalili at ntnu.no Mon Mar 2 08:16:59 2015 From: mohammadtaghi.khalili at ntnu.no (Ehsan Khalili) Date: Mon, 2 Mar 2015 13:16:59 +0000 Subject: [Paraview] make an animation movie Message-ID: <9DEED4F02747D44DBF50D34A6D6ACE7CC150AD@WAREHOUSE03.win.ntnu.no> Hi, I am a PhD candidate working on Numerical modelling of Fluid Structure Interaction. The code I am working with has been written in Fortran 90. Since I needed multi blocks for my grid domain, I implemented MPI in the code til the blocks have interaction with each other. For writing the data I am using the sequential approach which means each block writes the its data sequentially in the a txt file. Now I want to produce an animation movies for my moving grid mesh and vortexes. I know that the Paraview is the most powerful softwer in visualisation in CFD. However I have not any experienced in that. It would be grateful if you could help me out and tell me how to do it step by step. I am looking forward hearing form you. Thank so much in advance. Best regards, Ehsan -------------- next part -------------- An HTML attachment was scrubbed... URL: From felipe.bordeu at ec-nantes.fr Mon Mar 2 08:18:06 2015 From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu Weldt) Date: Mon, 2 Mar 2015 14:18:06 +0100 Subject: [Paraview] Annotate time filter - regard real time In-Reply-To: References: , Message-ID: you can use the python programable filter to create a field data with the date (in string) and use a annotate field data filter. Felipe Le 27 f?vr. 2015 ? 14:50, Madalena S. Malhadas a ?crit : > > Dear paraview users, > > I have a question over the use of Annotate time filter in Paraview. I have a paraview script that read netcdf data which has time axis given as "days since 1970-01-01 > 00:00" (Epoch Time). This gives problem if I want to show the real time of the data in the animation window. What I would like to have shown are the date as > 4-8-2003, 00:00 etc. and it shows big number like 19521, 19522. > > Does anyone have some idea how to solve the problem? > > Thanks a lot! > > Madalena > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: Message signed with OpenPGP using GPGMail URL: From nenasantos at hotmail.com Mon Mar 2 09:07:18 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Mon, 2 Mar 2015 14:07:18 +0000 Subject: [Paraview] Annotate time filter - regard real time In-Reply-To: References: , , , , Message-ID: But how do I do it? Can you explain the steps please? RegardsMadalena From: felipe.bordeu at ec-nantes.fr Date: Mon, 2 Mar 2015 14:18:06 +0100 CC: paraview at paraview.org Subject: Re: [Paraview] Annotate time filter - regard real time you can use the python programable filter to create a field data with the date (in string) and use a annotate field data filter. Felipe Le 27 f?vr. 2015 ? 14:50, Madalena S. Malhadas a ?crit : Dear paraview users,I have a question over the use of Annotate time filter in Paraview. I have a paraview script that read netcdf data which has time axis given as "days since 1970-01-0100:00" (Epoch Time). This gives problem if I want to show the real time of the data in the animation window. What I would like to have shown are the date as4-8-2003, 00:00 etc. and it shows big number like 19521, 19522. Does anyone have some idea how to solve the problem?Thanks a lot! Madalena_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 Christophe.Dang at sidel.com Mon Mar 2 09:18:28 2015 From: Christophe.Dang at sidel.com (Dang, Christophe) Date: Mon, 2 Mar 2015 14:18:28 +0000 Subject: [Paraview] make an animation movie In-Reply-To: <9DEED4F02747D44DBF50D34A6D6ACE7CC150AD@WAREHOUSE03.win.ntnu.no> References: <9DEED4F02747D44DBF50D34A6D6ACE7CC150AD@WAREHOUSE03.win.ntnu.no> Message-ID: Hello, > De : ParaView [mailto:paraview-bounces at paraview.org] De la part de Ehsan Khalili > Envoy? : lundi 2 mars 2015 14:17 > > Now I want to produce an animation movies for my moving grid mesh and vortexes You can create several files, one per step time, and give them the same name except a leading or ending number. ParaView will automatically understand the serial character of the files. See the Utkarsh Ayachit, /The ParaView Guide/ (2015), p.23 "Handling temporal file series" http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.3&type=data&os=all&downloadFile=TheParaViewGuide-v4.3-CC-Edition.pdf HTH Regards -- Christophe Dang Ngoc Chan Mechanical calculation engineer This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error), please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. From niklas.karcher at dlr.de Mon Mar 2 10:11:21 2015 From: niklas.karcher at dlr.de (Niklas Karcher) Date: Mon, 2 Mar 2015 16:11:21 +0100 Subject: [Paraview] Anti-Aliasing in SaveScreenshot Message-ID: <54F47D99.80406@dlr.de> Hi, I am using the pvbatch tool to generate plots. I ran into an issue where the SaveScreenshot method used in the pvbatch python script apparently does not use any anti-aliasing (see Python.png attachment). If I use the SaveScreenshot method inside of Paraview from the menu the result is anti-aliased. (see AA.png) How do I activate the anti-aliasing inside of my python script that is run by pvbatch? Thx for your help Niklas -------------- next part -------------- A non-text attachment was scrubbed... Name: Python.png Type: image/png Size: 4536 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: AA.png Type: image/png Size: 19490 bytes Desc: not available URL: From nenasantos at hotmail.com Mon Mar 2 10:38:53 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Mon, 2 Mar 2015 15:38:53 +0000 Subject: [Paraview] Save 2 views as animations/images in same layout In-Reply-To: <54F47D99.80406@dlr.de> References: <54F47D99.80406@dlr.de> Message-ID: Dear all,I have a script that animate two views in same layout. The Scritp run fine, but apears to have a problem saving one single image formed by the 2 views. I made a simple test by running the trace in paraview, creating and saving to views. Follow the example below and the output attached. The example compose the 2 views but produces also a black square in corner. Any one know to solve the problem? Kind regards --------------------------------------------------script example------------------------------------------------------------------- # get active viewrenderView1 = GetActiveViewOrCreate('RenderView') # get layoutviewLayout1 = GetLayout() # split cellviewLayout1.SplitVertical(0, 0.5) # Create a new 'Render View'renderView2 = CreateView('RenderView')renderView2.ViewSize = [1156, 383]renderView2.StereoType = 0renderView2.Background = [0.32, 0.34, 0.43] renderView1 = GetRenderView()renderView2 = GetRenderViews()[1] # current camera placement for renderView1 # current camera placement for renderView2 # current camera placement for renderView2 SaveAnimation ('C:/Users/madalenasantos/Desktop/Paraview/Teste.jpg', layout=viewLayout1) ------------------------------------------------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Teste.jpg Type: image/jpeg Size: 70215 bytes Desc: not available URL: From kmorel at sandia.gov Mon Mar 2 10:38:52 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 2 Mar 2015 15:38:52 +0000 Subject: [Paraview] Anti-Aliasing in SaveScreenshot Message-ID: Niklas, I realize this does not answer your question at all (I don't know the answer) but have you considered using the Export Scene utility (the ExportView function in Python) to create a pdf file? That will create the plot using vector graphics, which will look better than the png with or without anti-alaising. -Ken On 3/2/15, 8:11 AM, "Niklas Karcher" wrote: >Hi, >I am using the pvbatch tool to generate plots. I ran into an issue where >the SaveScreenshot method used in the pvbatch python script apparently >does not use any anti-aliasing (see Python.png attachment). >If I use the SaveScreenshot method inside of Paraview from the menu the >result is anti-aliased. (see AA.png) > >How do I activate the anti-aliasing inside of my python script that is >run by pvbatch? >Thx for your help >Niklas From felipe.bordeu at ec-nantes.fr Mon Mar 2 10:46:32 2015 From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu) Date: Mon, 02 Mar 2015 16:46:32 +0100 Subject: [Paraview] Annotate time filter - regard real time In-Reply-To: References: , , , , Message-ID: <54F485D8.3040702@ec-nantes.fr> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 to generate a string from you field data (using a ProgrammableFilter): script: pdo = self.GetOutput(); pdo.ShallowCopy(self.GetInput()); a = self.GetInput().GetInformation().Get(pdo.DATA_TIME_STEP()); # this is your convertion routine time_label = "Days from 12/12/1800 = " + str(a*100) + ":" + str((a*100)%2) + " ...days" label = vtk.vtkStringArray(); label.SetNumberOfComponents(1); label.Resize(1); label.SetName("TimeLabel"); label.SetValue(0,time_label); pdo.GetFieldData().AddArray(label) del label then you use a AnnotateGlobalData Filter. Done Le 02/03/2015 15:07, Madalena S. Malhadas a ?crit : > But how do I do it? Can you explain the steps please? > > Regards > Madalena > > ------------------------- > From: felipe.bordeu at ec-nantes.fr > Date: Mon, 2 Mar 2015 14:18:06 +0100 > CC: paraview at paraview.org > Subject: Re: [Paraview] Annotate time filter - regard real time > > you can use the python programable filter to create a field data with the date (in string) and use a annotate field data filter. > > Felipe > Le 27 f?vr. 2015 ? 14:50, Madalena S. Malhadas > a ?crit : > > > Dear paraview users, > > I have a question over the use of Annotate time filter in Paraview. I have a paraview script that read netcdf data which has time axis given as "days since 1970-01-01 > 00:00" (Epoch Time). This gives problem if I want to show the real time of the data in the animation window. What I would like to have shown are the date as > 4-8-2003, 00:00 etc. and it shows big number like 19521, 19522. > > Does anyone have some idea how to solve the problem? > > Thanks a lot! > > Madalena > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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 - -- Felipe Bordeu Weldt Ing?nieur de Recherche - ------------------------------------- T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS 6183 ?cole Centrale Nantes 1 Rue de La No?, 44321 Nantes, FRANCE - ------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU9IXSAAoJEE/fMfNgU9/DXNUIAJd5UqjbG2tj5Yaiun6fAcvQ iAkHUG6cPuRAxNW9mhvTQtjY57LoidZJ2Co0/rPtTEJSrLdJdAVhQNcrOATTkrHx QdojMW9R3Cv2/dB0T9zFQlQ4hhMnPCmXAX5af4XwHlCkVIX5blUNK6tpB1DAyYw/ Htjt/qrBWpYphh9ea6eX1cRBwOBzk1RY6c7Ts2dtVhkGjb1vmCrqqa5WzKP/3VQy Flzj+10vVKHH2XKO/6pqxALDVWWcGlyzTGUkifEz504R6mu9w7cS5/Ro+QzlH4pp trYpjH0NrprvmavD0s23bTn3aGbOz+qnbnM4Q4iEaZaBKxyqHIz2PpkxxlyshME= =hCMQ -----END PGP SIGNATURE----- -------------- next part -------------- An HTML attachment was scrubbed... URL: From nenasantos at hotmail.com Mon Mar 2 10:49:15 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Mon, 2 Mar 2015 15:49:15 +0000 Subject: [Paraview] Annotate time filter - regard real time In-Reply-To: <54F485D8.3040702@ec-nantes.fr> References: , , , , , , , , , <54F485D8.3040702@ec-nantes.fr> Message-ID: Thank you very much! I will test now. Kind regards Date: Mon, 2 Mar 2015 16:46:32 +0100 From: felipe.bordeu at ec-nantes.fr CC: paraview at paraview.org Subject: Re: [Paraview] Annotate time filter - regard real time -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 to generate a string from you field data (using a ProgrammableFilter): script: pdo = self.GetOutput(); pdo.ShallowCopy(self.GetInput()); a = self.GetInput().GetInformation().Get(pdo.DATA_TIME_STEP()); # this is your convertion routine time_label = "Days from 12/12/1800 = " + str(a*100) + ":" + str((a*100)%2) + " ...days" label = vtk.vtkStringArray(); label.SetNumberOfComponents(1); label.Resize(1); label.SetName("TimeLabel"); label.SetValue(0,time_label); pdo.GetFieldData().AddArray(label) del label then you use a AnnotateGlobalData Filter. Done Le 02/03/2015 15:07, Madalena S. Malhadas a ?crit : > But how do I do it? Can you explain the steps please? > > Regards > Madalena > > ------------------------- > From: felipe.bordeu at ec-nantes.fr > Date: Mon, 2 Mar 2015 14:18:06 +0100 > CC: paraview at paraview.org > Subject: Re: [Paraview] Annotate time filter - regard real time > > you can use the python programable filter to create a field data with the date (in string) and use a annotate field data filter. > > Felipe > Le 27 f?vr. 2015 ? 14:50, Madalena S. Malhadas > a ?crit : > > > Dear paraview users, > > I have a question over the use of Annotate time filter in Paraview. I have a paraview script that read netcdf data which has time axis given as "days since 1970-01-01 > 00:00" (Epoch Time). This gives problem if I want to show the real time of the data in the animation window. What I would like to have shown are the date as > 4-8-2003, 00:00 etc. and it shows big number like 19521, 19522. > > Does anyone have some idea how to solve the problem? > > Thanks a lot! > > Madalena > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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 - -- Felipe Bordeu Weldt Ing?nieur de Recherche - ------------------------------------- T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS 6183 ?cole Centrale Nantes 1 Rue de La No?, 44321 Nantes, FRANCE - ------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU9IXSAAoJEE/fMfNgU9/DXNUIAJd5UqjbG2tj5Yaiun6fAcvQ iAkHUG6cPuRAxNW9mhvTQtjY57LoidZJ2Co0/rPtTEJSrLdJdAVhQNcrOATTkrHx QdojMW9R3Cv2/dB0T9zFQlQ4hhMnPCmXAX5af4XwHlCkVIX5blUNK6tpB1DAyYw/ Htjt/qrBWpYphh9ea6eX1cRBwOBzk1RY6c7Ts2dtVhkGjb1vmCrqqa5WzKP/3VQy Flzj+10vVKHH2XKO/6pqxALDVWWcGlyzTGUkifEz504R6mu9w7cS5/Ro+QzlH4pp trYpjH0NrprvmavD0s23bTn3aGbOz+qnbnM4Q4iEaZaBKxyqHIz2PpkxxlyshME= =hCMQ -----END PGP SIGNATURE----- _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephen.wornom at inria.fr Mon Mar 2 11:25:32 2015 From: stephen.wornom at inria.fr (Stephen Wornom) Date: Mon, 02 Mar 2015 17:25:32 +0100 Subject: [Paraview] Save 2 views as animations/images in same layout In-Reply-To: References: <54F47D99.80406@dlr.de> Message-ID: <54F48EFC.9000009@inria.fr> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: stephen_wornom.vcf Type: text/x-vcard Size: 187 bytes Desc: not available URL: From nenasantos at hotmail.com Mon Mar 2 11:29:02 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Mon, 2 Mar 2015 16:29:02 +0000 Subject: [Paraview] Save 2 views as animations/images in same layout In-Reply-To: <54F48EFC.9000009@inria.fr> References: <54F47D99.80406@dlr.de> ,<54F48EFC.9000009@inria.fr> Message-ID: I use the PV 4.3. There is no reason to write a new script, it was a result from testing suggestions regarded in the samples provided in the menu. Can you provide me the correct code to test in my computer/PV version? Madalena Date: Mon, 2 Mar 2015 17:25:32 +0100 From: stephen.wornom at inria.fr To: nenasantos at hotmail.com CC: niklas.karcher at dlr.de; paraview at paraview.org Subject: Re: [Paraview] Save 2 views as animations/images in same layout Madalena S. Malhadas wrote: Dear all, I have a script that animate two views in same layout. The Scritp run fine, but apears to have a problem saving one single image formed by the 2 views. I made a simple test by running the trace in paraview, creating and saving to views. Follow the example below and the output attached. The example compose the 2 views but produces also a black square in corner. Any one know to solve the problem? Kind regards I have done this with PV 4.1. Split the screen and organize the two views,click on the animate icon, unclick "save selected view" , should work. Is there a reason why you write a new script? Stephen --------------------------------------------------script example------------------------------------------------------------------- # get active view renderView1 = GetActiveViewOrCreate('RenderView') # get layout viewLayout1 = GetLayout() # split cell viewLayout1.SplitVertical(0, 0.5) # Create a new 'Render View' renderView2 = CreateView('RenderView') renderView2.ViewSize = [1156, 383] renderView2.StereoType = 0 renderView2.Background = [0.32, 0.34, 0.43] renderView1 = GetRenderView() renderView2 = GetRenderViews()[1] # current camera placement for renderView1 # current camera placement for renderView2 # current camera placement for renderView2 SaveAnimation ('C:/Users/madalenasantos/Desktop/Paraview/Teste.jpg', layout=viewLayout1) ------------------------------------------------------------------------------------------------------------------------------------------- _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- stephen.wornom at inria.fr 2004 route des lucioles - BP93 Sophia Antipolis 06902 CEDEX Tel: 04 92 38 50 54 Fax: 04 97 15 53 51 -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Mon Mar 2 13:50:01 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Mon, 2 Mar 2015 13:50:01 -0500 Subject: [Paraview] VTK parallel unstructured grid and halo elements In-Reply-To: References: <1a180a02-4f10-4dff-91fe-a7a9ce1918ed@HUB06.ad.oak.ox.ac.uk> <7d78668e-79eb-4364-8e2d-08fb061dfb1f@HUB04.ad.oak.ox.ac.uk> Message-ID: The only way to do this currently is to use the threshold filter to remote the halo nodes. Best, -berk On Fri, Feb 27, 2015 at 6:32 AM, Louie Cardone-Noott < louie.cardone-noott at linacre.ox.ac.uk> wrote: > Hi Berk, > > Thanks for your reply. Yes that does sound like what I need to do. > Shouldn't the nodes of elements with vtkGhostLevels>0 already be ignored in > the range calculation though? > > Is there no way to do this currently then? I tried marking them with > vtkGhostPoints but it didn't help last time I tried. > > Cheers, > Louie > > On 25 February 2015 at 18:31, Berk Geveci wrote: > >> Hi Louie, >> >> Ghost/halo nodes are considered valid (but duplicated) so they are taken >> into account when calculating ranges, statistics etc. What you need is to >> mark them as invalid, it sounds like? We are making slow progress towards >> having an infrastructure that supports this but currently it is only >> partially support for structured grids and AMR meshes and a subset of >> filters. >> >> Best, >> -berk >> >> On Wed, Feb 25, 2015 at 11:06 AM, Louie Cardone-Noott < >> louie.cardone-noott at linacre.ox.ac.uk> wrote: >> >>> Hi again list, >>> >>> Inspired by David Ortley's recent success (see "Smooth seams in SILO >>> files") I wonder if perhaps the way I'm doing it is correct, but Paraview >>> is incorrectly considering the values at hidden nodes when calculating data >>> ranges. >>> >>> Essentially my "option 3" (writing a vtkGhostLevels array) appears to >>> work as it should, and the "seams" are hidden in my parallel data. But, if >>> I then Extract Surface and look at the Data Arrays -> Data Ranges I see >>> values which can only be from non-surface nodes. I suspect they are >>> probably from nodes on the (hidden) interior surfaces. This is obviously a >>> bug. >>> >>> I could probably provide a minimal example if useful. >>> >>> Best wishes, >>> Louie >>> >>> >>> On 17 January 2015 at 16:26, Louie Cardone-Noott < >>> louie.cardone-noott at linacre.ox.ac.uk> wrote: >>> >>>> Hi Paraview list, >>>> >>>> I use a finite element code that generates VTK output, but I'm having >>>> trouble dealing with halo (ghost) nodes/elements correctly. >>>> >>>> We currently partition meshes node-wise, and each process writes all >>>> its owned nodes and one level of halo nodes to a chunk. Once all the chunks >>>> are loaded there is a "double layer" of internal boundaries between >>>> processes. I'd really like to be able to use the Extract Surface filter >>>> correctly but as you would expect it also finds all the internal surfaces. >>>> From searching I've tried: >>>> >>>> * Clean To Grid, but this removes both sides of the double layer >>>> leaving unsightly gaps. >>>> * Writing a vtkGhostPoints array (on nodes) but this seems not to be >>>> used by this filter (or Paraview at all?) >>>> * Writing a vtkGhostLevels array (on elements). This correctly hides >>>> all the ghost elements at the internal boundaries (great!) but still >>>> doesn't let me do everything I want to. For example, the extracted surface >>>> looks right, but the array limits still seem to be based on the max/min of >>>> the external AND internal surfaces, so I suspect the internal ones are just >>>> "hidden from view". >>>> >>>> What's the right way to deal with this? >>>> >>>> Thanks in advance. >>>> >>>> Louie >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> 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 cjm2176 at columbia.edu Mon Mar 2 19:03:00 2015 From: cjm2176 at columbia.edu (Colin McAuliffe) Date: Mon, 2 Mar 2015 19:03:00 -0500 Subject: [Paraview] Opacity functions Message-ID: Hi all, I would like to make some areas appear transparent depending on a threshold value of a damage parameter. This is no problem if the plot is colored by the damage parameter. However, I am wondering if it is possible to have the opacity set by the damage parameter while the plot is colored by some other field. Is this sort of thing possible to do in paraview? Thanks, Colin -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Mar 2 20:46:28 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 3 Mar 2015 01:46:28 +0000 Subject: [Paraview] [EXTERNAL] Opacity functions In-Reply-To: References: Message-ID: The most transparent you can make a cell is to just remove it. Try using the threshold filter, and threshold on damage? Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Colin McAuliffe Sent: Monday, March 02, 2015 5:03 PM To: ParaView Subject: [EXTERNAL] [Paraview] Opacity functions Hi all, I would like to make some areas appear transparent depending on a threshold value of a damage parameter. This is no problem if the plot is colored by the damage parameter. However, I am wondering if it is possible to have the opacity set by the damage parameter while the plot is colored by some other field. Is this sort of thing possible to do in paraview? Thanks, Colin -------------- next part -------------- An HTML attachment was scrubbed... URL: From cjm2176 at columbia.edu Mon Mar 2 21:39:12 2015 From: cjm2176 at columbia.edu (Colin McAuliffe) Date: Mon, 2 Mar 2015 21:39:12 -0500 Subject: [Paraview] [EXTERNAL] Opacity functions In-Reply-To: References: Message-ID: Thank you Alan, this filter definitely works for what I want. I also tried to use a clip filter with a scalar and the final result appears a little bit smoother than the threshold filter. On Mon, Mar 2, 2015 at 8:46 PM, Scott, W Alan wrote: > The most transparent you can make a cell is to just remove it. Try > using the threshold filter, and threshold on damage? > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *Colin > McAuliffe > *Sent:* Monday, March 02, 2015 5:03 PM > *To:* ParaView > *Subject:* [EXTERNAL] [Paraview] Opacity functions > > > > Hi all, I would like to make some areas appear transparent depending on a > threshold value of a damage parameter. This is no problem if the plot is > colored by the damage parameter. However, I am wondering if it is possible > to have the opacity set by the damage parameter while the plot is colored > by some other field. Is this sort of thing possible to do in paraview? > Thanks, Colin > -------------- next part -------------- An HTML attachment was scrubbed... URL: From felipe.bordeu at ec-nantes.fr Tue Mar 3 03:30:19 2015 From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu) Date: Tue, 03 Mar 2015 09:30:19 +0100 Subject: [Paraview] Annotate time filter - regard real time - error in code after test In-Reply-To: References: , , , , , , , , , , , , , <54F485D8.3040702@ec-nantes.fr>, Message-ID: <54F5711B.8080205@ec-nantes.fr> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Please keep the discussion to the mailing list so others can benefit-from/contribute-to the conversion. the code I send is for the programmable filter!!! if you are using a python script these are the lines to use (generated with python trace in ParaView): the code in the Script variable of the programmable filter is always very ugly. you can put the source in a file extra file and use the execfile() function of python to call it. #--- begin code --- # create a new 'Programmable Filter' programmableFilter1 = ProgrammableFilter(Input=waterPropertiesnc) # Properties modified on programmableFilter1 programmableFilter1.Script = 'pdo = self.GetOutput();\npdo.ShallowCopy(self.GetInput());\na = self.GetInput().GetInformation().Get(pdo.DATA_TIME_STEP());\n# this is your convertion routine\ntime_label = "Days from 12/12/1800 = " + str(a*100) + ":" + str((a*100)%2) + " ...days"\nlabel = vtk.vtkStringArray();\nlabel.SetNumberOfComponents(1);\nlabel.Resize(1);\nlabel.SetName("TimeLabel");\nlabel.SetValue(0,time_label);\npdo.GetFieldData().AddArray(label)\n' programmableFilter1.RequestInformationScript = '' programmableFilter1.RequestUpdateExtentScript = '' programmableFilter1.PythonPath = '' annotateGlobalData1 = AnnotateGlobalData(Input=programmableFilter1) # show data in view annotateGlobalData1Display = Show(annotateGlobalData1, renderView1) #--- end code --- don?t forget to do the time conversion in the script!!! Felipe Le 02/03/2015 17:09, Madalena S. Malhadas a ?crit : > Hi Felipe, > > I am a new user of paraview/python, so i Have dificult to understand where i have to place the code in my script. > > My script read a nc file, then i use the annotate time filter to extract the time in file, but apears numbers (equivalent to seconds) > > Then i include your code after call annotate time filter but i get an error. > > Attached i send my scritp and if possible can you see the part of the time conversions and understand what ihave wrong. For me is to difficult to understand since i am novate in programming. > > Thank you very much > > Madalena > > ------------------------- > From: nenasantos at hotmail.com > To: felipe.bordeu at ec-nantes.fr > Date: Mon, 2 Mar 2015 15:49:15 +0000 > CC: paraview at paraview.org > Subject: Re: [Paraview] Annotate time filter - regard real time > > Thank you very much! I will test now. > > Kind regards > > ------------------------- > Date: Mon, 2 Mar 2015 16:46:32 +0100 > From: felipe.bordeu at ec-nantes.fr > CC: paraview at paraview.org > Subject: Re: [Paraview] Annotate time filter - regard real time > > > to generate a string from you field data (using a ProgrammableFilter): > > script: > > pdo = self.GetOutput(); > pdo.ShallowCopy(self.GetInput()); > a = self.GetInput().GetInformation().Get(pdo.DATA_TIME_STEP()); > # this is your convertion routine > time_label = "Days from 12/12/1800 = " + str(a*100) + ":" + str((a*100)%2) + " ...days" > label = vtk.vtkStringArray(); > label.SetNumberOfComponents(1); > label.Resize(1); > label.SetName("TimeLabel"); > label.SetValue(0,time_label); > pdo.GetFieldData().AddArray(label) > > del label > > then you use a AnnotateGlobalData Filter. > > Done > > > > > Le 02/03/2015 15:07, Madalena S. Malhadas a ?crit : > > But how do I do it? Can you explain the steps please? > > > Regards > > Madalena > > > ------------------------- > > From: felipe.bordeu at ec-nantes.fr > > Date: Mon, 2 Mar 2015 14:18:06 +0100 > > CC: paraview at paraview.org > > Subject: Re: [Paraview] Annotate time filter - regard real time > > > you can use the python programable filter to create a field data with the date (in string) and use a annotate field data filter. > > > Felipe > > Le 27 f?vr. 2015 ? 14:50, Madalena S. Malhadas > a ?crit : > > > > Dear paraview users, > > > I have a question over the use of Annotate time filter in Paraview. I have a paraview script that read netcdf data which has time axis given as "days since 1970-01-01 > > 00:00" (Epoch Time). This gives problem if I want to show the real time of the data in the animation window. What I would like to have shown are the date as > > 4-8-2003, 00:00 etc. and it shows big number like 19521, 19522. > > > Does anyone have some idea how to solve the problem? > > > Thanks a lot! > > > Madalena > > _______________________________________________ > > Powered by www.kitware.com > > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > > 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 - -- Felipe Bordeu Weldt Ing?nieur de Recherche - ------------------------------------- T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS 6183 ?cole Centrale Nantes 1 Rue de La No?, 44321 Nantes, FRANCE - ------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU9XEOAAoJEE/fMfNgU9/DWf4H/1J8KiRnj8bVjVQ9+4zw8Ne6 VQHw4Ibt+SQjq2LI400aNxbew92A3h7wY1Hd6PkV1hMmJt7lTRync6NJ27GAMnfZ P2mLEggin2r4ZEbSdOavA26wWSs2+yXs6sjQIOcivmsPHFGwY2+XpAAUwN1nIcxZ egqPEGyokauxkO3C3EKGcT6thl+6GXTZKh+5j/JfcoB0G54pxJjLeXqWdCIJiQ0X tuWHpx7kGdLdRMNH1Dm8KEd/C8iJneHKCYntK5b1U3kiCJZoiXccNszfTRO+xgFl 3hBv34eXPEiSk2q2+NW4S3mo2W9h+mB/gGswrX4zyyD/P6UFtIoS16POFcPu3Lw= =p6E1 -----END PGP SIGNATURE----- -------------- next part -------------- An HTML attachment was scrubbed... URL: From chengdi123000 at gmail.com Tue Mar 3 03:43:22 2015 From: chengdi123000 at gmail.com (=?UTF-8?B?56iL6L+q?=) Date: Tue, 3 Mar 2015 16:43:22 +0800 Subject: [Paraview] Hi, Apply button of ExtractLocation filter of paraview 4.3.1 does not work? Message-ID: I am using ubuntu 12.04 LTS and paraview 4.3.1 I am using a CGNS file generated by FLUENT 6.3, I import the data file and everything is ok, except the ExtractLocation filter does not work. The input is a slice of the imported MultiBlock dataset I have tried convert the slice from cell data to point data and use the result point data as ExtractLocation's input, it does not work; I have tried different mode of ExtractLocation, it does not work I tried use CGNS reader as ExtractLocation's input, it does not work I doubted if it is because my point is at the corner of the slice plane. And the float point is not accurate enough, so I tried >>>el.Location = [el.Input.GetDataInformation().DataInformation.GetBounds()[i] for i in [1,3,5]] It still does not work Finally, I used python shell to run >>>UpdatePipeline() it works, and the data information refreshed. I do not know why, it seems the apply button does not work. I do not know if this is a bug or feature? 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 Tel.: +86-15801594911 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nenasantos at hotmail.com Tue Mar 3 04:33:39 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Tue, 3 Mar 2015 09:33:39 +0000 Subject: [Paraview] Annotate time filter - regard real time - error in code after test In-Reply-To: <54F5711B.8080205@ec-nantes.fr> References: , , , ,,, , ,,, , ,,, ,,, <54F485D8.3040702@ec-nantes.fr>, , , , <54F5711B.8080205@ec-nantes.fr> Message-ID: Thank you very much. Date: Tue, 3 Mar 2015 09:30:19 +0100 From: felipe.bordeu at ec-nantes.fr To: paraview at paraview.org Subject: Re: [Paraview] Annotate time filter - regard real time - error in code after test -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Please keep the discussion to the mailing list so others can benefit-from/contribute-to the conversion. the code I send is for the programmable filter!!! if you are using a python script these are the lines to use (generated with python trace in ParaView): the code in the Script variable of the programmable filter is always very ugly. you can put the source in a file extra file and use the execfile() function of python to call it. #--- begin code --- # create a new 'Programmable Filter' programmableFilter1 = ProgrammableFilter(Input=waterPropertiesnc) # Properties modified on programmableFilter1 programmableFilter1.Script = 'pdo = self.GetOutput();\npdo.ShallowCopy(self.GetInput());\na = self.GetInput().GetInformation().Get(pdo.DATA_TIME_STEP());\n# this is your convertion routine\ntime_label = "Days from 12/12/1800 = " + str(a*100) + ":" + str((a*100)%2) + " ...days"\nlabel = vtk.vtkStringArray();\nlabel.SetNumberOfComponents(1);\nlabel.Resize(1);\nlabel.SetName("TimeLabel");\nlabel.SetValue(0,time_label);\npdo.GetFieldData().AddArray(label)\n' programmableFilter1.RequestInformationScript = '' programmableFilter1.RequestUpdateExtentScript = '' programmableFilter1.PythonPath = '' annotateGlobalData1 = AnnotateGlobalData(Input=programmableFilter1) # show data in view annotateGlobalData1Display = Show(annotateGlobalData1, renderView1) #--- end code --- don?t forget to do the time conversion in the script!!! Felipe Le 02/03/2015 17:09, Madalena S. Malhadas a ?crit : > Hi Felipe, > > I am a new user of paraview/python, so i Have dificult to understand where i have to place the code in my script. > > My script read a nc file, then i use the annotate time filter to extract the time in file, but apears numbers (equivalent to seconds) > > Then i include your code after call annotate time filter but i get an error. > > Attached i send my scritp and if possible can you see the part of the time conversions and understand what ihave wrong. For me is to difficult to understand since i am novate in programming. > > Thank you very much > > Madalena > > ------------------------- > From: nenasantos at hotmail.com > To: felipe.bordeu at ec-nantes.fr > Date: Mon, 2 Mar 2015 15:49:15 +0000 > CC: paraview at paraview.org > Subject: Re: [Paraview] Annotate time filter - regard real time > > Thank you very much! I will test now. > > Kind regards > > ------------------------- > Date: Mon, 2 Mar 2015 16:46:32 +0100 > From: felipe.bordeu at ec-nantes.fr > CC: paraview at paraview.org > Subject: Re: [Paraview] Annotate time filter - regard real time > > > to generate a string from you field data (using a ProgrammableFilter): > > script: > > pdo = self.GetOutput(); > pdo.ShallowCopy(self.GetInput()); > a = self.GetInput().GetInformation().Get(pdo.DATA_TIME_STEP()); > # this is your convertion routine > time_label = "Days from 12/12/1800 = " + str(a*100) + ":" + str((a*100)%2) + " ...days" > label = vtk.vtkStringArray(); > label.SetNumberOfComponents(1); > label.Resize(1); > label.SetName("TimeLabel"); > label.SetValue(0,time_label); > pdo.GetFieldData().AddArray(label) > > del label > > then you use a AnnotateGlobalData Filter. > > Done > > > > > Le 02/03/2015 15:07, Madalena S. Malhadas a ?crit : > > But how do I do it? Can you explain the steps please? > > > Regards > > Madalena > > > ------------------------- > > From: felipe.bordeu at ec-nantes.fr > > Date: Mon, 2 Mar 2015 14:18:06 +0100 > > CC: paraview at paraview.org > > Subject: Re: [Paraview] Annotate time filter - regard real time > > > you can use the python programable filter to create a field data with the date (in string) and use a annotate field data filter. > > > Felipe > > Le 27 f?vr. 2015 ? 14:50, Madalena S. Malhadas > a ?crit : > > > > Dear paraview users, > > > I have a question over the use of Annotate time filter in Paraview. I have a paraview script that read netcdf data which has time axis given as "days since 1970-01-01 > > 00:00" (Epoch Time). This gives problem if I want to show the real time of the data in the animation window. What I would like to have shown are the date as > > 4-8-2003, 00:00 etc. and it shows big number like 19521, 19522. > > > Does anyone have some idea how to solve the problem? > > > Thanks a lot! > > > Madalena > > _______________________________________________ > > Powered by www.kitware.com > > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > > 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 - -- Felipe Bordeu Weldt Ing?nieur de Recherche - ------------------------------------- T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS 6183 ?cole Centrale Nantes 1 Rue de La No?, 44321 Nantes, FRANCE - ------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU9XEOAAoJEE/fMfNgU9/DWf4H/1J8KiRnj8bVjVQ9+4zw8Ne6 VQHw4Ibt+SQjq2LI400aNxbew92A3h7wY1Hd6PkV1hMmJt7lTRync6NJ27GAMnfZ P2mLEggin2r4ZEbSdOavA26wWSs2+yXs6sjQIOcivmsPHFGwY2+XpAAUwN1nIcxZ egqPEGyokauxkO3C3EKGcT6thl+6GXTZKh+5j/JfcoB0G54pxJjLeXqWdCIJiQ0X tuWHpx7kGdLdRMNH1Dm8KEd/C8iJneHKCYntK5b1U3kiCJZoiXccNszfTRO+xgFl 3hBv34eXPEiSk2q2+NW4S3mo2W9h+mB/gGswrX4zyyD/P6UFtIoS16POFcPu3Lw= =p6E1 -----END PGP SIGNATURE----- _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 nenasantos at hotmail.com Tue Mar 3 08:06:31 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Tue, 3 Mar 2015 13:06:31 +0000 Subject: [Paraview] Annotate time filter - regard real time - error in code after test In-Reply-To: References: , , ,,,,, ,,,,, , , , , , , , , , , <54F485D8.3040702@ec-nantes.fr>, , , , , , , <54F5711B.8080205@ec-nantes.fr>, Message-ID: Dear all, I tryed to make the time conversion in the script but i have an error. When i put this programmableFilter1.Script = 'pdo = self.GetOutput();\npdo.ShallowCopy(self.GetInput());\na = self.GetInput().GetInformation().Get(pdo.DATA_TIME_STEP());\n# this is your convertion routine\ntime_label = "Days from 12/12/1800 = " + str(a*100) + ":" + str((a*100)%2) + " ...days"\nlabel = vtk.vtkStringArray();\nlabel.SetNumberOfComponents(1);\nlabel.Resize(1);\nlabel.SetName("TimeLabel");\nlabel.SetValue(0,time_label);\npdo.GetFieldData().AddArray(label)\n' in the script box via paraview i get error. Do you know how to solve the error. Madalena From: nenasantos at hotmail.com To: felipe.bordeu at ec-nantes.fr; paraview at paraview.org Date: Tue, 3 Mar 2015 09:33:39 +0000 Subject: Re: [Paraview] Annotate time filter - regard real time - error in code after test Thank you very much. Date: Tue, 3 Mar 2015 09:30:19 +0100 From: felipe.bordeu at ec-nantes.fr To: paraview at paraview.org Subject: Re: [Paraview] Annotate time filter - regard real time - error in code after test -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Please keep the discussion to the mailing list so others can benefit-from/contribute-to the conversion. the code I send is for the programmable filter!!! if you are using a python script these are the lines to use (generated with python trace in ParaView): the code in the Script variable of the programmable filter is always very ugly. you can put the source in a file extra file and use the execfile() function of python to call it. #--- begin code --- # create a new 'Programmable Filter' programmableFilter1 = ProgrammableFilter(Input=waterPropertiesnc) # Properties modified on programmableFilter1 programmableFilter1.Script = 'pdo = self.GetOutput();\npdo.ShallowCopy(self.GetInput());\na = self.GetInput().GetInformation().Get(pdo.DATA_TIME_STEP());\n# this is your convertion routine\ntime_label = "Days from 12/12/1800 = " + str(a*100) + ":" + str((a*100)%2) + " ...days"\nlabel = vtk.vtkStringArray();\nlabel.SetNumberOfComponents(1);\nlabel.Resize(1);\nlabel.SetName("TimeLabel");\nlabel.SetValue(0,time_label);\npdo.GetFieldData().AddArray(label)\n' programmableFilter1.RequestInformationScript = '' programmableFilter1.RequestUpdateExtentScript = '' programmableFilter1.PythonPath = '' annotateGlobalData1 = AnnotateGlobalData(Input=programmableFilter1) # show data in view annotateGlobalData1Display = Show(annotateGlobalData1, renderView1) #--- end code --- don?t forget to do the time conversion in the script!!! Felipe Le 02/03/2015 17:09, Madalena S. Malhadas a ?crit : > Hi Felipe, > > I am a new user of paraview/python, so i Have dificult to understand where i have to place the code in my script. > > My script read a nc file, then i use the annotate time filter to extract the time in file, but apears numbers (equivalent to seconds) > > Then i include your code after call annotate time filter but i get an error. > > Attached i send my scritp and if possible can you see the part of the time conversions and understand what ihave wrong. For me is to difficult to understand since i am novate in programming. > > Thank you very much > > Madalena > > ------------------------- > From: nenasantos at hotmail.com > To: felipe.bordeu at ec-nantes.fr > Date: Mon, 2 Mar 2015 15:49:15 +0000 > CC: paraview at paraview.org > Subject: Re: [Paraview] Annotate time filter - regard real time > > Thank you very much! I will test now. > > Kind regards > > ------------------------- > Date: Mon, 2 Mar 2015 16:46:32 +0100 > From: felipe.bordeu at ec-nantes.fr > CC: paraview at paraview.org > Subject: Re: [Paraview] Annotate time filter - regard real time > > > to generate a string from you field data (using a ProgrammableFilter): > > script: > > pdo = self.GetOutput(); > pdo.ShallowCopy(self.GetInput()); > a = self.GetInput().GetInformation().Get(pdo.DATA_TIME_STEP()); > # this is your convertion routine > time_label = "Days from 12/12/1800 = " + str(a*100) + ":" + str((a*100)%2) + " ...days" > label = vtk.vtkStringArray(); > label.SetNumberOfComponents(1); > label.Resize(1); > label.SetName("TimeLabel"); > label.SetValue(0,time_label); > pdo.GetFieldData().AddArray(label) > > del label > > then you use a AnnotateGlobalData Filter. > > Done > > > > > Le 02/03/2015 15:07, Madalena S. Malhadas a ?crit : > > But how do I do it? Can you explain the steps please? > > > Regards > > Madalena > > > ------------------------- > > From: felipe.bordeu at ec-nantes.fr > > Date: Mon, 2 Mar 2015 14:18:06 +0100 > > CC: paraview at paraview.org > > Subject: Re: [Paraview] Annotate time filter - regard real time > > > you can use the python programable filter to create a field data with the date (in string) and use a annotate field data filter. > > > Felipe > > Le 27 f?vr. 2015 ? 14:50, Madalena S. Malhadas > a ?crit : > > > > Dear paraview users, > > > I have a question over the use of Annotate time filter in Paraview. I have a paraview script that read netcdf data which has time axis given as "days since 1970-01-01 > > 00:00" (Epoch Time). This gives problem if I want to show the real time of the data in the animation window. What I would like to have shown are the date as > > 4-8-2003, 00:00 etc. and it shows big number like 19521, 19522. > > > Does anyone have some idea how to solve the problem? > > > Thanks a lot! > > > Madalena > > _______________________________________________ > > Powered by www.kitware.com > > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > > 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 - -- Felipe Bordeu Weldt Ing?nieur de Recherche - ------------------------------------- T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS 6183 ?cole Centrale Nantes 1 Rue de La No?, 44321 Nantes, FRANCE - ------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU9XEOAAoJEE/fMfNgU9/DWf4H/1J8KiRnj8bVjVQ9+4zw8Ne6 VQHw4Ibt+SQjq2LI400aNxbew92A3h7wY1Hd6PkV1hMmJt7lTRync6NJ27GAMnfZ P2mLEggin2r4ZEbSdOavA26wWSs2+yXs6sjQIOcivmsPHFGwY2+XpAAUwN1nIcxZ egqPEGyokauxkO3C3EKGcT6thl+6GXTZKh+5j/JfcoB0G54pxJjLeXqWdCIJiQ0X tuWHpx7kGdLdRMNH1Dm8KEd/C8iJneHKCYntK5b1U3kiCJZoiXccNszfTRO+xgFl 3hBv34eXPEiSk2q2+NW4S3mo2W9h+mB/gGswrX4zyyD/P6UFtIoS16POFcPu3Lw= =p6E1 -----END PGP SIGNATURE----- _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 Tue Mar 3 08:58:59 2015 From: houssen at ipgp.fr (houssen) Date: Tue, 03 Mar 2015 14:58:59 +0100 Subject: [Paraview] =?utf-8?q?How_to_check_for_duplicate_nodes_=3F?= In-Reply-To: References: Message-ID: <025244773badb338ada629a6aecdb24a@imap.ipgp.fr> Hello, I have data (nodes and cells like HEXA8) on screen (open xmdf data) : how to check for duplicate nodes ? Thanks, Franck From stephen.wornom at inria.fr Tue Mar 3 09:19:57 2015 From: stephen.wornom at inria.fr (Stephen Wornom) Date: Tue, 03 Mar 2015 15:19:57 +0100 Subject: [Paraview] PV4.1: How to see the 9 scalar components of the gradient of velocity Message-ID: <54F5C30D.10305@inria.fr> I compute the vector gradients. There are 9 components of the matrix. When I select the calculator, the 9 scalar components are not found. How can I get the 9 scalar components into the calculator? Hope my question is clear, Thanks, Stephen -- stephen.wornom at inria.fr 2004 route des lucioles - BP93 Sophia Antipolis 06902 CEDEX Tel: 04 92 38 50 54 Fax: 04 97 15 53 51 -------------- next part -------------- A non-text attachment was scrubbed... Name: stephen_wornom.vcf Type: text/x-vcard Size: 187 bytes Desc: not available URL: From andy.bauer at kitware.com Tue Mar 3 09:24:18 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 3 Mar 2015 09:24:18 -0500 Subject: [Paraview] PV4.1: How to see the 9 scalar components of the gradient of velocity In-Reply-To: <54F5C30D.10305@inria.fr> References: <54F5C30D.10305@inria.fr> Message-ID: I'm not sure how to do it in PV 4.1 but in PV 4.3 it will show all 9 scalar components in the Calculator filter. For PV 4.1 it may be easier to use the Python Calculator instead. Regards, Andy On Tue, Mar 3, 2015 at 9:19 AM, Stephen Wornom wrote: > I compute the vector gradients. There are 9 components of the matrix. > When I select the calculator, the 9 scalar components are not found. > How can I get the 9 scalar components into the calculator? > Hope my question is clear, > Thanks, > Stephen > > -- > stephen.wornom at inria.fr > 2004 route des lucioles - BP93 > Sophia Antipolis > 06902 CEDEX > > Tel: 04 92 38 50 54 > Fax: 04 97 15 53 51 > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 jfavre at cscs.ch Tue Mar 3 10:25:36 2015 From: jfavre at cscs.ch (Favre Jean) Date: Tue, 3 Mar 2015 15:25:36 +0000 Subject: [Paraview] Find Data at first timestep to use as selection Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F68317E6725@MBX111.d.ethz.ch> Hi there I have particle data, which I read with the H5PartReader plugin I need to extract the particles whose distances from an x axis offset are within a given threshold on the first timestep, and then follow only these as time goes on. the first thing is trivial. I use a python calculator to compute the distance as in pythonCalculator1 = PythonCalculator() pythonCalculator1.Expression = 'abs(inputs[0].Points[:,0]-1900)' # x axis offset is 1900 pythonCalculator1.ArrayName = 'diff' then I use FindData with diff <= 200 # 200 is the threshold. that also works fine. What I cannot make work is the 'Freeze Selection' which is supposed to freeze the currently selected elements by IDs. The Extract Selection input text correctly show Type: Id Selection Elements; points process ID Index but the selection is always an empty set. Has anyone gotten that [Freeze selection] to work? ----------------- Jean/CSCS -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephen.wornom at inria.fr Tue Mar 3 10:59:56 2015 From: stephen.wornom at inria.fr (Stephen Wornom) Date: Tue, 03 Mar 2015 16:59:56 +0100 Subject: [Paraview] PV4.1: How to see the 9 scalar components of the gradient of velocity In-Reply-To: References: <54F5C30D.10305@inria.fr> Message-ID: <54F5DA7C.8090300@inria.fr> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: stephen_wornom.vcf Type: text/x-vcard Size: 196 bytes Desc: not available URL: From kmorel at sandia.gov Tue Mar 3 11:07:30 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Tue, 3 Mar 2015 16:07:30 +0000 Subject: [Paraview] How to check for duplicate nodes ? Message-ID: Franck, Try the "Clean to Grid" filter. -Ken On 3/3/15, 6:58 AM, "houssen" wrote: >Hello, > >I have data (nodes and cells like HEXA8) on screen (open xmdf data) : >how to check for duplicate nodes ? > >Thanks, > >Franck > >_______________________________________________ >Powered by www.kitware.com > >Visit other Kitware open-source projects at >http://www.kitware.com/opensource/opensource.html > >Please keep messages on-topic and check the ParaView Wiki at: >http://paraview.org/Wiki/ParaView > >Search the list archives at: http://markmail.org/search/?q=ParaView > >Follow this link to subscribe/unsubscribe: >http://public.kitware.com/mailman/listinfo/paraview From andy.bauer at kitware.com Tue Mar 3 11:26:59 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 3 Mar 2015 11:26:59 -0500 Subject: [Paraview] PV4.1: How to see the 9 scalar components of the gradient of velocity In-Reply-To: <54F5DA7C.8090300@inria.fr> References: <54F5C30D.10305@inria.fr> <54F5DA7C.8090300@inria.fr> Message-ID: What I did was create a Wavelet source, then used the Gradient of Unstructured DataSet filter, then used the Gradient of Unstructured DataSet filter again with Gradients as the Scalar Array and Gradients2 for the Result Array Name. After this I see Coords[X,Y,Z}, Gradients_{X,Y,Z}, Gradients2_{0,...,8} and RTData in the Scalars drop down. Do you get the same thing with that procedure? On Tue, Mar 3, 2015 at 10:59 AM, Stephen Wornom wrote: > Andy Bauer wrote: > > I'm not sure how to do it in PV 4.1 but in PV 4.3 it will show all 9 > scalar components in the Calculator filter. For PV 4.1 it may be easier to > use the Python Calculator instead. > > I tried PV4.3.1. I compute derivatives but I do not see the components in > the calculator. Should I have selected "strain" as the output of compute > derivatives? > I am using the download 64-bit binary executable named paraview. > Stephen > > > Regards, > Andy > > On Tue, Mar 3, 2015 at 9:19 AM, Stephen Wornom > wrote: > >> I compute the vector gradients. There are 9 components of the matrix. >> When I select the calculator, the 9 scalar components are not found. >> How can I get the 9 scalar components into the calculator? >> Hope my question is clear, >> Thanks, >> Stephen >> >> -- >> stephen.wornom at inria.fr >> 2004 route des lucioles - BP93 >> Sophia Antipolis >> 06902 CEDEX >> >> Tel: 04 92 38 50 54 >> Fax: 04 97 15 53 51 >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > > -- stephen.wornom at inria.fr > 2004 route des lucioles - BP93 > Sophia Antipolis > 06902 CEDEX > > Tel: 04 92 38 50 54 > Fax: 04 97 15 53 51 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Mar 3 13:09:54 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 3 Mar 2015 18:09:54 +0000 Subject: [Paraview] Superbuilds and clusters Message-ID: <6f1c065114704eaea84a269221d9e5ab@ES05AMSNLNT.srn.sandia.gov> I am trying to use the superbuild to create pvserver on a cluster. It appears to be running in parallel, but isn't remote rendering. The issue i believe is that the Superbuild isn't building with Mesa. I have done an ldd for mesa in the lib/paraview4-3 directory, and when I turn on Show Annotation, Remote Rendering says no. I am turning on ENABLE_mesa (-DENABLE_mesa:BOOL=ON). Should I be using osmesa instead? Any ideas what I am doing wrong? Thanks!! Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Mar 3 13:12:33 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 3 Mar 2015 18:12:33 +0000 Subject: [Paraview] [EXTERNAL] How to check for duplicate nodes ? In-Reply-To: <025244773badb338ada629a6aecdb24a@imap.ipgp.fr> References: <025244773badb338ada629a6aecdb24a@imap.ipgp.fr> Message-ID: As Ken said, you get rid of duplicate nodes with Clean to Grid. I wonder if you could check for duplicate nodes using the Spreadsheet View, then sort on the cell locations? Alan -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of houssen Sent: Tuesday, March 03, 2015 6:59 AM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] How to check for duplicate nodes ? Hello, I have data (nodes and cells like HEXA8) on screen (open xmdf data) : how to check for duplicate nodes ? Thanks, Franck _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 arctica1963 at gmail.com Tue Mar 3 13:42:26 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Tue, 3 Mar 2015 18:42:26 +0000 Subject: [Paraview] Clipping issue ParaView 4.3.1 Message-ID: Hello, I have loaded a 3D data cube and that all looks fine, but when I try to clip the data, the clip ends up being offset from the model itself. The data origin when loaded looks fine; have tried X, Y and Z clips and all end up offset. Origin: 305853.291 2040975 -5000 Normal: 1 0 0 Resetting the origin does not seem to affect the clip position, so I am not sure what is wrong with the data to cause this. See pic attached. Any ideas would be helpful Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: clip1.png Type: image/png Size: 59895 bytes Desc: not available URL: From kevin.d.lau at gmail.com Tue Mar 3 14:43:39 2015 From: kevin.d.lau at gmail.com (Kevin Lau) Date: Tue, 3 Mar 2015 14:43:39 -0500 Subject: [Paraview] Hardware suggestions for volume rendering In-Reply-To: References: Message-ID: Dear Aashish, Thank you very much for your reply. The latest work you're doing on volume rendering is very impressive. In order to access the latest VTK rendering in ParaView would we have to compile both the latest VTK and ParaView from source? Is it possible to link ParaView to specific VTK builds? Also do you know if it is preferential to have a single GPU (i.e. a workstation graphics card) or multiple GPU (i.e. gaming graphics card) when using ParaView? Many thanks, Kevin On 27 February 2015 at 08:15, Aashish Chaudhary < aashish.chaudhary at kitware.com> wrote: > Dear Kevin, > > First, I would like to mention that we have been working hard to improve > rendering in VTK that includes volume rendering as well. You may want to > read this source article: http://www.kitware.com/source/home/post/154. > Most of the changes related to this work is now available in VTK github > repository in master branch. If you are targetting current VTK, I would > suggest that any card that can support OpenGL2.1 or higher would be great. > The higher the GPU memory the better. While these newer card will work with > the previous version of volume rendering, it may not scale very well (in > our testing that's what we have observed). Current the default in ParaView > is OpenGL Volume Rendering but that is going to change sometime soon and > once that happens you will have OpenGL2 backend for everything. > > Hope this helps. > - Aashish > > > > On Thu, Feb 26, 2015 at 5:41 PM, Kevin Lau wrote: > >> Hi, >> >> I'm looking to putting together a workstation to perform realtime volume >> rendering of our simulation data. >> >> Are there any particular GPU features I should look for? >> >> If there are multiple GPUs will Paraview be able to take advantage of >> each GPU for volume rendering? >> >> Many thanks >> >> Kevin >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 aashish.chaudhary at kitware.com Tue Mar 3 14:53:44 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Tue, 3 Mar 2015 14:53:44 -0500 Subject: [Paraview] Hardware suggestions for volume rendering In-Reply-To: References: Message-ID: On Tue, Mar 3, 2015 at 2:43 PM, Kevin Lau wrote: > Dear Aashish, > > Thank you very much for your reply. The latest work you're doing on volume > rendering is very impressive. > Thanks. > > In order to access the latest VTK rendering in ParaView would we have to > compile both the latest VTK and ParaView from source? Is it possible to > link ParaView to specific VTK builds? > Latest ParaView from source should be fine. Just make sure that you select VTK_RENDERING_BACKEND to OpenGL2 > > Also do you know if it is preferential to have a single GPU (i.e. a > workstation graphics card) or multiple GPU (i.e. gaming graphics card) when > using ParaView? > If I remember correctly, we don't explicitly assign tasks to GPU in ParaView if running a single process. You can find more information here: http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server#Multiple_GPUs_Per_Node Hope it helps. > > Many thanks, > > Kevin > > > On 27 February 2015 at 08:15, Aashish Chaudhary < > aashish.chaudhary at kitware.com> wrote: > >> Dear Kevin, >> >> First, I would like to mention that we have been working hard to improve >> rendering in VTK that includes volume rendering as well. You may want to >> read this source article: http://www.kitware.com/source/home/post/154. >> Most of the changes related to this work is now available in VTK github >> repository in master branch. If you are targetting current VTK, I would >> suggest that any card that can support OpenGL2.1 or higher would be great. >> The higher the GPU memory the better. While these newer card will work with >> the previous version of volume rendering, it may not scale very well (in >> our testing that's what we have observed). Current the default in ParaView >> is OpenGL Volume Rendering but that is going to change sometime soon and >> once that happens you will have OpenGL2 backend for everything. >> >> Hope this helps. >> - Aashish >> >> >> >> On Thu, Feb 26, 2015 at 5:41 PM, Kevin Lau wrote: >> >>> Hi, >>> >>> I'm looking to putting together a workstation to perform realtime volume >>> rendering of our simulation data. >>> >>> Are there any particular GPU features I should look for? >>> >>> If there are multiple GPUs will Paraview be able to take advantage of >>> each GPU for volume rendering? >>> >>> Many thanks >>> >>> Kevin >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> 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 >> * >> > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From deytonjh at ornl.gov Tue Mar 3 15:32:23 2015 From: deytonjh at ornl.gov (Jordan Deyton) Date: Tue, 03 Mar 2015 15:32:23 -0500 Subject: [Paraview] Mismatched image size returned from ViewPort image render Message-ID: <54F61A57.8050704@ornl.gov> ParaView gurus, I am working on a project that uses the JSON RPC protocols provided by ParaViewWeb. I've noticed that the image quality for ViewPorts seems bad regardless of what is specified in the call to viewport.image.render (docs here: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/api/protocols.ParaViewWebViewPortImageDelivery ). After decoding the returned image from the Base64 encoding, the JPEG image comes out as 636x420, while the quality is listed as 100 and the original size is 1440x850. The JSON object passed to viewport.image.render looks like {"args":[{ "localtime":1425413914878, "view":-1, "size":[1440,850], "quality":100}] } While the returned object from that RPC call looks like { "image": "very long encoded image text here", "localTime": 0, "stale": false, "size": [1440,850], "format": "jpeg;base64", "global_id": "315", "mtime": 3068929, "workTime": 1 } I've used two separate Base64 decoders, and both result in a JPEG image that is 636x420, not the reported 1440x850. Any idea what could be the problem here? Is this a bug in ParaViewWeb? I'm running the latest stable ParaView release (4.3.1) on RHEL. Thanks, Jordan -- Jordan Deyton Oak Ridge National Laboratory Telephone: (865) 574-1091 Email: deytonjh at ornl.gov From anton.piccardo-selg at stfc.ac.uk Tue Mar 3 16:11:26 2015 From: anton.piccardo-selg at stfc.ac.uk (anton.piccardo-selg at stfc.ac.uk) Date: Tue, 3 Mar 2015 21:11:26 +0000 Subject: [Paraview] How to hide properties in the properties panel? Message-ID: <593AFCE559F11049B8F268BE84170A0DC1C332@EXCHMBX03.fed.cclrc.ac.uk> Hi, I have been working on some ParaView plugin filters recently. I need to pass information to them and I do so by defining properties in the config xml file. I set the properties programmatically -- this works well. The properties are listed on the properties panel though, hence I was wondering if there is a way to make certain properties invisible on the panel? Is there a special flag with which I can hide some properties, such that the user will not be aware of their existence? Many thanks and best regards, Anton From cory.quammen at kitware.com Tue Mar 3 16:18:02 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 3 Mar 2015 16:18:02 -0500 Subject: [Paraview] How to hide properties in the properties panel? In-Reply-To: <593AFCE559F11049B8F268BE84170A0DC1C332@EXCHMBX03.fed.cclrc.ac.uk> References: <593AFCE559F11049B8F268BE84170A0DC1C332@EXCHMBX03.fed.cclrc.ac.uk> Message-ID: You can set a "panel_visiblity" attribute to "never" in the property element, .e.g., Prevents cache from getting reset so that new computation always start from previous results. HTH, Cory On Tue, Mar 3, 2015 at 4:11 PM, wrote: > Hi, > > I have been working on some ParaView plugin filters recently. I need to pass information to them and I do so by defining properties in the config xml file. I set the properties programmatically -- this works well. The properties are listed on the properties panel though, hence I was wondering if there is a way to make certain properties invisible on the panel? Is there a special flag with which I can hide some properties, such that the user will not be aware of their existence? > > Many thanks and best regards, > > 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 -- Cory Quammen R&D Engineer Kitware, Inc. From arctica1963 at gmail.com Tue Mar 3 17:22:38 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Tue, 3 Mar 2015 22:22:38 +0000 Subject: [Paraview] Clipping issue ParaView 4.3.1 In-Reply-To: References: Message-ID: I managed to get the clip block into position by applying a translation: 0 30000 10000 Shouldn't have to do that if just doing a simple x normal clip etc. Not sure what the issue is. On 3 March 2015 at 18:42, Lester Anderson wrote: > Hello, > > I have loaded a 3D data cube and that all looks fine, but when I try to > clip the data, the clip ends up being offset from the model itself. The > data origin when loaded looks fine; have tried X, Y and Z clips and all end > up offset. > > Origin: 305853.291 2040975 -5000 > Normal: 1 0 0 > > Resetting the origin does not seem to affect the clip position, so I am > not sure what is wrong with the data to cause this. See pic attached. > > Any ideas would be helpful > > Thanks > -------------- next part -------------- An HTML attachment was scrubbed... URL: From habe36 at gmail.com Wed Mar 4 03:22:42 2015 From: habe36 at gmail.com (ABE Hiroshi) Date: Wed, 4 Mar 2015 17:22:42 +0900 Subject: [Paraview] Vector Glyph with FieldData Message-ID: <65B6BF06-6FD1-4729-8AB8-ECFFA12D69F7@gmail.com> Dear All, I am new to the ParaView. The software is quite nice and I can use it without any problems in many cases. But I get a trouble in rendering 2D vector with my vtk file which contains ?Field Data? that is: # vtk DataFile Version 2.0 mag.vtk, Created by Freefem++ ASCII DATASET UNSTRUCTURED_GRID POINTS 46764 float ? FIELD FieldData 1 mag.field 2 94956 float 2.45639014e+00 -6.87174034e+00 1.62697911e+00 -8.08913136e+00 ? This is actually 2D FEM magnetic field data (Hx, Hy) produced by FreeFem++. Loading the vtk file(mag.vtk) to ParaView and I can see ?mag.field? in the ParaView?s menu and ?Magnitude/X/Y? next to the menu. Then select ?mag.vtk? in Pipeline Browser and click Glyph icon in the ParaView menu to see some weird Arrow in RenderView window. I expect something in ?Vectors? in "Active Attributes? in ?Properties? panel but the menu is empty. I would be really obliged if you could tell me the missing things in my procedure to show vector field with Arrow Glyph. My Env. is : iMac 21.5 inch Late 2013 (16GB main memory, Core i5 2.9GHz, NVIDIA GeForce GT 750M) Mac OS X 10.9.5 ParaView 4.3.1 64 bit And I have some documents, ParaViewTutorial42.pdf TheParaViewGuide-v4.3-CC-Edition.pdf ABE Hiroshi from Tokorozawa, JAPAN From houssen at ipgp.fr Wed Mar 4 06:15:10 2015 From: houssen at ipgp.fr (houssen) Date: Wed, 04 Mar 2015 12:15:10 +0100 Subject: [Paraview] =?utf-8?q?=5BEXTERNAL=5D__How_to_check_for_duplicate_n?= =?utf-8?q?odes_=3F?= In-Reply-To: References: <025244773badb338ada629a6aecdb24a@imap.ipgp.fr> Message-ID: <3a87ceaed23fd0c5d0f6693bcf6f9a29@imap.ipgp.fr> OK, clean to grid (that I didn't know) gets rid of duplicate nodes. For debugging (creating our own hdf5 to import/export data between solvers) and or checking (data received from elsewhere) purposes, I was more looking for a way to SEE duplicate nodes (red ball in the 3D viewpoint and/or spreadsheet listing duplicate nodes for instance) to know if the data contains or not some duplicate nodes : I guess I can do that with python, but however, this seems a bit complex for a simple check. (I believe something was already doing that) Franck Le 2015-03-03 19:12, Scott, W Alan a ?crit?: > As Ken said, you get rid of duplicate nodes with Clean to Grid. I > wonder if you could check for duplicate nodes using the Spreadsheet > View, then sort on the cell locations? > > Alan > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of > houssen > Sent: Tuesday, March 03, 2015 6:59 AM > To: paraview at paraview.org > Subject: [EXTERNAL] [Paraview] How to check for duplicate nodes ? > > Hello, > > I have data (nodes and cells like HEXA8) on screen (open xmdf data) : > how to check for duplicate nodes ? > > Thanks, > > Franck > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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: 3lines.png Type: image/png Size: 121259 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 3lines_cleantogrid.png Type: image/png Size: 109077 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: checkDuplicateNodes.xmf Type: application/xml Size: 856 bytes Desc: not available URL: From felipe.bordeu at ec-nantes.fr Wed Mar 4 11:04:29 2015 From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu) Date: Wed, 04 Mar 2015 17:04:29 +0100 Subject: [Paraview] Annotate time filter - regard real time - error in code after test In-Reply-To: References: , , , , , , , , , , , , , , , , , , , , , , <54F485D8.3040702@ec-nantes.fr>, , , , , , , <54F5711B.8080205@ec-nantes.fr>, Message-ID: <54F72D0D.8000705@ec-nantes.fr> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 what is the error message???? Le 03/03/2015 14:06, Madalena S. Malhadas a ?crit : > Dear all, > > I tryed to make the time conversion in the script but i have an error. When i put this > > programmableFilter1.Script = 'pdo = self.GetOutput();\npdo.ShallowCopy(self.GetInput());\na = self.GetInput().GetInformation().Get(pdo.DATA_TIME_STEP());\n# this is your convertion routine\ntime_label = "Days from 12/12/1800 = " + str(a*100) + ":" + str((a*100)%2) + " ...days"\nlabel = vtk.vtkStringArray();\nlabel.SetNumberOfComponents(1);\nlabel.Resize(1);\nlabel.SetName("TimeLabel");\nlabel.SetValue(0,time_label);\npdo.GetFieldData().AddArray(label)\n' > > in the script box via paraview i get error. Do you know how to solve the error. > > Madalena > ------------------------- > From: nenasantos at hotmail.com > To: felipe.bordeu at ec-nantes.fr; paraview at paraview.org > Date: Tue, 3 Mar 2015 09:33:39 +0000 > Subject: Re: [Paraview] Annotate time filter - regard real time - error in code after test > > Thank you very much. > > ------------------------- > Date: Tue, 3 Mar 2015 09:30:19 +0100 > From: felipe.bordeu at ec-nantes.fr > To: paraview at paraview.org > Subject: Re: [Paraview] Annotate time filter - regard real time - error in code after test > > > > > > Please keep the discussion to the mailing list so others can > benefit-from/contribute-to the conversion. > > the code I send is for the programmable filter!!! > > if you are using a python script these are the lines to use (generated with python trace in ParaView): > the code in the Script variable of the programmable filter is always very ugly. you can put the source in a file extra file and use the execfile() function of python to call it. > > #--- begin code --- > # create a new 'Programmable Filter' > programmableFilter1 = ProgrammableFilter(Input=waterPropertiesnc) > > # Properties modified on programmableFilter1 > programmableFilter1.Script = 'pdo = self.GetOutput();\npdo.ShallowCopy(self.GetInput());\na = self.GetInput().GetInformation().Get(pdo.DATA_TIME_STEP());\n# this is your convertion routine\ntime_label = "Days from 12/12/1800 = " + str(a*100) + ":" + str((a*100)%2) + " ...days"\nlabel = vtk.vtkStringArray();\nlabel.SetNumberOfComponents(1);\nlabel.Resize(1);\nlabel.SetName("TimeLabel");\nlabel.SetValue(0,time_label);\npdo.GetFieldData().AddArray(label)\n' > > programmableFilter1.RequestInformationScript = '' > programmableFilter1.RequestUpdateExtentScript = '' > programmableFilter1.PythonPath = '' > > annotateGlobalData1 = AnnotateGlobalData(Input=programmableFilter1) > > # show data in view > annotateGlobalData1Display = Show(annotateGlobalData1, renderView1) > > #--- end code --- > > don?t forget to do the time conversion in the script!!! > > > Felipe > > Le 02/03/2015 17:09, Madalena S. Malhadas a ?crit : > > Hi Felipe, > > > I am a new user of paraview/python, so i Have dificult to understand where i have to place the code in my script. > > > My script read a nc file, then i use the annotate time filter to extract the time in file, but apears numbers (equivalent to seconds) > > > Then i include your code after call annotate time filter but i get an error. > > > Attached i send my scritp and if possible can you see the part of the time conversions and understand what ihave wrong. For me is to difficult to understand since i am novate in programming. > > > Thank you very much > > > Madalena > > > ------------------------- > > From: nenasantos at hotmail.com > > To: felipe.bordeu at ec-nantes.fr > > Date: Mon, 2 Mar 2015 15:49:15 +0000 > > CC: paraview at paraview.org > > Subject: Re: [Paraview] Annotate time filter - regard real time > > > Thank you very much! I will test now. > > > Kind regards > > > ------------------------- > > Date: Mon, 2 Mar 2015 16:46:32 +0100 > > From: felipe.bordeu at ec-nantes.fr > > CC: paraview at paraview.org > > Subject: Re: [Paraview] Annotate time filter - regard real time > > > > to generate a string from you field data (using a ProgrammableFilter): > > > script: > > > pdo = self.GetOutput(); > > pdo.ShallowCopy(self.GetInput()); > > a = self.GetInput().GetInformation().Get(pdo.DATA_TIME_STEP()); > > # this is your convertion routine > > time_label = "Days from 12/12/1800 = " + str(a*100) + ":" + str((a*100)%2) + " ...days" > > label = vtk.vtkStringArray(); > > label.SetNumberOfComponents(1); > > label.Resize(1); > > label.SetName("TimeLabel"); > > label.SetValue(0,time_label); > > pdo.GetFieldData().AddArray(label) > > > del label > > > then you use a AnnotateGlobalData Filter. > > > Done > > > > > > Le 02/03/2015 15:07, Madalena S. Malhadas a ?crit : > > > But how do I do it? Can you explain the steps please? > > > > Regards > > > Madalena > > > > ------------------------- > > > From: felipe.bordeu at ec-nantes.fr > > > Date: Mon, 2 Mar 2015 14:18:06 +0100 > > > CC: paraview at paraview.org > > > Subject: Re: [Paraview] Annotate time filter - regard real time > > > > you can use the python programable filter to create a field data with the date (in string) and use a annotate field data filter. > > > > Felipe > > > Le 27 f?vr. 2015 ? 14:50, Madalena S. Malhadas > a ?crit : > > > > > Dear paraview users, > > > > I have a question over the use of Annotate time filter in Paraview. I have a paraview script that read netcdf data which has time axis given as "days since 1970-01-01 > > > 00:00" (Epoch Time). This gives problem if I want to show the real time of the data in the animation window. What I would like to have shown are the date as > > > 4-8-2003, 00:00 etc. and it shows big number like 19521, 19522. > > > > Does anyone have some idea how to solve the problem? > > > > Thanks a lot! > > > > Madalena > > > _______________________________________________ > > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > > > 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 > > _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview - -- Felipe Bordeu Weldt Ing?nieur de Recherche - ------------------------------------- T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS 6183 ?cole Centrale Nantes 1 Rue de La No?, 44321 Nantes, FRANCE - ------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU9yz5AAoJEE/fMfNgU9/DbTIH/jlA85WMsJQ2LikhPtpbPqz8 QyXa2HHVHmKrmRgYQeWsXY3mtIaJZgjKJQxaEByNu7xAVWxFDW8C2a0ZoV+NH90f WX2r/jwWF8AWnJk/IV+8r0Yitsj9TtYu1YGC5ZD+g6at5zLkyCEU5oocXXQex87y OdDIkFQi1XmKFZDHHoIgynsDVpD+JTvnXD/lgzE/XFtETlceKRuOGixwbC87/tcJ 3XFeaFd4us70LgvH0USx1/3jPH52k0wPJbhF85YiPKH5sNUEOm4JIKht/Ivhpk2o n5WKfmtIwtMy9Ti2EHjT3+RQGHO3c16WuHv35NqzypPCiRYZ54evDS+gnMWeeSQ= =dMXS -----END PGP SIGNATURE----- -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.wittenburg at kitware.com Wed Mar 4 12:15:44 2015 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Wed, 4 Mar 2015 10:15:44 -0700 Subject: [Paraview] Mismatched image size returned from ViewPort image render In-Reply-To: <54F61A57.8050704@ornl.gov> References: <54F61A57.8050704@ornl.gov> Message-ID: Hi Jordan, I wonder if that is the issue that is addressed in this topic: http://review.source.kitware.com/#/t/5425/ If so, I think this fix may be merged soon, as it has already been approved. If you built the ParaView release you're running yourself, you could always try to check out the topic and see if it fixes the issue you're seeing. Cheers, Scott On Tue, Mar 3, 2015 at 1:32 PM, Jordan Deyton wrote: > ParaView gurus, > > I am working on a project that uses the JSON RPC protocols provided by > ParaViewWeb. I've noticed that the image quality for ViewPorts seems bad > regardless of what is specified in the call to viewport.image.render (docs > here: http://www.paraview.org/ParaView3/Doc/Nightly/www/js- > doc/index.html#!/api/protocols.ParaViewWebViewPortImageDelivery ). > > After decoding the returned image from the Base64 encoding, the JPEG image > comes out as 636x420, while the quality is listed as 100 and the original > size is 1440x850. > > The JSON object passed to viewport.image.render looks like > > {"args":[{ > "localtime":1425413914878, > "view":-1, > "size":[1440,850], > "quality":100}] > } > > While the returned object from that RPC call looks like > > { > "image": "very long encoded image text here", > "localTime": 0, > "stale": false, > "size": [1440,850], > "format": "jpeg;base64", > "global_id": "315", > "mtime": 3068929, > "workTime": 1 > } > > I've used two separate Base64 decoders, and both result in a JPEG image > that is 636x420, not the reported 1440x850. > > Any idea what could be the problem here? Is this a bug in ParaViewWeb? I'm > running the latest stable ParaView release (4.3.1) on RHEL. > > Thanks, > Jordan > > -- > Jordan Deyton > Oak Ridge National Laboratory > Telephone: (865) 574-1091 > Email: deytonjh at ornl.gov > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From danielbruno at gmail.com Wed Mar 4 13:05:22 2015 From: danielbruno at gmail.com (Daniel Bruno) Date: Wed, 4 Mar 2015 15:05:22 -0300 Subject: [Paraview] Density of streamlines using StreamTracerWithCustomSource Message-ID: Hello all. I'm using StreamTracerWithCustomSource filter to generate streamlines shed from a specific surface. There are no problems to achieve my goals but I was not able to find a way to control the density of streamlines. Is it possible to control the number of streamlines that are shed when using StreamTracerWithCustomSource filter? Thank you so much for your help. Regards, Daniel. -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Wed Mar 4 13:33:10 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 4 Mar 2015 13:33:10 -0500 Subject: [Paraview] Density of streamlines using StreamTracerWithCustomSource In-Reply-To: References: Message-ID: I believe that the streamline density is based on the points from the custom source. If you add or remove points in the custom source you should get more or less streamlines, respectively. On Wed, Mar 4, 2015 at 1:05 PM, Daniel Bruno wrote: > Hello all. > > I'm using StreamTracerWithCustomSource filter to generate streamlines shed > from a specific surface. There are no problems to achieve my goals but I > was not able to find a way to control the density of streamlines. > > Is it possible to control the number of streamlines that are shed when > using StreamTracerWithCustomSource filter? > > Thank you so much for your help. > > Regards, > > > Daniel. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 Wed Mar 4 14:12:42 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Wed, 04 Mar 2015 21:12:42 +0200 Subject: [Paraview] [EXTERNAL] Fwd: Volume rendering with RGBA data In-Reply-To: References: Message-ID: <54F7592A.70009@gmail.com> Hi all, I also ran into some volume rendering issues. The issues occur when switching the data arrays to visualize and range from completely wrong visualizations to no visualization at all. The problem only occurs with the "GPU Based" renderer, the "Ray Cast" and "Texture Mapping" renderer work fine, though the result looks always different. I can reproduce the issues only for large data sets (>50 million points), but already the wavelet source with 400x400x400 points and a calculator filter (to get a second dataset) does the trick. I attached a state file which leads immediately to the following error: > ERROR: In /home/abuild/rpmbuild/BUILD/ParaView-v4.3.1-source/VTK/Rendering/OpenGL/vtkShaderProgram2.cxx, line 471 > vtkShaderProgram2 (0x5d9cf10): failed at glAttachShader 1 OpenGL errors detected > 0 : (1282) Invalid operation Hope this helps to track these issues down. -Armin On 02/25/2015 04:27 PM, Utkarsh Ayachit wrote: > As a side note, this is indeed going to be supported by the upcoming > changes to upgrade VTK's rendering pipeline to use OpenGL 2 features > (Aashish, please correct me if I am wrong). > > Utkarsh > > On Mon, Feb 23, 2015 at 4:28 PM, Scott, W Alan wrote: >> Ruq, >> >> Volume rendering vectors appears to have multiple bugs. And you are correct >> ? volume rendering a non map scalar vector appears to turn on map scalars. >> >> I wrote up bugs. >> >> >> >> http://www.paraview.org/Bug/view.php?id=15340 >> >> http://www.paraview.org/Bug/view.php?id=15339 >> >> >> >> I marked a duplicate, 14242, as targeted for PV 4.4. >> >> >> >> >> >> Alan >> >> >> >> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Xu, >> Ruqing >> Sent: Sunday, February 22, 2015 4:24 PM >> To: paraview at paraview.org >> Subject: [EXTERNAL] [Paraview] Fwd: Volume rendering with RGBA data >> >> >> >> Hello, >> >> >> >> I'm displaying my simple 3D data set on a structured grid. With a >> 4-component unsigned integer vector on each point, and after turning off the >> "map scalar" option in the displays, I have been able to present my data >> with the given RGBA values in the "surface" or "points" mode. In the >> "volume" mode, however, this breaks down and the colors & opacity are still >> mapped from the individual components of the 4-vectors as scalars. >> >> Am I missing anything? Or is this a known issue? I'm using ParaView 4.3.1, >> Thanks. >> >> -Ruq >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 -------------- From utkarsh.ayachit at kitware.com Wed Mar 4 15:37:21 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 4 Mar 2015 13:37:21 -0700 Subject: [Paraview] Superbuilds and clusters In-Reply-To: <6f1c065114704eaea84a269221d9e5ab@ES05AMSNLNT.srn.sandia.gov> References: <6f1c065114704eaea84a269221d9e5ab@ES05AMSNLNT.srn.sandia.gov> Message-ID: Alan, What do you mean by it isn't remote rendering? Does it say display is not accessible and hence cannot use remote rendering? Don't you have X server running? If not, then use, you'd need to use OSMesa. Utkarsh On Tue, Mar 3, 2015 at 11:09 AM, Scott, W Alan wrote: > I am trying to use the superbuild to create pvserver on a cluster. It > appears to be running in parallel, but isn?t remote rendering. The issue i > believe is that the Superbuild isn?t building with Mesa. I have done an > ldd for mesa in the lib/paraview4-3 directory, and when I turn on Show > Annotation, Remote Rendering says no. > > I am turning on ENABLE_mesa (-DENABLE_mesa:BOOL=ON). Should I be using > osmesa instead? Any ideas what I am doing wrong? > > 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 > From teojgor at gmail.com Wed Mar 4 18:26:04 2015 From: teojgor at gmail.com (Teo Ioannis) Date: Thu, 5 Mar 2015 01:26:04 +0200 Subject: [Paraview] Rotational Degrees of Freedom Message-ID: In many applications particularly engineering ones, structural finite elements are used such as beams and shells. In the case of beams, in addition to degrees of freedom representing translations there exist rotational degrees of freedom. Is there a way to make paraview 'recognize' these rotational degrees of freedom so that it's able to produce a correct deformed shape visualization? Thank you for your help. Manitaras Theofilos -------------- next part -------------- An HTML attachment was scrubbed... URL: From nikos.beratlis at gmail.com Wed Mar 4 18:57:58 2015 From: nikos.beratlis at gmail.com (Nikolaos Beratlis) Date: Wed, 4 Mar 2015 18:57:58 -0500 Subject: [Paraview] Help with producing a X Y plot of a scalar Message-ID: Hi, I have a cartesian grid and two scalars U, W that I read into paraview as follows: ../grid3dc_vxvyvz_VP.h5sp:/X ../grid3dc_vxvyvz_VP.h5sp:/Y ../grid3dc_vxvyvz_VP.h5sp:/Z ../oy_tmavg_cyl2car.h5sp:/var3d ../oy_tmavg_cyl2car.h5sp:/var3d I then multiply U*W using the calculator to get a new variable UW. What I want to do is create a scatter plot of the variable UW at a particular a slice in the domain where in the X-axis I have U variable and in the Y-axis I have W variable. The end result would like this ? Paraview has a function called scatter plot but it only allows to specify one axis, the X-axis data. How can I specify the Y-axis to be a different variable? Regards, Nikos -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: scatter plot.png Type: image/png Size: 103198 bytes Desc: not available URL: From wascott at sandia.gov Wed Mar 4 21:32:43 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 5 Mar 2015 02:32:43 +0000 Subject: [Paraview] [EXTERNAL] Re: Superbuilds and clusters In-Reply-To: References: <6f1c065114704eaea84a269221d9e5ab@ES05AMSNLNT.srn.sandia.gov> Message-ID: When I try to search the binaries (i.e., pvserver and associated libraries), as follows, I don't see mesa. When I do this search on a good, I made it myself build, I do see mesa. cd ....../lib/paraview.4.3 ldd * | egrep -i mesa Next, when I try to run with MPI, on the nodes of the clusters, 8 processes, I get the following: "Display is not accessible on the server side. Remote rendering will be disabled.". And, as expected, when I visualize wavelet, I see remote rendering is off. This is with a remote rendering threshold of 0. I also have Show Annotation on. OK, I don't know what you are talking about, so I assume I am not running an X server. Let me rebuild overnight with OSMesa. What is the difference? Alan -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Wednesday, March 04, 2015 1:37 PM To: Scott, W Alan Cc: paraview at paraview.org Subject: [EXTERNAL] Re: [Paraview] Superbuilds and clusters Alan, What do you mean by it isn't remote rendering? Does it say display is not accessible and hence cannot use remote rendering? Don't you have X server running? If not, then use, you'd need to use OSMesa. Utkarsh On Tue, Mar 3, 2015 at 11:09 AM, Scott, W Alan wrote: > I am trying to use the superbuild to create pvserver on a cluster. It > appears to be running in parallel, but isn?t remote rendering. The issue i > believe is that the Superbuild isn?t building with Mesa. I have done an > ldd for mesa in the lib/paraview4-3 directory, and when I turn on Show > Annotation, Remote Rendering says no. > > I am turning on ENABLE_mesa (-DENABLE_mesa:BOOL=ON). Should I be > using osmesa instead? Any ideas what I am doing wrong? > > 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 > From gaspare.argento at gmail.com Thu Mar 5 04:19:53 2015 From: gaspare.argento at gmail.com (Gaspare Argento) Date: Thu, 5 Mar 2015 10:19:53 +0100 Subject: [Paraview] PROBLEM IMPORTING ENSIGHT SOS FILE Message-ID: Hi everybody, I have a problem when importing an Ensight .sos file in Paraview. Loading the .sos file I get the following message (I attach only the lines about the first *.case file, because these are repeated for all *case files listed in the .sos): ========================================================================================================================== ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSightReader.cxx, line 340 vtkPGenericEnSightReader (000000000DC5E6E0): Unable to open file: J:\SERVER\CALC\VOF_TEST\Calculation\VOF_TEST\3D_EnSight\/VOF_TEST_DOM_0.case ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSightReader.cxx, line 340 vtkPGenericEnSightReader (000000000DC5E6E0): Unable to open file: J:\SERVER\CALC\VOF_TEST\Calculation\VOF_TEST\3D_EnSight\/VOF_TEST_DOM_0.case ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSightReader.cxx, line 811 vtkPGenericEnSightReader (000000000DC5E6E0): Error determining EnSightVersion ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx, line 784 vtkCompositeDataPipeline (000000000DBF33A0): Algorithm vtkPGenericEnSightReader(000000000DC5E6E0) returned failure for request: vtkInformation (000000000DEC2F60) Debug: Off Modified Time: 160501 Reference Count: 1 Registered Events: (none) Request: REQUEST_INFORMATION ALGORITHM_AFTER_FORWARD: 1 FORWARD_DIRECTION: 0 ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\VTKExtensions\Default\vtkPVEnSightMasterServerReader2.cxx, line 255 vtkPVEnSightMasterServerReader2 (0000000018693C90): Error reading case file on at least one node. ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx, line 784 vtkPVCompositeDataPipeline (0000000017BEA7E0): Algorithm vtkPVEnSightMasterServerReader2(0000000018693C90) returned failure for request: vtkInformation (0000000016F654A0) Debug: Off Modified Time: 6920520 Reference Count: 1 Registered Events: (none) Request: REQUEST_INFORMATION ALGORITHM_AFTER_FORWARD: 1 FORWARD_DIRECTION: 0 ========================================================================================================================== Below you can find an extract of the loaded .sos file (only the lines relative to the first server): ========================================================================================================================== # # Example Server-of-server case file # parts in <> have to be filled in by the user # FORMAT type: master_server gold SERVERS number of servers: 64 #Server 1 machine id: MACHINE_NAME executable: casefile: J:/SERVER/CALC/VOF_TEST/Calculation/VOF_TEST/3D_EnSight/DOM_0/VOF_TEST_DOM_0.case ========================================================================================================================== If I load the *.case files one by one I have no problem. Thanks for your support Gaspare From nenasantos at hotmail.com Thu Mar 5 04:30:55 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Thu, 5 Mar 2015 09:30:55 +0000 Subject: [Paraview] How move a solid (eg., box)in two ways? In-Reply-To: References: <6f1c065114704eaea84a269221d9e5ab@ES05AMSNLNT.srn.sandia.gov>, , Message-ID: Dear all,I want to animate a solidd (like a box or parallel) backward and forward in a ciclic mode? Ho i do these with animation mode and keyframes? Kind regardsMadalena -------------- next part -------------- An HTML attachment was scrubbed... URL: From Michael.Bussler at visus.uni-stuttgart.de Thu Mar 5 06:58:05 2015 From: Michael.Bussler at visus.uni-stuttgart.de (=?iso-8859-1?Q?Michael_Bu=DFler?=) Date: Thu, 5 Mar 2015 11:58:05 +0000 Subject: [Paraview] How move a solid (eg., box)in two ways? In-Reply-To: References: <6f1c065114704eaea84a269221d9e5ab@ES05AMSNLNT.srn.sandia.gov>, , Message-ID: Hi Madalena, I suggest you use a transform node to move the objects. The translation parameters of that node should be animatable through the animation tab. Best, Michael -- Michael Bu?ler, Dipl.-Inf. Visualization Research Center, Universit?t Stuttgart (VISUS) Allmandring 19 70569 Stuttgart Germany mail: michael.bussler at visus.uni-stuttgart.de room: Allmandring 19 / 01.033 phone: +49 (0)711 / 685 88634 fax: +49 (0)711 / 685 88610 Von: ParaView [mailto:paraview-bounces at paraview.org] Im Auftrag von Madalena S. Malhadas Gesendet: Donnerstag, 5. M?rz 2015 10:31 An: Scott, W Alan; Utkarsh Ayachit Cc: paraview at paraview.org Betreff: Re: [Paraview] How move a solid (eg., box)in two ways? Dear all, I want to animate a solidd (like a box or parallel) backward and forward in a ciclic mode? Ho i do these with animation mode and keyframes? Kind regards Madalena -------------- next part -------------- An HTML attachment was scrubbed... URL: From deytonjh at ornl.gov Thu Mar 5 10:40:11 2015 From: deytonjh at ornl.gov (Deyton, Jordan H.) Date: Thu, 5 Mar 2015 15:40:11 +0000 Subject: [Paraview] Mismatched image size returned from ViewPort image render In-Reply-To: References: <54F61A57.8050704@ornl.gov>, Message-ID: <1425570009950.27346@ornl.gov> Scott, I'll take a look at building ParaView on the remote server when I next get a chance and see if that fixes the problem. Thanks, Jordan? ________________________________ From: Scott Wittenburg Sent: Wednesday, March 04, 2015 12:15 PM To: Deyton, Jordan H. Cc: paraview at paraview.org Subject: Re: [Paraview] Mismatched image size returned from ViewPort image render Hi Jordan, I wonder if that is the issue that is addressed in this topic: http://review.source.kitware.com/#/t/5425/ If so, I think this fix may be merged soon, as it has already been approved. If you built the ParaView release you're running yourself, you could always try to check out the topic and see if it fixes the issue you're seeing. Cheers, Scott On Tue, Mar 3, 2015 at 1:32 PM, Jordan Deyton > wrote: ParaView gurus, I am working on a project that uses the JSON RPC protocols provided by ParaViewWeb. I've noticed that the image quality for ViewPorts seems bad regardless of what is specified in the call to viewport.image.render (docs here: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/api/protocols.ParaViewWebViewPortImageDelivery ). After decoding the returned image from the Base64 encoding, the JPEG image comes out as 636x420, while the quality is listed as 100 and the original size is 1440x850. The JSON object passed to viewport.image.render looks like {"args":[{ "localtime":1425413914878, "view":-1, "size":[1440,850], "quality":100}] } While the returned object from that RPC call looks like { "image": "very long encoded image text here", "localTime": 0, "stale": false, "size": [1440,850], "format": "jpeg;base64", "global_id": "315", "mtime": 3068929, "workTime": 1 } I've used two separate Base64 decoders, and both result in a JPEG image that is 636x420, not the reported 1440x850. Any idea what could be the problem here? Is this a bug in ParaViewWeb? I'm running the latest stable ParaView release (4.3.1) on RHEL. Thanks, Jordan -- Jordan Deyton Oak Ridge National Laboratory Telephone: (865) 574-1091 Email: deytonjh at ornl.gov _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From canismajorwuff at gmail.com Thu Mar 5 12:26:47 2015 From: canismajorwuff at gmail.com (Canis Major) Date: Thu, 5 Mar 2015 18:26:47 +0100 Subject: [Paraview] 2D Rectangular grid import of XDMF/HDF5 files Message-ID: I have the following configuration of geometry in XDMF file xdmf2d.h5:/X xdmf2d.h5:/Y In Paraview I that Z axis has a dimension of 220 and Y has 82, X -- 0. Why is that? How can I fix it? Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nikos.beratlis at gmail.com Thu Mar 5 12:35:44 2015 From: nikos.beratlis at gmail.com (Nikolaos Beratlis) Date: Thu, 5 Mar 2015 12:35:44 -0500 Subject: [Paraview] Attribute recalculation at center Message-ID: HI, I have a cartesian grid which I read into paraview along with its attribute as follows: ../grid3dc_vxvyvz_VP.h5sp:/X ../grid3dc_vxvyvz_VP.h5sp:/Y ../grid3dc_vxvyvz_VP.h5sp:/Z ../u_tmavg_cyl2car.h5sp:/var3d ../w_tmavg_cyl2car.h5sp:/var3d The variables are 3D arrays of size 202 x 100 x 100 (NZ x NY x NX). I want to create new variables as: do k=2,NZ do j=1,NY do i=1,NX Wnew(i,j,k) = 0.5*( W(i,j,k-1) + W(i,j,k) ) enddo enddo enddo and do k=1,NZ do j=1,NY do i=2,NX Unew(i,j,k) = 0.5*( U(i-1,j,k) + U(i,j,k) ) enddo enddo enddo I try to use the calculator filter but there is no option to specify the indices. How can I do that within Paraview? -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Mar 5 12:39:33 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 5 Mar 2015 17:39:33 +0000 Subject: [Paraview] [EXTERNAL] PROBLEM IMPORTING ENSIGHT SOS FILE In-Reply-To: References: Message-ID: I just opened an .sos file, with a 16 file dataset, with ParaView 4.3.1. Worked fine. Linux, local server. * I wonder if you have a problem with your SOS file. * Mind posting a/the dataset? Alan -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Gaspare Argento Sent: Thursday, March 05, 2015 2:20 AM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] PROBLEM IMPORTING ENSIGHT SOS FILE Hi everybody, I have a problem when importing an Ensight .sos file in Paraview. Loading the .sos file I get the following message (I attach only the lines about the first *.case file, because these are repeated for all *case files listed in the .sos): ========================================================================================================================== ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSightReader.cxx, line 340 vtkPGenericEnSightReader (000000000DC5E6E0): Unable to open file: J:\SERVER\CALC\VOF_TEST\Calculation\VOF_TEST\3D_EnSight\/VOF_TEST_DOM_0.case ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSightReader.cxx, line 340 vtkPGenericEnSightReader (000000000DC5E6E0): Unable to open file: J:\SERVER\CALC\VOF_TEST\Calculation\VOF_TEST\3D_EnSight\/VOF_TEST_DOM_0.case ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSightReader.cxx, line 811 vtkPGenericEnSightReader (000000000DC5E6E0): Error determining EnSightVersion ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx, line 784 vtkCompositeDataPipeline (000000000DBF33A0): Algorithm vtkPGenericEnSightReader(000000000DC5E6E0) returned failure for request: vtkInformation (000000000DEC2F60) Debug: Off Modified Time: 160501 Reference Count: 1 Registered Events: (none) Request: REQUEST_INFORMATION ALGORITHM_AFTER_FORWARD: 1 FORWARD_DIRECTION: 0 ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\VTKExtensions\Default\vtkPVEnSightMasterServerReader2.cxx, line 255 vtkPVEnSightMasterServerReader2 (0000000018693C90): Error reading case file on at least one node. ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx, line 784 vtkPVCompositeDataPipeline (0000000017BEA7E0): Algorithm vtkPVEnSightMasterServerReader2(0000000018693C90) returned failure for request: vtkInformation (0000000016F654A0) Debug: Off Modified Time: 6920520 Reference Count: 1 Registered Events: (none) Request: REQUEST_INFORMATION ALGORITHM_AFTER_FORWARD: 1 FORWARD_DIRECTION: 0 ========================================================================================================================== Below you can find an extract of the loaded .sos file (only the lines relative to the first server): ========================================================================================================================== # # Example Server-of-server case file # parts in <> have to be filled in by the user # FORMAT type: master_server gold SERVERS number of servers: 64 #Server 1 machine id: MACHINE_NAME executable: casefile: J:/SERVER/CALC/VOF_TEST/Calculation/VOF_TEST/3D_EnSight/DOM_0/VOF_TEST_DOM_0.case ========================================================================================================================== If I load the *.case files one by one I have no problem. Thanks for your support Gaspare _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 louie.cardone-noott at linacre.ox.ac.uk Thu Mar 5 12:59:50 2015 From: louie.cardone-noott at linacre.ox.ac.uk (Louie Cardone-Noott) Date: Thu, 5 Mar 2015 17:59:50 +0000 Subject: [Paraview] 2D Rectangular grid import of XDMF/HDF5 files In-Reply-To: References: Message-ID: Is VXVY a valid GeometryType? It doesn't appear in http://www.xdmf.org/index.php/XDMF_Model_and_Format On 5 March 2015 at 17:26, Canis Major wrote: > I have the following configuration of geometry in XDMF file > > > > > > > > xdmf2d.h5:/X > > > xdmf2d.h5:/Y > > > > > > In Paraview I that Z axis has a dimension of 220 and Y has 82, X -- 0. Why is that? How can I fix it? > > Thank you. > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From leonardopessanha74 at gmail.com Thu Mar 5 14:18:15 2015 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Thu, 5 Mar 2015 16:18:15 -0300 Subject: [Paraview] SEG-Y seismic data loading Message-ID: Hi, I would like to apologize, i do not know how to answer a question in the mailing list correctly, i think the way i am doing it right now is going to appear as a new question There is no easy way of doing it, to see SEG-Y data in paraview, i used another software to export the data to ASCII txt So i exported to a 4 collumn text file with "X" "Y" "Z" "AMPLITUDE", imported in paraview, table to structured grid points filter, and used the scalar variable amplitude to color the object Hope it helped! -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Mar 5 16:43:58 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 5 Mar 2015 21:43:58 +0000 Subject: [Paraview] [EXTERNAL] Re: Superbuilds and clusters In-Reply-To: References: <6f1c065114704eaea84a269221d9e5ab@ES05AMSNLNT.srn.sandia.gov> Message-ID: Thanks Utkarsh - that worked. I actually misinterpreted OSMesa as Operating System Mesa - but I believe it is Off Screen Mesa. The former is what I created, the latter is what I needed. OSMesa works. Alan -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan Sent: Wednesday, March 04, 2015 7:33 PM To: Utkarsh Ayachit Cc: paraview at paraview.org Subject: Re: [Paraview] [EXTERNAL] Re: Superbuilds and clusters When I try to search the binaries (i.e., pvserver and associated libraries), as follows, I don't see mesa. When I do this search on a good, I made it myself build, I do see mesa. cd ....../lib/paraview.4.3 ldd * | egrep -i mesa Next, when I try to run with MPI, on the nodes of the clusters, 8 processes, I get the following: "Display is not accessible on the server side. Remote rendering will be disabled.". And, as expected, when I visualize wavelet, I see remote rendering is off. This is with a remote rendering threshold of 0. I also have Show Annotation on. OK, I don't know what you are talking about, so I assume I am not running an X server. Let me rebuild overnight with OSMesa. What is the difference? Alan -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Wednesday, March 04, 2015 1:37 PM To: Scott, W Alan Cc: paraview at paraview.org Subject: [EXTERNAL] Re: [Paraview] Superbuilds and clusters Alan, What do you mean by it isn't remote rendering? Does it say display is not accessible and hence cannot use remote rendering? Don't you have X server running? If not, then use, you'd need to use OSMesa. Utkarsh On Tue, Mar 3, 2015 at 11:09 AM, Scott, W Alan wrote: > I am trying to use the superbuild to create pvserver on a cluster. It > appears to be running in parallel, but isn?t remote rendering. The issue i > believe is that the Superbuild isn?t building with Mesa. I have done an > ldd for mesa in the lib/paraview4-3 directory, and when I turn on Show > Annotation, Remote Rendering says no. > > I am turning on ENABLE_mesa (-DENABLE_mesa:BOOL=ON). Should I be > using osmesa instead? Any ideas what I am doing wrong? > > 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 > _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 arctica1963 at gmail.com Thu Mar 5 17:14:30 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Thu, 5 Mar 2015 22:14:30 +0000 Subject: [Paraview] SEG-Y seismic data loading In-Reply-To: References: Message-ID: Hi Leo, Thanks for the suggestions. What software did you use to export the data? Cheers Lester On 5 March 2015 at 19:18, L?o Pessanha wrote: > Hi, > > I would like to apologize, i do not know how to answer a question in the > mailing list correctly, i think the way i am doing it right now is going to > appear as a new question > > There is no easy way of doing it, to see SEG-Y data in paraview, i used > another software to export the data to ASCII txt > > So i exported to a 4 collumn text file with "X" "Y" "Z" "AMPLITUDE", > imported in paraview, table to structured grid points filter, and used the > scalar variable amplitude to color the object > > Hope it helped! > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nikos.beratlis at gmail.com Thu Mar 5 18:08:17 2015 From: nikos.beratlis at gmail.com (Nikolaos Beratlis) Date: Thu, 5 Mar 2015 18:08:17 -0500 Subject: [Paraview] XY plot of time series Message-ID: Hi, I am trying to create a plot of a time series. I read one file (0001) as follows: ../VPfield_files/grid3dc_vxvyvz_VP.h5sp:/X ../VPfield_files/grid3dc_vxvyvz_VP.h5sp:/Y ../VPfield_files/grid3dc_vxvyvz_VP.h5sp:/Z ../VPfield_files/ufluct.0001.h5sp:/var3d ../VPfield_files/wfluct.0001.h5sp:/var3d and I create a XY plot of the data as shown below: I want to superimpose on the same plot the data from the other files (0002-0025). Because the grid files are large and there are many files in the series I would like to do it without loading all the data simultaneously because I would ran out of memory. Is there a way to do this efficiently? Regards, Nikos ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2015-03-05 at 5.00.24 PM.png Type: image/png Size: 42372 bytes Desc: not available URL: From michael.l.mason at gmail.com Fri Mar 6 00:06:50 2015 From: michael.l.mason at gmail.com (Michael Mason) Date: Fri, 6 Mar 2015 00:06:50 -0500 Subject: [Paraview] Obtain pixel value of a line source using Python Message-ID: Hi, I have a line created by using a Line source and it's passing through a 3D volume of values that are non-uniform (I.e., the values inside the 3D volume are not constant, they fluctuate spatially and temporally). Is there a way to determine the values within the 3D volume that the line is passing through using Python? Or, is there a way to integrate (or accumulate) the values in the 3D volume through which the line passes. If this is possible, I'm guessing a step size will need to be provided to specify how often to spatially sample the line as it passes through the volume? Thanks for your time, Mike From gaspare.argento at gmail.com Fri Mar 6 02:46:50 2015 From: gaspare.argento at gmail.com (Gaspare Argento) Date: Fri, 6 Mar 2015 08:46:50 +0100 Subject: [Paraview] [EXTERNAL] PROBLEM IMPORTING ENSIGHT SOS FILE In-Reply-To: References: Message-ID: Hi Scott, thanks for answering. I'm sorry but I didn't understand exactly what do you mean: could you please explain it better? Did you ask me to attach the .sos file? Thanks, Gaspare 2015-03-05 18:39 GMT+01:00 Scott, W Alan : > I just opened an .sos file, with a 16 file dataset, with ParaView 4.3.1. Worked fine. Linux, local server. > > * I wonder if you have a problem with your SOS file. > * Mind posting a/the dataset? > > Alan > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Gaspare Argento > Sent: Thursday, March 05, 2015 2:20 AM > To: paraview at paraview.org > Subject: [EXTERNAL] [Paraview] PROBLEM IMPORTING ENSIGHT SOS FILE > > Hi everybody, > > I have a problem when importing an Ensight .sos file in Paraview. > > Loading the .sos file I get the following message (I attach only the lines about the first *.case file, because these are repeated for all *case files listed in the .sos): > ========================================================================================================================== > > ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSightReader.cxx, > line 340 > > vtkPGenericEnSightReader (000000000DC5E6E0): Unable to open file: > J:\SERVER\CALC\VOF_TEST\Calculation\VOF_TEST\3D_EnSight\/VOF_TEST_DOM_0.case > > > > > > ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSightReader.cxx, > line 340 > > vtkPGenericEnSightReader (000000000DC5E6E0): Unable to open file: > J:\SERVER\CALC\VOF_TEST\Calculation\VOF_TEST\3D_EnSight\/VOF_TEST_DOM_0.case > > > > > > ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSightReader.cxx, > line 811 > > vtkPGenericEnSightReader (000000000DC5E6E0): Error determining EnSightVersion > > > > > > ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx, > line 784 > > vtkCompositeDataPipeline (000000000DBF33A0): Algorithm > vtkPGenericEnSightReader(000000000DC5E6E0) returned failure for > request: vtkInformation (000000000DEC2F60) > > Debug: Off > > Modified Time: 160501 > > Reference Count: 1 > > Registered Events: (none) > > Request: REQUEST_INFORMATION > > ALGORITHM_AFTER_FORWARD: 1 > > FORWARD_DIRECTION: 0 > > > > > > ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\VTKExtensions\Default\vtkPVEnSightMasterServerReader2.cxx, > line 255 > > vtkPVEnSightMasterServerReader2 (0000000018693C90): Error reading case file on at least one node. > > > > > > ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx, > line 784 > > vtkPVCompositeDataPipeline (0000000017BEA7E0): Algorithm > vtkPVEnSightMasterServerReader2(0000000018693C90) returned failure for > request: vtkInformation (0000000016F654A0) > > Debug: Off > > Modified Time: 6920520 > > Reference Count: 1 > > Registered Events: (none) > > Request: REQUEST_INFORMATION > > ALGORITHM_AFTER_FORWARD: 1 > > FORWARD_DIRECTION: 0 > > ========================================================================================================================== > > > > Below you can find an extract of the loaded .sos file (only the lines relative to the first server): > ========================================================================================================================== > > # > > # Example Server-of-server case file > > # parts in <> have to be filled in by the user > > # > > FORMAT > > type: master_server gold > > SERVERS > > number of servers: 64 > > #Server 1 > > machine id: MACHINE_NAME > > executable: > > casefile: J:/SERVER/CALC/VOF_TEST/Calculation/VOF_TEST/3D_EnSight/DOM_0/VOF_TEST_DOM_0.case > > ========================================================================================================================== > > > > If I load the *.case files one by one I have no problem. > > > > Thanks for your support > > Gaspare > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From Christophe.Dang at sidel.com Fri Mar 6 02:47:42 2015 From: Christophe.Dang at sidel.com (Dang, Christophe) Date: Fri, 6 Mar 2015 07:47:42 +0000 Subject: [Paraview] Rotational Degrees of Freedom In-Reply-To: References: Message-ID: Hello, > De : ParaView [mailto:paraview-bounces at paraview.org] De la part de Teo Ioannis > Envoy? : jeudi 5 mars 2015 00:26 > > structural finite elements are used such as beams and shells. [...] > Is there a way to make paraview 'recognize' these rotational degrees of freedom > so that it's able to produce a correct deformed shape visualization? I don't know much ParaView, but to have a "realistic" rendering, the software should have the shape of the cross section of the beam or the thickness of the shell, to be able to rebuild an external surface. And I doubt ParaView has an available library of cross sections ar a ways to describe it, am I wrong? -- Christophe Dang Ngoc Chan Mechanical calculation engineer This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error), please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. From i.krukow at tu-braunschweig.de Fri Mar 6 05:36:01 2015 From: i.krukow at tu-braunschweig.de (Ian Krukow) Date: Fri, 06 Mar 2015 11:36:01 +0100 Subject: [Paraview] Load series of VTK files Message-ID: <54F98311.9010508@tu-braunschweig.de> Hi all, I want to load a series of VTU files, which are all stored in one directory, but not numbered in a way that ParaView recognises them as one series. In a python script, I can do it like this: import glob import paraview.simple as pv pattern = 'directory/*.vtu' files = glob.glob(pattern) reader = pv.XMLUnstructuredGridReader( FileName=files ) The directory may be an input parameter to the script. How can I transfer this into the GUI with the directory as a parameter? I have looked at python macros, but obviously it is not possible to define any parameters there. Is it possible to run a script from the python shell with a parameter? I also took a look at the Programmable Source. It should be a possible solution, but I have not found much explanation of what to do. Any ideas are welcome. Kind regards Ian From dkxls23 at gmail.com Fri Mar 6 05:56:27 2015 From: dkxls23 at gmail.com (dkxls23 at gmail.com) Date: Fri, 6 Mar 2015 10:56:27 +0000 Subject: [Paraview] Load series of VTK files In-Reply-To: <54F98311.9010508@tu-braunschweig.de> References: <54F98311.9010508@tu-braunschweig.de> Message-ID: Have you tried to name the files like this: fileName.0000.vtu fileName.0001.vtu fileName.0002.vtu ... ParaView should recognize them as a time series. That typically worked for me (cannot test it though at the moment). -Armin On Fri Mar 6 12:36:01 2015 GMT+0200, Ian Krukow wrote: > Hi all, > > I want to load a series of VTU files, which are all stored in one > directory, but not numbered in a way that ParaView recognises them as > one series. In a python script, I can do it like this: > > import glob > import paraview.simple as pv > pattern = 'directory/*.vtu' > files = glob.glob(pattern) > reader = pv.XMLUnstructuredGridReader( FileName=files ) > > The directory may be an input parameter to the script. > How can I transfer this into the GUI with the directory as a parameter? > > I have looked at python macros, but obviously it is not possible to > define any parameters there. > Is it possible to run a script from the python shell with a parameter? > I also took a look at the Programmable Source. It should be a possible > solution, but I have not found much explanation of what to do. > > Any ideas are welcome. > Kind regards > Ian > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Sent from my Jolla From arctica1963 at gmail.com Fri Mar 6 07:21:19 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Fri, 6 Mar 2015 12:21:19 +0000 Subject: [Paraview] SEG-Y seismic data loading In-Reply-To: References: Message-ID: This is definitely an import filter that would make ParaView more widely used, particularly in industry. Even doing as suggested by Leo, of reading the coordinates and extracting the amplitude would still be useful when viewing the data in 3D. Perhaps this will be addressed in a future release, but I know this has been asked for some years back I believe. On 5 March 2015 at 22:14, Lester Anderson wrote: > Hi Leo, > > Thanks for the suggestions. What software did you use to export the data? > > Cheers > Lester > > On 5 March 2015 at 19:18, L?o Pessanha > wrote: > >> Hi, >> >> I would like to apologize, i do not know how to answer a question in the >> mailing list correctly, i think the way i am doing it right now is going to >> appear as a new question >> >> There is no easy way of doing it, to see SEG-Y data in paraview, i used >> another software to export the data to ASCII txt >> >> So i exported to a 4 collumn text file with "X" "Y" "Z" "AMPLITUDE", >> imported in paraview, table to structured grid points filter, and used the >> scalar variable amplitude to color the object >> >> Hope it helped! >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From i.krukow at tu-braunschweig.de Fri Mar 6 08:13:17 2015 From: i.krukow at tu-braunschweig.de (Ian Krukow) Date: Fri, 06 Mar 2015 14:13:17 +0100 Subject: [Paraview] Load series of VTK files In-Reply-To: References: <54F98311.9010508@tu-braunschweig.de> Message-ID: <54F9A7ED.8020305@tu-braunschweig.de> Yes, that would work. I could write me a script for renaming the files. But I would rather avoid that, as I get the result files from a project partner with the simulation time in the filename. So, they are named something like file_t=0.0012.vtu file_t=0.0024.vtu ... As soon as t passes 1, ParaView sees a new series. In addition, the first timestep has a different filename, because it is a steady-state solution. I could remove the dots in the time values and rename the steady-state solution, but I would have to do it every time I get a new file series. Therefore, I have been looking for another solution. Kind regards Ian Am 06.03.2015 um 11:56 schrieb dkxls23 at gmail.com: > Have you tried to name the files like this: > fileName.0000.vtu > fileName.0001.vtu > fileName.0002.vtu > ... > > ParaView should recognize them as a time series. > > That typically worked for me (cannot test it though at the moment). > > -Armin > > > > > On Fri Mar 6 12:36:01 2015 GMT+0200, Ian Krukow wrote: >> Hi all, >> >> I want to load a series of VTU files, which are all stored in one >> directory, but not numbered in a way that ParaView recognises them as >> one series. In a python script, I can do it like this: >> >> import glob >> import paraview.simple as pv >> pattern = 'directory/*.vtu' >> files = glob.glob(pattern) >> reader = pv.XMLUnstructuredGridReader( FileName=files ) >> >> The directory may be an input parameter to the script. >> How can I transfer this into the GUI with the directory as a parameter? >> >> I have looked at python macros, but obviously it is not possible to >> define any parameters there. >> Is it possible to run a script from the python shell with a parameter? >> I also took a look at the Programmable Source. It should be a possible >> solution, but I have not found much explanation of what to do. >> >> Any ideas are welcome. >> Kind regards >> Ian >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> 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 dkxls23 at gmail.com Fri Mar 6 09:06:39 2015 From: dkxls23 at gmail.com (dkxls23 at gmail.com) Date: Fri, 6 Mar 2015 14:06:39 +0000 Subject: [Paraview] Load series of VTK files In-Reply-To: <54F9A7ED.8020305@tu-braunschweig.de> References: <54F98311.9010508@tu-braunschweig.de> <54F9A7ED.8020305@tu-braunschweig.de> Message-ID: Well, if you don't want to rename the data files then you could use a PVD wrapper file: http://www.paraview.org/Wiki/ParaView/Data_formats Never created one myself, but you could write out one from paraview and modify it. But maybe somebody else has a better idea altogether... -Armin On Fri Mar 6 15:13:17 2015 GMT+0200, Ian Krukow wrote: > Yes, that would work. I could write me a script for renaming the files. > But I would rather avoid that, as I get the result files from a project > partner with the simulation time in the filename. So, they are named > something like > file_t=0.0012.vtu > file_t=0.0024.vtu > ... > As soon as t passes 1, ParaView sees a new series. In addition, the > first timestep has a different filename, because it is a steady-state > solution. I could remove the dots in the time values and rename the > steady-state solution, but I would have to do it every time I get a new > file series. Therefore, I have been looking for another solution. > > Kind regards > Ian > > > > Am 06.03.2015 um 11:56 schrieb dkxls23 at gmail.com: > > Have you tried to name the files like this: > > fileName.0000.vtu > > fileName.0001.vtu > > fileName.0002.vtu > > ... > > > > ParaView should recognize them as a time series. > > > > That typically worked for me (cannot test it though at the moment). > > > > -Armin > > > > > > > > > > On Fri Mar 6 12:36:01 2015 GMT+0200, Ian Krukow wrote: > >> Hi all, > >> > >> I want to load a series of VTU files, which are all stored in one > >> directory, but not numbered in a way that ParaView recognises them as > >> one series. In a python script, I can do it like this: > >> > >> import glob > >> import paraview.simple as pv > >> pattern = 'directory/*.vtu' > >> files = glob.glob(pattern) > >> reader = pv.XMLUnstructuredGridReader( FileName=files ) > >> > >> The directory may be an input parameter to the script. > >> How can I transfer this into the GUI with the directory as a parameter? > >> > >> I have looked at python macros, but obviously it is not possible to > >> define any parameters there. > >> Is it possible to run a script from the python shell with a parameter? > >> I also took a look at the Programmable Source. It should be a possible > >> solution, but I have not found much explanation of what to do. > >> > >> Any ideas are welcome. > >> Kind regards > >> Ian > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > >> > >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > >> > >> Search the list archives at: http://markmail.org/search/?q=ParaView > >> > >> Follow this link to subscribe/unsubscribe: > >> http://public.kitware.com/mailman/listinfo/paraview > >> > > > -- Sent from my Jolla From yj.wang216 at gmail.com Fri Mar 6 09:21:02 2015 From: yj.wang216 at gmail.com (youjiang.wang) Date: Fri, 06 Mar 2015 15:21:02 +0100 Subject: [Paraview] Always crash when dealing with .tec files Message-ID: <54F9B7CE.4020005@gmail.com> Hallo, when i use simple tecplot files to store my data, and visualize it with paraview, there is always crash of the software. The crash doesn't happen immediately when the .tec file is read in, but after i have done some filters. And it can not be predicted when the crash will happen. I find that when working with .vtu file, there is no crash. Is there any method to solve such a problem? -you From dave.demarle at kitware.com Fri Mar 6 09:58:35 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 6 Mar 2015 09:58:35 -0500 Subject: [Paraview] SEG-Y seismic data loading In-Reply-To: References: Message-ID: +1, this would be great to have in ParaView. Just need someone out there to find the time and or funding to implement it. It could make a nice google summer of code effort if there is a student who is interested in the topic. http://www.kitware.com/blog/home/post/857 David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Mar 6, 2015 at 7:21 AM, Lester Anderson wrote: > This is definitely an import filter that would make ParaView more widely > used, particularly in industry. Even doing as suggested by Leo, of reading > the coordinates and extracting the amplitude would still be useful when > viewing the data in 3D. > > Perhaps this will be addressed in a future release, but I know this has > been asked for some years back I believe. > > On 5 March 2015 at 22:14, Lester Anderson wrote: > >> Hi Leo, >> >> Thanks for the suggestions. What software did you use to export the data? >> >> Cheers >> Lester >> >> On 5 March 2015 at 19:18, L?o Pessanha >> wrote: >> >>> Hi, >>> >>> I would like to apologize, i do not know how to answer a question in the >>> mailing list correctly, i think the way i am doing it right now is going to >>> appear as a new question >>> >>> There is no easy way of doing it, to see SEG-Y data in paraview, i used >>> another software to export the data to ASCII txt >>> >>> So i exported to a 4 collumn text file with "X" "Y" "Z" "AMPLITUDE", >>> imported in paraview, table to structured grid points filter, and used the >>> scalar variable amplitude to color the object >>> >>> Hope it helped! >>> >>> >>> >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Mar 6 10:20:50 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 6 Mar 2015 10:20:50 -0500 Subject: [Paraview] [EXTERNAL] Re: Superbuilds and clusters In-Reply-To: References: <6f1c065114704eaea84a269221d9e5ab@ES05AMSNLNT.srn.sandia.gov> Message-ID: Good to hear. Utkarsh On Thu, Mar 5, 2015 at 4:43 PM, Scott, W Alan wrote: > Thanks Utkarsh - that worked. I actually misinterpreted OSMesa as Operating System Mesa - but I believe it is Off Screen Mesa. The former is what I created, the latter is what I needed. > > OSMesa works. > > Alan > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan > Sent: Wednesday, March 04, 2015 7:33 PM > To: Utkarsh Ayachit > Cc: paraview at paraview.org > Subject: Re: [Paraview] [EXTERNAL] Re: Superbuilds and clusters > > When I try to search the binaries (i.e., pvserver and associated libraries), as follows, I don't see mesa. When I do this search on a good, I made it myself build, I do see mesa. > > cd ....../lib/paraview.4.3 > ldd * | egrep -i mesa > > Next, when I try to run with MPI, on the nodes of the clusters, 8 processes, I get the following: "Display is not accessible on the server side. Remote rendering will be disabled.". > > And, as expected, when I visualize wavelet, I see remote rendering is off. This is with a remote rendering threshold of 0. I also have Show Annotation on. > > OK, I don't know what you are talking about, so I assume I am not running an X server. Let me rebuild overnight with OSMesa. What is the difference? > > Alan > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Wednesday, March 04, 2015 1:37 PM > To: Scott, W Alan > Cc: paraview at paraview.org > Subject: [EXTERNAL] Re: [Paraview] Superbuilds and clusters > > Alan, > > What do you mean by it isn't remote rendering? Does it say display is not accessible and hence cannot use remote rendering? Don't you have X server running? If not, then use, you'd need to use OSMesa. > > Utkarsh > > On Tue, Mar 3, 2015 at 11:09 AM, Scott, W Alan wrote: >> I am trying to use the superbuild to create pvserver on a cluster. It >> appears to be running in parallel, but isn?t remote rendering. The issue i >> believe is that the Superbuild isn?t building with Mesa. I have done an >> ldd for mesa in the lib/paraview4-3 directory, and when I turn on Show >> Annotation, Remote Rendering says no. >> >> I am turning on ENABLE_mesa (-DENABLE_mesa:BOOL=ON). Should I be >> using osmesa instead? Any ideas what I am doing wrong? >> >> 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 >> > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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 arctica1963 at gmail.com Fri Mar 6 10:28:16 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Fri, 6 Mar 2015 15:28:16 +0000 Subject: [Paraview] SEG-Y seismic data loading In-Reply-To: References: Message-ID: Yes indeed David, I am sure it would make an interesting challenge for a coding exercise. Of course with the SEG-Y format, it would be easier (if that is the right term) to work on a 2D import first rather than jump into loading 3D cubes! I know that with the free GMT software it is possible to read the SEG-Y data (at least 2D) so I am wondering if there is a potential pathway via that code? The issues are not simple to overcome, as you need to be able to extract the positional (navigation) data (and understand the projection used), and then convert it to a visual format. It would be great if there was a way of dealing with this import using Python! Something to definitely think about for a future update. On 6 March 2015 at 14:58, David E DeMarle wrote: > +1, this would be great to have in ParaView. > > Just need someone out there to find the time and or funding to implement > it. > > It could make a nice google summer of code effort if there is a student > who is interested in the topic. > http://www.kitware.com/blog/home/post/857 > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Fri, Mar 6, 2015 at 7:21 AM, Lester Anderson > wrote: > >> This is definitely an import filter that would make ParaView more widely >> used, particularly in industry. Even doing as suggested by Leo, of reading >> the coordinates and extracting the amplitude would still be useful when >> viewing the data in 3D. >> >> Perhaps this will be addressed in a future release, but I know this has >> been asked for some years back I believe. >> >> On 5 March 2015 at 22:14, Lester Anderson wrote: >> >>> Hi Leo, >>> >>> Thanks for the suggestions. What software did you use to export the data? >>> >>> Cheers >>> Lester >>> >>> On 5 March 2015 at 19:18, L?o Pessanha >>> wrote: >>> >>>> Hi, >>>> >>>> I would like to apologize, i do not know how to answer a question in >>>> the mailing list correctly, i think the way i am doing it right now is >>>> going to appear as a new question >>>> >>>> There is no easy way of doing it, to see SEG-Y data in paraview, i used >>>> another software to export the data to ASCII txt >>>> >>>> So i exported to a 4 collumn text file with "X" "Y" "Z" "AMPLITUDE", >>>> imported in paraview, table to structured grid points filter, and used the >>>> scalar variable amplitude to color the object >>>> >>>> Hope it helped! >>>> >>>> >>>> >>> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nawijn at gmail.com Fri Mar 6 10:58:32 2015 From: nawijn at gmail.com (Marco Nawijn) Date: Fri, 6 Mar 2015 16:58:32 +0100 Subject: [Paraview] Load series of VTK files In-Reply-To: References: <54F98311.9010508@tu-braunschweig.de> <54F9A7ED.8020305@tu-braunschweig.de> Message-ID: On Fri, Mar 6, 2015 at 3:06 PM, wrote: > Well, if you don't want to rename the data files then you could use a PVD > wrapper file: > http://www.paraview.org/Wiki/ParaView/Data_formats > > Never created one myself, but you could write out one from paraview and > modify it. > > But maybe somebody else has a better idea altogether... > > -Armin > > > > > On Fri Mar 6 15:13:17 2015 GMT+0200, Ian Krukow wrote: > > Yes, that would work. I could write me a script for renaming the files. > > But I would rather avoid that, as I get the result files from a project > > partner with the simulation time in the filename. So, they are named > > something like > > file_t=0.0012.vtu > > file_t=0.0024.vtu > > ... > > As soon as t passes 1, ParaView sees a new series. In addition, the > > first timestep has a different filename, because it is a steady-state > > solution. I could remove the dots in the time values and rename the > > steady-state solution, but I would have to do it every time I get a new > > file series. Therefore, I have been looking for another solution. > > > > Kind regards > > Ian > > > > > > > > Am 06.03.2015 um 11:56 schrieb dkxls23 at gmail.com: > > > Have you tried to name the files like this: > > > fileName.0000.vtu > > > fileName.0001.vtu > > > fileName.0002.vtu > > > ... > > > > > > ParaView should recognize them as a time series. > > > > > > That typically worked for me (cannot test it though at the moment). > > > > > > -Armin > > > > > > > > > > > > > > > On Fri Mar 6 12:36:01 2015 GMT+0200, Ian Krukow wrote: > > >> Hi all, > > >> > > >> I want to load a series of VTU files, which are all stored in one > > >> directory, but not numbered in a way that ParaView recognises them as > > >> one series. In a python script, I can do it like this: > > >> > > >> import glob > > >> import paraview.simple as pv > > >> pattern = 'directory/*.vtu' > > >> files = glob.glob(pattern) > > >> reader = pv.XMLUnstructuredGridReader( FileName=files ) > > >> > > >> The directory may be an input parameter to the script. > > >> How can I transfer this into the GUI with the directory as a > parameter? > > >> > > >> I have looked at python macros, but obviously it is not possible to > > >> define any parameters there. > > >> Is it possible to run a script from the python shell with a parameter? > > >> I also took a look at the Programmable Source. It should be a possible > > >> solution, but I have not found much explanation of what to do. > > >> > > >> Any ideas are welcome. > > >> Kind regards > > >> Ian > > >> _______________________________________________ > > >> Powered by www.kitware.com > > >> > > >> Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > >> > > >> Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > >> > > >> Search the list archives at: http://markmail.org/search/?q=ParaView > > >> > > >> Follow this link to subscribe/unsubscribe: > > >> http://public.kitware.com/mailman/listinfo/paraview > > >> > > > > > > > -- > Sent from my Jolla > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > What about creating symbolic links (or shortcuts) to the real files. In this way you preserve the original filenames. PVD wrapper files also worked fine for me in the past. I have not used them recently however. Marco -------------- next part -------------- An HTML attachment was scrubbed... URL: From samuelkey at bresnan.net Fri Mar 6 09:20:09 2015 From: samuelkey at bresnan.net (Samuel Key) Date: Fri, 06 Mar 2015 07:20:09 -0700 Subject: [Paraview] Load series of VTK files In-Reply-To: <54F9A7ED.8020305@tu-braunschweig.de> References: <54F98311.9010508@tu-braunschweig.de> <54F9A7ED.8020305@tu-braunschweig.de> Message-ID: <54F9B799.7060906@bresnan.net> Ian, If the *.vtu files are using the XML-based format, the you can use a *.vtd "mother file" (or meta file) that references the *.vtu files. An example of a *.pvd file is attached, however, the 'name=...' item is ignored (not used) by PV's Extract Block filter. Sam On 3/6/2015 6:13 AM, Ian Krukow wrote: > Yes, that would work. I could write me a script for renaming the > files. But I would rather avoid that, as I get the result files from a > project partner with the simulation time in the filename. So, they are > named something like > file_t=0.0012.vtu > file_t=0.0024.vtu > ... > As soon as t passes 1, ParaView sees a new series. In addition, the > first timestep has a different filename, because it is a steady-state > solution. I could remove the dots in the time values and rename the > steady-state solution, but I would have to do it every time I get a > new file series. Therefore, I have been looking for another solution. > > Kind regards > Ian > > > > Am 06.03.2015 um 11:56 schrieb dkxls23 at gmail.com: >> Have you tried to name the files like this: >> fileName.0000.vtu >> fileName.0001.vtu >> fileName.0002.vtu >> ... >> >> ParaView should recognize them as a time series. >> >> That typically worked for me (cannot test it though at the moment). >> >> -Armin >> >> >> >> >> On Fri Mar 6 12:36:01 2015 GMT+0200, Ian Krukow wrote: >>> Hi all, >>> >>> I want to load a series of VTU files, which are all stored in one >>> directory, but not numbered in a way that ParaView recognises them as >>> one series. In a python script, I can do it like this: >>> >>> import glob >>> import paraview.simple as pv >>> pattern = 'directory/*.vtu' >>> files = glob.glob(pattern) >>> reader = pv.XMLUnstructuredGridReader( FileName=files ) >>> >>> The directory may be an input parameter to the script. >>> How can I transfer this into the GUI with the directory as a parameter? >>> >>> I have looked at python macros, but obviously it is not possible to >>> define any parameters there. >>> Is it possible to run a script from the python shell with a parameter? >>> I also took a look at the Programmable Source. It should be a possible >>> solution, but I have not found much explanation of what to do. >>> >>> Any ideas are welcome. >>> Kind regards >>> Ian >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >> > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- A non-text attachment was scrubbed... Name: fmavto.pvd Type: text/xml Size: 5356 bytes Desc: not available URL: From leonardopessanha74 at gmail.com Fri Mar 6 15:55:54 2015 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Fri, 6 Mar 2015 17:55:54 -0300 Subject: [Paraview] SEG-Y seismic data loading In-Reply-To: References: Message-ID: Putting a SEG-Y data in a more direct way is still in the escope of one of the projects that i am working on. I did some research not a long time ago and i found that Richard Strelitz wrote a paraview plugin for reading SEG-Y data at LANL but he gave up since there was no easy way of retaining the concept of a trace that is so essential to seismic data at the time he was still trying. He said that would for some of the files he created but we lost contact. Maybe he could help, and instead of starting from zero, maybe there`s a way to continue his work and save some time. For me it would be a really really great tool to have in paraview! With the proper guidance, i would really like to help(or try to help) ! 2015-03-06 11:58 GMT-03:00 David E DeMarle : > +1, this would be great to have in ParaView. > > Just need someone out there to find the time and or funding to implement > it. > > It could make a nice google summer of code effort if there is a student > who is interested in the topic. > http://www.kitware.com/blog/home/post/857 > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Fri, Mar 6, 2015 at 7:21 AM, Lester Anderson > wrote: > >> This is definitely an import filter that would make ParaView more widely >> used, particularly in industry. Even doing as suggested by Leo, of reading >> the coordinates and extracting the amplitude would still be useful when >> viewing the data in 3D. >> >> Perhaps this will be addressed in a future release, but I know this has >> been asked for some years back I believe. >> >> On 5 March 2015 at 22:14, Lester Anderson wrote: >> >>> Hi Leo, >>> >>> Thanks for the suggestions. What software did you use to export the data? >>> >>> Cheers >>> Lester >>> >>> On 5 March 2015 at 19:18, L?o Pessanha >>> wrote: >>> >>>> Hi, >>>> >>>> I would like to apologize, i do not know how to answer a question in >>>> the mailing list correctly, i think the way i am doing it right now is >>>> going to appear as a new question >>>> >>>> There is no easy way of doing it, to see SEG-Y data in paraview, i used >>>> another software to export the data to ASCII txt >>>> >>>> So i exported to a 4 collumn text file with "X" "Y" "Z" "AMPLITUDE", >>>> imported in paraview, table to structured grid points filter, and used the >>>> scalar variable amplitude to color the object >>>> >>>> Hope it helped! >>>> >>>> >>>> >>> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 canismajorwuff at gmail.com Fri Mar 6 16:17:52 2015 From: canismajorwuff at gmail.com (Canis Major) Date: Fri, 6 Mar 2015 22:17:52 +0100 Subject: [Paraview] Import of XDMF/HDF5:Cell centered attribute of 2D Rectangular grid Message-ID: I have troubles importing xdmf output to paraview. This is an example of xdmf of 0th iteration. xdmf2d.h5:/Z xdmf2d.h5:/Y xdmf2d.h5:/X xdmf2d.0.h5:/pressure I have an error that paraview failed to import attribute. What could be wrong? I have played around the parameters nothing helps. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dkxls23 at gmail.com Fri Mar 6 16:55:37 2015 From: dkxls23 at gmail.com (dkxls23 at gmail.com) Date: Fri, 6 Mar 2015 21:55:37 +0000 Subject: [Paraview] Import of XDMF/HDF5:Cell centered attribute of 2D Rectangular grid In-Reply-To: References: Message-ID: I have had similar problems with 2D structured grids and XDMF in the past. I never got them to work in ParaView. I solved the problem by using 3D grids and set the first dimension (i.e. the slowest varying) one to 1, the same way as you have done it with VXVYVZ. You just have to adjust your data arrays accordingly, i.e. dimensions 1 82 221 in your example. I can send you a working xdmf file when back in the office. I believe the computational overhead from 2D to 3D grids with effectively 2 dimensions is rather small. Maybe the next-generation XDMF reader in ParaView works better for 2D structued grids or somebody with the knowledge explains us how to write them correctly. :) -Armin On Fri Mar 6 23:17:52 2015 GMT+0200, Canis Major wrote: > I have troubles importing xdmf output to paraview. > > This is an example of xdmf of 0th iteration. > > > > > > > > > > xdmf2d.h5:/Z > > > > xdmf2d.h5:/Y > > > xdmf2d.h5:/X > > > Format="HDF"> > xdmf2d.0.h5:/pressure > > > > > > > > > I have an error that paraview failed to import attribute. What could > be wrong? I have played around the parameters nothing helps. > -- Sent from my Jolla From tim.gallagher at gatech.edu Fri Mar 6 17:54:38 2015 From: tim.gallagher at gatech.edu (Tim Gallagher) Date: Fri, 6 Mar 2015 17:54:38 -0500 (EST) Subject: [Paraview] Import of XDMF/HDF5:Cell centered attribute of 2D Rectangular grid In-Reply-To: Message-ID: <102718772.6116372.1425682478532.JavaMail.root@mail.gatech.edu> Hi guys, So the problems you're having are due to specifying inconsistent data here. You are specifying a 2DRectMesh grid but then giving it 3 vectors for the points. I don't have your HDF5 files so I made a light data XMF file that works for me on all versions going back to 3.14. I have attached it here for you to test. This all works fine. I've also created a 3DRectMesh. For that, you need to give it 2 points in the 3rd direction for the grid because you are specifying cell centered data. If you only give it 1 point in the 3rd direction, there is no "cell" anymore in which to specify the data. I'll leave adding the 3rd dimension as an exercise for you to work with. Once you figure out how it needs to work using the light data format, then switch over to using the heavy data format and get it working again. Hope that helps, Tim ----- Original Message ----- From: dkxls23 at gmail.com To: canismajorwuff at gmail.com Cc: paraview at paraview.org Sent: Friday, March 6, 2015 4:55:37 PM Subject: Re: [Paraview] Import of XDMF/HDF5:Cell centered attribute of 2D Rectangular grid I have had similar problems with 2D structured grids and XDMF in the past. I never got them to work in ParaView. I solved the problem by using 3D grids and set the first dimension (i.e. the slowest varying) one to 1, the same way as you have done it with VXVYVZ. You just have to adjust your data arrays accordingly, i.e. dimensions 1 82 221 in your example. I can send you a working xdmf file when back in the office. I believe the computational overhead from 2D to 3D grids with effectively 2 dimensions is rather small. Maybe the next-generation XDMF reader in ParaView works better for 2D structued grids or somebody with the knowledge explains us how to write them correctly. :) -Armin On Fri Mar 6 23:17:52 2015 GMT+0200, Canis Major wrote: > I have troubles importing xdmf output to paraview. > > This is an example of xdmf of 0th iteration. > > > > > > > > > > xdmf2d.h5:/Z > > > > xdmf2d.h5:/Y > > > xdmf2d.h5:/X > > > Format="HDF"> > xdmf2d.0.h5:/pressure > > > > > > > > > I have an error that paraview failed to import attribute. What could > be wrong? I have played around the parameters nothing helps. > -- Sent from my Jolla _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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: test.xmf Type: audio/x-xmf Size: 934 bytes Desc: not available URL: From cjm2176 at columbia.edu Fri Mar 6 18:23:57 2015 From: cjm2176 at columbia.edu (Colin McAuliffe) Date: Fri, 6 Mar 2015 18:23:57 -0500 Subject: [Paraview] Converting selection types Message-ID: Hi everybody, I am scripting in python and would like to be able to do a plot selection over time of the statistics for a subregion in my domain. The plot selection over time filter does not seem to work if I give a frustum selection source as the selection, but ID selection sources always work. My current workaround is to do a frustum selection by cell, apply an extract selection filter, then create an ID selection for all of the points in the result which then is passed to PSOT. Is there a simpler way to convert the frustum selection to an ID selection? Thanks, Colin -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.gallagher at gatech.edu Fri Mar 6 18:24:56 2015 From: tim.gallagher at gatech.edu (Tim Gallagher) Date: Fri, 6 Mar 2015 18:24:56 -0500 (EST) Subject: [Paraview] Import of XDMF/HDF5:Cell centered attribute of 2D Rectangular grid In-Reply-To: Message-ID: <147718449.6123444.1425684296831.JavaMail.root@mail.gatech.edu> Don't forget to reply to the list -- Without seeing errors or images of what was wrong about it, there isn't much we can do to help. The file I sent does work and PV reads it just fine. The coordinate axes in this case is Y-Z, but ultimately those are just names since it's 2D right? It doesn't matter if I call it X-Y, Y-Z, or X-Z so long as I have 2 orthogonal coordinates. The axes are specified in reverse order when you list them the way it is done there. So the first dataitem is always Z, the second is always Y and the third, if you have one, is always X. This also comes up when you specify the multi-dimensional data items in the attribute section because you have to remember it uses C memory layout (row major), which is different from the Fortran layout (column major) . We use XDMF for massive multiblock structured simulations and we store our coordinates in hdf5 files in full 3D arrays (so what something like the meshgrid function returns in Matlab/Numpy) and I've put an example at the end of my email here. In this case, we have a grid which in Fortran would have coordinates X(I,J,K) where I = 1, 83; J = 1, 83; K = 1, 4. Note that the indexing is flipped when we specify it in the XDMF file. It is also flipped from what one would expect coming from Fortran when you look at the h5dump (after the XDMF example). Our strategy is to specify our grid points as an array of vectors and we create that array of vectors using the JOIN function. The XDMF documentation isn't always as helpful as I'd like sometimes. It took a lot of trial and error on our part to get this working (and it's made more complicated because we use hyperslabs a lot to only display portions of our data). The PV release binaries are also not helpful in understanding the problems sometimes -- very often, it will just segfault or crash with a glibc double-linked list error or something. Building PV yourself with debug options may help if you are really stuck. But what you seem to be trying to do is fully supported and you just need to keep working at it to understand why it doesn't work. And if you are having problems, posting images of what it looks like when you import the data would really help if the issue is just that it doesn't seem to be what you think it should be. Tim &gridpath;/grid.h5:/Domain_00001/x &gridpath;/grid.h5:/Domain_00001/y &gridpath;/grid.h5:/Domain_00001/z &outputpath;/RESTS/REST_00000.h5:/FlowData/temperature GROUP "/" { GROUP "Domain_00001" { DATASET "x" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 6, 85, 85 ) / ( 6, 85, 85 ) } } DATASET "y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 6, 85, 85 ) / ( 6, 85, 85 ) } } DATASET "z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 6, 85, 85 ) / ( 6, 85, 85 ) } } } ----- Original Message ----- From: "Canis Major" To: "tim gallagher" Sent: Friday, March 6, 2015 6:05:43 PM Subject: Re: [Paraview] Import of XDMF/HDF5:Cell centered attribute of 2D Rectangular grid Tim, thank you for your concerns. But of course I tried the configuration like this, it is most intuitive way of description. But unfortunately, it does not work with paraview. In this case the wrong geometry is being created, I do not know how to more clearly describe what is wrong with it. First of all, there is nothing in X direction anymore, but in Y-Z plane, and the geometry shape is wrong, I do not know. Also I think there is no such geometry type as VXVY. I have not seen it in Xmdf specification. I suppose Armin tried it too and, as he said, failed. With Best Regards, Slava On Fri, Mar 6, 2015 at 11:54 PM, Tim Gallagher < tim.gallagher at gatech.edu > wrote: Hi guys, So the problems you're having are due to specifying inconsistent data here. You are specifying a 2DRectMesh grid but then giving it 3 vectors for the points. I don't have your HDF5 files so I made a light data XMF file that works for me on all versions going back to 3.14. I have attached it here for you to test. This all works fine. I've also created a 3DRectMesh. For that, you need to give it 2 points in the 3rd direction for the grid because you are specifying cell centered data. If you only give it 1 point in the 3rd direction, there is no "cell" anymore in which to specify the data. I'll leave adding the 3rd dimension as an exercise for you to work with. Once you figure out how it needs to work using the light data format, then switch over to using the heavy data format and get it working again. Hope that helps, Tim ----- Original Message ----- From: dkxls23 at gmail.com To: canismajorwuff at gmail.com Cc: paraview at paraview.org Sent: Friday, March 6, 2015 4:55:37 PM Subject: Re: [Paraview] Import of XDMF/HDF5:Cell centered attribute of 2D Rectangular grid I have had similar problems with 2D structured grids and XDMF in the past. I never got them to work in ParaView. I solved the problem by using 3D grids and set the first dimension (i.e. the slowest varying) one to 1, the same way as you have done it with VXVYVZ. You just have to adjust your data arrays accordingly, i.e. dimensions 1 82 221 in your example. I can send you a working xdmf file when back in the office. I believe the computational overhead from 2D to 3D grids with effectively 2 dimensions is rather small. Maybe the next-generation XDMF reader in ParaView works better for 2D structued grids or somebody with the knowledge explains us how to write them correctly. :) -Armin On Fri Mar 6 23:17:52 2015 GMT+0200, Canis Major wrote: > I have troubles importing xdmf output to paraview. > > This is an example of xdmf of 0th iteration. > > > > > > > > > > xdmf2d.h5:/Z > > > > xdmf2d.h5:/Y > > > xdmf2d.h5:/X > > > Format="HDF"> > xdmf2d.0.h5:/pressure > > > > > > > > > I have an error that paraview failed to import attribute. What could > be wrong? I have played around the parameters nothing helps. > -- Sent from my Jolla _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 nikos.beratlis at gmail.com Fri Mar 6 18:59:42 2015 From: nikos.beratlis at gmail.com (Nikolaos Beratlis) Date: Fri, 6 Mar 2015 18:59:42 -0500 Subject: [Paraview] How to change background color on scatter plot? Message-ID: I have a scatter plot like this one ? and I want to change the background color from white to green or some other color. How can I do that? Regards, Nikos -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: uw_quadrant_x1.1_VP0001.jpg Type: image/jpeg Size: 109790 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Sat Mar 7 10:36:20 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sat, 7 Mar 2015 10:36:20 -0500 Subject: [Paraview] How to change background color on scatter plot? In-Reply-To: References: Message-ID: Alas, no. That isn't currently supported, but should be straight forward to implement. Mind reporting a feature request on the bug tracker: http://paraview.org/Bug. Thanks. Utkarsh On Fri, Mar 6, 2015 at 6:59 PM, Nikolaos Beratlis wrote: > I have a scatter plot like this one > > > ? > > and I want to change the background color from white to green or some > other color. How can I do that? > > Regards, > > Nikos > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: uw_quadrant_x1.1_VP0001.jpg Type: image/jpeg Size: 109790 bytes Desc: not available URL: From arctica1963 at gmail.com Sun Mar 8 09:50:30 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Sun, 8 Mar 2015 13:50:30 +0000 Subject: [Paraview] SEG-Y seismic data loading In-Reply-To: References: Message-ID: The other workaround is to have an image of the seismic line that can be georeferenced for loading into Paraview. However, this requires a seismic viewer capable of exporting a good quality image and not all do (SeiSee is quite good). Obviously things get a little complex when having to convert from time to depth, but not so if you are dealing with Z as the time coordinate. Is there a georeference filter/tool in ParaView? Cheers On 6 March 2015 at 20:55, L?o Pessanha wrote: > Putting a SEG-Y data in a more direct way is still in the escope of one of > the projects that i am working on. I did some research not a long time ago > and i found that Richard Strelitz wrote a paraview plugin for reading SEG-Y > data at LANL but he gave up since there was no easy way of retaining the > concept of a trace that is so essential to seismic data at the time he was > still trying. He said that would for some of the files he created but we > lost contact. > > Maybe he could help, and instead of starting from zero, maybe there`s a > way to continue his work and save some time. > > For me it would be a really really great tool to have in paraview! > > With the proper guidance, i would really like to help(or try to help) ! > > 2015-03-06 11:58 GMT-03:00 David E DeMarle : > > +1, this would be great to have in ParaView. >> >> Just need someone out there to find the time and or funding to implement >> it. >> >> It could make a nice google summer of code effort if there is a student >> who is interested in the topic. >> http://www.kitware.com/blog/home/post/857 >> >> >> David E DeMarle >> Kitware, Inc. >> R&D Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 >> >> On Fri, Mar 6, 2015 at 7:21 AM, Lester Anderson >> wrote: >> >>> This is definitely an import filter that would make ParaView more widely >>> used, particularly in industry. Even doing as suggested by Leo, of reading >>> the coordinates and extracting the amplitude would still be useful when >>> viewing the data in 3D. >>> >>> Perhaps this will be addressed in a future release, but I know this has >>> been asked for some years back I believe. >>> >>> On 5 March 2015 at 22:14, Lester Anderson wrote: >>> >>>> Hi Leo, >>>> >>>> Thanks for the suggestions. What software did you use to export the >>>> data? >>>> >>>> Cheers >>>> Lester >>>> >>>> On 5 March 2015 at 19:18, L?o Pessanha >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> I would like to apologize, i do not know how to answer a question in >>>>> the mailing list correctly, i think the way i am doing it right now is >>>>> going to appear as a new question >>>>> >>>>> There is no easy way of doing it, to see SEG-Y data in paraview, i >>>>> used another software to export the data to ASCII txt >>>>> >>>>> So i exported to a 4 collumn text file with "X" "Y" "Z" "AMPLITUDE", >>>>> imported in paraview, table to structured grid points filter, and used the >>>>> scalar variable amplitude to color the object >>>>> >>>>> Hope it helped! >>>>> >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> 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 i.krukow at tu-braunschweig.de Mon Mar 9 06:41:17 2015 From: i.krukow at tu-braunschweig.de (Ian Krukow) Date: Mon, 09 Mar 2015 11:41:17 +0100 Subject: [Paraview] Load series of VTK files In-Reply-To: References: <54F98311.9010508@tu-braunschweig.de> <54F9A7ED.8020305@tu-braunschweig.de> Message-ID: <54FD78CD.1070103@tu-braunschweig.de> Thank you for your suggestions! Still: No matter which one I choose, I would have to edit every new set of files, before I can load it into ParaView. I have now set up a (very small) pvypthon module vtuseries.py, which looks like this: import os,glob import paraview.simple as pv def load(directory): """Load VTU file series from given directory """ pattern = os.path.join(directory, '*.vtu') files = glob.glob(pattern) reader = pv.XMLUnstructuredGridReader( FileName=files ) Putting this module on the path of the ParaView Python Shell gives me the opportunity to run import vtuseries vtuseries.load(directory) from the Python Shell, which creates a reader with all the vtu files in the given directory. Maybe this is not even easier than the other suggestions, but it is closer to what I had been looking for originally. I thought there might be a better way to run python code depending on a given parameter (the input directory) in the ParaView GUI, but I have not found it. One last question to the developers: Is there a special reason, that it is not possible to select several VTK files from the Open dialog, which are then opened as a sequence? Kind regards Ian Am 06.03.2015 um 16:58 schrieb Marco Nawijn: > On Fri, Mar 6, 2015 at 3:06 PM, > wrote: > > Well, if you don't want to rename the data files then you could use > a PVD wrapper file: > http://www.paraview.org/Wiki/ParaView/Data_formats > > Never created one myself, but you could write out one from paraview > and modify it. > > But maybe somebody else has a better idea altogether... > > -Armin > > > > > On Fri Mar 6 15:13:17 2015 GMT+0200, Ian Krukow wrote: > > Yes, that would work. I could write me a script for renaming the > files. > > But I would rather avoid that, as I get the result files from a > project > > partner with the simulation time in the filename. So, they are named > > something like > > file_t=0.0012.vtu > > file_t=0.0024.vtu > > ... > > As soon as t passes 1, ParaView sees a new series. In addition, the > > first timestep has a different filename, because it is a steady-state > > solution. I could remove the dots in the time values and rename the > > steady-state solution, but I would have to do it every time I get > a new > > file series. Therefore, I have been looking for another solution. > > > > Kind regards > > Ian > > > > > > > > Am 06.03.2015 um 11:56 schrieb dkxls23 at gmail.com > : > > > Have you tried to name the files like this: > > > fileName.0000.vtu > > > fileName.0001.vtu > > > fileName.0002.vtu > > > ... > > > > > > ParaView should recognize them as a time series. > > > > > > That typically worked for me (cannot test it though at the moment). > > > > > > -Armin > > > > > > > > > > > > > > > On Fri Mar 6 12:36:01 2015 GMT+0200, Ian Krukow wrote: > > >> Hi all, > > >> > > >> I want to load a series of VTU files, which are all stored in one > > >> directory, but not numbered in a way that ParaView recognises > them as > > >> one series. In a python script, I can do it like this: > > >> > > >> import glob > > >> import paraview.simple as pv > > >> pattern = 'directory/*.vtu' > > >> files = glob.glob(pattern) > > >> reader = pv.XMLUnstructuredGridReader( FileName=files ) > > >> > > >> The directory may be an input parameter to the script. > > >> How can I transfer this into the GUI with the directory as a > parameter? > > >> > > >> I have looked at python macros, but obviously it is not > possible to > > >> define any parameters there. > > >> Is it possible to run a script from the python shell with a > parameter? > > >> I also took a look at the Programmable Source. It should be a > possible > > >> solution, but I have not found much explanation of what to do. > > >> > > >> Any ideas are welcome. > > >> Kind regards > > >> Ian > > >> _______________________________________________ > > >> Powered by www.kitware.com > > >> > > >> Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > >> > > >> Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > >> > > >> Search the list archives at: > http://markmail.org/search/?q=ParaView > > >> > > >> Follow this link to subscribe/unsubscribe: > > >> http://public.kitware.com/mailman/listinfo/paraview > > >> > > > > > > > -- > Sent from my Jolla > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > What about creating symbolic links (or shortcuts) to the > real files. In this way you preserve the original filenames. > > PVD wrapper files also worked fine for me in the past. > I have not used them recently however. > > Marco From stephen.wornom at inria.fr Mon Mar 9 12:47:00 2015 From: stephen.wornom at inria.fr (Stephen Wornom) Date: Mon, 09 Mar 2015 17:47:00 +0100 Subject: [Paraview] PV 4.1.0: save the data saves only 1/2 of a circle Message-ID: <54FDCE84.9010100@inria.fr> I have a cylinder ( a circle in the x-y plane, z is the span direction). I do: - extract surface - connectivity - threshold (defines the surface of the cylinder) The result is the circle shown in that attached figure. I want to write the circle values to a file so I save the data. The problem is that PV4.10 saves only 1/2 half of the data (y<0). For y> 0 only 4 points are written to the csv file, 124 points for y <0. How can I save the data so that all values are written? Hope the question is clear. Stephen -- stephen.wornom at inria.fr 2004 route des lucioles - BP93 Sophia Antipolis 06902 CEDEX Tel: 04 92 38 50 54 Fax: 04 97 15 53 51 -------------- next part -------------- A non-text attachment was scrubbed... Name: circle-in-x-y_plane.jpg Type: image/jpeg Size: 34095 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: stephen_wornom.vcf Type: text/x-vcard Size: 187 bytes Desc: not available URL: From kmorel at sandia.gov Mon Mar 9 13:28:45 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 9 Mar 2015 17:28:45 +0000 Subject: [Paraview] PV 4.1.0: save the data saves only 1/2 of a circle Message-ID: Stephen, The CSV writer should write out all the points. I tried repeating your instructions with ParaView 4.3.1 using both the Cylinder source and the disk_out_ref dataset to write out data for a hollow cylinder source to a csv file and it looks like it works fine. I can only think of the most basic things to try: * Are you sure your cylinder is centered in the x-y plane? Maybe the circle is actually sitting below the y axis. Check that with either the cube axes or the information panel. * Is the connectivity/threshold filters really the best way to get a circle from a cylinder. You might consider instead to use the slice filter to get the circle. (I don't know why that would fix any I/O issues, though.) * Is there any chance you can try using the latest version of ParaView. I don't recall any such problems with the CSV reader in 4.1, but you never know. -Ken On 3/9/15, 10:47 AM, "Stephen Wornom" wrote: >I have a cylinder ( a circle in the x-y plane, z is the span direction). >I do: >- extract surface >- connectivity >- threshold (defines the surface of the cylinder) > >The result is the circle shown in that attached figure. > >I want to write the circle values to a file so I save the data. > The problem is that PV4.10 saves only 1/2 half of the data (y<0). For >y> 0 only 4 points are written to the csv file, 124 points for y <0. > >How can I save the data so that all values are written? >Hope the question is clear. >Stephen > >-- >stephen.wornom at inria.fr >2004 route des lucioles - BP93 >Sophia Antipolis >06902 CEDEX > >Tel: 04 92 38 50 54 >Fax: 04 97 15 53 51 > From ondrej.certik at gmail.com Mon Mar 9 14:54:49 2015 From: ondrej.certik at gmail.com (=?UTF-8?B?T25kxZllaiDEjGVydMOtaw==?=) Date: Mon, 9 Mar 2015 12:54:49 -0600 Subject: [Paraview] Compilation failure with the latest git master Message-ID: Hi, I have a working version using git f7aac037722d9d13b75d9fdb15a1053c0874c6c6. I kept the same versions of all the external dependencies (boost, png, qt, zlib, bzip2, gdal, hdf5, mpi, netcdf4, netcdf4cpp, freetype, python, numpy, matplotlib, libxml2, mesa), but upgraded to the latest git master of ParaView (and updated submodules): 7e714de07e6a3c0e376ed634cf83be44be13d733. Now paraview fails to build with: [paraview] /local/certik/tmp/paraview-xx3asav3as7r-1/_build/Wrapping/ClientServer/vtkGDALClientServer.cxx:13:41: error: invalid conversion from 'vtkObject*' to 'vtkGDAL*' [-fpermissive] [paraview] vtkGDAL *op = vtkGDAL::SafeDownCast(ob); [paraview] ^ Here is a full build log: https://gist.githubusercontent.com/certik/05d98c5b60664e028eee/raw/gistfile1.txt Any ideas what could be causing it? Thanks, Ondrej From ondrej.certik at gmail.com Mon Mar 9 15:29:57 2015 From: ondrej.certik at gmail.com (=?UTF-8?B?T25kxZllaiDEjGVydMOtaw==?=) Date: Mon, 9 Mar 2015 13:29:57 -0600 Subject: [Paraview] Segfault when selecting "Unset Visibility" in Multi-block Inspector Message-ID: Hi, I get a segfault with the git version f7aac037722d9d13b75d9fdb15a1053c0874c6c6. Here is a minimal set of steps to reproduce: $ wget -O mug.e https://github.com/idaholab/moose/blob/devel/examples/ex01_inputfile/mug.e?raw=true $ paraview mug.e Click "Apply" Click "View -> Multi-block Inspector" Right click the first line in the Multi-block Inspector (mug.e) Select "Unset Visibility" It will immediately segfault (just writes "Segmentation fault" into the terminal and ends, no other info is printed). This seems to happen with any ExodusII mesh that I tried (I just used some publicly available mesh so that you can reproduce it). Let me know if you can reproduce the problem. Ondrej From wascott at sandia.gov Mon Mar 9 17:27:34 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 9 Mar 2015 21:27:34 +0000 Subject: [Paraview] [EXTERNAL] PROBLEM IMPORTING ENSIGHT SOS FILE In-Reply-To: References: Message-ID: I believe my thoughts below were wrong. Ignore them. Could you give us a trivial dataset that shows this issue? Thanks, Alan -----Original Message----- From: Gaspare Argento [mailto:gaspare.argento at gmail.com] Sent: Friday, March 06, 2015 12:47 AM To: Scott, W Alan Cc: paraview at paraview.org Subject: Re: [EXTERNAL] [Paraview] PROBLEM IMPORTING ENSIGHT SOS FILE Hi Scott, thanks for answering. I'm sorry but I didn't understand exactly what do you mean: could you please explain it better? Did you ask me to attach the .sos file? Thanks, Gaspare 2015-03-05 18:39 GMT+01:00 Scott, W Alan : > I just opened an .sos file, with a 16 file dataset, with ParaView 4.3.1. Worked fine. Linux, local server. > > * I wonder if you have a problem with your SOS file. > * Mind posting a/the dataset? > > Alan > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of > Gaspare Argento > Sent: Thursday, March 05, 2015 2:20 AM > To: paraview at paraview.org > Subject: [EXTERNAL] [Paraview] PROBLEM IMPORTING ENSIGHT SOS FILE > > Hi everybody, > > I have a problem when importing an Ensight .sos file in Paraview. > > Loading the .sos file I get the following message (I attach only the lines about the first *.case file, because these are repeated for all *case files listed in the .sos): > ====================================================================== > ==================================================== > > ERROR: In > C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSightR > eader.cxx, > line 340 > > vtkPGenericEnSightReader (000000000DC5E6E0): Unable to open file: > J:\SERVER\CALC\VOF_TEST\Calculation\VOF_TEST\3D_EnSight\/VOF_TEST_DOM_ > 0.case > > > > > > ERROR: In > C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSightR > eader.cxx, > line 340 > > vtkPGenericEnSightReader (000000000DC5E6E0): Unable to open file: > J:\SERVER\CALC\VOF_TEST\Calculation\VOF_TEST\3D_EnSight\/VOF_TEST_DOM_ > 0.case > > > > > > ERROR: In > C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSightR > eader.cxx, > line 811 > > vtkPGenericEnSightReader (000000000DC5E6E0): Error determining > EnSightVersion > > > > > > ERROR: In > C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExec > utive.cxx, > line 784 > > vtkCompositeDataPipeline (000000000DBF33A0): Algorithm > vtkPGenericEnSightReader(000000000DC5E6E0) returned failure for > request: vtkInformation (000000000DEC2F60) > > Debug: Off > > Modified Time: 160501 > > Reference Count: 1 > > Registered Events: (none) > > Request: REQUEST_INFORMATION > > ALGORITHM_AFTER_FORWARD: 1 > > FORWARD_DIRECTION: 0 > > > > > > ERROR: In > C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\VTKExtensions\Defaul > t\vtkPVEnSightMasterServerReader2.cxx, > line 255 > > vtkPVEnSightMasterServerReader2 (0000000018693C90): Error reading case file on at least one node. > > > > > > ERROR: In > C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExec > utive.cxx, > line 784 > > vtkPVCompositeDataPipeline (0000000017BEA7E0): Algorithm > vtkPVEnSightMasterServerReader2(0000000018693C90) returned failure for > request: vtkInformation (0000000016F654A0) > > Debug: Off > > Modified Time: 6920520 > > Reference Count: 1 > > Registered Events: (none) > > Request: REQUEST_INFORMATION > > ALGORITHM_AFTER_FORWARD: 1 > > FORWARD_DIRECTION: 0 > > ====================================================================== > ==================================================== > > > > Below you can find an extract of the loaded .sos file (only the lines relative to the first server): > ====================================================================== > ==================================================== > > # > > # Example Server-of-server case file > > # parts in <> have to be filled in by the user > > # > > FORMAT > > type: master_server gold > > SERVERS > > number of servers: 64 > > #Server 1 > > machine id: MACHINE_NAME > > executable: > > casefile: > J:/SERVER/CALC/VOF_TEST/Calculation/VOF_TEST/3D_EnSight/DOM_0/VOF_TEST > _DOM_0.case > > ====================================================================== > ==================================================== > > > > If I load the *.case files one by one I have no problem. > > > > Thanks for your support > > Gaspare > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From ondrej.certik at gmail.com Mon Mar 9 19:22:53 2015 From: ondrej.certik at gmail.com (=?UTF-8?B?T25kxZllaiDEjGVydMOtaw==?=) Date: Mon, 9 Mar 2015 17:22:53 -0600 Subject: [Paraview] Compilation failure with the latest git master In-Reply-To: References: Message-ID: On Mon, Mar 9, 2015 at 12:54 PM, Ond?ej ?ert?k wrote: > Hi, > > I have a working version using git > f7aac037722d9d13b75d9fdb15a1053c0874c6c6. I kept the same versions of > all the external dependencies (boost, png, qt, zlib, bzip2, gdal, > hdf5, mpi, netcdf4, netcdf4cpp, freetype, python, numpy, matplotlib, > libxml2, mesa), but upgraded to the latest git master of ParaView (and > updated submodules): 7e714de07e6a3c0e376ed634cf83be44be13d733. > > Now paraview fails to build with: > > [paraview] /local/certik/tmp/paraview-xx3asav3as7r-1/_build/Wrapping/ClientServer/vtkGDALClientServer.cxx:13:41: > error: invalid conversion from 'vtkObject*' to 'vtkGDAL*' > [-fpermissive] > [paraview] vtkGDAL *op = vtkGDAL::SafeDownCast(ob); > [paraview] ^ > > > Here is a full build log: > https://gist.githubusercontent.com/certik/05d98c5b60664e028eee/raw/gistfile1.txt > > Any ideas what could be causing it? I used git bisect and it said: 25f505c5dc55c9f38df2fbb374e1a8ecdc2479fd is the first bad commit commit 25f505c5dc55c9f38df2fbb374e1a8ecdc2479fd Author: Shawn Waldon Date: Fri Feb 13 16:24:05 2015 -0500 Update VTK to get vtkPointGaussianMapper bugfix Change-Id: I49f288c2a2f8bd9282facb473a26557a4a771a1c This commit only updates the VTK submodule: diff --git a/VTK b/VTK index 96c61c1..8bb1cd3 160000 --- a/VTK +++ b/VTK @@ -1 +1 @@ -Subproject commit 96c61c1cd52e3c4e2e38414b7a703999e4e6fc3e +Subproject commit 8bb1cd3a0799ba9d663547c9c1427cb5a230d3cd So it looks like a bug in VTK. Any ideas how to fix it? Perhaps VTK requires more recent GDAL? I use the one from http://vtk.org/files/support/gdal_5b8309b.tar.gz. Ondrej From gaspare.argento at gmail.com Tue Mar 10 07:25:22 2015 From: gaspare.argento at gmail.com (Gaspare Argento) Date: Tue, 10 Mar 2015 12:25:22 +0100 Subject: [Paraview] CONFIGURING DEFAULT CAMERA 3D MANIPULATORS Message-ID: Hi, I'm trying to change default camera 3D Manipulators editing the JSON file, because I'd like to use the middle button for Zoom and the right one for Pan. So I modified the JSON file adding the following lines: "settings" : { "GeneralSettings" : { "DefaultTimeStep" : 0 }, "RenderViewInteractionSettings" : { "Camera3DManipulators" : [ 4, 2, 1, 3, 4, 1, 2, 4, 2 ] The JSON file seems correct because Paraview open without any problem, however the new 3d Manipulators configuration is not loaded. Any tips? Thanks, Gaspare From utkarsh.ayachit at kitware.com Tue Mar 10 10:45:13 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 10 Mar 2015 10:45:13 -0400 Subject: [Paraview] Segfault when selecting "Unset Visibility" in Multi-block Inspector In-Reply-To: References: Message-ID: Yup, I can reproduce it. I've pushed a fix (http://www.paraview.org/Bug/view.php?id=15367). Attached is the patch against git/master. On Mon, Mar 9, 2015 at 3:29 PM, Ond?ej ?ert?k wrote: > Hi, > > I get a segfault with the git version > f7aac037722d9d13b75d9fdb15a1053c0874c6c6. Here is a minimal set of > steps to reproduce: > > $ wget -O mug.e > https://github.com/idaholab/moose/blob/devel/examples/ex01_inputfile/mug.e?raw=true > $ paraview mug.e > > Click "Apply" > Click "View -> Multi-block Inspector" > Right click the first line in the Multi-block Inspector (mug.e) > Select "Unset Visibility" > > It will immediately segfault (just writes "Segmentation fault" into > the terminal and ends, no other info is printed). > > This seems to happen with any ExodusII mesh that I tried (I just used > some publicly available mesh so that you can reproduce it). Let me > know if you can reproduce the problem. > > Ondrej > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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: 0001-BUG-15367.-Fixes-segfault-in-pqMultiBlockInspectorPa.patch Type: text/x-patch Size: 3781 bytes Desc: not available URL: From robert.maynard at kitware.com Tue Mar 10 10:48:08 2015 From: robert.maynard at kitware.com (Robert Maynard) Date: Tue, 10 Mar 2015 10:48:08 -0400 Subject: [Paraview] Compilation failure with the latest git master In-Reply-To: References: Message-ID: It looks like vtkGDAL is incorrectly being wrapped, even though it has been marked as wrap execluded. On Mon, Mar 9, 2015 at 7:22 PM, Ond?ej ?ert?k wrote: > On Mon, Mar 9, 2015 at 12:54 PM, Ond?ej ?ert?k > wrote: > > Hi, > > > > I have a working version using git > > f7aac037722d9d13b75d9fdb15a1053c0874c6c6. I kept the same versions of > > all the external dependencies (boost, png, qt, zlib, bzip2, gdal, > > hdf5, mpi, netcdf4, netcdf4cpp, freetype, python, numpy, matplotlib, > > libxml2, mesa), but upgraded to the latest git master of ParaView (and > > updated submodules): 7e714de07e6a3c0e376ed634cf83be44be13d733. > > > > Now paraview fails to build with: > > > > [paraview] > /local/certik/tmp/paraview-xx3asav3as7r-1/_build/Wrapping/ClientServer/vtkGDALClientServer.cxx:13:41: > > error: invalid conversion from 'vtkObject*' to 'vtkGDAL*' > > [-fpermissive] > > [paraview] vtkGDAL *op = vtkGDAL::SafeDownCast(ob); > > [paraview] ^ > > > > > > Here is a full build log: > > > https://gist.githubusercontent.com/certik/05d98c5b60664e028eee/raw/gistfile1.txt > > > > Any ideas what could be causing it? > > I used git bisect and it said: > > 25f505c5dc55c9f38df2fbb374e1a8ecdc2479fd is the first bad commit > commit 25f505c5dc55c9f38df2fbb374e1a8ecdc2479fd > Author: Shawn Waldon > Date: Fri Feb 13 16:24:05 2015 -0500 > > Update VTK to get vtkPointGaussianMapper bugfix > > Change-Id: I49f288c2a2f8bd9282facb473a26557a4a771a1c > > This commit only updates the VTK submodule: > > diff --git a/VTK b/VTK > index 96c61c1..8bb1cd3 160000 > --- a/VTK > +++ b/VTK > @@ -1 +1 @@ > -Subproject commit 96c61c1cd52e3c4e2e38414b7a703999e4e6fc3e > +Subproject commit 8bb1cd3a0799ba9d663547c9c1427cb5a230d3cd > > > So it looks like a bug in VTK. Any ideas how to fix it? Perhaps VTK > requires more recent GDAL? I use the one from > http://vtk.org/files/support/gdal_5b8309b.tar.gz. > > Ondrej > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephen.wornom at inria.fr Tue Mar 10 13:01:37 2015 From: stephen.wornom at inria.fr (Stephen Wornom) Date: Tue, 10 Mar 2015 18:01:37 +0100 (CET) Subject: [Paraview] PV 4.1.0: save the data saves only 1/2 of a circle In-Reply-To: References: Message-ID: <243672491.5322107.1426006897929.JavaMail.zimbra@inria.fr> I tried both PV 4.10 and PV 4.31 and get the same result. - extract surface - connectivity - threshold (defines the surface of the cylinder) information shows ymax= 0.5, ymin=-0.5 which is correct as the radius of the circle is 0.5. When I save data, the csv files has all of the y< 0 values. For y>0 most values are missing. For the csv file, ymin= 0.5 but ymax = 0.24. There are actually two circles, could this pose a problem? I really need to solve this problem of missing values. Give me ideas to try, alternative ways to write the data (how do I write only the values for the 1st cylinder to see if this is the problem?). Thanks for your help, Stephen ----- Original Message ----- > From: "Kenneth Moreland" > To: "Stephen Wornom" , "ParaView list" > Sent: Monday, March 9, 2015 6:28:45 PM > Subject: Re: [Paraview] PV 4.1.0: save the data saves only 1/2 of a circle > > Stephen, > > The CSV writer should write out all the points. I tried repeating your > instructions with ParaView 4.3.1 using both the Cylinder source and the > disk_out_ref dataset to write out data for a hollow cylinder source to a > csv file and it looks like it works fine. I can only think of the most > basic things to try: > > * Are you sure your cylinder is centered in the x-y plane? Maybe the > circle is actually sitting below the y axis. Check that with either the > cube axes or the information panel. > * Is the connectivity/threshold filters really the best way to get a > circle from a cylinder. You might consider instead to use the slice filter > to get the circle. (I don't know why that would fix any I/O issues, > though.) > * Is there any chance you can try using the latest version of ParaView. I > don't recall any such problems with the CSV reader in 4.1, but you never > know. > > -Ken > > > > > On 3/9/15, 10:47 AM, "Stephen Wornom" wrote: > > >I have a cylinder ( a circle in the x-y plane, z is the span direction). > >I do: > >- extract surface > >- connectivity > >- threshold (defines the surface of the cylinder) > > > >The result is the circle shown in that attached figure. > > > >I want to write the circle values to a file so I save the data. > > The problem is that PV4.10 saves only 1/2 half of the data (y<0). For > >y> 0 only 4 points are written to the csv file, 124 points for y <0. > > > >How can I save the data so that all values are written? > >Hope the question is clear. > >Stephen > > > >-- > >stephen.wornom at inria.fr > >2004 route des lucioles - BP93 > >Sophia Antipolis > >06902 CEDEX > > > >Tel: 04 92 38 50 54 > >Fax: 04 97 15 53 51 > > > > From kmorel at sandia.gov Tue Mar 10 13:06:06 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Tue, 10 Mar 2015 17:06:06 +0000 Subject: [Paraview] PV 4.1.0: save the data saves only 1/2 of a circle Message-ID: Is there any way you can share your data? That might help diagnose the problem. On 3/10/15, 11:01 AM, "Stephen Wornom" wrote: >I tried both PV 4.10 and PV 4.31 and get the same result. >- extract surface >- connectivity >- threshold (defines the surface of the cylinder) > >information shows ymax= 0.5, ymin=-0.5 which is correct as the radius of >the circle is 0.5. >When I save data, the csv files has all of the y< 0 values. For y>0 most >values are missing. >For the csv file, ymin= 0.5 but ymax = 0.24. > >There are actually two circles, could this pose a problem? > >I really need to solve this problem of missing values. >Give me ideas to try, alternative ways to write the data (how do I write >only the values for the 1st cylinder to see if this is the problem?). >Thanks for your help, >Stephen > > >----- Original Message ----- >> From: "Kenneth Moreland" >> To: "Stephen Wornom" , "ParaView list" >> >> Sent: Monday, March 9, 2015 6:28:45 PM >> Subject: Re: [Paraview] PV 4.1.0: save the data saves only 1/2 of a >>circle >> >> Stephen, >> >> The CSV writer should write out all the points. I tried repeating your >> instructions with ParaView 4.3.1 using both the Cylinder source and the >> disk_out_ref dataset to write out data for a hollow cylinder source to a >> csv file and it looks like it works fine. I can only think of the most >> basic things to try: >> >> * Are you sure your cylinder is centered in the x-y plane? Maybe the >> circle is actually sitting below the y axis. Check that with either the >> cube axes or the information panel. >> * Is the connectivity/threshold filters really the best way to get a >> circle from a cylinder. You might consider instead to use the slice >>filter >> to get the circle. (I don't know why that would fix any I/O issues, >> though.) >> * Is there any chance you can try using the latest version of ParaView. >>I >> don't recall any such problems with the CSV reader in 4.1, but you never >> know. >> >> -Ken >> >> >> >> >> On 3/9/15, 10:47 AM, "Stephen Wornom" wrote: >> >> >I have a cylinder ( a circle in the x-y plane, z is the span >>direction). >> >I do: >> >- extract surface >> >- connectivity >> >- threshold (defines the surface of the cylinder) >> > >> >The result is the circle shown in that attached figure. >> > >> >I want to write the circle values to a file so I save the data. >> > The problem is that PV4.10 saves only 1/2 half of the data (y<0). >>For >> >y> 0 only 4 points are written to the csv file, 124 points for y <0. >> > >> >How can I save the data so that all values are written? >> >Hope the question is clear. >> >Stephen >> > >> >-- >> >stephen.wornom at inria.fr >> >2004 route des lucioles - BP93 >> >Sophia Antipolis >> >06902 CEDEX >> > >> >Tel: 04 92 38 50 54 >> >Fax: 04 97 15 53 51 >> > >> >> From utkarsh.ayachit at kitware.com Tue Mar 10 13:43:46 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 10 Mar 2015 13:43:46 -0400 Subject: [Paraview] Compilation failure with the latest git master In-Reply-To: References: Message-ID: Ondrej, Can you try the attached patch to see if that helps? It's a VTK patch, so you'll need to apply in in the ParaView/VTK directory. Thanks Utkarsh On Tue, Mar 10, 2015 at 10:48 AM, Robert Maynard wrote: > It looks like vtkGDAL is incorrectly being wrapped, even though it has been > marked as wrap execluded. > > On Mon, Mar 9, 2015 at 7:22 PM, Ond?ej ?ert?k > wrote: >> >> On Mon, Mar 9, 2015 at 12:54 PM, Ond?ej ?ert?k >> wrote: >> > Hi, >> > >> > I have a working version using git >> > f7aac037722d9d13b75d9fdb15a1053c0874c6c6. I kept the same versions of >> > all the external dependencies (boost, png, qt, zlib, bzip2, gdal, >> > hdf5, mpi, netcdf4, netcdf4cpp, freetype, python, numpy, matplotlib, >> > libxml2, mesa), but upgraded to the latest git master of ParaView (and >> > updated submodules): 7e714de07e6a3c0e376ed634cf83be44be13d733. >> > >> > Now paraview fails to build with: >> > >> > [paraview] >> > /local/certik/tmp/paraview-xx3asav3as7r-1/_build/Wrapping/ClientServer/vtkGDALClientServer.cxx:13:41: >> > error: invalid conversion from 'vtkObject*' to 'vtkGDAL*' >> > [-fpermissive] >> > [paraview] vtkGDAL *op = vtkGDAL::SafeDownCast(ob); >> > [paraview] ^ >> > >> > >> > Here is a full build log: >> > >> > https://gist.githubusercontent.com/certik/05d98c5b60664e028eee/raw/gistfile1.txt >> > >> > Any ideas what could be causing it? >> >> I used git bisect and it said: >> >> 25f505c5dc55c9f38df2fbb374e1a8ecdc2479fd is the first bad commit >> commit 25f505c5dc55c9f38df2fbb374e1a8ecdc2479fd >> Author: Shawn Waldon >> Date: Fri Feb 13 16:24:05 2015 -0500 >> >> Update VTK to get vtkPointGaussianMapper bugfix >> >> Change-Id: I49f288c2a2f8bd9282facb473a26557a4a771a1c >> >> This commit only updates the VTK submodule: >> >> diff --git a/VTK b/VTK >> index 96c61c1..8bb1cd3 160000 >> --- a/VTK >> +++ b/VTK >> @@ -1 +1 @@ >> -Subproject commit 96c61c1cd52e3c4e2e38414b7a703999e4e6fc3e >> +Subproject commit 8bb1cd3a0799ba9d663547c9c1427cb5a230d3cd >> >> >> So it looks like a bug in VTK. Any ideas how to fix it? Perhaps VTK >> requires more recent GDAL? I use the one from >> http://vtk.org/files/support/gdal_5b8309b.tar.gz. >> >> Ondrej >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- A non-text attachment was scrubbed... Name: FixGDAL.patch Type: text/x-patch Size: 486 bytes Desc: not available URL: From ondrej.certik at gmail.com Tue Mar 10 15:06:30 2015 From: ondrej.certik at gmail.com (=?UTF-8?B?T25kxZllaiDEjGVydMOtaw==?=) Date: Tue, 10 Mar 2015 13:06:30 -0600 Subject: [Paraview] Compilation failure with the latest git master In-Reply-To: References: Message-ID: Hi Utkarsh, On Tue, Mar 10, 2015 at 11:43 AM, Utkarsh Ayachit wrote: > Ondrej, > > Can you try the attached patch to see if that helps? It's a VTK patch, > so you'll need to apply in in the ParaView/VTK directory. It works!! Thanks a lot for figuring out what the problem was. So it looks like it was caused by: https://github.com/Kitware/VTK/commit/9b41015660e20fdb92d13ffcef9015f138e34b33 Was my machine the only place it failed? Ondrej > > Thanks > Utkarsh > > On Tue, Mar 10, 2015 at 10:48 AM, Robert Maynard > wrote: >> It looks like vtkGDAL is incorrectly being wrapped, even though it has been >> marked as wrap execluded. >> >> On Mon, Mar 9, 2015 at 7:22 PM, Ond?ej ?ert?k >> wrote: >>> >>> On Mon, Mar 9, 2015 at 12:54 PM, Ond?ej ?ert?k >>> wrote: >>> > Hi, >>> > >>> > I have a working version using git >>> > f7aac037722d9d13b75d9fdb15a1053c0874c6c6. I kept the same versions of >>> > all the external dependencies (boost, png, qt, zlib, bzip2, gdal, >>> > hdf5, mpi, netcdf4, netcdf4cpp, freetype, python, numpy, matplotlib, >>> > libxml2, mesa), but upgraded to the latest git master of ParaView (and >>> > updated submodules): 7e714de07e6a3c0e376ed634cf83be44be13d733. >>> > >>> > Now paraview fails to build with: >>> > >>> > [paraview] >>> > /local/certik/tmp/paraview-xx3asav3as7r-1/_build/Wrapping/ClientServer/vtkGDALClientServer.cxx:13:41: >>> > error: invalid conversion from 'vtkObject*' to 'vtkGDAL*' >>> > [-fpermissive] >>> > [paraview] vtkGDAL *op = vtkGDAL::SafeDownCast(ob); >>> > [paraview] ^ >>> > >>> > >>> > Here is a full build log: >>> > >>> > https://gist.githubusercontent.com/certik/05d98c5b60664e028eee/raw/gistfile1.txt >>> > >>> > Any ideas what could be causing it? >>> >>> I used git bisect and it said: >>> >>> 25f505c5dc55c9f38df2fbb374e1a8ecdc2479fd is the first bad commit >>> commit 25f505c5dc55c9f38df2fbb374e1a8ecdc2479fd >>> Author: Shawn Waldon >>> Date: Fri Feb 13 16:24:05 2015 -0500 >>> >>> Update VTK to get vtkPointGaussianMapper bugfix >>> >>> Change-Id: I49f288c2a2f8bd9282facb473a26557a4a771a1c >>> >>> This commit only updates the VTK submodule: >>> >>> diff --git a/VTK b/VTK >>> index 96c61c1..8bb1cd3 160000 >>> --- a/VTK >>> +++ b/VTK >>> @@ -1 +1 @@ >>> -Subproject commit 96c61c1cd52e3c4e2e38414b7a703999e4e6fc3e >>> +Subproject commit 8bb1cd3a0799ba9d663547c9c1427cb5a230d3cd >>> >>> >>> So it looks like a bug in VTK. Any ideas how to fix it? Perhaps VTK >>> requires more recent GDAL? I use the one from >>> http://vtk.org/files/support/gdal_5b8309b.tar.gz. >>> >>> Ondrej >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> 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 utkarsh.ayachit at kitware.com Tue Mar 10 15:13:41 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 10 Mar 2015 15:13:41 -0400 Subject: [Paraview] Compilation failure with the latest git master In-Reply-To: References: Message-ID: Cool. John, can you please have the fix merged in VTK/ParaView? Ondrej, it seems that vtkIOGDAL module is not enabled in ParaView by default. Did you enable it explicitly? That'd explain why it's not failing on the dashboards. Utkarsh On Tue, Mar 10, 2015 at 3:06 PM, Ond?ej ?ert?k wrote: > Hi Utkarsh, > > On Tue, Mar 10, 2015 at 11:43 AM, Utkarsh Ayachit > wrote: >> Ondrej, >> >> Can you try the attached patch to see if that helps? It's a VTK patch, >> so you'll need to apply in in the ParaView/VTK directory. > > It works!! Thanks a lot for figuring out what the problem was. So it > looks like it was caused by: > > https://github.com/Kitware/VTK/commit/9b41015660e20fdb92d13ffcef9015f138e34b33 > > Was my machine the only place it failed? > > Ondrej > >> >> Thanks >> Utkarsh >> >> On Tue, Mar 10, 2015 at 10:48 AM, Robert Maynard >> wrote: >>> It looks like vtkGDAL is incorrectly being wrapped, even though it has been >>> marked as wrap execluded. >>> >>> On Mon, Mar 9, 2015 at 7:22 PM, Ond?ej ?ert?k >>> wrote: >>>> >>>> On Mon, Mar 9, 2015 at 12:54 PM, Ond?ej ?ert?k >>>> wrote: >>>> > Hi, >>>> > >>>> > I have a working version using git >>>> > f7aac037722d9d13b75d9fdb15a1053c0874c6c6. I kept the same versions of >>>> > all the external dependencies (boost, png, qt, zlib, bzip2, gdal, >>>> > hdf5, mpi, netcdf4, netcdf4cpp, freetype, python, numpy, matplotlib, >>>> > libxml2, mesa), but upgraded to the latest git master of ParaView (and >>>> > updated submodules): 7e714de07e6a3c0e376ed634cf83be44be13d733. >>>> > >>>> > Now paraview fails to build with: >>>> > >>>> > [paraview] >>>> > /local/certik/tmp/paraview-xx3asav3as7r-1/_build/Wrapping/ClientServer/vtkGDALClientServer.cxx:13:41: >>>> > error: invalid conversion from 'vtkObject*' to 'vtkGDAL*' >>>> > [-fpermissive] >>>> > [paraview] vtkGDAL *op = vtkGDAL::SafeDownCast(ob); >>>> > [paraview] ^ >>>> > >>>> > >>>> > Here is a full build log: >>>> > >>>> > https://gist.githubusercontent.com/certik/05d98c5b60664e028eee/raw/gistfile1.txt >>>> > >>>> > Any ideas what could be causing it? >>>> >>>> I used git bisect and it said: >>>> >>>> 25f505c5dc55c9f38df2fbb374e1a8ecdc2479fd is the first bad commit >>>> commit 25f505c5dc55c9f38df2fbb374e1a8ecdc2479fd >>>> Author: Shawn Waldon >>>> Date: Fri Feb 13 16:24:05 2015 -0500 >>>> >>>> Update VTK to get vtkPointGaussianMapper bugfix >>>> >>>> Change-Id: I49f288c2a2f8bd9282facb473a26557a4a771a1c >>>> >>>> This commit only updates the VTK submodule: >>>> >>>> diff --git a/VTK b/VTK >>>> index 96c61c1..8bb1cd3 160000 >>>> --- a/VTK >>>> +++ b/VTK >>>> @@ -1 +1 @@ >>>> -Subproject commit 96c61c1cd52e3c4e2e38414b7a703999e4e6fc3e >>>> +Subproject commit 8bb1cd3a0799ba9d663547c9c1427cb5a230d3cd >>>> >>>> >>>> So it looks like a bug in VTK. Any ideas how to fix it? Perhaps VTK >>>> requires more recent GDAL? I use the one from >>>> http://vtk.org/files/support/gdal_5b8309b.tar.gz. >>>> >>>> Ondrej >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> 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 ondrej.certik at gmail.com Tue Mar 10 15:19:38 2015 From: ondrej.certik at gmail.com (=?UTF-8?B?T25kxZllaiDEjGVydMOtaw==?=) Date: Tue, 10 Mar 2015 13:19:38 -0600 Subject: [Paraview] Compilation failure with the latest git master In-Reply-To: References: Message-ID: On Tue, Mar 10, 2015 at 1:13 PM, Utkarsh Ayachit wrote: > Cool. John, can you please have the fix merged in VTK/ParaView? > > Ondrej, it seems that vtkIOGDAL module is not enabled in ParaView by > default. Did you enable it explicitly? That'd explain why it's not > failing on the dashboards. Ah I see -- yes, we had '-DModule_vtkIOGDAL:BOOL=ON'. Robert created the initial script, here is what we use: https://github.com/hashdist/hashstack/blob/ac8ccec893e9e9ae6b9b6bbce0c6ed5541509d7e/pkgs/paraview/paraview.yaml And to fix it, I just added your patch in, as follows: diff --git a/pkgs/paraview/FixGDAL.patch b/pkgs/paraview/FixGDAL.patch new file mode 100644 index 0000000..4ed413d --- /dev/null +++ b/pkgs/paraview/FixGDAL.patch @@ -0,0 +1,13 @@ +diff --git a/IO/GDAL/CMakeLists.txt b/IO/GDAL/CMakeLists.txt +index 9cb8fe6..eb1b582 100644 +--- a/IO/GDAL/CMakeLists.txt ++++ b/IO/GDAL/CMakeLists.txt +@@ -4,7 +4,7 @@ mark_as_advanced(GDAL_INCLUDE_DIR GDAL_LIBRARY) + set(GDAL_SRCS vtkGDAL.cxx vtkGDALVectorReader.cxx vtkGDALRasterReader.cxx) + + include_directories(${GDAL_INCLUDE_DIRS}) +-set_source_files_properties(vtkGDAL.h WRAP_EXCLUDE) ++set_source_files_properties(vtkGDAL WRAP_EXCLUDE) + + vtk_module_library(vtkIOGDAL ${GDAL_SRCS}) + diff --git a/pkgs/paraview/paraview.yaml b/pkgs/paraview/paraview.yaml index e05a7cb..4cba6ff 100644 --- a/pkgs/paraview/paraview.yaml +++ b/pkgs/paraview/paraview.yaml @@ -5,7 +5,7 @@ dependencies: python, numpy, matplotlib, libxml2, {{build_with}}] sources: -- key: git:f7aac037722d9d13b75d9fdb15a1053c0874c6c6 +- key: git:0a4ad038370beb6d30f51f43e32555b3adcea123 url: https://github.com/Kitware/ParaView.git defaults: @@ -20,6 +20,13 @@ build_stages: bash: | patch -up1 < _hashdist/installGenerateFiles.patch +- name: patch5 + before: configure + files: [FixGDAL.patch] + handler: bash + bash: | + (cd VTK; patch -up1 < ../_hashdist/FixGDAL.patch) + - name: configure mode: override extra: [ I'll wait until you fix it in VTK and update the VTK submodule in Paraview, and then just use the latest git master. But the above fixes it. Thanks again for figuring it out so quickly. Ondrej From ondrej.certik at gmail.com Tue Mar 10 16:59:13 2015 From: ondrej.certik at gmail.com (=?UTF-8?B?T25kxZllaiDEjGVydMOtaw==?=) Date: Tue, 10 Mar 2015 14:59:13 -0600 Subject: [Paraview] vtkBlockColors legend should show correct sideset IDs Message-ID: Hi, I am testing the new vtkBlockColors feature in the latest Paraview (I am using 0a4ad038370beb6d30f51f43e32555b3adcea123), as introduced in the blog post: http://www.kitware.com/blog/home/post/859 Currently the legend shows colors with numbers 0-6. However, many times the sidesets in an ExodusII file are not labeled like that. I am attaching a screenshot with an example. As you can see, both the Properties as well as Multi-block Inspector shows the correct side set ID numbers (1, 5, 10, 15), but the vtkBlockColors legend shows numbers 0-6. Note that if I color by vtkCompositeIndex, the legend shows the correct side set ID, but the problem is that it's a continuous legend, and the colors are close to each other, so it's hard (essentially impossible) to tell what the ID is from the color. I understand the user case when there is thousands of blocks. But I think there is also a use case when there is relatively few (~10) boundary conditions, and you just want to see them all at once using a legend, so that you can take a screenshot and send it to somebody. Maybe there can be some check-box that would switch the two modes of the legend. Currently the best way seems to be to use vtkBlockColors, and then send a screenshot that includes the Multi-block Inspector window, which also shows the colors and proper IDs. There is also the issue of Block ID versus Side Set ID (as a side set can have the same id as a block set), I usually turn one or the other off in Multi-block Inspector, then they are not mixed. Let me know what you think. Ondrej -------------- next part -------------- A non-text attachment was scrubbed... Name: paraview_vtkBlockColors.png Type: image/png Size: 85665 bytes Desc: not available URL: From arctica1963 at gmail.com Tue Mar 10 18:43:01 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Tue, 10 Mar 2015 22:43:01 +0000 Subject: [Paraview] Earthquake focal mechanism solution (3D "beach ball" plot) Message-ID: Hello, Just a quick query to see if anyone knows of any code for generating the 3D beach ball plots of earthquake focal mechanism solution in ParaView? It is easy to load up hypocentre data into ParaView but not the motion solutions eg from Global CMT. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephen.wornom at inria.fr Wed Mar 11 08:57:13 2015 From: stephen.wornom at inria.fr (Stephen Wornom) Date: Wed, 11 Mar 2015 13:57:13 +0100 Subject: [Paraview] PV 4.1.0: save the data saves only 1/2 of a circle In-Reply-To: References: Message-ID: <55003BA9.3050004@inria.fr> Moreland, Kenneth wrote: > Is there any way you can share your data? That might help diagnose the > problem. Yes, I will send it. I did an additional test with a single cylinder and the file is written correctly. So it appears that the problem occurs only with two tandem cylinders in the mesh. Stephen > > > On 3/10/15, 11:01 AM, "Stephen Wornom" wrote: > >> I tried both PV 4.10 and PV 4.31 and get the same result. >> - extract surface >> - connectivity >> - threshold (defines the surface of the cylinder) >> >> information shows ymax= 0.5, ymin=-0.5 which is correct as the radius of >> the circle is 0.5. >> When I save data, the csv files has all of the y< 0 values. For y>0 most >> values are missing. >> For the csv file, ymin= 0.5 but ymax = 0.24. >> >> There are actually two circles, could this pose a problem? >> >> I really need to solve this problem of missing values. >> Give me ideas to try, alternative ways to write the data (how do I write >> only the values for the 1st cylinder to see if this is the problem?). >> Thanks for your help, >> Stephen >> >> >> ----- Original Message ----- >>> From: "Kenneth Moreland" >>> To: "Stephen Wornom" , "ParaView list" >>> >>> Sent: Monday, March 9, 2015 6:28:45 PM >>> Subject: Re: [Paraview] PV 4.1.0: save the data saves only 1/2 of a >>> circle >>> >>> Stephen, >>> >>> The CSV writer should write out all the points. I tried repeating your >>> instructions with ParaView 4.3.1 using both the Cylinder source and the >>> disk_out_ref dataset to write out data for a hollow cylinder source to a >>> csv file and it looks like it works fine. I can only think of the most >>> basic things to try: >>> >>> * Are you sure your cylinder is centered in the x-y plane? Maybe the >>> circle is actually sitting below the y axis. Check that with either the >>> cube axes or the information panel. >>> * Is the connectivity/threshold filters really the best way to get a >>> circle from a cylinder. You might consider instead to use the slice >>> filter >>> to get the circle. (I don't know why that would fix any I/O issues, >>> though.) >>> * Is there any chance you can try using the latest version of ParaView. >>> I >>> don't recall any such problems with the CSV reader in 4.1, but you never >>> know. >>> >>> -Ken >>> >>> >>> >>> >>> On 3/9/15, 10:47 AM, "Stephen Wornom" wrote: >>> >>>> I have a cylinder ( a circle in the x-y plane, z is the span >>> direction). >>>> I do: >>>> - extract surface >>>> - connectivity >>>> - threshold (defines the surface of the cylinder) >>>> >>>> The result is the circle shown in that attached figure. >>>> >>>> I want to write the circle values to a file so I save the data. >>>> The problem is that PV4.10 saves only 1/2 half of the data (y<0). >>> For >>>> y> 0 only 4 points are written to the csv file, 124 points for y <0. >>>> >>>> How can I save the data so that all values are written? >>>> Hope the question is clear. >>>> Stephen >>>> >>>> -- >>>> stephen.wornom at inria.fr >>>> 2004 route des lucioles - BP93 >>>> Sophia Antipolis >>>> 06902 CEDEX >>>> >>>> Tel: 04 92 38 50 54 >>>> Fax: 04 97 15 53 51 >>>> >>> -- stephen.wornom at inria.fr 2004 route des lucioles - BP93 Sophia Antipolis 06902 CEDEX Tel: 04 92 38 50 54 Fax: 04 97 15 53 51 -------------- next part -------------- A non-text attachment was scrubbed... Name: stephen_wornom.vcf Type: text/x-vcard Size: 187 bytes Desc: not available URL: From tweyens at fis.uc3m.es Wed Mar 11 10:09:13 2015 From: tweyens at fis.uc3m.es (Toon) Date: Wed, 11 Mar 2015 14:09:13 +0000 (UTC) Subject: [Paraview] storing tensors in hdf5? References: <4DA05F0B.70902@gmail.com> <4DA23B2E.30105@gmail.com> <4DA33CE3.4040407@gmail.com> Message-ID: Pratik Mallya gmail.com> writes: > > Pratik Mallya wrote: > > Pratik Mallya wrote: > >> Well, that is why i chose the subject title to be so :). > >> In particular, I since I am using numpy (and h5py) to calculate the > >> tensor, I am storing the result (a 256X256X9 ndarray named Q) into h5 > >> file by using a command of the form: > >> g.create_dataset("Q", data=Q) > >> Does the problem lie here? Am i supposed to use a different > >> format/function of h5py, or something? Because I can see the .h5 > >> file using hdfview, and it seems perfectly all right. > >> > >> > > I figured out a workaround: although my h5 file has nine component(3 > > are redundant since it is a symmetric tensor) i am reading it as a 6 > > component tensor, and paraview is now able to read it! > > I wonder why this is the case? I have already detailed the code in > > previous mail; can someone please tell me why it is working like this? > > > > Thanks in anticipation. > > > Well...no one seemed to have cared to reply. > Anyways, it turns out that in the xdmf file, if you supply the dimension > as one less than what is present in the .h5 file, then the xdmf reader > can properly read the thing. e.g since the tensors i was storing were in > the shape (1,9) (each tensor), i gave the topology as "1 8", and then it > read the data, no complaints and perfect plot :). > Thank you Pratik! I have had similar problems when I tried to read my old XDMF files after reinstalling my whole system. It appears that sometimes I used 3 dimensions for 2D plots (even though I still defined it as 2D, for example with 2Dsmesh). One of the dimensions would then be 1, of course. This never gave me problems in the past but now it did. The solution was to adapt my XDMF routines to output only the indices that are bigger than 1. Now it works! Thanks again! From kmorel at sandia.gov Wed Mar 11 11:55:06 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Wed, 11 Mar 2015 15:55:06 +0000 Subject: [Paraview] PV 4.1.0: save the data saves only 1/2 of a circle Message-ID: Stephen, I got your data and tried again. Once again I cannot replicate your error. When I open up the csv file in Excel, I get the number of rows I expect and the bounds of Y are what I expect. I tried both on a serial process and using a parallel job (in case there was a problem with writing CSV in parallel, which there has been in the past but has since been fixed). When you sent the file to me, you mentioned some further instructions I didn't understand about modifying the csv file and loading it indirectly through an inp file. I don't know anything about the inp format (and there appear to be three readers of different formats that expect that extension), but perhaps the real problem is in the inp reader? Did you try looking at the csv file directly in a text editor or spreadsheet program? -Ken On 3/11/15, 6:57 AM, "Stephen Wornom" wrote: >Moreland, Kenneth wrote: >> Is there any way you can share your data? That might help diagnose the >> problem. >Yes, I will send it. I did an additional test with a single cylinder and >the file is written correctly. So it appears that the problem occurs >only with two tandem cylinders in the mesh. >Stephen >> >> >> On 3/10/15, 11:01 AM, "Stephen Wornom" wrote: >> >>> I tried both PV 4.10 and PV 4.31 and get the same result. >>> - extract surface >>> - connectivity >>> - threshold (defines the surface of the cylinder) >>> >>> information shows ymax= 0.5, ymin=-0.5 which is correct as the radius >>>of >>> the circle is 0.5. >>> When I save data, the csv files has all of the y< 0 values. For y>0 >>>most >>> values are missing. >>> For the csv file, ymin= 0.5 but ymax = 0.24. >>> >>> There are actually two circles, could this pose a problem? >>> >>> I really need to solve this problem of missing values. >>> Give me ideas to try, alternative ways to write the data (how do I >>>write >>> only the values for the 1st cylinder to see if this is the problem?). >>> Thanks for your help, >>> Stephen >>> >>> >>> ----- Original Message ----- >>>> From: "Kenneth Moreland" >>>> To: "Stephen Wornom" , "ParaView list" >>>> >>>> Sent: Monday, March 9, 2015 6:28:45 PM >>>> Subject: Re: [Paraview] PV 4.1.0: save the data saves only 1/2 of a >>>> circle >>>> >>>> Stephen, >>>> >>>> The CSV writer should write out all the points. I tried repeating your >>>> instructions with ParaView 4.3.1 using both the Cylinder source and >>>>the >>>> disk_out_ref dataset to write out data for a hollow cylinder source >>>>to a >>>> csv file and it looks like it works fine. I can only think of the most >>>> basic things to try: >>>> >>>> * Are you sure your cylinder is centered in the x-y plane? Maybe the >>>> circle is actually sitting below the y axis. Check that with either >>>>the >>>> cube axes or the information panel. >>>> * Is the connectivity/threshold filters really the best way to get a >>>> circle from a cylinder. You might consider instead to use the slice >>>> filter >>>> to get the circle. (I don't know why that would fix any I/O issues, >>>> though.) >>>> * Is there any chance you can try using the latest version of >>>>ParaView. >>>> I >>>> don't recall any such problems with the CSV reader in 4.1, but you >>>>never >>>> know. >>>> >>>> -Ken >>>> >>>> >>>> >>>> >>>> On 3/9/15, 10:47 AM, "Stephen Wornom" wrote: >>>> >>>>> I have a cylinder ( a circle in the x-y plane, z is the span >>>> direction). >>>>> I do: >>>>> - extract surface >>>>> - connectivity >>>>> - threshold (defines the surface of the cylinder) >>>>> >>>>> The result is the circle shown in that attached figure. >>>>> >>>>> I want to write the circle values to a file so I save the data. >>>>> The problem is that PV4.10 saves only 1/2 half of the data (y<0). >>>> For >>>>> y> 0 only 4 points are written to the csv file, 124 points for y <0. >>>>> >>>>> How can I save the data so that all values are written? >>>>> Hope the question is clear. >>>>> Stephen >>>>> >>>>> -- >>>>> stephen.wornom at inria.fr >>>>> 2004 route des lucioles - BP93 >>>>> Sophia Antipolis >>>>> 06902 CEDEX >>>>> >>>>> Tel: 04 92 38 50 54 >>>>> Fax: 04 97 15 53 51 >>>>> >>>> > > >-- >stephen.wornom at inria.fr >2004 route des lucioles - BP93 >Sophia Antipolis >06902 CEDEX > >Tel: 04 92 38 50 54 >Fax: 04 97 15 53 51 > From stephen.wornom at inria.fr Wed Mar 11 12:16:52 2015 From: stephen.wornom at inria.fr (Stephen Wornom) Date: Wed, 11 Mar 2015 17:16:52 +0100 (CET) Subject: [Paraview] PV 4.1.0: save the data saves only 1/2 of a circle In-Reply-To: References: Message-ID: <222342041.5736223.1426090612462.JavaMail.zimbra@inria.fr> ----- Original Message ----- > From: "Kenneth Moreland" > To: "Stephen Wornom" > Cc: "ParaView list" > Sent: Wednesday, March 11, 2015 4:55:06 PM > Subject: Re: [Paraview] PV 4.1.0: save the data saves only 1/2 of a circle > > Stephen, > > I got your data and tried again. Once again I cannot replicate your error. > When I open up the csv file in Excel, I get the number of rows I expect > and the bounds of Y are what I expect. I tried both on a serial process > and using a parallel job (in case there was a problem with writing CSV in > parallel, which there has been in the past but has since been fixed). > > When you sent the file to me, you mentioned some further instructions I > didn't understand about modifying the csv file and loading it indirectly > through an inp file. I don't know anything about the inp format (and there > appear to be three readers of different formats that expect that > extension), but perhaps the real problem is in the inp reader? Did you try > looking at the csv file directly in a text editor or spreadsheet program? I will look at the inp file and see if how I read the csv file (recall that I replace the commas with blanks) in fortran could be a problem. I forgot to mention that I am running on my linux workstation the 64-bit binary versions of PV 4.1.0 and 4.3.1 that I downloaded from paraview web site. Are you using the binary or an installation from source on your workstation?. It is strange that for a single cylinder I get the correct number of values for the upper and lower parts of the cylinder. The problem occurs when there two cylinders. I will look at the excel files and if it is correct, maybe I can save it in text format that I can read into gnuplot. I have no experience with excel nor reading csv in gnuplot scripts. Will keep you posted. Stephen > > -Ken > > > > On 3/11/15, 6:57 AM, "Stephen Wornom" wrote: > > >Moreland, Kenneth wrote: > >> Is there any way you can share your data? That might help diagnose the > >> problem. > >Yes, I will send it. I did an additional test with a single cylinder and > >the file is written correctly. So it appears that the problem occurs > >only with two tandem cylinders in the mesh. > >Stephen > >> > >> > >> On 3/10/15, 11:01 AM, "Stephen Wornom" wrote: > >> > >>> I tried both PV 4.10 and PV 4.31 and get the same result. > >>> - extract surface > >>> - connectivity > >>> - threshold (defines the surface of the cylinder) > >>> > >>> information shows ymax= 0.5, ymin=-0.5 which is correct as the radius > >>>of > >>> the circle is 0.5. > >>> When I save data, the csv files has all of the y< 0 values. For y>0 > >>>most > >>> values are missing. > >>> For the csv file, ymin= 0.5 but ymax = 0.24. > >>> > >>> There are actually two circles, could this pose a problem? > >>> > >>> I really need to solve this problem of missing values. > >>> Give me ideas to try, alternative ways to write the data (how do I > >>>write > >>> only the values for the 1st cylinder to see if this is the problem?). > >>> Thanks for your help, > >>> Stephen > >>> > >>> > >>> ----- Original Message ----- > >>>> From: "Kenneth Moreland" > >>>> To: "Stephen Wornom" , "ParaView list" > >>>> > >>>> Sent: Monday, March 9, 2015 6:28:45 PM > >>>> Subject: Re: [Paraview] PV 4.1.0: save the data saves only 1/2 of a > >>>> circle > >>>> > >>>> Stephen, > >>>> > >>>> The CSV writer should write out all the points. I tried repeating your > >>>> instructions with ParaView 4.3.1 using both the Cylinder source and > >>>>the > >>>> disk_out_ref dataset to write out data for a hollow cylinder source > >>>>to a > >>>> csv file and it looks like it works fine. I can only think of the most > >>>> basic things to try: > >>>> > >>>> * Are you sure your cylinder is centered in the x-y plane? Maybe the > >>>> circle is actually sitting below the y axis. Check that with either > >>>>the > >>>> cube axes or the information panel. > >>>> * Is the connectivity/threshold filters really the best way to get a > >>>> circle from a cylinder. You might consider instead to use the slice > >>>> filter > >>>> to get the circle. (I don't know why that would fix any I/O issues, > >>>> though.) > >>>> * Is there any chance you can try using the latest version of > >>>>ParaView. > >>>> I > >>>> don't recall any such problems with the CSV reader in 4.1, but you > >>>>never > >>>> know. > >>>> > >>>> -Ken > >>>> > >>>> > >>>> > >>>> > >>>> On 3/9/15, 10:47 AM, "Stephen Wornom" wrote: > >>>> > >>>>> I have a cylinder ( a circle in the x-y plane, z is the span > >>>> direction). > >>>>> I do: > >>>>> - extract surface > >>>>> - connectivity > >>>>> - threshold (defines the surface of the cylinder) > >>>>> > >>>>> The result is the circle shown in that attached figure. > >>>>> > >>>>> I want to write the circle values to a file so I save the data. > >>>>> The problem is that PV4.10 saves only 1/2 half of the data (y<0). > >>>> For > >>>>> y> 0 only 4 points are written to the csv file, 124 points for y <0. > >>>>> > >>>>> How can I save the data so that all values are written? > >>>>> Hope the question is clear. > >>>>> Stephen > >>>>> > >>>>> -- > >>>>> stephen.wornom at inria.fr > >>>>> 2004 route des lucioles - BP93 > >>>>> Sophia Antipolis > >>>>> 06902 CEDEX > >>>>> > >>>>> Tel: 04 92 38 50 54 > >>>>> Fax: 04 97 15 53 51 > >>>>> > >>>> > > > > > >-- > >stephen.wornom at inria.fr > >2004 route des lucioles - BP93 > >Sophia Antipolis > >06902 CEDEX > > > >Tel: 04 92 38 50 54 > >Fax: 04 97 15 53 51 > > > > From danielbruno at gmail.com Wed Mar 11 12:24:46 2015 From: danielbruno at gmail.com (Daniel Bruno) Date: Wed, 11 Mar 2015 13:24:46 -0300 Subject: [Paraview] Density of streamlines using StreamTracerWithCustomSource In-Reply-To: References: Message-ID: Hi. Andy. Thank you for your quick reply. I understand your point but my source is a surface area (in fact it is the inlet BC that has a rectangular shape). By what you said there should be no means of controlling streamlines density. Regards, Daniel. Daniel. On Wed, Mar 4, 2015 at 3:33 PM, Andy Bauer wrote: > I believe that the streamline density is based on the points from the > custom source. If you add or remove points in the custom source you should > get more or less streamlines, respectively. > > On Wed, Mar 4, 2015 at 1:05 PM, Daniel Bruno > wrote: > >> Hello all. >> >> I'm using StreamTracerWithCustomSource filter to generate streamlines >> shed from a specific surface. There are no problems to achieve my goals but >> I was not able to find a way to control the density of streamlines. >> >> Is it possible to control the number of streamlines that are shed when >> using StreamTracerWithCustomSource filter? >> >> Thank you so much for your help. >> >> Regards, >> >> >> Daniel. >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 Wed Mar 11 13:12:33 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Wed, 11 Mar 2015 19:12:33 +0200 Subject: [Paraview] Import of XDMF/HDF5:Cell centered attribute of 2D Rectangular grid In-Reply-To: References: Message-ID: <55007781.7000306@gmail.com> Here is the 3DRectMesh example I promised, it even includes a temporal collection. I also attached the headers (h5dump -H data.h5) of the corresponding HDF5 data file. I created the XDMF file with a hand-crafted python script (using h5py and xml.etree.cElementTree). Hope it helps you to sort out things... -Armin On 03/06/2015 11:55 PM, dkxls23 at gmail.com wrote: > I have had similar problems with 2D structured grids and XDMF in the past. > I never got them to work in ParaView. > > I solved the problem by using 3D grids and set the first dimension (i.e. the slowest varying) one to 1, the same way as you have done it with VXVYVZ. > You just have to adjust your data arrays accordingly, i.e. dimensions 1 82 221 in your example. > > I can send you a working xdmf file when back in the office. > > I believe the computational overhead from 2D to 3D grids with effectively 2 dimensions is rather small. > > Maybe the next-generation XDMF reader in ParaView works better for 2D structued grids or somebody with the knowledge explains us how to write them correctly. :) > > -Armin > > > > On Fri Mar 6 23:17:52 2015 GMT+0200, Canis Major wrote: >> I have troubles importing xdmf output to paraview. >> >> This is an example of xdmf of 0th iteration. >> >> >> >> >> >> >> >> >> >> xdmf2d.h5:/Z >> >> >> >> xdmf2d.h5:/Y >> >> >> xdmf2d.h5:/X >> >> >> > Format="HDF"> >> xdmf2d.0.h5:/pressure >> >> >> >> >> >> >> >> >> I have an error that paraview failed to import attribute. What could >> be wrong? I have played around the parameters nothing helps. >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: data.xmf Type: audio/x-xmf Size: 111331 bytes Desc: not available URL: -------------- next part -------------- HDF5 "data.h5" { GROUP "/" { GROUP "VELOCITY" { ATTRIBUTE "timeUnit" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } GROUP "-0.083" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "-0.183" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "0.017" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "0.117" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "0.217" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "0.317" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "0.417" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "0.517" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "0.617" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "0.717" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "0.817" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "0.917" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "1.017" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "1.117" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "1.217" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "1.317" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "1.417" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "1.517" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "1.617" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "1.717" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "1.817" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "1.917" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "2.017" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "2.117" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "2.217" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "2.317" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "2.417" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "2.517" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "2.617" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "2.717" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "2.817" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "2.917" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "3.017" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "3.117" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "3.217" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "3.317" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "3.417" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "3.517" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "3.617" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "3.717" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "3.817" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "3.917" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "4.017" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "4.117" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "4.217" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "4.317" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "4.417" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "4.517" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "4.617" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "4.717" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "4.817" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "4.917" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "5.017" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "5.117" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "5.217" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "5.317" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "5.417" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "5.517" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "5.617" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "5.717" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "5.817" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "5.917" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "6.017" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "6.117" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "6.217" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "6.317" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "6.417" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "6.517" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "6.617" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "6.717" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "6.817" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "6.917" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "7.017" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } GROUP "7.117" { DATASET "U" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "UstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "V" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "VstdDev" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1, 30, 88 ) / ( 1, 30, 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "X" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 88 ) / ( 88 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Y" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 30 ) / ( 30 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } DATASET "Z" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1 ) / ( 1 ) } ATTRIBUTE "header" { DATATYPE H5T_STRING { STRSIZE H5T_VARIABLE; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_UTF8; CTYPE H5T_C_S1; } DATASPACE SCALAR } } } } } } From cjm2176 at columbia.edu Wed Mar 11 14:04:32 2015 From: cjm2176 at columbia.edu (Colin McAuliffe) Date: Wed, 11 Mar 2015 14:04:32 -0400 Subject: [Paraview] Converting selection types In-Reply-To: References: Message-ID: Can anyone offer a suggestion for this? Thanks for the help. Colin On Fri, Mar 6, 2015 at 6:23 PM, Colin McAuliffe wrote: > Hi everybody, I am scripting in python and would like to be able to do a > plot selection over time of the statistics for a subregion in my domain. > > The plot selection over time filter does not seem to work if I give a > frustum selection source as the selection, but ID selection sources always > work. My current workaround is to do a frustum selection by cell, apply an > extract selection filter, then create an ID selection for all of the points > in the result which then is passed to PSOT. Is there a simpler way to > convert the frustum selection to an ID selection? Thanks, Colin > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dkxls23 at gmail.com Wed Mar 11 14:05:16 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Wed, 11 Mar 2015 20:05:16 +0200 Subject: [Paraview] Import of XDMF/HDF5:Cell centered attribute of 2D Rectangular grid In-Reply-To: <102718772.6116372.1425682478532.JavaMail.root@mail.gatech.edu> References: <102718772.6116372.1425682478532.JavaMail.root@mail.gatech.edu> Message-ID: <550083DC.8000206@gmail.com> Hi all! Thanks a lot Tim for the clarifications on the XDMF/HDF5 data format! You are right, without proper bug reports the potential problems won't be fixed. So, I probably should have reported the not working XDMF files with screenshots, but I just figured that I might do something wrong and got it working otherwise. :) There where two important things that I learned step by step about VTK/XDMF/HDF5: 1. The 2D grids (e.g. 2DRectMesh) allow only two-component vectors, kind of logic, but I also did that mistake. 2. Paraview reads the dimensions, origin and spacing for uniform rectangular meshes (i.e. 2DCoRectMesh and 3DCoRectMesh) in ZYX order as opposed to XYZ. The underlying reason is probably the C memory layout, as Tim already explained (more details can also be found here [1]). However, this behavior is not always consistent in all XDMF readers. For example, the 1D coordinate arrays for a 3DRectMesh (using VXVYVZ) have to be listed in X, Y, Z order, while the dimensions are specified in ZYX order (see my earlier mail for an example). In all cases, the data arrays have to be in reveres (i.e. ZYX) order. Now, when I started to read and write XDMF/HDF5 files, I also had to experiment quite a bit and I believe the major reason why I didn't get the 2D grids working was related to the memory layout. Nowadays, I use XDMF/HDF5 files for almost everything. It's just to easy to have a quick look at the data in ParaView, and one can read them otherwise very nicely with python (using vtk or h5py directly). Though, I haven't looked into the more advanced stuff like hyperslabs and the like yet. Attached is one more example of a 3DCoRectMesh, which essentially is a 2D surface (has however three-component vectors). -Armin [1] http://www.visitusers.org/index.php?title=Memory_access On 03/07/2015 01:24 AM, Tim Gallagher wrote:> Don't forget to reply to the list -- >> >> Without seeing errors or images of what was wrong about it, there isn't >> much we can do to help. The file I sent does work and PV reads it just >> fine. The coordinate axes in this case is Y-Z, but ultimately those are >> just names since it's 2D right? It doesn't matter if I call it X-Y, Y-Z, >> or X-Z so long as I have 2 orthogonal coordinates. >> >> The axes are specified in reverse order when you list them the way it is >> done there. So the first dataitem is always Z, the second is always Y >> and the third, if you have one, is always X. This also comes up when you >> specify the multi-dimensional data items in the attribute section >> because you have to remember it uses C memory layout (row major), which >> is different from the Fortran layout (column major). >> >> We use XDMF for massive multiblock structured simulations and we store >> our coordinates in hdf5 files in full 3D arrays (so what something like >> the meshgrid function returns in Matlab/Numpy) and I've put an example >> at the end of my email here. In this case, we have a grid which in >> Fortran would have coordinates X(I,J,K) where I = 1, 83; J = 1, 83; K = >> 1, 4. Note that the indexing is flipped when we specify it in the XDMF >> file. It is also flipped from what one would expect coming from Fortran >> when you look at the h5dump (after the XDMF example). Our strategy is to >> specify our grid points as an array of vectors and we create that array >> of vectors using the JOIN function. >> >> The XDMF documentation isn't always as helpful as I'd like sometimes. It >> took a lot of trial and error on our part to get this working (and it's >> made more complicated because we use hyperslabs a lot to only display >> portions of our data). The PV release binaries are also not helpful in >> understanding the problems sometimes -- very often, it will just >> segfault or crash with a glibc double-linked list error or something. >> Building PV yourself with debug options may help if you are really stuck. >> >> But what you seem to be trying to do is fully supported and you just >> need to keep working at it to understand why it doesn't work. And if you >> are having problems, posting images of what it looks like when you >> import the data would really help if the issue is just that it doesn't >> seem to be what you think it should be. >> >> Tim >> >> >> >> > Function="JOIN($0, $1, $2)" Dimensions="4 83 83 3"> >> > NumberType="Float" Precision="8" >> Format="HDF">&gridpath;/grid.h5:/Domain_00001/x >> > NumberType="Float" Precision="8" >> Format="HDF">&gridpath;/grid.h5:/Domain_00001/y >> > NumberType="Float" Precision="8" >> Format="HDF">&gridpath;/grid.h5:/Domain_00001/z >> >> >> >> > Name="Temperature [K]"> >> > Precision="8" >> Format="HDF">&outputpath;/RESTS/REST_00000.h5:/FlowData/temperature >> >> GROUP "/" { >> GROUP "Domain_00001" { >> DATASET "x" { >> DATATYPE H5T_IEEE_F64LE >> DATASPACE SIMPLE { ( 6, 85, 85 ) / ( 6, 85, 85 ) } >> } >> DATASET "y" { >> DATATYPE H5T_IEEE_F64LE >> DATASPACE SIMPLE { ( 6, 85, 85 ) / ( 6, 85, 85 ) } >> } >> DATASET "z" { >> DATATYPE H5T_IEEE_F64LE >> DATASPACE SIMPLE { ( 6, 85, 85 ) / ( 6, 85, 85 ) } >> } >> } >> On 03/07/2015 12:54 AM, Tim Gallagher wrote: > Hi guys, > > So the problems you're having are due to specifying inconsistent data here. You are specifying a 2DRectMesh grid but then giving it 3 vectors for the points. I don't have your HDF5 files so I made a light data XMF file that works for me on all versions going back to 3.14. I have attached it here for you to test. > > This all works fine. I've also created a 3DRectMesh. For that, you need to give it 2 points in the 3rd direction for the grid because you are specifying cell centered data. If you only give it 1 point in the 3rd direction, there is no "cell" anymore in which to specify the data. > > I'll leave adding the 3rd dimension as an exercise for you to work with. Once you figure out how it needs to work using the light data format, then switch over to using the heavy data format and get it working again. > > Hope that helps, > > Tim > > ----- Original Message ----- > From: dkxls23 at gmail.com > To: canismajorwuff at gmail.com > Cc: paraview at paraview.org > Sent: Friday, March 6, 2015 4:55:37 PM > Subject: Re: [Paraview] Import of XDMF/HDF5:Cell centered attribute of 2D Rectangular grid > > I have had similar problems with 2D structured grids and XDMF in the past. > I never got them to work in ParaView. > > I solved the problem by using 3D grids and set the first dimension (i.e. the slowest varying) one to 1, the same way as you have done it with VXVYVZ. > You just have to adjust your data arrays accordingly, i.e. dimensions 1 82 221 in your example. > > I can send you a working xdmf file when back in the office. > > I believe the computational overhead from 2D to 3D grids with effectively 2 dimensions is rather small. > > Maybe the next-generation XDMF reader in ParaView works better for 2D structued grids or somebody with the knowledge explains us how to write them correctly. :) > > -Armin > > > > On Fri Mar 6 23:17:52 2015 GMT+0200, Canis Major wrote: >> I have troubles importing xdmf output to paraview. >> >> This is an example of xdmf of 0th iteration. >> >> >> >> >> >> >> >> >> >> xdmf2d.h5:/Z >> >> >> >> xdmf2d.h5:/Y >> >> >> xdmf2d.h5:/X >> >> >> > Format="HDF"> >> xdmf2d.0.h5:/pressure >> >> >> >> >> >> >> >> >> I have an error that paraview failed to import attribute. What could >> be wrong? I have played around the parameters nothing helps. >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: circAvgFavre.xmf Type: audio/x-xmf Size: 10888 bytes Desc: not available URL: From berk.geveci at kitware.com Wed Mar 11 16:16:18 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Wed, 11 Mar 2015 16:16:18 -0400 Subject: [Paraview] Pitch for Google Summer of Code topics Message-ID: Hi folks, I wanted to make a pitch for the Google Summer of Code topics listed below. Better support for shared-memory parallelism is essential for a healthy VTK for many years to come. If you are a student, please consider writing a proposal for one of these topics. If you are a professor/mentor, please encourage strong developers in your institution to apply. Best, -berk References: http://www.vtk.org/Wiki/VTK/GSoC_2015 http://www.google-melange.com/gsoc/homepage/google/gsoc2015 *Shared Memory Parallelism in VTK* Brief explanation: Development of multi-threaded algorithms in VTK. Multiple R&D efforts are leading the creation of an infrastructure to support next generation multi-threaded parallel algorithm development in VTK. These efforts are based on modern parallel libraries such as Intel TBB and Inria KAAPI. The main goal of this project will be the development of algorithms that leverage this infrastructure. The focus will be on upgrading existing core algorithms such as iso-surfacing, clipping, cutting, warping etc. to be parallel. Ideally, this will include modernization of the old multi-threading code in the imaging pipeline. Expected results: A number of algorithms that execute in parallel using shared memory. Scalability of new algorithms will have to be measured and documented. Development of regression tests and examples will be also expected. Prerequisites: Experience in C++ and multi-threaded code development. Understanding of core visualization algorithms and data structures. Some experience in VTK ideally but not necessary. Mentor: Berk Geveci (berk dot geveci at kitware dot com) and David Gobbi (david dot gobbi at gmail dot com) *Fine-Grained Parallelism in VTK-m* Brief explanation: VTK-m is a toolkit of scientific visualization algorithms for emerging processor architectures ( GPU's and Coprocessors's ). VTK-m is designed for fine-grained concurrency and provides abstract data and execution models that can be applied to a variety of algorithms. The goal of the project will be on developing algorithms such as Slice by implicit surface, Gradient, Streamlines, External Faces, Resample, etc. using VTKM-m data and execution model. Expected results: A collection of algorithms that are processor architecture agnostic and execute on GPU's and Coprocessor's using VTK-m's data and execution model. Performance of new algorithms will have to be measured and documented. Development of regression tests and examples will be also expected. Prerequisites: Experience in templated C++ development, visualization algorithms, data structures and highly parallel architectures such as GPU's. Some experience in VTK or CUDA or OpenCL would be ideal but not necessary. Mentor: Robert Maynard (robert dot maynard at kitware dot com) and Kenneth Moreland (kmorel at sandia dot gov) -------------- next part -------------- An HTML attachment was scrubbed... URL: From i.krukow at tu-braunschweig.de Wed Mar 11 17:03:32 2015 From: i.krukow at tu-braunschweig.de (Ian Krukow) Date: Wed, 11 Mar 2015 22:03:32 +0100 Subject: [Paraview] Build error on Windows Message-ID: <5500ADA4.102@tu-braunschweig.de> Hi all, I am trying to build ParaView on Windows, but I get the following error, and I have no idea what it means or how to fix it: 4>C:\ParaView\ParaView-v4.3.1-source\VTK\Wrapping\Tools\vtkWrapPythonInit.c : fatal error C1041: cannot open program database 'c:\paraview\pv\vtk\wrapping\tools\x64\debug\vc120.pdb'; if multiple CL.EXE write to the same .PDB file, please use /FS I use ParaView 4.3.1 source code and Visual Studio 2013. Can anyone help me? Kind regards Ian From leonardopessanha74 at gmail.com Wed Mar 11 18:20:34 2015 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Wed, 11 Mar 2015 19:20:34 -0300 Subject: [Paraview] Paraview 4.3.1 - Glyph Filter - Mask Points and Random Mode Option Message-ID: Hi, I recently updated my Paraview version, and now i am using the 4.3.1 downloaded from the kitware site In the 4.1 version, the glyph filter had two options, to mask the glyphed points and to do it randomly They are important to me and i can't find this options in the new version, not even toggling the advanced properties There's another way to do that? Att, Leonardo Pessanha GRVa-LAMCE-COPPE-UFRJ -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Mar 11 18:43:42 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 11 Mar 2015 18:43:42 -0400 Subject: [Paraview] Paraview 4.3.1 - Glyph Filter - Mask Points and Random Mode Option In-Reply-To: References: Message-ID: Leo, Checkout Section 5.7.8 from the ParaView Guide. It covers the new parameters on the Glyph filter. The free version of the guide can be downloaded form http://www.paraview.org/documentation/ Utkarsh On Wed, Mar 11, 2015 at 6:20 PM, L?o Pessanha wrote: > Hi, > > I recently updated my Paraview version, and now i am using the 4.3.1 > downloaded from the kitware site > > In the 4.1 version, the glyph filter had two options, to mask the glyphed > points and to do it randomly > > They are important to me and i can't find this options in the new version, > not even toggling the advanced properties > > There's another way to do that? > > Att, > Leonardo Pessanha > GRVa-LAMCE-COPPE-UFRJ > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 lyon at fnal.gov Thu Mar 12 02:55:24 2015 From: lyon at fnal.gov (Adam Lyon) Date: Thu, 12 Mar 2015 01:55:24 -0500 Subject: [Paraview] Trying example in Paraview manual section 13.2.2 - can't get it to work Message-ID: Hi, I'm trying to write a Python Programmable Source that can read files based on a time stamp (e.g. pick the file using the "VCR" buttons in Paraview). I see a nice example in the new Paraview manual (PDF) in section 13.2.2 - CSV file series, but I can't get that example to work. The UPDATE_TIME_STEP is always a value like 0.11111, 0.22222, 0.33333, up to 1. It's never from the set of times specified by the RequestInformation script. I'm using Paraview v4.3.1 64-bit Mac Yosemite. Here's what I did... I have a Programmable Source as the only item in my pipeline. The output dataset type is vtkTable. The "Script" is, # -- Script -- import numpy as np def GetUpdateTimestep(algorithm): executive = algorithm.GetExecutive() outInfo = executive.GetOutputInformation(0) print outInfo.Get(executive.TIME_STEPS()) return outInfo.Get(executive.UPDATE_TIME_STEP()) if outInfo.Has(executive.UPDATE_TIME_STEP()) else None req_time = GetUpdateTimestep(self) a = np.array([req_time] ) output.RowData.append(a, "Adam") #--------------- And the "RequestInformation" script is (taken verbatim from the example in the manual)... # -- RequestInformation -- def setOutputTimesteps(algorithm , timesteps): "helper routine to set timestep information" executive = algorithm.GetExecutive() outInfo = executive.GetOutputInformation(0) outInfo.Remove(executive.TIME_STEPS()) for timestep in timesteps: outInfo.Append(executive.TIME_STEPS(), timestep) outInfo.Remove(executive.TIME_RANGE()) outInfo.Append(executive.TIME_RANGE(), timesteps[0]) outInfo.Append(executive.TIME_RANGE(), timesteps[-1]) setOutputTimesteps(self, (1.0, 2.0, 20.0, 30.0)) ---- So as you can see, I'm just copying the value of UPDATE_TIME_STEP into the output table, which I can look at in the spreadsheet view. When I hit the "VCR buttons", the values I get are 0.111111, 0.222222, ... -- not the values that I had set in TIME_STEPS. Note that in the top script I have a line, print outInfo.Get(executive.TIME_STEPS()) which prints out the right thing ... (1.0, 2.0, 20.0, 30.0) I can print out TIME_RANGE and that's correct too (1.0, 30.0) So I think everything is set correctly, but for some reason Paraview is ignoring the settings. Do I need to call something to tell Paraview to notice my changing of TIME_STEPS/TIME_RANGE? Thanks in advance for any help! -- Adam -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephen.wornom at inria.fr Thu Mar 12 04:49:59 2015 From: stephen.wornom at inria.fr (Stephen Wornom) Date: Thu, 12 Mar 2015 09:49:59 +0100 (CET) Subject: [Paraview] PV 4.1.0: save the data saves only 1/2 of a circle PROBLEM SOLVED - SAVE the csv file using the SCIENTIFIC NOTATION In-Reply-To: <222342041.5736223.1426090612462.JavaMail.zimbra@inria.fr> References: <222342041.5736223.1426090612462.JavaMail.zimbra@inria.fr> Message-ID: <1857850757.5899167.1426150199506.JavaMail.zimbra@inria.fr> Recall that I have two cylinders. 1- extract a surface 2- connectivity 3- threshold 4 slice in the z-coordinate This produces two circles in the x-y plane. 5- I save the data in a csv file using the default format. 6- To read the cvs file in fortran, I replace the commas by a blank. 7- I read the csv file in a fortran program and plot the values for y> 0 (upper circle) and y<0 (lower circle) 8 Result is upper circle points ar missing. Cause is csv file was written with the default notation which has reals and integers which I then read as reals in the fortran code. Stephen From anton.piccardo-selg at stfc.ac.uk Thu Mar 12 12:10:12 2015 From: anton.piccardo-selg at stfc.ac.uk (anton.piccardo-selg at stfc.ac.uk) Date: Thu, 12 Mar 2015 16:10:12 +0000 Subject: [Paraview] Setting glyph color to be independent of color scale and color map Message-ID: <593AFCE559F11049B8F268BE84170A0DC2481B@EXCHMBX03.fed.cclrc.ac.uk> Hi, We are building a customization of ParaView 3.98.1. Data sets are loaded with a signal range which is then used to set the scalar range for the color scale. Besides the data we plot some simple glyphs to indicate special points in our rendered data set. Currently they are all rendered white, as the glyphs don't have a scalar value attached to them ( I guess it is the NAN color). I was wondering if there is a way to set the color of these glyphs to a fixed value, independent of the color scale or the selected color map. In our case we would always want to render an ellipsoidal glyph with a yellow color. Is this possible? Many thanks and best regards, Anton From kmorel at sandia.gov Thu Mar 12 12:32:37 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 12 Mar 2015 16:32:37 +0000 Subject: [Paraview] Setting glyph color to be independent of color scale and color map Message-ID: The coloring of an object (in this case, the result of the glyph filter) is controlled by the representation object. The representation object can be set to be either a solid color or mapping a variable. It sounds like your glyph representation is already set to a solid color since the default solid color is white. There are several parameters on the representation object that control the solid color. The most relevant is the DiffuseColor parameter. Change that to be yellow (i.e. [1,1,0]) and that should do what you want. -Ken On 3/12/15, 10:10 AM, "anton.piccardo-selg at stfc.ac.uk" wrote: >Hi, > >We are building a customization of ParaView 3.98.1. Data sets are loaded >with a signal range which is then used to set the scalar range for the >color scale. Besides the data we plot some simple glyphs to indicate >special points in our rendered data set. > >Currently they are all rendered white, as the glyphs don't have a scalar >value attached to them ( I guess it is the NAN color). I was wondering >if there is a way to set the color of these glyphs to a fixed value, >independent of the color scale or the selected color map. In our case we >would always want to render an ellipsoidal glyph with a yellow color. Is >this possible? > >Many thanks and best regards, > >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 dan.lipsa at kitware.com Thu Mar 12 12:50:00 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Thu, 12 Mar 2015 12:50:00 -0400 Subject: [Paraview] vtkBlockColors legend should show correct sideset IDs In-Reply-To: References: Message-ID: Hi Ond?ej, On Tue, Mar 10, 2015 at 4:59 PM, Ond?ej ?ert?k wrote: > Hi, > > I am testing the new vtkBlockColors feature in the latest Paraview (I > am using 0a4ad038370beb6d30f51f43e32555b3adcea123), as introduced in > the blog post: http://www.kitware.com/blog/home/post/859 > > Currently the legend shows colors with numbers 0-6. However, many > times the sidesets in an ExodusII file are not labeled like that. I am > attaching a screenshot with an example. As you can see, both the > Properties as well as Multi-block Inspector shows the correct side set > ID numbers (1, 5, 10, 15), but the vtkBlockColors legend shows numbers > 0-6. > > Note that if I color by vtkCompositeIndex, the legend shows the > correct side set ID, but the problem is that it's a continuous legend, > and the colors are close to each other, so it's hard (essentially > impossible) to tell what the ID is from the color. > Could you set 'Interpret Values as Categories' in the Color Map Editor? Than, in the Annotations panel press 'Add active values from Selected Source' and then 'Choose preset' to to desired color palette. > > I understand the user case when there is thousands of blocks. But I > think there is also a use case when there is relatively few (~10) > boundary conditions, and you just want to see them all at once using a > legend, so that you can take a screenshot and send it to somebody. > Maybe there can be some check-box that would switch the two modes of > the legend. See the previous suggestion. I think that will give you the desired result. > > Currently the best way seems to be to use vtkBlockColors, and then > send a screenshot that includes the Multi-block Inspector window, > which also shows the colors and proper IDs. > > There is also the issue of Block ID versus Side Set ID (as a side set > can have the same id as a block set), I usually turn one or the other > off in Multi-block Inspector, then they are not mixed. > Indeed, the ID we use is the index resulted from traversing the block tree. Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Mar 12 22:55:09 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 13 Mar 2015 02:55:09 +0000 Subject: [Paraview] Superbuild and code changes Message-ID: <1eea1343efff41a9beeca45a6195335f@ES05AMSNLNT.srn.sandia.gov> Is it possible to build ParaView with the superbuild, but change a few lines of code? I want to comment out a few warnings. These lines of source code keep getting written over. Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Thu Mar 12 23:18:54 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Thu, 12 Mar 2015 23:18:54 -0400 Subject: [Paraview] Superbuild and code changes In-Reply-To: <1eea1343efff41a9beeca45a6195335f@ES05AMSNLNT.srn.sandia.gov> References: <1eea1343efff41a9beeca45a6195335f@ES05AMSNLNT.srn.sandia.gov> Message-ID: <20150313031854.GE15361@bronto-burt.dev.benboeckel.net> On Fri, Mar 13, 2015 at 02:55:09 +0000, Scott, W Alan wrote: > Is it possible to build ParaView with the superbuild, but change a few > lines of code? I want to comment out a few warnings. These lines of > source code keep getting written over. You could apply a "patch"[1] (using an ExternalData step of which at least Projects/apple/qt.cmake should have an example or two) or point the superbuild to a different git repo with the patches applied. Without looking, I can't remember the exact names of the cache variables, but they're something like "paraview_GIT_URL" and "paraview_GIT_HASH". Both should be advanced variables on the master branch. --Ben [1]Due to the lack of a patch command on Windows, "patch" in superbuilds usually means "copy a file wholesale as a replacement". From Gottfried.Necker at partner.kit.edu Fri Mar 13 07:34:40 2015 From: Gottfried.Necker at partner.kit.edu (Gottfried Necker) Date: Fri, 13 Mar 2015 12:34:40 +0100 Subject: [Paraview] Temporal collection problem Message-ID: <1933136.oAl0JOl9zD@iket-pslinux01> Hello, I'm pretty new to ParaView. I'm trying to visualize a short sequence (2 time steps) using a Xdmf file with a temporal collection. When I open the file in ParaView 4.3.1 (binary for Linux x64 from paraview.org) I can see the first time step and display a variable using the threshold filter. Using the "Current Time Controls" I can go to the second time step, but the display does not change. On the information tab I can see that ParaView recognizes the 2 time steps, but when I change the time using the controls the "Current data time" stays at the first time step. When I open the same file in ParaView 4.2.0 I can switch between the two time steps as expected and everything seems to work fine for this simple case. And of course the displayed image looks as expected. I've attached the XML file to this mail. If anybody is interested to try this, I can provide the HDF5 files too. Is there something wrong with the file(s)? Thanks Gottfried -------------- next part -------------- A non-text attachment was scrubbed... Name: only-mesh.xmf Type: audio/x-xmf Size: 3621 bytes Desc: not available URL: From ben.boeckel at kitware.com Fri Mar 13 08:58:55 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Fri, 13 Mar 2015 08:58:55 -0400 Subject: [Paraview] Superbuild and code changes In-Reply-To: <20150313031854.GE15361@bronto-burt.dev.benboeckel.net> References: <1eea1343efff41a9beeca45a6195335f@ES05AMSNLNT.srn.sandia.gov> <20150313031854.GE15361@bronto-burt.dev.benboeckel.net> Message-ID: <20150313125855.GA26263@megas.kitwarein.com> On Thu, Mar 12, 2015 at 23:18:54 -0400, Ben Boeckel wrote: > Without looking, I can't remember the exact names of the cache > variables, but they're something like "paraview_GIT_URL" and > "paraview_GIT_HASH". They are PARAVIEW_GIT_REPOSITORY and PARAVIEW_GIT_TAG (which is any git refname, not just a tag). --Ben From dkxls23 at gmail.com Fri Mar 13 09:13:36 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Fri, 13 Mar 2015 15:13:36 +0200 Subject: [Paraview] Temporal collection problem In-Reply-To: <1933136.oAl0JOl9zD@iket-pslinux01> References: <1933136.oAl0JOl9zD@iket-pslinux01> Message-ID: <5502E280.5010803@gmail.com> At a first glance I don't see anything wrong with the XDMF file, but if you could upload the HDF5 file somewhere and post the link, it would be easier to figure out whats going wrong. It would already help to see the structure of the HDF5 file, essentially the output of this: > h5dump -H filename.h5 > filename.h5dump -Armin On 03/13/2015 01:34 PM, Gottfried Necker wrote: > Hello, > > I'm pretty new to ParaView. I'm trying to visualize a short sequence (2 time > steps) using a Xdmf file with a temporal collection. When I open the file in > ParaView 4.3.1 (binary for Linux x64 from paraview.org) I can see the first > time step and display a variable using the threshold filter. Using the > "Current Time Controls" I can go to the second time step, but the display does > not change. On the information tab I can see that ParaView recognizes the 2 > time steps, but when I change the time using the controls the "Current data > time" stays at the first time step. > > When I open the same file in ParaView 4.2.0 I can switch between the two time > steps as expected and everything seems to work fine for this simple case. And > of course the displayed image looks as expected. > > I've attached the XML file to this mail. If anybody is interested to try this, > I can provide the HDF5 files too. > > Is there something wrong with the file(s)? > > Thanks > > Gottfried > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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 Gottfried.Necker at partner.kit.edu Fri Mar 13 10:37:48 2015 From: Gottfried.Necker at partner.kit.edu (Gottfried Necker) Date: Fri, 13 Mar 2015 15:37:48 +0100 Subject: [Paraview] Temporal collection problem In-Reply-To: <5502E280.5010803@gmail.com> References: <1933136.oAl0JOl9zD@iket-pslinux01> <5502E280.5010803@gmail.com> Message-ID: <15855682.Wo0WhRR7or@iket-pslinux01> Am Freitag, 13. M?rz 2015, 14:13:36 schrieb Armin Wehrfritz: > At a first glance I don't see anything wrong with the XDMF file, but if > you could upload the HDF5 file somewhere and post the link, it would be > easier to figure out whats going wrong. > > It would already help to see the structure of the HDF5 file, essentially > > the output of this: > > h5dump -H filename.h5 > filename.h5dump > > -Armin > I don't have any space where I can upload something. I've attached the h5dump of the first netCDF4/HDF5 file. The structure of the second file is exactly identical and so is the h5dump. These files contain more data than referenced in the XML file, but this should not hurt. I didn't mention: I can read this file in VisIt and everything works as expected. Thanks, Gottfried -------------- next part -------------- HDF5 "vis1.nc" { GROUP "/" { ATTRIBUTE "_nc3_strict" { DATATYPE H5T_STD_I32LE DATASPACE SCALAR } DATASET "Dim0000003" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 3 ) / ( 3 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 6 ) / ( 6 ) } } } DATASET "Dim0000004" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 4 ) / ( 4 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 6 ) / ( 6 ) } } } DATASET "Dim0000008" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 8 ) / ( 8 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 1 ) / ( 1 ) } } } DATASET "Dim0000010" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 10 ) / ( 10 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 7 ) / ( 7 ) } } } DATASET "Dim0000011" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 11 ) / ( 11 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 1 ) / ( 1 ) } } } DATASET "Dim0000013" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 13 ) / ( 13 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 4 ) / ( 4 ) } } } DATASET "Dim0000023" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 23 ) / ( 23 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 7 ) / ( 7 ) } } } DATASET "Dim0000024" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 24 ) / ( 24 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 1 ) / ( 1 ) } } } DATASET "Dim0000026" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 26 ) / ( 26 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 4 ) / ( 4 ) } } } DATASET "Dim0000039" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 39 ) / ( 39 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 7 ) / ( 7 ) } } } DATASET "Dim0000040" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 40 ) / ( 40 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 1 ) / ( 1 ) } } } DATASET "Dim0000042" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 42 ) / ( 42 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 4 ) / ( 4 ) } } } DATASET "Dim0000243" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 243 ) / ( 243 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 3 ) / ( 3 ) } } } DATASET "Dim0000260" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 260 ) / ( 260 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 3 ) / ( 3 ) } } } DATASET "Dim0000556" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 556 ) / ( 556 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 3 ) / ( 3 ) } } } DATASET "Dim0001036" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 1036 ) / ( 1036 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 3 ) / ( 3 ) } } } DATASET "Dim0001527" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 1527 ) / ( 1527 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 1 ) / ( 1 ) } } } DATASET "Dim0002495" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 2495 ) / ( 2495 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 2 ) / ( 2 ) } } } DATASET "Dim0004541" { DATATYPE H5T_IEEE_F32BE DATASPACE SIMPLE { ( 4541 ) / ( 4541 ) } ATTRIBUTE "CLASS" { DATATYPE H5T_STRING { STRSIZE 16; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "NAME" { DATATYPE H5T_STRING { STRSIZE 64; STRPAD H5T_STR_NULLTERM; CSET H5T_CSET_ASCII; CTYPE H5T_C_S1; } DATASPACE SCALAR } ATTRIBUTE "REFERENCE_LIST" { DATATYPE H5T_COMPOUND { H5T_REFERENCE { H5T_STD_REF_OBJECT } "dataset"; H5T_STD_I32LE "dimension"; } DATASPACE SIMPLE { ( 3 ) / ( 3 ) } } } DATASET "full_mesh" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 13, 26, 42, 3 ) / ( 13, 26, 42, 3 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 4 ) / ( 4 ) } } } DATASET "full_meship" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 13, 26, 42, 3 ) / ( 13, 26, 42, 3 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 4 ) / ( 4 ) } } } DATASET "full_meshjp" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 13, 26, 42, 3 ) / ( 13, 26, 42, 3 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 4 ) / ( 4 ) } } } DATASET "full_meshkp" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 13, 26, 42, 3 ) / ( 13, 26, 42, 3 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 4 ) / ( 4 ) } } } DATASET "ht_slabs" { DATATYPE H5T_STD_I32LE DATASPACE SIMPLE { ( 4541, 4 ) / ( 4541, 4 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 2 ) / ( 2 ) } } } DATASET "ht_wall_0" { DATATYPE H5T_STD_I32LE DATASPACE SIMPLE { ( 1036, 4 ) / ( 1036, 4 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 2 ) / ( 2 ) } } } DATASET "ht_wall_1" { DATATYPE H5T_STD_I32LE DATASPACE SIMPLE { ( 556, 4 ) / ( 556, 4 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 2 ) / ( 2 ) } } } DATASET "ht_wall_2" { DATATYPE H5T_STD_I32LE DATASPACE SIMPLE { ( 260, 4 ) / ( 260, 4 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 2 ) / ( 2 ) } } } DATASET "ht_wall_3" { DATATYPE H5T_STD_I32LE DATASPACE SIMPLE { ( 243, 4 ) / ( 243, 4 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 2 ) / ( 2 ) } } } DATASET "mat_mobs" { DATATYPE H5T_STD_I32LE DATASPACE SIMPLE { ( 2495 ) / ( 2495 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 1 ) / ( 1 ) } } } DATASET "mat_slabs" { DATATYPE H5T_STD_I32LE DATASPACE SIMPLE { ( 4541 ) / ( 4541 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 1 ) / ( 1 ) } } } DATASET "mat_wall_0" { DATATYPE H5T_STD_I32LE DATASPACE SIMPLE { ( 1036 ) / ( 1036 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 1 ) / ( 1 ) } } } DATASET "mat_wall_1" { DATATYPE H5T_STD_I32LE DATASPACE SIMPLE { ( 556 ) / ( 556 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 1 ) / ( 1 ) } } } DATASET "mat_wall_2" { DATATYPE H5T_STD_I32LE DATASPACE SIMPLE { ( 260 ) / ( 260 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 1 ) / ( 1 ) } } } DATASET "mat_wall_3" { DATATYPE H5T_STD_I32LE DATASPACE SIMPLE { ( 243 ) / ( 243 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 1 ) / ( 1 ) } } } DATASET "mesh" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 11, 24, 40, 3 ) / ( 11, 24, 40, 3 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 4 ) / ( 4 ) } } } DATASET "mobs" { DATATYPE H5T_STD_I32LE DATASPACE SIMPLE { ( 2495, 8 ) / ( 2495, 8 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 2 ) / ( 2 ) } } } DATASET "pressure" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 10, 23, 39 ) / ( 10, 23, 39 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 3 ) / ( 3 ) } } } DATASET "slab_temp" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 4541 ) / ( 4541 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 1 ) / ( 1 ) } } } DATASET "temperature" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 10, 23, 39 ) / ( 10, 23, 39 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 3 ) / ( 3 ) } } } DATASET "total_density" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 10, 23, 39 ) / ( 10, 23, 39 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 3 ) / ( 3 ) } } } DATASET "velocity" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 10, 23, 39, 3 ) / ( 10, 23, 39, 3 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 4 ) / ( 4 ) } } } DATASET "vf_air" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 10, 23, 39 ) / ( 10, 23, 39 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 3 ) / ( 3 ) } } } DATASET "vf_h2o" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 10, 23, 39 ) / ( 10, 23, 39 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 3 ) / ( 3 ) } } } DATASET "vf_lg" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 10, 23, 39 ) / ( 10, 23, 39 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 3 ) / ( 3 ) } } } DATASET "wall_temp_0" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 1036 ) / ( 1036 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 1 ) / ( 1 ) } } } DATASET "wall_temp_1" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 556 ) / ( 556 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 1 ) / ( 1 ) } } } DATASET "wall_temp_2" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 260 ) / ( 260 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 1 ) / ( 1 ) } } } DATASET "wall_temp_3" { DATATYPE H5T_IEEE_F64LE DATASPACE SIMPLE { ( 243 ) / ( 243 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 1 ) / ( 1 ) } } } DATASET "walls" { DATATYPE H5T_STD_I32LE DATASPACE SIMPLE { ( 1527, 4 ) / ( 1527, 4 ) } ATTRIBUTE "DIMENSION_LIST" { DATATYPE H5T_VLEN { H5T_REFERENCE { H5T_STD_REF_OBJECT }} DATASPACE SIMPLE { ( 2 ) / ( 2 ) } } } } } From gonzalo.feijoo at siemens.com Fri Mar 13 11:29:42 2015 From: gonzalo.feijoo at siemens.com (Feijoo, Gonzalo) Date: Fri, 13 Mar 2015 15:29:42 +0000 Subject: [Paraview] Gauraud shading when reading from HDF5 file. Message-ID: <055B9084EECF0244A45C95019FFA1D037CEEB90D@USSLMMBX003.net.plm.eds.com> Hello, Everyone, How can I use normals defined at each node to visualize a triangulation using Gouraud shading? If I write my data in the .vtk format, then this is automatically done by Paraview by saving the normals in the NORMALS field within the POINT_DATA field. But how can I do this from data saved in an XDMF/HDF5 file? I mean, how would I need to specify the normals in the XDMF file for the shader to use these vectors? Thank you in advance for any help. Best regards, Gonzalo R. Feij?o Advanced projects and architecture Specialized Engineering Siemens Industry Sector Siemens Product Lifecycle Management Software Inc. 200 Fifth Avenue Waltham, MA 02451 United States Tel. :+1 (781) 907-9751 Fax :+1 (781) 907-9880 gonzalo.feijoo at siemens.com www.siemens.com/plm -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Fri Mar 13 15:34:14 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 13 Mar 2015 19:34:14 +0000 Subject: [Paraview] [EXTERNAL] PROBLEM IMPORTING ENSIGHT SOS FILE In-Reply-To: References: Message-ID: <5a805951bc3a40a780d8638552585a81@ES05AMSNLNT.srn.sandia.gov> Gaspare, I tried opening your .case files with ParaView and EnSight, and they seem OK. I then tried opening the .sos file, and had issues - even after removing the site specific information. I had issues with ParaView, and it crashed EnSight. Thus, I believe the issue is with the .sos file. I am not an expert on .sos files at all - so let me aim you at the online documentation. By doing a google search, I found the following: http://www3.ensight.com/EnSight10_Docs/UserManual.pdf. Look in chapter 9.8, SOS file formats. That's about all I know... Alan -----Original Message----- From: Gaspare Argento [mailto:gaspare.argento at gmail.com] Sent: Tuesday, March 10, 2015 5:04 AM To: Scott, W Alan Cc: paraview at paraview.org Subject: Re: [EXTERNAL] [Paraview] PROBLEM IMPORTING ENSIGHT SOS FILE Hi Scott, please find attached a case test that was launched on two cores. In the first folder you can find the *.sos file, manually edited with the correct machine name and the absolute path to the Ensight server (I'm not sure it is the correct file to use); in the folders DOM_0 and DOM_1 you can find the *.case files (I can load them one by one correctly). These files are written by AVL Fire. Because Paraview doesn't support the native format of FIRE for 3D Results, I ask to the software to write them also in the Ensight format. Thanks for your support, Gaspare 2015-03-09 22:27 GMT+01:00 Scott, W Alan : > I believe my thoughts below were wrong. Ignore them. > > Could you give us a trivial dataset that shows this issue? > > Thanks, > > Alan > > -----Original Message----- > From: Gaspare Argento [mailto:gaspare.argento at gmail.com] > Sent: Friday, March 06, 2015 12:47 AM > To: Scott, W Alan > Cc: paraview at paraview.org > Subject: Re: [EXTERNAL] [Paraview] PROBLEM IMPORTING ENSIGHT SOS FILE > > Hi Scott, > > thanks for answering. > > I'm sorry but I didn't understand exactly what do you mean: could you please explain it better? Did you ask me to attach the .sos file? > > Thanks, > > Gaspare > > 2015-03-05 18:39 GMT+01:00 Scott, W Alan : >> I just opened an .sos file, with a 16 file dataset, with ParaView 4.3.1. Worked fine. Linux, local server. >> >> * I wonder if you have a problem with your SOS file. >> * Mind posting a/the dataset? >> >> Alan >> >> -----Original Message----- >> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of >> Gaspare Argento >> Sent: Thursday, March 05, 2015 2:20 AM >> To: paraview at paraview.org >> Subject: [EXTERNAL] [Paraview] PROBLEM IMPORTING ENSIGHT SOS FILE >> >> Hi everybody, >> >> I have a problem when importing an Ensight .sos file in Paraview. >> >> Loading the .sos file I get the following message (I attach only the lines about the first *.case file, because these are repeated for all *case files listed in the .sos): >> ===================================================================== >> = ==================================================== >> >> ERROR: In >> C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSight >> R >> eader.cxx, >> line 340 >> >> vtkPGenericEnSightReader (000000000DC5E6E0): Unable to open file: >> J:\SERVER\CALC\VOF_TEST\Calculation\VOF_TEST\3D_EnSight\/VOF_TEST_DOM >> _ >> 0.case >> >> >> >> >> >> ERROR: In >> C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSight >> R >> eader.cxx, >> line 340 >> >> vtkPGenericEnSightReader (000000000DC5E6E0): Unable to open file: >> J:\SERVER\CALC\VOF_TEST\Calculation\VOF_TEST\3D_EnSight\/VOF_TEST_DOM >> _ >> 0.case >> >> >> >> >> >> ERROR: In >> C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSight >> R >> eader.cxx, >> line 811 >> >> vtkPGenericEnSightReader (000000000DC5E6E0): Error determining >> EnSightVersion >> >> >> >> >> >> ERROR: In >> C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExe >> c >> utive.cxx, >> line 784 >> >> vtkCompositeDataPipeline (000000000DBF33A0): Algorithm >> vtkPGenericEnSightReader(000000000DC5E6E0) returned failure for >> request: vtkInformation (000000000DEC2F60) >> >> Debug: Off >> >> Modified Time: 160501 >> >> Reference Count: 1 >> >> Registered Events: (none) >> >> Request: REQUEST_INFORMATION >> >> ALGORITHM_AFTER_FORWARD: 1 >> >> FORWARD_DIRECTION: 0 >> >> >> >> >> >> ERROR: In >> C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\VTKExtensions\Defau >> l t\vtkPVEnSightMasterServerReader2.cxx, >> line 255 >> >> vtkPVEnSightMasterServerReader2 (0000000018693C90): Error reading case file on at least one node. >> >> >> >> >> >> ERROR: In >> C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExe >> c >> utive.cxx, >> line 784 >> >> vtkPVCompositeDataPipeline (0000000017BEA7E0): Algorithm >> vtkPVEnSightMasterServerReader2(0000000018693C90) returned failure >> for >> request: vtkInformation (0000000016F654A0) >> >> Debug: Off >> >> Modified Time: 6920520 >> >> Reference Count: 1 >> >> Registered Events: (none) >> >> Request: REQUEST_INFORMATION >> >> ALGORITHM_AFTER_FORWARD: 1 >> >> FORWARD_DIRECTION: 0 >> >> ===================================================================== >> = ==================================================== >> >> >> >> Below you can find an extract of the loaded .sos file (only the lines relative to the first server): >> ===================================================================== >> = ==================================================== >> >> # >> >> # Example Server-of-server case file >> >> # parts in <> have to be filled in by the user >> >> # >> >> FORMAT >> >> type: master_server gold >> >> SERVERS >> >> number of servers: 64 >> >> #Server 1 >> >> machine id: MACHINE_NAME >> >> executable: >> >> casefile: >> J:/SERVER/CALC/VOF_TEST/Calculation/VOF_TEST/3D_EnSight/DOM_0/VOF_TES >> T >> _DOM_0.case >> >> ===================================================================== >> = ==================================================== >> >> >> >> If I load the *.case files one by one I have no problem. >> >> >> >> Thanks for your support >> >> Gaspare >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 yingz at ufl.edu Fri Mar 13 17:21:48 2015 From: yingz at ufl.edu (Zhang,Ying) Date: Fri, 13 Mar 2015 21:21:48 +0000 Subject: [Paraview] Algorithm to find grain neighbors Message-ID: <34F51C09-ADD2-4645-AE79-6C576455B158@ufl.edu> Dear Paraview developers, I sent a question a while ago and probably didn?t get to the list. But here is my question again: I have a grain image in vti format and use Paraview to visualize the grains. In Paraview I use Representation/Surface along with xml template for coloring to display the grain image based on the vti file. I would like to know if there is a way to find out the number of neighbors each grain has. I wonder if paraview has a such tool to give this information. Thank you! Ying Zhang From wascott at sandia.gov Fri Mar 13 20:19:41 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Sat, 14 Mar 2015 00:19:41 +0000 Subject: [Paraview] Superbuild, CGNS and debug Message-ID: I am trying to get a debugger into a CGNS build of ParaView. CGNS builds seems to be dying trying to link to HDF5. Has anyone else seen this? Any ideas how to compile debug with CGNS and the Superbuild? Here is some of the errors that I am seeing: checking whether build environment is sane... ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_INT32_g' ../libcgns.so.3.1: undefined reference to `H5P_CLS_FILE_CREATE_g' ../libcgns.so.3.1: undefined reference to `H5Pcreate' ../libcgns.so.3.1: undefined reference to `H5Tcopy' ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_UINT32_g' ../libcgns.so.3.1: undefined reference to `H5Sget_simple_extent_dims' ../libcgns.so.3.1: undefined reference to `H5Eset_auto2' ../libcgns.so.3.1: undefined reference to `H5Sget_simple_extent_ndims' ../libcgns.so.3.1: undefined reference to `H5Aget_type' ../libcgns.so.3.1: undefined reference to `H5Fcreate' ../libcgns.so.3.1: undefined reference to `H5Sset_extent_simple' ../libcgns.so.3.1: undefined reference to `H5Sclose' ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_SCHAR_g' ../libcgns.so.3.1: undefined reference to `H5Aopen_name' ../libcgns.so.3.1: undefined reference to `H5Gunlink' ../libcgns.so.3.1: undefined reference to `H5Lget_val' ../libcgns.so.3.1: undefined reference to `H5Tget_native_type' ../libcgns.so.3.1: undefined reference to `H5Acreate2' ../libcgns.so.3.1: undefined reference to `H5Aclose' ../libcgns.so.3.1: undefined reference to `H5Pset_deflate' ../libcgns.so.3.1: undefined reference to `H5T_C_S1_g' ../libcgns.so.3.1: undefined reference to `H5Tset_precision' ../libcgns.so.3.1: undefined reference to `H5Dopen2' ../libcgns.so.3.1: undefined reference to `H5Dget_type' ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_FLOAT_g' ../libcgns.so.3.1: undefined reference to `H5Lunpack_elink_val' ../libcgns.so.3.1: undefined reference to `H5Dwrite' ../libcgns.so.3.1: undefined reference to `H5Lcreate_external' ../libcgns.so.3.1: undefined reference to `H5Dget_storage_size' ../libcgns.so.3.1: undefined reference to `H5Screate_simple' ../libcgns.so.3.1: undefined reference to `H5Aread' ../libcgns.so.3.1: undefined reference to `H5check_version' ../libcgns.so.3.1: undefined reference to `H5Iget_name' ../libcgns.so.3.1: undefined reference to `H5Lis_registered' ../libcgns.so.3.1: undefined reference to `H5Fget_obj_ids' ../libcgns.so.3.1: undefined reference to `H5P_CLS_GROUP_CREATE_g' ../libcgns.so.3.1: undefined reference to `H5Gcreate2' ../libcgns.so.3.1: undefined reference to `H5Giterate' ../libcgns.so.3.1: undefined reference to `H5Tget_size' ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_UCHAR_g' ../libcgns.so.3.1: undefined reference to `H5Screate' ../libcgns.so.3.1: undefined reference to `H5T_IEEE_F32BE_g' ../libcgns.so.3.1: undefined reference to `H5Literate' ../libcgns.so.3.1: undefined reference to `H5Gopen2' ../libcgns.so.3.1: undefined reference to `H5Dset_extent' ../libcgns.so.3.1: undefined reference to `H5T_IEEE_F64BE_g' ../libcgns.so.3.1: undefined reference to `H5Dget_space' ../libcgns.so.3.1: undefined reference to `H5Dclose' ../libcgns.so.3.1: undefined reference to `H5P_CLS_FILE_ACCESS_g' ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_UINT64_g' Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Mar 13 20:51:04 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 13 Mar 2015 20:51:04 -0400 Subject: [Paraview] Superbuild, CGNS and debug In-Reply-To: References: Message-ID: I don't follow...what do you mean by "get a debugger into a CGNS build of ParaView"? You are getting these errors when building ParaView or running in in a debugger? On Fri, Mar 13, 2015 at 8:19 PM, Scott, W Alan wrote: > I am trying to get a debugger into a CGNS build of ParaView. CGNS builds > seems to be dying trying to link to HDF5. Has anyone else seen this? Any > ideas how to compile debug with CGNS and the Superbuild? > > Here is some of the errors that I am seeing: > > checking whether build environment is sane... ../libcgns.so.3.1: undefined > reference to `H5T_NATIVE_INT32_g' > ../libcgns.so.3.1: undefined reference to `H5P_CLS_FILE_CREATE_g' > ../libcgns.so.3.1: undefined reference to `H5Pcreate' > ../libcgns.so.3.1: undefined reference to `H5Tcopy' > ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_UINT32_g' > ../libcgns.so.3.1: undefined reference to `H5Sget_simple_extent_dims' > ../libcgns.so.3.1: undefined reference to `H5Eset_auto2' > ../libcgns.so.3.1: undefined reference to `H5Sget_simple_extent_ndims' > ../libcgns.so.3.1: undefined reference to `H5Aget_type' > ../libcgns.so.3.1: undefined reference to `H5Fcreate' > ../libcgns.so.3.1: undefined reference to `H5Sset_extent_simple' > ../libcgns.so.3.1: undefined reference to `H5Sclose' > ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_SCHAR_g' > ../libcgns.so.3.1: undefined reference to `H5Aopen_name' > ../libcgns.so.3.1: undefined reference to `H5Gunlink' > ../libcgns.so.3.1: undefined reference to `H5Lget_val' > ../libcgns.so.3.1: undefined reference to `H5Tget_native_type' > ../libcgns.so.3.1: undefined reference to `H5Acreate2' > ../libcgns.so.3.1: undefined reference to `H5Aclose' > ../libcgns.so.3.1: undefined reference to `H5Pset_deflate' > ../libcgns.so.3.1: undefined reference to `H5T_C_S1_g' > ../libcgns.so.3.1: undefined reference to `H5Tset_precision' > ../libcgns.so.3.1: undefined reference to `H5Dopen2' > ../libcgns.so.3.1: undefined reference to `H5Dget_type' > ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_FLOAT_g' > ../libcgns.so.3.1: undefined reference to `H5Lunpack_elink_val' > ../libcgns.so.3.1: undefined reference to `H5Dwrite' > ../libcgns.so.3.1: undefined reference to `H5Lcreate_external' > ../libcgns.so.3.1: undefined reference to `H5Dget_storage_size' > ../libcgns.so.3.1: undefined reference to `H5Screate_simple' > ../libcgns.so.3.1: undefined reference to `H5Aread' > ../libcgns.so.3.1: undefined reference to `H5check_version' > ../libcgns.so.3.1: undefined reference to `H5Iget_name' > ../libcgns.so.3.1: undefined reference to `H5Lis_registered' > ../libcgns.so.3.1: undefined reference to `H5Fget_obj_ids' > ../libcgns.so.3.1: undefined reference to `H5P_CLS_GROUP_CREATE_g' > ../libcgns.so.3.1: undefined reference to `H5Gcreate2' > ../libcgns.so.3.1: undefined reference to `H5Giterate' > ../libcgns.so.3.1: undefined reference to `H5Tget_size' > ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_UCHAR_g' > ../libcgns.so.3.1: undefined reference to `H5Screate' > ../libcgns.so.3.1: undefined reference to `H5T_IEEE_F32BE_g' > ../libcgns.so.3.1: undefined reference to `H5Literate' > ../libcgns.so.3.1: undefined reference to `H5Gopen2' > ../libcgns.so.3.1: undefined reference to `H5Dset_extent' > ../libcgns.so.3.1: undefined reference to `H5T_IEEE_F64BE_g' > ../libcgns.so.3.1: undefined reference to `H5Dget_space' > ../libcgns.so.3.1: undefined reference to `H5Dclose' > ../libcgns.so.3.1: undefined reference to `H5P_CLS_FILE_ACCESS_g' > ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_UINT64_g' > > 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 > From wascott at sandia.gov Fri Mar 13 21:02:14 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Sat, 14 Mar 2015 01:02:14 +0000 Subject: [Paraview] [EXTERNAL] Re: Superbuild, CGNS and debug In-Reply-To: References: Message-ID: <7850a62e092341adac3baac33a73a272@ES05AMSNLNT.srn.sandia.gov> I wasn't very clear, was I? :-) I am trying to do a superbuild. I have enabled CMAKE_BUILD_TYPE:STRING=Debug and ENABLE_cgns:BOOL=ON (along with lots of other stuff). I blow away my previous build. I run cmake. I then try to compile the superbuild, and it dies as shown below. Attaching the root CMakeCache.txt file from the superbuild. Alan -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Friday, March 13, 2015 6:51 PM To: Scott, W Alan Cc: paraview at paraview.org Subject: [EXTERNAL] Re: [Paraview] Superbuild, CGNS and debug I don't follow...what do you mean by "get a debugger into a CGNS build of ParaView"? You are getting these errors when building ParaView or running in in a debugger? On Fri, Mar 13, 2015 at 8:19 PM, Scott, W Alan wrote: > I am trying to get a debugger into a CGNS build of ParaView. CGNS > builds seems to be dying trying to link to HDF5. Has anyone else seen > this? Any ideas how to compile debug with CGNS and the Superbuild? > > Here is some of the errors that I am seeing: > > checking whether build environment is sane... ../libcgns.so.3.1: > undefined reference to `H5T_NATIVE_INT32_g' > ../libcgns.so.3.1: undefined reference to `H5P_CLS_FILE_CREATE_g' > ../libcgns.so.3.1: undefined reference to `H5Pcreate' > ../libcgns.so.3.1: undefined reference to `H5Tcopy' > ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_UINT32_g' > ../libcgns.so.3.1: undefined reference to `H5Sget_simple_extent_dims' > ../libcgns.so.3.1: undefined reference to `H5Eset_auto2' > ../libcgns.so.3.1: undefined reference to `H5Sget_simple_extent_ndims' > ../libcgns.so.3.1: undefined reference to `H5Aget_type' > ../libcgns.so.3.1: undefined reference to `H5Fcreate' > ../libcgns.so.3.1: undefined reference to `H5Sset_extent_simple' > ../libcgns.so.3.1: undefined reference to `H5Sclose' > ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_SCHAR_g' > ../libcgns.so.3.1: undefined reference to `H5Aopen_name' > ../libcgns.so.3.1: undefined reference to `H5Gunlink' > ../libcgns.so.3.1: undefined reference to `H5Lget_val' > ../libcgns.so.3.1: undefined reference to `H5Tget_native_type' > ../libcgns.so.3.1: undefined reference to `H5Acreate2' > ../libcgns.so.3.1: undefined reference to `H5Aclose' > ../libcgns.so.3.1: undefined reference to `H5Pset_deflate' > ../libcgns.so.3.1: undefined reference to `H5T_C_S1_g' > ../libcgns.so.3.1: undefined reference to `H5Tset_precision' > ../libcgns.so.3.1: undefined reference to `H5Dopen2' > ../libcgns.so.3.1: undefined reference to `H5Dget_type' > ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_FLOAT_g' > ../libcgns.so.3.1: undefined reference to `H5Lunpack_elink_val' > ../libcgns.so.3.1: undefined reference to `H5Dwrite' > ../libcgns.so.3.1: undefined reference to `H5Lcreate_external' > ../libcgns.so.3.1: undefined reference to `H5Dget_storage_size' > ../libcgns.so.3.1: undefined reference to `H5Screate_simple' > ../libcgns.so.3.1: undefined reference to `H5Aread' > ../libcgns.so.3.1: undefined reference to `H5check_version' > ../libcgns.so.3.1: undefined reference to `H5Iget_name' > ../libcgns.so.3.1: undefined reference to `H5Lis_registered' > ../libcgns.so.3.1: undefined reference to `H5Fget_obj_ids' > ../libcgns.so.3.1: undefined reference to `H5P_CLS_GROUP_CREATE_g' > ../libcgns.so.3.1: undefined reference to `H5Gcreate2' > ../libcgns.so.3.1: undefined reference to `H5Giterate' > ../libcgns.so.3.1: undefined reference to `H5Tget_size' > ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_UCHAR_g' > ../libcgns.so.3.1: undefined reference to `H5Screate' > ../libcgns.so.3.1: undefined reference to `H5T_IEEE_F32BE_g' > ../libcgns.so.3.1: undefined reference to `H5Literate' > ../libcgns.so.3.1: undefined reference to `H5Gopen2' > ../libcgns.so.3.1: undefined reference to `H5Dset_extent' > ../libcgns.so.3.1: undefined reference to `H5T_IEEE_F64BE_g' > ../libcgns.so.3.1: undefined reference to `H5Dget_space' > ../libcgns.so.3.1: undefined reference to `H5Dclose' > ../libcgns.so.3.1: undefined reference to `H5P_CLS_FILE_ACCESS_g' > ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_UINT64_g' > > 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 embedded and charset-unspecified text was scrubbed... Name: CMakeCache.txt URL: From utkarsh.ayachit at kitware.com Fri Mar 13 23:07:42 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 13 Mar 2015 23:07:42 -0400 Subject: [Paraview] [EXTERNAL] Re: Superbuild, CGNS and debug In-Reply-To: <7850a62e092341adac3baac33a73a272@ES05AMSNLNT.srn.sandia.gov> References: <7850a62e092341adac3baac33a73a272@ES05AMSNLNT.srn.sandia.gov> Message-ID: Hmm...odd...not entirely sure why. So this worked with the same settings but "Release" mode earlier and now it's failing with "Debug"? Utkarsh On Fri, Mar 13, 2015 at 9:02 PM, Scott, W Alan wrote: > I wasn't very clear, was I? :-) > > I am trying to do a superbuild. I have enabled CMAKE_BUILD_TYPE:STRING=Debug and ENABLE_cgns:BOOL=ON (along with lots of other stuff). I blow away my previous build. I run cmake. I then try to compile the superbuild, and it dies as shown below. > > Attaching the root CMakeCache.txt file from the superbuild. > > Alan > > > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Friday, March 13, 2015 6:51 PM > To: Scott, W Alan > Cc: paraview at paraview.org > Subject: [EXTERNAL] Re: [Paraview] Superbuild, CGNS and debug > > I don't follow...what do you mean by "get a debugger into a CGNS build of ParaView"? You are getting these errors when building ParaView or running in in a debugger? > > On Fri, Mar 13, 2015 at 8:19 PM, Scott, W Alan wrote: >> I am trying to get a debugger into a CGNS build of ParaView. CGNS >> builds seems to be dying trying to link to HDF5. Has anyone else seen >> this? Any ideas how to compile debug with CGNS and the Superbuild? >> >> Here is some of the errors that I am seeing: >> >> checking whether build environment is sane... ../libcgns.so.3.1: >> undefined reference to `H5T_NATIVE_INT32_g' >> ../libcgns.so.3.1: undefined reference to `H5P_CLS_FILE_CREATE_g' >> ../libcgns.so.3.1: undefined reference to `H5Pcreate' >> ../libcgns.so.3.1: undefined reference to `H5Tcopy' >> ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_UINT32_g' >> ../libcgns.so.3.1: undefined reference to `H5Sget_simple_extent_dims' >> ../libcgns.so.3.1: undefined reference to `H5Eset_auto2' >> ../libcgns.so.3.1: undefined reference to `H5Sget_simple_extent_ndims' >> ../libcgns.so.3.1: undefined reference to `H5Aget_type' >> ../libcgns.so.3.1: undefined reference to `H5Fcreate' >> ../libcgns.so.3.1: undefined reference to `H5Sset_extent_simple' >> ../libcgns.so.3.1: undefined reference to `H5Sclose' >> ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_SCHAR_g' >> ../libcgns.so.3.1: undefined reference to `H5Aopen_name' >> ../libcgns.so.3.1: undefined reference to `H5Gunlink' >> ../libcgns.so.3.1: undefined reference to `H5Lget_val' >> ../libcgns.so.3.1: undefined reference to `H5Tget_native_type' >> ../libcgns.so.3.1: undefined reference to `H5Acreate2' >> ../libcgns.so.3.1: undefined reference to `H5Aclose' >> ../libcgns.so.3.1: undefined reference to `H5Pset_deflate' >> ../libcgns.so.3.1: undefined reference to `H5T_C_S1_g' >> ../libcgns.so.3.1: undefined reference to `H5Tset_precision' >> ../libcgns.so.3.1: undefined reference to `H5Dopen2' >> ../libcgns.so.3.1: undefined reference to `H5Dget_type' >> ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_FLOAT_g' >> ../libcgns.so.3.1: undefined reference to `H5Lunpack_elink_val' >> ../libcgns.so.3.1: undefined reference to `H5Dwrite' >> ../libcgns.so.3.1: undefined reference to `H5Lcreate_external' >> ../libcgns.so.3.1: undefined reference to `H5Dget_storage_size' >> ../libcgns.so.3.1: undefined reference to `H5Screate_simple' >> ../libcgns.so.3.1: undefined reference to `H5Aread' >> ../libcgns.so.3.1: undefined reference to `H5check_version' >> ../libcgns.so.3.1: undefined reference to `H5Iget_name' >> ../libcgns.so.3.1: undefined reference to `H5Lis_registered' >> ../libcgns.so.3.1: undefined reference to `H5Fget_obj_ids' >> ../libcgns.so.3.1: undefined reference to `H5P_CLS_GROUP_CREATE_g' >> ../libcgns.so.3.1: undefined reference to `H5Gcreate2' >> ../libcgns.so.3.1: undefined reference to `H5Giterate' >> ../libcgns.so.3.1: undefined reference to `H5Tget_size' >> ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_UCHAR_g' >> ../libcgns.so.3.1: undefined reference to `H5Screate' >> ../libcgns.so.3.1: undefined reference to `H5T_IEEE_F32BE_g' >> ../libcgns.so.3.1: undefined reference to `H5Literate' >> ../libcgns.so.3.1: undefined reference to `H5Gopen2' >> ../libcgns.so.3.1: undefined reference to `H5Dset_extent' >> ../libcgns.so.3.1: undefined reference to `H5T_IEEE_F64BE_g' >> ../libcgns.so.3.1: undefined reference to `H5Dget_space' >> ../libcgns.so.3.1: undefined reference to `H5Dclose' >> ../libcgns.so.3.1: undefined reference to `H5P_CLS_FILE_ACCESS_g' >> ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_UINT64_g' >> >> 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 >> From ioannis.vogiatzis at psi.ch Sat Mar 14 14:32:13 2015 From: ioannis.vogiatzis at psi.ch (Vogiatzis Oikonomidis Ioannis (PSI)) Date: Sat, 14 Mar 2015 18:32:13 +0000 Subject: [Paraview] yosemite crashes In-Reply-To: References: Message-ID: Hi I updated to Yosemite and I keep getting the following crash I reinstalled paraview already And deleted the files from /library/preferences Could you help me somehow locate/fix the error? Thanks! Process: paraview [639] Path: /Applications/paraview.app/Contents/MacOS/paraview Identifier: ??? Version: ??? (???) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: paraview [639] User ID: 501 Date/Time: 2015-03-14 19:17:35.584 +0100 OS Version: Mac OS X 10.10.2 (14C1510) Report Version: 11 Anonymous UUID: D81E119C-8D65-4AA3-E575-453588A4B223 Time Awake Since Boot: 370 seconds Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: EXC_I386_GPFLT Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 QtCore 0x00000001086bc2c4 QString::operator=(QString const&) + 20 1 libvtkpqCore-pv4.3.1.dylib 0x0000000105bcfb51 pqServerResource::pqImplementation::pqImplementation(QString const&) + 3761 2 libvtkpqCore-pv4.3.1.dylib 0x0000000105bcc998 pqServerResource::pqServerResource(QString const&) + 40 3 libvtkpqCore-pv4.3.1.dylib 0x0000000105bbd1bd pqRecentlyUsedResourcesList::load(pqSettings&) + 205 4 libvtkpqCore-pv4.3.1.dylib 0x0000000105b72178 pqApplicationCore::recentlyUsedResources() + 72 5 libvtkpqComponents-pv4.3.1.dylib0x00000001057d2ff3 pqRecentFilesMenu::pqRecentFilesMenu(QMenu&, QObject*) + 83 6 libvtkpqApplicationComponents-pv4.3.1.dylib0x000000010492fe77 pqParaViewMenuBuilders::buildFileMenu(QMenu&) + 167 7 0x00000001047ec93d ParaViewMainWindow::ParaViewMainWindow() + 1533 8 0x00000001047eac28 pqparaviewInitializer::Initialize(int, char**) + 632 9 0x00000001047ea7ea main + 346 10 0x00000001047ea684 start + 52 Thread 1:: Dispatch queue: com.apple.libdispatch-manager 0 libsystem_kernel.dylib 0x00007fff898b0232 kevent64 + 10 1 libdispatch.dylib 0x00007fff8c1aca6a _dispatch_mgr_thread + 52 Thread 2: 0 libsystem_kernel.dylib 0x00007fff898af94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8f15640d start_wqthread + 13 Thread 3: 0 libsystem_kernel.dylib 0x00007fff898af94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8f15640d start_wqthread + 13 Thread 4: 0 libsystem_kernel.dylib 0x00007fff898af94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8f15640d start_wqthread + 13 Thread 5: 0 libsystem_kernel.dylib 0x00007fff898af94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8f15640d start_wqthread + 13 Thread 6: 0 libsystem_kernel.dylib 0x00007fff898aa4de mach_msg_trap + 10 1 libsystem_kernel.dylib 0x00007fff898a964f mach_msg + 55 2 com.apple.CoreFoundation 0x00007fff85150b34 __CFRunLoopServiceMachPort + 212 3 com.apple.CoreFoundation 0x00007fff8514fffb __CFRunLoopRun + 1371 4 com.apple.CoreFoundation 0x00007fff8514f858 CFRunLoopRunSpecific + 296 5 com.apple.AppKit 0x00007fff8c82b33b _NSEventThread + 137 6 libsystem_pthread.dylib 0x00007fff8f158268 _pthread_body + 131 7 libsystem_pthread.dylib 0x00007fff8f1581e5 _pthread_start + 176 8 libsystem_pthread.dylib 0x00007fff8f15641d thread_start + 13 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x6000000000000000 rbx: 0x00007ff5b97b2b98 rcx: 0x0000000000000000 rdx: 0x00007ff5b97b2ba8 rdi: 0x00007ff5b97b2b98 rsi: 0x00007ff5bb868a40 rbp: 0x00007fff5b427370 rsp: 0x00007fff5b427350 r8: 0x0000000000000001 r9: 0x00000000f8000000 r10: 0x0000000000000005 r11: 0x00007ff5b9700000 r12: 0x00007fff5b4273b8 r13: 0x00007ff5bb868a50 r14: 0x00007ff5bb868a40 r15: 0x00007ff5bb89ba68 rip: 0x00000001086bc2c4 rfl: 0x0000000000010206 cr2: 0x000000010871c660 Logical CPU: 0 Error Code: 0x00000000 Trap Number: 13 Binary Images: 0x1047d8000 - 0x1048b8fff + (??? - ???) <4BC69DCC-801D-3147-B644-34C32D30589E> /Applications/paraview.app/Contents/MacOS/paraview 0x1048c7000 - 0x1049f4ff7 +libvtkpqApplicationComponents-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkpqApplicationComponents-pv4.3.1.dylib 0x104a74000 - 0x1053a0ff7 +libvtkPVServerManagerApplication-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkPVServerManagerApplication-pv4.3.1.dylib 0x10568e000 - 0x105690fff +libvtkUtilitiesPythonInitializer-pv4.3.1.dylib (1) <5472BDC8-A99D-345A-8CC5-70B1A2ED5531> /Applications/paraview.app/Contents/Libraries/libvtkUtilitiesPythonInitializer-pv4.3.1.dylib 0x105697000 - 0x105a08ff7 +libvtkpqComponents-pv4.3.1.dylib (1) <8C344569-0D53-3E23-8F80-30E591C07AB6> /Applications/paraview.app/Contents/Libraries/libvtkpqComponents-pv4.3.1.dylib 0x105b01000 - 0x105b2ffff +libvtkpqPython-pv4.3.1.dylib (1) <95DD2CE4-E399-3AA8-8189-829D3FF01117> /Applications/paraview.app/Contents/Libraries/libvtkpqPython-pv4.3.1.dylib 0x105b45000 - 0x105ceafff +libvtkpqCore-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkpqCore-pv4.3.1.dylib 0x105da8000 - 0x105e11ff7 +libvtkpqWidgets-pv4.3.1.dylib (1) <15BDB4F2-210D-383B-B89A-9598F1BEEBFE> /Applications/paraview.app/Contents/Libraries/libvtkpqWidgets-pv4.3.1.dylib 0x105e5e000 - 0x105ea1fff +libQtTesting.dylib (0) /Applications/paraview.app/Contents/Libraries/libQtTesting.dylib 0x105ecc000 - 0x105f3bff7 +QtHelp (4.8.6) <3192B34A-3926-37D1-8B89-3B3492B5FBFF> /Applications/paraview.app/Contents/Frameworks/QtHelp.framework/Versions/4/QtHelp 0x105f6a000 - 0x105f9aff7 +QtSql (4.8.6) <33136CCE-45BB-36B6-AD25-709CDB65E699> /Applications/paraview.app/Contents/Frameworks/QtSql.framework/Versions/4/QtSql 0x105fb0000 - 0x105ff0ff7 +QtXml (4.8.6) /Applications/paraview.app/Contents/Frameworks/QtXml.framework/Versions/4/QtXml 0x10600d000 - 0x10611aff7 +libvtkPVServerManagerCore-pv4.3.1.dylib (1) <01FA3A66-BB73-30AF-A6D7-1F444066A48F> /Applications/paraview.app/Contents/Libraries/libvtkPVServerManagerCore-pv4.3.1.dylib 0x106198000 - 0x106209ff7 +libvtkPVServerImplementationCore-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkPVServerImplementationCore-pv4.3.1.dylib 0x106256000 - 0x1062f8fff +libprotobuf.dylib (0) <3EB31081-36B8-3439-AE66-D4A9D8D155DD> /Applications/paraview.app/Contents/Libraries/libprotobuf.dylib 0x106350000 - 0x1063e1ff7 +libvtkPVClientServerCoreCore-pv4.3.1.dylib (1) <47DC486E-3E55-3734-A6BC-3FC5AD6372E8> /Applications/paraview.app/Contents/Libraries/libvtkPVClientServerCoreCore-pv4.3.1.dylib 0x106421000 - 0x106428fff +libvtkFiltersProgrammable-pv4.3.1.dylib (1) <8D4509AA-86B9-37C4-BC58-B664CCBCD51A> /Applications/paraview.app/Contents/Libraries/libvtkFiltersProgrammable-pv4.3.1.dylib 0x106432000 - 0x106459fff +libvtkGUISupportQt-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkGUISupportQt-pv4.3.1.dylib 0x10647f000 - 0x106499fff +libvtkPVVTKExtensionsCore-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkPVVTKExtensionsCore-pv4.3.1.dylib 0x1064b7000 - 0x1064ccff7 +libvtkPVCommon-pv4.3.1.dylib (1) <6FC2CE8D-B9C6-3C69-8DD3-B4D4A98A1B01> /Applications/paraview.app/Contents/Libraries/libvtkPVCommon-pv4.3.1.dylib 0x1064de000 - 0x1064feff7 +libvtkClientServer-pv4.3.1.dylib (1) <5B932017-BE40-3143-B802-A57D40DE4F69> /Applications/paraview.app/Contents/Libraries/libvtkClientServer-pv4.3.1.dylib 0x106513000 - 0x106519fff +libvtkPythonInterpreter-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkPythonInterpreter-pv4.3.1.dylib 0x106522000 - 0x10656afff +libvtkFiltersParallel-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkFiltersParallel-pv4.3.1.dylib 0x10659e000 - 0x1065adfff +libvtkParallelMPI-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkParallelMPI-pv4.3.1.dylib 0x1065b8000 - 0x1065c7ff7 +libvtkIOXMLParser-pv4.3.1.dylib (1) <058B93DA-80DE-31B2-B4E2-F525667E3E55> /Applications/paraview.app/Contents/Libraries/libvtkIOXMLParser-pv4.3.1.dylib 0x1065d0000 - 0x106604fff +libvtkParallelCore-pv4.3.1.dylib (1) <0FB741D0-6E83-3297-831F-3AF5F96AECB0> /Applications/paraview.app/Contents/Libraries/libvtkParallelCore-pv4.3.1.dylib 0x106619000 - 0x10666cff7 +libvtkIOLegacy-pv4.3.1.dylib (1) <95E43364-0198-3FEA-A59D-860DBBE28638> /Applications/paraview.app/Contents/Libraries/libvtkIOLegacy-pv4.3.1.dylib 0x106696000 - 0x1066bbfff +libvtkInteractionStyle-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkInteractionStyle-pv4.3.1.dylib 0x1066db000 - 0x10670dff7 +libvtkFiltersModeling-pv4.3.1.dylib (1) <6DEDC1C1-49FC-3983-B06C-657D8D534B8B> /Applications/paraview.app/Contents/Libraries/libvtkFiltersModeling-pv4.3.1.dylib 0x10672f000 - 0x106882fff +libvtkRenderingOpenGL-pv4.3.1.dylib (1) <0FA9DEC6-9EC1-31F9-8E20-15E5419F4DFB> /Applications/paraview.app/Contents/Libraries/libvtkRenderingOpenGL-pv4.3.1.dylib 0x10691d000 - 0x106966ff7 +libvtkIOCore-pv4.3.1.dylib (1) <40806557-8A1C-3448-909F-43E790CE3390> /Applications/paraview.app/Contents/Libraries/libvtkIOCore-pv4.3.1.dylib 0x106991000 - 0x106a91ff7 +libvtkRenderingCore-pv4.3.1.dylib (1) <6BA5FDD3-BBD2-32C0-A9FF-60818592062D> /Applications/paraview.app/Contents/Libraries/libvtkRenderingCore-pv4.3.1.dylib 0x106b17000 - 0x106b28fff +libvtkCommonColor-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkCommonColor-pv4.3.1.dylib 0x106b32000 - 0x106bc5fff +libvtkFiltersExtraction-pv4.3.1.dylib (1) <15B9907A-F426-346E-B988-B69BECAA775C> /Applications/paraview.app/Contents/Libraries/libvtkFiltersExtraction-pv4.3.1.dylib 0x106bf0000 - 0x106c3cfff +libvtkFiltersStatistics-pv4.3.1.dylib (1) <0EA46DF4-EDEB-3B36-9892-CEE76F8C0E3B> /Applications/paraview.app/Contents/Libraries/libvtkFiltersStatistics-pv4.3.1.dylib 0x106c62000 - 0x106c79fff +libvtkImagingFourier-pv4.3.1.dylib (1) <07ADAC2B-6403-3998-A200-B0DBD2F73B27> /Applications/paraview.app/Contents/Libraries/libvtkImagingFourier-pv4.3.1.dylib 0x106c8a000 - 0x106dcaff7 +libvtkImagingCore-pv4.3.1.dylib (1) <48B71579-97AA-3688-8C30-29EE957B21DF> /Applications/paraview.app/Contents/Libraries/libvtkImagingCore-pv4.3.1.dylib 0x106e1a000 - 0x106e3bff7 +libvtkalglib-pv4.3.1.dylib (1) <06B28EF3-A2E9-3C83-A76B-E34913D9DB34> /Applications/paraview.app/Contents/Libraries/libvtkalglib-pv4.3.1.dylib 0x106e45000 - 0x106e86fff +libvtkFiltersGeometry-pv4.3.1.dylib (1) <00AD1596-23E6-318C-80DC-A0FAEF21CEDF> /Applications/paraview.app/Contents/Libraries/libvtkFiltersGeometry-pv4.3.1.dylib 0x106ea9000 - 0x106ef8ff7 +libvtkFiltersSources-pv4.3.1.dylib (1) <29EA8573-FFCE-371C-86D1-A2B09533BF23> /Applications/paraview.app/Contents/Libraries/libvtkFiltersSources-pv4.3.1.dylib 0x106f2b000 - 0x10711dff7 +libvtkFiltersGeneral-pv4.3.1.dylib (1) <1148AC8C-DFC2-327F-AC5F-6557D7A2B736> /Applications/paraview.app/Contents/Libraries/libvtkFiltersGeneral-pv4.3.1.dylib 0x1071c1000 - 0x10746cff7 +libvtkFiltersCore-pv4.3.1.dylib (1) <4D14E490-6E9A-3912-8FD3-CE43C26B78EA> /Applications/paraview.app/Contents/Libraries/libvtkFiltersCore-pv4.3.1.dylib 0x1074f0000 - 0x107542fff +libvtkCommonExecutionModel-pv4.3.1.dylib (1) <3580792E-DFB7-3B53-81CC-05B54831DD90> /Applications/paraview.app/Contents/Libraries/libvtkCommonExecutionModel-pv4.3.1.dylib 0x107586000 - 0x10759bff7 +libvtkCommonComputationalGeometry-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkCommonComputationalGeometry-pv4.3.1.dylib 0x1075b0000 - 0x1077cdfff +libvtkCommonDataModel-pv4.3.1.dylib (1) <9F954D39-EA3C-3C65-A107-6C5C246DCB10> /Applications/paraview.app/Contents/Libraries/libvtkCommonDataModel-pv4.3.1.dylib 0x10789f000 - 0x1078bbff7 +libvtkCommonTransforms-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkCommonTransforms-pv4.3.1.dylib 0x1078ce000 - 0x1078dcfff +libvtkCommonMisc-pv4.3.1.dylib (1) <20CE15AC-AFD2-37C0-9A26-AB7AB4C1514F> /Applications/paraview.app/Contents/Libraries/libvtkCommonMisc-pv4.3.1.dylib 0x1078e6000 - 0x1078fbfff +libvtkCommonMath-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkCommonMath-pv4.3.1.dylib 0x107908000 - 0x107914ff7 +libvtkCommonSystem-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkCommonSystem-pv4.3.1.dylib 0x107925000 - 0x107929fff com.apple.agl (3.3.0 - AGL-3.3.0) <8DEEE0ED-5B8C-3B37-AF85-D82A0E207B83> /System/Library/Frameworks/AGL.framework/Versions/A/AGL 0x107935000 - 0x108284ff7 +QtGui (4.8.6) /Applications/paraview.app/Contents/Frameworks/QtGui.framework/Versions/4/QtGui 0x10850b000 - 0x1085feff7 +QtNetwork (4.8.6) <759A9FCA-B8B6-32B7-95B8-14972442D74B> /Applications/paraview.app/Contents/Frameworks/QtNetwork.framework/Versions/4/QtNetwork 0x108653000 - 0x1088eaff7 +QtCore (4.8.6) /Applications/paraview.app/Contents/Frameworks/QtCore.framework/Versions/4/QtCore 0x10897a000 - 0x10899dfff +libvtkWrappingPython27Core-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkWrappingPython27Core-pv4.3.1.dylib 0x1089ae000 - 0x108c34fff +libvtkCommonCore-pv4.3.1.dylib (1) <5D27F918-213A-382A-9203-AB1951997967> /Applications/paraview.app/Contents/Libraries/libvtkCommonCore-pv4.3.1.dylib 0x108d0b000 - 0x108dfcff7 org.python.python (2.7.6 - 2.7.6) /System/Library/Frameworks/Python.framework/Versions/2.7/Python 0x108e63000 - 0x108e95fff +libvtksys-pv4.3.1.dylib (1) <2B04D8E0-C9E7-3301-87C8-2E0CB851AA8A> /Applications/paraview.app/Contents/Libraries/libvtksys-pv4.3.1.dylib 0x108eab000 - 0x108ef2fff +libvtkPVAnimation-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkPVAnimation-pv4.3.1.dylib 0x108f18000 - 0x108f4bff7 +libvtkPVServerManagerDefault-pv4.3.1.dylib (1) <682A8844-22DF-3882-8E2C-DFD072523506> /Applications/paraview.app/Contents/Libraries/libvtkPVServerManagerDefault-pv4.3.1.dylib 0x108f66000 - 0x108fdfff7 +libvtkPVServerManagerRendering-pv4.3.1.dylib (1) <69CDF348-ADCC-3E16-81A8-914A39814AF6> /Applications/paraview.app/Contents/Libraries/libvtkPVServerManagerRendering-pv4.3.1.dylib 0x10901f000 - 0x109045ff7 +libvtkPVServerImplementationRendering-pv4.3.1.dylib (1) <5D0776E6-D8AF-31B0-B3F1-65BA594C7FB3> /Applications/paraview.app/Contents/Libraries/libvtkPVServerImplementationRendering-pv4.3.1.dylib 0x109057000 - 0x10911cfff +libvtkPVClientServerCoreRendering-pv4.3.1.dylib (1) <76E36697-303F-3438-8EB6-8122BB8C3B22> /Applications/paraview.app/Contents/Libraries/libvtkPVClientServerCoreRendering-pv4.3.1.dylib 0x1091a7000 - 0x10937bfff +libvtkPVVTKExtensionsDefault-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkPVVTKExtensionsDefault-pv4.3.1.dylib 0x109437000 - 0x109452fff +libvtkFiltersParallelStatistics-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkFiltersParallelStatistics-pv4.3.1.dylib 0x10946d000 - 0x1094cafff +libvtkIOEnSight-pv4.3.1.dylib (1) <56E34E92-AE00-38C5-AAF5-F1733E4B43EB> /Applications/paraview.app/Contents/Libraries/libvtkIOEnSight-pv4.3.1.dylib 0x1094e2000 - 0x109506fff +libvtkIOImport-pv4.3.1.dylib (1) <06AE17B8-BCFA-3BCA-A813-D1BB03443CAB> /Applications/paraview.app/Contents/Libraries/libvtkIOImport-pv4.3.1.dylib 0x109515000 - 0x109524fff +libvtkIOMPIImage-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkIOMPIImage-pv4.3.1.dylib 0x109532000 - 0x109564fff +libvtkIOParallel-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkIOParallel-pv4.3.1.dylib 0x109584000 - 0x1095c4fff +libvtkIONetCDF-pv4.3.1.dylib (1) <609A5595-7205-3AC3-B99C-F2D1FB67C0FE> /Applications/paraview.app/Contents/Libraries/libvtkIONetCDF-pv4.3.1.dylib 0x1095dd000 - 0x1095fafff +libvtkIOParallelExodus-pv4.3.1.dylib (1) <777BA698-791D-319D-887D-C162E82FFB2A> /Applications/paraview.app/Contents/Libraries/libvtkIOParallelExodus-pv4.3.1.dylib 0x10960f000 - 0x109680fff +libvtkIOExodus-pv4.3.1.dylib (1) <52718EF1-E525-37CE-B116-BD1F7D51AAF2> /Applications/paraview.app/Contents/Libraries/libvtkIOExodus-pv4.3.1.dylib 0x1096af000 - 0x1096bffff +libvtkIOParallelXML-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkIOParallelXML-pv4.3.1.dylib 0x1096d7000 - 0x1097aeff7 +libvtkPVVTKExtensionsRendering-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkPVVTKExtensionsRendering-pv4.3.1.dylib 0x109821000 - 0x10983bfff +libvtkFiltersGeneric-pv4.3.1.dylib (1) <261E7736-545C-364E-BF68-3C8BA0CA1C3A> /Applications/paraview.app/Contents/Libraries/libvtkFiltersGeneric-pv4.3.1.dylib 0x109853000 - 0x109872fff +libvtkFiltersHyperTree-pv4.3.1.dylib (1) <18BB4C85-FA1B-3538-877B-9C8166F3EE3B> /Applications/paraview.app/Contents/Libraries/libvtkFiltersHyperTree-pv4.3.1.dylib 0x10988a000 - 0x1098aafff +libvtkFiltersParallelMPI-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkFiltersParallelMPI-pv4.3.1.dylib 0x1098bf000 - 0x1098caff7 +libvtkRenderingFreeTypeOpenGL-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkRenderingFreeTypeOpenGL-pv4.3.1.dylib 0x1098d8000 - 0x1098e5ff7 +libvtkRenderingMatplotlib-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkRenderingMatplotlib-pv4.3.1.dylib 0x1098ef000 - 0x109916fff +libvtkRenderingParallel-pv4.3.1.dylib (1) <1FAF4ADF-17FC-3048-A55D-15D6AFFA9EC2> /Applications/paraview.app/Contents/Libraries/libvtkRenderingParallel-pv4.3.1.dylib 0x10992f000 - 0x1099a7ff7 +libvtkRenderingParallelLIC-pv4.3.1.dylib (1) <95F627A9-F981-3A3A-8517-3884E9E6570E> /Applications/paraview.app/Contents/Libraries/libvtkRenderingParallelLIC-pv4.3.1.dylib 0x1099d2000 - 0x109a5aff7 +libvtkRenderingLIC-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkRenderingLIC-pv4.3.1.dylib 0x109a7d000 - 0x109a80fff +libIceTMPI.dylib (0) /Applications/paraview.app/Contents/Libraries/libIceTMPI.dylib 0x109a88000 - 0x109ae7fe7 +libpmpich.3.3.dylib (3) <4DB0267B-CB59-315D-9F0D-0CE796D1B11A> /Applications/paraview.app/Contents/Libraries/libpmpich.3.3.dylib 0x109afc000 - 0x109c42fef +libmpich.3.3.dylib (3) /Applications/paraview.app/Contents/Libraries/libmpich.3.3.dylib 0x109ccb000 - 0x109ccbff7 +libopa.1.dylib (2) <8C11CB09-92C1-31E6-9057-FD4CED5223F0> /Applications/paraview.app/Contents/Libraries/libopa.1.dylib 0x109cd5000 - 0x109cd8fff +libmpl.1.dylib (3) <640A334F-A318-358E-A7A4-4FA3BF21D403> /Applications/paraview.app/Contents/Libraries/libmpl.1.dylib 0x109ce1000 - 0x109ce4ff7 +libIceTGL.dylib (0) <40F31FBA-B539-33CF-B851-056676F71A6D> /Applications/paraview.app/Contents/Libraries/libIceTGL.dylib 0x109cee000 - 0x109d0aff7 +libIceTCore.dylib (0) <4EAD8DAC-24E4-3E48-8A9A-845834CCB8FE> /Applications/paraview.app/Contents/Libraries/libIceTCore.dylib 0x109d11000 - 0x109d30fff +libvtkDomainsChemistry-pv4.3.1.dylib (1) <99D915C9-07D3-369D-9590-5518440786CA> /Applications/paraview.app/Contents/Libraries/libvtkDomainsChemistry-pv4.3.1.dylib 0x109d48000 - 0x109db0ff7 +libvtkIOXML-pv4.3.1.dylib (1) <270D6EC0-0A5A-31D5-916E-A0E7E0795A59> /Applications/paraview.app/Contents/Libraries/libvtkIOXML-pv4.3.1.dylib 0x109df3000 - 0x109ed5ff7 +libvtkIOGeometry-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkIOGeometry-pv4.3.1.dylib 0x109f10000 - 0x109f1bfff +libvtkRenderingVolumeAMR-pv4.3.1.dylib (1) <61FA61B2-FDB0-3D50-A8A9-64DEB9D1EEAF> /Applications/paraview.app/Contents/Libraries/libvtkRenderingVolumeAMR-pv4.3.1.dylib 0x109f23000 - 0x109f3bfff +libvtkFiltersAMR-pv4.3.1.dylib (1) <510A291D-7AD3-3801-84BB-C673F2E15F3C> /Applications/paraview.app/Contents/Libraries/libvtkFiltersAMR-pv4.3.1.dylib 0x109f51000 - 0x109fc5ff7 +libvtkRenderingVolumeOpenGL-pv4.3.1.dylib (1) <0792C71E-CC00-3B00-8F42-C6F594E94D0F> /Applications/paraview.app/Contents/Libraries/libvtkRenderingVolumeOpenGL-pv4.3.1.dylib 0x109fe7000 - 0x109ff5ff7 +libvtkViewsContext2D-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkViewsContext2D-pv4.3.1.dylib 0x10a000000 - 0x10a01afff +libvtkViewsCore-pv4.3.1.dylib (1) <41AB0330-34B7-3AFA-82E1-08100DAC2A74> /Applications/paraview.app/Contents/Libraries/libvtkViewsCore-pv4.3.1.dylib 0x10a030000 - 0x10a05fff7 +libvtkWebGLExporter-pv4.3.1.dylib (1) <64E9D93E-098A-3F17-9988-F2ADE26A6645> /Applications/paraview.app/Contents/Libraries/libvtkWebGLExporter-pv4.3.1.dylib 0x10a06a000 - 0x10a185fff +libvtkInteractionWidgets-pv4.3.1.dylib (1) <096276C8-6360-3E03-BF39-68B1BB1CACE0> /Applications/paraview.app/Contents/Libraries/libvtkInteractionWidgets-pv4.3.1.dylib 0x10a227000 - 0x10a2aaff7 +libvtkFiltersHybrid-pv4.3.1.dylib (1) <02C7C38F-5D97-3460-BCDF-D84CFE861176> /Applications/paraview.app/Contents/Libraries/libvtkFiltersHybrid-pv4.3.1.dylib 0x10a2d6000 - 0x10a367ff7 +libvtkImagingGeneral-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkImagingGeneral-pv4.3.1.dylib 0x10a391000 - 0x10a3b9ff7 +libvtkImagingSources-pv4.3.1.dylib (1) <2F2B7317-EF18-34B2-9463-C66E47CC375A> /Applications/paraview.app/Contents/Libraries/libvtkImagingSources-pv4.3.1.dylib 0x10a3c9000 - 0x10a6d0fff +libvtkRenderingVolume-pv4.3.1.dylib (1) <1C8C3509-02F0-377A-8098-179459456F40> /Applications/paraview.app/Contents/Libraries/libvtkRenderingVolume-pv4.3.1.dylib 0x10a901000 - 0x10a93fff7 +libvtkIOExport-pv4.3.1.dylib (1) <33ABAE99-BA81-3A1C-B51B-FAA0F08FD8EF> /Applications/paraview.app/Contents/Libraries/libvtkIOExport-pv4.3.1.dylib 0x10a95b000 - 0x10a9e0fff +libvtkRenderingAnnotation-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkRenderingAnnotation-pv4.3.1.dylib 0x10aa20000 - 0x10aa47fff +libvtkImagingColor-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkImagingColor-pv4.3.1.dylib 0x10aa5f000 - 0x10aaccfff +libvtkRenderingLabel-pv4.3.1.dylib (1) <9D8DD187-96B5-3E71-8B84-E2C1D26C5804> /Applications/paraview.app/Contents/Libraries/libvtkRenderingLabel-pv4.3.1.dylib 0x10aaf0000 - 0x10ab01fff +libvtkRenderingGL2PS-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkRenderingGL2PS-pv4.3.1.dylib 0x10ab0f000 - 0x10ab2efff +libvtkRenderingContextOpenGL-pv4.3.1.dylib (1) <35BEC02F-7FEB-3061-A925-A19EEAACDCE7> /Applications/paraview.app/Contents/Libraries/libvtkRenderingContextOpenGL-pv4.3.1.dylib 0x10ab41000 - 0x10ab78fff +libvtkImagingHybrid-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkImagingHybrid-pv4.3.1.dylib 0x10ab93000 - 0x10ac94fff +libvtkIOImage-pv4.3.1.dylib (1) <310D3749-015D-34BF-B0E5-AB516E7207B0> /Applications/paraview.app/Contents/Libraries/libvtkIOImage-pv4.3.1.dylib 0x10acd6000 - 0x10adb8ff7 +libvtkChartsCore-pv4.3.1.dylib (1) <6E7525F6-975A-3D4F-88E4-0EAE5262024E> /Applications/paraview.app/Contents/Libraries/libvtkChartsCore-pv4.3.1.dylib 0x10adfa000 - 0x10ae16ff7 +libvtkRenderingContext2D-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkRenderingContext2D-pv4.3.1.dylib 0x10ae2b000 - 0x10ae60ff7 +libvtkRenderingFreeType-pv4.3.1.dylib (1) <5D924F70-334A-3471-B593-5A552268CB0B> /Applications/paraview.app/Contents/Libraries/libvtkRenderingFreeType-pv4.3.1.dylib 0x10aeeb000 - 0x10aef2ff7 +libvtkftgl-pv4.3.1.dylib (1) <3B42DD7E-40E5-3023-9D0D-B12304507983> /Applications/paraview.app/Contents/Libraries/libvtkftgl-pv4.3.1.dylib 0x10aefa000 - 0x10af6cfff +libvtkfreetype-pv4.3.1.dylib (1) <43FDBA0C-4C59-3BDF-A4C7-4230C9CA2BC4> /Applications/paraview.app/Contents/Libraries/libvtkfreetype-pv4.3.1.dylib 0x10af80000 - 0x10af91ff7 +libvtkzlib-pv4.3.1.dylib (1) <4E7B5BAE-E1E8-3F96-9826-E04CFE2B654A> /Applications/paraview.app/Contents/Libraries/libvtkzlib-pv4.3.1.dylib 0x10af95000 - 0x10afc6fff +libvtkPVClientServerCoreDefault-pv4.3.1.dylib (1) <74915F79-D481-33EC-8B42-83DEA5F9FD32> /Applications/paraview.app/Contents/Libraries/libvtkPVClientServerCoreDefault-pv4.3.1.dylib 0x10afdc000 - 0x10afebfff +libvtkTestingRendering-pv4.3.1.dylib (1) <0CFC448F-5330-3790-AB55-8A5600205F2B> /Applications/paraview.app/Contents/Libraries/libvtkTestingRendering-pv4.3.1.dylib 0x10affb000 - 0x10b01aff7 +libvtkjpeg-pv4.3.1.dylib (1) <01DF8BE0-02DE-352A-928A-E10B6B857206> /Applications/paraview.app/Contents/Libraries/libvtkjpeg-pv4.3.1.dylib 0x10b021000 - 0x10b03dfff +libvtkpng-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkpng-pv4.3.1.dylib 0x10b045000 - 0x10b093fff +libvtktiff-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtktiff-pv4.3.1.dylib 0x10b09f000 - 0x10b10fff7 +libvtkmetaio-pv4.3.1.dylib (1) <33B098D1-03F2-3AEA-88CA-FD37B5BC3312> /Applications/paraview.app/Contents/Libraries/libvtkmetaio-pv4.3.1.dylib 0x10b139000 - 0x10b149fff +libvtkDICOMParser-pv4.3.1.dylib (1) <33063DF5-5642-3BFA-ACBB-6AB9A66BED02> /Applications/paraview.app/Contents/Libraries/libvtkDICOMParser-pv4.3.1.dylib 0x10b15a000 - 0x10b175fff +libvtkjsoncpp-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkjsoncpp-pv4.3.1.dylib 0x10b185000 - 0x10b1a7fff +libvtkpugixml-pv4.3.1.dylib (1) <8B519171-1ADC-34F3-98FF-B8A7C68D8A28> /Applications/paraview.app/Contents/Libraries/libvtkpugixml-pv4.3.1.dylib 0x10b1b4000 - 0x10b1bfff7 +libmpichcxx.3.3.dylib (3) /Applications/paraview.app/Contents/Libraries/libmpichcxx.3.3.dylib 0x10b1da000 - 0x10b1f6ff7 +libvtkexpat-pv4.3.1.dylib (1) <0EE1AB4B-4637-3766-81A0-D4617B012862> /Applications/paraview.app/Contents/Libraries/libvtkexpat-pv4.3.1.dylib 0x10b201000 - 0x10b2d6ff7 +libQtCLucene.4.8.6.dylib (4.8.6) <3698852D-5AB2-3629-B633-5D3C440BBCDA> /Applications/paraview.app/Contents/Libraries/libQtCLucene.4.8.6.dylib 0x10b368000 - 0x10b370fff +libvtkIOMovie-pv4.3.1.dylib (1) <740B37F9-EB35-3AD8-9118-3355ABAE1ABF> /Applications/paraview.app/Contents/Libraries/libvtkIOMovie-pv4.3.1.dylib 0x10b37d000 - 0x10b386ff7 +libvtkIOFFMPEG-pv4.3.1.dylib (1) <21F44A85-D490-3337-911A-8C9767E8618D> /Applications/paraview.app/Contents/Libraries/libvtkIOFFMPEG-pv4.3.1.dylib 0x10b391000 - 0x10b3c4ff7 +libvtkoggtheora-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkoggtheora-pv4.3.1.dylib 0x10b3cf000 - 0x10b410fff +libvtkIOInfovis-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkIOInfovis-pv4.3.1.dylib 0x10b436000 - 0x10b4b0ff7 +libvtkNetCDF-pv4.3.1.dylib (1) <2CFF277E-40F2-350A-B86B-97568FDBF1CA> /Applications/paraview.app/Contents/Libraries/libvtkNetCDF-pv4.3.1.dylib 0x10b517000 - 0x10b52aff7 +libvtkNetCDF_cxx-pv4.3.1.dylib (1) <901FADFF-564C-3A35-82D2-8576138A321E> /Applications/paraview.app/Contents/Libraries/libvtkNetCDF_cxx-pv4.3.1.dylib 0x10b53b000 - 0x10b77cfff +libhdf5.1.8.13.dylib (1.8.13) <1E597EEB-BBFA-38B1-89F4-F98811100A9E> /Applications/paraview.app/Contents/Libraries/libhdf5.1.8.13.dylib 0x10b7b9000 - 0x10b7d0ff7 +libhdf5_hl.1.8.13.dylib (1.8.13) /Applications/paraview.app/Contents/Libraries/libhdf5_hl.1.8.13.dylib 0x10b7ef000 - 0x10b877fff +libvtkInfovisCore-pv4.3.1.dylib (1) <5A7D15C2-4A16-3D81-BB9B-4226A2F6557F> /Applications/paraview.app/Contents/Libraries/libvtkInfovisCore-pv4.3.1.dylib 0x10b8bb000 - 0x10b8fbfff +libvtkexoIIc-pv4.3.1.dylib (1) <3E3D0FEE-CAFA-3575-B1DC-364E5087CD17> /Applications/paraview.app/Contents/Libraries/libvtkexoIIc-pv4.3.1.dylib 0x10b906000 - 0x10b91cff7 +libsz.2.0.0.dylib (3) <24F97187-414C-321F-A4A7-A1940B1D4E1C> /Applications/paraview.app/Contents/Libraries/libsz.2.0.0.dylib 0x10b92b000 - 0x10b941ff7 +libvtkgl2ps-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkgl2ps-pv4.3.1.dylib 0x10b949000 - 0x10ba72ff7 +libvtklibxml2-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtklibxml2-pv4.3.1.dylib 0x10baa5000 - 0x10bbadfff +libavformat.55.48.100.dylib (55.48.100) <50306DDA-D994-3F4C-9051-40A6E8B0CCE0> /Applications/paraview.app/Contents/Libraries/libavformat.55.48.100.dylib 0x10bbdf000 - 0x10bfa1fef +libavcodec.55.69.100.dylib (55.69.100) <750867A2-16AC-34B5-A7F2-EA2737610B46> /Applications/paraview.app/Contents/Libraries/libavcodec.55.69.100.dylib 0x10c338000 - 0x10c36aff7 +libavutil.52.92.100.dylib (52.92.100) <6240342E-1539-3C71-9336-90FC81D0D977> /Applications/paraview.app/Contents/Libraries/libavutil.52.92.100.dylib 0x10c389000 - 0x10c3e8ff7 +libswscale.2.6.100.dylib (2.6.100) <220113D9-09CF-39F6-858F-A712A980E2A8> /Applications/paraview.app/Contents/Libraries/libswscale.2.6.100.dylib 0x10c3f5000 - 0x10c3f6fff com.apple.VideoDecodeAcceleration (1.1 - 8) /System/Library/Frameworks/VideoDecodeAcceleration.framework/Versions/A/VideoDecodeAcceleration 0x10c400000 - 0x10c41dfff +libvtkFiltersParallelFlowPaths-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkFiltersParallelFlowPaths-pv4.3.1.dylib 0x10c435000 - 0x10c445ff7 +libvtkFiltersParallelImaging-pv4.3.1.dylib (1) <1E142C83-10BE-3473-8CBA-9CD6CB009961> /Applications/paraview.app/Contents/Libraries/libvtkFiltersParallelImaging-pv4.3.1.dylib 0x10c454000 - 0x10c465ff7 +libvtkFiltersImaging-pv4.3.1.dylib (1) <4FDF2F1C-5CCF-379A-B268-00CAAFA2AD51> /Applications/paraview.app/Contents/Libraries/libvtkFiltersImaging-pv4.3.1.dylib 0x10c472000 - 0x10c478fff +libvtkFiltersPython-pv4.3.1.dylib (1) <68BE1615-7BFF-3F36-8D9D-C2BA202D15BD> /Applications/paraview.app/Contents/Libraries/libvtkFiltersPython-pv4.3.1.dylib 0x10c480000 - 0x10c48ffff +libvtkFiltersTexture-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkFiltersTexture-pv4.3.1.dylib 0x10c49c000 - 0x10c4abff7 +libvtkFiltersVerdict-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkFiltersVerdict-pv4.3.1.dylib 0x10c4b9000 - 0x10c4e0ff7 +libvtkverdict-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkverdict-pv4.3.1.dylib 0x10c4ea000 - 0x10c50dfff +libvtkIOAMR-pv4.3.1.dylib (1) <89F257DF-7922-33C5-B1F5-A380BAB111DD> /Applications/paraview.app/Contents/Libraries/libvtkIOAMR-pv4.3.1.dylib 0x10c520000 - 0x10c52efff +libvtkIOPLY-pv4.3.1.dylib (1) <68505D87-5E53-32C1-95A3-9C9E26E0CA8C> /Applications/paraview.app/Contents/Libraries/libvtkIOPLY-pv4.3.1.dylib 0x10c53e000 - 0x10c546ff7 +libvtkIOParallelLSDyna-pv4.3.1.dylib (1) <293D4702-2733-3D3F-82D2-818B65CE05D6> /Applications/paraview.app/Contents/Libraries/libvtkIOParallelLSDyna-pv4.3.1.dylib 0x10c552000 - 0x10c597fff +libvtkIOLSDyna-pv4.3.1.dylib (1) <12ADC5E5-92B0-33F3-B96A-E8AF53ADDCA9> /Applications/paraview.app/Contents/Libraries/libvtkIOLSDyna-pv4.3.1.dylib 0x10c5ad000 - 0x10c5b8ff7 +libvtkIOParallelNetCDF-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkIOParallelNetCDF-pv4.3.1.dylib 0x10c5c7000 - 0x10c5d1ff7 +libvtkIOVPIC-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkIOVPIC-pv4.3.1.dylib 0x10c5dc000 - 0x10c5eeff7 +libvtkVPIC-pv4.3.1.dylib (1) <7C6FC608-9489-328A-95DA-779D158E625B> /Applications/paraview.app/Contents/Libraries/libvtkVPIC-pv4.3.1.dylib 0x10c5fc000 - 0x10caa7ff7 +libvtkIOVisItBridge-pv4.3.1.dylib (1) <6F235AB1-0753-39CA-88D0-D08211EB97B9> /Applications/paraview.app/Contents/Libraries/libvtkIOVisItBridge-pv4.3.1.dylib 0x10cbcb000 - 0x10cc04fff +libvtkFiltersFlowPaths-pv4.3.1.dylib (1) <3C0EC193-6B3F-3FE3-854D-372F5FBD1C5B> /Applications/paraview.app/Contents/Libraries/libvtkFiltersFlowPaths-pv4.3.1.dylib 0x10cc29000 - 0x10cc50ff7 +libvtkIOXdmf2-pv4.3.1.dylib (1) <1B9EBB16-5059-3D1D-B926-656F33AFC1D4> /Applications/paraview.app/Contents/Libraries/libvtkIOXdmf2-pv4.3.1.dylib 0x10cc6c000 - 0x10ccbcfff +libvtkImagingMorphological-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkImagingMorphological-pv4.3.1.dylib 0x10ccd3000 - 0x10cce6ff7 +libvtkInteractionImage-pv4.3.1.dylib (1) <31230E13-4265-3861-B835-032DBA547247> /Applications/paraview.app/Contents/Libraries/libvtkInteractionImage-pv4.3.1.dylib 0x10ccf7000 - 0x10cd95ff7 +libvtkPVVTKExtensionsCosmoTools-pv4.3.1.dylib (1) <6EA41887-9CBC-36FF-BD1D-6AC4599E3464> /Applications/paraview.app/Contents/Libraries/libvtkPVVTKExtensionsCosmoTools-pv4.3.1.dylib 0x10cdc6000 - 0x10cdcdfff +libvtkParallelMPI4Py-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkParallelMPI4Py-pv4.3.1.dylib 0x10cdd4000 - 0x10cddeff7 +libvtkRenderingLOD-pv4.3.1.dylib (1) <5EF4A213-43B3-3B1F-8E2A-30FC03691739> /Applications/paraview.app/Contents/Libraries/libvtkRenderingLOD-pv4.3.1.dylib 0x10cde6000 - 0x10ce0dff7 +libvtkParaViewWebCore-pv4.3.1.dylib (1) <73F0A5EC-1778-38D8-B5B0-A405C1BA2762> /Applications/paraview.app/Contents/Libraries/libvtkParaViewWebCore-pv4.3.1.dylib 0x10ce19000 - 0x10ce32ff7 +libvtkWebCore-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkWebCore-pv4.3.1.dylib 0x10ce41000 - 0x10d18fff7 +libvtkvisitcommon-pv4.3.1.dylib (1) <3A0EFF98-97CA-36AD-A190-3D6BDA87FBC1> /Applications/paraview.app/Contents/Libraries/libvtkvisitcommon-pv4.3.1.dylib 0x10d2ac000 - 0x10d36ffff +libvtkavtdatabase_par-pv4.3.1.dylib (1) <9F7651A1-15D6-3241-AB60-A76F595B2B02> /Applications/paraview.app/Contents/Libraries/libvtkavtdatabase_par-pv4.3.1.dylib 0x10d3b8000 - 0x10d499fff +libvtkavtpipeline_par-pv4.3.1.dylib (1) <801F6604-FDA1-3826-83B1-2AD6C50BA3CF> /Applications/paraview.app/Contents/Libraries/libvtkavtpipeline_par-pv4.3.1.dylib 0x10d52a000 - 0x10d544fff +libvtkavtivp-pv4.3.1.dylib (1) <8CAEA88E-65C1-3978-A2E2-692DBE367F94> /Applications/paraview.app/Contents/Libraries/libvtkavtivp-pv4.3.1.dylib 0x10d54f000 - 0x10d625fff +libvtkvisit_vtk-pv4.3.1.dylib (1) <6C69269C-8A26-369C-AC60-288466F16F07> /Applications/paraview.app/Contents/Libraries/libvtkvisit_vtk-pv4.3.1.dylib 0x10d684000 - 0x10d7fffff +libsiloh5.dylib (0) <8C24854F-D96C-3276-888F-B9E8640BF217> /Applications/paraview.app/Contents/Libraries/libsiloh5.dylib 0x10d891000 - 0x10d909ff7 +libcgns.3.1.dylib (3.1) /Applications/paraview.app/Contents/Libraries/libcgns.3.1.dylib 0x10d93e000 - 0x10d9a5ff7 +libvtkavtdbatts-pv4.3.1.dylib (1) <441C59A2-80E8-386D-8DA2-F80D74B23372> /Applications/paraview.app/Contents/Libraries/libvtkavtdbatts-pv4.3.1.dylib 0x10d9da000 - 0x10da13ff7 +libvtklightweight_visit_vtk-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtklightweight_visit_vtk-pv4.3.1.dylib 0x10da54000 - 0x10da5dfff +libvtkavtmath-pv4.3.1.dylib (1) <5D678EBD-A0CF-36A7-8DC4-3820A44232E9> /Applications/paraview.app/Contents/Libraries/libvtkavtmath-pv4.3.1.dylib 0x10da63000 - 0x10dab2fff +libvtkxdmf2-pv4.3.1.dylib (1) /Applications/paraview.app/Contents/Libraries/libvtkxdmf2-pv4.3.1.dylib 0x10fc25000 - 0x10fc40ff3 com.apple.security.csparser (3.0 - 57031.10.10) <6AC29346-B10D-3986-B06E-876B57392FC2> /System/Library/Frameworks/Security.framework/PlugIns/csparser.bundle/Contents/MacOS/csparser 0x10fc53000 - 0x10fcfffff ColorSyncDeprecated.dylib (442) <478F3331-E7E2-36BF-9C4D-A86D8F542225> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/Resources/ColorSyncDeprecated.dylib 0x11445c000 - 0x114461fff +libqgif.dylib (0) <21044114-2C24-3E6C-A6A9-64A29C4158D1> /Applications/paraview.app/Contents/Plugins/imageformats/libqgif.dylib 0x114466000 - 0x11446bfff +libqico.dylib (0) <3107C469-5CA7-3047-93CC-FEBAAF98F011> /Applications/paraview.app/Contents/Plugins/imageformats/libqico.dylib 0x114470000 - 0x1144a8fff +libqjpeg.dylib (0) <6BF550B0-D41B-3E0A-9165-9A68E9F41732> /Applications/paraview.app/Contents/Plugins/imageformats/libqjpeg.dylib 0x1144b1000 - 0x1144fdfff +libqmng.dylib (0) <70C0ADB6-A5E3-3F77-90DE-9346263191A4> /Applications/paraview.app/Contents/Plugins/imageformats/libqmng.dylib 0x11450f000 - 0x114512ff7 +libqtga.dylib (0) <58A92F0F-440B-3C6D-9CC1-1AC9407B5B86> /Applications/paraview.app/Contents/Plugins/imageformats/libqtga.dylib 0x114517000 - 0x114568ff7 +libqtiff.dylib (0) <2B884758-C84A-30A8-A174-A94705087821> /Applications/paraview.app/Contents/Plugins/imageformats/libqtiff.dylib 0x7fff6dd2a000 - 0x7fff6dd60837 dyld (353.2.1) <65DCCB06-339C-3E25-9702-600A28291D0E> /usr/lib/dyld 0x7fff813d8000 - 0x7fff81498fff com.apple.backup.framework (1.6.2 - 1.6.2) <63E8CA47-B7B8-3A63-B505-D1622CE52527> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup 0x7fff814a4000 - 0x7fff814a6ffb libCGXType.A.dylib (775.16) /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib 0x7fff814a7000 - 0x7fff814f8ff7 com.apple.AppleVAFramework (5.0.31 - 5.0.31) <56AA4060-63DF-3DF0-AB8A-880D0DD6F075> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA 0x7fff81577000 - 0x7fff81579ff7 libsystem_coreservices.dylib (9) <41B7C578-5A53-31C8-A96F-C73E030B0938> /usr/lib/system/libsystem_coreservices.dylib 0x7fff815bc000 - 0x7fff81837ff7 com.apple.CoreData (111 - 526.1) /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData 0x7fff81838000 - 0x7fff8183aff7 libsystem_sandbox.dylib (358.1.1) <95312E09-DA28-324A-A084-F3E574D0210E> /usr/lib/system/libsystem_sandbox.dylib 0x7fff8183b000 - 0x7fff8188aff7 com.apple.opencl (2.4.2 - 2.4.2) /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL 0x7fff818d0000 - 0x7fff81937ff7 com.apple.framework.CoreWiFi (3.0 - 300.4) <19269C1D-EB29-384A-83F3-7DDDEB7D9DAD> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi 0x7fff81938000 - 0x7fff8193cff7 libGIF.dylib (1232) <3C70FBBC-FBA5-3013-A440-05D68B63885F> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib 0x7fff81950000 - 0x7fff8195dff7 libxar.1.dylib (254) /usr/lib/libxar.1.dylib 0x7fff81a7d000 - 0x7fff81db0fff libmecabra.dylib (666.2) /usr/lib/libmecabra.dylib 0x7fff81db1000 - 0x7fff81dc7ff7 libsystem_asl.dylib (267) /usr/lib/system/libsystem_asl.dylib 0x7fff81dc8000 - 0x7fff82030ff3 com.apple.security (7.0 - 57031.10.10) <79C37E73-271B-3BEF-A96E-CDB83FF12CF0> /System/Library/Frameworks/Security.framework/Versions/A/Security 0x7fff820b8000 - 0x7fff82149ff7 com.apple.cloudkit.CloudKit (259.2.5 - 259.2.5) <241EB647-C917-32F7-956A-6E505827048C> /System/Library/Frameworks/CloudKit.framework/Versions/A/CloudKit 0x7fff822b7000 - 0x7fff822b9fff libRadiance.dylib (1232) <9C2DBBDF-0F0B-36BF-84D0-13E0086F793A> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib 0x7fff822ba000 - 0x7fff822cbff3 libsystem_coretls.dylib (35.10.1) <3EAED90A-7AA0-323C-A52B-E16477981D59> /usr/lib/system/libsystem_coretls.dylib 0x7fff822cc000 - 0x7fff822cefff com.apple.SecCodeWrapper (4.0 - 238.10.1) <8DAF71DB-C99A-3B72-A639-2C8CBEA84B93> /System/Library/PrivateFrameworks/SecCodeWrapper.framework/Versions/A/SecCodeWrapper 0x7fff822cf000 - 0x7fff82315ff7 libauto.dylib (186) /usr/lib/libauto.dylib 0x7fff82316000 - 0x7fff82631fcf com.apple.vImage (8.0 - 8.0) <1183FE6A-FDB6-3B3B-928D-50C7909F2308> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage 0x7fff82641000 - 0x7fff829acfff com.apple.VideoToolbox (1.0 - 1562.107) <2EAFB008-7F19-34C2-A5A6-43B4CD35FEF3> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox 0x7fff829c2000 - 0x7fff829e6fef libJPEG.dylib (1232) <638302B6-369F-3C50-BF63-F8D19C393F47> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib 0x7fff829e7000 - 0x7fff82cceffb com.apple.CoreServices.CarbonCore (1108.2 - 1108.2) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore 0x7fff82ce7000 - 0x7fff82ce9fff com.apple.EFILogin (2.0 - 2) <39895ACB-E756-342C-ABE5-DB7100EF0A69> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin 0x7fff82cea000 - 0x7fff82cf0ff7 libsystem_networkextension.dylib (167.1.10) <29AB225B-D7FB-30ED-9600-65D44B9A9442> /usr/lib/system/libsystem_networkextension.dylib 0x7fff82d27000 - 0x7fff82d2cff7 libsystem_stats.dylib (163.10.18) <9B8CCF24-DDDB-399A-9237-4BEC225D2E8C> /usr/lib/system/libsystem_stats.dylib 0x7fff82d2d000 - 0x7fff82d7aff3 com.apple.CoreMediaIO (601.0 - 4749) /System/Library/Frameworks/CoreMediaIO.framework/Versions/A/CoreMediaIO 0x7fff82d7b000 - 0x7fff82d98ffb libresolv.9.dylib (57) <26B38E61-298A-3C3A-82C1-3B5E98AD5E29> /usr/lib/libresolv.9.dylib 0x7fff82da8000 - 0x7fff82ddfffb com.apple.LDAPFramework (2.4.28 - 194.5) /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP 0x7fff82e0c000 - 0x7fff83219ff7 libLAPACK.dylib (1128) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib 0x7fff8321e000 - 0x7fff83250ff3 com.apple.frameworks.CoreDaemon (1.3 - 1.3) /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon 0x7fff83403000 - 0x7fff835fd46f libobjc.A.dylib (647) <759E155D-BC42-3D4E-869B-6F57D477177C> /usr/lib/libobjc.A.dylib 0x7fff835fe000 - 0x7fff83e37fe3 com.apple.CoreGraphics (1.600.0 - 775.16) /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics 0x7fff83e45000 - 0x7fff83e99fff libc++.1.dylib (120) <1B9530FD-989B-3174-BB1C-BDC159501710> /usr/lib/libc++.1.dylib 0x7fff83ee8000 - 0x7fff83fd8fef libJP2.dylib (1232) <13BFC6A7-E24E-3F29-AD3C-E2D382A1223A> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib 0x7fff83fde000 - 0x7fff84067fff com.apple.CoreSymbolication (3.1 - 57020) /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication 0x7fff84068000 - 0x7fff84070fff libsystem_platform.dylib (63) <64E34079-D712-3D66-9CE2-418624A5C040> /usr/lib/system/libsystem_platform.dylib 0x7fff84071000 - 0x7fff8409cff3 libarchive.2.dylib (30) <8CBB4416-EBE9-3574-8ADC-44655D245F39> /usr/lib/libarchive.2.dylib 0x7fff8409d000 - 0x7fff840cdff3 com.apple.CoreAVCHD (5.7.5 - 5750.4.1) <3E51287C-E97D-3886-BE88-8F6872400876> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD 0x7fff8441b000 - 0x7fff84476fef libTIFF.dylib (1232) <56D444B7-A37A-30BC-80B5-5E702FFAAAAB> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib 0x7fff84477000 - 0x7fff84490ff7 com.apple.CFOpenDirectory (10.10 - 187) <0F9747EF-12A3-3694-984D-0B8352CA6C0F> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory 0x7fff84491000 - 0x7fff84522ff7 libCoreStorage.dylib (471.10.6) <892DEEE7-C8C7-35EA-931D-FF9862BDEB2B> /usr/lib/libCoreStorage.dylib 0x7fff84541000 - 0x7fff845b0fff com.apple.SearchKit (1.4.0 - 1.4.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit 0x7fff845b1000 - 0x7fff848b5ffb com.apple.HIToolbox (2.1.1 - 757.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox 0x7fff848f1000 - 0x7fff84a4fffb com.apple.avfoundation (2.0 - 889.102) <7D2E62AF-CDEA-394C-84B2-656629F00197> /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation 0x7fff84a59000 - 0x7fff84aa2ff3 com.apple.HIServices (1.22 - 520.12) <8EAC82AB-6A7D-3606-AF6F-60A9410D1278> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices 0x7fff84fb7000 - 0x7fff84fcbff7 com.apple.ProtectedCloudStorage (1.0 - 1) <52CFE68A-0663-3756-AB5B-B42195026052> /System/Library/PrivateFrameworks/ProtectedCloudStorage.framework/Versions/A/ProtectedCloudStorage 0x7fff84fcc000 - 0x7fff85038fff com.apple.framework.CoreWLAN (5.0 - 500.35.2) <37551DDD-C07C-31EB-923A-9721F03D7E29> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN 0x7fff85039000 - 0x7fff85046fff com.apple.SpeechRecognitionCore (2.0.32 - 2.0.32) <87F0C88D-502D-3217-8B4A-8388288568BA> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore 0x7fff85047000 - 0x7fff850dbfff com.apple.ink.framework (10.9 - 213) <8E029630-1530-3734-A446-13353F0E7AC5> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink 0x7fff850dc000 - 0x7fff850ddfff libsystem_secinit.dylib (18) <581DAD0F-6B63-3A48-B63B-917AF799ABAA> /usr/lib/system/libsystem_secinit.dylib 0x7fff850de000 - 0x7fff85474fff com.apple.CoreFoundation (6.9 - 1152) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x7fff854de000 - 0x7fff854defff com.apple.CoreServices (62 - 62) <9E4577CA-3FC3-300D-AB00-87ADBDDA2E37> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices 0x7fff854e8000 - 0x7fff854e8ff7 libunc.dylib (29) <5676F7EA-C1DF-329F-B006-D2C3022B7D70> /usr/lib/system/libunc.dylib 0x7fff854e9000 - 0x7fff854f2ff3 com.apple.CommonAuth (4.0 - 2.0) /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth 0x7fff8565a000 - 0x7fff85685fff com.apple.DictionaryServices (1.2 - 229) <6789EC43-CADA-394D-8FE8-FC3A2DD136B9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices 0x7fff856a9000 - 0x7fff8579dfff libFontParser.dylib (134.1) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib 0x7fff8579e000 - 0x7fff857a8ff7 com.apple.CrashReporterSupport (10.10 - 629) <4BCAA6B5-EC7F-365F-9D3F-BC483B7E956C> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport 0x7fff857a9000 - 0x7fff857bfff7 com.apple.CoreMediaAuthoring (2.2 - 951) <3EAFC9D1-8D7C-30CF-92C7-903A5C241763> /System/Library/PrivateFrameworks/CoreMediaAuthoring.framework/Versions/A/CoreMediaAuthoring 0x7fff857c0000 - 0x7fff857c7fff libCGCMS.A.dylib (775.16) <8A173E74-7123-35F1-B160-853528C144ED> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGCMS.A.dylib 0x7fff857c8000 - 0x7fff857e3ff7 com.apple.aps.framework (4.0 - 4.0) /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService 0x7fff857e4000 - 0x7fff857e4fff com.apple.Accelerate (1.10 - Accelerate 1.10) <2C8AF258-4F11-3BEC-A826-22D7199B3975> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate 0x7fff8588c000 - 0x7fff859a4ffb com.apple.CoreText (352.0 - 454.3) /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText 0x7fff859a5000 - 0x7fff859a6ffb libremovefile.dylib (35) <3485B5F4-6CE8-3C62-8DFD-8736ED6E8531> /usr/lib/system/libremovefile.dylib 0x7fff859b4000 - 0x7fff859eeffb com.apple.DebugSymbols (115 - 115) <6F03761D-7C3A-3C80-8031-AA1C1AD7C706> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols 0x7fff85c98000 - 0x7fff85ce4ff7 com.apple.corelocation (1486.17 - 1615.21.1) /System/Library/Frameworks/CoreLocation.framework/Versions/A/CoreLocation 0x7fff85ce5000 - 0x7fff85cf4fff com.apple.LangAnalysis (1.7.0 - 1.7.0) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis 0x7fff85d4d000 - 0x7fff85d50fff com.apple.IOSurface (97.0.1 - 97.0.1) <0C9ED49D-AADB-3CB9-9A11-F5D765253548> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface 0x7fff85dee000 - 0x7fff85df2fff com.apple.LoginUICore (3.0 - 3.0) <035C8626-9E66-3E3F-9976-BA4BCD9646F3> /System/Library/PrivateFrameworks/LoginUIKit.framework/Versions/A/Frameworks/LoginUICore.framework/Versions/A/LoginUICore 0x7fff85df3000 - 0x7fff85df4fff libSystem.B.dylib (1213) <90B107BC-FF74-32CC-B1CF-4E02F544D957> /usr/lib/libSystem.B.dylib 0x7fff86353000 - 0x7fff863c5ff7 com.apple.framework.IOKit (2.0.2 - 1050.10.8) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit 0x7fff863c6000 - 0x7fff863c7fff com.apple.TrustEvaluationAgent (2.0 - 25) <2D61A2C3-C83E-3A3F-8EC1-736DBEC250AB> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent 0x7fff863fd000 - 0x7fff8640fff7 com.apple.CoreDuetDaemonProtocol (1.0 - 1) /System/Library/PrivateFrameworks/CoreDuetDaemonProtocol.framework/Versions/A/CoreDuetDaemonProtocol 0x7fff8643f000 - 0x7fff86448ff7 libsystem_notify.dylib (133.1.1) <61147800-F320-3DAA-850C-BADF33855F29> /usr/lib/system/libsystem_notify.dylib 0x7fff864ba000 - 0x7fff86528ffb com.apple.Heimdal (4.0 - 2.0) <3E5DA653-A343-3257-ADE1-BA879BAE280F> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal 0x7fff86529000 - 0x7fff86543ff7 liblzma.5.dylib (7) <1D03E875-A7C0-3028-814C-3C27F7B7C079> /usr/lib/liblzma.5.dylib 0x7fff86548000 - 0x7fff86548fff com.apple.ApplicationServices (48 - 48) <5BF7910B-C328-3BF8-BA4F-CE52B574CE01> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices 0x7fff86549000 - 0x7fff86563fff com.apple.AppleVPAFramework (1.2.10 - 1.2.10) /System/Library/PrivateFrameworks/AppleVPA.framework/Versions/A/AppleVPA 0x7fff86564000 - 0x7fff86594fff com.apple.GSS (4.0 - 2.0) /System/Library/Frameworks/GSS.framework/Versions/A/GSS 0x7fff865e8000 - 0x7fff865f2ff7 com.apple.NetAuth (5.0 - 5.0) /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth 0x7fff865f3000 - 0x7fff865f3fff libOpenScriptingUtil.dylib (162) /usr/lib/libOpenScriptingUtil.dylib 0x7fff86696000 - 0x7fff86788fff libxml2.2.dylib (26) /usr/lib/libxml2.2.dylib 0x7fff86789000 - 0x7fff8678dfff libCoreVMClient.dylib (79) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib 0x7fff867a2000 - 0x7fff867afff7 libbz2.1.0.dylib (36) <2DF83FBC-5C08-39E1-94F5-C28653791B5F> /usr/lib/libbz2.1.0.dylib 0x7fff867b0000 - 0x7fff86803ffb libAVFAudio.dylib (118.3) /System/Library/Frameworks/AVFoundation.framework/Versions/A/Resources/libAVFAudio.dylib 0x7fff86804000 - 0x7fff8683cffb libsystem_network.dylib (411.1) <2EC3A005-473F-3C36-A665-F88B5BACC7F0> /usr/lib/system/libsystem_network.dylib 0x7fff868d5000 - 0x7fff86b81fff com.apple.GeoServices (1.0 - 982.4.10) <8A7FE04A-2785-30E7-A6E2-DC15D170DAF5> /System/Library/PrivateFrameworks/GeoServices.framework/Versions/A/GeoServices 0x7fff86b82000 - 0x7fff86ba5fff com.apple.Sharing (328.3.2 - 328.3.2) /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing 0x7fff86ba6000 - 0x7fff86bd9ff7 com.apple.MediaKit (16 - 757) <345EDAFE-3E39-3B0F-8D84-54657EC4396D> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit 0x7fff86be5000 - 0x7fff86c1dfff com.apple.RemoteViewServices (2.0 - 99) /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices 0x7fff86c2b000 - 0x7fff86c36ff7 com.apple.speech.synthesis.framework (5.3.3 - 5.3.3) <7DF3C68C-B219-3E13-AE72-24B8606A1560> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis 0x7fff86c3a000 - 0x7fff86c4dff7 com.apple.CoreBluetooth (1.0 - 1) /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth 0x7fff86ccb000 - 0x7fff86ccffff libpam.2.dylib (20) /usr/lib/libpam.2.dylib 0x7fff86cd0000 - 0x7fff86cd5ff7 libmacho.dylib (862) <126CA2ED-DE91-308F-8881-B9DAEC3C63B6> /usr/lib/system/libmacho.dylib 0x7fff86e14000 - 0x7fff86e96fff com.apple.PerformanceAnalysis (1.0 - 1) <94F08B1A-F6AF-38D5-BE92-4FED34742966> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis 0x7fff86f02000 - 0x7fff86f4fff3 com.apple.print.framework.PrintCore (10.0 - 451) <3CA58254-D14F-3913-9DFB-CAC499570CC7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore 0x7fff875b8000 - 0x7fff875c3fff com.apple.AppSandbox (4.0 - 238.10.1) <4C171026-DC9A-3CEE-AB42-110859674F61> /System/Library/PrivateFrameworks/AppSandbox.framework/Versions/A/AppSandbox 0x7fff875c4000 - 0x7fff875f0fff com.apple.framework.SystemAdministration (1.0 - 1.0) /System/Library/PrivateFrameworks/SystemAdministration.framework/Versions/A/SystemAdministration 0x7fff87624000 - 0x7fff87628fff com.apple.TCC (1.0 - 1) <61F36A72-B983-3A2D-9D37-A2F194D31E7D> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC 0x7fff87629000 - 0x7fff8762bff7 libquarantine.dylib (76) /usr/lib/system/libquarantine.dylib 0x7fff8762c000 - 0x7fff876c2ffb com.apple.CoreMedia (1.0 - 1562.107) /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia 0x7fff876c3000 - 0x7fff876e9ff7 com.apple.ChunkingLibrary (2.1 - 163.1) <3514F2A4-38BD-3849-9286-B3B991057742> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary 0x7fff876ea000 - 0x7fff87738fff libcurl.4.dylib (83.1.2) <337A1FF8-E8B1-3173-9F29-C0D4C851D8E1> /usr/lib/libcurl.4.dylib 0x7fff87739000 - 0x7fff87744fff libcommonCrypto.dylib (60061) /usr/lib/system/libcommonCrypto.dylib 0x7fff87745000 - 0x7fff87756fff libcmph.dylib (1) <46EC3997-DB5E-38AE-BBBB-A035A54AD3C0> /usr/lib/libcmph.dylib 0x7fff879ee000 - 0x7fff879f0fff com.apple.CoreDuetDebugLogging (1.0 - 1) <9A6E5710-EA99-366E-BF40-9A65EC1B46A1> /System/Library/PrivateFrameworks/CoreDuetDebugLogging.framework/Versions/A/CoreDuetDebugLogging 0x7fff87a04000 - 0x7fff87a07ff7 com.apple.Mangrove (1.0 - 1) <2AF1CAE9-8BF9-33C4-9C1B-123DBAF1522B> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove 0x7fff87a08000 - 0x7fff87a1cff7 com.apple.MultitouchSupport.framework (262.33.1 - 262.33.1) <62DF9340-01A1-3E12-A604-C90F6361FD9E> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport 0x7fff883a6000 - 0x7fff883b6ff7 libbsm.0.dylib (34) /usr/lib/libbsm.0.dylib 0x7fff883d3000 - 0x7fff883d3fff com.apple.Cocoa (6.8 - 21) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa 0x7fff883d4000 - 0x7fff883d9fff com.apple.DiskArbitration (2.6 - 2.6) <0DFF4D9B-2AC3-3B82-B5C5-30F4EFBD2DB9> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration 0x7fff88638000 - 0x7fff88643ff7 libkxld.dylib (2782.10.72) <68E07A32-28F5-3FBB-9D74-00B4F53C2FD4> /usr/lib/system/libkxld.dylib 0x7fff88662000 - 0x7fff88679ff7 libLinearAlgebra.dylib (1128) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib 0x7fff8878a000 - 0x7fff88860ff3 com.apple.DiskImagesFramework (10.10.1 - 396) /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages 0x7fff88861000 - 0x7fff8888affb libxslt.1.dylib (13) /usr/lib/libxslt.1.dylib 0x7fff8888b000 - 0x7fff88901fe7 libcorecrypto.dylib (233.1.2) /usr/lib/system/libcorecrypto.dylib 0x7fff8892a000 - 0x7fff8892efff com.apple.CommonPanels (1.2.6 - 96) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels 0x7fff8892f000 - 0x7fff88949ff7 libextension.dylib (55.1) <6D0CF094-85E8-3F5B-A3F1-25ECF60F80D9> /usr/lib/libextension.dylib 0x7fff8894a000 - 0x7fff88956ff7 com.apple.OpenDirectory (10.10 - 187) <8B98ECCB-7EFA-3A58-BD2B-A0835D869B1A> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory 0x7fff88957000 - 0x7fff88c26ff3 com.apple.CoreImage (10.0.33) <6E3DDA29-718B-3BDB-BFAF-F8C201BF93A4> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage.framework/Versions/A/CoreImage 0x7fff88c27000 - 0x7fff88c54fff com.apple.Accounts (113 - 113) <990F0F61-6AC5-3076-932E-02A9A7F75AC4> /System/Library/Frameworks/Accounts.framework/Versions/A/Accounts 0x7fff88c55000 - 0x7fff88d10ff7 com.apple.DiscRecording (9.0 - 9000.4.2) <9BB46993-311A-3F2E-BD77-3CBEFB71C1F0> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording 0x7fff88d11000 - 0x7fff88d19ff7 com.apple.icloud.FindMyDevice (1.0 - 1) /System/Library/PrivateFrameworks/FindMyDevice.framework/Versions/A/FindMyDevice 0x7fff88d1a000 - 0x7fff88d1aff7 libkeymgr.dylib (28) <77845842-DE70-3CC5-BD01-C3D14227CED5> /usr/lib/system/libkeymgr.dylib 0x7fff89139000 - 0x7fff89146fff com.apple.ProtocolBuffer (1 - 225.1) <2D502FBB-D2A0-3937-A5C5-385FA65B3874> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer 0x7fff89148000 - 0x7fff891e6fff com.apple.Metadata (10.7.0 - 917.1) <46BE997C-B1F4-3BED-9332-FAC87297C87A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata 0x7fff891e7000 - 0x7fff89220fff com.apple.AirPlaySupport (2.0 - 215.15) /System/Library/PrivateFrameworks/AirPlaySupport.framework/Versions/A/AirPlaySupport 0x7fff89221000 - 0x7fff89288ffb com.apple.datadetectorscore (6.0 - 396.1.1) <80379385-A4EC-3F9B-AFED-9B1DF781943D> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore 0x7fff89289000 - 0x7fff892a5ff7 libsystem_malloc.dylib (53.1.1) <19BCC257-5717-3502-A71F-95D65AFA861B> /usr/lib/system/libsystem_malloc.dylib 0x7fff892a6000 - 0x7fff892a8fff com.apple.loginsupport (1.0 - 1) <21DBC18C-F260-39FC-B52F-04A5AA84523A> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport 0x7fff892a9000 - 0x7fff892d4fff libc++abi.dylib (125) <88A22A0F-87C6-3002-BFBA-AC0F2808B8B9> /usr/lib/libc++abi.dylib 0x7fff892d5000 - 0x7fff89603fff com.apple.Foundation (6.9 - 1152.14) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation 0x7fff89604000 - 0x7fff8961dfff com.apple.openscripting (1.4 - 162) <80DFF366-B950-3F79-903F-99DA0FFDB570> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting 0x7fff896ce000 - 0x7fff896d9ff7 com.apple.DirectoryService.Framework (10.10 - 187) <29F7A48C-D8DD-33EB-B9E3-863DA7DBB421> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService 0x7fff896da000 - 0x7fff89868fff libBLAS.dylib (1128) <497912C1-A98E-3281-BED7-E9C751552F61> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib 0x7fff89869000 - 0x7fff89895fff libsandbox.1.dylib (358.1.1) /usr/lib/libsandbox.1.dylib 0x7fff89896000 - 0x7fff89898fff libCVMSPluginSupport.dylib (11.1.1) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib 0x7fff89899000 - 0x7fff898b6fff libsystem_kernel.dylib (2782.10.72) <97CD7ACD-EA0C-3434-BEFC-FCD013D6BB73> /usr/lib/system/libsystem_kernel.dylib 0x7fff898b7000 - 0x7fff898bdfff libsystem_trace.dylib (72.1.3) /usr/lib/system/libsystem_trace.dylib 0x7fff898be000 - 0x7fff8996dfe7 libvMisc.dylib (516) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib 0x7fff89b22000 - 0x7fff89bc4ff7 com.apple.Bluetooth (4.3.2 - 4.3.2f6) <95676652-21AB-3FFA-B53D-EBC8BF4E913E> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth 0x7fff89c10000 - 0x7fff89c10fff com.apple.Carbon (154 - 157) <0DF27AD6-ED64-34D7-825D-65297D276652> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon 0x7fff89ff1000 - 0x7fff8a02cfff com.apple.Symbolication (1.4 - 56045) /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication 0x7fff8a02d000 - 0x7fff8a07eff7 com.apple.audio.CoreAudio (4.3.0 - 4.3.0) /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio 0x7fff8a07f000 - 0x7fff8a081fff com.apple.OAuth (25 - 25) /System/Library/PrivateFrameworks/OAuth.framework/Versions/A/OAuth 0x7fff8a0cc000 - 0x7fff8a0cfff7 libdyld.dylib (353.2.1) <4E33E416-F1D8-3598-B8CC-6863E2ECD0E6> /usr/lib/system/libdyld.dylib 0x7fff8aa16000 - 0x7fff8af02ff7 com.apple.MediaToolbox (1.0 - 1562.107) /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox 0x7fff8baff000 - 0x7fff8bb00ff7 libsystem_blocks.dylib (65) <9615D10A-FCA7-3BE4-AA1A-1B195DACE1A1> /usr/lib/system/libsystem_blocks.dylib 0x7fff8bb01000 - 0x7fff8bb0cfff com.apple.CommerceCore (1.0 - 376.6.2) <3FD9A3A6-C12F-31E0-B90E-5E325B595750> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCore.framework/Versions/A/CommerceCore 0x7fff8bb0d000 - 0x7fff8bb28ff7 libCRFSuite.dylib (34) /usr/lib/libCRFSuite.dylib 0x7fff8bb29000 - 0x7fff8bb31fff libMatch.1.dylib (24) /usr/lib/libMatch.1.dylib 0x7fff8bb32000 - 0x7fff8bc76ff7 com.apple.QTKit (7.7.3 - 2890) <6F6CD79F-CFBB-3FE4-82C6-47991346FB17> /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit 0x7fff8bc77000 - 0x7fff8bc82ff7 libcsfde.dylib (471.10.6) /usr/lib/libcsfde.dylib 0x7fff8bd7a000 - 0x7fff8bd81ff7 libcompiler_rt.dylib (35) /usr/lib/system/libcompiler_rt.dylib 0x7fff8bd82000 - 0x7fff8bdaafff libsystem_info.dylib (459) /usr/lib/system/libsystem_info.dylib 0x7fff8bdab000 - 0x7fff8bef1fef libsqlite3.dylib (168) <8B78BED1-7B9B-3943-80DC-0871015AEAC4> /usr/lib/libsqlite3.dylib 0x7fff8bf07000 - 0x7fff8bf7bfff com.apple.ApplicationServices.ATS (360 - 375) <2824D38D-460D-353C-9D18-499B4BEEABB7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS 0x7fff8bf7c000 - 0x7fff8bf83fff com.apple.NetFS (6.0 - 4.0) <1581D25F-CC07-39B0-90E8-5D4F3CF84EBA> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS 0x7fff8bf84000 - 0x7fff8bfa7ff7 com.apple.framework.familycontrols (4.1 - 410) <153DC4C9-3C06-3147-8AC6-024AB4819C00> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyControls 0x7fff8bfa8000 - 0x7fff8bfaefff com.apple.speech.recognition.framework (5.0.9 - 5.0.9) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition 0x7fff8bfd4000 - 0x7fff8c104fff com.apple.UIFoundation (1.0 - 1) <8E030D93-441C-3997-9CD2-55C8DFAC8B84> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation 0x7fff8c105000 - 0x7fff8c10efff libGFXShared.dylib (11.1.1) <7AE7D152-597E-3B27-A52C-8DA76760B61C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib 0x7fff8c13f000 - 0x7fff8c140ff7 libodfde.dylib (22) <52D0ABCD-F464-362C-86EA-ACA10993F556> /usr/lib/libodfde.dylib 0x7fff8c141000 - 0x7fff8c153ff7 com.apple.ImageCapture (9.0 - 9.0) <7FB65DD4-56B5-35C4-862C-7A2DED991D1F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture 0x7fff8c154000 - 0x7fff8c154fff com.apple.audio.units.AudioUnit (1.12 - 1.12) <76EF1C9D-DEA4-3E55-A134-4099B2FD2CF2> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit 0x7fff8c155000 - 0x7fff8c1a4ff7 libstdc++.6.dylib (104.1) <803F6AC8-87DC-3E24-9E80-729B551F6FFF> /usr/lib/libstdc++.6.dylib 0x7fff8c1a5000 - 0x7fff8c1a7fff libsystem_configuration.dylib (699.1.5) <5E14864E-089A-3D84-85A4-980B776427A8> /usr/lib/system/libsystem_configuration.dylib 0x7fff8c1a8000 - 0x7fff8c1d2ff7 libdispatch.dylib (442.1.4) <502CF32B-669B-3709-8862-08188225E4F0> /usr/lib/system/libdispatch.dylib 0x7fff8c363000 - 0x7fff8c365ff7 libutil.dylib (38) <471AD65E-B86E-3C4A-8ABD-B8665A2BCE3F> /usr/lib/libutil.dylib 0x7fff8c3b5000 - 0x7fff8c432fff com.apple.CoreServices.OSServices (640.3 - 640.3) <84A91B00-0ED4-350C-B30A-AEAE437AE02A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices 0x7fff8c433000 - 0x7fff8c555ff7 com.apple.LaunchServices (644.12.4 - 644.12.4) <59E909E8-ED4A-33EA-B85D-D409BADDF854> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices 0x7fff8c556000 - 0x7fff8c688ff7 com.apple.MediaControlSender (2.0 - 215.15) <454420EB-E6FE-3074-8D58-67471E1D61E5> /System/Library/PrivateFrameworks/MediaControlSender.framework/Versions/A/MediaControlSender 0x7fff8c689000 - 0x7fff8c6a3ff3 com.apple.Ubiquity (1.3 - 313) /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Ubiquity 0x7fff8c6a4000 - 0x7fff8d1eeff7 com.apple.AppKit (6.9 - 1344.72) <44EF7DEB-3072-3515-9F34-2857D557E828> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit 0x7fff8d1f0000 - 0x7fff8d3f3ff3 com.apple.CFNetwork (720.2.4 - 720.2.4) /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork 0x7fff8d3f4000 - 0x7fff8d422fff com.apple.CoreServicesInternal (221.2.2 - 221.2.2) <16F7A7F1-CF1D-35AD-A91F-690A814048DF> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal 0x7fff8d423000 - 0x7fff8d463ff7 libGLImage.dylib (11.1.1) <3986BFA3-4F55-380F-B01D-91BA9785D70C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib 0x7fff8d464000 - 0x7fff8d484fff com.apple.IconServices (47.1 - 47.1) /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices 0x7fff8d765000 - 0x7fff8d76bff7 com.apple.XPCService (2.0 - 1) /System/Library/PrivateFrameworks/XPCService.framework/Versions/A/XPCService 0x7fff8d79b000 - 0x7fff8d8adff7 libvDSP.dylib (516) <151B3CCB-77D3-3715-A3D0-7C74CD5C7FFC> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib 0x7fff8d8cb000 - 0x7fff8d906fff com.apple.QD (301 - 301) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD 0x7fff8d907000 - 0x7fff8d923fff com.apple.GenerationalStorage (2.0 - 209.11) <9FF8DD11-25FB-3047-A5BF-9415339B3EEC> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage 0x7fff8da33000 - 0x7fff8db17fff libcrypto.0.9.8.dylib (52.10.1) <2A2924DE-63FB-37F6-B102-84D69240675B> /usr/lib/libcrypto.0.9.8.dylib 0x7fff8db18000 - 0x7fff8db72ff7 com.apple.LanguageModeling (1.0 - 1) /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling 0x7fff8db7d000 - 0x7fff8db9cfff com.apple.CoreDuet (1.0 - 1) <36AA9FD5-2685-314D-B364-3FA4688D86BD> /System/Library/PrivateFrameworks/CoreDuet.framework/Versions/A/CoreDuet 0x7fff8db9d000 - 0x7fff8dba5ffb libcopyfile.dylib (118.1.2) <0C68D3A6-ACDD-3EF3-991A-CC82C32AB836> /usr/lib/system/libcopyfile.dylib 0x7fff8dc4f000 - 0x7fff8dc7ffff libsystem_m.dylib (3086.1) <1E12AB45-6D96-36D0-A226-F24D9FB0D9D6> /usr/lib/system/libsystem_m.dylib 0x7fff8dc80000 - 0x7fff8dc80ff7 liblaunch.dylib (559.10.3) /usr/lib/system/liblaunch.dylib 0x7fff8dc81000 - 0x7fff8dc81fff com.apple.Accelerate.vecLib (3.10 - vecLib 3.10) <9D749502-A228-3BF1-B52F-A182DEEB2C4D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib 0x7fff8dc8e000 - 0x7fff8dcd4ffb libFontRegistry.dylib (134) <01B8034A-45FD-3360-A347-A1896F591363> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib 0x7fff8dcd5000 - 0x7fff8dd61ff7 libsystem_c.dylib (1044.10.1) <199ED5EB-77A1-3D43-AA51-81779CE0A742> /usr/lib/system/libsystem_c.dylib 0x7fff8dd62000 - 0x7fff8dde3ff3 com.apple.CoreUtils (1.0 - 101.1) <45E5E51B-947E-3F2D-BD9C-480E72555C23> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils 0x7fff8dde4000 - 0x7fff8ded6ff7 libiconv.2.dylib (42) <2A06D02F-8B76-3864-8D96-64EF5B40BC6C> /usr/lib/libiconv.2.dylib 0x7fff8ded7000 - 0x7fff8dfffff7 com.apple.coreui (2.1 - 305.6.1) /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI 0x7fff8e000000 - 0x7fff8e008ff7 com.apple.AppleSRP (5.0 - 1) <01EC5144-D09A-3D6A-AE35-F6D48585F154> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP 0x7fff8e043000 - 0x7fff8e1aeff7 com.apple.audio.toolbox.AudioToolbox (1.12 - 1.12) <5C6DBEB4-F2EA-3262-B9FC-AFB89404C1DA> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox 0x7fff8e1d7000 - 0x7fff8e217ff7 com.apple.CloudDocs (1.0 - 280.6) /System/Library/PrivateFrameworks/CloudDocs.framework/Versions/A/CloudDocs 0x7fff8e263000 - 0x7fff8e267fff libcache.dylib (69) <45E9A2E7-99C4-36B2-BEE3-0C4E11614AD1> /usr/lib/system/libcache.dylib 0x7fff8e287000 - 0x7fff8e2b4fff com.apple.CoreVideo (1.8 - 145.1) <18DB07E0-B927-3260-A234-636F298D1917> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo 0x7fff8e33a000 - 0x7fff8e35ffff libPng.dylib (1232) <10DC46CC-A4FD-3B1A-AA23-E4F12938BC13> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib 0x7fff8e360000 - 0x7fff8e737fe7 com.apple.CoreAUC (211.0.0 - 211.0.0) /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC 0x7fff8e738000 - 0x7fff8e759fff com.apple.framework.Apple80211 (10.1 - 1010.64) /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211 0x7fff8e75a000 - 0x7fff8e774ff7 com.apple.Kerberos (3.0 - 1) <7760E0C2-A222-3709-B2A6-B692D900CEB1> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos 0x7fff8e77e000 - 0x7fff8e92eff7 com.apple.QuartzCore (1.10 - 361.15) <72A78C43-30DF-3748-9015-4B28119DB27B> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore 0x7fff8e92f000 - 0x7fff8e93afff libGL.dylib (11.1.1) <1F0EB9FB-4B0F-349B-80DD-93FD3F45B9C7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib 0x7fff8ea70000 - 0x7fff8ea78fff libsystem_dnssd.dylib (561.1.1) <62B70ECA-E40D-3C63-896E-7F00EC386DDB> /usr/lib/system/libsystem_dnssd.dylib 0x7fff8eaa7000 - 0x7fff8eaa9ff7 com.apple.securityhi (9.0 - 55006) <1F40ECF1-6AEF-3E64-9DAD-ADC646CCEA98> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI 0x7fff8eace000 - 0x7fff8ead6ffb com.apple.CoreServices.FSEvents (1210 - 1210) <782A9C69-7A45-31A7-8960-D08A36CBD0A7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents 0x7fff8ec76000 - 0x7fff8ec7bff7 libunwind.dylib (35.3) /usr/lib/system/libunwind.dylib 0x7fff8ec7c000 - 0x7fff8ec8dff7 libz.1.dylib (55) <88C7C7DE-04B8-316F-8B74-ACD9F3DE1AA1> /usr/lib/libz.1.dylib 0x7fff8ec8e000 - 0x7fff8ecb6ffb libRIP.A.dylib (775.16) <7711F7A7-1813-3024-AE42-75CA7C5422B7> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib 0x7fff8ecb7000 - 0x7fff8ecbefff com.apple.network.statistics.framework (1.2 - 1) <61B311D1-7F15-35B3-80D4-99B8BE90ACD9> /System/Library/PrivateFrameworks/NetworkStatistics.framework/Versions/A/NetworkStatistics 0x7fff8ed0a000 - 0x7fff8eda9df7 com.apple.AppleJPEG (1.0 - 1) <9BB3D7DF-630A-3E1C-A124-12D6C4D0DE70> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG 0x7fff8edaa000 - 0x7fff8eeb8fff com.apple.desktopservices (1.9.2 - 1.9.2) <8670FD3B-8A5B-3D84-B21E-DF21140545A2> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv 0x7fff8eeb9000 - 0x7fff8f09eff3 libicucore.A.dylib (531.31) /usr/lib/libicucore.A.dylib 0x7fff8f09f000 - 0x7fff8f134ff7 com.apple.ColorSync (4.9.0 - 4.9.0) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync 0x7fff8f135000 - 0x7fff8f13aff7 com.apple.MediaAccessibility (1.0 - 61) <00A3E0B6-79AC-387E-B282-AADFBD5722F6> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility 0x7fff8f155000 - 0x7fff8f15efff libsystem_pthread.dylib (105.10.1) <3103AA7F-3BAE-3673-9649-47FFD7E15C97> /usr/lib/system/libsystem_pthread.dylib 0x7fff8f23f000 - 0x7fff8f242fff com.apple.xpc.ServiceManagement (1.0 - 1) <5EFD45BF-B0CD-39F2-8232-6BA33E63E5D4> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement 0x7fff8f2cf000 - 0x7fff8f2d0fff liblangid.dylib (117) /usr/lib/liblangid.dylib 0x7fff8f330000 - 0x7fff8f3a4ff3 com.apple.securityfoundation (6.0 - 55126) /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation 0x7fff8f3a5000 - 0x7fff8f3a8fff com.apple.help (1.3.3 - 46) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help 0x7fff8f3a9000 - 0x7fff8f421ff7 com.apple.SystemConfiguration (1.14 - 1.14) /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration 0x7fff8f422000 - 0x7fff8f437ff7 com.apple.AppContainer (4.0 - 238.10.1) <24A43E31-BCD3-32DB-8023-DE7EEA912E89> /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer 0x7fff8f43c000 - 0x7fff8f576ff7 com.apple.ImageIO.framework (3.3.0 - 1232) /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO 0x7fff8f577000 - 0x7fff8f578ff7 com.apple.print.framework.Print (10.0 - 265) <3BC4FE7F-78A0-3E57-8F4C-520E7EFD36FA> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print 0x7fff9069c000 - 0x7fff906e8ff7 libcups.2.dylib (408) <9CECCDE3-51D7-3028-830C-F58BD36E3317> /usr/lib/libcups.2.dylib 0x7fff906e9000 - 0x7fff906f7ff7 com.apple.opengl (11.1.1 - 11.1.1) /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL 0x7fff90717000 - 0x7fff90729fff libsasl2.2.dylib (193) /usr/lib/libsasl2.2.dylib 0x7fff90736000 - 0x7fff90b66fff com.apple.vision.FaceCore (3.1.6 - 3.1.6) /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore 0x7fff90b67000 - 0x7fff90ba8fff libGLU.dylib (11.1.1) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib 0x7fff90ba9000 - 0x7fff90baafff libDiagnosticMessagesClient.dylib (100) <2EE8E436-5CDC-34C5-9959-5BA218D507FB> /usr/lib/libDiagnosticMessagesClient.dylib 0x7fff90bab000 - 0x7fff90bd3fff libxpc.dylib (559.10.3) <876216DC-D5D3-381E-8AF9-49AE464E5107> /usr/lib/system/libxpc.dylib 0x7fff90bd4000 - 0x7fff90bd9ffb libheimdal-asn1.dylib (398.10.1) /usr/lib/libheimdal-asn1.dylib 0x7fff90bda000 - 0x7fff90c39ff3 com.apple.AE (681 - 681) <7F544183-A515-31A8-B45F-89A167F56216> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 1 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 228 thread_create: 1 thread_set_state: 0 VM Region Summary: ReadOnly portion of Libraries: Total=334.5M resident=172.2M(51%) swapped_out_or_unallocated=162.3M(49%) Writable regions: Total=89.8M written=10.7M(12%) resident=18.2M(20%) swapped_out=0K(0%) unallocated=71.6M(80%) REGION TYPE VIRTUAL =========== ======= CG backing stores 800K CG shared images 176K CoreServices 128K CoreUI image data 28K Dispatch continuations 8192K Kernel Alloc Once 8K MALLOC 43.2M MALLOC (admin) 32K Memory Tag 242 12K STACK GUARD 56.0M Stack 10.6M VM_ALLOCATE 17.1M __DATA 28.9M __IMAGE 528K __LINKEDIT 99.0M __TEXT 235.5M __UNICODE 544K mapped file 93.9M shared memory 4K =========== ======= TOTAL 594.4M Model: MacBookPro11,1, BootROM MBP111.0138.B14, 2 processors, Intel Core i5, 2.6 GHz, 16 GB, SMC 2.16f68 Graphics: Intel Iris, Intel Iris, Built-In Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020 Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x112), Broadcom BCM43xx 1.0 (7.15.159.13.12) Bluetooth: Version 4.3.2f6 15235, 3 services, 19 devices, 1 incoming serial ports Network Service: Wi-Fi, AirPort, en0 Serial ATA Device: APPLE SSD SM0256F, 251 GB USB Device: Internal Memory Card Reader USB Device: BRCM20702 Hub USB Device: Bluetooth USB Host Controller USB Device: Apple Internal Keyboard / Trackpad Thunderbolt Bus: MacBook Pro, Apple Inc., 17.2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From livia.barazzetti at istb.unibe.ch Sun Mar 15 05:30:12 2015 From: livia.barazzetti at istb.unibe.ch (livia.barazzetti at istb.unibe.ch) Date: Sun, 15 Mar 2015 09:30:12 +0000 Subject: [Paraview] Paraview support of FieldData in a vtkTable Message-ID: Hello, I am thinking to store some info as FieldData of a table (for example, the parameters used for the calculation of the data in the table - possibly they could also be changing depending on other elements of the pipeline). I tried a toy example in Python and it seems that vtkTable supports it (I am able to add an array and read it back). In Paraview 4.3.1, visualizing the field data from a python annotation works, but if I open the spreadsheet view to see the field data I get Warning: In C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\VTKExtensions\Rendering\vtkMarkSelectedRows.cxx, line 209 vtkMarkSelectedRows (0000000010381890): FieldAssociation type not supported yet. Selected elements may not be shown correctly. , also the writer doen't export the field data. Should I go forward in using the FieldData of a table (just remembering that before exporting I should use a Python annotation or a programmable filter to read the field data) or it is actually not supported by paraview and I should avoid it? (for example, the field data would not be updated as the rest of the pipeline, or something like that)? Thank you Best regards Livia Barazzetti -------------- next part -------------- An HTML attachment was scrubbed... URL: From mshoji-tky at umin.ac.jp Sun Mar 15 10:39:16 2015 From: mshoji-tky at umin.ac.jp (Masaaki SHOJIMA) Date: Sun, 15 Mar 2015 23:39:16 +0900 Subject: [Paraview] Fwd: Gradient of Unstructed dataset In-Reply-To: References: Message-ID: Hi, I calculated the velocity distribution in a cylinder, and calculated the gradient of Pressure with several software. But the results were quite different. "Gradient of Unstructed dataset" was used to calculate the gradient of Pressure. SC/Tetra post and Ensight showed similar results. But the results of Paraview was quite different from the other two software. I would like to hear some advices, please. Thank you. MS [image: ?????? 1] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 209016 bytes Desc: not available URL: From eleonorapiersanti at yahoo.it Sun Mar 15 12:04:08 2015 From: eleonorapiersanti at yahoo.it (Eleonora Piersanti) Date: Sun, 15 Mar 2015 16:04:08 +0000 (UTC) Subject: [Paraview] Select two regions and merge them Message-ID: <282902736.8261653.1426435448248.JavaMail.yahoo@mail.yahoo.com> Hi all,I have two .vtk files with two velocity fields. I would like to select the upper part (y>0) from one file and the lower part from the other one and then to merge them. Is it possible to do this? Thank you,E. -------------- next part -------------- An HTML attachment was scrubbed... URL: From samuelkey at bresnan.net Sun Mar 15 16:58:57 2015 From: samuelkey at bresnan.net (Samuel Key) Date: Sun, 15 Mar 2015 14:58:57 -0600 Subject: [Paraview] Select two regions and merge them In-Reply-To: <282902736.8261653.1426435448248.JavaMail.yahoo@mail.yahoo.com> References: <282902736.8261653.1426435448248.JavaMail.yahoo@mail.yahoo.com> Message-ID: <5505F291.1080108@bresnan.net> An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Mon Mar 16 09:36:30 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Mon, 16 Mar 2015 09:36:30 -0400 Subject: [Paraview] Fwd: Gradient of Unstructed dataset In-Reply-To: References: Message-ID: Hi Masaaki, Can you send me the file? It would be great if you could also send the results from one of the other packages. Best, -berk On Sun, Mar 15, 2015 at 10:39 AM, Masaaki SHOJIMA wrote: > Hi, > > I calculated the velocity distribution in a cylinder, and calculated > the gradient of Pressure with several software. But the results were quite > different. > > "Gradient of Unstructed dataset" was used to calculate the gradient of > Pressure. > > SC/Tetra post and Ensight showed similar results. > But the results of Paraview was quite different from the other two > software. > > I would like to hear some advices, please. > > Thank you. > > MS > > [image: ?????? 1] > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 209016 bytes Desc: not available URL: From arctica1963 at gmail.com Mon Mar 16 09:54:29 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Mon, 16 Mar 2015 13:54:29 +0000 Subject: [Paraview] Earthquake beachball in 3D Message-ID: Hello, I found a script based on the thesis work of Christoph Moder (2006) that was plotting focal mechanism solutions via a Gawk and VTK route. Now, I have managed to get a single solution plotted but not a multiple suite of solutions from a file. Whether the script is not writing the VTK properly or some other issue, I do not know. This is not a perfect solution for this work but is a start. The input is: Longitude Latitude Depth Magnitude Strike Dip Rake sinlgle plot data: 120.07 -7.37 623 6.4 233 38 -96 61 53 -85 Two solutions: 120.07 -7.37 623 6.4 233 38 -96 61 53 -85 121.69 -8.47 39 6.0 68 36 83 257 54 95 The only issue I see with the VTK import in ParaView is that there are no coordinates stored (Long, Lat) so it does not seem possible to position it spatially in a georeferenced view. Data can be retrieved from www.globalcmt.org Cheers Lester -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: beachball2.awk Type: application/octet-stream Size: 4746 bytes Desc: not available URL: From kmorel at sandia.gov Mon Mar 16 11:05:17 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 16 Mar 2015 15:05:17 +0000 Subject: [Paraview] Algorithm to find grain neighbors Message-ID: I don't really understand the question, but the answer is probably no. What do you mean by a "grain"? Is that some roundish feature in the image? And what does it mean for two grains to be neighbors? Does it mean they are touching? That they are within some certain distance of each other? That they are not being obscured by some other grain? Assuming I've guessed closed in any of these aspects, I don't think ParaView comes with any filters that perform that action. -Ken On 3/13/15, 3:21 PM, "Zhang,Ying" wrote: >Dear Paraview developers, > >I sent a question a while ago and probably didn?t get to the list. But >here is my question again: > >I have a grain image in vti format and use Paraview to visualize the >grains. In Paraview I use Representation/Surface along with xml template >for coloring to display the grain image based on the vti file. I would >like to know if there is a way to find out the number of neighbors each >grain has. I wonder if paraview has a such tool to give this information. > >Thank you! > >Ying Zhang > > >_______________________________________________ >Powered by www.kitware.com > >Visit other Kitware open-source projects at >http://www.kitware.com/opensource/opensource.html > >Please keep messages on-topic and check the ParaView Wiki at: >http://paraview.org/Wiki/ParaView > >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 nenasantos at hotmail.com Mon Mar 16 11:18:50 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Mon, 16 Mar 2015 15:18:50 +0000 Subject: [Paraview] Add logo to animation paraview script In-Reply-To: References: Message-ID: Dear all,What are the steps to include a image, as logo, in a corner of an animated script. Basicaly I want to know what is the code that allows to include image as logo in my animated script. I do not want image as background but image as logo, placed in one of the corners of my figure. Kind regards Madalena -------------- next part -------------- An HTML attachment was scrubbed... URL: From yingz at ufl.edu Mon Mar 16 11:18:53 2015 From: yingz at ufl.edu (Zhang,Ying) Date: Mon, 16 Mar 2015 15:18:53 +0000 Subject: [Paraview] Algorithm to find grain neighbors In-Reply-To: References: Message-ID: Hi Ken, I work in Research Computing at University of Florida and have a user (Cc'ed) who is using Paraview to visualize his grain image on our computing systems. Steven, could you explain to Ken about your image and the information you are trying to find? Thanks, Ying > On Mar 16, 2015, at 11:05 AM, Moreland, Kenneth wrote: > > I don't really understand the question, but the answer is probably no. > > > What do you mean by a "grain"? Is that some roundish feature in the image? > And what does it mean for two grains to be neighbors? Does it mean they > are touching? That they are within some certain distance of each other? > That they are not being obscured by some other grain? > > Assuming I've guessed closed in any of these aspects, I don't think > ParaView comes with any filters that perform that action. > > -Ken > > On 3/13/15, 3:21 PM, "Zhang,Ying" wrote: > >> Dear Paraview developers, >> >> I sent a question a while ago and probably didn?t get to the list. But >> here is my question again: >> >> I have a grain image in vti format and use Paraview to visualize the >> grains. In Paraview I use Representation/Surface along with xml template >> for coloring to display the grain image based on the vti file. I would >> like to know if there is a way to find out the number of neighbors each >> grain has. I wonder if paraview has a such tool to give this information. >> >> Thank you! >> >> Ying Zhang >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 yingz at ufl.edu Mon Mar 16 12:08:46 2015 From: yingz at ufl.edu (Zhang,Ying) Date: Mon, 16 Mar 2015 16:08:46 +0000 Subject: [Paraview] Algorithm to find grain neighbors In-Reply-To: References: Message-ID: Sorry that I forgot to Cc Steven. > On Mar 16, 2015, at 11:18 AM, Zhang,Ying wrote: > > Hi Ken, > > I work in Research Computing at University of Florida and have a user (Cc'ed) who is using Paraview to visualize his grain image on our computing systems. > > Steven, could you explain to Ken about your image and the information you are trying to find? > > Thanks, > > Ying > >> On Mar 16, 2015, at 11:05 AM, Moreland, Kenneth wrote: >> >> I don't really understand the question, but the answer is probably no. >> >> >> What do you mean by a "grain"? Is that some roundish feature in the image? >> And what does it mean for two grains to be neighbors? Does it mean they >> are touching? That they are within some certain distance of each other? >> That they are not being obscured by some other grain? >> >> Assuming I've guessed closed in any of these aspects, I don't think >> ParaView comes with any filters that perform that action. >> >> -Ken >> >> On 3/13/15, 3:21 PM, "Zhang,Ying" wrote: >> >>> Dear Paraview developers, >>> >>> I sent a question a while ago and probably didn?t get to the list. But >>> here is my question again: >>> >>> I have a grain image in vti format and use Paraview to visualize the >>> grains. In Paraview I use Representation/Surface along with xml template >>> for coloring to display the grain image based on the vti file. I would >>> like to know if there is a way to find out the number of neighbors each >>> grain has. I wonder if paraview has a such tool to give this information. >>> >>> Thank you! >>> >>> Ying Zhang >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> > From wascott at sandia.gov Mon Mar 16 12:54:31 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 16 Mar 2015 16:54:31 +0000 Subject: [Paraview] [EXTERNAL] Re: Superbuild, CGNS and debug In-Reply-To: References: <7850a62e092341adac3baac33a73a272@ES05AMSNLNT.srn.sandia.gov> Message-ID: <3976194e193d482f9e484603f2cb0ee5@ES05AMSNLNT.srn.sandia.gov> Correct. Alan -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Friday, March 13, 2015 9:08 PM To: Scott, W Alan Cc: paraview at paraview.org Subject: Re: [EXTERNAL] Re: [Paraview] Superbuild, CGNS and debug Hmm...odd...not entirely sure why. So this worked with the same settings but "Release" mode earlier and now it's failing with "Debug"? Utkarsh On Fri, Mar 13, 2015 at 9:02 PM, Scott, W Alan wrote: > I wasn't very clear, was I? :-) > > I am trying to do a superbuild. I have enabled CMAKE_BUILD_TYPE:STRING=Debug and ENABLE_cgns:BOOL=ON (along with lots of other stuff). I blow away my previous build. I run cmake. I then try to compile the superbuild, and it dies as shown below. > > Attaching the root CMakeCache.txt file from the superbuild. > > Alan > > > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Friday, March 13, 2015 6:51 PM > To: Scott, W Alan > Cc: paraview at paraview.org > Subject: [EXTERNAL] Re: [Paraview] Superbuild, CGNS and debug > > I don't follow...what do you mean by "get a debugger into a CGNS build of ParaView"? You are getting these errors when building ParaView or running in in a debugger? > > On Fri, Mar 13, 2015 at 8:19 PM, Scott, W Alan wrote: >> I am trying to get a debugger into a CGNS build of ParaView. CGNS >> builds seems to be dying trying to link to HDF5. Has anyone else >> seen this? Any ideas how to compile debug with CGNS and the Superbuild? >> >> Here is some of the errors that I am seeing: >> >> checking whether build environment is sane... ../libcgns.so.3.1: >> undefined reference to `H5T_NATIVE_INT32_g' >> ../libcgns.so.3.1: undefined reference to `H5P_CLS_FILE_CREATE_g' >> ../libcgns.so.3.1: undefined reference to `H5Pcreate' >> ../libcgns.so.3.1: undefined reference to `H5Tcopy' >> ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_UINT32_g' >> ../libcgns.so.3.1: undefined reference to `H5Sget_simple_extent_dims' >> ../libcgns.so.3.1: undefined reference to `H5Eset_auto2' >> ../libcgns.so.3.1: undefined reference to `H5Sget_simple_extent_ndims' >> ../libcgns.so.3.1: undefined reference to `H5Aget_type' >> ../libcgns.so.3.1: undefined reference to `H5Fcreate' >> ../libcgns.so.3.1: undefined reference to `H5Sset_extent_simple' >> ../libcgns.so.3.1: undefined reference to `H5Sclose' >> ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_SCHAR_g' >> ../libcgns.so.3.1: undefined reference to `H5Aopen_name' >> ../libcgns.so.3.1: undefined reference to `H5Gunlink' >> ../libcgns.so.3.1: undefined reference to `H5Lget_val' >> ../libcgns.so.3.1: undefined reference to `H5Tget_native_type' >> ../libcgns.so.3.1: undefined reference to `H5Acreate2' >> ../libcgns.so.3.1: undefined reference to `H5Aclose' >> ../libcgns.so.3.1: undefined reference to `H5Pset_deflate' >> ../libcgns.so.3.1: undefined reference to `H5T_C_S1_g' >> ../libcgns.so.3.1: undefined reference to `H5Tset_precision' >> ../libcgns.so.3.1: undefined reference to `H5Dopen2' >> ../libcgns.so.3.1: undefined reference to `H5Dget_type' >> ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_FLOAT_g' >> ../libcgns.so.3.1: undefined reference to `H5Lunpack_elink_val' >> ../libcgns.so.3.1: undefined reference to `H5Dwrite' >> ../libcgns.so.3.1: undefined reference to `H5Lcreate_external' >> ../libcgns.so.3.1: undefined reference to `H5Dget_storage_size' >> ../libcgns.so.3.1: undefined reference to `H5Screate_simple' >> ../libcgns.so.3.1: undefined reference to `H5Aread' >> ../libcgns.so.3.1: undefined reference to `H5check_version' >> ../libcgns.so.3.1: undefined reference to `H5Iget_name' >> ../libcgns.so.3.1: undefined reference to `H5Lis_registered' >> ../libcgns.so.3.1: undefined reference to `H5Fget_obj_ids' >> ../libcgns.so.3.1: undefined reference to `H5P_CLS_GROUP_CREATE_g' >> ../libcgns.so.3.1: undefined reference to `H5Gcreate2' >> ../libcgns.so.3.1: undefined reference to `H5Giterate' >> ../libcgns.so.3.1: undefined reference to `H5Tget_size' >> ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_UCHAR_g' >> ../libcgns.so.3.1: undefined reference to `H5Screate' >> ../libcgns.so.3.1: undefined reference to `H5T_IEEE_F32BE_g' >> ../libcgns.so.3.1: undefined reference to `H5Literate' >> ../libcgns.so.3.1: undefined reference to `H5Gopen2' >> ../libcgns.so.3.1: undefined reference to `H5Dset_extent' >> ../libcgns.so.3.1: undefined reference to `H5T_IEEE_F64BE_g' >> ../libcgns.so.3.1: undefined reference to `H5Dget_space' >> ../libcgns.so.3.1: undefined reference to `H5Dclose' >> ../libcgns.so.3.1: undefined reference to `H5P_CLS_FILE_ACCESS_g' >> ../libcgns.so.3.1: undefined reference to `H5T_NATIVE_UINT64_g' >> >> 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 >> From Gottfried.Necker at partner.kit.edu Mon Mar 16 14:14:40 2015 From: Gottfried.Necker at partner.kit.edu (Gottfried Necker) Date: Mon, 16 Mar 2015 19:14:40 +0100 Subject: [Paraview] Temporal collection problem In-Reply-To: <1933136.oAl0JOl9zD@iket-pslinux01> References: <1933136.oAl0JOl9zD@iket-pslinux01> Message-ID: <1997007.C4HApFSnHF@iket-pslinux01> Hello again, I have to reply to myself. On friday I wrote the following mail: > Hello, > > I'm pretty new to ParaView. I'm trying to visualize a short sequence (2 time > steps) using a Xdmf file with a temporal collection. When I open the file > in ParaView 4.3.1 (binary for Linux x64 from paraview.org) I can see the > first time step and display a variable using the threshold filter. Using > the "Current Time Controls" I can go to the second time step, but the > display does not change. On the information tab I can see that ParaView > recognizes the 2 time steps, but when I change the time using the controls > the "Current data time" stays at the first time step. > > When I open the same file in ParaView 4.2.0 I can switch between the two > time steps as expected and everything seems to work fine for this simple > case. And of course the displayed image looks as expected. > > I've attached the XML file to this mail. If anybody is interested to try > this, I can provide the HDF5 files too. > > Is there something wrong with the file(s)? > Unfortunatly I was not able to provide a simple example to demonstrate the problem. But today I found one by modifying a Xdmf test case. The original is TetrahedronSpatialTimestep.xmf, the modified TetrahedronSpatialTimestep- mod.xmf. The change is in the "Value" strings for the time. I deliberately added some decimal places. Using ParaView 4.3.1 I can step through all 3 time steps of the original case, but only through the first 2 of the modified. My original problem also works if the time values are truncated to 4 decimal places. Best regards, Gottfried -------------- next part -------------- A non-text attachment was scrubbed... Name: TetrahedronSpatialTimestep.xmf Type: audio/x-xmf Size: 6567 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: TetrahedronSpatialTimestep-mod.xmf Type: audio/x-xmf Size: 6612 bytes Desc: not available URL: From berk.geveci at kitware.com Mon Mar 16 16:12:43 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Mon, 16 Mar 2015 16:12:43 -0400 Subject: [Paraview] SEG-Y seismic data loading In-Reply-To: References: Message-ID: A quick Google search yields a few Python libraries such as http://segymat.sourceforge.net/segypy/ Has anyone experimented with any of those? Once someone can figure out how to bring the data in, we can figure out how to visualize it. -berk On Sun, Mar 8, 2015 at 9:50 AM, Lester Anderson wrote: > The other workaround is to have an image of the seismic line that can be > georeferenced for loading into Paraview. However, this requires a seismic > viewer capable of exporting a good quality image and not all do (SeiSee is > quite good). Obviously things get a little complex when having to convert > from time to depth, but not so if you are dealing with Z as the time > coordinate. > > Is there a georeference filter/tool in ParaView? > > Cheers > > On 6 March 2015 at 20:55, L?o Pessanha > wrote: > >> Putting a SEG-Y data in a more direct way is still in the escope of one >> of the projects that i am working on. I did some research not a long time >> ago and i found that Richard Strelitz wrote a paraview plugin for reading >> SEG-Y data at LANL but he gave up since there was no easy way of retaining >> the concept of a trace that is so essential to seismic data at the time he >> was still trying. He said that would for some of the files he created but >> we lost contact. >> >> Maybe he could help, and instead of starting from zero, maybe there`s a >> way to continue his work and save some time. >> >> For me it would be a really really great tool to have in paraview! >> >> With the proper guidance, i would really like to help(or try to help) ! >> >> 2015-03-06 11:58 GMT-03:00 David E DeMarle : >> >> +1, this would be great to have in ParaView. >>> >>> Just need someone out there to find the time and or funding to implement >>> it. >>> >>> It could make a nice google summer of code effort if there is a student >>> who is interested in the topic. >>> http://www.kitware.com/blog/home/post/857 >>> >>> >>> David E DeMarle >>> Kitware, Inc. >>> R&D Engineer >>> 21 Corporate Drive >>> Clifton Park, NY 12065-8662 >>> Phone: 518-881-4909 >>> >>> On Fri, Mar 6, 2015 at 7:21 AM, Lester Anderson >>> wrote: >>> >>>> This is definitely an import filter that would make ParaView more >>>> widely used, particularly in industry. Even doing as suggested by Leo, of >>>> reading the coordinates and extracting the amplitude would still be useful >>>> when viewing the data in 3D. >>>> >>>> Perhaps this will be addressed in a future release, but I know this has >>>> been asked for some years back I believe. >>>> >>>> On 5 March 2015 at 22:14, Lester Anderson >>>> wrote: >>>> >>>>> Hi Leo, >>>>> >>>>> Thanks for the suggestions. What software did you use to export the >>>>> data? >>>>> >>>>> Cheers >>>>> Lester >>>>> >>>>> On 5 March 2015 at 19:18, L?o Pessanha >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I would like to apologize, i do not know how to answer a question in >>>>>> the mailing list correctly, i think the way i am doing it right now is >>>>>> going to appear as a new question >>>>>> >>>>>> There is no easy way of doing it, to see SEG-Y data in paraview, i >>>>>> used another software to export the data to ASCII txt >>>>>> >>>>>> So i exported to a 4 collumn text file with "X" "Y" "Z" "AMPLITUDE", >>>>>> imported in paraview, table to structured grid points filter, and used the >>>>>> scalar variable amplitude to color the object >>>>>> >>>>>> Hope it helped! >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> 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 Mon Mar 16 18:14:11 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 16 Mar 2015 22:14:11 +0000 Subject: [Paraview] Trace recorder and presets (color table) Message-ID: <23e410a9b2c245ca8c1f8a8928329688@ES05AMSNLNT.srn.sandia.gov> I have a user that needs to change the ParaView preset from default (cool to warm) to another ParaView preset (Blue to Red Rainbow). He wants to do this in a python trace. So, he used the trace recorder to record his steps. Unfortunately, changing presets is not recorded with the trace recorder. I have written this issue up as bug number http://www.paraview.org/Bug/view.php?id=15116, but need to give the user the code that would have/ should have been produced. Does anyone have the python code that changes presets? Thanks all! Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Mon Mar 16 18:45:18 2015 From: bloring at lbl.gov (Burlen Loring) Date: Mon, 16 Mar 2015 15:45:18 -0700 Subject: [Paraview] Trace recorder and presets (color table) In-Reply-To: <23e410a9b2c245ca8c1f8a8928329688@ES05AMSNLNT.srn.sandia.gov> References: <23e410a9b2c245ca8c1f8a8928329688@ES05AMSNLNT.srn.sandia.gov> Message-ID: <55075CFE.30106@lbl.gov> Hi Alan, You can use the AssignLookupTable function to reference builtin lookup tables by name. For example see code between # marks below. There are a few other conveniences for working with the builtin tables as well, see this recipe w = Wavelet() w_rep = Show(w) w_rep.Representation = 'Surface' # w_rep.ColorArrayName = 'RTData' w_arr = w.PointData.GetArray('RTData') w_rep.LookupTable = AssignLookupTable(w_arr, 'Rainbow Blended White') # Render().ResetCamera() Burlen On 03/16/2015 03:14 PM, Scott, W Alan wrote: > I have a user that needs to change the ParaView preset from default > (cool to warm) to another ParaView preset (Blue to Red Rainbow). He > wants to do this in a python trace. So, he used the trace recorder to > record his steps. Unfortunately, changing presets is not recorded with > the trace recorder. > I have written this issue up as bug number > _http://www.paraview.org/Bug/view.php?id=15116_, but need to give the > user the code that would have/ should have been produced. Does anyone > have the python code that changes presets? > Thanks all! > 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 ronald.fowler at stfc.ac.uk Mon Mar 16 19:08:50 2015 From: ronald.fowler at stfc.ac.uk (ronald.fowler at stfc.ac.uk) Date: Mon, 16 Mar 2015 23:08:50 +0000 Subject: [Paraview] Trace recorder and presets (color table) In-Reply-To: <23e410a9b2c245ca8c1f8a8928329688@ES05AMSNLNT.srn.sandia.gov> References: <23e410a9b2c245ca8c1f8a8928329688@ES05AMSNLNT.srn.sandia.gov> Message-ID: <398242C76E3D3740BA94E23089B34E2C9EC06EC8@EXCHMBX03.fed.cclrc.ac.uk> Are you sure that is a wise thing to do in the first place, at least the bit about making "rainbow" the default? See e.g.: https://eagereyes.org/basics/rainbow-color-map ________________________________ From: ParaView [paraview-bounces at paraview.org] on behalf of Scott, W Alan [wascott at sandia.gov] Sent: 16 March 2015 22:14 To: paraview at paraview.org Subject: [Paraview] Trace recorder and presets (color table) I have a user that needs to change the ParaView preset from default (cool to warm) to another ParaView preset (Blue to Red Rainbow). He wants to do this in a python trace. So, he used the trace recorder to record his steps. Unfortunately, changing presets is not recorded with the trace recorder. I have written this issue up as bug number http://www.paraview.org/Bug/view.php?id=15116, but need to give the user the code that would have/ should have been produced. Does anyone have the python code that changes presets? Thanks all! Alan From wascott at sandia.gov Mon Mar 16 19:46:45 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 16 Mar 2015 23:46:45 +0000 Subject: [Paraview] [EXTERNAL] RE: Trace recorder and presets (color table) In-Reply-To: <398242C76E3D3740BA94E23089B34E2C9EC06EC8@EXCHMBX03.fed.cclrc.ac.uk> References: <23e410a9b2c245ca8c1f8a8928329688@ES05AMSNLNT.srn.sandia.gov> <398242C76E3D3740BA94E23089B34E2C9EC06EC8@EXCHMBX03.fed.cclrc.ac.uk> Message-ID: Ron, Three answers. * My user is only trying to use rainbow on specific runs, not as the default color map for all time. * I already gave that lecture to the user. I always ask what are your goals? To create informative accurate simulations that don't give color blind folks fits, or eye candy? For me (making cool movies), it's eye candy. For my users (analysts trying to do real work), it's accurate information. * My goal is to support my user. If said user wants rainbow, I tell them how to do rainbow. :-) Thanks for the reminder, Alan -----Original Message----- From: ronald.fowler at stfc.ac.uk [mailto:ronald.fowler at stfc.ac.uk] Sent: Monday, March 16, 2015 5:09 PM To: Scott, W Alan; paraview at paraview.org Subject: [EXTERNAL] RE: Trace recorder and presets (color table) Are you sure that is a wise thing to do in the first place, at least the bit about making "rainbow" the default? See e.g.: https://eagereyes.org/basics/rainbow-color-map ________________________________ From: ParaView [paraview-bounces at paraview.org] on behalf of Scott, W Alan [wascott at sandia.gov] Sent: 16 March 2015 22:14 To: paraview at paraview.org Subject: [Paraview] Trace recorder and presets (color table) I have a user that needs to change the ParaView preset from default (cool to warm) to another ParaView preset (Blue to Red Rainbow). He wants to do this in a python trace. So, he used the trace recorder to record his steps. Unfortunately, changing presets is not recorded with the trace recorder. I have written this issue up as bug number http://www.paraview.org/Bug/view.php?id=15116, but need to give the user the code that would have/ should have been produced. Does anyone have the python code that changes presets? Thanks all! Alan From mshoji-tky at umin.ac.jp Tue Mar 17 00:04:52 2015 From: mshoji-tky at umin.ac.jp (Masaaki SHOJIMA) Date: Tue, 17 Mar 2015 13:04:52 +0900 Subject: [Paraview] Fwd: Gradient of Unstructed dataset In-Reply-To: References: Message-ID: Hi Berk, I appreciate your kindness Here, I attaches the data. Compare Gradient.pdf (252KB) A calculated field by SC/Tetra solver is uploaded in Dropbox. (Calc.zip) Please download the data. It contains FLD format for SC/Tetra post and CGNS format for Ensight and Paraview. https://www.dropbox.com/s/5fpeu1qwhyzjn5u/Calc.zip?dl=0 (1) I calculated the flow and the pressure in a simple cylinder for a test ( diameter 0.005m, length 0.01m). Plug flow at inlet with 0.03 m/s. (2) Data were transfered to Ensight and Paraview in CGNS format. (3) Pressure was mapped on the surface and compared between SC/Tetra post, Ensight and Paraview. All application provided same results. (4) Gradient (pressure) was calculated in each post and z-component of Gradient (pressure) was visualized with same colored contour. Only paraview provided a different image because the computed gradients in paraview had half values compared to SC/Tetra post and Ensight. (5) Gradient (velocity-X) was also calculated in each post and the X-component of Grad (velocity-X) was visualized. Same results as shown in 4. Thanks a lot. Masaaki -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Compare Gradient.pdf Type: application/pdf Size: 257912 bytes Desc: not available URL: From mickey.phy at gmail.com Tue Mar 17 03:02:49 2015 From: mickey.phy at gmail.com (Mickael Philit) Date: Tue, 17 Mar 2015 08:02:49 +0100 Subject: [Paraview] Fwd: Gradient of Unstructed dataset In-Reply-To: References: Message-ID: <5507D199.5040505@gmail.com> Hello, sorry to intrude, I think the problem may come from the CGNS loader of ParaView. When using the CGNS plugin from ParaView development version, you get the same picture as Ensight. My two cents Mickael On 17/03/2015 05:04, Masaaki SHOJIMA wrote: > Hi Berk, > > I appreciate your kindness > > Here, I attaches the data. > Compare Gradient.pdf (252KB) > > A calculated field by SC/Tetra solver is uploaded in Dropbox. (Calc.zip) > Please download the data. It contains FLD format for SC/Tetra post and > CGNS format for Ensight and Paraview. > https://www.dropbox.com/s/5fpeu1qwhyzjn5u/Calc.zip?dl=0 > > (1) I calculated the flow and the pressure in a simple cylinder for a > test ( diameter 0.005m, length 0.01m). Plug flow at inlet with 0.03 m/s. > > (2) Data were transfered to Ensight and Paraview in CGNS format. > > (3) Pressure was mapped on the surface and compared between SC/Tetra > post, Ensight and Paraview. All application provided same results. > > (4) Gradient (pressure) was calculated in each post and z-component of > Gradient (pressure) was visualized with same colored contour. Only > paraview provided a different image because the computed gradients in > paraview had half values compared to SC/Tetra post and Ensight. > > (5) Gradient (velocity-X) was also calculated in each post and the > X-component of Grad (velocity-X) was visualized. Same results as shown > in 4. > > > Thanks a lot. > > Masaaki > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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 gaspare.argento at gmail.com Tue Mar 17 04:37:11 2015 From: gaspare.argento at gmail.com (Gaspare Argento) Date: Tue, 17 Mar 2015 09:37:11 +0100 Subject: [Paraview] [EXTERNAL] PROBLEM IMPORTING ENSIGHT SOS FILE In-Reply-To: <5a805951bc3a40a780d8638552585a81@ES05AMSNLNT.srn.sandia.gov> References: <5a805951bc3a40a780d8638552585a81@ES05AMSNLNT.srn.sandia.gov> Message-ID: Dear Alan, thank you for your time. The userguide you linked in your mail was interesting but it seems that the problem is correlated to Paraview, because the *.sos file format I used was correct. Just for a general knowledge: for some reason Paraview search the case files in the same directory of the sos file, independently from the path you write in the *sos file (it is not important what path to case file you write, I tried totally wrong path but the error was the same). Ensight write his data with the following structure: \general_path\3D_EnSight\*sos \general_path\3D_EnSight\DOM_0\*case \general_path\3D_EnSight\DOM_1\*case \general_path\3D_EnSight\DOM_n\*case Because the case files are stored in DOM_x folders, Paraview doens't find them. You have to put all the content of the DOM_x folders one step up, at the same path of the *sos file. Now it works. I hope it could be useful for someone. Gaspare 2015-03-13 20:34 GMT+01:00 Scott, W Alan : > Gaspare, > > I tried opening your .case files with ParaView and EnSight, and they seem OK. I then tried opening the .sos file, and had issues - even after removing the site specific information. I had issues with ParaView, and it crashed EnSight. Thus, I believe the issue is with the .sos file. I am not an expert on .sos files at all - so let me aim you at the online documentation. By doing a google search, I found the following: http://www3.ensight.com/EnSight10_Docs/UserManual.pdf. Look in chapter 9.8, SOS file formats. > > That's about all I know... > > Alan > > -----Original Message----- > From: Gaspare Argento [mailto:gaspare.argento at gmail.com] > Sent: Tuesday, March 10, 2015 5:04 AM > To: Scott, W Alan > Cc: paraview at paraview.org > Subject: Re: [EXTERNAL] [Paraview] PROBLEM IMPORTING ENSIGHT SOS FILE > > Hi Scott, > > please find attached a case test that was launched on two cores. In the first folder you can find the *.sos file, manually edited with the correct machine name and the absolute path to the Ensight server (I'm not sure it is the correct file to use); in the folders DOM_0 and > DOM_1 you can find the *.case files (I can load them one by one correctly). > > These files are written by AVL Fire. Because Paraview doesn't support the native format of FIRE for 3D Results, I ask to the software to write them also in the Ensight format. > > Thanks for your support, > > Gaspare > > 2015-03-09 22:27 GMT+01:00 Scott, W Alan : >> I believe my thoughts below were wrong. Ignore them. >> >> Could you give us a trivial dataset that shows this issue? >> >> Thanks, >> >> Alan >> >> -----Original Message----- >> From: Gaspare Argento [mailto:gaspare.argento at gmail.com] >> Sent: Friday, March 06, 2015 12:47 AM >> To: Scott, W Alan >> Cc: paraview at paraview.org >> Subject: Re: [EXTERNAL] [Paraview] PROBLEM IMPORTING ENSIGHT SOS FILE >> >> Hi Scott, >> >> thanks for answering. >> >> I'm sorry but I didn't understand exactly what do you mean: could you please explain it better? Did you ask me to attach the .sos file? >> >> Thanks, >> >> Gaspare >> >> 2015-03-05 18:39 GMT+01:00 Scott, W Alan : >>> I just opened an .sos file, with a 16 file dataset, with ParaView 4.3.1. Worked fine. Linux, local server. >>> >>> * I wonder if you have a problem with your SOS file. >>> * Mind posting a/the dataset? >>> >>> Alan >>> >>> -----Original Message----- >>> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of >>> Gaspare Argento >>> Sent: Thursday, March 05, 2015 2:20 AM >>> To: paraview at paraview.org >>> Subject: [EXTERNAL] [Paraview] PROBLEM IMPORTING ENSIGHT SOS FILE >>> >>> Hi everybody, >>> >>> I have a problem when importing an Ensight .sos file in Paraview. >>> >>> Loading the .sos file I get the following message (I attach only the lines about the first *.case file, because these are repeated for all *case files listed in the .sos): >>> ===================================================================== >>> = ==================================================== >>> >>> ERROR: In >>> C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSight >>> R >>> eader.cxx, >>> line 340 >>> >>> vtkPGenericEnSightReader (000000000DC5E6E0): Unable to open file: >>> J:\SERVER\CALC\VOF_TEST\Calculation\VOF_TEST\3D_EnSight\/VOF_TEST_DOM >>> _ >>> 0.case >>> >>> >>> >>> >>> >>> ERROR: In >>> C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSight >>> R >>> eader.cxx, >>> line 340 >>> >>> vtkPGenericEnSightReader (000000000DC5E6E0): Unable to open file: >>> J:\SERVER\CALC\VOF_TEST\Calculation\VOF_TEST\3D_EnSight\/VOF_TEST_DOM >>> _ >>> 0.case >>> >>> >>> >>> >>> >>> ERROR: In >>> C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSight >>> R >>> eader.cxx, >>> line 811 >>> >>> vtkPGenericEnSightReader (000000000DC5E6E0): Error determining >>> EnSightVersion >>> >>> >>> >>> >>> >>> ERROR: In >>> C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExe >>> c >>> utive.cxx, >>> line 784 >>> >>> vtkCompositeDataPipeline (000000000DBF33A0): Algorithm >>> vtkPGenericEnSightReader(000000000DC5E6E0) returned failure for >>> request: vtkInformation (000000000DEC2F60) >>> >>> Debug: Off >>> >>> Modified Time: 160501 >>> >>> Reference Count: 1 >>> >>> Registered Events: (none) >>> >>> Request: REQUEST_INFORMATION >>> >>> ALGORITHM_AFTER_FORWARD: 1 >>> >>> FORWARD_DIRECTION: 0 >>> >>> >>> >>> >>> >>> ERROR: In >>> C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\VTKExtensions\Defau >>> l t\vtkPVEnSightMasterServerReader2.cxx, >>> line 255 >>> >>> vtkPVEnSightMasterServerReader2 (0000000018693C90): Error reading case file on at least one node. >>> >>> >>> >>> >>> >>> ERROR: In >>> C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExe >>> c >>> utive.cxx, >>> line 784 >>> >>> vtkPVCompositeDataPipeline (0000000017BEA7E0): Algorithm >>> vtkPVEnSightMasterServerReader2(0000000018693C90) returned failure >>> for >>> request: vtkInformation (0000000016F654A0) >>> >>> Debug: Off >>> >>> Modified Time: 6920520 >>> >>> Reference Count: 1 >>> >>> Registered Events: (none) >>> >>> Request: REQUEST_INFORMATION >>> >>> ALGORITHM_AFTER_FORWARD: 1 >>> >>> FORWARD_DIRECTION: 0 >>> >>> ===================================================================== >>> = ==================================================== >>> >>> >>> >>> Below you can find an extract of the loaded .sos file (only the lines relative to the first server): >>> ===================================================================== >>> = ==================================================== >>> >>> # >>> >>> # Example Server-of-server case file >>> >>> # parts in <> have to be filled in by the user >>> >>> # >>> >>> FORMAT >>> >>> type: master_server gold >>> >>> SERVERS >>> >>> number of servers: 64 >>> >>> #Server 1 >>> >>> machine id: MACHINE_NAME >>> >>> executable: >>> >>> casefile: >>> J:/SERVER/CALC/VOF_TEST/Calculation/VOF_TEST/3D_EnSight/DOM_0/VOF_TES >>> T >>> _DOM_0.case >>> >>> ===================================================================== >>> = ==================================================== >>> >>> >>> >>> If I load the *.case files one by one I have no problem. >>> >>> >>> >>> Thanks for your support >>> >>> Gaspare >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> 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 livia.barazzetti at istb.unibe.ch Tue Mar 17 05:23:08 2015 From: livia.barazzetti at istb.unibe.ch (livia.barazzetti at istb.unibe.ch) Date: Tue, 17 Mar 2015 09:23:08 +0000 Subject: [Paraview] Manage Links from Python Script Message-ID: Hello, I would like to create automatically a property link (like what you do in the link manager) in a macro. I tried tracing but I did not get anything for it. Is there any python command for property links (Paraview 4.3.1)? Thanks Best regards Liva Barazzetti -------------- next part -------------- An HTML attachment was scrubbed... URL: From nenasantos at hotmail.com Tue Mar 17 05:27:19 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Tue, 17 Mar 2015 09:27:19 +0000 Subject: [Paraview] Add logo to animation paraview script In-Reply-To: References: , Message-ID: Dear all,What are the steps to include a image, as logo, in a corner of an animated script. Basicaly I want to know what is the code that allows to include image as logo in my animated script. I do not want image as background but image as logo, placed in one of the corners of my figure. Kind regards Madalena _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 mshoji-tky at umin.ac.jp Tue Mar 17 06:19:46 2015 From: mshoji-tky at umin.ac.jp (Masaaki SHOJIMA) Date: Tue, 17 Mar 2015 19:19:46 +0900 Subject: [Paraview] Fwd: Gradient of Unstructed dataset In-Reply-To: <5507D199.5040505@gmail.com> References: <5507D199.5040505@gmail.com> Message-ID: Hi Mickael, I like to try it. Where or How can I get the file of CGNS plugin ? I am using Paraview 4.3.1 for windows (may be the latest one). I am not familiar with Linux or Unix... But I try to comple the source code... Thank you so much teaching me. Masaaki 2015-03-17 16:02 GMT+09:00 Mickael Philit : > Hello, > > sorry to intrude, > I think the problem may come from the CGNS loader of ParaView. > When using the CGNS plugin from ParaView development version, you get the > same picture as Ensight. > My two cents > > Mickael > > > On 17/03/2015 05:04, Masaaki SHOJIMA wrote: > > Hi Berk, > > I appreciate your kindness > > Here, I attaches the data. > Compare Gradient.pdf (252KB) > > A calculated field by SC/Tetra solver is uploaded in Dropbox. (Calc.zip) > Please download the data. It contains FLD format for SC/Tetra post and > CGNS format for Ensight and Paraview. > https://www.dropbox.com/s/5fpeu1qwhyzjn5u/Calc.zip?dl=0 > > (1) I calculated the flow and the pressure in a simple cylinder for a test > ( diameter 0.005m, length 0.01m). Plug flow at inlet with 0.03 m/s. > > (2) Data were transfered to Ensight and Paraview in CGNS format. > > (3) Pressure was mapped on the surface and compared between SC/Tetra post, > Ensight and Paraview. All application provided same results. > > (4) Gradient (pressure) was calculated in each post and z-component of > Gradient (pressure) was visualized with same colored contour. Only paraview > provided a different image because the computed gradients in paraview had > half values compared to SC/Tetra post and Ensight. > > (5) Gradient (velocity-X) was also calculated in each post and the > X-component of Grad (velocity-X) was visualized. Same results as shown in 4. > > > Thanks a lot. > > Masaaki > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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 mshoji-tky at umin.ac.jp Tue Mar 17 06:27:27 2015 From: mshoji-tky at umin.ac.jp (Masaaki SHOJIMA) Date: Tue, 17 Mar 2015 19:27:27 +0900 Subject: [Paraview] Fwd: Gradient of Unstructed dataset In-Reply-To: <5507D199.5040505@gmail.com> References: <5507D199.5040505@gmail.com> Message-ID: Hi, Michael, I found a web-page regarding the CGNS reader, in which you are making important comments. http://comments.gmane.org/gmane.comp.science.paraview.user/23957 I have to wait for the next version, is it right? Thanks Masaaki 2015-03-17 16:02 GMT+09:00 Mickael Philit : > Hello, > > sorry to intrude, > I think the problem may come from the CGNS loader of ParaView. > When using the CGNS plugin from ParaView development version, you get the > same picture as Ensight. > My two cents > > Mickael > > > On 17/03/2015 05:04, Masaaki SHOJIMA wrote: > > Hi Berk, > > I appreciate your kindness > > Here, I attaches the data. > Compare Gradient.pdf (252KB) > > A calculated field by SC/Tetra solver is uploaded in Dropbox. (Calc.zip) > Please download the data. It contains FLD format for SC/Tetra post and > CGNS format for Ensight and Paraview. > https://www.dropbox.com/s/5fpeu1qwhyzjn5u/Calc.zip?dl=0 > > (1) I calculated the flow and the pressure in a simple cylinder for a test > ( diameter 0.005m, length 0.01m). Plug flow at inlet with 0.03 m/s. > > (2) Data were transfered to Ensight and Paraview in CGNS format. > > (3) Pressure was mapped on the surface and compared between SC/Tetra post, > Ensight and Paraview. All application provided same results. > > (4) Gradient (pressure) was calculated in each post and z-component of > Gradient (pressure) was visualized with same colored contour. Only paraview > provided a different image because the computed gradients in paraview had > half values compared to SC/Tetra post and Ensight. > > (5) Gradient (velocity-X) was also calculated in each post and the > X-component of Grad (velocity-X) was visualized. Same results as shown in 4. > > > Thanks a lot. > > Masaaki > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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 arctica1963 at gmail.com Tue Mar 17 07:56:33 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Tue, 17 Mar 2015 11:56:33 +0000 Subject: [Paraview] SEG-Y seismic data loading In-Reply-To: References: Message-ID: There is an updated version of the code here: https://github.com/rob-smallshire/segpy I only have 64 bit Python, and this needs 32 bit PyGtk - anyway the route for reading the data is certainly there. The one issue we would have is that seismic data can be both in Time (Z axis) or depth, depending on whether it has been depth converted. In terms of attributes to deal with, there could be any number of components, including velocity, amplitude, density etc. but most people just view a colour-shaded amplitude image for interpretation. The wiggle trace is fine at a smaller scale. As an import, it would be necessary to be able to either read the time of Z-scale or define manually. On 16 March 2015 at 20:12, Berk Geveci wrote: > A quick Google search yields a few Python libraries such as > > http://segymat.sourceforge.net/segypy/ > > Has anyone experimented with any of those? Once someone can figure out how > to bring the data in, we can figure out how to visualize it. > > -berk > > On Sun, Mar 8, 2015 at 9:50 AM, Lester Anderson > wrote: > >> The other workaround is to have an image of the seismic line that can be >> georeferenced for loading into Paraview. However, this requires a seismic >> viewer capable of exporting a good quality image and not all do (SeiSee is >> quite good). Obviously things get a little complex when having to convert >> from time to depth, but not so if you are dealing with Z as the time >> coordinate. >> >> Is there a georeference filter/tool in ParaView? >> >> Cheers >> >> On 6 March 2015 at 20:55, L?o Pessanha >> wrote: >> >>> Putting a SEG-Y data in a more direct way is still in the escope of one >>> of the projects that i am working on. I did some research not a long time >>> ago and i found that Richard Strelitz wrote a paraview plugin for reading >>> SEG-Y data at LANL but he gave up since there was no easy way of retaining >>> the concept of a trace that is so essential to seismic data at the time he >>> was still trying. He said that would for some of the files he created but >>> we lost contact. >>> >>> Maybe he could help, and instead of starting from zero, maybe there`s a >>> way to continue his work and save some time. >>> >>> For me it would be a really really great tool to have in paraview! >>> >>> With the proper guidance, i would really like to help(or try to help) ! >>> >>> 2015-03-06 11:58 GMT-03:00 David E DeMarle : >>> >>> +1, this would be great to have in ParaView. >>>> >>>> Just need someone out there to find the time and or funding to >>>> implement it. >>>> >>>> It could make a nice google summer of code effort if there is a student >>>> who is interested in the topic. >>>> http://www.kitware.com/blog/home/post/857 >>>> >>>> >>>> David E DeMarle >>>> Kitware, Inc. >>>> R&D Engineer >>>> 21 Corporate Drive >>>> Clifton Park, NY 12065-8662 >>>> Phone: 518-881-4909 >>>> >>>> On Fri, Mar 6, 2015 at 7:21 AM, Lester Anderson >>>> wrote: >>>> >>>>> This is definitely an import filter that would make ParaView more >>>>> widely used, particularly in industry. Even doing as suggested by Leo, of >>>>> reading the coordinates and extracting the amplitude would still be useful >>>>> when viewing the data in 3D. >>>>> >>>>> Perhaps this will be addressed in a future release, but I know this >>>>> has been asked for some years back I believe. >>>>> >>>>> On 5 March 2015 at 22:14, Lester Anderson >>>>> wrote: >>>>> >>>>>> Hi Leo, >>>>>> >>>>>> Thanks for the suggestions. What software did you use to export the >>>>>> data? >>>>>> >>>>>> Cheers >>>>>> Lester >>>>>> >>>>>> On 5 March 2015 at 19:18, L?o Pessanha >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I would like to apologize, i do not know how to answer a question in >>>>>>> the mailing list correctly, i think the way i am doing it right now is >>>>>>> going to appear as a new question >>>>>>> >>>>>>> There is no easy way of doing it, to see SEG-Y data in paraview, i >>>>>>> used another software to export the data to ASCII txt >>>>>>> >>>>>>> So i exported to a 4 collumn text file with "X" "Y" "Z" "AMPLITUDE", >>>>>>> imported in paraview, table to structured grid points filter, and used the >>>>>>> scalar variable amplitude to color the object >>>>>>> >>>>>>> Hope it helped! >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> 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 dkxls23 at gmail.com Tue Mar 17 08:09:22 2015 From: dkxls23 at gmail.com (dkxls23 at gmail.com) Date: Tue, 17 Mar 2015 12:09:22 +0000 Subject: [Paraview] Fwd: Gradient of Unstructed dataset In-Reply-To: References: <5507D199.5040505@gmail.com> Message-ID: You could test it with the nighly builds from the dashboard. That way you don't have to compile anything. You can find more information here: http://www.paraview.org/Wiki/ParaView_Nightly_Binaries -Armin On Tue Mar 17 12:27:27 2015 GMT+0200, Masaaki SHOJIMA wrote: > Hi, Michael, > > I found a web-page regarding the CGNS reader, in which you are making > important comments. > http://comments.gmane.org/gmane.comp.science.paraview.user/23957 > > I have to wait for the next version, is it right? > > Thanks > > Masaaki > > 2015-03-17 16:02 GMT+09:00 Mickael Philit : > > > Hello, > > > > sorry to intrude, > > I think the problem may come from the CGNS loader of ParaView. > > When using the CGNS plugin from ParaView development version, you get the > > same picture as Ensight. > > My two cents > > > > Mickael > > > > > > On 17/03/2015 05:04, Masaaki SHOJIMA wrote: > > > > Hi Berk, > > > > I appreciate your kindness > > > > Here, I attaches the data. > > Compare Gradient.pdf (252KB) > > > > A calculated field by SC/Tetra solver is uploaded in Dropbox. (Calc.zip) > > Please download the data. It contains FLD format for SC/Tetra post and > > CGNS format for Ensight and Paraview. > > https://www.dropbox.com/s/5fpeu1qwhyzjn5u/Calc.zip?dl=0 > > > > (1) I calculated the flow and the pressure in a simple cylinder for a test > > ( diameter 0.005m, length 0.01m). Plug flow at inlet with 0.03 m/s. > > > > (2) Data were transfered to Ensight and Paraview in CGNS format. > > > > (3) Pressure was mapped on the surface and compared between SC/Tetra post, > > Ensight and Paraview. All application provided same results. > > > > (4) Gradient (pressure) was calculated in each post and z-component of > > Gradient (pressure) was visualized with same colored contour. Only paraview > > provided a different image because the computed gradients in paraview had > > half values compared to SC/Tetra post and Ensight. > > > > (5) Gradient (velocity-X) was also calculated in each post and the > > X-component of Grad (velocity-X) was visualized. Same results as shown in 4. > > > > > > Thanks a lot. > > > > Masaaki > > > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/paraview > > > > > > > -- Sent from my Jolla From rohitnarurkar at gmail.com Tue Mar 17 08:37:15 2015 From: rohitnarurkar at gmail.com (Rohit Narurkar) Date: Tue, 17 Mar 2015 18:07:15 +0530 Subject: [Paraview] Fluid Flow Simulation in ParaView Message-ID: Hello I wish to simulate fluid flow using ParaView. I have 1000 .vtk files for the 1000 time steps. I have attached along with this mail one of the .vtk files. When I open this collection in ParaView, and change the 'coloring' to the velocity name I have given i.e. "VecVelocity" as you can see in the sample .vtk file. There is another option to its right which offers 'magnitude', 'x', 'y' and 'z'. But there are some points with negative velocities and ParaView is only considering the magnitude (hence positive). I wish to display even the negative values. How do I do that? Any help would be great! Thank you! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: vel0010.vtk Type: application/octet-stream Size: 92313 bytes Desc: not available URL: From berk.geveci at kitware.com Tue Mar 17 09:01:51 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Tue, 17 Mar 2015 09:01:51 -0400 Subject: [Paraview] Fwd: Gradient of Unstructed dataset In-Reply-To: References: <5507D199.5040505@gmail.com> Message-ID: Hi Masaaki, I will hold off testing on my end until you have a chance to test with nightly binaries. Please let us know how it goes. Regards, -berk On Tue, Mar 17, 2015 at 8:09 AM, wrote: > You could test it with the nighly builds from the dashboard. That way you > don't have to compile anything. > > You can find more information here: > http://www.paraview.org/Wiki/ParaView_Nightly_Binaries > > -Armin > > > > On Tue Mar 17 12:27:27 2015 GMT+0200, Masaaki SHOJIMA wrote: > > Hi, Michael, > > > > I found a web-page regarding the CGNS reader, in which you are making > > important comments. > > http://comments.gmane.org/gmane.comp.science.paraview.user/23957 > > > > I have to wait for the next version, is it right? > > > > Thanks > > > > Masaaki > > > > 2015-03-17 16:02 GMT+09:00 Mickael Philit : > > > > > Hello, > > > > > > sorry to intrude, > > > I think the problem may come from the CGNS loader of ParaView. > > > When using the CGNS plugin from ParaView development version, you get > the > > > same picture as Ensight. > > > My two cents > > > > > > Mickael > > > > > > > > > On 17/03/2015 05:04, Masaaki SHOJIMA wrote: > > > > > > Hi Berk, > > > > > > I appreciate your kindness > > > > > > Here, I attaches the data. > > > Compare Gradient.pdf (252KB) > > > > > > A calculated field by SC/Tetra solver is uploaded in Dropbox. > (Calc.zip) > > > Please download the data. It contains FLD format for SC/Tetra post and > > > CGNS format for Ensight and Paraview. > > > https://www.dropbox.com/s/5fpeu1qwhyzjn5u/Calc.zip?dl=0 > > > > > > (1) I calculated the flow and the pressure in a simple cylinder for a > test > > > ( diameter 0.005m, length 0.01m). Plug flow at inlet with 0.03 m/s. > > > > > > (2) Data were transfered to Ensight and Paraview in CGNS format. > > > > > > (3) Pressure was mapped on the surface and compared between SC/Tetra > post, > > > Ensight and Paraview. All application provided same results. > > > > > > (4) Gradient (pressure) was calculated in each post and z-component of > > > Gradient (pressure) was visualized with same colored contour. Only > paraview > > > provided a different image because the computed gradients in paraview > had > > > half values compared to SC/Tetra post and Ensight. > > > > > > (5) Gradient (velocity-X) was also calculated in each post and the > > > X-component of Grad (velocity-X) was visualized. Same results as shown > in 4. > > > > > > > > > Thanks a lot. > > > > > > Masaaki > > > > > > > > > > > > > > > _______________________________________________ > > > Powered by www.kitware.com > > > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > > > > > > > > > -- > Sent from my Jolla > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 alyckegaard at xnovotech.com Tue Mar 17 09:03:56 2015 From: alyckegaard at xnovotech.com (Allan Lyckegaard) Date: Tue, 17 Mar 2015 14:03:56 +0100 Subject: [Paraview] Get selection of input in Python programmable filter Message-ID: <1BDD6D81-9F41-4CEE-97A8-A8C2840B873F@xnovotech.com> Hi Paraview users, I have been searching this list and the documentation but without luck. I am working on a python programmable filter with two vtkimagedata as inputs. In the paraview GUI, both input vtkimagedata has an associated selection picked by ?Select Points With Polygon?. How do I in the python programmable filter find out what points have been selected in the two input vtkimagedata? /Allan From oshima at eng.niigata-u.ac.jp Tue Mar 17 10:15:06 2015 From: oshima at eng.niigata-u.ac.jp (Takuya OSHIMA) Date: Tue, 17 Mar 2015 23:15:06 +0900 Subject: [Paraview] Japanese translation of the ParaView Tutorial version 4.2 is available Message-ID: <1426601706963285.1675068776@camail01.cais.niigata-u.ac.jp> Hi, We are pleased to announce the availability of the Japanese translation of the ParaView Tutorial version 4.2 by Kenneth Moreland. Download from the Translations section of http://www.paraview.org/Wiki/The_ParaView_Tutorial . It is an update after more than four years since the last release for version 3.8. We would like to thank the original author for the excellent tutorial and for continuously providing the LaTeX source files on GitHub. Also, the translators are grateful to the Open CAE Society of Japan (http://www.opencae.jp/) for funding the translation project. Takuya From dave.demarle at kitware.com Tue Mar 17 10:20:14 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 17 Mar 2015 10:20:14 -0400 Subject: [Paraview] Japanese translation of the ParaView Tutorial version 4.2 is available In-Reply-To: <1426601706963285.1675068776@camail01.cais.niigata-u.ac.jp> References: <1426601706963285.1675068776@camail01.cais.niigata-u.ac.jp> Message-ID: ????????????? Doumo arigatou gozaimasu! David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Mar 17, 2015 at 10:15 AM, Takuya OSHIMA wrote: > Hi, > > We are pleased to announce the availability of the Japanese > translation of the ParaView Tutorial version 4.2 by Kenneth > Moreland. Download from the Translations section of > http://www.paraview.org/Wiki/The_ParaView_Tutorial . > > It is an update after more than four years since the last > release for version 3.8. > > We would like to thank the original author for the excellent > tutorial and for continuously providing the LaTeX source files on > GitHub. Also, the translators are grateful to the Open CAE > Society of Japan (http://www.opencae.jp/) for funding the > translation project. > > Takuya > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Tue Mar 17 11:00:21 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Tue, 17 Mar 2015 15:00:21 +0000 Subject: [Paraview] Japanese translation of the ParaView Tutorial version 4.2 is available Message-ID: Very nice! Thanks so much for taking the time to do this. -Ken On 3/17/15, 8:15 AM, "Takuya OSHIMA" wrote: >Hi, > >We are pleased to announce the availability of the Japanese >translation of the ParaView Tutorial version 4.2 by Kenneth >Moreland. Download from the Translations section of >http://www.paraview.org/Wiki/The_ParaView_Tutorial . > >It is an update after more than four years since the last >release for version 3.8. > >We would like to thank the original author for the excellent >tutorial and for continuously providing the LaTeX source files on >GitHub. Also, the translators are grateful to the Open CAE >Society of Japan (http://www.opencae.jp/) for funding the >translation project. > >Takuya >_______________________________________________ >Powered by www.kitware.com > >Visit other Kitware open-source projects at >http://www.kitware.com/opensource/opensource.html > >Please keep messages on-topic and check the ParaView Wiki at: >http://paraview.org/Wiki/ParaView > >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 felipe.bordeu at ec-nantes.fr Tue Mar 17 11:06:30 2015 From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu) Date: Tue, 17 Mar 2015 16:06:30 +0100 Subject: [Paraview] ParaView and Matlab lovers Parula ColorScale Message-ID: <550842F6.7050207@ec-nantes.fr> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi to all, Attached you can find the Parula coloscale from the last Matlab release. Felipe - -- Felipe Bordeu Weldt Ing?nieur de Recherche - ------------------------------------- T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS 6183 ?cole Centrale Nantes 1 Rue de La No?, 44321 Nantes, FRANCE - ------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVCELyAAoJEE/fMfNgU9/D2zEIAJtQFgOUO+8UgQNwGNRKsagi jJNUuF4Z3P+lE55OvrT/YNJVUJtQYndeTv8EtFwq0O03sF014DQJn6koPRnVvnVB x3ITAmwtTUGpUcgl08k6qIB2T77LlEWvjIZLR/Uzj+dQ+qHtTUSIMXxOsHcKyvMR 27JiyKdCk5t+iAxHNqkdNXiHRY4tXNAgi8cqZYwIPLo8d4N+Z4OVIz+bJy7xP0EQ WXk7nwAxKsqWoktozsg/+LiZR6YCU+RI5CWcucCQ3D0+tdieO6rSikgkVBYPpWBg nFTx6fZx+YH27h75R6pcda+lOOFtubFr4cNHeiWz9zyNBXe85OvGXdS4aYEO/kg= =C+Se -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: parula.xml Type: text/xml Size: 4231 bytes Desc: not available URL: From pabosle at sandia.gov Tue Mar 17 13:40:19 2015 From: pabosle at sandia.gov (Bosler, Peter Andrew) Date: Tue, 17 Mar 2015 17:40:19 +0000 Subject: [Paraview] Headlight in 4.3.1? In-Reply-To: References: Message-ID: Good morning, I have just upgraded to Paraview 4.3.1 from 4.10, because I was unable to change the specularity of a surface in 4.1 (this is fixed in 4.3, which is nice). But now I can't find the "headlight" option that used to be in 4.1's render view options. Without it, the images I need to produce for a publication look dark and washed out. Could you point me toward the lighting tool in 4.3 that lets me turn on a headlight? Thanks for your time, Pete Bosler ----- Peter Bosler, PhD John von Neumann Fellow Sandia National Laboratories Multiphysics Applications (01446) pabosle at sandia.gov (505) 845 - 0427 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Mar 17 13:49:35 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 17 Mar 2015 13:49:35 -0400 Subject: [Paraview] Headlight in 4.3.1? In-Reply-To: References: Message-ID: Peter, You can find the headlight by looking in the Properties panel under the Lights section. This is an advanced setting, so click the gear icon in the Properties panel to expose it. Under the Lights section in the panel (it's towards the bottom), click the "Edit" button and select "Additional Headlight" in the Lights Editor dialog that pops up. Hope that helps, Cory On Tue, Mar 17, 2015 at 1:40 PM, Bosler, Peter Andrew wrote: > Good morning, > > I have just upgraded to Paraview 4.3.1 from 4.10, because I was unable to > change the specularity of a surface in 4.1 (this is fixed in 4.3, which is > nice). But now I can?t find the ?headlight? option that used to be in 4.1?s > render view options. > > Without it, the images I need to produce for a publication look dark and > washed out. > > Could you point me toward the lighting tool in 4.3 that lets me turn on a > headlight? > > Thanks for your time, > > Pete Bosler > > ????? > Peter Bosler, PhD > John von Neumann Fellow > Sandia National Laboratories > Multiphysics Applications (01446) > pabosle at sandia.gov > (505) 845 - 0427 > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 pabosle at sandia.gov Tue Mar 17 13:56:55 2015 From: pabosle at sandia.gov (Bosler, Peter Andrew) Date: Tue, 17 Mar 2015 17:56:55 +0000 Subject: [Paraview] [EXTERNAL] Re: Headlight in 4.3.1? In-Reply-To: References: Message-ID: Perfect! Thanks very much. Pete On 3/17/15, 11:49 AM, "Cory Quammen" wrote: >Peter, > >You can find the headlight by looking in the Properties panel under >the Lights section. This is an advanced setting, so click the gear >icon in the Properties panel to expose it. Under the Lights section in >the panel (it's towards the bottom), click the "Edit" button and >select "Additional Headlight" in the Lights Editor dialog that pops >up. > >Hope that helps, >Cory > >On Tue, Mar 17, 2015 at 1:40 PM, Bosler, Peter Andrew > wrote: >> Good morning, >> >> I have just upgraded to Paraview 4.3.1 from 4.10, because I was unable >>to >> change the specularity of a surface in 4.1 (this is fixed in 4.3, which >>is >> nice). But now I can?t find the ?headlight? option that used to be in >>4.1?s >> render view options. >> >> Without it, the images I need to produce for a publication look dark and >> washed out. >> >> Could you point me toward the lighting tool in 4.3 that lets me turn on >>a >> headlight? >> >> Thanks for your time, >> >> Pete Bosler >> >> ????? >> Peter Bosler, PhD >> John von Neumann Fellow >> Sandia National Laboratories >> Multiphysics Applications (01446) >> pabosle at sandia.gov >> (505) 845 - 0427 >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 jm.lucas at gantha.com Tue Mar 17 12:46:08 2015 From: jm.lucas at gantha.com (Jean-Michel) Date: Tue, 17 Mar 2015 17:46:08 +0100 Subject: [Paraview] Fetching data from xdmf temporal collection Message-ID: <001b01d060d1$df435e70$9dca1b50$@lucas@gantha.com> Dear all, I am trying to fetch data out of a xdmf/h5 file. My xdmf file is a temporal collection and the xdmf reader recognizes the time steps (index/values in the information block). I would like to access the point data for each time steps. However, I seem to only get one time step when fetching the point data from the multi-block dataset and I don't know how to iterate over the different time steps. Hope somebody can help. Thank you very much, Jean-Michel --- 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: From tim.gallagher at gatech.edu Tue Mar 17 14:43:49 2015 From: tim.gallagher at gatech.edu (Tim Gallagher) Date: Tue, 17 Mar 2015 14:43:49 -0400 (EDT) Subject: [Paraview] Fetching data from xdmf temporal collection In-Reply-To: <001b01d060d1$df435e70$9dca1b50$@lucas@gantha.com> Message-ID: <1752313018.10321908.1426617829417.JavaMail.root@mail.gatech.edu> Hi Jean-Michel, For what it's worth, we never had much luck when we tried using XDMF time series (back in the early PV version 3.14 days). So we instead just got in the habit of looking at individual snap shots and if we wanted to do an animation, we would use the Python trace feature to set up our view and then make some small modifications to the generated trace script. We would wrap all of the contents in a function that took in a file name/number and output an image at the end and then we would write a small driver program that would call that function, looping over our temporal series that way. It has the added benefit of running the visualization on a cluster where each process is serial and handles a range of data files. Hopefully somebody who has gotten temporal series to work can help you out. If not, I'll be happy to share some example scripts for processing time series data as snapshots using pvpython. Tim ----- Original Message ----- From: "Jean-Michel" To: paraview at paraview.org Sent: Tuesday, March 17, 2015 12:46:08 PM Subject: [Paraview] Fetching data from xdmf temporal collection Dear all, I am trying to fetch data out of a xdmf/h5 file. My xdmf file is a temporal collection and the xdmf reader recognizes the time steps (index/values in the information block). I would like to access the point data for each time steps. However, I seem to only get one time step when fetching the point data from the multi-block dataset and I don't know how to iterate over the different time steps. Hope somebody can help. Thank you very much, Jean-Michel 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Mar 17 14:46:02 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 17 Mar 2015 18:46:02 +0000 Subject: [Paraview] [EXTERNAL] Re: Trace recorder and presets (color table) In-Reply-To: <55075CFE.30106@lbl.gov> References: <23e410a9b2c245ca8c1f8a8928329688@ES05AMSNLNT.srn.sandia.gov> <55075CFE.30106@lbl.gov> Message-ID: Thanks Burlen! Obviously, my ParaView Python fu is weak. I tried to merge this code into Python created by the trace recorder, but couldn't. Say a person does the following (which is sort of what my customer is doing) : * Trace recorder on. * Wavelet. Apply. Surface. RTData. * Color Editor/ Presets/ Blue to Red Rainbow. * Trace Recorder off. The line setting Blue to Red Rainbow doesn't get recorded. What code would I paste in there? Here is the incorrect trace: #### import the simple module from the paraview from paraview.simple import * #### disable automatic camera reset on 'Show' paraview.simple._DisableFirstRenderCameraReset() # create a new 'Wavelet' wavelet1 = Wavelet() # get active view renderView1 = GetActiveViewOrCreate('RenderView') # uncomment following to set a specific view size # renderView1.ViewSize = [856, 797] # show data in view wavelet1Display = Show(wavelet1, renderView1) # trace defaults for the display properties. wavelet1Display.Representation = 'Outline' wavelet1Display.ColorArrayName = ['POINTS', ''] wavelet1Display.ScalarOpacityUnitDistance = 1.7320508075688779 wavelet1Display.Slice = 10 # reset view to fit data renderView1.ResetCamera() # change representation type wavelet1Display.SetRepresentationType('Surface') # set scalar coloring ColorBy(wavelet1Display, ('POINTS', 'RTData')) # rescale color and/or opacity maps used to include current data range wavelet1Display.RescaleTransferFunctionToDataRange(True) # show color bar/color legend wavelet1Display.SetScalarBarVisibility(renderView1, True) # get color transfer function/color map for 'RTData' rTDataLUT = GetColorTransferFunction('RTData') rTDataLUT.RGBPoints = [37.35310363769531, 0.231373, 0.298039, 0.752941, 112.04112243652344, 0.865003, 0.865003, 0.865003, 186.72914123535156, 0.705882, 0.0156863, 0.14902] rTDataLUT.ScalarRangeInitialized = 1.0 # get opacity transfer function/opacity map for 'RTData' rTDataPWF = GetOpacityTransferFunction('RTData') rTDataPWF.Points = [37.35310363769531, 0.0, 0.5, 0.0, 186.72914123535156, 1.0, 0.5, 0.0] rTDataPWF.ScalarRangeInitialized = 1 #### saving camera placements for all active views # current camera placement for renderView1 renderView1.CameraPosition = [0.0, 0.0, 66.92130429902464] renderView1.CameraParallelScale = 17.320508075688775 #### uncomment the following to render all views # RenderAllViews() # alternatively, if you want to write images, you can use SaveScreenshot(...). From: Burlen Loring [mailto:bloring at lbl.gov] Sent: Monday, March 16, 2015 4:45 PM To: Scott, W Alan; paraview at paraview.org Subject: [EXTERNAL] Re: [Paraview] Trace recorder and presets (color table) Hi Alan, You can use the AssignLookupTable function to reference builtin lookup tables by name. For example see code between # marks below. There are a few other conveniences for working with the builtin tables as well, see this recipe w = Wavelet() w_rep = Show(w) w_rep.Representation = 'Surface' # w_rep.ColorArrayName = 'RTData' w_arr = w.PointData.GetArray('RTData') w_rep.LookupTable = AssignLookupTable(w_arr, 'Rainbow Blended White') # Render().ResetCamera() Burlen On 03/16/2015 03:14 PM, Scott, W Alan wrote: I have a user that needs to change the ParaView preset from default (cool to warm) to another ParaView preset (Blue to Red Rainbow). He wants to do this in a python trace. So, he used the trace recorder to record his steps. Unfortunately, changing presets is not recorded with the trace recorder. I have written this issue up as bug number http://www.paraview.org/Bug/view.php?id=15116, but need to give the user the code that would have/ should have been produced. Does anyone have the python code that changes presets? Thanks all! 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 bloring at lbl.gov Tue Mar 17 16:16:45 2015 From: bloring at lbl.gov (Burlen Loring) Date: Tue, 17 Mar 2015 13:16:45 -0700 Subject: [Paraview] [EXTERNAL] Re: Trace recorder and presets (color table) In-Reply-To: References: <23e410a9b2c245ca8c1f8a8928329688@ES05AMSNLNT.srn.sandia.gov> <55075CFE.30106@lbl.gov> Message-ID: <55088BAD.5020700@lbl.gov> Hi Alan, The verbosity of the trace can be confusing, 90% of it is unnecessary, and can be removed. Here's how it looks in your example with unnecessary stuff removed and the 3 lines added to change the lut by name. #### import the simple module from the paraview from paraview.simple import * #### disable automatic camera reset on 'Show' paraview.simple._DisableFirstRenderCameraReset() # create a new 'Wavelet' wavelet1 = Wavelet() # get active view renderView1 = GetActiveViewOrCreate('RenderView') # uncomment following to set a specific view size # renderView1.ViewSize = [856, 797] # show data in view wavelet1Display = Show(wavelet1, renderView1) # change representation type wavelet1Display.SetRepresentationType('Surface') *# change lookup table** **wavelet1Display.ColorArrayName = 'RTData'** **w_arr = wavelet1.PointData.GetArray('RTData')** **wavelet1Display.LookupTable = AssignLookupTable(w_arr, 'Rainbow Blended White')* # show color bar/color legend wavelet1Display.SetScalarBarVisibility(renderView1, True) # reset view to fit data renderView1.ResetCamera() #### uncomment the following to render all views # RenderAllViews() # alternatively, if you want to write images, you can use SaveScreenshot(...). On 03/17/2015 11:46 AM, Scott, W Alan wrote: > > Thanks Burlen! > > Obviously, my ParaView Python fu is weak. I tried to merge this code > into Python created by the trace recorder, but couldn?t. Say a person > does the following (which is sort of what my customer is doing) : > > ?Trace recorder on. > > ?Wavelet. Apply. Surface. RTData. > > ?Color Editor/ Presets/ Blue to Red Rainbow. > > ?Trace Recorder off. > > The line setting Blue to Red Rainbow doesn?t get recorded. What code > would I paste in there? > > Here is the incorrect trace: > > #### import the simple module from the paraview > > from paraview.simple import * > > #### disable automatic camera reset on 'Show' > > paraview.simple._DisableFirstRenderCameraReset() > > # create a new 'Wavelet' > > wavelet1 = Wavelet() > > # get active view > > renderView1 = GetActiveViewOrCreate('RenderView') > > # uncomment following to set a specific view size > > # renderView1.ViewSize = [856, 797] > > # show data in view > > wavelet1Display = Show(wavelet1, renderView1) > > # trace defaults for the display properties. > > wavelet1Display.Representation = 'Outline' > > wavelet1Display.ColorArrayName = ['POINTS', ''] > > wavelet1Display.ScalarOpacityUnitDistance = 1.7320508075688779 > > wavelet1Display.Slice = 10 > > # reset view to fit data > > renderView1.ResetCamera() > > # change representation type > > wavelet1Display.SetRepresentationType('Surface') > > # set scalar coloring > > ColorBy(wavelet1Display, ('POINTS', 'RTData')) > > # rescale color and/or opacity maps used to include current data range > > wavelet1Display.RescaleTransferFunctionToDataRange(True) > > # show color bar/color legend > > wavelet1Display.SetScalarBarVisibility(renderView1, True) > > # get color transfer function/color map for 'RTData' > > rTDataLUT = GetColorTransferFunction('RTData') > > rTDataLUT.RGBPoints = [37.35310363769531, 0.231373, 0.298039, > 0.752941, 112.04112243652344, 0.865003, 0.865003, 0.865003, > 186.72914123535156, 0.705882, 0.0156863, 0.14902] > > rTDataLUT.ScalarRangeInitialized = 1.0 > > # get opacity transfer function/opacity map for 'RTData' > > rTDataPWF = GetOpacityTransferFunction('RTData') > > rTDataPWF.Points = [37.35310363769531, 0.0, 0.5, 0.0, > 186.72914123535156, 1.0, 0.5, 0.0] > > rTDataPWF.ScalarRangeInitialized = 1 > > #### saving camera placements for all active views > > # current camera placement for renderView1 > > renderView1.CameraPosition = [0.0, 0.0, 66.92130429902464] > > renderView1.CameraParallelScale = 17.320508075688775 > > #### uncomment the following to render all views > > # RenderAllViews() > > # alternatively, if you want to write images, you can use > SaveScreenshot(...). > > *From:*Burlen Loring [mailto:bloring at lbl.gov] > *Sent:* Monday, March 16, 2015 4:45 PM > *To:* Scott, W Alan; paraview at paraview.org > *Subject:* [EXTERNAL] Re: [Paraview] Trace recorder and presets (color > table) > > Hi Alan, > > You can use the AssignLookupTable function to reference builtin lookup > tables by name. For example see code between # marks below. There are > a few other conveniences for working with the builtin tables as well, > see this recipe > > > w = Wavelet() > w_rep = Show(w) > w_rep.Representation = 'Surface' > # > w_rep.ColorArrayName = 'RTData' > w_arr = w.PointData.GetArray('RTData') > w_rep.LookupTable = AssignLookupTable(w_arr, 'Rainbow Blended White') > # > Render().ResetCamera() > > Burlen > > On 03/16/2015 03:14 PM, Scott, W Alan wrote: > > I have a user that needs to change the ParaView preset from > default (cool to warm) to another ParaView preset (Blue to Red > Rainbow). He wants to do this in a python trace. So, he used the > trace recorder to record his steps. Unfortunately, changing > presets is not recorded with the trace recorder. > > I have written this issue up as bug number > http://www.paraview.org/Bug/view.php?id=15116, but need to give > the user the code that would have/ should have been produced. > Does anyone have the python code that changes presets? > > Thanks all! > > Alan > > > > > _______________________________________________ > > 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 wascott at sandia.gov Tue Mar 17 19:48:44 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 17 Mar 2015 23:48:44 +0000 Subject: [Paraview] [EXTERNAL] Re: Trace recorder and presets (color table) In-Reply-To: <55088BAD.5020700@lbl.gov> References: <23e410a9b2c245ca8c1f8a8928329688@ES05AMSNLNT.srn.sandia.gov> <55075CFE.30106@lbl.gov> <55088BAD.5020700@lbl.gov> Message-ID: Excellent! One question - my user may want to use Opacity mapping. The code below changes the Mapping Data view, removing the Opacity part of the view. Is there a way to return it to normal, enabling Opacity Mapping? Thanks From: Burlen Loring [mailto:bloring at lbl.gov] Sent: Tuesday, March 17, 2015 2:17 PM To: Scott, W Alan; paraview at paraview.org Subject: Re: [EXTERNAL] Re: [Paraview] Trace recorder and presets (color table) Hi Alan, The verbosity of the trace can be confusing, 90% of it is unnecessary, and can be removed. Here's how it looks in your example with unnecessary stuff removed and the 3 lines added to change the lut by name. #### import the simple module from the paraview from paraview.simple import * #### disable automatic camera reset on 'Show' paraview.simple._DisableFirstRenderCameraReset() # create a new 'Wavelet' wavelet1 = Wavelet() # get active view renderView1 = GetActiveViewOrCreate('RenderView') # uncomment following to set a specific view size # renderView1.ViewSize = [856, 797] # show data in view wavelet1Display = Show(wavelet1, renderView1) # change representation type wavelet1Display.SetRepresentationType('Surface') # change lookup table wavelet1Display.ColorArrayName = 'RTData' w_arr = wavelet1.PointData.GetArray('RTData') wavelet1Display.LookupTable = AssignLookupTable(w_arr, 'Rainbow Blended White') # show color bar/color legend wavelet1Display.SetScalarBarVisibility(renderView1, True) # reset view to fit data renderView1.ResetCamera() #### uncomment the following to render all views # RenderAllViews() # alternatively, if you want to write images, you can use SaveScreenshot(...). On 03/17/2015 11:46 AM, Scott, W Alan wrote: Thanks Burlen! Obviously, my ParaView Python fu is weak. I tried to merge this code into Python created by the trace recorder, but couldn't. Say a person does the following (which is sort of what my customer is doing) : * Trace recorder on. * Wavelet. Apply. Surface. RTData. * Color Editor/ Presets/ Blue to Red Rainbow. * Trace Recorder off. The line setting Blue to Red Rainbow doesn't get recorded. What code would I paste in there? Here is the incorrect trace: #### import the simple module from the paraview from paraview.simple import * #### disable automatic camera reset on 'Show' paraview.simple._DisableFirstRenderCameraReset() # create a new 'Wavelet' wavelet1 = Wavelet() # get active view renderView1 = GetActiveViewOrCreate('RenderView') # uncomment following to set a specific view size # renderView1.ViewSize = [856, 797] # show data in view wavelet1Display = Show(wavelet1, renderView1) # trace defaults for the display properties. wavelet1Display.Representation = 'Outline' wavelet1Display.ColorArrayName = ['POINTS', ''] wavelet1Display.ScalarOpacityUnitDistance = 1.7320508075688779 wavelet1Display.Slice = 10 # reset view to fit data renderView1.ResetCamera() # change representation type wavelet1Display.SetRepresentationType('Surface') # set scalar coloring ColorBy(wavelet1Display, ('POINTS', 'RTData')) # rescale color and/or opacity maps used to include current data range wavelet1Display.RescaleTransferFunctionToDataRange(True) # show color bar/color legend wavelet1Display.SetScalarBarVisibility(renderView1, True) # get color transfer function/color map for 'RTData' rTDataLUT = GetColorTransferFunction('RTData') rTDataLUT.RGBPoints = [37.35310363769531, 0.231373, 0.298039, 0.752941, 112.04112243652344, 0.865003, 0.865003, 0.865003, 186.72914123535156, 0.705882, 0.0156863, 0.14902] rTDataLUT.ScalarRangeInitialized = 1.0 # get opacity transfer function/opacity map for 'RTData' rTDataPWF = GetOpacityTransferFunction('RTData') rTDataPWF.Points = [37.35310363769531, 0.0, 0.5, 0.0, 186.72914123535156, 1.0, 0.5, 0.0] rTDataPWF.ScalarRangeInitialized = 1 #### saving camera placements for all active views # current camera placement for renderView1 renderView1.CameraPosition = [0.0, 0.0, 66.92130429902464] renderView1.CameraParallelScale = 17.320508075688775 #### uncomment the following to render all views # RenderAllViews() # alternatively, if you want to write images, you can use SaveScreenshot(...). From: Burlen Loring [mailto:bloring at lbl.gov] Sent: Monday, March 16, 2015 4:45 PM To: Scott, W Alan; paraview at paraview.org Subject: [EXTERNAL] Re: [Paraview] Trace recorder and presets (color table) Hi Alan, You can use the AssignLookupTable function to reference builtin lookup tables by name. For example see code between # marks below. There are a few other conveniences for working with the builtin tables as well, see this recipe w = Wavelet() w_rep = Show(w) w_rep.Representation = 'Surface' # w_rep.ColorArrayName = 'RTData' w_arr = w.PointData.GetArray('RTData') w_rep.LookupTable = AssignLookupTable(w_arr, 'Rainbow Blended White') # Render().ResetCamera() Burlen On 03/16/2015 03:14 PM, Scott, W Alan wrote: I have a user that needs to change the ParaView preset from default (cool to warm) to another ParaView preset (Blue to Red Rainbow). He wants to do this in a python trace. So, he used the trace recorder to record his steps. Unfortunately, changing presets is not recorded with the trace recorder. I have written this issue up as bug number http://www.paraview.org/Bug/view.php?id=15116, but need to give the user the code that would have/ should have been produced. Does anyone have the python code that changes presets? Thanks all! 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 mshoji-tky at umin.ac.jp Tue Mar 17 20:04:16 2015 From: mshoji-tky at umin.ac.jp (Masaaki SHOJIMA) Date: Wed, 18 Mar 2015 09:04:16 +0900 Subject: [Paraview] Fwd: Gradient of Unstructed dataset In-Reply-To: References: <5507D199.5040505@gmail.com> Message-ID: Hi Berk, Armin, Michael and friends It is getting warm and flowers are starting to bloom in japan, this morning. Nightly Builds of Paraview was downloaded on 2015-Mar-18 (ParaView-Windows-64bit-NIGHTLY.zip). Gradient of Pressure was calculated using "Gradient of Unstrucutred Dataset" filter and Z component of Grad (pressure) was visualized. Unfortunately, Nightly build did not settle the problem... The computed values by nightly builds were also half compared to those of Ensight. Could you take a look of the result in the attached PDF? Thanks for your continuous help. Masaaki 2015-03-17 22:01 GMT+09:00 Berk Geveci : > Hi Masaaki, > > I will hold off testing on my end until you have a chance to test with > nightly binaries. Please let us know how it goes. > > Regards, > -berk > > On Tue, Mar 17, 2015 at 8:09 AM, wrote: > >> You could test it with the nighly builds from the dashboard. That way you >> don't have to compile anything. >> >> You can find more information here: >> http://www.paraview.org/Wiki/ParaView_Nightly_Binaries >> >> -Armin >> >> >> >> On Tue Mar 17 12:27:27 2015 GMT+0200, Masaaki SHOJIMA wrote: >> > Hi, Michael, >> > >> > I found a web-page regarding the CGNS reader, in which you are making >> > important comments. >> > http://comments.gmane.org/gmane.comp.science.paraview.user/23957 >> > >> > I have to wait for the next version, is it right? >> > >> > Thanks >> > >> > Masaaki >> > >> > 2015-03-17 16:02 GMT+09:00 Mickael Philit : >> > >> > > Hello, >> > > >> > > sorry to intrude, >> > > I think the problem may come from the CGNS loader of ParaView. >> > > When using the CGNS plugin from ParaView development version, you get >> the >> > > same picture as Ensight. >> > > My two cents >> > > >> > > Mickael >> > > >> > > >> > > On 17/03/2015 05:04, Masaaki SHOJIMA wrote: >> > > >> > > Hi Berk, >> > > >> > > I appreciate your kindness >> > > >> > > Here, I attaches the data. >> > > Compare Gradient.pdf (252KB) >> > > >> > > A calculated field by SC/Tetra solver is uploaded in Dropbox. >> (Calc.zip) >> > > Please download the data. It contains FLD format for SC/Tetra post and >> > > CGNS format for Ensight and Paraview. >> > > https://www.dropbox.com/s/5fpeu1qwhyzjn5u/Calc.zip?dl=0 >> > > >> > > (1) I calculated the flow and the pressure in a simple cylinder for a >> test >> > > ( diameter 0.005m, length 0.01m). Plug flow at inlet with 0.03 m/s. >> > > >> > > (2) Data were transfered to Ensight and Paraview in CGNS format. >> > > >> > > (3) Pressure was mapped on the surface and compared between SC/Tetra >> post, >> > > Ensight and Paraview. All application provided same results. >> > > >> > > (4) Gradient (pressure) was calculated in each post and z-component of >> > > Gradient (pressure) was visualized with same colored contour. Only >> paraview >> > > provided a different image because the computed gradients in paraview >> had >> > > half values compared to SC/Tetra post and Ensight. >> > > >> > > (5) Gradient (velocity-X) was also calculated in each post and the >> > > X-component of Grad (velocity-X) was visualized. Same results as >> shown in 4. >> > > >> > > >> > > Thanks a lot. >> > > >> > > Masaaki >> > > >> > > >> > > >> > > >> > > _______________________________________________ >> > > Powered by www.kitware.com >> > > >> > > Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> > > >> > > Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> > > >> > > Search the list archives at: http://markmail.org/search/?q=ParaView >> > > >> > > Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > >> > > >> > > >> > >> >> -- >> Sent from my Jolla >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Nightly builds Gradient of Pressure.pdf Type: application/pdf Size: 85222 bytes Desc: not available URL: From alyckegaard at xnovotech.com Wed Mar 18 04:57:18 2015 From: alyckegaard at xnovotech.com (Allan Lyckegaard) Date: Wed, 18 Mar 2015 09:57:18 +0100 Subject: [Paraview] Get selection of input in Python programmable filter In-Reply-To: <1BDD6D81-9F41-4CEE-97A8-A8C2840B873F@xnovotech.com> References: <1BDD6D81-9F41-4CEE-97A8-A8C2840B873F@xnovotech.com> Message-ID: Ok, I think I found a way to do it. First get the proxy of the filter itself (http://public.kitware.com/pipermail/paraview/2011-November/023336.html ): import paraview.servermanager as sm proxies = sm.ProxyManager().GetProxiesInGroup("sources").values() selfProxy = [p for p in proxies if p.GetClientSideObject() is self][0] Then get the selected points of the proxy?s input like this (http://stackoverflow.com/a/27805049): proxy = paraview.simple.GetActiveSource() active_selection = proxy.GetSelectionInput(proxy.Port) /Allan > On 17 Mar 2015, at 14:03, Allan Lyckegaard wrote: > > Hi Paraview users, > > I have been searching this list and the documentation but without luck. > > I am working on a python programmable filter with two vtkimagedata as inputs. In the paraview GUI, both input vtkimagedata has an associated selection picked by ?Select Points With Polygon?. > > How do I in the python programmable filter find out what points have been selected in the two input vtkimagedata? > > /Allan -------------- next part -------------- An HTML attachment was scrubbed... URL: From nenasantos at hotmail.com Wed Mar 18 05:18:27 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Wed, 18 Mar 2015 09:18:27 +0000 Subject: [Paraview] Add logo to animation paraview script In-Reply-To: References: , , , Message-ID: Dear all,What are the steps to include a image, as logo, in a corner of an animated script. Basicaly I want to know what is the code that allows to include image as logo in my animated script. I do not want image as background but image as logo, placed in one of the corners of my figure. Kind regards Madalena -------------- next part -------------- An HTML attachment was scrubbed... URL: From marco.goetz at tu-dresden.de Wed Mar 18 06:20:24 2015 From: marco.goetz at tu-dresden.de (Marco Goetz) Date: Wed, 18 Mar 2015 11:20:24 +0100 Subject: [Paraview] Bug in interpolation of point data Message-ID: <001501d06165$25efad40$71cf07c0$@tu-dresden.de> Hello, I tried to interpolate nodal values using ParaView. But for symmetric problems there are asymmetric results, as can be seen in the figures appended. I tested it with hexahedron and quad type elements, but both give the same results. You can find my simplified input file also appended. Hopefully you can help me to create symmetric interpolation results for symmetric problems. Thank you in advance, best regard Marco G?tz ---------------------------------------------- Technische Universit?t Dresden Faculty of Civil Engineering Institute for Structural Analysis -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: hexahedron_error.png Type: image/png Size: 18157 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: quad_error.png Type: image/png Size: 14152 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: hexahedron_error.vtu Type: application/octet-stream Size: 1938 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: quad_error.vtu Type: application/octet-stream Size: 1264 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Wed Mar 18 08:06:13 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 18 Mar 2015 08:06:13 -0400 Subject: [Paraview] Add logo to animation paraview script In-Reply-To: References: Message-ID: The easier way is to simply create a large image with the logo in the corner and use that as a background. You can use Python tracing to determine the Python code to use to set the background image. Utkarsh On Mon, Mar 16, 2015 at 11:18 AM, Madalena S. Malhadas wrote: > > Dear all, > What are the steps to include a image, as logo, in a corner of an animated > script. > > Basicaly I want to know what is the code that allows to include image as > logo in my animated script. I do not want image as background but image as > logo, placed in one of the corners of my figure. > > Kind regards > > Madalena > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Wed Mar 18 08:14:20 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 18 Mar 2015 08:14:20 -0400 Subject: [Paraview] ParaView and Matlab lovers Parula ColorScale In-Reply-To: <550842F6.7050207@ec-nantes.fr> References: <550842F6.7050207@ec-nantes.fr> Message-ID: Folks, It must be noted that Mathworks considers the Parula colorscale their intellectual property and that it's not "appropriate or acceptable to copy or re-use it in non-MathWorks plotting tools" [1]. Utkarsh [1] http://blogs.mathworks.com/steve/2014/10/20/a-new-colormap-for-matlab-part-2-troubles-with-rainbows/#comment-27702 On Tue, Mar 17, 2015 at 11:06 AM, Felipe Bordeu wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > hi to all, > > Attached you can find the Parula coloscale from the last Matlab release. > > Felipe > > - -- > Felipe Bordeu Weldt > Ing?nieur de Recherche > - ------------------------------------- > T?l. : 33 (0)2 40 37 16 57 > Fax. : 33 (0)2 40 74 74 06 > Felipe.Bordeu at ec-nantes.fr > Institut GeM - UMR CNRS 6183 > ?cole Centrale Nantes > 1 Rue de La No?, 44321 Nantes, FRANCE > - ------------------------------------- > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iQEcBAEBAgAGBQJVCELyAAoJEE/fMfNgU9/D2zEIAJtQFgOUO+8UgQNwGNRKsagi > jJNUuF4Z3P+lE55OvrT/YNJVUJtQYndeTv8EtFwq0O03sF014DQJn6koPRnVvnVB > x3ITAmwtTUGpUcgl08k6qIB2T77LlEWvjIZLR/Uzj+dQ+qHtTUSIMXxOsHcKyvMR > 27JiyKdCk5t+iAxHNqkdNXiHRY4tXNAgi8cqZYwIPLo8d4N+Z4OVIz+bJy7xP0EQ > WXk7nwAxKsqWoktozsg/+LiZR6YCU+RI5CWcucCQ3D0+tdieO6rSikgkVBYPpWBg > nFTx6fZx+YH27h75R6pcda+lOOFtubFr4cNHeiWz9zyNBXe85OvGXdS4aYEO/kg= > =C+Se > -----END PGP SIGNATURE----- > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Wed Mar 18 08:20:11 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 18 Mar 2015 08:20:11 -0400 Subject: [Paraview] Fluid Flow Simulation in ParaView In-Reply-To: References: Message-ID: Try applying the "Glyph" filter or using the "Surface LIC" plugin[1] [1] http://www.paraview.org/Wiki/ParaView/Line_Integral_Convolution Utkarsh On Tue, Mar 17, 2015 at 8:37 AM, Rohit Narurkar wrote: > Hello > > I wish to simulate fluid flow using ParaView. I have 1000 .vtk files for the > 1000 time steps. > I have attached along with this mail one of the .vtk files. When I open this > collection in ParaView, and change the 'coloring' to the velocity name I > have given i.e. "VecVelocity" as you can see in the sample .vtk file. There > is another option to its right which offers 'magnitude', 'x', 'y' and 'z'. > But there are some points with negative velocities and ParaView is only > considering the magnitude (hence positive). I wish to display even the > negative values. How do I do that? > > Any help would be great! > > Thank you! > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From nenasantos at hotmail.com Wed Mar 18 08:49:52 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Wed, 18 Mar 2015 12:49:52 +0000 Subject: [Paraview] Add logo to animation paraview script In-Reply-To: References: , , Message-ID: Dear all, What are the steps to include a image, as logo, in a corner of an animated script. Basicaly I want to know what is the code that allows to include image as logo in my animated script. I do not want image as background but image as logo, placed in one of the corners of my figure. Kind regards Madalena -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Wed Mar 18 08:59:27 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Wed, 18 Mar 2015 08:59:27 -0400 Subject: [Paraview] Fwd: Gradient of Unstructed dataset In-Reply-To: References: <5507D199.5040505@gmail.com> Message-ID: Thanks Masaaki. I will look into it. I wish that I could say the same about northern New York State. The high temperature for today and tomorrow is 30F (-1C). Most of the snow melted though so spring is coming :-) -berk On Tue, Mar 17, 2015 at 8:04 PM, Masaaki SHOJIMA wrote: > Hi Berk, Armin, Michael and friends > > It is getting warm and flowers are starting to bloom in japan, this > morning. > > Nightly Builds of Paraview was downloaded on 2015-Mar-18 > (ParaView-Windows-64bit-NIGHTLY.zip). > > Gradient of Pressure was calculated using "Gradient of Unstrucutred > Dataset" filter and Z component of Grad (pressure) was visualized. > > Unfortunately, Nightly build did not settle the problem... > The computed values by nightly builds were also half compared to those of > Ensight. > > Could you take a look of the result in the attached PDF? > > Thanks for your continuous help. > > Masaaki > > 2015-03-17 22:01 GMT+09:00 Berk Geveci : > >> Hi Masaaki, >> >> I will hold off testing on my end until you have a chance to test with >> nightly binaries. Please let us know how it goes. >> >> Regards, >> -berk >> >> On Tue, Mar 17, 2015 at 8:09 AM, wrote: >> >>> You could test it with the nighly builds from the dashboard. That way >>> you don't have to compile anything. >>> >>> You can find more information here: >>> http://www.paraview.org/Wiki/ParaView_Nightly_Binaries >>> >>> -Armin >>> >>> >>> >>> On Tue Mar 17 12:27:27 2015 GMT+0200, Masaaki SHOJIMA wrote: >>> > Hi, Michael, >>> > >>> > I found a web-page regarding the CGNS reader, in which you are making >>> > important comments. >>> > http://comments.gmane.org/gmane.comp.science.paraview.user/23957 >>> > >>> > I have to wait for the next version, is it right? >>> > >>> > Thanks >>> > >>> > Masaaki >>> > >>> > 2015-03-17 16:02 GMT+09:00 Mickael Philit : >>> > >>> > > Hello, >>> > > >>> > > sorry to intrude, >>> > > I think the problem may come from the CGNS loader of ParaView. >>> > > When using the CGNS plugin from ParaView development version, you >>> get the >>> > > same picture as Ensight. >>> > > My two cents >>> > > >>> > > Mickael >>> > > >>> > > >>> > > On 17/03/2015 05:04, Masaaki SHOJIMA wrote: >>> > > >>> > > Hi Berk, >>> > > >>> > > I appreciate your kindness >>> > > >>> > > Here, I attaches the data. >>> > > Compare Gradient.pdf (252KB) >>> > > >>> > > A calculated field by SC/Tetra solver is uploaded in Dropbox. >>> (Calc.zip) >>> > > Please download the data. It contains FLD format for SC/Tetra post >>> and >>> > > CGNS format for Ensight and Paraview. >>> > > https://www.dropbox.com/s/5fpeu1qwhyzjn5u/Calc.zip?dl=0 >>> > > >>> > > (1) I calculated the flow and the pressure in a simple cylinder for >>> a test >>> > > ( diameter 0.005m, length 0.01m). Plug flow at inlet with 0.03 m/s. >>> > > >>> > > (2) Data were transfered to Ensight and Paraview in CGNS format. >>> > > >>> > > (3) Pressure was mapped on the surface and compared between SC/Tetra >>> post, >>> > > Ensight and Paraview. All application provided same results. >>> > > >>> > > (4) Gradient (pressure) was calculated in each post and z-component >>> of >>> > > Gradient (pressure) was visualized with same colored contour. Only >>> paraview >>> > > provided a different image because the computed gradients in >>> paraview had >>> > > half values compared to SC/Tetra post and Ensight. >>> > > >>> > > (5) Gradient (velocity-X) was also calculated in each post and the >>> > > X-component of Grad (velocity-X) was visualized. Same results as >>> shown in 4. >>> > > >>> > > >>> > > Thanks a lot. >>> > > >>> > > Masaaki >>> > > >>> > > >>> > > >>> > > >>> > > _______________________________________________ >>> > > Powered by www.kitware.com >>> > > >>> > > Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> > > >>> > > Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> > > >>> > > Search the list archives at: http://markmail.org/search/?q=ParaView >>> > > >>> > > Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> > > >>> > > >>> > > >>> > >>> >>> -- >>> Sent from my Jolla >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> 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 KSheldon at slb.com Wed Mar 18 09:55:14 2015 From: KSheldon at slb.com (Ken Sheldon) Date: Wed, 18 Mar 2015 13:55:14 +0000 Subject: [Paraview] Fetching data from xdmf temporal collection Message-ID: <2911E772881F8B4AB39462AA4A35EC5501019D8368@NL0230MBX12N2.DIR.slb.com> Jean-Michel I find the reader is very sensitive to input errors. The diagnostic messages are not always sufficient to identify mistakes in the XDMF file. I spent some time getting this to work for some our data. If you would like send me a copy of your XDMF (not the HDF5), or at least the first few timesteps of it, I would be happy to take a look. ----Ken Date: Tue, 17 Mar 2015 17:46:08 +0100 From: "Jean-Michel" To: Subject: [Paraview] Fetching data from xdmf temporal collection Message-ID: <001b01d060d1$df435e70$9dca1b50$@lucas at gantha.com> Content-Type: text/plain; charset="utf-8" Dear all, I am trying to fetch data out of a xdmf/h5 file. My xdmf file is a temporal collection and the xdmf reader recognizes the time steps (index/values in the information block). I would like to access the point data for each time steps. However, I seem to only get one time step when fetching the point data from the multi-block dataset and I don't know how to iterate over the different time steps. Hope somebody can help. Thank you very much, Jean-Michel From jm.lucas at gantha.com Wed Mar 18 10:19:39 2015 From: jm.lucas at gantha.com (Jean-Michel) Date: Wed, 18 Mar 2015 15:19:39 +0100 Subject: [Paraview] Fetching data from xdmf temporal collection In-Reply-To: <2911E772881F8B4AB39462AA4A35EC5501019D8368@NL0230MBX12N2.DIR.slb.com> References: <2911E772881F8B4AB39462AA4A35EC5501019D8368@NL0230MBX12N2.DIR.slb.com> Message-ID: <001f01d06186$92b10110$b8130330$@lucas@gantha.com> Hi Ken, Thank you very much for offering your help. Attached is the xmf file from which I'm trying to extract the data. I did delete a fair amount of lines from it to keep only the first 10 time steps - hope it won't affect anything. Jean-Michel -----Message d'origine----- De?: Ken Sheldon [mailto:KSheldon at slb.com] Envoy??: mercredi 18 mars 2015 14:55 ??: paraview at paraview.org Cc?: jm.lucas at gantha.com Objet?: RE: [Paraview] Fetching data from xdmf temporal collection Jean-Michel I find the reader is very sensitive to input errors. The diagnostic messages are not always sufficient to identify mistakes in the XDMF file. I spent some time getting this to work for some our data. If you would like send me a copy of your XDMF (not the HDF5), or at least the first few timesteps of it, I would be happy to take a look. ----Ken Date: Tue, 17 Mar 2015 17:46:08 +0100 From: "Jean-Michel" To: Subject: [Paraview] Fetching data from xdmf temporal collection Message-ID: <001b01d060d1$df435e70$9dca1b50$@lucas at gantha.com> Content-Type: text/plain; charset="utf-8" Dear all, I am trying to fetch data out of a xdmf/h5 file. My xdmf file is a temporal collection and the xdmf reader recognizes the time steps (index/values in the information block). I would like to access the point data for each time steps. However, I seem to only get one time step when fetching the point data from the multi-block dataset and I don't know how to iterate over the different time steps. Hope somebody can help. Thank you very much, Jean-Michel --- L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le logiciel antivirus Avast. http://www.avast.com -------------- next part -------------- A non-text attachment was scrubbed... Name: testfile.xmf Type: application/octet-stream Size: 7956 bytes Desc: not available URL: From kmorel at sandia.gov Wed Mar 18 11:15:00 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Wed, 18 Mar 2015 15:15:00 +0000 Subject: [Paraview] Add logo to animation paraview script Message-ID: ParaView currently does not have any direct way to add a logo to a view's foreground or to an animation capture. The best you can do right now is one of the following hacks: 1. As Utkarsh suggested, make a background image with the logo where you want it. Set up your animation so that nothing covers the logo. 2. Make a Plane source. Add a transform filter to place the plane where you want the logo to show up. In the properties panel under Display and then the Miscellaneous subgroup, there is an advanced option for Texture. (The easiest way to find it is to type "texture" in the properties panel's search box.) Use that to load your logo as a texture on the plane. (Lighting and placement could be an issue with this approach.) 3. Add the logo after the movie is generated in a movie-editing tool. This is probably the method I would go for, but it does require finding and using a separate software application. -Ken From: "Madalena S. Malhadas" > Date: Wednesday, March 18, 2015 at 6:49 AM To: "paraview at paraview.org" > Subject: [EXTERNAL] Re: [Paraview] Add logo to animation paraview script Dear all, What are the steps to include a image, as logo, in a corner of an animated script. Basicaly I want to know what is the code that allows to include image as logo in my animated script. I do not want image as background but image as logo, placed in one of the corners of my figure. Kind regards Madalena -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Mar 18 11:26:17 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 18 Mar 2015 11:26:17 -0400 Subject: [Paraview] yosemite crashes In-Reply-To: References: Message-ID: Can you try running with "-dr" command line argument? You may need to specify the full path to the paraview executable in the .app bundle on the command line. Utkarsh On Sat, Mar 14, 2015 at 2:32 PM, Vogiatzis Oikonomidis Ioannis (PSI) wrote: > Hi > > I updated to Yosemite and I keep getting the following crash > I reinstalled paraview already > And deleted the files from /library/preferences > Could you help me somehow locate/fix the error? > > Thanks! From utkarsh.ayachit at kitware.com Wed Mar 18 11:27:20 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 18 Mar 2015 11:27:20 -0400 Subject: [Paraview] Build error on Windows In-Reply-To: <5500ADA4.102@tu-braunschweig.de> References: <5500ADA4.102@tu-braunschweig.de> Message-ID: Not entirely sure what the problem could be. The latest master seems to build fine with VS 2013. Maybe it's a parallel build issue? Try kicking the build off again. Utkarsh On Wed, Mar 11, 2015 at 5:03 PM, Ian Krukow wrote: > Hi all, > > I am trying to build ParaView on Windows, but I get the following error, and > I have no idea what it means or how to fix it: > > 4>C:\ParaView\ParaView-v4.3.1-source\VTK\Wrapping\Tools\vtkWrapPythonInit.c > : fatal error C1041: cannot open program database > 'c:\paraview\pv\vtk\wrapping\tools\x64\debug\vc120.pdb'; if multiple CL.EXE > write to the same .PDB file, please use /FS > > I use ParaView 4.3.1 source code and Visual Studio 2013. > Can anyone help me? > > Kind regards > Ian > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 jm.lucas at gantha.com Wed Mar 18 09:09:28 2015 From: jm.lucas at gantha.com (Jean-Michel) Date: Wed, 18 Mar 2015 14:09:28 +0100 Subject: [Paraview] Fetching data from xdmf temporal collection In-Reply-To: <1752313018.10321908.1426617829417.JavaMail.root@mail.gatech.edu> References: <001b01d060d1$df435e70$9dca1b50$@lucas@gantha.com> <1752313018.10321908.1426617829417.JavaMail.root@mail.gatech.edu> Message-ID: <001901d0617c$c417fdd0$4c47f970$@lucas@gantha.com> Hi Tim, Thank you very much for the input. However, the animation works fine for me from the xdmf time series. From what I understand, your script handles several separate files to generate an animation. My problem is rather to retrieve the point data values at each time step from a unique xmf file for further manipulation in python. Anyway, thank you again for your suggestion. Jean-Michel De : Tim Gallagher [mailto:tim.gallagher at gatech.edu] Envoy? : mardi 17 mars 2015 19:44 ? : Jean-Michel Cc : paraview at paraview.org Objet : Re: [Paraview] Fetching data from xdmf temporal collection Hi Jean-Michel, For what it's worth, we never had much luck when we tried using XDMF time series (back in the early PV version 3.14 days). So we instead just got in the habit of looking at individual snap shots and if we wanted to do an animation, we would use the Python trace feature to set up our view and then make some small modifications to the generated trace script. We would wrap all of the contents in a function that took in a file name/number and output an image at the end and then we would write a small driver program that would call that function, looping over our temporal series that way. It has the added benefit of running the visualization on a cluster where each process is serial and handles a range of data files. Hopefully somebody who has gotten temporal series to work can help you out. If not, I'll be happy to share some example scripts for processing time series data as snapshots using pvpython. Tim _____ From: "Jean-Michel" To: paraview at paraview.org Sent: Tuesday, March 17, 2015 12:46:08 PM Subject: [Paraview] Fetching data from xdmf temporal collection Dear all, I am trying to fetch data out of a xdmf/h5 file. My xdmf file is a temporal collection and the xdmf reader recognizes the time steps (index/values in the information block). I would like to access the point data for each time steps. However, I seem to only get one time step when fetching the point data from the multi-block dataset and I don't know how to iterate over the different time steps. Hope somebody can help. Thank you very much, Jean-Michel _____ Image supprim?e par l'exp?diteur. 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 kmorel at sandia.gov Wed Mar 18 11:42:13 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Wed, 18 Mar 2015 15:42:13 +0000 Subject: [Paraview] Bug in interpolation of point data Message-ID: Yup. This is a known issue with how pretty much every implementation of OpenGL renders quadrilaterals. For the most part, ParaView will interpolate the fields on your hexahedra and quadrilaterals correctly. For example, in either data set, if you add a plot over line filter and plot along the Y axis, you will see that the plot over line filter is symmetrically interpolating the cells (see the attached screenshot). The issue is that both data sets are rendered by sending quadrilaterals to the OpenGL rendering engine. Every implementation of OpenGL I have run into in at least the last 15 years internally breaks the quadrilaterals into triangles (because it makes the rasterization faster). It turns out, the linear interpolation of the two triangles is subtly different than the bi-linear interpolation on a quadrilateral. And, most importantly for your specific question, the interpolation is subtly different depending on which which diagonal is used to split the quadrilateral. In your case, the rendering system is picking different diagonals for the rotationally isomorphic quadrilaterals (ooh, that sounds mathy) and is causing the asymmetric interpolation. We've had multiple discussions about fixing this. In the end we decided to leave it as it is. The issue is that the fix is to break polygons like quadrilaterals into several triangles that are closer to the bilinear interpolation. The issue is that it would add a large computation and memory overhead for an issue that is almost never noticeable. -Ken From: Marco Goetz > Date: Wednesday, March 18, 2015 at 4:20 AM To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] Bug in interpolation of point data Hello, I tried to interpolate nodal values using ParaView. But for symmetric problems there are asymmetric results, as can be seen in the figures appended. I tested it with hexahedron and quad type elements, but both give the same results. You can find my simplified input file also appended. Hopefully you can help me to create symmetric interpolation results for symmetric problems. Thank you in advance, best regard Marco G?tz ---------------------------------------------- Technische Universit?t Dresden Faculty of Civil Engineering Institute for Structural Analysis -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ParaView001.png Type: image/png Size: 180663 bytes Desc: ParaView001.png URL: From dave.demarle at kitware.com Wed Mar 18 12:06:18 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 18 Mar 2015 12:06:18 -0400 Subject: [Paraview] Gauraud shading when reading from HDF5 file. In-Reply-To: <055B9084EECF0244A45C95019FFA1D037CEEB90D@USSLMMBX003.net.plm.eds.com> References: <055B9084EECF0244A45C95019FFA1D037CEEB90D@USSLMMBX003.net.plm.eds.com> Message-ID: XDMF does not have a defined way to mark an array as being "the shading normals". Even for its attribute types scalar, vector tensor etc, vtk's DataSetAttributes active attribute concept is not a 1:1 match so losing semantic information like this in translation there happens. The work around is to apply a filter that tells ParaView that you want this specific array to be used in that way. For example: apply calculator filter with expression "Normals" and check off the "Result Normals" control. Note, if speed/memory is a concern you do the same thing by shallow copying and directly setting the attribute flag in the python programmable filter. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Mar 13, 2015 at 11:29 AM, Feijoo, Gonzalo < gonzalo.feijoo at siemens.com> wrote: > Hello, Everyone, > > > > How can I use normals defined at each node to visualize a triangulation > using Gouraud shading? If I write my data in the .vtk format, then this is > automatically done by Paraview by saving the normals in the NORMALS field > within the POINT_DATA field. But how can I do this from data saved in an > XDMF/HDF5 file? I mean, how would I need to specify the normals in the XDMF > file for the shader to use these vectors? > > > > Thank you in advance for any help. > > > > Best regards, > > > > Gonzalo R. Feij?o > > Advanced projects and architecture > > Specialized Engineering > > > > Siemens Industry Sector > > Siemens Product Lifecycle Management Software Inc. > > 200 Fifth Avenue > > Waltham, MA 02451 United States > > Tel. :+1 (781) 907-9751 > > Fax :+1 (781) 907-9880 > > gonzalo.feijoo at siemens.com > > www.siemens.com/plm > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 Mar 18 14:12:09 2015 From: burlen.loring at gmail.com (Burlen Loring) Date: Wed, 18 Mar 2015 11:12:09 -0700 Subject: [Paraview] [EXTERNAL] Re: Trace recorder and presets (color table) In-Reply-To: References: <23e410a9b2c245ca8c1f8a8928329688@ES05AMSNLNT.srn.sandia.gov> <55075CFE.30106@lbl.gov> <55088BAD.5020700@lbl.gov> Message-ID: <5509BFF9.9040803@gmail.com> did you try including the code from the trace that set the opacity values? try adding that after the lut is set. > wavelet1Display.ScalarOpacityUnitDistance = 1.7320508075688779 > rTDataPWF = GetOpacityTransferFunction('RTData') > rTDataPWF.Points = [37.35310363769531, 0.0, 0.5, 0.0, > 186.72914123535156, 1.0, 0.5, 0.0] On 03/17/2015 04:48 PM, Scott, W Alan wrote: > > Excellent! > > One question ? my user may want to use Opacity mapping. The code > below changes the Mapping Data view, removing the Opacity part of the > view. Is there a way to return it to normal, enabling Opacity Mapping? > > Thanks > > *From:*Burlen Loring [mailto:bloring at lbl.gov] > *Sent:* Tuesday, March 17, 2015 2:17 PM > *To:* Scott, W Alan; paraview at paraview.org > *Subject:* Re: [EXTERNAL] Re: [Paraview] Trace recorder and presets > (color table) > > Hi Alan, > > The verbosity of the trace can be confusing, 90% of it is unnecessary, > and can be removed. Here's how it looks in your example with > unnecessary stuff removed and the 3 lines added to change the lut by name. > > #### import the simple module from the paraview > from paraview.simple import * > > #### disable automatic camera reset on 'Show' > paraview.simple._DisableFirstRenderCameraReset() > > # create a new 'Wavelet' > wavelet1 = Wavelet() > > # get active view > renderView1 = GetActiveViewOrCreate('RenderView') > > # uncomment following to set a specific view size > # renderView1.ViewSize = [856, 797] > > # show data in view > wavelet1Display = Show(wavelet1, renderView1) > > # change representation type > wavelet1Display.SetRepresentationType('Surface') > > *# change lookup table** > wavelet1Display.ColorArrayName = 'RTData' > w_arr = wavelet1.PointData.GetArray('RTData') > wavelet1Display.LookupTable = AssignLookupTable(w_arr, 'Rainbow > Blended White')* > > # show color bar/color legend > wavelet1Display.SetScalarBarVisibility(renderView1, True) > > # reset view to fit data > renderView1.ResetCamera() > > #### uncomment the following to render all views > # RenderAllViews() > # alternatively, if you want to write images, you can use > SaveScreenshot(...). > > On 03/17/2015 11:46 AM, Scott, W Alan wrote: > > Thanks Burlen! > > Obviously, my ParaView Python fu is weak. I tried to merge this > code into Python created by the trace recorder, but couldn?t. Say > a person does the following (which is sort of what my customer is > doing) : > > ?Trace recorder on. > > ?Wavelet. Apply. Surface. RTData. > > ?Color Editor/ Presets/ Blue to Red Rainbow. > > ?Trace Recorder off. > > The line setting Blue to Red Rainbow doesn?t get recorded. What > code would I paste in there? > > Here is the incorrect trace: > > #### import the simple module from the paraview > > from paraview.simple import * > > #### disable automatic camera reset on 'Show' > > paraview.simple._DisableFirstRenderCameraReset() > > # create a new 'Wavelet' > > wavelet1 = Wavelet() > > # get active view > > renderView1 = GetActiveViewOrCreate('RenderView') > > # uncomment following to set a specific view size > > # renderView1.ViewSize = [856, 797] > > # show data in view > > wavelet1Display = Show(wavelet1, renderView1) > > # trace defaults for the display properties. > > wavelet1Display.Representation = 'Outline' > > wavelet1Display.ColorArrayName = ['POINTS', ''] > > wavelet1Display.ScalarOpacityUnitDistance = 1.7320508075688779 > > wavelet1Display.Slice = 10 > > # reset view to fit data > > renderView1.ResetCamera() > > # change representation type > > wavelet1Display.SetRepresentationType('Surface') > > # set scalar coloring > > ColorBy(wavelet1Display, ('POINTS', 'RTData')) > > # rescale color and/or opacity maps used to include current data range > > wavelet1Display.RescaleTransferFunctionToDataRange(True) > > # show color bar/color legend > > wavelet1Display.SetScalarBarVisibility(renderView1, True) > > # get color transfer function/color map for 'RTData' > > rTDataLUT = GetColorTransferFunction('RTData') > > rTDataLUT.RGBPoints = [37.35310363769531, 0.231373, 0.298039, > 0.752941, 112.04112243652344, 0.865003, 0.865003, 0.865003, > 186.72914123535156, 0.705882, 0.0156863, 0.14902] > > rTDataLUT.ScalarRangeInitialized = 1.0 > > # get opacity transfer function/opacity map for 'RTData' > > rTDataPWF = GetOpacityTransferFunction('RTData') > > rTDataPWF.Points = [37.35310363769531, 0.0, 0.5, 0.0, > 186.72914123535156, 1.0, 0.5, 0.0] > > rTDataPWF.ScalarRangeInitialized = 1 > > #### saving camera placements for all active views > > # current camera placement for renderView1 > > renderView1.CameraPosition = [0.0, 0.0, 66.92130429902464] > > renderView1.CameraParallelScale = 17.320508075688775 > > #### uncomment the following to render all views > > # RenderAllViews() > > # alternatively, if you want to write images, you can use > SaveScreenshot(...). > > *From:*Burlen Loring [mailto:bloring at lbl.gov] > *Sent:* Monday, March 16, 2015 4:45 PM > *To:* Scott, W Alan; paraview at paraview.org > > *Subject:* [EXTERNAL] Re: [Paraview] Trace recorder and presets > (color table) > > Hi Alan, > > You can use the AssignLookupTable function to reference builtin > lookup tables by name. For example see code between # marks below. > There are a few other conveniences for working with the builtin > tables as well, see this recipe > > > w = Wavelet() > w_rep = Show(w) > w_rep.Representation = 'Surface' > # > w_rep.ColorArrayName = 'RTData' > w_arr = w.PointData.GetArray('RTData') > w_rep.LookupTable = AssignLookupTable(w_arr, 'Rainbow Blended White') > # > Render().ResetCamera() > > Burlen > > On 03/16/2015 03:14 PM, Scott, W Alan wrote: > > I have a user that needs to change the ParaView preset from > default (cool to warm) to another ParaView preset (Blue to Red > Rainbow). He wants to do this in a python trace. So, he used > the trace recorder to record his steps. Unfortunately, > changing presets is not recorded with the trace recorder. > > I have written this issue up as bug number > http://www.paraview.org/Bug/view.php?id=15116, but need to > give the user the code that would have/ should have been > produced. Does anyone have the python code that changes presets? > > Thanks all! > > Alan > > > > > > _______________________________________________ > > 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 dkxls23 at gmail.com Wed Mar 18 16:34:19 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Wed, 18 Mar 2015 22:34:19 +0200 Subject: [Paraview] Fetching data from xdmf temporal collection In-Reply-To: <55098d26.0857320a.741c.ffffad48SMTPIN_ADDED_BROKEN@mx.google.com> References: <2911E772881F8B4AB39462AA4A35EC5501019D8368@NL0230MBX12N2.DIR.slb.com> <55098d26.0857320a.741c.ffffad48SMTPIN_ADDED_BROKEN@mx.google.com> Message-ID: <5509E14B.3020701@gmail.com> I'm not quite sure what the problem here is. However, I think this is nothing XDMF specific, but rather a general question on how to access the raw data in ParaView at a certain time level. Am I correct with this Jean-Michel? I attached a script that simply loads a xdmf file, steps though all time-steps, renders the data and prints the min/max values of the selected field. There are probably better ways to do this though. Generally, I prefer to use VTK directly for such kind of tasks, especially with the new VTK dataset adapter [1]. -Armin [1] http://www.kitware.com/blog/home/post/709 On 03/18/2015 04:19 PM, Jean-Michel wrote: > Hi Ken, > > Thank you very much for offering your help. > Attached is the xmf file from which I'm trying to extract the data. I did > delete a fair amount of lines from it to keep only the first 10 time steps - > hope it won't affect anything. > > Jean-Michel > > -----Message d'origine----- > De : Ken Sheldon [mailto:KSheldon at slb.com] > Envoy? : mercredi 18 mars 2015 14:55 > ? : paraview at paraview.org > Cc : jm.lucas at gantha.com > Objet : RE: [Paraview] Fetching data from xdmf temporal collection > > Jean-Michel > I find the reader is very sensitive to input errors. The diagnostic messages > are not always sufficient to identify mistakes in the XDMF file. I spent > some time getting this to work for some our data. If you would like send me > a copy of your XDMF (not the HDF5), or at least the first few timesteps of > it, I would be happy to take a look. > ----Ken > > Date: Tue, 17 Mar 2015 17:46:08 +0100 > From: "Jean-Michel" > To: > Subject: [Paraview] Fetching data from xdmf temporal collection > Message-ID: <001b01d060d1$df435e70$9dca1b50$@lucas at gantha.com> > Content-Type: text/plain; charset="utf-8" > > Dear all, > > I am trying to fetch data out of a xdmf/h5 file. > > My xdmf file is a temporal collection and the xdmf reader recognizes the > time steps (index/values in the information block). > > I would like to access the point data for each time steps. However, I seem > to only get one time step when fetching the point data from the multi-block > dataset and I don't know how to iterate over the different time steps. > > Hope somebody can help. Thank you very much, > > Jean-Michel > > > --- > L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le logiciel antivirus Avast. > http://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 > -------------- next part -------------- A non-text attachment was scrubbed... Name: pvReadXDMF.py Type: text/x-python Size: 928 bytes Desc: not available URL: From dave.demarle at kitware.com Wed Mar 18 17:31:19 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 18 Mar 2015 17:31:19 -0400 Subject: [Paraview] Fetching data from xdmf temporal collection In-Reply-To: <5509E14B.3020701@gmail.com> References: <2911E772881F8B4AB39462AA4A35EC5501019D8368@NL0230MBX12N2.DIR.slb.com> <55098d26.0857320a.741c.ffffad48SMTPIN_ADDED_BROKEN@mx.google.com> <5509E14B.3020701@gmail.com> Message-ID: I agree with Armin. ParaView is mostly set up to look at a single time step at a time. I say mostly because a few filters (like temporal cache, temporal interpolator) work across the time dimension and those can request and thus access data from multiple time steps at the same time. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Mar 18, 2015 at 4:34 PM, Armin Wehrfritz wrote: > I'm not quite sure what the problem here is. > However, I think this is nothing XDMF specific, but rather a general > question on how to access the raw data in ParaView at a certain time level. > Am I correct with this Jean-Michel? > > I attached a script that simply loads a xdmf file, steps though all > time-steps, renders the data and prints the min/max values of the selected > field. > > There are probably better ways to do this though. > Generally, I prefer to use VTK directly for such kind of tasks, especially > with the new VTK dataset adapter [1]. > > -Armin > > > [1] http://www.kitware.com/blog/home/post/709 > > > > On 03/18/2015 04:19 PM, Jean-Michel wrote: > >> Hi Ken, >> >> Thank you very much for offering your help. >> Attached is the xmf file from which I'm trying to extract the data. I did >> delete a fair amount of lines from it to keep only the first 10 time >> steps - >> hope it won't affect anything. >> >> Jean-Michel >> >> -----Message d'origine----- >> De : Ken Sheldon [mailto:KSheldon at slb.com] >> Envoy? : mercredi 18 mars 2015 14:55 >> ? : paraview at paraview.org >> Cc : jm.lucas at gantha.com >> Objet : RE: [Paraview] Fetching data from xdmf temporal collection >> >> Jean-Michel >> I find the reader is very sensitive to input errors. The diagnostic >> messages >> are not always sufficient to identify mistakes in the XDMF file. I spent >> some time getting this to work for some our data. If you would like send >> me >> a copy of your XDMF (not the HDF5), or at least the first few timesteps of >> it, I would be happy to take a look. >> ----Ken >> >> Date: Tue, 17 Mar 2015 17:46:08 +0100 >> From: "Jean-Michel" >> To: >> Subject: [Paraview] Fetching data from xdmf temporal collection >> Message-ID: <001b01d060d1$df435e70$9dca1b50$@lucas at gantha.com> >> Content-Type: text/plain; charset="utf-8" >> >> Dear all, >> >> I am trying to fetch data out of a xdmf/h5 file. >> >> My xdmf file is a temporal collection and the xdmf reader recognizes the >> time steps (index/values in the information block). >> >> I would like to access the point data for each time steps. However, I seem >> to only get one time step when fetching the point data from the >> multi-block >> dataset and I don't know how to iterate over the different time steps. >> >> Hope somebody can help. Thank you very much, >> >> Jean-Michel >> >> >> --- >> L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le >> logiciel antivirus Avast. >> http://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 >> >> > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 rohitnarurkar at gmail.com Thu Mar 19 07:49:13 2015 From: rohitnarurkar at gmail.com (Rohit Narurkar) Date: Thu, 19 Mar 2015 17:19:13 +0530 Subject: [Paraview] Fluid Flow Simulation in ParaView In-Reply-To: References: Message-ID: Is there no simple feature or option that considers negative values as well? On Wed, Mar 18, 2015 at 5:50 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Try applying the "Glyph" filter or using the "Surface LIC" plugin[1] > > [1] http://www.paraview.org/Wiki/ParaView/Line_Integral_Convolution > > Utkarsh > > On Tue, Mar 17, 2015 at 8:37 AM, Rohit Narurkar > wrote: > > Hello > > > > I wish to simulate fluid flow using ParaView. I have 1000 .vtk files for > the > > 1000 time steps. > > I have attached along with this mail one of the .vtk files. When I open > this > > collection in ParaView, and change the 'coloring' to the velocity name I > > have given i.e. "VecVelocity" as you can see in the sample .vtk file. > There > > is another option to its right which offers 'magnitude', 'x', 'y' and > 'z'. > > But there are some points with negative velocities and ParaView is only > > considering the magnitude (hence positive). I wish to display even the > > negative values. How do I do that? > > > > Any help would be great! > > > > Thank you! > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mvanmoer at illinois.edu Thu Mar 19 09:50:53 2015 From: mvanmoer at illinois.edu (Vanmoer, Mark W) Date: Thu, 19 Mar 2015 13:50:53 +0000 Subject: [Paraview] server configuration with two factor authentication? Message-ID: <7F781841FF1E044388AFA42B70703A7A8A13A2B4@CITESMBX6.ad.uillinois.edu> Hi, is there a way to set up the server XML so that it works with two factor authentication, as in a token generator? This is for the Blue Waters machine at NCSA. What I mean is, something like how VisIt acts, which when doing the connection will prompt for the password and token. In the past, on machines without two factor auth, I've used http://www.paraview.org/Wiki/ParaView:Server_Configuration#Case_Eleven:_Launch_pvserver_on_a_cluster_using_PBS_-_use_reverse_connection_to_client but that requires having ssh keys set up. Thanks, Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Thu Mar 19 11:56:51 2015 From: burlen.loring at gmail.com (Burlen Loring) Date: Thu, 19 Mar 2015 08:56:51 -0700 Subject: [Paraview] server configuration with two factor authentication? In-Reply-To: <7F781841FF1E044388AFA42B70703A7A8A13A2B4@CITESMBX6.ad.uillinois.edu> References: <7F781841FF1E044388AFA42B70703A7A8A13A2B4@CITESMBX6.ad.uillinois.edu> Message-ID: <550AF1C3.8010707@gmail.com> Hi Mark, This works without anything special if you launch in an xterm. We did this at NICS which requires both ssh authentication and rsa secure id token. Here is an example Burlen On 03/19/2015 06:50 AM, Vanmoer, Mark W wrote: > > Hi, is there a way to set up the server XML so that it works with two > factor authentication, as in a token generator? This is for the Blue > Waters machine at NCSA. What I mean is, something like how VisIt acts, > which when doing the connection will prompt for the password and token. > > In the past, on machines without two factor auth, I?ve used > > http://www.paraview.org/Wiki/ParaView:Server_Configuration#Case_Eleven:_Launch_pvserver_on_a_cluster_using_PBS_-_use_reverse_connection_to_client > > but that requires having ssh keys set up. > > Thanks, > > 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: From dave.demarle at kitware.com Thu Mar 19 12:22:07 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 19 Mar 2015 12:22:07 -0400 Subject: [Paraview] server configuration with two factor authentication? In-Reply-To: <550AF1C3.8010707@gmail.com> References: <7F781841FF1E044388AFA42B70703A7A8A13A2B4@CITESMBX6.ad.uillinois.edu> <550AF1C3.8010707@gmail.com> Message-ID: Howdy Mark, Adding to what Burlen said. You can grab pvsc examples for ORNL, ANL and NERSC via paraview->File->Connect? Fetch servers. //File->Conenct?FetchServers->Edit Sources replace with pvsc http://www.paraview.org/files/pvscWindows Kitware Inc. on windows. Mac requires XQuartz, windows requires putty. Let me know when you get it working, with your permission I'ld love to add NCSA (and everywhere else) there so that users get it by default. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Mar 19, 2015 at 11:56 AM, Burlen Loring wrote: > Hi Mark, > > This works without anything special if you launch in an xterm. We did this > at NICS which requires both ssh authentication and rsa secure id token. > Here is an example > > > Burlen > > > On 03/19/2015 06:50 AM, Vanmoer, Mark W wrote: > > Hi, is there a way to set up the server XML so that it works with two > factor authentication, as in a token generator? This is for the Blue Waters > machine at NCSA. What I mean is, something like how VisIt acts, which when > doing the connection will prompt for the password and token. > > > > In the past, on machines without two factor auth, I?ve used > > > > > http://www.paraview.org/Wiki/ParaView:Server_Configuration#Case_Eleven:_Launch_pvserver_on_a_cluster_using_PBS_-_use_reverse_connection_to_client > > > > but that requires having ssh keys set up. > > > > Thanks, > > 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 > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 jm.lucas at gantha.com Thu Mar 19 12:47:11 2015 From: jm.lucas at gantha.com (Jean-Michel) Date: Thu, 19 Mar 2015 17:47:11 +0100 Subject: [Paraview] Fetching data from xdmf temporal collection Message-ID: <000601d06264$59308cb0$0b91a610$@lucas@gantha.com> Thank you very much Armin. The problem was indeed to access the raw data for a time dependant format. Using UpdatePipeline(timestep) allowed me to change the time step before fetching the data. It works fine, although using VTK directly might indeed be more efficient. Jean-Michel --- 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: From kevin.dean at decisionsciencescorp.com Thu Mar 19 13:43:19 2015 From: kevin.dean at decisionsciencescorp.com (Kevin Dean) Date: Thu, 19 Mar 2015 10:43:19 -0700 Subject: [Paraview] Use External VTK for ParaView Build Message-ID: Hi, my name is Kevin, I have recently tried building ParaView Source via external VTK. However, I seem to be running into a snag. For some reason, after my own "fun" debug process of external versus internal builds, it seems the problem comes from this section of ParaViewTopModule.cmake: foreach (source_dir IN LISTS PARAVIEW_MODULE_ROOTS) file(GLOB_RECURSE files RELATIVE "${CMAKE_CURRENT_SOURCE_DIR}" "${source_dir}/module.cmake") foreach (module_cmake IN LISTS files) get_filename_component(base "${module_cmake}" PATH) message(STATUS "MODULE_CMAKE ----> ${module_cmake}") if (PARAVIEW_USING_EXTERNAL_VTK) vtk_add_module( "${CMAKE_CURRENT_SOURCE_DIR}/${base}" module.cmake #"${CMAKE_CURRENT_BINARY_DIR}/${base}" ${_test_languages}) #message(STATUS "module ----> ${module}") #message(STATUS "CMAKE_CURRENT_BINARY_DIR ----> ${CMAKE_CURRENT_BINARY_DIR}") else() # Simply add to module-search paths for VTK and let VTK deal with it. vtk_add_to_module_search_path( "${CMAKE_CURRENT_SOURCE_DIR}/${base}" "${CMAKE_CURRENT_BINARY_DIR}/${base}") #message(STATUS "CMAKE_CURRENT_BINARY_DIR ----> ${CMAKE_CURRENT_BINARY_DIR}") endif() endforeach() endforeach() if (NOT PARAVIEW_USING_EXTERNAL_VTK) # include VTK set (old_build_examples ${BUILD_EXAMPLES}) message(STATUS "BUILD EXAMPLES ----> ${BUILD_EXAMPLES}") set (BUILD_EXAMPLES FALSE CACHE BOOL "" FORCE) add_subdirectory(VTK) set (BUILD_EXAMPLES ${old_build_examples} CACHE BOOL "" FORCE) include(${ParaView_BINARY_DIR}/VTK/VTKConfig.cmake) return() endif() it seems as if the CMakeLists.txt from the External VTK build is not being called. I figured this, because When calling vtkGroups.cmake (which is the next include process), I am only able to access 4 out of the 9 groups... i.e. I only have access to ParaView modules. Therefore, the add_subdirectory for these modules that will be loaded later fails. Is there another step that I should consider that I am not currently seeing? Or am I way off base? Thanks in advance! 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 kevin.dean at decisionsciencescorp.com Thu Mar 19 13:46:28 2015 From: kevin.dean at decisionsciencescorp.com (Kevin Dean) Date: Thu, 19 Mar 2015 10:46:28 -0700 Subject: [Paraview] Use External VTK for ParaView Build In-Reply-To: References: Message-ID: sorry, ParaViewModuleTop.cmake file... On Thu, Mar 19, 2015 at 10:43 AM, Kevin Dean < kevin.dean at decisionsciencescorp.com> wrote: > Hi, my name is Kevin, > > I have recently tried building ParaView Source via external VTK. However, > I seem to be running into a snag. For some reason, after my own "fun" debug > process of external versus internal builds, it seems the problem comes from > this section of ParaViewTopModule.cmake: > > foreach (source_dir IN LISTS PARAVIEW_MODULE_ROOTS) > file(GLOB_RECURSE files RELATIVE > "${CMAKE_CURRENT_SOURCE_DIR}" "${source_dir}/module.cmake") > foreach (module_cmake IN LISTS files) > get_filename_component(base "${module_cmake}" PATH) > message(STATUS "MODULE_CMAKE ----> ${module_cmake}") > if (PARAVIEW_USING_EXTERNAL_VTK) > vtk_add_module( > "${CMAKE_CURRENT_SOURCE_DIR}/${base}" > module.cmake > #"${CMAKE_CURRENT_BINARY_DIR}/${base}" > ${_test_languages}) > #message(STATUS "module ----> ${module}") > #message(STATUS "CMAKE_CURRENT_BINARY_DIR ----> > ${CMAKE_CURRENT_BINARY_DIR}") > else() > # Simply add to module-search paths for VTK and let VTK deal with it. > vtk_add_to_module_search_path( > "${CMAKE_CURRENT_SOURCE_DIR}/${base}" > "${CMAKE_CURRENT_BINARY_DIR}/${base}") > #message(STATUS "CMAKE_CURRENT_BINARY_DIR ----> > ${CMAKE_CURRENT_BINARY_DIR}") > endif() > endforeach() > endforeach() > > if (NOT PARAVIEW_USING_EXTERNAL_VTK) > # include VTK > set (old_build_examples ${BUILD_EXAMPLES}) > message(STATUS "BUILD EXAMPLES ----> ${BUILD_EXAMPLES}") > set (BUILD_EXAMPLES FALSE CACHE BOOL "" FORCE) > add_subdirectory(VTK) > set (BUILD_EXAMPLES ${old_build_examples} CACHE BOOL "" FORCE) > include(${ParaView_BINARY_DIR}/VTK/VTKConfig.cmake) > return() > endif() > > it seems as if the CMakeLists.txt from the External VTK build is not being > called. I figured this, because When calling vtkGroups.cmake (which is the > next include process), I am only able to access 4 out of the 9 groups... > i.e. I only have access to ParaView modules. Therefore, the > add_subdirectory for these modules that will be loaded later fails. Is > there another step that I should consider that I am not currently seeing? > Or am I way off base? Thanks in advance! > > 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 burlen.loring at gmail.com Thu Mar 19 14:18:46 2015 From: burlen.loring at gmail.com (Burlen Loring) Date: Thu, 19 Mar 2015 11:18:46 -0700 Subject: [Paraview] server configuration with two factor authentication? In-Reply-To: References: <7F781841FF1E044388AFA42B70703A7A8A13A2B4@CITESMBX6.ad.uillinois.edu> <550AF1C3.8010707@gmail.com> Message-ID: <550B1306.6000904@gmail.com> ""C:\Program Files (x86)\PuTTY\plink.exe"" so that's the secret to paths with spaces! nice, thanks for sharing that! On 03/19/2015 09:22 AM, David E DeMarle wrote: > Howdy Mark, > > Adding to what Burlen said. > > You can grab pvsc examples for ORNL, ANL and NERSC via > paraview->File->Connect? Fetch servers. > //File->Conenct?FetchServers->Edit Sources replace with pvsc > http://www.paraview.org/files/pvscWindows Kitware Inc. on windows. > Mac requires XQuartz, windows requires putty. > > Let me know when you get it working, with your permission I'ld love to > add NCSA (and everywhere else) there so that users get it by default. > > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Thu, Mar 19, 2015 at 11:56 AM, Burlen Loring > > wrote: > > Hi Mark, > > This works without anything special if you launch in an xterm. We > did this at NICS which requires both ssh authentication and rsa > secure id token. Here is an example > > > > Burlen > > > On 03/19/2015 06:50 AM, Vanmoer, Mark W wrote: >> >> Hi, is there a way to set up the server XML so that it works with >> two factor authentication, as in a token generator? This is for >> the Blue Waters machine at NCSA. What I mean is, something like >> how VisIt acts, which when doing the connection will prompt for >> the password and token. >> >> In the past, on machines without two factor auth, I?ve used >> >> http://www.paraview.org/Wiki/ParaView:Server_Configuration#Case_Eleven:_Launch_pvserver_on_a_cluster_using_PBS_-_use_reverse_connection_to_client >> >> but that requires having ssh keys set up. >> >> Thanks, >> >> Mark >> >> >> >> _______________________________________________ >> 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 dave.demarle at kitware.com Thu Mar 19 14:28:21 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 19 Mar 2015 14:28:21 -0400 Subject: [Paraview] server configuration with two factor authentication? In-Reply-To: <550B1306.6000904@gmail.com> References: <7F781841FF1E044388AFA42B70703A7A8A13A2B4@CITESMBX6.ad.uillinois.edu> <550AF1C3.8010707@gmail.com> <550B1306.6000904@gmail.com> Message-ID: I liked this bit too as the windows version 'xterm -e ssh &'. > so that's the secret to paths with spaces! nice, thanks for sharing that! > > On 03/19/2015 09:22 AM, David E DeMarle wrote: > > Howdy Mark, > > Adding to what Burlen said. > > You can grab pvsc examples for ORNL, ANL and NERSC via > paraview->File->Connect? Fetch servers. > //File->Conenct?FetchServers->Edit Sources replace with pvsc > http://www.paraview.org/files/pvscWindows Kitware Inc. on windows. > Mac requires XQuartz, windows requires putty. > > Let me know when you get it working, with your permission I'ld love to > add NCSA (and everywhere else) there so that users get it by default. > > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Thu, Mar 19, 2015 at 11:56 AM, Burlen Loring > wrote: > >> Hi Mark, >> >> This works without anything special if you launch in an xterm. We did >> this at NICS which requires both ssh authentication and rsa secure id >> token. Here is an example >> >> >> Burlen >> >> >> On 03/19/2015 06:50 AM, Vanmoer, Mark W wrote: >> >> Hi, is there a way to set up the server XML so that it works with two >> factor authentication, as in a token generator? This is for the Blue Waters >> machine at NCSA. What I mean is, something like how VisIt acts, which when >> doing the connection will prompt for the password and token. >> >> >> >> In the past, on machines without two factor auth, I?ve used >> >> >> >> >> http://www.paraview.org/Wiki/ParaView:Server_Configuration#Case_Eleven:_Launch_pvserver_on_a_cluster_using_PBS_-_use_reverse_connection_to_client >> >> >> >> but that requires having ssh keys set up. >> >> >> >> Thanks, >> >> 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 >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Mar 19 14:38:08 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 19 Mar 2015 14:38:08 -0400 Subject: [Paraview] Use External VTK for ParaView Build In-Reply-To: References: Message-ID: Kevin, This is not support yet. There is just place holder code, but it isn't intended to work. Utkarsh On Thu, Mar 19, 2015 at 1:46 PM, Kevin Dean wrote: > sorry, ParaViewModuleTop.cmake file... > > On Thu, Mar 19, 2015 at 10:43 AM, Kevin Dean > wrote: >> >> Hi, my name is Kevin, >> >> I have recently tried building ParaView Source via external VTK. However, >> I seem to be running into a snag. For some reason, after my own "fun" debug >> process of external versus internal builds, it seems the problem comes from >> this section of ParaViewTopModule.cmake: >> >> foreach (source_dir IN LISTS PARAVIEW_MODULE_ROOTS) >> file(GLOB_RECURSE files RELATIVE >> "${CMAKE_CURRENT_SOURCE_DIR}" "${source_dir}/module.cmake") >> foreach (module_cmake IN LISTS files) >> get_filename_component(base "${module_cmake}" PATH) >> message(STATUS "MODULE_CMAKE ----> ${module_cmake}") >> if (PARAVIEW_USING_EXTERNAL_VTK) >> vtk_add_module( >> "${CMAKE_CURRENT_SOURCE_DIR}/${base}" >> module.cmake >> #"${CMAKE_CURRENT_BINARY_DIR}/${base}" >> ${_test_languages}) >> #message(STATUS "module ----> ${module}") >> #message(STATUS "CMAKE_CURRENT_BINARY_DIR ----> >> ${CMAKE_CURRENT_BINARY_DIR}") >> else() >> # Simply add to module-search paths for VTK and let VTK deal with >> it. >> vtk_add_to_module_search_path( >> "${CMAKE_CURRENT_SOURCE_DIR}/${base}" >> "${CMAKE_CURRENT_BINARY_DIR}/${base}") >> #message(STATUS "CMAKE_CURRENT_BINARY_DIR ----> >> ${CMAKE_CURRENT_BINARY_DIR}") >> endif() >> endforeach() >> endforeach() >> >> if (NOT PARAVIEW_USING_EXTERNAL_VTK) >> # include VTK >> set (old_build_examples ${BUILD_EXAMPLES}) >> message(STATUS "BUILD EXAMPLES ----> ${BUILD_EXAMPLES}") >> set (BUILD_EXAMPLES FALSE CACHE BOOL "" FORCE) >> add_subdirectory(VTK) >> set (BUILD_EXAMPLES ${old_build_examples} CACHE BOOL "" FORCE) >> include(${ParaView_BINARY_DIR}/VTK/VTKConfig.cmake) >> return() >> endif() >> >> it seems as if the CMakeLists.txt from the External VTK build is not being >> called. I figured this, because When calling vtkGroups.cmake (which is the >> next include process), I am only able to access 4 out of the 9 groups... >> i.e. I only have access to ParaView modules. Therefore, the add_subdirectory >> for these modules that will be loaded later fails. Is there another step >> that I should consider that I am not currently seeing? Or am I way off base? >> Thanks in advance! >> >> Kevin E. Dean > > > > This email and its contents are confidential. If you are not the intended > recipient, please do not disclose or use the information within this email > or its attachments. If you have received this email in error, please report > the error to the sender by return email and delete this communication from > your records. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From samuelkey at bresnan.net Thu Mar 19 11:43:01 2015 From: samuelkey at bresnan.net (Samuel Key) Date: Thu, 19 Mar 2015 09:43:01 -0600 Subject: [Paraview] Fluid Flow Simulation in ParaView In-Reply-To: References: Message-ID: <550AEE85.9050102@bresnan.net> An HTML attachment was scrubbed... URL: From mvanmoer at illinois.edu Thu Mar 19 17:24:28 2015 From: mvanmoer at illinois.edu (Vanmoer, Mark W) Date: Thu, 19 Mar 2015 21:24:28 +0000 Subject: [Paraview] server configuration with two factor authentication? In-Reply-To: References: <7F781841FF1E044388AFA42B70703A7A8A13A2B4@CITESMBX6.ad.uillinois.edu> <550AF1C3.8010707@gmail.com> <550B1306.6000904@gmail.com> Message-ID: <7F781841FF1E044388AFA42B70703A7A8A141540@CITESMBX6.ad.uillinois.edu> This great, thanks for sharing, guys. Using xterm would have never occurred to me. Are you setting the pvserver ?client-host somehow? My old pvsc from Forge sent over the client?s hostname to the script. I tried that on Blue Waters and it works, but do I not need to actually do that? Also, are either of you setting ?server-port in the launch script? From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Thursday, March 19, 2015 1:28 PM To: Burlen Loring Cc: Vanmoer, Mark W; paraview at paraview.org Subject: Re: [Paraview] server configuration with two factor authentication? I liked this bit too as the windows version 'xterm -e ssh &'. File->Connect? Fetch servers. //File->Conenct?FetchServers->Edit Sources replace with pvsc http://www.paraview.org/files/pvscWindows Kitware Inc. on windows. Mac requires XQuartz, windows requires putty. Let me know when you get it working, with your permission I'ld love to add NCSA (and everywhere else) there so that users get it by default. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Mar 19, 2015 at 11:56 AM, Burlen Loring > wrote: Hi Mark, This works without anything special if you launch in an xterm. We did this at NICS which requires both ssh authentication and rsa secure id token. Here is an example Burlen On 03/19/2015 06:50 AM, Vanmoer, Mark W wrote: Hi, is there a way to set up the server XML so that it works with two factor authentication, as in a token generator? This is for the Blue Waters machine at NCSA. What I mean is, something like how VisIt acts, which when doing the connection will prompt for the password and token. In the past, on machines without two factor auth, I?ve used http://www.paraview.org/Wiki/ParaView:Server_Configuration#Case_Eleven:_Launch_pvserver_on_a_cluster_using_PBS_-_use_reverse_connection_to_client but that requires having ssh keys set up. Thanks, 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 _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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.d.lau at gmail.com Thu Mar 19 17:33:28 2015 From: kevin.d.lau at gmail.com (Kevin Lau) Date: Thu, 19 Mar 2015 17:33:28 -0400 Subject: [Paraview] Hardware suggestions for volume rendering In-Reply-To: References: Message-ID: Dear Aashish, Thanks for your reply, I've now managed to build ParaView from the Master branch with VTK_RENDERING_BACKEND set to OpenGL2 and I have noticed a visible difference in the rendering. However comparison of the rendering performance in the interactive mode of builds with the standard OpenGL backend vs the OpenGL2 backend, both show similar frame rates. Are there other build options that I'm missing? Should I be building the VTK libraries themselves? Many thanks, Kevin On 3 March 2015 at 14:53, Aashish Chaudhary wrote: > On Tue, Mar 3, 2015 at 2:43 PM, Kevin Lau wrote: > >> Dear Aashish, >> >> Thank you very much for your reply. The latest work you're doing on >> volume rendering is very impressive. >> > > Thanks. > >> >> In order to access the latest VTK rendering in ParaView would we have to >> compile both the latest VTK and ParaView from source? Is it possible to >> link ParaView to specific VTK builds? >> > > Latest ParaView from source should be fine. Just make sure that you select > VTK_RENDERING_BACKEND to OpenGL2 > >> >> Also do you know if it is preferential to have a single GPU (i.e. a >> workstation graphics card) or multiple GPU (i.e. gaming graphics card) when >> using ParaView? >> > > If I remember correctly, we don't explicitly assign tasks to GPU in > ParaView if running a single process. You can find more information here: > http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server#Multiple_GPUs_Per_Node > > Hope it helps. > >> >> Many thanks, >> >> Kevin >> >> >> On 27 February 2015 at 08:15, Aashish Chaudhary < >> aashish.chaudhary at kitware.com> wrote: >> >>> Dear Kevin, >>> >>> First, I would like to mention that we have been working hard to improve >>> rendering in VTK that includes volume rendering as well. You may want to >>> read this source article: http://www.kitware.com/source/home/post/154. >>> Most of the changes related to this work is now available in VTK github >>> repository in master branch. If you are targetting current VTK, I would >>> suggest that any card that can support OpenGL2.1 or higher would be great. >>> The higher the GPU memory the better. While these newer card will work with >>> the previous version of volume rendering, it may not scale very well (in >>> our testing that's what we have observed). Current the default in ParaView >>> is OpenGL Volume Rendering but that is going to change sometime soon and >>> once that happens you will have OpenGL2 backend for everything. >>> >>> Hope this helps. >>> - Aashish >>> >>> >>> >>> On Thu, Feb 26, 2015 at 5:41 PM, Kevin Lau >>> wrote: >>> >>>> Hi, >>>> >>>> I'm looking to putting together a workstation to perform realtime >>>> volume rendering of our simulation data. >>>> >>>> Are there any particular GPU features I should look for? >>>> >>>> If there are multiple GPUs will Paraview be able to take advantage of >>>> each GPU for volume rendering? >>>> >>>> Many thanks >>>> >>>> Kevin >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> 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 >>> * >>> >> >> > > > -- > > > > *| 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 Thu Mar 19 17:48:09 2015 From: burlen.loring at gmail.com (Burlen Loring) Date: Thu, 19 Mar 2015 14:48:09 -0700 Subject: [Paraview] server configuration with two factor authentication? In-Reply-To: <7F781841FF1E044388AFA42B70703A7A8A141540@CITESMBX6.ad.uillinois.edu> References: <7F781841FF1E044388AFA42B70703A7A8A13A2B4@CITESMBX6.ad.uillinois.edu> <550AF1C3.8010707@gmail.com> <550B1306.6000904@gmail.com> <7F781841FF1E044388AFA42B70703A7A8A141540@CITESMBX6.ad.uillinois.edu> Message-ID: <550B4419.8020301@gmail.com> Hi Mark, Yes to both. The way this could work on a simple cluster is: from the user's system which is assumed to be remote, the pvsc creates an ssh tunnel inside the xterm and calls the launch script on the compute system login node. the launch script submits the batch job. pvserver, when run in the batch script, connects back to the ssh tunnel on the login node. "client host" is the login node host name. "server port" is specified by the user in the pvsc. There's a slight complication with some Cray systems that means we need to involve a special node called the "mom" node in the tunnel. This will be clear if you see a complete example, for instance the following 3 scripts are used with NERSC's Cray Edison:pvsc , launch script , batch script . Burlen On 03/19/2015 02:24 PM, Vanmoer, Mark W wrote: > > This great, thanks for sharing, guys. Using xterm would have never > occurred to me. > > Are you setting the pvserver ?client-host somehow? My old pvsc from > Forge sent over the client?s hostname to the script. I tried that on > Blue Waters and it works, but do I not need to actually do that? Also, > are either of you setting ?server-port in the launch script? > > *From:*David E DeMarle [mailto:dave.demarle at kitware.com] > *Sent:* Thursday, March 19, 2015 1:28 PM > *To:* Burlen Loring > *Cc:* Vanmoer, Mark W; paraview at paraview.org > *Subject:* Re: [Paraview] server configuration with two factor > authentication? > > I liked this bit too as the windows version 'xterm -e ssh &'. > > > > > > > > > > > so that's the secret to paths with spaces! nice, thanks for sharing that! > > On 03/19/2015 09:22 AM, David E DeMarle wrote: > > Howdy Mark, > > Adding to what Burlen said. > > You can grab pvsc examples for ORNL, ANL and NERSC via > > paraview->File->Connect? Fetch servers. > > //File->Conenct?FetchServers->Edit Sources replace with pvsc > http://www.paraview.org/files/pvscWindows Kitware Inc. on windows. > > Mac requires XQuartz, windows requires putty. > > Let me know when you get it working, with your permission I'ld > love to add NCSA (and everywhere else) there so that users get > it by default. > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Thu, Mar 19, 2015 at 11:56 AM, Burlen Loring > > wrote: > > Hi Mark, > > This works without anything special if you launch in an > xterm. We did this at NICS which requires both ssh > authentication and rsa secure id token. Here is an example > > > > Burlen > > On 03/19/2015 06:50 AM, Vanmoer, Mark W wrote: > > Hi, is there a way to set up the server XML so that it > works with two factor authentication, as in a token > generator? This is for the Blue Waters machine at > NCSA. What I mean is, something like how VisIt acts, > which when doing the connection will prompt for the > password and token. > > In the past, on machines without two factor auth, I?ve > used > > http://www.paraview.org/Wiki/ParaView:Server_Configuration#Case_Eleven:_Launch_pvserver_on_a_cluster_using_PBS_-_use_reverse_connection_to_client > > but that requires having ssh keys set up. > > Thanks, > > Mark > > _______________________________________________ > > 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 biplabdutta27 at gmail.com Fri Mar 20 02:46:18 2015 From: biplabdutta27 at gmail.com (Biplab Dutta) Date: Fri, 20 Mar 2015 12:16:18 +0530 Subject: [Paraview] Paraview + Google Cardboard = 3D immersive data visualization Message-ID: Hi, I was wondering if one could use Google Cardboard along with a smartphone to do data visualization. I achieved this 3d stereoscopic visualization indirectly. I made an improved version of the cardboard myself which I call DOLLY VR. I start the paraview in stereo-type="SplitViewportHorizontal" on my desktop equipped with 3D monitor and Quadro4000 graphics card. I share the screen of my monitor using teamviewer on my smartphone. I then align the shared screen with divider on the VR. I can now see stereoscopic 3d on my DOLLY VR and navigate the data with the help of mouse. This process, I guess, can be simplified and made more direct using kiwiviewer to do the screen sharing and attaching the camera movement with the clicking of the magnetic trigger on the viewer so that one can fly inside the data and on another click can stop and look around as one can do it in Google earth demo in Google cardboard App. I would appreciate any comments or suggestions about the idea. Thanks and regards, Biplab Dutta Department of Physics, IIT Kanpur, India DOLLY VR fb: www.facebook.com/dolly.biplab -------------- next part -------------- An HTML attachment was scrubbed... URL: From mshoji-tky at umin.ac.jp Fri Mar 20 07:37:59 2015 From: mshoji-tky at umin.ac.jp (Masaaki SHOJIMA) Date: Fri, 20 Mar 2015 20:37:59 +0900 Subject: [Paraview] Fwd: Gradient of Unstructed dataset In-Reply-To: References: Message-ID: Hi Berk, "Gradient of Unstructured dataset" filter seems working nicely in your computer... I am using Paraview in MacOS Yosemite and Windows 7. In both setting, the computed gradinet values are half of Ensight and SC/Tetra post. Is your Paraview running in Linux ? Client information is also attached to show you my computer enviroment. Grad-P.vtm is attached with this mail. Gradient of Pressure was calculated with "Gradient of Unstructured dataset" filter, and saved as "VTK multi block files". Select "GradientOfUnstructuredDataSet1" in the pipeline browser, "File" -> "Save Data..." -> Files of type "VTK Multi Block Files (*.vtm)". I don't know how to "save out the output of the gradient filter as a .vtk file (or .vtu). If "vtm" is not suitable, please teach me how to output a vtk or vtu file. Thank you for your hard work and efforts very much. Masaaki (1) Client Information of my computer.pdf https://www.dropbox.com/s/u9f4pu84u5j347k/Client%20Information%20of%20my%20computer.pdf?dl=0 (2) Grad-P.vtm https://www.dropbox.com/s/g6lhwf6b01j7ma2/Grad-P.vtm?dl=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mshoji-tky at umin.ac.jp Fri Mar 20 08:00:24 2015 From: mshoji-tky at umin.ac.jp (Masaaki SHOJIMA) Date: Fri, 20 Mar 2015 21:00:24 +0900 Subject: [Paraview] Fwd: Gradient of Unstructed dataset In-Reply-To: References: Message-ID: Hi Berk, I found vtu file ! Its was created on my Desktop. Masaaki Grad-P_0_0.vtu https://www.dropbox.com/s/rhdkb20c965rvao/Grad-P_0_0.vtu?dl=0 GradP.vtm https://www.dropbox.com/s/g6lhwf6b01j7ma2/Grad-P.vtm?dl=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Fri Mar 20 10:33:42 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Fri, 20 Mar 2015 10:33:42 -0400 Subject: [Paraview] Hardware suggestions for volume rendering In-Reply-To: References: Message-ID: Hey Kevin, On Thu, Mar 19, 2015 at 5:33 PM, Kevin Lau wrote: > Dear Aashish, > > Thanks for your reply, I've now managed to build ParaView from the Master > branch with VTK_RENDERING_BACKEND set to OpenGL2 and I have noticed a > visible difference in the rendering. > > However comparison of the rendering performance in the interactive mode of > builds with the standard OpenGL backend vs the OpenGL2 backend, both show > similar frame rates. > Depending on the card and features you are using you may not see a huge bump in performance. On some systems we have seen 300 times performance improvements and on others there were close specially when you have VSync on. Said that, can you provide more infromation on 1) Data size 2) OS 3) Graphics card 4) Features you have enabled? 5) You expectation and problem 6) What SHA of ParaView you are using? Are there other build options that I'm missing? Should I be building the > VTK libraries themselves? > Just make sure that you built from a clean state other than that you should be good. Thanks, > Many thanks, > > Kevin > > > On 3 March 2015 at 14:53, Aashish Chaudhary > wrote: > >> On Tue, Mar 3, 2015 at 2:43 PM, Kevin Lau wrote: >> >>> Dear Aashish, >>> >>> Thank you very much for your reply. The latest work you're doing on >>> volume rendering is very impressive. >>> >> >> Thanks. >> >>> >>> In order to access the latest VTK rendering in ParaView would we have to >>> compile both the latest VTK and ParaView from source? Is it possible to >>> link ParaView to specific VTK builds? >>> >> >> Latest ParaView from source should be fine. Just make sure that you >> select VTK_RENDERING_BACKEND to OpenGL2 >> >>> >>> Also do you know if it is preferential to have a single GPU (i.e. a >>> workstation graphics card) or multiple GPU (i.e. gaming graphics card) when >>> using ParaView? >>> >> >> If I remember correctly, we don't explicitly assign tasks to GPU in >> ParaView if running a single process. You can find more information here: >> http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server#Multiple_GPUs_Per_Node >> >> Hope it helps. >> >>> >>> Many thanks, >>> >>> Kevin >>> >>> >>> On 27 February 2015 at 08:15, Aashish Chaudhary < >>> aashish.chaudhary at kitware.com> wrote: >>> >>>> Dear Kevin, >>>> >>>> First, I would like to mention that we have been working hard to >>>> improve rendering in VTK that includes volume rendering as well. You may >>>> want to read this source article: >>>> http://www.kitware.com/source/home/post/154. Most of the changes >>>> related to this work is now available in VTK github repository in master >>>> branch. If you are targetting current VTK, I would suggest that any card >>>> that can support OpenGL2.1 or higher would be great. The higher the GPU >>>> memory the better. While these newer card will work with the previous >>>> version of volume rendering, it may not scale very well (in our testing >>>> that's what we have observed). Current the default in ParaView is OpenGL >>>> Volume Rendering but that is going to change sometime soon and once that >>>> happens you will have OpenGL2 backend for everything. >>>> >>>> Hope this helps. >>>> - Aashish >>>> >>>> >>>> >>>> On Thu, Feb 26, 2015 at 5:41 PM, Kevin Lau >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> I'm looking to putting together a workstation to perform realtime >>>>> volume rendering of our simulation data. >>>>> >>>>> Are there any particular GPU features I should look for? >>>>> >>>>> If there are multiple GPUs will Paraview be able to take advantage of >>>>> each GPU for volume rendering? >>>>> >>>>> Many thanks >>>>> >>>>> Kevin >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> 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 >>>> * >>>> >>> >>> >> >> >> -- >> >> >> >> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >> * >> *| http://www.kitware.com/company/team/chaudhary.html >> * >> > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From etienne.tang at gmail.com Fri Mar 20 11:26:00 2015 From: etienne.tang at gmail.com (Etienne Tang) Date: Fri, 20 Mar 2015 16:26:00 +0100 Subject: [Paraview] Issue with structured grids and extraction of boundaries with cell data Message-ID: <550C3C08.2090101@gmail.com> Hello, I'm working with a 3D structured dataset containing cell data. I tried to extract a 2D boundary of this dataset corresponding to the maximum index of a dimension with the Extract Subset filter and ParaView 4.3.1, and I found an issue: the resulting dataset is incorrect. It holds cell data from the opposite boundary (eg. if I try to extract the i = imax boundary, I get values from i = 0 boundary), and these values are shifted of one index in the other dimensions. This case worked with ParaView 4.1.0, maybe it is related to this other bug about structured data : http://markmail.org/message/fvatgidqbvnufgi6#query:+page:1+mid:fvatgidqbvnufgi6+state:results ? Here are some pictures showing the problem on a simple dataset which can be used to reproduce it: - The simple .vts file : http://z1.gb2n.org/pv/test.vts - The original dataset : http://z1.gb2n.org/pv/original_dataset.png - The result of the ExtractSubset filter to extract the i = imax boundary : http://z1.gb2n.org/pv/extract_subset.png Best regards, -- Etienne Tang From kevin.d.lau at gmail.com Fri Mar 20 14:33:08 2015 From: kevin.d.lau at gmail.com (Kevin Lau) Date: Fri, 20 Mar 2015 14:33:08 -0400 Subject: [Paraview] Hardware suggestions for volume rendering In-Reply-To: References: Message-ID: Dear Aashish, Thanks for your reply. (1) We tried testing it with 2 different data sets of simulation data, one medium sized and one very large: Medium Cells: 1309489 Points: 247984 Memory [MB]: 119.179 Geometry [MB]: 8.201 Very Large Cells: 51937191 Points: 11019274 Memory [MB]: 4709.731 Geometry [MB]: 776.237 These datasets are unstructured grids (tetrahedral meshes) read into ParaView using the Phasta data reader. (2) The OS used was Ubuntu (3) The graphics card was a NVIDIA Quatro K6000 running the NVIDIA drivers from the Ubuntu Repos (v 331.113) (4) We configured ParaView using the default CMake options, changing VTK _RENDERING_BACKEND=OpenGL2 and disabling all the plug-ins. These tests were run in serial, as building with MPI was throwing errors. (5) We expected that the OpenGL2 version of ParaView would be able to volume render faster than the standard OpenGL version. However the reported frame rates were the same in both builds when clicking and dragging (~2 FPS). This is a problem because we're mainly interested in visualising our data and having users able to rotate the model and interact with it. At these frame rates the response is a bit sluggish. Also I've done serial test using an OpenGL2 build on Windows using an old GeForce 8800 with the same medium sized data. On this machine the frame rate was similar at around ~1.5 FPS. (6) ParaView was built by checking out the master from git. Sadly I'm not on that test machine now, so I can't check the SHA Many thanks for your help again. Kevin On 20 March 2015 at 10:33, Aashish Chaudhary wrote: > Hey Kevin, > > On Thu, Mar 19, 2015 at 5:33 PM, Kevin Lau wrote: > >> Dear Aashish, >> >> Thanks for your reply, I've now managed to build ParaView from the Master >> branch with VTK_RENDERING_BACKEND set to OpenGL2 and I have noticed a >> visible difference in the rendering. >> >> However comparison of the rendering performance in the interactive mode >> of builds with the standard OpenGL backend vs the OpenGL2 backend, both >> show similar frame rates. >> > > Depending on the card and features you are using you may not see a huge > bump in performance. On some systems we have seen 300 times performance > improvements and on others there were close specially when you have VSync > on. Said that, can you provide more infromation on > > 1) Data size > 2) OS > 3) Graphics card > 4) Features you have enabled? > 5) You expectation and problem > 6) What SHA of ParaView you are using? > > Are there other build options that I'm missing? Should I be building the >> VTK libraries themselves? >> > > Just make sure that you built from a clean state other than that you > should be good. > > Thanks, > > >> Many thanks, >> >> Kevin >> >> >> On 3 March 2015 at 14:53, Aashish Chaudhary < >> aashish.chaudhary at kitware.com> wrote: >> >>> On Tue, Mar 3, 2015 at 2:43 PM, Kevin Lau wrote: >>> >>>> Dear Aashish, >>>> >>>> Thank you very much for your reply. The latest work you're doing on >>>> volume rendering is very impressive. >>>> >>> >>> Thanks. >>> >>>> >>>> In order to access the latest VTK rendering in ParaView would we have >>>> to compile both the latest VTK and ParaView from source? Is it possible to >>>> link ParaView to specific VTK builds? >>>> >>> >>> Latest ParaView from source should be fine. Just make sure that you >>> select VTK_RENDERING_BACKEND to OpenGL2 >>> >>>> >>>> Also do you know if it is preferential to have a single GPU (i.e. a >>>> workstation graphics card) or multiple GPU (i.e. gaming graphics card) when >>>> using ParaView? >>>> >>> >>> If I remember correctly, we don't explicitly assign tasks to GPU in >>> ParaView if running a single process. You can find more information here: >>> http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server#Multiple_GPUs_Per_Node >>> >>> Hope it helps. >>> >>>> >>>> Many thanks, >>>> >>>> Kevin >>>> >>>> >>>> On 27 February 2015 at 08:15, Aashish Chaudhary < >>>> aashish.chaudhary at kitware.com> wrote: >>>> >>>>> Dear Kevin, >>>>> >>>>> First, I would like to mention that we have been working hard to >>>>> improve rendering in VTK that includes volume rendering as well. You may >>>>> want to read this source article: >>>>> http://www.kitware.com/source/home/post/154. Most of the changes >>>>> related to this work is now available in VTK github repository in master >>>>> branch. If you are targetting current VTK, I would suggest that any card >>>>> that can support OpenGL2.1 or higher would be great. The higher the GPU >>>>> memory the better. While these newer card will work with the previous >>>>> version of volume rendering, it may not scale very well (in our testing >>>>> that's what we have observed). Current the default in ParaView is OpenGL >>>>> Volume Rendering but that is going to change sometime soon and once that >>>>> happens you will have OpenGL2 backend for everything. >>>>> >>>>> Hope this helps. >>>>> - Aashish >>>>> >>>>> >>>>> >>>>> On Thu, Feb 26, 2015 at 5:41 PM, Kevin Lau >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I'm looking to putting together a workstation to perform realtime >>>>>> volume rendering of our simulation data. >>>>>> >>>>>> Are there any particular GPU features I should look for? >>>>>> >>>>>> If there are multiple GPUs will Paraview be able to take advantage of >>>>>> each GPU for volume rendering? >>>>>> >>>>>> Many thanks >>>>>> >>>>>> Kevin >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> 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 >>>>> * >>>>> >>>> >>>> >>> >>> >>> -- >>> >>> >>> >>> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >>> * >>> *| http://www.kitware.com/company/team/chaudhary.html >>> * >>> >> >> > > > -- > > > > *| Aashish Chaudhary | Technical Leader | Kitware Inc. * > *| http://www.kitware.com/company/team/chaudhary.html > * > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryan.abernathey at gmail.com Fri Mar 20 15:38:18 2015 From: ryan.abernathey at gmail.com (Ryan Abernathey) Date: Fri, 20 Mar 2015 15:38:18 -0400 Subject: [Paraview] colormap nan opacity Message-ID: Hi, I use paraview to render ocean model data. My datasets are usually rectilinear grids, cell data and / or point data. Frequently I want to mask points that are below the level of topography, so I usually set those points to NaN when preparing my data for paraview. I do a lot of volume rendering, so I am very familiar with the opacity mapping options within the colormap editor. The colormap editor allows you to choose your NaN color, but this dialog doesn't include an alpha / opacity option. Would that be difficult to add? It would really help me. Instead, what I have to do is use a clip filter to mask the NaNs, which ends up turning my rectilinear grid data into unstructure grid data, with significant performance and memory impacts. If NaNs could be made transparent at the level of the color map editor, it would make my pipeline much more efficient. Is this a feature that might be supported in future releases? Thanks, Ryan Abernathey -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.thompson at kitware.com Fri Mar 20 15:46:46 2015 From: david.thompson at kitware.com (David Thompson) Date: Fri, 20 Mar 2015 15:46:46 -0400 Subject: [Paraview] colormap nan opacity In-Reply-To: References: Message-ID: <898A359B-611B-49D5-A736-10DC2CF5B09B@kitware.com> Hi Ryan, > I use paraview to render ocean model data. My datasets are usually rectilinear grids ... > ... The colormap editor allows you to choose your NaN color, but this dialog doesn't include an alpha / opacity option. ... > Instead, what I have to do is use a clip filter to mask the NaNs, which ends up turning my rectilinear grid data into unstructure grid data, ... I haven't worked with rectilinear grids in a while... but at least one structured-data PV representation accepts a blanking array. Would it be possible to use that to cull cells instead of the NaN color? David From mvanmoer at illinois.edu Fri Mar 20 17:26:18 2015 From: mvanmoer at illinois.edu (Vanmoer, Mark W) Date: Fri, 20 Mar 2015 21:26:18 +0000 Subject: [Paraview] server configuration with two factor authentication? In-Reply-To: <550B4419.8020301@gmail.com> References: <7F781841FF1E044388AFA42B70703A7A8A13A2B4@CITESMBX6.ad.uillinois.edu> <550AF1C3.8010707@gmail.com> <550B1306.6000904@gmail.com> <7F781841FF1E044388AFA42B70703A7A8A141540@CITESMBX6.ad.uillinois.edu> <550B4419.8020301@gmail.com> Message-ID: <7F781841FF1E044388AFA42B70703A7A8A145851@CITESMBX6.ad.uillinois.edu> Hi Burlen, Are you using ncat to setup those connections because of a policy (like no outside network connections allowed) or for a technical reason? Mark From: Burlen Loring [mailto:burlen.loring at gmail.com] Sent: Thursday, March 19, 2015 4:48 PM To: Vanmoer, Mark W; David E DeMarle Cc: paraview at paraview.org Subject: Re: [Paraview] server configuration with two factor authentication? Hi Mark, Yes to both. The way this could work on a simple cluster is: from the user's system which is assumed to be remote, the pvsc creates an ssh tunnel inside the xterm and calls the launch script on the compute system login node. the launch script submits the batch job. pvserver, when run in the batch script, connects back to the ssh tunnel on the login node. "client host" is the login node host name. "server port" is specified by the user in the pvsc. There's a slight complication with some Cray systems that means we need to involve a special node called the "mom" node in the tunnel. This will be clear if you see a complete example, for instance the following 3 scripts are used with NERSC's Cray Edison: pvsc, launch script, batch script. Burlen On 03/19/2015 02:24 PM, Vanmoer, Mark W wrote: This great, thanks for sharing, guys. Using xterm would have never occurred to me. Are you setting the pvserver ?client-host somehow? My old pvsc from Forge sent over the client?s hostname to the script. I tried that on Blue Waters and it works, but do I not need to actually do that? Also, are either of you setting ?server-port in the launch script? From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Thursday, March 19, 2015 1:28 PM To: Burlen Loring Cc: Vanmoer, Mark W; paraview at paraview.org Subject: Re: [Paraview] server configuration with two factor authentication? I liked this bit too as the windows version 'xterm -e ssh &'. File->Connect? Fetch servers. //File->Conenct?FetchServers->Edit Sources replace with pvsc http://www.paraview.org/files/pvscWindows Kitware Inc. on windows. Mac requires XQuartz, windows requires putty. Let me know when you get it working, with your permission I'ld love to add NCSA (and everywhere else) there so that users get it by default. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Mar 19, 2015 at 11:56 AM, Burlen Loring > wrote: Hi Mark, This works without anything special if you launch in an xterm. We did this at NICS which requires both ssh authentication and rsa secure id token. Here is an example Burlen On 03/19/2015 06:50 AM, Vanmoer, Mark W wrote: Hi, is there a way to set up the server XML so that it works with two factor authentication, as in a token generator? This is for the Blue Waters machine at NCSA. What I mean is, something like how VisIt acts, which when doing the connection will prompt for the password and token. In the past, on machines without two factor auth, I?ve used http://www.paraview.org/Wiki/ParaView:Server_Configuration#Case_Eleven:_Launch_pvserver_on_a_cluster_using_PBS_-_use_reverse_connection_to_client but that requires having ssh keys set up. Thanks, 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 _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 Mar 20 17:42:22 2015 From: burlen.loring at gmail.com (Burlen Loring) Date: Fri, 20 Mar 2015 14:42:22 -0700 Subject: [Paraview] server configuration with two factor authentication? In-Reply-To: <7F781841FF1E044388AFA42B70703A7A8A145851@CITESMBX6.ad.uillinois.edu> References: <7F781841FF1E044388AFA42B70703A7A8A13A2B4@CITESMBX6.ad.uillinois.edu> <550AF1C3.8010707@gmail.com> <550B1306.6000904@gmail.com> <7F781841FF1E044388AFA42B70703A7A8A141540@CITESMBX6.ad.uillinois.edu> <550B4419.8020301@gmail.com> <7F781841FF1E044388AFA42B70703A7A8A145851@CITESMBX6.ad.uillinois.edu> Message-ID: <550C943E.4050009@gmail.com> there are 2 places I used netcat. 1) ssh policy on login node only allows us to connect to ssh tunnels from localhost. using ncat there fools ssh into thinking we are connecting on localhost. I think it's dumb that we have to do this, but our sys admins refuse to make the change. The ssh option is called GatewayPorts. 2) there is a different network protocol used on the compute nodes of our cray, the mom node understands that protocol and acts like a bridge to the login node. we create the tunnel from mom to login with netcat. there are other ways to forward the connections beside netcat, but it's easy to build, install, and use, and it's fast. On 03/20/2015 02:26 PM, Vanmoer, Mark W wrote: > > Hi Burlen, > > Are you using ncat to setup those connections because of a policy > (like no outside network connections allowed) or for a technical reason? > > Mark > > *From:*Burlen Loring [mailto:burlen.loring at gmail.com] > *Sent:* Thursday, March 19, 2015 4:48 PM > *To:* Vanmoer, Mark W; David E DeMarle > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] server configuration with two factor > authentication? > > Hi Mark, > > Yes to both. The way this could work on a simple cluster is: from the > user's system which is assumed to be remote, the pvsc creates an ssh > tunnel inside the xterm and calls the launch script on the compute > system login node. the launch script submits the batch job. pvserver, > when run in the batch script, connects back to the ssh tunnel on the > login node. "client host" is the login node host name. "server port" > is specified by the user in the pvsc. > > There's a slight complication with some Cray systems that means we > need to involve a special node called the "mom" node in the tunnel. > > This will be clear if you see a complete example, for instance the > following 3 scripts are used with NERSC's Cray Edison:pvsc > , > launch script > , > batch script > . > > Burlen > > On 03/19/2015 02:24 PM, Vanmoer, Mark W wrote: > > This great, thanks for sharing, guys. Using xterm would have never > occurred to me. > > Are you setting the pvserver ?client-host somehow? My old pvsc > from Forge sent over the client?s hostname to the script. I tried > that on Blue Waters and it works, but do I not need to actually do > that? Also, are either of you setting ?server-port in the launch > script? > > *From:*David E DeMarle [mailto:dave.demarle at kitware.com] > *Sent:* Thursday, March 19, 2015 1:28 PM > *To:* Burlen Loring > *Cc:* Vanmoer, Mark W; paraview at paraview.org > > *Subject:* Re: [Paraview] server configuration with two factor > authentication? > > I liked this bit too as the windows version 'xterm -e ssh &'. > > > > > > > > > > > so that's the secret to paths with spaces! nice, thanks for sharing that! > > On 03/19/2015 09:22 AM, David E DeMarle wrote: > > Howdy Mark, > > Adding to what Burlen said. > > You can grab pvsc examples for ORNL, ANL and NERSC via > > paraview->File->Connect? Fetch servers. > > //File->Conenct?FetchServers->Edit Sources replace with > pvsc http://www.paraview.org/files/pvscWindows Kitware > Inc. on windows. > > Mac requires XQuartz, windows requires putty. > > Let me know when you get it working, with your permission > I'ld love to add NCSA (and everywhere else) there so that > users get it by default. > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Thu, Mar 19, 2015 at 11:56 AM, Burlen Loring > > > wrote: > > Hi Mark, > > This works without anything special if you launch in > an xterm. We did this at NICS which requires both ssh > authentication and rsa secure id token. Here is an > example > > > > Burlen > > On 03/19/2015 06:50 AM, Vanmoer, Mark W wrote: > > Hi, is there a way to set up the server XML so > that it works with two factor authentication, as > in a token generator? This is for the Blue Waters > machine at NCSA. What I mean is, something like > how VisIt acts, which when doing the connection > will prompt for the password and token. > > In the past, on machines without two factor auth, > I?ve used > > http://www.paraview.org/Wiki/ParaView:Server_Configuration#Case_Eleven:_Launch_pvserver_on_a_cluster_using_PBS_-_use_reverse_connection_to_client > > but that requires having ssh keys set up. > > Thanks, > > Mark > > _______________________________________________ > > 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 utkarsh.ayachit at kitware.com Sat Mar 21 08:45:38 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sat, 21 Mar 2015 08:45:38 -0400 Subject: [Paraview] Dropping Snow Leopard OsX binaries for ParaView In-Reply-To: References: Message-ID: Folks, I'd like to revisit this thread to review if we still need to continue building binaries for 10.5 (Snow Leopard). Apple has stopped supporting it since February 26, 2014 (the last security update happened in September 2013). Utkarsh On Fri, Aug 22, 2014 at 10:37 AM, Utkarsh Ayachit wrote: > Sounds good, Rick. I'll shelve this proposal for now. We can revisit for 4.3. > > I'll look into renaming the OsX binaries to minimize confusion. > > Utkarsh > > > > On Fri, Aug 22, 2014 at 9:21 AM, Angelini, Richard C (Rick) CIV USARMY > ARL (US) wrote: >> Classification: UNCLASSIFIED >> Caveats: NONE >> >> Utkarsh - unfortunately, we still have a number of Macs that are still >> running 10.6 and are using ParaView. We'd like to use the pre-built >> binaries for the next ParaView release on these machines if possible. We >> currently don't build from source for the Macs, so that could be a real >> challenge for us if we needed to start doing that ..... We're pushing >> hard to get these 10.6 systems either replaced or upgraded in the near >> future, but not soon enough. >> >> ----------------------------------------------------------------- >> >> Folks, >> >> I wanted to get a quick survey if anyone cares if we drop support for >> distributing ParaVIew binaries compatible with Snow Leopard. Lion on >> wards will still be supported. >> >> There are two OsX binaries for ParaView currently and it can be a >> little confusing which one to use and why and hence this change. >> >> Utkarsh >> >> ________________________________ >> Rick Angelini >> USArmy Research Laboratory >> CISD/HPC Architectures Team >> Phone: 410-278-6266 >> >> >> >> Classification: UNCLASSIFIED >> Caveats: NONE >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> From dave.demarle at kitware.com Sat Mar 21 12:15:23 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Sat, 21 Mar 2015 12:15:23 -0400 Subject: [Paraview] server configuration with two factor authentication? In-Reply-To: <550C943E.4050009@gmail.com> References: <7F781841FF1E044388AFA42B70703A7A8A13A2B4@CITESMBX6.ad.uillinois.edu> <550AF1C3.8010707@gmail.com> <550B1306.6000904@gmail.com> <7F781841FF1E044388AFA42B70703A7A8A141540@CITESMBX6.ad.uillinois.edu> <550B4419.8020301@gmail.com> <7F781841FF1E044388AFA42B70703A7A8A145851@CITESMBX6.ad.uillinois.edu> <550C943E.4050009@gmail.com> Message-ID: I use a tiny executable called SocketRelay for the same purpose. We borrowed it from VisIt. On Mar 20, 2015 5:42 PM, "Burlen Loring" wrote: > there are 2 places I used netcat. > > 1) ssh policy on login node only allows us to connect to ssh tunnels from > localhost. using ncat there fools ssh into thinking we are connecting on > localhost. I think it's dumb that we have to do this, but our sys admins > refuse to make the change. The ssh option is called GatewayPorts. > > 2) there is a different network protocol used on the compute nodes of our > cray, the mom node understands that protocol and acts like a bridge to the > login node. we create the tunnel from mom to login with netcat. > > there are other ways to forward the connections beside netcat, but it's > easy to build, install, and use, and it's fast. > > On 03/20/2015 02:26 PM, Vanmoer, Mark W wrote: > > Hi Burlen, > > > > Are you using ncat to setup those connections because of a policy (like no > outside network connections allowed) or for a technical reason? > > > > Mark > > *From:* Burlen Loring [mailto:burlen.loring at gmail.com > ] > *Sent:* Thursday, March 19, 2015 4:48 PM > *To:* Vanmoer, Mark W; David E DeMarle > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] server configuration with two factor > authentication? > > > > Hi Mark, > > Yes to both. The way this could work on a simple cluster is: from the > user's system which is assumed to be remote, the pvsc creates an ssh tunnel > inside the xterm and calls the launch script on the compute system login > node. the launch script submits the batch job. pvserver, when run in the > batch script, connects back to the ssh tunnel on the login node. "client > host" is the login node host name. "server port" is specified by the user > in the pvsc. > > There's a slight complication with some Cray systems that means we need to > involve a special node called the "mom" node in the tunnel. > > This will be clear if you see a complete example, for instance the > following 3 scripts are used with NERSC's Cray Edison: pvsc > , > launch script > , > batch script > > . > > Burlen > > On 03/19/2015 02:24 PM, Vanmoer, Mark W wrote: > > This great, thanks for sharing, guys. Using xterm would have never > occurred to me. > > > > Are you setting the pvserver ?client-host somehow? My old pvsc from Forge > sent over the client?s hostname to the script. I tried that on Blue Waters > and it works, but do I not need to actually do that? Also, are either of > you setting ?server-port in the launch script? > > > > > > *From:* David E DeMarle [mailto:dave.demarle at kitware.com > ] > *Sent:* Thursday, March 19, 2015 1:28 PM > *To:* Burlen Loring > *Cc:* Vanmoer, Mark W; paraview at paraview.org > *Subject:* Re: [Paraview] server configuration with two factor > authentication? > > > > I liked this bit too as the windows version 'xterm -e ssh &'. > > > > > > > > > > > so that's the secret to paths with spaces! nice, thanks for sharing that! > > On 03/19/2015 09:22 AM, David E DeMarle wrote: > > Howdy Mark, > > > > Adding to what Burlen said. > > > > You can grab pvsc examples for ORNL, ANL and NERSC via > > paraview->File->Connect? Fetch servers. > > //File->Conenct?FetchServers->Edit Sources replace with pvsc > http://www.paraview.org/files/pvscWindows Kitware Inc. on windows. > > Mac requires XQuartz, windows requires putty. > > > > Let me know when you get it working, with your permission I'ld love to add > NCSA (and everywhere else) there so that users get it by default. > > > > > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > > On Thu, Mar 19, 2015 at 11:56 AM, Burlen Loring > wrote: > > Hi Mark, > > This works without anything special if you launch in an xterm. We did this > at NICS which requires both ssh authentication and rsa secure id token. > Here is an example > > > Burlen > > > > On 03/19/2015 06:50 AM, Vanmoer, Mark W wrote: > > Hi, is there a way to set up the server XML so that it works with two > factor authentication, as in a token generator? This is for the Blue Waters > machine at NCSA. What I mean is, something like how VisIt acts, which when > doing the connection will prompt for the password and token. > > > > In the past, on machines without two factor auth, I?ve used > > > > > http://www.paraview.org/Wiki/ParaView:Server_Configuration#Case_Eleven:_Launch_pvserver_on_a_cluster_using_PBS_-_use_reverse_connection_to_client > > > > but that requires having ssh keys set up. > > > > Thanks, > > 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 > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Mar 23 00:01:11 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 23 Mar 2015 00:01:11 -0400 Subject: [Paraview] Build error on Windows In-Reply-To: <550C19C0.30205@tu-braunschweig.de> References: <5500ADA4.102@tu-braunschweig.de> <550C19C0.30205@tu-braunschweig.de> Message-ID: I think the real problem is the errors like this: 7>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppBuild.targets(388,5): warning MSB8028: The intermediate directory (x64\Debug\) contains files shared from another project (vtkWrapPythonInit.vcxproj, vtkWrappingTools.vcxproj). This can lead to incorrect clean and rebuild behavior. 7> Building Custom Rule D:/ParaView/ParaView/VTK/Wrapping/Tools/CMakeLists.txt 7> CMake does not need to re-run because D:\ParaView\pv-4.3.1-git\VTK\Wrapping\Tools\CMakeFiles\generate.stamp is up-to-date. 7> vtkWrapHierarchy.c 5> lq.cpp 3> EncodingC.c 7>LINK : fatal error LNK1104: cannot open file '..\..\..\lib\Debug\vtkWrappingTools-pv4.3.lib' I have no idea why that's happening. Maybe someone more familiar with VS knows. I am not sure if there are any issues with the source and build directories being on different drives. Try moving both the same drive, to see if that helps -- but that's just a wild guess. Utkarsh On Fri, Mar 20, 2015 at 8:59 AM, Ian Krukow wrote: > Ok, I tried it again from scratch (with a fresh download), but I have the > same issue. I also tried to build the git version, but it is the same too. > > I attach the log file from Visual Studio and the CMakeCache.txt. Maybe I > missed something in the settings causing this problem? The error I mentioned > is the first 'fatal error' in the log file in line 343. > > Ian > > > Am 18.03.2015 um 16:27 schrieb Utkarsh Ayachit: > >> Not entirely sure what the problem could be. The latest master seems >> to build fine with VS 2013. Maybe it's a parallel build issue? Try >> kicking the build off again. >> >> Utkarsh >> >> On Wed, Mar 11, 2015 at 5:03 PM, Ian Krukow >> wrote: >>> >>> Hi all, >>> >>> I am trying to build ParaView on Windows, but I get the following error, >>> and >>> I have no idea what it means or how to fix it: >>> >>> >>> 4>C:\ParaView\ParaView-v4.3.1-source\VTK\Wrapping\Tools\vtkWrapPythonInit.c >>> : fatal error C1041: cannot open program database >>> 'c:\paraview\pv\vtk\wrapping\tools\x64\debug\vc120.pdb'; if multiple >>> CL.EXE >>> write to the same .PDB file, please use /FS >>> >>> I use ParaView 4.3.1 source code and Visual Studio 2013. >>> Can anyone help me? >>> >>> Kind regards >>> Ian >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> 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 i.krukow at tu-braunschweig.de Mon Mar 23 05:14:28 2015 From: i.krukow at tu-braunschweig.de (Ian Krukow) Date: Mon, 23 Mar 2015 10:14:28 +0100 Subject: [Paraview] Build error on Windows In-Reply-To: References: <5500ADA4.102@tu-braunschweig.de> <550C19C0.30205@tu-braunschweig.de> Message-ID: <550FD974.7040904@tu-braunschweig.de> The build and source directory are on the same drive, only it is not the system drive (where VS lies). But I had them both on the system drive at first, and it was the same. Any other ideas? Ian Am 23.03.2015 um 05:01 schrieb Utkarsh Ayachit: > I think the real problem is the errors like this: > > 7>C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppBuild.targets(388,5): > warning MSB8028: The intermediate directory (x64\Debug\) contains > files shared from another project (vtkWrapPythonInit.vcxproj, > vtkWrappingTools.vcxproj). This can lead to incorrect clean and > rebuild behavior. > 7> Building Custom Rule D:/ParaView/ParaView/VTK/Wrapping/Tools/CMakeLists.txt > 7> CMake does not need to re-run because > D:\ParaView\pv-4.3.1-git\VTK\Wrapping\Tools\CMakeFiles\generate.stamp > is up-to-date. > 7> vtkWrapHierarchy.c 5> lq.cpp 3> EncodingC.c > 7>LINK : fatal error LNK1104: cannot open file > '..\..\..\lib\Debug\vtkWrappingTools-pv4.3.lib' > > I have no idea why that's happening. Maybe someone more familiar with VS knows. > > I am not sure if there are any issues with the source and build > directories being on different drives. Try moving both the same drive, > to see if that helps -- but that's just a wild guess. > > Utkarsh > > On Fri, Mar 20, 2015 at 8:59 AM, Ian Krukow wrote: >> Ok, I tried it again from scratch (with a fresh download), but I have the >> same issue. I also tried to build the git version, but it is the same too. >> >> I attach the log file from Visual Studio and the CMakeCache.txt. Maybe I >> missed something in the settings causing this problem? The error I mentioned >> is the first 'fatal error' in the log file in line 343. >> >> Ian >> >> >> Am 18.03.2015 um 16:27 schrieb Utkarsh Ayachit: >> >>> Not entirely sure what the problem could be. The latest master seems >>> to build fine with VS 2013. Maybe it's a parallel build issue? Try >>> kicking the build off again. >>> >>> Utkarsh >>> >>> On Wed, Mar 11, 2015 at 5:03 PM, Ian Krukow >>> wrote: >>>> >>>> Hi all, >>>> >>>> I am trying to build ParaView on Windows, but I get the following error, >>>> and >>>> I have no idea what it means or how to fix it: >>>> >>>> >>>> 4>C:\ParaView\ParaView-v4.3.1-source\VTK\Wrapping\Tools\vtkWrapPythonInit.c >>>> : fatal error C1041: cannot open program database >>>> 'c:\paraview\pv\vtk\wrapping\tools\x64\debug\vc120.pdb'; if multiple >>>> CL.EXE >>>> write to the same .PDB file, please use /FS >>>> >>>> I use ParaView 4.3.1 source code and Visual Studio 2013. >>>> Can anyone help me? >>>> >>>> Kind regards >>>> Ian >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> 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 Mar 23 06:17:54 2015 From: stefano.zaghi at gmail.com (Stefano Zaghi) Date: Mon, 23 Mar 2015 11:17:54 +0100 Subject: [Paraview] A VTS file producing a Segmentation fault Message-ID: Hi all, I have a problem with the VTS file attached. If I load it importing all cell variables Paraview exits with "Segmentation fault (core dumped) paraview", whereas if I import all cell variables until "f0" (included) Paraview works well. I am using Paraview v4.3.1 64 bit (pre-compiled binary), with Qt 4.8.6 on an Arch Linux with 3.18.6-1 kernel. Can anyone give me a deep insight of what is wrong with this file? Thank you for any suggestions. 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 *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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ptc_001_n_00001_blk_0063_fac_5_grp_000.vts Type: application/octet-stream Size: 192489 bytes Desc: not available URL: From cory.quammen at kitware.com Mon Mar 23 06:49:00 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 23 Mar 2015 06:49:00 -0400 Subject: [Paraview] Build error on Windows In-Reply-To: <550FD974.7040904@tu-braunschweig.de> References: <5500ADA4.102@tu-braunschweig.de> <550C19C0.30205@tu-braunschweig.de> <550FD974.7040904@tu-braunschweig.de> Message-ID: Ian, Do you have more than one instance of Visual Studio 2013 running with the ParaView solution file loaded (that might explain the writing to PDB warning in your first message). Which version of CMake are you using? - Cory On Mon, Mar 23, 2015 at 5:14 AM, Ian Krukow wrote: > The build and source directory are on the same drive, only it is not the > system drive (where VS lies). But I had them both on the system drive at > first, and it was the same. > > Any other ideas? > > Ian > > > Am 23.03.2015 um 05:01 schrieb Utkarsh Ayachit: > >> I think the real problem is the errors like this: >> >> 7>C:\Program Files >> (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppBuild.targets(388,5): >> warning MSB8028: The intermediate directory (x64\Debug\) contains >> files shared from another project (vtkWrapPythonInit.vcxproj, >> vtkWrappingTools.vcxproj). This can lead to incorrect clean and >> rebuild behavior. >> 7> Building Custom Rule >> D:/ParaView/ParaView/VTK/Wrapping/Tools/CMakeLists.txt >> 7> CMake does not need to re-run because >> D:\ParaView\pv-4.3.1-git\VTK\Wrapping\Tools\CMakeFiles\generate.stamp >> is up-to-date. >> 7> vtkWrapHierarchy.c 5> lq.cpp 3> EncodingC.c >> 7>LINK : fatal error LNK1104: cannot open file >> '..\..\..\lib\Debug\vtkWrappingTools-pv4.3.lib' >> >> I have no idea why that's happening. Maybe someone more familiar with VS >> knows. >> >> I am not sure if there are any issues with the source and build >> directories being on different drives. Try moving both the same drive, >> to see if that helps -- but that's just a wild guess. >> >> Utkarsh >> >> On Fri, Mar 20, 2015 at 8:59 AM, Ian Krukow >> wrote: >>> >>> Ok, I tried it again from scratch (with a fresh download), but I have the >>> same issue. I also tried to build the git version, but it is the same >>> too. >>> >>> I attach the log file from Visual Studio and the CMakeCache.txt. Maybe I >>> missed something in the settings causing this problem? The error I >>> mentioned >>> is the first 'fatal error' in the log file in line 343. >>> >>> Ian >>> >>> >>> Am 18.03.2015 um 16:27 schrieb Utkarsh Ayachit: >>> >>>> Not entirely sure what the problem could be. The latest master seems >>>> to build fine with VS 2013. Maybe it's a parallel build issue? Try >>>> kicking the build off again. >>>> >>>> Utkarsh >>>> >>>> On Wed, Mar 11, 2015 at 5:03 PM, Ian Krukow >>>> >>>> wrote: >>>>> >>>>> >>>>> Hi all, >>>>> >>>>> I am trying to build ParaView on Windows, but I get the following >>>>> error, >>>>> and >>>>> I have no idea what it means or how to fix it: >>>>> >>>>> >>>>> >>>>> 4>C:\ParaView\ParaView-v4.3.1-source\VTK\Wrapping\Tools\vtkWrapPythonInit.c >>>>> : fatal error C1041: cannot open program database >>>>> 'c:\paraview\pv\vtk\wrapping\tools\x64\debug\vc120.pdb'; if multiple >>>>> CL.EXE >>>>> write to the same .PDB file, please use /FS >>>>> >>>>> I use ParaView 4.3.1 source code and Visual Studio 2013. >>>>> Can anyone help me? >>>>> >>>>> Kind regards >>>>> Ian >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -- Cory Quammen R&D Engineer Kitware, Inc. From jm.lucas at gantha.com Mon Mar 23 09:15:33 2015 From: jm.lucas at gantha.com (Jean-Michel) Date: Mon, 23 Mar 2015 14:15:33 +0100 Subject: [Paraview] Fetching data from xdmf temporal collection Message-ID: <000001d0656b$71d70f50$55852df0$@lucas@gantha.com> Armin, you said you would rather use vtk directly to access raw data in xdmf files. I tried to follow your advice, but I struggle with the vtkXdmfReader. Basically, here is what I do: import vtk reader = vtk.vtkXdmfReader() reader.SetFileName(myfile) reader.ReadAllScalarsOn() reader.Update() However, I don't know how to access the data inside reader once this is done. The GetOutput() method doesn't seem to work. Do you know what I am missing here ? If not, I'll try and move the discussion over at the vtk-users list. Thank you for your help. Jean-Michel --- 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: From mvanmoer at illinois.edu Mon Mar 23 10:33:42 2015 From: mvanmoer at illinois.edu (Vanmoer, Mark W) Date: Mon, 23 Mar 2015 14:33:42 +0000 Subject: [Paraview] server configuration with two factor authentication? In-Reply-To: References: <7F781841FF1E044388AFA42B70703A7A8A13A2B4@CITESMBX6.ad.uillinois.edu> <550AF1C3.8010707@gmail.com> <550B1306.6000904@gmail.com> <7F781841FF1E044388AFA42B70703A7A8A141540@CITESMBX6.ad.uillinois.edu> <550B4419.8020301@gmail.com> <7F781841FF1E044388AFA42B70703A7A8A145851@CITESMBX6.ad.uillinois.edu> <550C943E.4050009@gmail.com> Message-ID: <7F781841FF1E044388AFA42B70703A7A8A152E46@CHIMBX6.ad.uillinois.edu> Okay, makes sense. I wanted to make sure I understood every step. BW has a more lenient policy on connections from the compute nodes because the VisIt maintainer put in the hard work of getting them to change it. From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Saturday, March 21, 2015 11:15 AM To: burlen Cc: paraview at paraview.org; Vanmoer, Mark W Subject: Re: [Paraview] server configuration with two factor authentication? I use a tiny executable called SocketRelay for the same purpose. We borrowed it from VisIt. On Mar 20, 2015 5:42 PM, "Burlen Loring" > wrote: there are 2 places I used netcat. 1) ssh policy on login node only allows us to connect to ssh tunnels from localhost. using ncat there fools ssh into thinking we are connecting on localhost. I think it's dumb that we have to do this, but our sys admins refuse to make the change. The ssh option is called GatewayPorts. 2) there is a different network protocol used on the compute nodes of our cray, the mom node understands that protocol and acts like a bridge to the login node. we create the tunnel from mom to login with netcat. there are other ways to forward the connections beside netcat, but it's easy to build, install, and use, and it's fast. On 03/20/2015 02:26 PM, Vanmoer, Mark W wrote: Hi Burlen, Are you using ncat to setup those connections because of a policy (like no outside network connections allowed) or for a technical reason? Mark From: Burlen Loring [mailto:burlen.loring at gmail.com] Sent: Thursday, March 19, 2015 4:48 PM To: Vanmoer, Mark W; David E DeMarle Cc: paraview at paraview.org Subject: Re: [Paraview] server configuration with two factor authentication? Hi Mark, Yes to both. The way this could work on a simple cluster is: from the user's system which is assumed to be remote, the pvsc creates an ssh tunnel inside the xterm and calls the launch script on the compute system login node. the launch script submits the batch job. pvserver, when run in the batch script, connects back to the ssh tunnel on the login node. "client host" is the login node host name. "server port" is specified by the user in the pvsc. There's a slight complication with some Cray systems that means we need to involve a special node called the "mom" node in the tunnel. This will be clear if you see a complete example, for instance the following 3 scripts are used with NERSC's Cray Edison: pvsc, launch script, batch script. Burlen On 03/19/2015 02:24 PM, Vanmoer, Mark W wrote: This great, thanks for sharing, guys. Using xterm would have never occurred to me. Are you setting the pvserver ?client-host somehow? My old pvsc from Forge sent over the client?s hostname to the script. I tried that on Blue Waters and it works, but do I not need to actually do that? Also, are either of you setting ?server-port in the launch script? From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Thursday, March 19, 2015 1:28 PM To: Burlen Loring Cc: Vanmoer, Mark W; paraview at paraview.org Subject: Re: [Paraview] server configuration with two factor authentication? I liked this bit too as the windows version 'xterm -e ssh &'. File->Connect? Fetch servers. //File->Conenct?FetchServers->Edit Sources replace with pvsc http://www.paraview.org/files/pvscWindows Kitware Inc. on windows. Mac requires XQuartz, windows requires putty. Let me know when you get it working, with your permission I'ld love to add NCSA (and everywhere else) there so that users get it by default. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Mar 19, 2015 at 11:56 AM, Burlen Loring > wrote: Hi Mark, This works without anything special if you launch in an xterm. We did this at NICS which requires both ssh authentication and rsa secure id token. Here is an example Burlen On 03/19/2015 06:50 AM, Vanmoer, Mark W wrote: Hi, is there a way to set up the server XML so that it works with two factor authentication, as in a token generator? This is for the Blue Waters machine at NCSA. What I mean is, something like how VisIt acts, which when doing the connection will prompt for the password and token. In the past, on machines without two factor auth, I?ve used http://www.paraview.org/Wiki/ParaView:Server_Configuration#Case_Eleven:_Launch_pvserver_on_a_cluster_using_PBS_-_use_reverse_connection_to_client but that requires having ssh keys set up. Thanks, 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 _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 i.krukow at tu-braunschweig.de Mon Mar 23 10:42:42 2015 From: i.krukow at tu-braunschweig.de (Ian Krukow) Date: Mon, 23 Mar 2015 15:42:42 +0100 Subject: [Paraview] Build error on Windows In-Reply-To: References: <5500ADA4.102@tu-braunschweig.de> <550C19C0.30205@tu-braunschweig.de> <550FD974.7040904@tu-braunschweig.de> Message-ID: <55102662.2050303@tu-braunschweig.de> Hi Cory, I never had more than one instance of Visual Studio 2013 running. I am using CMake 3.1.0. Ian Am 23.03.2015 um 11:49 schrieb Cory Quammen: > Ian, > > Do you have more than one instance of Visual Studio 2013 running with > the ParaView solution file loaded (that might explain the writing to > PDB warning in your first message). > > Which version of CMake are you using? > > - Cory > > On Mon, Mar 23, 2015 at 5:14 AM, Ian Krukow wrote: >> The build and source directory are on the same drive, only it is not the >> system drive (where VS lies). But I had them both on the system drive at >> first, and it was the same. >> >> Any other ideas? >> >> Ian >> >> >> Am 23.03.2015 um 05:01 schrieb Utkarsh Ayachit: >> >>> I think the real problem is the errors like this: >>> >>> 7>C:\Program Files >>> (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppBuild.targets(388,5): >>> warning MSB8028: The intermediate directory (x64\Debug\) contains >>> files shared from another project (vtkWrapPythonInit.vcxproj, >>> vtkWrappingTools.vcxproj). This can lead to incorrect clean and >>> rebuild behavior. >>> 7> Building Custom Rule >>> D:/ParaView/ParaView/VTK/Wrapping/Tools/CMakeLists.txt >>> 7> CMake does not need to re-run because >>> D:\ParaView\pv-4.3.1-git\VTK\Wrapping\Tools\CMakeFiles\generate.stamp >>> is up-to-date. >>> 7> vtkWrapHierarchy.c 5> lq.cpp 3> EncodingC.c >>> 7>LINK : fatal error LNK1104: cannot open file >>> '..\..\..\lib\Debug\vtkWrappingTools-pv4.3.lib' >>> >>> I have no idea why that's happening. Maybe someone more familiar with VS >>> knows. >>> >>> I am not sure if there are any issues with the source and build >>> directories being on different drives. Try moving both the same drive, >>> to see if that helps -- but that's just a wild guess. >>> >>> Utkarsh >>> >>> On Fri, Mar 20, 2015 at 8:59 AM, Ian Krukow >>> wrote: >>>> >>>> Ok, I tried it again from scratch (with a fresh download), but I have the >>>> same issue. I also tried to build the git version, but it is the same >>>> too. >>>> >>>> I attach the log file from Visual Studio and the CMakeCache.txt. Maybe I >>>> missed something in the settings causing this problem? The error I >>>> mentioned >>>> is the first 'fatal error' in the log file in line 343. >>>> >>>> Ian >>>> >>>> >>>> Am 18.03.2015 um 16:27 schrieb Utkarsh Ayachit: >>>> >>>>> Not entirely sure what the problem could be. The latest master seems >>>>> to build fine with VS 2013. Maybe it's a parallel build issue? Try >>>>> kicking the build off again. >>>>> >>>>> Utkarsh >>>>> >>>>> On Wed, Mar 11, 2015 at 5:03 PM, Ian Krukow >>>>> >>>>> wrote: >>>>>> >>>>>> >>>>>> Hi all, >>>>>> >>>>>> I am trying to build ParaView on Windows, but I get the following >>>>>> error, >>>>>> and >>>>>> I have no idea what it means or how to fix it: >>>>>> >>>>>> >>>>>> >>>>>> 4>C:\ParaView\ParaView-v4.3.1-source\VTK\Wrapping\Tools\vtkWrapPythonInit.c >>>>>> : fatal error C1041: cannot open program database >>>>>> 'c:\paraview\pv\vtk\wrapping\tools\x64\debug\vc120.pdb'; if multiple >>>>>> CL.EXE >>>>>> write to the same .PDB file, please use /FS >>>>>> >>>>>> I use ParaView 4.3.1 source code and Visual Studio 2013. >>>>>> Can anyone help me? >>>>>> >>>>>> Kind regards >>>>>> Ian >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> 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 utkarsh.ayachit at kitware.com Mon Mar 23 11:05:22 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 23 Mar 2015 11:05:22 -0400 Subject: [Paraview] A VTS file producing a Segmentation fault In-Reply-To: References: Message-ID: The problem is that the arrays under "CellData" has duplicate names: "fx", "fx_p", "fx_v", "mx", "mx_p" and "mx_v" appear twice. Utkarsh On Mon, Mar 23, 2015 at 6:17 AM, Stefano Zaghi wrote: > Hi all, > > I have a problem with the VTS file attached. If I load it importing all cell > variables Paraview exits with "Segmentation fault (core dumped) paraview", > whereas if I import all cell variables until "f0" (included) Paraview works > well. > > I am using Paraview v4.3.1 64 bit (pre-compiled binary), with Qt 4.8.6 on an > Arch Linux with 3.18.6-1 kernel. > > Can anyone give me a deep insight of what is wrong with this file? > > Thank you for any suggestions. > > > 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 > 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 > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 sturgman at gmail.com Mon Mar 23 11:52:19 2015 From: sturgman at gmail.com (Salomon Turgman Cohen) Date: Mon, 23 Mar 2015 11:52:19 -0400 Subject: [Paraview] Repeating a Visualization in Several Data Sets Message-ID: Dear All, I suspect this question has been answered many times in this forum but I had trouble finding the answer. Say I have generated several data sets from a transient (multiple-time step) multiphysics simulation. Each one of my data sets if of exactly the same geometry but it may vary in the parameters and the number of time steps. I open one of these data sets (they are obtained from Elmer and are in the form of vtu files), set up a filter pipeline, and a number of visuals in paraview. Now I want to repeat the same steps on all the data sets but everything I have tried fails in some way. The pipeline consists of a "slice" of the data and three "Probe Location" filters each one with a "plot selection over time" filter for the line plots (if there is a better way to plot a local scalar quantity over time please let me know) Here is what I have found so far: 1. Save the state. Saving the state gets most of what I want done with one exception. Upon loading a state file I get asked to fix the path to the data file and this is how I change the data set that I am probing. However, if the data sets have a larger number of steps than the original saved one, I cannot see the rendering of the extra steps in paraview. For example, if I'm trying to see timestep 100 paraview only shows the last timestep in the original simulation (59). This one may or may not be an actual bug in paraview. 2. Create a custom filter. I have managed to do this with the three probes and their plots over time. The problem is that all the details about the variables plotted, legend name, and color of the line plots are lost. This made me suspect that this is not the functionality I am looking for or that I am not doing it correctly. 3. The final approach I tried is to start a trace before doing all the manipulations and then running that trace as a script or as a macro. When I run it from the python shell I get the following traceback: "Traceback (most recent call last): File "", line 541, in File "C:\Users\sturgmancohen\paraview\ParaView 4.3.1\lib\paraview -4.3\site-packages\paraview\servermanager.py", line 305, in __setattr__ setter(self, value) File "C:\Users\sturgmancohen\paraview\ParaView 4.3.1\lib\paraview -4.3\site-packages\paraview\servermanager.py", line 2474, in setProperty return self.SetPropertyWithName(propName, value) File "C:\Users\sturgmancohen\paraview\ParaView 4.3.1\lib\paraview -4.3\site-packages\paraview\servermanager.py", line 360, in SetPropertyWithName prop.SetData(arg) File "C:\Users\sturgmancohen\paraview\ParaView 4.3.1\lib\paraview -4.3\site-packages\paraview\servermanager.py", line 788, in SetData raise RuntimeError("This property requires %d values." % self.GetNumberOfElements()) RuntimeError: This property requires 0 values." And when I run it as a Macro, it does not reach the final state of the intended visualization. Any ideas? Thanks in advance. Salomon -- Salomon Turgman Cohen Assistant Professor Chemical Engineering Kettering University (919) 341-9650 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Mon Mar 23 13:21:40 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 23 Mar 2015 17:21:40 +0000 Subject: [Paraview] IMPORTANT-Particles+HPC Message-ID: That clarifies things, but I'm not sure how much I can help you. First, you just asked how ParaView will interpret this file. ParaView will read this as an "image" that is a regular 2D grid of data. It will show the data pretty much the same as the image below. (The colors will be different, but the meaning will be the same.) If you want to look at a single grain at a time, you can do that fairly easily with what is available in ParaView. You can either use the Threshold filter to extract a grain with a particular ID. Better yet, you can use the Find Data feature to select all "cells" that belong to a particular grain. That will help you locate a grain in the image, where you can zoom in and manually peek at neighboring grains. Beyond that, you might need to design your own analysis algorithms. At this point, I'm not sure what you want to see. From an image processing point of view, your data is already classified since there is a unique identifier for each grain. You could write a custom operation to identify all neighbors of all grains, but I'm not sure what you do with it after that. -Ken From: , Steven > Date: Monday, March 23, 2015 at 10:23 AM To: "Zhang,Ying" >, Kenneth Moreland > Cc: "paraview at paraview.org" >, "Sahi,Catherine A" > Subject: [EXTERNAL] IMPORTANT-Particles+HPC ?Hello all, Sorry for the delayed response. We were at the TMS conference the past week. > Steven, could you explain to Ken about your image and the information you are trying to find? Ken, we are in the Material Science and Engineering field. These files come from Dream3d and SPPARKS simulations. What do you mean by a "grain"? Is that some roundish feature in the image? [cid:bff29ec3-f8c7-4416-8c2b-ecb07ca5607c] An individual grain is define as 1 of the objects seen in the picture of above showing a 2-D face of our microstructure. What does it mean for two grains to be neighbors? Does it mean they are touching? -neighboring grains are grains that are adjacent to each other in the picture above. From the vti file stand point: 1 grain is comprised of 1 set of unique contiguous spins as see below. [cid:dd03b91e-c8c0-4939-bc25-6ea90dccd471] Link to dump.#.vti file in google drive: https://drive.google.com/folderview?id=0B-JhfuaY4N27fndFQXpYOEtHN0NzTWoyN2Q4cUtvY1BFV21lWHZoSFV3bnlwMUVzc2l6VHM&usp=sharing That they are within some certain distance of each other? I'm not sure what you mean. When we make the structures in dream3d, there is an option for spacing. [cid:97ae960d-11c3-4ff5-8531-0362b0d1c0ae] That they are not being obscured by some other grain? This will be on a 2-D scale so it will be like the image as seen previously. However, our microstructures are 3-D and we manually take a slice through it using paraview. Additionally, How would paraview interpret /read this vti? Contact me if you need anything. Best, Steven. ________________________________ From: Zhang,Ying Sent: Monday, March 16, 2015 12:08 PM To: Moreland, Kenneth Cc: paraview at paraview.org; Chiu,Steven Subject: Re: [Paraview] Algorithm to find grain neighbors Sorry that I forgot to Cc Steven. > On Mar 16, 2015, at 11:18 AM, Zhang,Ying > wrote: > > Hi Ken, > > I work in Research Computing at University of Florida and have a user (Cc'ed) who is using Paraview to visualize his grain image on our computing systems. > > Steven, could you explain to Ken about your image and the information you are trying to find? > > Thanks, > > Ying > >> On Mar 16, 2015, at 11:05 AM, Moreland, Kenneth > wrote: >> >> I don't really understand the question, but the answer is probably no. >> >> >> What do you mean by a "grain"? Is that some roundish feature in the image? >> And what does it mean for two grains to be neighbors? Does it mean they >> are touching? That they are within some certain distance of each other? >> That they are not being obscured by some other grain? >> >> Assuming I've guessed closed in any of these aspects, I don't think >> ParaView comes with any filters that perform that action. >> >> -Ken >> >> On 3/13/15, 3:21 PM, "Zhang,Ying" > wrote: >> >>> Dear Paraview developers, >>> >>> I sent a question a while ago and probably didn?t get to the list. But >>> here is my question again: >>> >>> I have a grain image in vti format and use Paraview to visualize the >>> grains. In Paraview I use Representation/Surface along with xml template >>> for coloring to display the grain image based on the vti file. I would >>> like to know if there is a way to find out the number of neighbors each >>> grain has. I wonder if paraview has a such tool to give this information. >>> >>> Thank you! >>> >>> Ying Zhang >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: b&w.png Type: image/png Size: 59779 bytes Desc: b&w.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2015-03-16 at 1.12.43 PM.png Type: image/png Size: 129601 bytes Desc: Screen Shot 2015-03-16 at 1.12.43 PM.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2015-03-23 at 12.10.43 PM.png Type: image/png Size: 47340 bytes Desc: Screen Shot 2015-03-23 at 12.10.43 PM.png URL: From Patrick.Brockmann at lsce.ipsl.fr Mon Mar 23 13:41:22 2015 From: Patrick.Brockmann at lsce.ipsl.fr (Patrick Brockmann) Date: Mon, 23 Mar 2015 18:41:22 +0100 Subject: [Paraview] TextureMapToSphere seam problem Message-ID: <55105042.5090404@lsce.ipsl.fr> Hi, I have a "ghost wrapped image" at the seam when I apply a texture to a sphere source. I don't know how to figure out this problem. Attached 2 captures. Let me know if I have misunderstood something or if there is a workaround. Tested with 4.3.1 64-bit Linux Regards Patrick -- LSCE/IPSL, Laboratoire CEA-CNRS-UVSQ Data Analysis and Visualization Engineer ICMC - IPSL Climate Modelling Centre -- -------------- next part -------------- A non-text attachment was scrubbed... Name: f0.png Type: image/png Size: 141450 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: f1.png Type: image/png Size: 132839 bytes Desc: not available URL: From yingz at ufl.edu Mon Mar 23 13:44:07 2015 From: yingz at ufl.edu (Zhang,Ying) Date: Mon, 23 Mar 2015 17:44:07 +0000 Subject: [Paraview] IMPORTANT-Particles+HPC In-Reply-To: References: Message-ID: Hi Ken, I am a little puzzled. For Steven?s VTI file, each cluster/grain has a unique ID, for example: 3732, 3240, 4955, etc. When Paraview visualize this file, how does it place one grain next to each other, or how does it determine one grain is adjacent to another? Is there any algorithm in paraview that defines adjacency? (I work in Research Computing center at UF and try to help Steven to run his program, so not really familiar with this work.) Thanks, Ying On Mar 23, 2015, at 1:21 PM, Moreland, Kenneth > wrote: That clarifies things, but I'm not sure how much I can help you. First, you just asked how ParaView will interpret this file. ParaView will read this as an "image" that is a regular 2D grid of data. It will show the data pretty much the same as the image below. (The colors will be different, but the meaning will be the same.) If you want to look at a single grain at a time, you can do that fairly easily with what is available in ParaView. You can either use the Threshold filter to extract a grain with a particular ID. Better yet, you can use the Find Data feature to select all "cells" that belong to a particular grain. That will help you locate a grain in the image, where you can zoom in and manually peek at neighboring grains. Beyond that, you might need to design your own analysis algorithms. At this point, I'm not sure what you want to see. From an image processing point of view, your data is already classified since there is a unique identifier for each grain. You could write a custom operation to identify all neighbors of all grains, but I'm not sure what you do with it after that. -Ken From: , Steven > Date: Monday, March 23, 2015 at 10:23 AM To: "Zhang,Ying" >, Kenneth Moreland > Cc: "paraview at paraview.org" >, "Sahi,Catherine A" > Subject: [EXTERNAL] IMPORTANT-Particles+HPC ?Hello all, Sorry for the delayed response. We were at the TMS conference the past week. > Steven, could you explain to Ken about your image and the information you are trying to find? Ken, we are in the Material Science and Engineering field. These files come from Dream3d and SPPARKS simulations. What do you mean by a "grain"? Is that some roundish feature in the image? An individual grain is define as 1 of the objects seen in the picture of above showing a 2-D face of our microstructure. What does it mean for two grains to be neighbors? Does it mean they are touching? -neighboring grains are grains that are adjacent to each other in the picture above. From the vti file stand point: 1 grain is comprised of 1 set of unique contiguous spins as see below. Link to dump.#.vti file in google drive: https://drive.google.com/folderview?id=0B-JhfuaY4N27fndFQXpYOEtHN0NzTWoyN2Q4cUtvY1BFV21lWHZoSFV3bnlwMUVzc2l6VHM&usp=sharing That they are within some certain distance of each other? I'm not sure what you mean. When we make the structures in dream3d, there is an option for spacing. That they are not being obscured by some other grain? This will be on a 2-D scale so it will be like the image as seen previously. However, our microstructures are 3-D and we manually take a slice through it using paraview. Additionally, How would paraview interpret /read this vti? Contact me if you need anything. Best, Steven. ________________________________ From: Zhang,Ying Sent: Monday, March 16, 2015 12:08 PM To: Moreland, Kenneth Cc: paraview at paraview.org; Chiu,Steven Subject: Re: [Paraview] Algorithm to find grain neighbors Sorry that I forgot to Cc Steven. > On Mar 16, 2015, at 11:18 AM, Zhang,Ying > wrote: > > Hi Ken, > > I work in Research Computing at University of Florida and have a user (Cc'ed) who is using Paraview to visualize his grain image on our computing systems. > > Steven, could you explain to Ken about your image and the information you are trying to find? > > Thanks, > > Ying > >> On Mar 16, 2015, at 11:05 AM, Moreland, Kenneth > wrote: >> >> I don't really understand the question, but the answer is probably no. >> >> >> What do you mean by a "grain"? Is that some roundish feature in the image? >> And what does it mean for two grains to be neighbors? Does it mean they >> are touching? That they are within some certain distance of each other? >> That they are not being obscured by some other grain? >> >> Assuming I've guessed closed in any of these aspects, I don't think >> ParaView comes with any filters that perform that action. >> >> -Ken >> >> On 3/13/15, 3:21 PM, "Zhang,Ying" > wrote: >> >>> Dear Paraview developers, >>> >>> I sent a question a while ago and probably didn?t get to the list. But >>> here is my question again: >>> >>> I have a grain image in vti format and use Paraview to visualize the >>> grains. In Paraview I use Representation/Surface along with xml template >>> for coloring to display the grain image based on the vti file. I would >>> like to know if there is a way to find out the number of neighbors each >>> grain has. I wonder if paraview has a such tool to give this information. >>> >>> Thank you! >>> >>> Ying Zhang >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Mon Mar 23 14:13:22 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 23 Mar 2015 18:13:22 +0000 Subject: [Paraview] IMPORTANT-Particles+HPC Message-ID: ParaView does not do anything special about the grains. It does not even understand the concept of "grain." You can ask ParaView to find all cells with a grain ID, for example 3732. You, as a human, can then look at those cells, understand that collectively they are a grain, and examine its neighbors. -Ken From: , Ying > Date: Monday, March 23, 2015 at 11:44 AM To: Kenneth Moreland > Cc: "Chiu,Steven" >, "paraview at paraview.org" >, "Sahi,Catherine A" > Subject: [EXTERNAL] Re: IMPORTANT-Particles+HPC Hi Ken, I am a little puzzled. For Steven?s VTI file, each cluster/grain has a unique ID, for example: 3732, 3240, 4955, etc. When Paraview visualize this file, how does it place one grain next to each other, or how does it determine one grain is adjacent to another? Is there any algorithm in paraview that defines adjacency? (I work in Research Computing center at UF and try to help Steven to run his program, so not really familiar with this work.) Thanks, Ying On Mar 23, 2015, at 1:21 PM, Moreland, Kenneth > wrote: That clarifies things, but I'm not sure how much I can help you. First, you just asked how ParaView will interpret this file. ParaView will read this as an "image" that is a regular 2D grid of data. It will show the data pretty much the same as the image below. (The colors will be different, but the meaning will be the same.) If you want to look at a single grain at a time, you can do that fairly easily with what is available in ParaView. You can either use the Threshold filter to extract a grain with a particular ID. Better yet, you can use the Find Data feature to select all "cells" that belong to a particular grain. That will help you locate a grain in the image, where you can zoom in and manually peek at neighboring grains. Beyond that, you might need to design your own analysis algorithms. At this point, I'm not sure what you want to see. From an image processing point of view, your data is already classified since there is a unique identifier for each grain. You could write a custom operation to identify all neighbors of all grains, but I'm not sure what you do with it after that. -Ken From: , Steven > Date: Monday, March 23, 2015 at 10:23 AM To: "Zhang,Ying" >, Kenneth Moreland > Cc: "paraview at paraview.org" >, "Sahi,Catherine A" > Subject: [EXTERNAL] IMPORTANT-Particles+HPC ?Hello all, Sorry for the delayed response. We were at the TMS conference the past week. > Steven, could you explain to Ken about your image and the information you are trying to find? Ken, we are in the Material Science and Engineering field. These files come from Dream3d and SPPARKS simulations. What do you mean by a "grain"? Is that some roundish feature in the image? An individual grain is define as 1 of the objects seen in the picture of above showing a 2-D face of our microstructure. What does it mean for two grains to be neighbors? Does it mean they are touching? -neighboring grains are grains that are adjacent to each other in the picture above. From the vti file stand point: 1 grain is comprised of 1 set of unique contiguous spins as see below. Link to dump.#.vti file in google drive: https://drive.google.com/folderview?id=0B-JhfuaY4N27fndFQXpYOEtHN0NzTWoyN2Q4cUtvY1BFV21lWHZoSFV3bnlwMUVzc2l6VHM&usp=sharing That they are within some certain distance of each other? I'm not sure what you mean. When we make the structures in dream3d, there is an option for spacing. That they are not being obscured by some other grain? This will be on a 2-D scale so it will be like the image as seen previously. However, our microstructures are 3-D and we manually take a slice through it using paraview. Additionally, How would paraview interpret /read this vti? Contact me if you need anything. Best, Steven. ________________________________ From: Zhang,Ying Sent: Monday, March 16, 2015 12:08 PM To: Moreland, Kenneth Cc: paraview at paraview.org; Chiu,Steven Subject: Re: [Paraview] Algorithm to find grain neighbors Sorry that I forgot to Cc Steven. > On Mar 16, 2015, at 11:18 AM, Zhang,Ying > wrote: > > Hi Ken, > > I work in Research Computing at University of Florida and have a user (Cc'ed) who is using Paraview to visualize his grain image on our computing systems. > > Steven, could you explain to Ken about your image and the information you are trying to find? > > Thanks, > > Ying > >> On Mar 16, 2015, at 11:05 AM, Moreland, Kenneth > wrote: >> >> I don't really understand the question, but the answer is probably no. >> >> >> What do you mean by a "grain"? Is that some roundish feature in the image? >> And what does it mean for two grains to be neighbors? Does it mean they >> are touching? That they are within some certain distance of each other? >> That they are not being obscured by some other grain? >> >> Assuming I've guessed closed in any of these aspects, I don't think >> ParaView comes with any filters that perform that action. >> >> -Ken >> >> On 3/13/15, 3:21 PM, "Zhang,Ying" > wrote: >> >>> Dear Paraview developers, >>> >>> I sent a question a while ago and probably didn?t get to the list. But >>> here is my question again: >>> >>> I have a grain image in vti format and use Paraview to visualize the >>> grains. In Paraview I use Representation/Surface along with xml template >>> for coloring to display the grain image based on the vti file. I would >>> like to know if there is a way to find out the number of neighbors each >>> grain has. I wonder if paraview has a such tool to give this information. >>> >>> Thank you! >>> >>> Ying Zhang >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> 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 Mar 23 19:25:21 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 23 Mar 2015 23:25:21 +0000 Subject: [Paraview] Setting color maps in python Message-ID: <15a961a2cb6841e7969c30e66590461e@ES05AMSNLNT.srn.sandia.gov> With a lot of help from Utkarsh, I now know how to set custom color maps in Python. Here is what I did, and the code, for coloring Sources/ Wavelet by the blue to red rainbow. (And has been said, blue to red rainbow is a poor color map for doing real work. It does create pretty pictures, however.) ParaView 4.3.1, local server, Linux. Sources/ wavelet/ apply. Change outline to surface. Paint by RTData. Color editor. Preset - Blue to Red Rainbow. Export. Save this as an xml file somewhere you can find it. Edit this .xml file. There will be two ColorMaps (unless this has been fixed). Delete the second group (from ColorMap to /ColorMap). Also, delete the two lines with ColorMaps in them. (Note - I will write up bugs for these two issues.) Edit/ reset session. Tools/ Start Trace. OK. Sources/ Wavelet. Apply. Change outline to surface. Paint by RTData. Tools/ Stop Trace. Save the script. Edit the script. Below the line where it says wavelet1Display.SetScalarBarVisibility(renderView1, True), add the following: lut = GetColorTransferFunction("RTData") with open("/..../junkDir/blue-to-red-rainbow.xml", "r") as f: data = f.read() lut.ApplyColorMap(data) Then, comment out the two lines that say: # get color transfer function/color map for 'RTData' rTDataLUT = GetColorTransferFunction('RTData') # get opacity transfer function/opacity map for 'RTData' rTDataPWF = GetOpacityTransferFunction('RTData') Save your file, then in ParaView do the following: Edit/ reset session. Tools/ Python shell. Run script. Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From christian.butcher at oist.jp Tue Mar 24 02:18:02 2015 From: christian.butcher at oist.jp (Christian Butcher) Date: Tue, 24 Mar 2015 15:18:02 +0900 Subject: [Paraview] Fwd: Rendering speed sluggish using cluster In-Reply-To: References: Message-ID: Dear ParaView Users, I'm rendering a pseudo-2D data set of approx 7 million cells, running 'mpirun ... pvserver'. I can connect remotely. The cluster does not have graphics cards installed, so I'm using the '--use-offscreen-rendering' flag. The client options for 'Remote Render Threshold' and 'LODThreshold' are both set to 0. On the cluster, I'm currently trying with 48 cores each using 16GB RAM, just in case I was previously using too little. I'm pretty sure this is overkill - certainly the problem seems comparable to when I run it on 8 cores each using 4GB RAM etc. I suspect I'm just not using the software well, or have installed either the client or (more likely?) the cluster's pvserver badly. Both are using 4.2.0, client has version "4.2.0-287-g1631961 64-bit", pvserver returns just "4.2.0" as the version. When changing any aspect of the render view, the client becomes unresponsive/sluggish for long periods of time. This includes, for example, moving the coloring scale bar across the screen. I'm sure I'm missing something obvious (like a step to cut down the requirements on the client workstation, for example). What should I be doing differently? The script I used to start ccmake is below - other options were left at default values (iirc): ccmake \ -DCMAKE_BUILD_TYPE:STRING=RelWithDebInfo \ -DCMAKE_CXX_COMPILER:FILEPATH=/apps/gnu/openmpi.gcc/1.8.3/bin/mpic++ \ -DCMAKE_C_COMPILER:FILEPATH=/apps/gnu/openmpi.gcc/1.8.3/bin/mpicc \ -DCMAKE_Fortran_COMPILER:FILEPATH=/apps/gnu/openmpi.gcc/1.8.3/bin/mpifort \ -DPARAVIEW_USE_MPI:BOOL=ON \ \ -DCMAKE_INSTALL_PREFIX:PATH=/home/c/christian-butcher/Applications \ -DBoost_INCLUDE_DIR:PATH=/home/c/christian-butcher/Applications/include \ -DBoost_LIBRARY_DIRS:FILEPATH=/home/c/christian-butcher/Applications/lib \ \ -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ -DBUILD_TESTING:BOOL=OFF \ -DBUILD_EXAMPLES:BOOL=FALSE \ -DBUILD_SHARED_LIBS:BOOL=ON \ -DBUILD_DOCUMENTATION:BOOL=OFF \ -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON \ \ -DPARAVIEW_ENABLE_FFMPEG:BOOL=ON \ -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \ \ -DVTK_OPENGL_HAS_OSMESA:BOOL=ON \ -DVTK_USE_OFFSCREEN:BOOL=ON \ -DVISIT_BUILD_READER_GMV:BOOL=OFF \ \ -DPARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_H5PartReader:BOOL=ON \ -DPARAVIEW_BUILD_PLUGIN_GMVReader:BOOL=FALSE \ -DPARAVIEW_BUILD_PLUGIN_Moments:BOOL=FALSE \ -DPARAVIEW_BUILD_PLUGIN_PacMan:BOOL=FALSE \ -DPARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=FALSE \ -DPARAVIEW_BUILD_PLUGIN_SciberQuestToolKit:BOOL=FALSE \ -DPARAVIEW_BUILD_PLUGIN_SierraPlotTools:BOOL=FALSE \ \ -DVTK_USE_SYSTEM_ZLIB:BOOL=ON \ -DVTK_USE_SYSTEM_EXPAT:BOOL=ON \ -DVTK_USE_X:BOOL=OFF \ \ -DModule_vtkFiltersParallelGeometry=ON \ -DModule_vtkFiltersSMP=ON \ -DModule_vtkFiltersSelection=ON \ -DModule_vtkIOMPIParallel=ON \ -DModule_vtkImagingMath=ON \ -DModule_vtkImagingStatistics=ON \ -DModule_vtkImagingStencil=ON \ \ -DOPENGL_INCLUDE_DIR:PATH=/home/c/christian-butcher/Applications/include \ -DOPENGL_gl_LIBRARY:FILEPATH=/home/c/christian-butcher/Applications/lib/libOSMesa.so \ -DOPENGL_glu_LIBRARY:FILEPATH=/home/c/christian-butcher/Applications/lib/libGLU.so \ -DOSMESA_LIBRARY:FILEPATH=/home/c/christian-butcher/Applications/lib/libOSMesa.so \ -DOSMESA_INCLUDE_DIR:PATH=/home/c/christian-butcher/Applications/include \ $APPS/source/git-sources/ParaView From mickey.phy at gmail.com Tue Mar 24 02:54:33 2015 From: mickey.phy at gmail.com (Mickael Philit) Date: Tue, 24 Mar 2015 07:54:33 +0100 Subject: [Paraview] Issue with structured grids and extraction of boundaries with cell data In-Reply-To: <550C3C08.2090101@gmail.com> References: <550C3C08.2090101@gmail.com> Message-ID: <55110A29.2000008@gmail.com> Hello, I managed to reproduce the problem. The difference between ParaView 4.3.1 and previous version comes to the removal of vtkPVTrivialExtentTranslator in the pipeline. Thus, the update extent requested by the extract filter may not be updated correctly anymore. It is a similar problem to this other bug: http://marc.info/?l=paraview&m=142168609529307&w=2 Best Regards Mickael On 20/03/2015 16:26, Etienne Tang wrote: > Hello, > > I'm working with a 3D structured dataset containing cell data. I tried > to extract a 2D boundary of this dataset corresponding to the maximum > index of a dimension with the Extract Subset filter and ParaView 4.3.1, > and I found an issue: the resulting dataset is incorrect. It holds cell > data from the opposite boundary (eg. if I try to extract the i = imax > boundary, I get values from i = 0 boundary), and these values are > shifted of one index in the other dimensions. > > This case worked with ParaView 4.1.0, maybe it is related to this other > bug about structured data : > http://markmail.org/message/fvatgidqbvnufgi6#query:+page:1+mid:fvatgidqbvnufgi6+state:results > ? > > Here are some pictures showing the problem on a simple dataset which can > be used to reproduce it: > - The simple .vts file : http://z1.gb2n.org/pv/test.vts > - The original dataset : http://z1.gb2n.org/pv/original_dataset.png > - The result of the ExtractSubset filter to extract the i = imax > boundary : http://z1.gb2n.org/pv/extract_subset.png > > Best regards, From matthew.jackson at ch.abb.com Tue Mar 24 08:39:57 2015 From: matthew.jackson at ch.abb.com (Matthew Jackson) Date: Tue, 24 Mar 2015 12:39:57 +0000 Subject: [Paraview] .ini File Change in Version 4.2 Message-ID: Hello, I recently started using Paraview 4.3 instead of Paraview 4.1. I notice that the way the settings are stored was changed in 4.2. Before, I could change the Auto Apply setting in the Property Panel Options by editing the .ini file. I also need to change a few other options. This is for an application I am developing that uses Paraview, and I need to set these settings automatically every time the application launches Paraview. Does anybody know how to do this in version 4.2+? Regards, Matthew Jackson -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Tue Mar 24 10:48:55 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Tue, 24 Mar 2015 10:48:55 -0400 Subject: [Paraview] Hardware suggestions for volume rendering In-Reply-To: References: Message-ID: Hey Kevin, On Fri, Mar 20, 2015 at 2:33 PM, Kevin Lau wrote: > Dear Aashish, > > Thanks for your reply. > > (1) > > We tried testing it with 2 different data sets of simulation data, one > medium sized and one very large: > > Medium > Cells: 1309489 > Points: 247984 > Memory [MB]: 119.179 > Geometry [MB]: 8.201 > > Very Large > Cells: 51937191 > Points: 11019274 > Memory [MB]: 4709.731 > Geometry [MB]: 776.237 > > These datasets are unstructured grids (tetrahedral meshes) read into > ParaView using the Phasta data reader. > > I see. Most of the performance improvements we have achieved is with GPU RayCast Volume mapper (uses image data). If you can sample your data into a strucuted grid then you will be able to use the new mapper. Thanks, > (2) > > The OS used was Ubuntu > > (3) > > The graphics card was a NVIDIA Quatro K6000 running the NVIDIA drivers > from the Ubuntu Repos (v 331.113) > > (4) > > We configured ParaView using the default CMake options, changing VTK > _RENDERING_BACKEND=OpenGL2 and disabling all the plug-ins. These tests > were run in serial, as building with MPI was throwing errors. > > (5) > > We expected that the OpenGL2 version of ParaView would be able to volume > render faster than the standard OpenGL version. However the reported > frame rates were the same in both builds when clicking and dragging (~2 > FPS). > > This is a problem because we're mainly interested in visualising our data > and having users able to rotate the model and interact with it. At these > frame rates the response is a bit sluggish. > > Also I've done serial test using an OpenGL2 build on Windows using an old > GeForce 8800 with the same medium sized data. On this machine the frame > rate was similar at around ~1.5 FPS. > > (6) > > ParaView was built by checking out the master from git. Sadly I'm not on > that test machine now, so I can't check the SHA > > Many thanks for your help again. > > Kevin > > > On 20 March 2015 at 10:33, Aashish Chaudhary < > aashish.chaudhary at kitware.com> wrote: > >> Hey Kevin, >> >> On Thu, Mar 19, 2015 at 5:33 PM, Kevin Lau wrote: >> >>> Dear Aashish, >>> >>> Thanks for your reply, I've now managed to build ParaView from the >>> Master branch with VTK_RENDERING_BACKEND set to OpenGL2 and I have noticed >>> a visible difference in the rendering. >>> >>> However comparison of the rendering performance in the interactive mode >>> of builds with the standard OpenGL backend vs the OpenGL2 backend, both >>> show similar frame rates. >>> >> >> Depending on the card and features you are using you may not see a huge >> bump in performance. On some systems we have seen 300 times performance >> improvements and on others there were close specially when you have VSync >> on. Said that, can you provide more infromation on >> >> 1) Data size >> 2) OS >> 3) Graphics card >> 4) Features you have enabled? >> 5) You expectation and problem >> 6) What SHA of ParaView you are using? >> >> Are there other build options that I'm missing? Should I be building the >>> VTK libraries themselves? >>> >> >> Just make sure that you built from a clean state other than that you >> should be good. >> >> Thanks, >> >> >>> Many thanks, >>> >>> Kevin >>> >>> >>> On 3 March 2015 at 14:53, Aashish Chaudhary < >>> aashish.chaudhary at kitware.com> wrote: >>> >>>> On Tue, Mar 3, 2015 at 2:43 PM, Kevin Lau >>>> wrote: >>>> >>>>> Dear Aashish, >>>>> >>>>> Thank you very much for your reply. The latest work you're doing on >>>>> volume rendering is very impressive. >>>>> >>>> >>>> Thanks. >>>> >>>>> >>>>> In order to access the latest VTK rendering in ParaView would we have >>>>> to compile both the latest VTK and ParaView from source? Is it possible to >>>>> link ParaView to specific VTK builds? >>>>> >>>> >>>> Latest ParaView from source should be fine. Just make sure that you >>>> select VTK_RENDERING_BACKEND to OpenGL2 >>>> >>>>> >>>>> Also do you know if it is preferential to have a single GPU (i.e. a >>>>> workstation graphics card) or multiple GPU (i.e. gaming graphics card) when >>>>> using ParaView? >>>>> >>>> >>>> If I remember correctly, we don't explicitly assign tasks to GPU in >>>> ParaView if running a single process. You can find more information here: >>>> http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server#Multiple_GPUs_Per_Node >>>> >>>> Hope it helps. >>>> >>>>> >>>>> Many thanks, >>>>> >>>>> Kevin >>>>> >>>>> >>>>> On 27 February 2015 at 08:15, Aashish Chaudhary < >>>>> aashish.chaudhary at kitware.com> wrote: >>>>> >>>>>> Dear Kevin, >>>>>> >>>>>> First, I would like to mention that we have been working hard to >>>>>> improve rendering in VTK that includes volume rendering as well. You may >>>>>> want to read this source article: >>>>>> http://www.kitware.com/source/home/post/154. Most of the changes >>>>>> related to this work is now available in VTK github repository in master >>>>>> branch. If you are targetting current VTK, I would suggest that any card >>>>>> that can support OpenGL2.1 or higher would be great. The higher the GPU >>>>>> memory the better. While these newer card will work with the previous >>>>>> version of volume rendering, it may not scale very well (in our testing >>>>>> that's what we have observed). Current the default in ParaView is OpenGL >>>>>> Volume Rendering but that is going to change sometime soon and once that >>>>>> happens you will have OpenGL2 backend for everything. >>>>>> >>>>>> Hope this helps. >>>>>> - Aashish >>>>>> >>>>>> >>>>>> >>>>>> On Thu, Feb 26, 2015 at 5:41 PM, Kevin Lau >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I'm looking to putting together a workstation to perform realtime >>>>>>> volume rendering of our simulation data. >>>>>>> >>>>>>> Are there any particular GPU features I should look for? >>>>>>> >>>>>>> If there are multiple GPUs will Paraview be able to take advantage >>>>>>> of each GPU for volume rendering? >>>>>>> >>>>>>> Many thanks >>>>>>> >>>>>>> Kevin >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at >>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>> http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>> 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 >>>>>> * >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> >>>> >>>> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >>>> * >>>> *| http://www.kitware.com/company/team/chaudhary.html >>>> * >>>> >>> >>> >> >> >> -- >> >> >> >> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >> * >> *| http://www.kitware.com/company/team/chaudhary.html >> * >> > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From dkxls23 at gmail.com Tue Mar 24 11:43:08 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Tue, 24 Mar 2015 17:43:08 +0200 Subject: [Paraview] Hardware suggestions for volume rendering In-Reply-To: References: Message-ID: <5511860C.4080501@gmail.com> Hey Kevin and Aashish, I found this discussion rather interesting, especially since I'm basically facing the same problem as Kevin. In almost all cases, we are dealing here with large unstructured grids (e.g. 12M cells) and the volume rendering is performance is extremely bad, not to say unusable, for these cases. I only tested it with ParaView 4.3.1 and older versions, i.e. with the old OpenGL algorithms, but the performance is barely influenced by the actual volume renderer (i.e. GPU vs. CPU based). For an unstructured grid the volume rendering seems to be CPU limited in any case, at least my CPU is at 100% for quite some time and the GPU load is negligible. ParaView's status bar indicates that it's busy with "OpenGLProjectedTetrahedraMapper". This can be easily reproduced with the wavelet source (with e.g. 125k points) and tessellation filter. So far I have resorted to resampling the data onto a structured grid. This has the clear drawback that a structured grid with the same resolution has about 70M grid points compared to the 12M points of the unstructured grid. The volume rendering performance of a 70M unstructured grid is however already decent with the old OpenGL algorithms. So is there a way to improve the rendering of unstructured grids to avoid the resampling? Best regards, Armin On 03/24/2015 04:48 PM, Aashish Chaudhary wrote: > Hey Kevin, > > > > On Fri, Mar 20, 2015 at 2:33 PM, Kevin Lau > wrote: > > Dear Aashish, > > Thanks for your reply. > > (1) > > We tried testing it with 2 different data sets of simulation data, > one medium sized and one very large: > > Medium > Cells: 1309489 > Points: 247984 > Memory [MB]: 119.179 > Geometry [MB]: 8.201 > > Very Large > Cells: 51937191 > Points: 11019274 > Memory [MB]: 4709.731 > Geometry [MB]: 776.237 > > These datasets are unstructured grids (tetrahedral meshes) read into > ParaView using the Phasta data reader. > > I see. Most of the performance improvements we have achieved is with GPU > RayCast Volume mapper (uses image data). If you can sample your data > into a strucuted grid then you will be able to use the new mapper. > > Thanks, > > (2) > > The OS used was Ubuntu > > (3) > > The graphics card was a NVIDIA Quatro K6000 running the NVIDIA > drivers from the Ubuntu Repos (v 331.113) > > (4) > > We configured ParaView using the default CMake options, changing > VTK_RENDERING_BACKEND=OpenGL2 and disabling all the plug-ins. These > tests were run in serial, as building with MPI was throwing errors. > > (5) > > We expected that the OpenGL2 version of ParaView would be able to > volume render faster than the standard OpenGL version. However the > reported frame rates were the same in both builds when clicking and > dragging (~2 FPS). > > This is a problem because we're mainly interested in visualising our > data and having users able to rotate the model and interact with it. > At these frame rates the response is a bit sluggish. > > Also I've done serial test using an OpenGL2 build on Windows using > an old GeForce 8800 with the same medium sized data. On this machine > the frame rate was similar at around ~1.5 FPS. > > (6) > > ParaView was built by checking out the master from git. Sadly I'm > not on that test machine now, so I can't check the SHA > > Many thanks for your help again. > > Kevin > > > On 20 March 2015 at 10:33, Aashish Chaudhary > > wrote: > > Hey Kevin, > > On Thu, Mar 19, 2015 at 5:33 PM, Kevin Lau > > wrote: > > Dear Aashish, > > Thanks for your reply, I've now managed to build ParaView > from the Master branch with VTK_RENDERING_BACKEND set to > OpenGL2 and I have noticed a visible difference in the > rendering. > > However comparison of the rendering performance in the > interactive mode of builds with the standard OpenGL backend > vs the OpenGL2 backend, both show similar frame rates. > > > Depending on the card and features you are using you may not see > a huge bump in performance. On some systems we have seen 300 > times performance improvements and on others there were close > specially when you have VSync on. Said that, can you provide > more infromation on > > 1) Data size > 2) OS > 3) Graphics card > 4) Features you have enabled? > 5) You expectation and problem > 6) What SHA of ParaView you are using? > > Are there other build options that I'm missing? Should I be > building the VTK libraries themselves? > > > Just make sure that you built from a clean state other than that > you should be good. > Thanks, > > > Many thanks, > > Kevin > > > On 3 March 2015 at 14:53, Aashish Chaudhary > > wrote: > > On Tue, Mar 3, 2015 at 2:43 PM, Kevin Lau > > > wrote: > > Dear Aashish, > > Thank you very much for your reply. The latest work > you're doing on volume rendering is very impressive. > > > Thanks. > > > In order to access the latest VTK rendering in > ParaView would we have to compile both the latest > VTK and ParaView from source? Is it possible to link > ParaView to specific VTK builds? > > > Latest ParaView from source should be fine. Just make > sure that you select VTK_RENDERING_BACKEND to OpenGL2 > > > Also do you know if it is preferential to have a > single GPU (i.e. a workstation graphics card) or > multiple GPU (i.e. gaming graphics card) when using > ParaView? > > > If I remember correctly, we don't explicitly assign > tasks to GPU in ParaView if running a single process. > You can find more information here: > http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server#Multiple_GPUs_Per_Node > > Hope it helps. > > > Many thanks, > > Kevin > > > On 27 February 2015 at 08:15, Aashish Chaudhary > > wrote: > > Dear Kevin, > > First, I would like to mention that we have been > working hard to improve rendering in VTK that > includes volume rendering as well. You may want > to read this source article: > http://www.kitware.com/source/home/post/154. > Most of the changes related to this work is now > available in VTK github repository in master > branch. If you are targetting current VTK, I > would suggest that any card that can support > OpenGL2.1 or higher would be great. The higher > the GPU memory the better. While these newer > card will work with the previous version of > volume rendering, it may not scale very well (in > our testing that's what we have observed). > Current the default in ParaView is OpenGL Volume > Rendering but that is going to change sometime > soon and once that happens you will have OpenGL2 > backend for everything. > > Hope this helps. > - Aashish > > > > On Thu, Feb 26, 2015 at 5:41 PM, Kevin Lau > > wrote: > > Hi, > > I'm looking to putting together a > workstation to perform realtime volume > rendering of our simulation data. > > Are there any particular GPU features I > should look for? > > If there are multiple GPUs will Paraview be > able to take advantage of each GPU for > volume rendering? > > Many thanks > > Kevin > > > > _______________________________________________ > Powered by www.kitware.com > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the > ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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/ > > > > > > -- > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. > / > /| http://www.kitware.com/company/team/chaudhary.html/ > > > > > > -- > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. > / > /| http://www.kitware.com/company/team/chaudhary.html/ > > > > > > -- > /| 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 > From berk.geveci at kitware.com Tue Mar 24 13:13:17 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Tue, 24 Mar 2015 13:13:17 -0400 Subject: [Paraview] Fwd: Gradient of Unstructed dataset In-Reply-To: References: <5507D199.5040505@gmail.com> Message-ID: Hi Masaaki and others that may be interested, I identified the issue. The default CGSN reader that we use (which is from VisIt originally) produces incorrect results. The pressure values are incorrect. If you load the CGNS reader plugin and open the CGNS file with that, you will see the correct results. I tested this with the nightly binary of ParaView. I will ask someone in the ParaView team to disable the VisIt CGNS reader and move the plugin into ParaView proper so that we can use it by default. Best, -berk On Wed, Mar 18, 2015 at 8:59 AM, Berk Geveci wrote: > Thanks Masaaki. I will look into it. > > I wish that I could say the same about northern New York State. The high > temperature for today and tomorrow is 30F (-1C). Most of the snow melted > though so spring is coming :-) > > -berk > > On Tue, Mar 17, 2015 at 8:04 PM, Masaaki SHOJIMA > wrote: > >> Hi Berk, Armin, Michael and friends >> >> It is getting warm and flowers are starting to bloom in japan, this >> morning. >> >> Nightly Builds of Paraview was downloaded on 2015-Mar-18 >> (ParaView-Windows-64bit-NIGHTLY.zip). >> >> Gradient of Pressure was calculated using "Gradient of Unstrucutred >> Dataset" filter and Z component of Grad (pressure) was visualized. >> >> Unfortunately, Nightly build did not settle the problem... >> The computed values by nightly builds were also half compared to those of >> Ensight. >> >> Could you take a look of the result in the attached PDF? >> >> Thanks for your continuous help. >> >> Masaaki >> >> 2015-03-17 22:01 GMT+09:00 Berk Geveci : >> >>> Hi Masaaki, >>> >>> I will hold off testing on my end until you have a chance to test with >>> nightly binaries. Please let us know how it goes. >>> >>> Regards, >>> -berk >>> >>> On Tue, Mar 17, 2015 at 8:09 AM, wrote: >>> >>>> You could test it with the nighly builds from the dashboard. That way >>>> you don't have to compile anything. >>>> >>>> You can find more information here: >>>> http://www.paraview.org/Wiki/ParaView_Nightly_Binaries >>>> >>>> -Armin >>>> >>>> >>>> >>>> On Tue Mar 17 12:27:27 2015 GMT+0200, Masaaki SHOJIMA wrote: >>>> > Hi, Michael, >>>> > >>>> > I found a web-page regarding the CGNS reader, in which you are making >>>> > important comments. >>>> > http://comments.gmane.org/gmane.comp.science.paraview.user/23957 >>>> > >>>> > I have to wait for the next version, is it right? >>>> > >>>> > Thanks >>>> > >>>> > Masaaki >>>> > >>>> > 2015-03-17 16:02 GMT+09:00 Mickael Philit : >>>> > >>>> > > Hello, >>>> > > >>>> > > sorry to intrude, >>>> > > I think the problem may come from the CGNS loader of ParaView. >>>> > > When using the CGNS plugin from ParaView development version, you >>>> get the >>>> > > same picture as Ensight. >>>> > > My two cents >>>> > > >>>> > > Mickael >>>> > > >>>> > > >>>> > > On 17/03/2015 05:04, Masaaki SHOJIMA wrote: >>>> > > >>>> > > Hi Berk, >>>> > > >>>> > > I appreciate your kindness >>>> > > >>>> > > Here, I attaches the data. >>>> > > Compare Gradient.pdf (252KB) >>>> > > >>>> > > A calculated field by SC/Tetra solver is uploaded in Dropbox. >>>> (Calc.zip) >>>> > > Please download the data. It contains FLD format for SC/Tetra post >>>> and >>>> > > CGNS format for Ensight and Paraview. >>>> > > https://www.dropbox.com/s/5fpeu1qwhyzjn5u/Calc.zip?dl=0 >>>> > > >>>> > > (1) I calculated the flow and the pressure in a simple cylinder for >>>> a test >>>> > > ( diameter 0.005m, length 0.01m). Plug flow at inlet with 0.03 m/s. >>>> > > >>>> > > (2) Data were transfered to Ensight and Paraview in CGNS format. >>>> > > >>>> > > (3) Pressure was mapped on the surface and compared between >>>> SC/Tetra post, >>>> > > Ensight and Paraview. All application provided same results. >>>> > > >>>> > > (4) Gradient (pressure) was calculated in each post and z-component >>>> of >>>> > > Gradient (pressure) was visualized with same colored contour. Only >>>> paraview >>>> > > provided a different image because the computed gradients in >>>> paraview had >>>> > > half values compared to SC/Tetra post and Ensight. >>>> > > >>>> > > (5) Gradient (velocity-X) was also calculated in each post and the >>>> > > X-component of Grad (velocity-X) was visualized. Same results as >>>> shown in 4. >>>> > > >>>> > > >>>> > > Thanks a lot. >>>> > > >>>> > > Masaaki >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > _______________________________________________ >>>> > > Powered by www.kitware.com >>>> > > >>>> > > Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> > > >>>> > > Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> > > >>>> > > Search the list archives at: http://markmail.org/search/?q=ParaView >>>> > > >>>> > > Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> > > >>>> > > >>>> > > >>>> > >>>> >>>> -- >>>> Sent from my Jolla >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> 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.brito at aia.rwth-aachen.de Tue Mar 24 13:21:23 2015 From: g.brito at aia.rwth-aachen.de (Gonzalo Brito Gadeschi) Date: Tue, 24 Mar 2015 18:21:23 +0100 Subject: [Paraview] Add plugin for a particular cmake target only Message-ID: When I add a paraview plugin to my cmake project via: add_paraview_plugin(...) The plugin is compiled with just "make". It is possible to allow e.g. compiling the plugin via "make my_target" using: add_dependencies(my_target MyPlugin) Is it possible to avoid that the plugin is automatically compiled via "make" (without target)? That is, to control to which cmake target add_paraview_plugin adds the plugin too? Bests, Gonzalo BG -- Dipl.-Ing. Gonzalo Brito Gadeschi Institute of Aerodynamics and Chair of Fluid Mechanics RWTH Aachen University Wuellnerstra?e 5a D-52062 Aachen Germany Phone: ++49-(0)241-80-94821 Fax: ++49-(0)241-80-92257 E-mail: g.brito at aia.rwth-aachen.de Internet: www.aia.rwth-aachen.de -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Tue Mar 24 15:48:59 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 24 Mar 2015 15:48:59 -0400 Subject: [Paraview] announce: VTK and ParaView training - April 21, Clifton Park NY Message-ID: Kitware is hosting a VTK-ParaView training course in Clifton Park, NY. The course will be held on April 21, 2015. Attendees will gain practical experience in both ParaView, a scalable application for general purpose scientific visualization, and The Visualization Toolkit (VTK), the underlying open-source library from which ParaView is built. The training mixes theory and application to guide attendees through a set of exercises, which are all given in the python programming language. Upon completion of this course, attendees will not only know how to use ParaView and VTK, but they will also know how to extend ParaView at run time, use it in concert with other Python capable applications, and run it in batch processing HPC contexts. Additional details and registration information are available on the Kitware website . The price of the course via early registration is $650. Early registration is available through April 15, 2015. The price of the course via regular registration is $815. In addition, Kitware will be hosting a ?Project Lifecycle Management with the CMake Family of Tools? training course on April 22, 2015. This course will also be hosted in Clifton Park. For more information, please visit http://www.kitware.com/products/protraining.php. 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 leonardopessanha74 at gmail.com Tue Mar 24 17:22:48 2015 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Tue, 24 Mar 2015 18:22:48 -0300 Subject: [Paraview] Exporting VRML file series with python script Message-ID: Hi, I would like to export a series of vtk files in the VRML format trough scripting, i found a script in the mailing list but it doesnt seem to work anymore http://public.kitware.com/pipermail/paraview/2010-June/017989.html the compiler gives me an error in the line: vrml.View = GetActiveView() Can someone help? Att, Leonardo Pessanha GRVa-LAMCE-COPPE-UFRJ -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Mar 24 18:32:05 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 24 Mar 2015 18:32:05 -0400 Subject: [Paraview] Paraview support of FieldData in a vtkTable In-Reply-To: References: Message-ID: Livia, Which writer are you using that doesn't save the field data? Thanks, Cory On Sun, Mar 15, 2015 at 5:30 AM, wrote: > Hello, > I am thinking to store some info as FieldData of a table (for example, the > parameters used for the calculation of the data in the table - possibly > they could also be changing depending on other elements of the pipeline). I > tried a toy example in Python and it seems that vtkTable supports it (I am > able to add an array and read it back). In Paraview 4.3.1, visualizing the > field data from a python annotation works, but if I open the spreadsheet > view to see the field data I get > Warning: In > C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\VTKExtensions\Rendering\vtkMarkSelectedRows.cxx, > line 209 > > vtkMarkSelectedRows (0000000010381890): FieldAssociation type not > supported yet. Selected elements may not be shown correctly. > > > , also the writer doen't export the field data. > Should I go forward in using the FieldData of a table (just remembering > that before exporting I should use a Python annotation or a programmable > filter to read the field data) or it is actually not supported by paraview > and I should avoid it? (for example, the field data would not be updated as > the rest of the pipeline, or something like that)? > Thank you > Best regards > Livia Barazzetti > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 bloring at lbl.gov Tue Mar 24 18:34:12 2015 From: bloring at lbl.gov (Burlen Loring) Date: Tue, 24 Mar 2015 15:34:12 -0700 Subject: [Paraview] Hardware suggestions for volume rendering In-Reply-To: <5511860C.4080501@gmail.com> References: <5511860C.4080501@gmail.com> Message-ID: <5511E664.6010109@lbl.gov> I have the same issue with unstructured grids(not using the new opengl work yet). A while back I wanted to volume render a large image dataset after clipping it. The clip made it unstructured. This was on a few hundered nodes on edison, I couldn't get the unstructured volume rendering to work, it appeared to hang(took so long I couldn't tell) and it crashed a few times as well(may have ran out of memory). I think I tried a couple of the various mappers before I gave up. Would be nice to have it working better. On 3/24/2015 8:43 AM, Armin Wehrfritz wrote: > Hey Kevin and Aashish, > > I found this discussion rather interesting, especially since I'm > basically facing the same problem as Kevin. > > In almost all cases, we are dealing here with large unstructured grids > (e.g. 12M cells) and the volume rendering is performance is extremely > bad, not to say unusable, for these cases. > > I only tested it with ParaView 4.3.1 and older versions, i.e. with the > old OpenGL algorithms, but the performance is barely influenced by the > actual volume renderer (i.e. GPU vs. CPU based). > > For an unstructured grid the volume rendering seems to be CPU limited > in any case, at least my CPU is at 100% for quite some time and the > GPU load is negligible. ParaView's status bar indicates that it's busy > with > "OpenGLProjectedTetrahedraMapper". > > This can be easily reproduced with the wavelet source (with e.g. 125k > points) and tessellation filter. > > So far I have resorted to resampling the data onto a structured grid. > This has the clear drawback that a structured grid with the same > resolution has about 70M grid points compared to the 12M points of the > unstructured grid. > The volume rendering performance of a 70M unstructured grid is however > already decent with the old OpenGL algorithms. > > So is there a way to improve the rendering of unstructured grids to > avoid the resampling? > > Best regards, > Armin > > > > > On 03/24/2015 04:48 PM, Aashish Chaudhary wrote: >> Hey Kevin, >> >> >> >> On Fri, Mar 20, 2015 at 2:33 PM, Kevin Lau > > wrote: >> >> Dear Aashish, >> >> Thanks for your reply. >> >> (1) >> >> We tried testing it with 2 different data sets of simulation data, >> one medium sized and one very large: >> >> Medium >> Cells: 1309489 >> Points: 247984 >> Memory [MB]: 119.179 >> Geometry [MB]: 8.201 >> >> Very Large >> Cells: 51937191 >> Points: 11019274 >> Memory [MB]: 4709.731 >> Geometry [MB]: 776.237 >> >> These datasets are unstructured grids (tetrahedral meshes) read into >> ParaView using the Phasta data reader. >> >> I see. Most of the performance improvements we have achieved is with GPU >> RayCast Volume mapper (uses image data). If you can sample your data >> into a strucuted grid then you will be able to use the new mapper. >> >> Thanks, >> >> (2) >> >> The OS used was Ubuntu >> >> (3) >> >> The graphics card was a NVIDIA Quatro K6000 running the NVIDIA >> drivers from the Ubuntu Repos (v 331.113) >> >> (4) >> >> We configured ParaView using the default CMake options, changing >> VTK_RENDERING_BACKEND=OpenGL2 and disabling all the plug-ins. These >> tests were run in serial, as building with MPI was throwing errors. >> >> (5) >> >> We expected that the OpenGL2 version of ParaView would be able to >> volume render faster than the standard OpenGL version. However the >> reported frame rates were the same in both builds when clicking and >> dragging (~2 FPS). >> >> This is a problem because we're mainly interested in visualising our >> data and having users able to rotate the model and interact with it. >> At these frame rates the response is a bit sluggish. >> >> Also I've done serial test using an OpenGL2 build on Windows using >> an old GeForce 8800 with the same medium sized data. On this machine >> the frame rate was similar at around ~1.5 FPS. >> >> (6) >> >> ParaView was built by checking out the master from git. Sadly I'm >> not on that test machine now, so I can't check the SHA >> >> Many thanks for your help again. >> >> Kevin >> >> >> On 20 March 2015 at 10:33, Aashish Chaudhary >> > > wrote: >> >> Hey Kevin, >> >> On Thu, Mar 19, 2015 at 5:33 PM, Kevin Lau >> > wrote: >> >> Dear Aashish, >> >> Thanks for your reply, I've now managed to build ParaView >> from the Master branch with VTK_RENDERING_BACKEND set to >> OpenGL2 and I have noticed a visible difference in the >> rendering. >> >> However comparison of the rendering performance in the >> interactive mode of builds with the standard OpenGL backend >> vs the OpenGL2 backend, both show similar frame rates. >> >> >> Depending on the card and features you are using you may not see >> a huge bump in performance. On some systems we have seen 300 >> times performance improvements and on others there were close >> specially when you have VSync on. Said that, can you provide >> more infromation on >> >> 1) Data size >> 2) OS >> 3) Graphics card >> 4) Features you have enabled? >> 5) You expectation and problem >> 6) What SHA of ParaView you are using? >> >> Are there other build options that I'm missing? Should I be >> building the VTK libraries themselves? >> >> >> Just make sure that you built from a clean state other than that >> you should be good. >> Thanks, >> >> >> Many thanks, >> >> Kevin >> >> >> On 3 March 2015 at 14:53, Aashish Chaudhary >> > > wrote: >> >> On Tue, Mar 3, 2015 at 2:43 PM, Kevin Lau >> > >> wrote: >> >> Dear Aashish, >> >> Thank you very much for your reply. The latest work >> you're doing on volume rendering is very impressive. >> >> >> Thanks. >> >> >> In order to access the latest VTK rendering in >> ParaView would we have to compile both the latest >> VTK and ParaView from source? Is it possible to link >> ParaView to specific VTK builds? >> >> >> Latest ParaView from source should be fine. Just make >> sure that you select VTK_RENDERING_BACKEND to OpenGL2 >> >> >> Also do you know if it is preferential to have a >> single GPU (i.e. a workstation graphics card) or >> multiple GPU (i.e. gaming graphics card) when using >> ParaView? >> >> >> If I remember correctly, we don't explicitly assign >> tasks to GPU in ParaView if running a single process. >> You can find more information here: >> http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server#Multiple_GPUs_Per_Node >> >> Hope it helps. >> >> >> Many thanks, >> >> Kevin >> >> >> On 27 February 2015 at 08:15, Aashish Chaudhary >> > > wrote: >> >> Dear Kevin, >> >> First, I would like to mention that we have been >> working hard to improve rendering in VTK that >> includes volume rendering as well. You may want >> to read this source article: >> http://www.kitware.com/source/home/post/154. >> Most of the changes related to this work is now >> available in VTK github repository in master >> branch. If you are targetting current VTK, I >> would suggest that any card that can support >> OpenGL2.1 or higher would be great. The higher >> the GPU memory the better. While these newer >> card will work with the previous version of >> volume rendering, it may not scale very well (in >> our testing that's what we have observed). >> Current the default in ParaView is OpenGL Volume >> Rendering but that is going to change sometime >> soon and once that happens you will have OpenGL2 >> backend for everything. >> >> Hope this helps. >> - Aashish >> >> >> >> On Thu, Feb 26, 2015 at 5:41 PM, Kevin Lau >> > > wrote: >> >> Hi, >> >> I'm looking to putting together a >> workstation to perform realtime volume >> rendering of our simulation data. >> >> Are there any particular GPU features I >> should look for? >> >> If there are multiple GPUs will Paraview be >> able to take advantage of each GPU for >> volume rendering? >> >> Many thanks >> >> Kevin >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the >> ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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/ >> >> >> >> >> >> -- >> /| Aashish Chaudhary >> | Technical Leader >> | Kitware Inc. >> / >> /| http://www.kitware.com/company/team/chaudhary.html/ >> >> >> >> >> >> -- >> /| Aashish Chaudhary >> | Technical Leader >> | Kitware Inc. >> / >> /| http://www.kitware.com/company/team/chaudhary.html/ >> >> >> >> >> >> -- >> /| 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 From aashish.chaudhary at kitware.com Tue Mar 24 19:31:39 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Tue, 24 Mar 2015 19:31:39 -0400 Subject: [Paraview] Hardware suggestions for volume rendering In-Reply-To: <5511E664.6010109@lbl.gov> References: <5511860C.4080501@gmail.com> <5511E664.6010109@lbl.gov> Message-ID: Okay, I will talk to some folks here to see what we can do to address these issues. - Aashish On Tue, Mar 24, 2015 at 6:34 PM, Burlen Loring wrote: > I have the same issue with unstructured grids(not using the new opengl > work yet). A while back I wanted to volume render a large image dataset > after clipping it. The clip made it unstructured. This was on a few > hundered nodes on edison, I couldn't get the unstructured volume rendering > to work, it appeared to hang(took so long I couldn't tell) and it crashed a > few times as well(may have ran out of memory). I think I tried a couple of > the various mappers before I gave up. Would be nice to have it working > better. > > > On 3/24/2015 8:43 AM, Armin Wehrfritz wrote: > >> Hey Kevin and Aashish, >> >> I found this discussion rather interesting, especially since I'm >> basically facing the same problem as Kevin. >> >> In almost all cases, we are dealing here with large unstructured grids >> (e.g. 12M cells) and the volume rendering is performance is extremely bad, >> not to say unusable, for these cases. >> >> I only tested it with ParaView 4.3.1 and older versions, i.e. with the >> old OpenGL algorithms, but the performance is barely influenced by the >> actual volume renderer (i.e. GPU vs. CPU based). >> >> For an unstructured grid the volume rendering seems to be CPU limited in >> any case, at least my CPU is at 100% for quite some time and the GPU load >> is negligible. ParaView's status bar indicates that it's busy with >> "OpenGLProjectedTetrahedraMapper". >> >> This can be easily reproduced with the wavelet source (with e.g. 125k >> points) and tessellation filter. >> >> So far I have resorted to resampling the data onto a structured grid. >> This has the clear drawback that a structured grid with the same resolution >> has about 70M grid points compared to the 12M points of the unstructured >> grid. >> The volume rendering performance of a 70M unstructured grid is however >> already decent with the old OpenGL algorithms. >> >> So is there a way to improve the rendering of unstructured grids to avoid >> the resampling? >> >> Best regards, >> Armin >> >> >> >> >> On 03/24/2015 04:48 PM, Aashish Chaudhary wrote: >> >>> Hey Kevin, >>> >>> >>> >>> On Fri, Mar 20, 2015 at 2:33 PM, Kevin Lau >> > wrote: >>> >>> Dear Aashish, >>> >>> Thanks for your reply. >>> >>> (1) >>> >>> We tried testing it with 2 different data sets of simulation data, >>> one medium sized and one very large: >>> >>> Medium >>> Cells: 1309489 >>> Points: 247984 >>> Memory [MB]: 119.179 >>> Geometry [MB]: 8.201 >>> >>> Very Large >>> Cells: 51937191 >>> Points: 11019274 >>> Memory [MB]: 4709.731 >>> Geometry [MB]: 776.237 >>> >>> These datasets are unstructured grids (tetrahedral meshes) read into >>> ParaView using the Phasta data reader. >>> >>> I see. Most of the performance improvements we have achieved is with GPU >>> RayCast Volume mapper (uses image data). If you can sample your data >>> into a strucuted grid then you will be able to use the new mapper. >>> >>> Thanks, >>> >>> (2) >>> >>> The OS used was Ubuntu >>> >>> (3) >>> >>> The graphics card was a NVIDIA Quatro K6000 running the NVIDIA >>> drivers from the Ubuntu Repos (v 331.113) >>> >>> (4) >>> >>> We configured ParaView using the default CMake options, changing >>> VTK_RENDERING_BACKEND=OpenGL2 and disabling all the plug-ins. These >>> tests were run in serial, as building with MPI was throwing errors. >>> >>> (5) >>> >>> We expected that the OpenGL2 version of ParaView would be able to >>> volume render faster than the standard OpenGL version. However the >>> reported frame rates were the same in both builds when clicking and >>> dragging (~2 FPS). >>> >>> This is a problem because we're mainly interested in visualising our >>> data and having users able to rotate the model and interact with it. >>> At these frame rates the response is a bit sluggish. >>> >>> Also I've done serial test using an OpenGL2 build on Windows using >>> an old GeForce 8800 with the same medium sized data. On this machine >>> the frame rate was similar at around ~1.5 FPS. >>> >>> (6) >>> >>> ParaView was built by checking out the master from git. Sadly I'm >>> not on that test machine now, so I can't check the SHA >>> >>> Many thanks for your help again. >>> >>> Kevin >>> >>> >>> On 20 March 2015 at 10:33, Aashish Chaudhary >>> >> > wrote: >>> >>> Hey Kevin, >>> >>> On Thu, Mar 19, 2015 at 5:33 PM, Kevin Lau >>> > wrote: >>> >>> Dear Aashish, >>> >>> Thanks for your reply, I've now managed to build ParaView >>> from the Master branch with VTK_RENDERING_BACKEND set to >>> OpenGL2 and I have noticed a visible difference in the >>> rendering. >>> >>> However comparison of the rendering performance in the >>> interactive mode of builds with the standard OpenGL backend >>> vs the OpenGL2 backend, both show similar frame rates. >>> >>> >>> Depending on the card and features you are using you may not see >>> a huge bump in performance. On some systems we have seen 300 >>> times performance improvements and on others there were close >>> specially when you have VSync on. Said that, can you provide >>> more infromation on >>> >>> 1) Data size >>> 2) OS >>> 3) Graphics card >>> 4) Features you have enabled? >>> 5) You expectation and problem >>> 6) What SHA of ParaView you are using? >>> >>> Are there other build options that I'm missing? Should I be >>> building the VTK libraries themselves? >>> >>> >>> Just make sure that you built from a clean state other than that >>> you should be good. >>> Thanks, >>> >>> >>> Many thanks, >>> >>> Kevin >>> >>> >>> On 3 March 2015 at 14:53, Aashish Chaudhary >>> >> > wrote: >>> >>> On Tue, Mar 3, 2015 at 2:43 PM, Kevin Lau >>> > >>> wrote: >>> >>> Dear Aashish, >>> >>> Thank you very much for your reply. The latest work >>> you're doing on volume rendering is very impressive. >>> >>> >>> Thanks. >>> >>> >>> In order to access the latest VTK rendering in >>> ParaView would we have to compile both the latest >>> VTK and ParaView from source? Is it possible to link >>> ParaView to specific VTK builds? >>> >>> >>> Latest ParaView from source should be fine. Just make >>> sure that you select VTK_RENDERING_BACKEND to OpenGL2 >>> >>> >>> Also do you know if it is preferential to have a >>> single GPU (i.e. a workstation graphics card) or >>> multiple GPU (i.e. gaming graphics card) when using >>> ParaView? >>> >>> >>> If I remember correctly, we don't explicitly assign >>> tasks to GPU in ParaView if running a single process. >>> You can find more information here: >>> http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server# >>> Multiple_GPUs_Per_Node >>> >>> Hope it helps. >>> >>> >>> Many thanks, >>> >>> Kevin >>> >>> >>> On 27 February 2015 at 08:15, Aashish Chaudhary >>> >> > wrote: >>> >>> Dear Kevin, >>> >>> First, I would like to mention that we have been >>> working hard to improve rendering in VTK that >>> includes volume rendering as well. You may want >>> to read this source article: >>> http://www.kitware.com/source/home/post/154. >>> Most of the changes related to this work is now >>> available in VTK github repository in master >>> branch. If you are targetting current VTK, I >>> would suggest that any card that can support >>> OpenGL2.1 or higher would be great. The higher >>> the GPU memory the better. While these newer >>> card will work with the previous version of >>> volume rendering, it may not scale very well (in >>> our testing that's what we have observed). >>> Current the default in ParaView is OpenGL Volume >>> Rendering but that is going to change sometime >>> soon and once that happens you will have OpenGL2 >>> backend for everything. >>> >>> Hope this helps. >>> - Aashish >>> >>> >>> >>> On Thu, Feb 26, 2015 at 5:41 PM, Kevin Lau >>> >> > wrote: >>> >>> Hi, >>> >>> I'm looking to putting together a >>> workstation to perform realtime volume >>> rendering of our simulation data. >>> >>> Are there any particular GPU features I >>> should look for? >>> >>> If there are multiple GPUs will Paraview be >>> able to take advantage of each GPU for >>> volume rendering? >>> >>> Many thanks >>> >>> Kevin >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the >>> ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> 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/ >>> >>> >>> >>> >>> >>> -- >>> /| Aashish Chaudhary >>> | Technical Leader >>> | Kitware Inc. >>> / >>> /| http://www.kitware.com/company/team/chaudhary.html/ >>> >>> >>> >>> >>> >>> -- >>> /| Aashish Chaudhary >>> | Technical Leader >>> | Kitware Inc. >>> / >>> /| http://www.kitware.com/company/team/chaudhary.html/ >>> >>> >>> >>> >>> >>> -- >>> /| 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 >> > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From mshoji-tky at umin.ac.jp Tue Mar 24 22:23:59 2015 From: mshoji-tky at umin.ac.jp (Masaaki SHOJIMA) Date: Wed, 25 Mar 2015 11:23:59 +0900 Subject: [Paraview] Fwd: Gradient of Unstructed dataset In-Reply-To: References: <5507D199.5040505@gmail.com> Message-ID: Hi Berk, Thank you for your greatest efforts. It makes sense to me, but I have to wait for the future version since I dont have skills to integrate the CGNS reader plug-in into the Paraview binary... Thanks anyway and Best wishes, Masaaki 2015-03-25 2:13 GMT+09:00 Berk Geveci : > Hi Masaaki and others that may be interested, > > I identified the issue. The default CGSN reader that we use (which is from > VisIt originally) produces incorrect results. The pressure values are > incorrect. If you load the CGNS reader plugin and open the CGNS file with > that, you will see the correct results. I tested this with the nightly > binary of ParaView. I will ask someone in the ParaView team to disable the > VisIt CGNS reader and move the plugin into ParaView proper so that we can > use it by default. > > Best, > -berk > > On Wed, Mar 18, 2015 at 8:59 AM, Berk Geveci > wrote: > >> Thanks Masaaki. I will look into it. >> >> I wish that I could say the same about northern New York State. The high >> temperature for today and tomorrow is 30F (-1C). Most of the snow melted >> though so spring is coming :-) >> >> -berk >> >> On Tue, Mar 17, 2015 at 8:04 PM, Masaaki SHOJIMA >> wrote: >> >>> Hi Berk, Armin, Michael and friends >>> >>> It is getting warm and flowers are starting to bloom in japan, this >>> morning. >>> >>> Nightly Builds of Paraview was downloaded on 2015-Mar-18 >>> (ParaView-Windows-64bit-NIGHTLY.zip). >>> >>> Gradient of Pressure was calculated using "Gradient of Unstrucutred >>> Dataset" filter and Z component of Grad (pressure) was visualized. >>> >>> Unfortunately, Nightly build did not settle the problem... >>> The computed values by nightly builds were also half compared to those >>> of Ensight. >>> >>> Could you take a look of the result in the attached PDF? >>> >>> Thanks for your continuous help. >>> >>> Masaaki >>> >>> 2015-03-17 22:01 GMT+09:00 Berk Geveci : >>> >>>> Hi Masaaki, >>>> >>>> I will hold off testing on my end until you have a chance to test with >>>> nightly binaries. Please let us know how it goes. >>>> >>>> Regards, >>>> -berk >>>> >>>> On Tue, Mar 17, 2015 at 8:09 AM, wrote: >>>> >>>>> You could test it with the nighly builds from the dashboard. That way >>>>> you don't have to compile anything. >>>>> >>>>> You can find more information here: >>>>> http://www.paraview.org/Wiki/ParaView_Nightly_Binaries >>>>> >>>>> -Armin >>>>> >>>>> >>>>> >>>>> On Tue Mar 17 12:27:27 2015 GMT+0200, Masaaki SHOJIMA wrote: >>>>> > Hi, Michael, >>>>> > >>>>> > I found a web-page regarding the CGNS reader, in which you are making >>>>> > important comments. >>>>> > http://comments.gmane.org/gmane.comp.science.paraview.user/23957 >>>>> > >>>>> > I have to wait for the next version, is it right? >>>>> > >>>>> > Thanks >>>>> > >>>>> > Masaaki >>>>> > >>>>> > 2015-03-17 16:02 GMT+09:00 Mickael Philit : >>>>> > >>>>> > > Hello, >>>>> > > >>>>> > > sorry to intrude, >>>>> > > I think the problem may come from the CGNS loader of ParaView. >>>>> > > When using the CGNS plugin from ParaView development version, you >>>>> get the >>>>> > > same picture as Ensight. >>>>> > > My two cents >>>>> > > >>>>> > > Mickael >>>>> > > >>>>> > > >>>>> > > On 17/03/2015 05:04, Masaaki SHOJIMA wrote: >>>>> > > >>>>> > > Hi Berk, >>>>> > > >>>>> > > I appreciate your kindness >>>>> > > >>>>> > > Here, I attaches the data. >>>>> > > Compare Gradient.pdf (252KB) >>>>> > > >>>>> > > A calculated field by SC/Tetra solver is uploaded in Dropbox. >>>>> (Calc.zip) >>>>> > > Please download the data. It contains FLD format for SC/Tetra post >>>>> and >>>>> > > CGNS format for Ensight and Paraview. >>>>> > > https://www.dropbox.com/s/5fpeu1qwhyzjn5u/Calc.zip?dl=0 >>>>> > > >>>>> > > (1) I calculated the flow and the pressure in a simple cylinder >>>>> for a test >>>>> > > ( diameter 0.005m, length 0.01m). Plug flow at inlet with 0.03 m/s. >>>>> > > >>>>> > > (2) Data were transfered to Ensight and Paraview in CGNS format. >>>>> > > >>>>> > > (3) Pressure was mapped on the surface and compared between >>>>> SC/Tetra post, >>>>> > > Ensight and Paraview. All application provided same results. >>>>> > > >>>>> > > (4) Gradient (pressure) was calculated in each post and >>>>> z-component of >>>>> > > Gradient (pressure) was visualized with same colored contour. Only >>>>> paraview >>>>> > > provided a different image because the computed gradients in >>>>> paraview had >>>>> > > half values compared to SC/Tetra post and Ensight. >>>>> > > >>>>> > > (5) Gradient (velocity-X) was also calculated in each post and the >>>>> > > X-component of Grad (velocity-X) was visualized. Same results as >>>>> shown in 4. >>>>> > > >>>>> > > >>>>> > > Thanks a lot. >>>>> > > >>>>> > > Masaaki >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > _______________________________________________ >>>>> > > Powered by www.kitware.com >>>>> > > >>>>> > > Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> > > >>>>> > > Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> > > >>>>> > > Search the list archives at: >>>>> http://markmail.org/search/?q=ParaView >>>>> > > >>>>> > > Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> > > >>>>> > > >>>>> > > >>>>> > >>>>> >>>>> -- >>>>> Sent from my Jolla >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> 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 sebastien.jourdain at kitware.com Tue Mar 24 22:47:24 2015 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Tue, 24 Mar 2015 20:47:24 -0600 Subject: [Paraview] Exporting VRML file series with python script In-Reply-To: References: Message-ID: try vrml.SetView(GetActiveView().SMProxy) On Tue, Mar 24, 2015 at 3:22 PM, L?o Pessanha wrote: > Hi, > > I would like to export a series of vtk files in the VRML format trough > scripting, i found a script in the mailing list but it doesnt seem to work > anymore > > http://public.kitware.com/pipermail/paraview/2010-June/017989.html > > the compiler gives me an error in the line: > > vrml.View = GetActiveView() > > Can someone help? > > Att, > Leonardo Pessanha > GRVa-LAMCE-COPPE-UFRJ > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 Wed Mar 25 02:49:09 2015 From: mickey.phy at gmail.com (Mickael Philit) Date: Wed, 25 Mar 2015 07:49:09 +0100 Subject: [Paraview] Issue with structured grids and extraction of boundaries with cell data In-Reply-To: <550C3C08.2090101@gmail.com> References: <550C3C08.2090101@gmail.com> Message-ID: <55125A65.9000707@gmail.com> Hello, my previous mail was wrong. The present problem is not related to those other bugs. Here, when using ExtractSubset the extent for cell data in miscalculated if i==imax or j==jmax or k == kmax. in vtkExtractGrid.cxx: we have the call "this->Internal->CopyCellData(inExt,outExt,cd,outCD);" that use point extent and then in vtkExtractStructuredGridHelper.cxx the extent is computed for cells "vtkStructuredData::GetCellExtentFromPointExtent(outExt,outCellExt);" but this later function does not know about the whole extent of cell data. Thus you need to pass down a valid extent for cells before calling it. If you have inExt = {0, 30, 0, 20, 0, 10} and you pass outExt = {0,30,0,20, 10,10} the result outCellExt will be {0,29,0,19,*10,10*} and then the copy of cell data will be done outside of the array leading to segfault. The outExt extent should have been corrected to be {0,30,0,20,9,10} or {0,30,0,20,9,9}... I hope it is clearer now. Best Regards Mickael On 20/03/2015 16:26, Etienne Tang wrote: > Hello, > > I'm working with a 3D structured dataset containing cell data. I tried > to extract a 2D boundary of this dataset corresponding to the maximum > index of a dimension with the Extract Subset filter and ParaView 4.3.1, > and I found an issue: the resulting dataset is incorrect. It holds cell > data from the opposite boundary (eg. if I try to extract the i = imax > boundary, I get values from i = 0 boundary), and these values are > shifted of one index in the other dimensions. > > This case worked with ParaView 4.1.0, maybe it is related to this other > bug about structured data : > http://markmail.org/message/fvatgidqbvnufgi6#query:+page:1+mid:fvatgidqbvnufgi6+state:results > ? > > Here are some pictures showing the problem on a simple dataset which can > be used to reproduce it: > - The simple .vts file : http://z1.gb2n.org/pv/test.vts > - The original dataset : http://z1.gb2n.org/pv/original_dataset.png > - The result of the ExtractSubset filter to extract the i = imax > boundary : http://z1.gb2n.org/pv/extract_subset.png > > Best regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: From livia.barazzetti at istb.unibe.ch Wed Mar 25 04:24:48 2015 From: livia.barazzetti at istb.unibe.ch (livia.barazzetti at istb.unibe.ch) Date: Wed, 25 Mar 2015 08:24:48 +0000 Subject: [Paraview] Load text file delimited by tab Message-ID: Hello, As an update to this issue (not being able to set tab as field delimiter character for the csv reader in the gui - it works only copy&pasting or setting the field delimiter in python shell), I just found out that this setting is also not loaded from the .pvsm file in paraview 4.3.1, while it was in paraview 4.1.0 Regards Livia Barazzetti -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Wed Mar 25 09:24:35 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Wed, 25 Mar 2015 09:24:35 -0400 Subject: [Paraview] Fwd: Gradient of Unstructed dataset In-Reply-To: References: <5507D199.5040505@gmail.com> Message-ID: Hi Masaaki, You don't have to wait. Simply download the latest nightly binary and the go to Tools -> Manage Plugins. There you should see the CGNS plugin. Load it. After that, when you open the CGNS file, it will give you an option to use the plugin based reader. Best, -berk On Tue, Mar 24, 2015 at 10:23 PM, Masaaki SHOJIMA wrote: > Hi Berk, > > Thank you for your greatest efforts. > > It makes sense to me, but I have to wait for the future version since I > dont have skills to integrate the CGNS reader plug-in into the Paraview > binary... > > Thanks anyway and Best wishes, > > Masaaki > > 2015-03-25 2:13 GMT+09:00 Berk Geveci : > >> Hi Masaaki and others that may be interested, >> >> I identified the issue. The default CGSN reader that we use (which is >> from VisIt originally) produces incorrect results. The pressure values are >> incorrect. If you load the CGNS reader plugin and open the CGNS file with >> that, you will see the correct results. I tested this with the nightly >> binary of ParaView. I will ask someone in the ParaView team to disable the >> VisIt CGNS reader and move the plugin into ParaView proper so that we can >> use it by default. >> >> Best, >> -berk >> >> On Wed, Mar 18, 2015 at 8:59 AM, Berk Geveci >> wrote: >> >>> Thanks Masaaki. I will look into it. >>> >>> I wish that I could say the same about northern New York State. The high >>> temperature for today and tomorrow is 30F (-1C). Most of the snow melted >>> though so spring is coming :-) >>> >>> -berk >>> >>> On Tue, Mar 17, 2015 at 8:04 PM, Masaaki SHOJIMA >>> wrote: >>> >>>> Hi Berk, Armin, Michael and friends >>>> >>>> It is getting warm and flowers are starting to bloom in japan, this >>>> morning. >>>> >>>> Nightly Builds of Paraview was downloaded on 2015-Mar-18 >>>> (ParaView-Windows-64bit-NIGHTLY.zip). >>>> >>>> Gradient of Pressure was calculated using "Gradient of Unstrucutred >>>> Dataset" filter and Z component of Grad (pressure) was visualized. >>>> >>>> Unfortunately, Nightly build did not settle the problem... >>>> The computed values by nightly builds were also half compared to those >>>> of Ensight. >>>> >>>> Could you take a look of the result in the attached PDF? >>>> >>>> Thanks for your continuous help. >>>> >>>> Masaaki >>>> >>>> 2015-03-17 22:01 GMT+09:00 Berk Geveci : >>>> >>>>> Hi Masaaki, >>>>> >>>>> I will hold off testing on my end until you have a chance to test with >>>>> nightly binaries. Please let us know how it goes. >>>>> >>>>> Regards, >>>>> -berk >>>>> >>>>> On Tue, Mar 17, 2015 at 8:09 AM, wrote: >>>>> >>>>>> You could test it with the nighly builds from the dashboard. That way >>>>>> you don't have to compile anything. >>>>>> >>>>>> You can find more information here: >>>>>> http://www.paraview.org/Wiki/ParaView_Nightly_Binaries >>>>>> >>>>>> -Armin >>>>>> >>>>>> >>>>>> >>>>>> On Tue Mar 17 12:27:27 2015 GMT+0200, Masaaki SHOJIMA wrote: >>>>>> > Hi, Michael, >>>>>> > >>>>>> > I found a web-page regarding the CGNS reader, in which you are >>>>>> making >>>>>> > important comments. >>>>>> > http://comments.gmane.org/gmane.comp.science.paraview.user/23957 >>>>>> > >>>>>> > I have to wait for the next version, is it right? >>>>>> > >>>>>> > Thanks >>>>>> > >>>>>> > Masaaki >>>>>> > >>>>>> > 2015-03-17 16:02 GMT+09:00 Mickael Philit : >>>>>> > >>>>>> > > Hello, >>>>>> > > >>>>>> > > sorry to intrude, >>>>>> > > I think the problem may come from the CGNS loader of ParaView. >>>>>> > > When using the CGNS plugin from ParaView development version, you >>>>>> get the >>>>>> > > same picture as Ensight. >>>>>> > > My two cents >>>>>> > > >>>>>> > > Mickael >>>>>> > > >>>>>> > > >>>>>> > > On 17/03/2015 05:04, Masaaki SHOJIMA wrote: >>>>>> > > >>>>>> > > Hi Berk, >>>>>> > > >>>>>> > > I appreciate your kindness >>>>>> > > >>>>>> > > Here, I attaches the data. >>>>>> > > Compare Gradient.pdf (252KB) >>>>>> > > >>>>>> > > A calculated field by SC/Tetra solver is uploaded in Dropbox. >>>>>> (Calc.zip) >>>>>> > > Please download the data. It contains FLD format for SC/Tetra >>>>>> post and >>>>>> > > CGNS format for Ensight and Paraview. >>>>>> > > https://www.dropbox.com/s/5fpeu1qwhyzjn5u/Calc.zip?dl=0 >>>>>> > > >>>>>> > > (1) I calculated the flow and the pressure in a simple cylinder >>>>>> for a test >>>>>> > > ( diameter 0.005m, length 0.01m). Plug flow at inlet with 0.03 >>>>>> m/s. >>>>>> > > >>>>>> > > (2) Data were transfered to Ensight and Paraview in CGNS format. >>>>>> > > >>>>>> > > (3) Pressure was mapped on the surface and compared between >>>>>> SC/Tetra post, >>>>>> > > Ensight and Paraview. All application provided same results. >>>>>> > > >>>>>> > > (4) Gradient (pressure) was calculated in each post and >>>>>> z-component of >>>>>> > > Gradient (pressure) was visualized with same colored contour. >>>>>> Only paraview >>>>>> > > provided a different image because the computed gradients in >>>>>> paraview had >>>>>> > > half values compared to SC/Tetra post and Ensight. >>>>>> > > >>>>>> > > (5) Gradient (velocity-X) was also calculated in each post and the >>>>>> > > X-component of Grad (velocity-X) was visualized. Same results as >>>>>> shown in 4. >>>>>> > > >>>>>> > > >>>>>> > > Thanks a lot. >>>>>> > > >>>>>> > > Masaaki >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > _______________________________________________ >>>>>> > > Powered by www.kitware.com >>>>>> > > >>>>>> > > Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> > > >>>>>> > > Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> > > >>>>>> > > Search the list archives at: >>>>>> http://markmail.org/search/?q=ParaView >>>>>> > > >>>>>> > > Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > >>>>>> >>>>>> -- >>>>>> Sent from my Jolla >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> 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 livia.barazzetti at istb.unibe.ch Wed Mar 25 09:47:36 2015 From: livia.barazzetti at istb.unibe.ch (livia.barazzetti at istb.unibe.ch) Date: Wed, 25 Mar 2015 13:47:36 +0000 Subject: [Paraview] Paraview support of FieldData in a vtkTable In-Reply-To: References: Message-ID: Hi, I was using the writer from the gui in Paraview. I created a very simple programmable source (with output type vtkTable) with a column and a field data array, then clicked File-Save Data from the menu. In the case of a table, the writer window doesn?t allow to specify the association field, so only the row values are exported to the csv file. By the way, I see that if I apply a TableToPoints filter, the field array is copied to the polydata correctly (and can be exported from there), but I haven?t experimented with this solution further yet Thanks Livia From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: 24 March 2015 23:32 To: Barazzetti, Livia (ISTB) Cc: ParaView Subject: Re: [Paraview] Paraview support of FieldData in a vtkTable Livia, Which writer are you using that doesn't save the field data? Thanks, Cory On Sun, Mar 15, 2015 at 5:30 AM, > wrote: Hello, I am thinking to store some info as FieldData of a table (for example, the parameters used for the calculation of the data in the table - possibly they could also be changing depending on other elements of the pipeline). I tried a toy example in Python and it seems that vtkTable supports it (I am able to add an array and read it back). In Paraview 4.3.1, visualizing the field data from a python annotation works, but if I open the spreadsheet view to see the field data I get Warning: In C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\VTKExtensions\Rendering\vtkMarkSelectedRows.cxx, line 209 vtkMarkSelectedRows (0000000010381890): FieldAssociation type not supported yet. Selected elements may not be shown correctly. , also the writer doen't export the field data. Should I go forward in using the FieldData of a table (just remembering that before exporting I should use a Python annotation or a programmable filter to read the field data) or it is actually not supported by paraview and I should avoid it? (for example, the field data would not be updated as the rest of the pipeline, or something like that)? Thank you Best regards Livia Barazzetti _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 furutaka.kazuyoshi at jaea.go.jp Wed Mar 25 20:47:56 2015 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Thu, 26 Mar 2015 09:47:56 +0900 (JST) Subject: [Paraview] how not to scale the thickness of the Arrow Glyph? Message-ID: <20150326.094756.207947649.furutaka.kazuyoshi@jaea.go.jp> Dear ParaView experts, I'm visualizing paths of neutrons in some media. Now I prepared the data as point data with displacement vector to the next point attached to each point, and visualize them using the Glyph filter with the following setting: Glyph Type: Arrow Orientation: Orient Scale Mode "vector" Scale Factor = 1.0 Glyph Mode: All Points The problem is that some arrows are too thick... So here are my questions. (1)How can I make the thickness of the arrows not to scale (only the lengths do)? (2)It may be better to use "2D Glyph" instead of "Arrow", but the 2D Glyph is centered at a data point, instead of starting from the point... How can I make the 2D Glyphs start from the data points? (3)Do you have any recommendation on how to visualize such a particle paths? Thanks in advance, Kazuyoshi -- Kazuyoshi Furutaka furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp -------------- next part -------------- A non-text attachment was scrubbed... Name: arrows.png Type: image/png Size: 30281 bytes Desc: arrows.png URL: From david.thompson at kitware.com Wed Mar 25 23:01:51 2015 From: david.thompson at kitware.com (David Thompson) Date: Wed, 25 Mar 2015 23:01:51 -0400 Subject: [Paraview] how not to scale the thickness of the Arrow Glyph? In-Reply-To: <20150326.094756.207947649.furutaka.kazuyoshi@jaea.go.jp> References: <20150326.094756.207947649.furutaka.kazuyoshi@jaea.go.jp> Message-ID: <305BB950-5456-49EA-B486-54282BB1503E@kitware.com> Hi Kazuyoshi, I do not think the glyph filter will do what you want it to. You might use a Python programmable filter[1] to turn each point into a line segment (i.e., a line from (x,y,z) to (x+dx, y+dy, z+dz)). Then run "Cell Centers" on the resulting line segment data and add oriented, unscaled cone glyphs at each cell center to indicate the direction along the line segments. That would draw lines along the path plus cones pointing along the direction of the path. David [1]: http://www.paraview.org/Wiki/Python_Programmable_Filter > On Mar 25, 2015, at 8:47 PM, Kazuyoshi Furutaka wrote: > > Dear ParaView experts, > > I'm visualizing paths of neutrons in some media. > Now I prepared the data as point data with displacement > vector to the next point attached to each point, and > visualize them using the Glyph filter with the following > setting: > Glyph Type: Arrow > Orientation: Orient > Scale Mode "vector" > Scale Factor = 1.0 > Glyph Mode: All Points > > The problem is that some arrows are too thick... > > So here are my questions. > > (1)How can I make the thickness of the arrows not > to scale (only the lengths do)? > > (2)It may be better to use "2D Glyph" instead of > "Arrow", but the 2D Glyph is centered at a > data point, instead of starting from the point... > How can I make the 2D Glyphs start from the data > points? > > (3)Do you have any recommendation on how to visualize > such a particle paths? > > Thanks in advance, > > Kazuyoshi > -- > Kazuyoshi Furutaka > furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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 cory.quammen at kitware.com Wed Mar 25 23:36:24 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 25 Mar 2015 23:36:24 -0400 Subject: [Paraview] Paraview support of FieldData in a vtkTable In-Reply-To: References: Message-ID: Livia, It seems reasonable that you should be able to save field data stored in a vtkTable. Would you mind writing up a feature request at http://www.paraview.org/Bug/view_all_bug_page.php? Thanks, Cory On Wed, Mar 25, 2015 at 9:47 AM, wrote: > Hi, > > I was using the writer from the gui in Paraview. I created a very simple > programmable source (with output type vtkTable) with a column and a field > data array, then clicked File-Save Data from the menu. > > In the case of a table, the writer window doesn?t allow to specify the > association field, so only the row values are exported to the csv file. > > By the way, I see that if I apply a TableToPoints filter, the field array > is copied to the polydata correctly (and can be exported from there), but I > haven?t experimented with this solution further yet > > Thanks > > Livia > > > > *From:* Cory Quammen [mailto:cory.quammen at kitware.com] > *Sent:* 24 March 2015 23:32 > *To:* Barazzetti, Livia (ISTB) > *Cc:* ParaView > *Subject:* Re: [Paraview] Paraview support of FieldData in a vtkTable > > > > Livia, > > > > Which writer are you using that doesn't save the field data? > > > > Thanks, > > Cory > > > > On Sun, Mar 15, 2015 at 5:30 AM, wrote: > > Hello, > > I am thinking to store some info as FieldData of a table (for example, the > parameters used for the calculation of the data in the table - possibly > they could also be changing depending on other elements of the pipeline). I > tried a toy example in Python and it seems that vtkTable supports it (I am > able to add an array and read it back). In Paraview 4.3.1, visualizing the > field data from a python annotation works, but if I open the spreadsheet > view to see the field data I get > > Warning: In > C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\VTKExtensions\Rendering\vtkMarkSelectedRows.cxx, > line 209 > > vtkMarkSelectedRows (0000000010381890): FieldAssociation type not > supported yet. Selected elements may not be shown correctly. > > > > , also the writer doen't export the field data. > > Should I go forward in using the FieldData of a table (just remembering > that before exporting I should use a Python annotation or a programmable > filter to read the field data) or it is actually not supported by paraview > and I should avoid it? (for example, the field data would not be updated as > the rest of the pipeline, or something like that)? > > Thank you > > Best regards > > Livia Barazzetti > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > > -- > > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Mar 25 23:46:57 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 25 Mar 2015 23:46:57 -0400 Subject: [Paraview] .ini File Change in Version 4.2 In-Reply-To: References: Message-ID: Hi Matthew, Settings have been revamped since version 2.4. While some still are stored in the usual .ini file, most are now stored in a JSON file which is described on this blog post: http://www.kitware.com/blog/home/post/672 While the blog post focuses on setting custom defaults, the general settings are stored in the same way as custom defaults. For the Auto Apply setting, your ParaView-UserSettings.json file will need to have at least the following: { "settings" : { "GeneralSettings" : { "AutoApply" : 1 } } } To see what you should put in your ParaView-UserSettings.json file, it is probably easiest to set them in the ParaView GUI and then close the program. Your ParaView-UserSettings.json file will be updated with the JSON you need. I hope that helps, Cory On Tue, Mar 24, 2015 at 8:39 AM, Matthew Jackson wrote: > Hello, > > > > I recently started using Paraview 4.3 instead of Paraview 4.1. I notice > that the way the settings are stored was changed in 4.2. Before, I could > change the Auto Apply setting in the Property Panel Options by editing the > .ini file. I also need to change a few other options. This is for an > application I am developing that uses Paraview, and I need to set these > settings automatically every time the application launches Paraview. Does > anybody know how to do this in version 4.2+? > > > > Regards, > > Matthew Jackson > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 furutaka.kazuyoshi at jaea.go.jp Thu Mar 26 01:36:41 2015 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Thu, 26 Mar 2015 14:36:41 +0900 (JST) Subject: [Paraview] how not to scale the thickness of the Arrow Glyph? In-Reply-To: <305BB950-5456-49EA-B486-54282BB1503E@kitware.com> References: <20150326.094756.207947649.furutaka.kazuyoshi@jaea.go.jp> <305BB950-5456-49EA-B486-54282BB1503E@kitware.com> Message-ID: <20150326.143641.444834243.furutaka.kazuyoshi@jaea.go.jp> Dear David, Thanks for your response. I'll give it a try. Kazuyoshi From: David Thompson Subject: Re: [Paraview] how not to scale the thickness of the Arrow Glyph? Date: Wed, 25 Mar 2015 23:01:51 -0400 > Hi Kazuyoshi, > > I do not think the glyph filter will do what you want it to. You might use a Python programmable filter[1] to turn each point into a line segment (i.e., a line from (x,y,z) to (x+dx, y+dy, z+dz)). Then run "Cell Centers" on the resulting line segment data and add oriented, unscaled cone glyphs at each cell center to indicate the direction along the line segments. That would draw lines along the path plus cones pointing along the direction of the path. > > David > > [1]: http://www.paraview.org/Wiki/Python_Programmable_Filter > > >> On Mar 25, 2015, at 8:47 PM, Kazuyoshi Furutaka wrote: >> >> Dear ParaView experts, >> >> I'm visualizing paths of neutrons in some media. >> Now I prepared the data as point data with displacement >> vector to the next point attached to each point, and >> visualize them using the Glyph filter with the following >> setting: >> Glyph Type: Arrow >> Orientation: Orient >> Scale Mode "vector" >> Scale Factor = 1.0 >> Glyph Mode: All Points >> >> The problem is that some arrows are too thick... >> >> So here are my questions. >> >> (1)How can I make the thickness of the arrows not >> to scale (only the lengths do)? >> >> (2)It may be better to use "2D Glyph" instead of >> "Arrow", but the 2D Glyph is centered at a >> data point, instead of starting from the point... >> How can I make the 2D Glyphs start from the data >> points? >> >> (3)Do you have any recommendation on how to visualize >> such a particle paths? >> >> Thanks in advance, >> >> Kazuyoshi >> -- >> Kazuyoshi Furutaka >> furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> 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 mshoji-tky at umin.ac.jp Thu Mar 26 02:18:58 2015 From: mshoji-tky at umin.ac.jp (Masaaki SHOJIMA) Date: Thu, 26 Mar 2015 15:18:58 +0900 Subject: [Paraview] Fwd: Gradient of Unstructed dataset In-Reply-To: References: <5507D199.5040505@gmail.com> Message-ID: Hi Berk, After I loaded "CGNSReader" , I achieved success in getting the gradient of a certain scalar same with Ensight and SC/Tetra post . I used the Paraview Nightly build g544b3a7 for mac. Thank you !! But I could not found the CGNSReader in nightly builids for win 32bit and win 64bit. Win 32bit, g04df19f, and Win 64bit, g04df19f In the windows version, I found GMVReader, but it didn't work with CGNS ( I tried). By the way, my final goal is to calculate the wall shear stress of vessel from velocity and wall normals. Now, the barrier has been removed by you, and I can calculate and visualize the WSS in Paraview. I already see it in SC/Tetra post and Ensight. But Paraview makes more beautiful graphics and I am very happy. Thank you for your kindness !!! 2015-03-26 15:18 GMT+09:00 Masaaki SHOJIMA : > Hi Berk, > > After I loaded "CGNSReader" , I achieved success in getting the gradient > of a certain scalar same with Ensight and SC/Tetra post . I used the > Paraview Nightly build g544b3a7 for mac. Thank you !! > > But I could not found the CGNSReader in nightly builids for win 32bit and > win 64bit. > Win 32bit, g04df19f, and Win 64bit, g04df19f > In the windows version, I found GMVReader, but it didn't work with CGNS ( > I tried). > > By the way, my final goal is to calculate the wall shear stress of vessel > from velocity and wall normals. > Now, the barrier has been removed by you, and I can calculate and > visualize the WSS in Paraview. I already see it in SC/Tetra post and > Ensight. But Paraview makes more beautiful graphics and I am very happy. > > Thank you for your kindness !!! > > Masaaki > > 2015-03-25 22:24 GMT+09:00 Berk Geveci : > >> Hi Masaaki, >> >> You don't have to wait. Simply download the latest nightly binary and the >> go to Tools -> Manage Plugins. There you should see the CGNS plugin. Load >> it. After that, when you open the CGNS file, it will give you an option to >> use the plugin based reader. >> >> Best, >> -berk >> >> On Tue, Mar 24, 2015 at 10:23 PM, Masaaki SHOJIMA >> wrote: >> >>> Hi Berk, >>> >>> Thank you for your greatest efforts. >>> >>> It makes sense to me, but I have to wait for the future version since I >>> dont have skills to integrate the CGNS reader plug-in into the Paraview >>> binary... >>> >>> Thanks anyway and Best wishes, >>> >>> Masaaki >>> >>> 2015-03-25 2:13 GMT+09:00 Berk Geveci : >>> >>>> Hi Masaaki and others that may be interested, >>>> >>>> I identified the issue. The default CGSN reader that we use (which is >>>> from VisIt originally) produces incorrect results. The pressure values are >>>> incorrect. If you load the CGNS reader plugin and open the CGNS file with >>>> that, you will see the correct results. I tested this with the nightly >>>> binary of ParaView. I will ask someone in the ParaView team to disable the >>>> VisIt CGNS reader and move the plugin into ParaView proper so that we can >>>> use it by default. >>>> >>>> Best, >>>> -berk >>>> >>>> On Wed, Mar 18, 2015 at 8:59 AM, Berk Geveci >>>> wrote: >>>> >>>>> Thanks Masaaki. I will look into it. >>>>> >>>>> I wish that I could say the same about northern New York State. The >>>>> high temperature for today and tomorrow is 30F (-1C). Most of the snow >>>>> melted though so spring is coming :-) >>>>> >>>>> -berk >>>>> >>>>> On Tue, Mar 17, 2015 at 8:04 PM, Masaaki SHOJIMA < >>>>> mshoji-tky at umin.ac.jp> wrote: >>>>> >>>>>> Hi Berk, Armin, Michael and friends >>>>>> >>>>>> It is getting warm and flowers are starting to bloom in japan, this >>>>>> morning. >>>>>> >>>>>> Nightly Builds of Paraview was downloaded on 2015-Mar-18 >>>>>> (ParaView-Windows-64bit-NIGHTLY.zip). >>>>>> >>>>>> Gradient of Pressure was calculated using "Gradient of Unstrucutred >>>>>> Dataset" filter and Z component of Grad (pressure) was visualized. >>>>>> >>>>>> Unfortunately, Nightly build did not settle the problem... >>>>>> The computed values by nightly builds were also half compared to >>>>>> those of Ensight. >>>>>> >>>>>> Could you take a look of the result in the attached PDF? >>>>>> >>>>>> Thanks for your continuous help. >>>>>> >>>>>> Masaaki >>>>>> >>>>>> 2015-03-17 22:01 GMT+09:00 Berk Geveci : >>>>>> >>>>>>> Hi Masaaki, >>>>>>> >>>>>>> I will hold off testing on my end until you have a chance to test >>>>>>> with nightly binaries. Please let us know how it goes. >>>>>>> >>>>>>> Regards, >>>>>>> -berk >>>>>>> >>>>>>> On Tue, Mar 17, 2015 at 8:09 AM, wrote: >>>>>>> >>>>>>>> You could test it with the nighly builds from the dashboard. That >>>>>>>> way you don't have to compile anything. >>>>>>>> >>>>>>>> You can find more information here: >>>>>>>> http://www.paraview.org/Wiki/ParaView_Nightly_Binaries >>>>>>>> >>>>>>>> -Armin >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Tue Mar 17 12:27:27 2015 GMT+0200, Masaaki SHOJIMA wrote: >>>>>>>> > Hi, Michael, >>>>>>>> > >>>>>>>> > I found a web-page regarding the CGNS reader, in which you are >>>>>>>> making >>>>>>>> > important comments. >>>>>>>> > http://comments.gmane.org/gmane.comp.science.paraview.user/23957 >>>>>>>> > >>>>>>>> > I have to wait for the next version, is it right? >>>>>>>> > >>>>>>>> > Thanks >>>>>>>> > >>>>>>>> > Masaaki >>>>>>>> > >>>>>>>> > 2015-03-17 16:02 GMT+09:00 Mickael Philit : >>>>>>>> > >>>>>>>> > > Hello, >>>>>>>> > > >>>>>>>> > > sorry to intrude, >>>>>>>> > > I think the problem may come from the CGNS loader of ParaView. >>>>>>>> > > When using the CGNS plugin from ParaView development version, >>>>>>>> you get the >>>>>>>> > > same picture as Ensight. >>>>>>>> > > My two cents >>>>>>>> > > >>>>>>>> > > Mickael >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > On 17/03/2015 05:04, Masaaki SHOJIMA wrote: >>>>>>>> > > >>>>>>>> > > Hi Berk, >>>>>>>> > > >>>>>>>> > > I appreciate your kindness >>>>>>>> > > >>>>>>>> > > Here, I attaches the data. >>>>>>>> > > Compare Gradient.pdf (252KB) >>>>>>>> > > >>>>>>>> > > A calculated field by SC/Tetra solver is uploaded in Dropbox. >>>>>>>> (Calc.zip) >>>>>>>> > > Please download the data. It contains FLD format for SC/Tetra >>>>>>>> post and >>>>>>>> > > CGNS format for Ensight and Paraview. >>>>>>>> > > https://www.dropbox.com/s/5fpeu1qwhyzjn5u/Calc.zip?dl=0 >>>>>>>> > > >>>>>>>> > > (1) I calculated the flow and the pressure in a simple cylinder >>>>>>>> for a test >>>>>>>> > > ( diameter 0.005m, length 0.01m). Plug flow at inlet with 0.03 >>>>>>>> m/s. >>>>>>>> > > >>>>>>>> > > (2) Data were transfered to Ensight and Paraview in CGNS format. >>>>>>>> > > >>>>>>>> > > (3) Pressure was mapped on the surface and compared between >>>>>>>> SC/Tetra post, >>>>>>>> > > Ensight and Paraview. All application provided same results. >>>>>>>> > > >>>>>>>> > > (4) Gradient (pressure) was calculated in each post and >>>>>>>> z-component of >>>>>>>> > > Gradient (pressure) was visualized with same colored contour. >>>>>>>> Only paraview >>>>>>>> > > provided a different image because the computed gradients in >>>>>>>> paraview had >>>>>>>> > > half values compared to SC/Tetra post and Ensight. >>>>>>>> > > >>>>>>>> > > (5) Gradient (velocity-X) was also calculated in each post and >>>>>>>> the >>>>>>>> > > X-component of Grad (velocity-X) was visualized. Same results >>>>>>>> as shown in 4. >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > Thanks a lot. >>>>>>>> > > >>>>>>>> > > Masaaki >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > _______________________________________________ >>>>>>>> > > Powered by www.kitware.com >>>>>>>> > > >>>>>>>> > > Visit other Kitware open-source projects at >>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>> > > >>>>>>>> > > Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>> > > >>>>>>>> > > Search the list archives at: >>>>>>>> http://markmail.org/search/?q=ParaView >>>>>>>> > > >>>>>>>> > > Follow this link to subscribe/unsubscribe: >>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > >>>>>>>> >>>>>>>> -- >>>>>>>> Sent from my Jolla >>>>>>>> _______________________________________________ >>>>>>>> Powered by www.kitware.com >>>>>>>> >>>>>>>> Visit other Kitware open-source projects at >>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>> >>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>> >>>>>>>> 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 felipe.bordeu at ec-nantes.fr Thu Mar 26 04:20:57 2015 From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu Weldt) Date: Thu, 26 Mar 2015 09:20:57 +0100 Subject: [Paraview] how not to scale the thickness of the Arrow Glyph? In-Reply-To: <20150326.094756.207947649.furutaka.kazuyoshi@jaea.go.jp> References: <20150326.094756.207947649.furutaka.kazuyoshi@jaea.go.jp> Message-ID: <7460F02A-D0B5-4CC5-B5A3-A9D24A0AE03F@ec-nantes.fr> Or you can move your points half the distance with the calculator (coords +0.5*dep) and then apply the 2D Glyph Felipe Le 26 mars 2015 ? 01:47, Kazuyoshi Furutaka a ?crit : > Dear ParaView experts, > > I'm visualizing paths of neutrons in some media. > Now I prepared the data as point data with displacement > vector to the next point attached to each point, and > visualize them using the Glyph filter with the following > setting: > Glyph Type: Arrow > Orientation: Orient > Scale Mode "vector" > Scale Factor = 1.0 > Glyph Mode: All Points > > The problem is that some arrows are too thick... > > So here are my questions. > > (1)How can I make the thickness of the arrows not > to scale (only the lengths do)? > > (2)It may be better to use "2D Glyph" instead of > "Arrow", but the 2D Glyph is centered at a > data point, instead of starting from the point... > How can I make the 2D Glyphs start from the data > points? > > (3)Do you have any recommendation on how to visualize > such a particle paths? > > Thanks in advance, > > Kazuyoshi > -- > Kazuyoshi Furutaka > furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: Message signed with OpenPGP using GPGMail URL: From dkxls23 at gmail.com Thu Mar 26 09:33:07 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Thu, 26 Mar 2015 15:33:07 +0200 Subject: [Paraview] Fetching data from xdmf temporal collection In-Reply-To: <551011f8.8f2a460a.25d3.ffff9baaSMTPIN_ADDED_BROKEN@mx.google.com> References: <551011f8.8f2a460a.25d3.ffff9baaSMTPIN_ADDED_BROKEN@mx.google.com> Message-ID: <55140A93.3080500@gmail.com> Hi Jean-Michel, just to mention, I don't think VTK is significantly more efficient than ParaView. In practice you shouldn't feel a difference, since all the heavy data handling is anyways done by VTK. Anyway, I attached a script that shows you how to read XDMF data, step through the time steps, wrap the data for numpy and print out some basic infos. Regarding the GetOutput() method, to get data object from the XDMF reader you have to use the GetOutputDataObject(0) method. But I don't know the difference between the two of them, and this also may depends on your VTK version, I'm using 6.2. -Armin On 03/23/2015 03:15 PM, Jean-Michel wrote: > Armin, > > you said you would rather use vtk directly to access raw data in xdmf > files. I tried to follow your advice, but I struggle with the > vtkXdmfReader. Basically, here is what I do: > > import vtk > > reader = vtk.vtkXdmfReader() > > reader.SetFileName(myfile) > > reader.ReadAllScalarsOn() > > reader.Update() > > However, I don't know how to access the data inside reader once this is > done. The GetOutput() method doesn't seem to work. Do you know what I am > missing here ? If not, I'll try and move the discussion over at the > vtk-users list. > > Thank you for your help. > > Jean-Michel > > > > ------------------------------------------------------------------------ > 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 -------------- A non-text attachment was scrubbed... Name: readXDMF.py Type: text/x-python Size: 1575 bytes Desc: not available URL: From jm.lucas at gantha.com Thu Mar 26 12:14:17 2015 From: jm.lucas at gantha.com (Jean-Michel) Date: Thu, 26 Mar 2015 17:14:17 +0100 Subject: [Paraview] Fetching data from xdmf temporal collection In-Reply-To: <55140A93.3080500@gmail.com> References: <551011f8.8f2a460a.25d3.ffff9baaSMTPIN_ADDED_BROKEN@mx.google.com> <55140A93.3080500@gmail.com> Message-ID: <001001d067df$eb220e70$c1662b50$@lucas@gantha.com> Hi Armin, thanks a lot for your script, it's everything I needed to be able to read my data. Jean-Michel -----Message d'origine----- De : Armin Wehrfritz [mailto:dkxls23 at gmail.com] Envoy? : jeudi 26 mars 2015 14:33 ? : Jean-Michel Cc : paraview at paraview.org Objet : Re: [Paraview] Fetching data from xdmf temporal collection Hi Jean-Michel, just to mention, I don't think VTK is significantly more efficient than ParaView. In practice you shouldn't feel a difference, since all the heavy data handling is anyways done by VTK. Anyway, I attached a script that shows you how to read XDMF data, step through the time steps, wrap the data for numpy and print out some basic infos. Regarding the GetOutput() method, to get data object from the XDMF reader you have to use the GetOutputDataObject(0) method. But I don't know the difference between the two of them, and this also may depends on your VTK version, I'm using 6.2. -Armin On 03/23/2015 03:15 PM, Jean-Michel wrote: > Armin, > > you said you would rather use vtk directly to access raw data in xdmf > files. I tried to follow your advice, but I struggle with the > vtkXdmfReader. Basically, here is what I do: > > import vtk > > reader = vtk.vtkXdmfReader() > > reader.SetFileName(myfile) > > reader.ReadAllScalarsOn() > > reader.Update() > > However, I don't know how to access the data inside reader once this > is done. The GetOutput() method doesn't seem to work. Do you know what > I am missing here ? If not, I'll try and move the discussion over at > the vtk-users list. > > Thank you for your help. > > Jean-Michel > > > > ------------------------------------------------------------------------ > 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 From ped3 at buffalo.edu Thu Mar 26 15:28:14 2015 From: ped3 at buffalo.edu (Paul DesJardin) Date: Thu, 26 Mar 2015 15:28:14 -0400 Subject: [Paraview] PlotSelectionOverTime filter in python Message-ID: Hi, I'm trying to use the PlotSelectionOverTime command in a python script for use with pvbatch. When using PlotSelectionOverTime in the GUI, there is a "Copy Active Selection" operation required which I cannot replicate in the python script. The incremental trace option doesn't appear to provide information since nothing is reported when the the "Copy Active Selection" button is pushed. Any help would be much appreciated..... Thanks! Paul From andy.bauer at kitware.com Thu Mar 26 15:49:49 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 26 Mar 2015 15:49:49 -0400 Subject: [Paraview] PlotSelectionOverTime filter in python In-Reply-To: References: Message-ID: Hi Paul, This should get tracked in the Python Trace functionality. I'll add a bug report for this. For now you can do it manually with something like: >>> w = Wavelet() >>> selection = SelectCells(query="id==0") >>> ec = ExtractSelection(Selection=selection) >>> ec.UpdatePipeline() This should select the first cell of the Wavelet source and extract it. For point selection replace SelectCells with SelectPoints. There's probably more complex selections for multiblock data sets but talking to you I thought you had an unstructured data set. For the query string, you can see how more complex queries are created in the Find Data option under the Edit menu. Let me know if this doesn't work for you. Cheers, Andy On Thu, Mar 26, 2015 at 3:28 PM, Paul DesJardin wrote: > Hi, > > I'm trying to use the PlotSelectionOverTime command in a python script > for use with pvbatch. When using PlotSelectionOverTime in the GUI, > there is a "Copy Active Selection" operation required which I cannot > replicate in the python script. The incremental trace option doesn't > appear to provide information since nothing is reported when the the > "Copy Active Selection" button is pushed. > > Any help would be much appreciated..... > > Thanks! > > Paul > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ped3 at buffalo.edu Thu Mar 26 16:10:45 2015 From: ped3 at buffalo.edu (Paul DesJardin) Date: Thu, 26 Mar 2015 16:10:45 -0400 Subject: [Paraview] PlotSelectionOverTime filter in python In-Reply-To: References: Message-ID: Hi Andy, Thanks for the quick response. I tried the following in the python window with the integrated variables highlighted in the GUI .... >>> ss = GetActiveSource() >>> selection = SelectCells(query="id==0") >>> ec = ExtractSelection(Selection=selection) >>> ec.UpdatePipeline() >>> PlotSelectionOverTime(Input=ss,Selection=ec) and the below output was spit to the the Output Messages indicating that nothing was selected. Does the above syntax make sense to you? Paul Generic Warning: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/ParaViewCore/ServerManager/Core/vtkSMTrace.cxx, line 134 Failed to generate state. Traceback (most recent call last): File "/Applications/paraview.app/Contents/Python/paraview/smstate.py", line 170, in get_state traceitem.finalize() File "/Applications/paraview.app/Contents/Python/paraview/smtrace.py", line 752, in finalize trace.append(accessor.trace_ctor(ctor, filter_type)) File "/Applications/paraview.app/Contents/Python/paraview/smtrace.py", line 430, in trace_ctor ctor_props_trace = self.trace_properties(ctor_props, in_ctor=True) File "/Applications/paraview.app/Contents/Python/paraview/smtrace.py", line 423, in trace_properties return joiner.join([x.get_property_trace(in_ctor) for x in props]) File "/Applications/paraview.app/Contents/Python/paraview/smtrace.py", line 533, in get_property_trace if in_ctor: return "%s=%s" % (varname, self.get_value()) File "/Applications/paraview.app/Contents/Python/paraview/smtrace.py", line 553, in get_value data = [str(Trace.get_accessor(x)) for x in self.get_object()[:]] File "/Applications/paraview.app/Contents/Python/paraview/smtrace.py", line 167, in get_accessor "it. Skipping this action." % repr(obj)) paraview.smtrace.Untraceable: " is not 'known' at this point. Hence, we cannot trace it. Skipping this action." Empty state generated. Generic Warning: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/ParaViewCore/ServerManager/Core/vtkSMTrace.cxx, line 112 Tracing is active. Cannot save state. Empty state generated. ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 810 vtkPVCompositeDataPipeline (0x7ff19b7f6dc0): Input for connection index 0 on input port index 1 for algorithm vtkPVExtractArraysOverTime(0x7ff198f30380) is of type vtkUnstructuredGrid, but a vtkSelection is required. ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 810 vtkPVCompositeDataPipeline (0x7ff19b7f6dc0): Input for connection index 0 on input port index 1 for algorithm vtkPVExtractArraysOverTime(0x7ff198f30380) is of type vtkUnstructuredGrid, but a vtkSelection is required. Generic Warning: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx, line 641 Call not supported for the current property type. ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 810 vtkPVCompositeDataPipeline (0x7ff19b7f6dc0): Input for connection index 0 on input port index 1 for algorithm vtkPVExtractArraysOverTime(0x7ff198f30380) is of type vtkUnstructuredGrid, but a vtkSelection is required. ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 810 vtkPVCompositeDataPipeline (0x7ff1963cedc0): Input for connection index 0 on input port index 1 for algorithm vtkPVExtractArraysOverTime(0x7ff198b8e7e0) is of type vtkUnstructuredGrid, but a vtkSelection is required. ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 810 vtkPVCompositeDataPipeline (0x7ff1963cedc0): Input for connection index 0 on input port index 1 for algorithm vtkPVExtractArraysOverTime(0x7ff198b8e7e0) is of type vtkUnstructuredGrid, but a vtkSelection is required. Generic Warning: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx, line 641 Call not supported for the current property type. On Thu, Mar 26, 2015 at 3:49 PM, Andy Bauer wrote: > Hi Paul, > > This should get tracked in the Python Trace functionality. I'll add a bug > report for this. For now you can do it manually with something like: >>>> w = Wavelet() > >>>> selection = SelectCells(query="id==0") > >>>> ec = ExtractSelection(Selection=selection) > >>>> ec.UpdatePipeline() > > > This should select the first cell of the Wavelet source and extract it. For > point selection replace SelectCells with SelectPoints. There's probably more > complex selections for multiblock data sets but talking to you I thought you > had an unstructured data set. For the query string, you can see how more > complex queries are created in the Find Data option under the Edit menu. > > > Let me know if this doesn't work for you. > > > Cheers, > > Andy > > > > On Thu, Mar 26, 2015 at 3:28 PM, Paul DesJardin wrote: >> >> Hi, >> >> I'm trying to use the PlotSelectionOverTime command in a python script >> for use with pvbatch. When using PlotSelectionOverTime in the GUI, >> there is a "Copy Active Selection" operation required which I cannot >> replicate in the python script. The incremental trace option doesn't >> appear to provide information since nothing is reported when the the >> "Copy Active Selection" button is pushed. >> >> Any help would be much appreciated..... >> >> Thanks! >> >> 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 > -- ========================================= Paul DesJardin, Ph.D. Professor University at Buffalo, State University of New York Buffalo, NY 14260-4400 Tel: 716-645-1467 email: ped3 at buffalo.edu web: cet.eng.buffalo.edu ========================================= From jayreno33 at gmail.com Thu Mar 26 16:28:07 2015 From: jayreno33 at gmail.com (Jay Romero) Date: Thu, 26 Mar 2015 15:28:07 -0500 Subject: [Paraview] Get point array data in paraview from python shell Message-ID: I am trying to get point array data ( node and its values) of a variable in paraview: so far I can use following (python shell): from paraview.simple import * out = GetActiveSource() The point array data is a velocity vector on each node, and I can calculate magnitude of a vector, next I want to treat these magnitude values as new point array data in the pipeline browser. How to do in python shell? Best Regards Jay -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Thu Mar 26 17:13:36 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 26 Mar 2015 17:13:36 -0400 Subject: [Paraview] PlotSelectionOverTime filter in python In-Reply-To: References: Message-ID: Hi Paul, I think because of the bug you'll need to cobble together the Python script you want. First you can try doing everything in the GUI and recording it in a single trace and see if manually adding in the: selection = SelectCells(query="id==0") ec = ExtractSelection(Selection=selection) ec.UpdatePipeline() PlotSelectionOverTime(Input=ss,Selection=ec) parts as needed. If this doesn't work you may have to record everything up to the above point. Then do the selection and PlotSelectionOverTime() manually in the GUI as well as appending to the Python script, and then finally doing another trace with the final couple of steps. Let me know if that works for you. Regards, Andy On Thu, Mar 26, 2015 at 4:10 PM, Paul DesJardin wrote: > Hi Andy, > > Thanks for the quick response. I tried the following in the python > window with the integrated variables highlighted in the GUI .... > > >>> ss = GetActiveSource() > >>> selection = SelectCells(query="id==0") > >>> ec = ExtractSelection(Selection=selection) > >>> ec.UpdatePipeline() > >>> PlotSelectionOverTime(Input=ss,Selection=ec) > > and the below output was spit to the the Output Messages indicating > that nothing was selected. Does the above syntax make sense to you? > > Paul > > > > > Generic Warning: In > > /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/ParaViewCore/ServerManager/Core/vtkSMTrace.cxx, > line 134 > > Failed to generate state. > > > > Traceback (most recent call last): > > File "/Applications/paraview.app/Contents/Python/paraview/smstate.py", > line 170, in get_state > > traceitem.finalize() > > File "/Applications/paraview.app/Contents/Python/paraview/smtrace.py", > line 752, in finalize > > trace.append(accessor.trace_ctor(ctor, filter_type)) > > File "/Applications/paraview.app/Contents/Python/paraview/smtrace.py", > line 430, in trace_ctor > > ctor_props_trace = self.trace_properties(ctor_props, in_ctor=True) > > File "/Applications/paraview.app/Contents/Python/paraview/smtrace.py", > line 423, in trace_properties > > return joiner.join([x.get_property_trace(in_ctor) for x in props]) > > File "/Applications/paraview.app/Contents/Python/paraview/smtrace.py", > line 533, in get_property_trace > > if in_ctor: return "%s=%s" % (varname, self.get_value()) > > File "/Applications/paraview.app/Contents/Python/paraview/smtrace.py", > line 553, in get_value > > data = [str(Trace.get_accessor(x)) for x in self.get_object()[:]] > > File "/Applications/paraview.app/Contents/Python/paraview/smtrace.py", > line 167, in get_accessor > > "it. Skipping this action." % repr(obj)) > > paraview.smtrace.Untraceable: > " is > not 'known' at this point. Hence, we cannot trace it. Skipping this > action." > > Empty state generated. > > Generic Warning: In > > /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/ParaViewCore/ServerManager/Core/vtkSMTrace.cxx, > line 112 > > Tracing is active. Cannot save state. > > > > Empty state generated. > > ERROR: In > /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, > line 810 > > vtkPVCompositeDataPipeline (0x7ff19b7f6dc0): Input for connection > index 0 on input port index 1 for algorithm > vtkPVExtractArraysOverTime(0x7ff198f30380) is of type > vtkUnstructuredGrid, but a vtkSelection is required. > > > > ERROR: In > /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, > line 810 > > vtkPVCompositeDataPipeline (0x7ff19b7f6dc0): Input for connection > index 0 on input port index 1 for algorithm > vtkPVExtractArraysOverTime(0x7ff198f30380) is of type > vtkUnstructuredGrid, but a vtkSelection is required. > > > > Generic Warning: In > > /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx, > line 641 > > Call not supported for the current property type. > > > > ERROR: In > /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, > line 810 > > vtkPVCompositeDataPipeline (0x7ff19b7f6dc0): Input for connection > index 0 on input port index 1 for algorithm > vtkPVExtractArraysOverTime(0x7ff198f30380) is of type > vtkUnstructuredGrid, but a vtkSelection is required. > > > > ERROR: In > /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, > line 810 > > vtkPVCompositeDataPipeline (0x7ff1963cedc0): Input for connection > index 0 on input port index 1 for algorithm > vtkPVExtractArraysOverTime(0x7ff198b8e7e0) is of type > vtkUnstructuredGrid, but a vtkSelection is required. > > > > ERROR: In > /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, > line 810 > > vtkPVCompositeDataPipeline (0x7ff1963cedc0): Input for connection > index 0 on input port index 1 for algorithm > vtkPVExtractArraysOverTime(0x7ff198b8e7e0) is of type > vtkUnstructuredGrid, but a vtkSelection is required. > > > > Generic Warning: In > > /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx, > line 641 > > Call not supported for the current property type. > > > > On Thu, Mar 26, 2015 at 3:49 PM, Andy Bauer > wrote: > > Hi Paul, > > > > This should get tracked in the Python Trace functionality. I'll add a bug > > report for this. For now you can do it manually with something like: > >>>> w = Wavelet() > > > >>>> selection = SelectCells(query="id==0") > > > >>>> ec = ExtractSelection(Selection=selection) > > > >>>> ec.UpdatePipeline() > > > > > > This should select the first cell of the Wavelet source and extract it. > For > > point selection replace SelectCells with SelectPoints. There's probably > more > > complex selections for multiblock data sets but talking to you I thought > you > > had an unstructured data set. For the query string, you can see how more > > complex queries are created in the Find Data option under the Edit menu. > > > > > > Let me know if this doesn't work for you. > > > > > > Cheers, > > > > Andy > > > > > > > > On Thu, Mar 26, 2015 at 3:28 PM, Paul DesJardin > wrote: > >> > >> Hi, > >> > >> I'm trying to use the PlotSelectionOverTime command in a python script > >> for use with pvbatch. When using PlotSelectionOverTime in the GUI, > >> there is a "Copy Active Selection" operation required which I cannot > >> replicate in the python script. The incremental trace option doesn't > >> appear to provide information since nothing is reported when the the > >> "Copy Active Selection" button is pushed. > >> > >> Any help would be much appreciated..... > >> > >> Thanks! > >> > >> 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 > > > > > > -- > ========================================= > Paul DesJardin, Ph.D. > Professor > University at Buffalo, State University of New York > Buffalo, NY 14260-4400 > Tel: 716-645-1467 > email: ped3 at buffalo.edu > web: cet.eng.buffalo.edu > ========================================= > -------------- next part -------------- An HTML attachment was scrubbed... URL: From patrick.brockmann at lsce.ipsl.fr Thu Mar 26 17:14:59 2015 From: patrick.brockmann at lsce.ipsl.fr (Patrick Brockmann) Date: Thu, 26 Mar 2015 22:14:59 +0100 Subject: [Paraview] modify data (cell data) from Spreadsheet View Message-ID: <711-55147700-77-2b866bc0@242178987> Hi all, Is it possible to modify cell data from the Spreadsheet View ? My purpose is to modify a bathymetry field stored as a vtkStructuredGrid that has been read with the vtkNetCDFCFReader reader. The Spreadsheet View presents nicely selected cells but only in my understanding in a read mode. Am I missing something ? Regards Patrick -- LSCE/IPSL, Laboratoire CEA-CNRS-UVSQ Data Analysis and Visualization Engineer ICMC - IPSL Climate Modelling Centre -- From berk.geveci at kitware.com Thu Mar 26 20:45:52 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Thu, 26 Mar 2015 20:45:52 -0400 Subject: [Paraview] Get point array data in paraview from python shell In-Reply-To: References: Message-ID: Hi Jay, The Python console is not the right way to go. Use the Python Calculator with an expression like: mag() Best, -berk On Thu, Mar 26, 2015 at 4:28 PM, Jay Romero wrote: > I am trying to get point array data ( node and its values) of a variable > in paraview: so far I can use following (python shell): > > from paraview.simple import * > out = GetActiveSource() > > The point array data is a velocity vector on each node, and I can > calculate magnitude of a vector, next I want to treat these magnitude > values as new point array data in the pipeline browser. > How to do in python shell? > > Best Regards > > Jay > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 furutaka.kazuyoshi at jaea.go.jp Thu Mar 26 22:35:21 2015 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Fri, 27 Mar 2015 11:35:21 +0900 (JST) Subject: [Paraview] how not to scale the thickness of the Arrow Glyph? In-Reply-To: <20150326.143641.444834243.furutaka.kazuyoshi@jaea.go.jp> References: <20150326.094756.207947649.furutaka.kazuyoshi@jaea.go.jp> <305BB950-5456-49EA-B486-54282BB1503E@kitware.com> <20150326.143641.444834243.furutaka.kazuyoshi@jaea.go.jp> Message-ID: <20150327.113521.171448685.furutaka.kazuyoshi@jaea.go.jp> Dear all, Well... I'm still attached to the original idea, and after some googling I found the following article and mantis entry... https://paraview.uservoice.com/forums/11350-general/suggestions/450560-glyphs-scale-only-the-arrow-length-instead-of-the http://www.vtk.org/Bug/view.php?id=13660 So I've loaded the ArrowGlyph plugin onto my ParaView 4.3.1 32-bit (on linux (compiled by myself), and on windows vista (a binary downloaded from the paraview site)) and applied it to my data. But even though I can see glyphs and can change e.g. radius of shafts, I can NOT choose any "Scaling Array"; the pull-down menus do NOT respond to clicking... Any clue to this? Thanks in advance, Kazuyoshi From: Kazuyoshi Furutaka Subject: Re: [Paraview] how not to scale the thickness of the Arrow Glyph? Date: Thu, 26 Mar 2015 14:36:41 +0900 (JST) > Dear David, > > Thanks for your response. I'll give it a try. > > Kazuyoshi > > From: David Thompson > Subject: Re: [Paraview] how not to scale the thickness of the Arrow Glyph? > Date: Wed, 25 Mar 2015 23:01:51 -0400 > >> Hi Kazuyoshi, >> >> I do not think the glyph filter will do what you want it to. You might use a Python programmable filter[1] to turn each point into a line segment (i.e., a line from (x,y,z) to (x+dx, y+dy, z+dz)). Then run "Cell Centers" on the resulting line segment data and add oriented, unscaled cone glyphs at each cell center to indicate the direction along the line segments. That would draw lines along the path plus cones pointing along the direction of the path. >> >> David >> >> [1]: http://www.paraview.org/Wiki/Python_Programmable_Filter >> >> >>> On Mar 25, 2015, at 8:47 PM, Kazuyoshi Furutaka wrote: >>> >>> Dear ParaView experts, >>> >>> I'm visualizing paths of neutrons in some media. >>> Now I prepared the data as point data with displacement >>> vector to the next point attached to each point, and >>> visualize them using the Glyph filter with the following >>> setting: >>> Glyph Type: Arrow >>> Orientation: Orient >>> Scale Mode "vector" >>> Scale Factor = 1.0 >>> Glyph Mode: All Points >>> >>> The problem is that some arrows are too thick... >>> >>> So here are my questions. >>> >>> (1)How can I make the thickness of the arrows not >>> to scale (only the lengths do)? >>> >>> (2)It may be better to use "2D Glyph" instead of >>> "Arrow", but the 2D Glyph is centered at a >>> data point, instead of starting from the point... >>> How can I make the 2D Glyphs start from the data >>> points? >>> >>> (3)Do you have any recommendation on how to visualize >>> such a particle paths? >>> >>> Thanks in advance, >>> >>> Kazuyoshi >>> -- >>> Kazuyoshi Furutaka >>> furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>> >>> 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 furutaka.kazuyoshi at jaea.go.jp Fri Mar 27 03:54:40 2015 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Fri, 27 Mar 2015 16:54:40 +0900 (JST) Subject: [Paraview] may be a typo? (CMake/smxml_to_xml.xsl) Message-ID: <20150327.165440.64549290.furutaka.kazuyoshi@jaea.go.jp> diff --git a/CMake/smxml_to_xml.xsl b/CMake/smxml_to_xml.xsl index 4b00e2a..fa4c77e 100644 --- a/CMake/smxml_to_xml.xsl +++ b/CMake/smxml_to_xml.xsl @@ -124,7 +124,7 @@ - The dataset much contain a field array () + The dataset must contain a field array () with component(s). -- Kazuyoshi Furutaka furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp From henry.lehmann at informatik.tu-freiberg.de Fri Mar 27 06:29:02 2015 From: henry.lehmann at informatik.tu-freiberg.de (Henry Lehmann) Date: Fri, 27 Mar 2015 11:29:02 +0100 Subject: [Paraview] Fwd: Temporal Animation Start/Stop Callback In-Reply-To: <55152EE8.8000101@informatik.tu-freiberg.de> References: <55152EE8.8000101@informatik.tu-freiberg.de> Message-ID: <551530EE.2050708@informatik.tu-freiberg.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello, i am developing a Filter similar to the PCL Plugin. The PCL Plugin Filter uses a Thread in the background to fetch Data from a Device. The Gui of the Filter checks for new Data using SMProxy. When the new Data is there Modify() is called through SMProxy on the filter and the Gui calls Render(). The nice Thing is, that the Pipeline does something in real time. So far i could reproduce this setup. The Gui uses a Timer and frequently calls a Method through a SMProxy. However i want two different behaviors: 1. when Animation is Running (Play button was clicked) and 2. when the Animation is stoped (Pause button was clicked). This requires that the current state of the play/Pause-Button, or something similar, can be accessed. My questions are: 1. Is it possible to get the Information about the Animation (Play/Pause)? 2. How can the Information be accessed? (e.g. In Filter through InformationKeys/Vectors, or in the FilterGui) 3. Is there a starting point for me to find it out in the source code? Thanks in Advance, Henry - -- Henry Lehmann, M.Sc. Technische Universit?t Bergakademie Freiberg Fakult?t f?r Mathematik und Informatik Institut f?r Informatik -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVFTDjAAoJEM0zIsxevdB2qmwH/1xYIh5iAs2UBUR6UAx5/kR4 +G6pamq0aOh8vrRPDyH/5hLCEzgus0KiG519mIJFmsH1n1xWdwA5nNn+FjRDCqPf JtcvlcoO6FrF7UvsZBf1H6V3Z7PeQONndy0e5F9ntwScfZCp7dNAw0eZhyh8Ptwv /xW1yKHWCzqj/nBuzL+oFnWXB6iVXueDkqz2WZueXGzi/0QkLzXZ+AriF+0lDnbz jChOWBJzY9+kjvmAQ6ysXrTrcHu/YP+6lmbtVkv5/+8GrmbZzbmIQAuTzZDeXqEL ifBmPXId4w9DfrP6D0gej9qnh0ht0veOV0yCzitvsMafj+aYgdgqa5Z9A1bPjmE= =XmZf -----END PGP SIGNATURE----- From berk.geveci at kitware.com Fri Mar 27 09:36:37 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Fri, 27 Mar 2015 09:36:37 -0400 Subject: [Paraview] Get point array data in paraview from python shell In-Reply-To: References: Message-ID: Yes. You can use temporal statistics. Please direct questions to the mailing list so everyone can benefit from the answers. Best, -berk On Thu, Mar 26, 2015 at 10:28 PM, Jay Romero wrote: > Hi Berk > > Thanks for reply. I can try python calculator. > Actually, I am trying to calculate the time average of a vector variable ( > for example: velocity vector) as: > > (1/k) Sum ( I V_k | dt_k ) > > where V_k : velocity vector > dt_k: time step > k: time step number > > I am wondering how I can achieve it. Is it possible to do in Python > calculator. Any help would be great. > > Best Regards > > Jay > > On Thu, Mar 26, 2015 at 7:45 PM, Berk Geveci > wrote: > >> Hi Jay, >> >> The Python console is not the right way to go. Use the Python Calculator >> with an expression like: >> >> mag() >> >> Best, >> -berk >> >> On Thu, Mar 26, 2015 at 4:28 PM, Jay Romero wrote: >> >>> I am trying to get point array data ( node and its values) of a variable >>> in paraview: so far I can use following (python shell): >>> >>> from paraview.simple import * >>> out = GetActiveSource() >>> >>> The point array data is a velocity vector on each node, and I can >>> calculate magnitude of a vector, next I want to treat these magnitude >>> values as new point array data in the pipeline browser. >>> How to do in python shell? >>> >>> Best Regards >>> >>> Jay >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> 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 jayreno33 at gmail.com Fri Mar 27 11:25:55 2015 From: jayreno33 at gmail.com (Jay Romero) Date: Fri, 27 Mar 2015 10:25:55 -0500 Subject: [Paraview] Sum of a vector variable over time in paraview Message-ID: Hi I want achieve this simple step in paraview: I am trying to calculate the temporal sum of a vector variable ( for example: velocity vector) as: Sum ( I V_k | dt_k ) where | V_k | : magnitude of velocity vector dt_k: time step k: time step number I am wondering how to achieve it in paraview. Is it possible to do in Python calculator or Python Shell. Best Regards Jay -------------- next part -------------- An HTML attachment was scrubbed... URL: From kit.chambers.kc at gmail.com Fri Mar 27 12:36:19 2015 From: kit.chambers.kc at gmail.com (Kit Chambers) Date: Fri, 27 Mar 2015 16:36:19 +0000 Subject: [Paraview] dlopen: cannot load anymore object with static TLS Message-ID: Hi All, I have a ParaView plugin which in turn links against a couple of other shared libraries, these in turn use OpenMP for threading. After a recent re-build I get the following error when the plugin is loaded. dlopen: cannot load anymore object with static TLS However, if I compile the supporting libraries without OpenMP it works fine. Has anyone else come across this? My system is: Ubuntu 14.04 - (64bit) kernel = 3.13.0-46-generic ParaView Version = 4.2 Cheers Kit -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Fri Mar 27 12:54:07 2015 From: bloring at lbl.gov (Burlen Loring) Date: Fri, 27 Mar 2015 09:54:07 -0700 Subject: [Paraview] dlopen: cannot load anymore object with static TLS In-Reply-To: References: Message-ID: <55158B2F.2010107@lbl.gov> I don't know the answer but you might try adding -fPIC -ftls-model=global-dynamic to CMAKE_CXX_FLAGS and CMAKE_C_FLAGS vars when build PV and your plugin. On 03/27/2015 09:36 AM, Kit Chambers wrote: > Hi All, > > I have a ParaView plugin which in turn links against a couple of other > shared libraries, these in turn use OpenMP for threading. After a > recent re-build I get the following error when the plugin is loaded. > > dlopen: cannot load anymore object with static TLS > > However, if I compile the supporting libraries without OpenMP it works > fine. > > Has anyone else come across this? > > My system is: > Ubuntu 14.04 - (64bit) > kernel = 3.13.0-46-generic > ParaView Version = 4.2 > > > Cheers > > Kit > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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 ped3 at buffalo.edu Fri Mar 27 18:24:22 2015 From: ped3 at buffalo.edu (Paul DesJardin) Date: Fri, 27 Mar 2015 18:24:22 -0400 Subject: [Paraview] saving table data Message-ID: Hi, I'm trying to save a subset of data generated from the PlotSelectionOverTime filter. I tried using the PassArrays filter to narrow my selection but the data doesn't appear under Point, Cell or Field data options for that filter. The data in the PlotSelectionOverTime is labeled as "Cell Statistics" and was created using the following lines from a Python script... selection = SelectCells(query="id==0") PSOT = PlotSelectionOverTime(Selection=selection) PSOT.UpdatePipeline() Any help would be much appreciated.... Thanks, Paul -- ========================================= Paul DesJardin, Ph.D. Professor University at Buffalo, State University of New York Buffalo, NY 14260-4400 Tel: 716-645-1467 email: ped3 at buffalo.edu web: cet.eng.buffalo.edu ========================================= From andy.bauer at kitware.com Sat Mar 28 09:04:37 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Sat, 28 Mar 2015 09:04:37 -0400 Subject: [Paraview] saving table data In-Reply-To: References: Message-ID: Hi Paul, >From what I can tell from playing around with the PlotSelectionOverTime filter, it doesn't create any extra arrays so I think it may work by using the PassArrays filter right before the PlotSelectionOverTime filter. If that doesn't get your desired behavior then maybe you want to try the Programmable Filter. Information on that is available at http://www.paraview.org/Wiki/Python_Programmable_Filter. Regards, Andy On Fri, Mar 27, 2015 at 6:24 PM, Paul DesJardin wrote: > Hi, > > I'm trying to save a subset of data generated from the > PlotSelectionOverTime filter. I tried using the PassArrays filter to > narrow my selection but the data doesn't appear under Point, Cell or > Field data options for that filter. The data in the > PlotSelectionOverTime is labeled as "Cell Statistics" and was created > using the following lines from a Python script... > > selection = SelectCells(query="id==0") > PSOT = PlotSelectionOverTime(Selection=selection) > PSOT.UpdatePipeline() > > Any help would be much appreciated.... > > Thanks, > > Paul > > -- > ========================================= > Paul DesJardin, Ph.D. > Professor > University at Buffalo, State University of New York > Buffalo, NY 14260-4400 > Tel: 716-645-1467 > email: ped3 at buffalo.edu > web: cet.eng.buffalo.edu > ========================================= > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ped3 at buffalo.edu Sat Mar 28 09:30:06 2015 From: ped3 at buffalo.edu (Paul DesJardin) Date: Sat, 28 Mar 2015 09:30:06 -0400 Subject: [Paraview] saving table data In-Reply-To: References: Message-ID: Hi Andy, Thanks for the prompt response. The generation of extra arrays arises after the call to the PlotSelectionOverTime filter, so filtering before that call will not have the desired reduction. For whatever reason, there is a difference between the output of the PlotSelectionOverTime filter using the GUI vs. calling it in the python script using the SelectCells filter (below). When you run it through the GUI, I get the original variables as a function of time (as expected). When I run through the python script, I get the avg, std, q1, q2, q3, q4, .... (bunch of other statistics) for every variable. This is what I'm trying to eliminate - clearly there is a difference between what GUI selection approach and using SelectCells in the python script. Is there detailed documentation on valid arguments for SelectCells? For instance, I haven't a clue exactly what query="id==0" means. Are there other arguments to shut of statistics? I can only find very tutorial type of information on the wiki and in the KitWare published texts (VTk and paraview). I poked around on the doxygen site and didn't find too much information there either. Is the source code viewable for the SelectCells filter so I can see what exactly it is doing? It looks like the programmable filter provides a mechanism to run python code. Wouldn't this be the same thing as running python code via pvbatch? I don't see how using the programmable filter would provide an alternative solution approach. I must be missing something.... Thanks, Paul On Sat, Mar 28, 2015 at 9:04 AM, Andy Bauer wrote: > Hi Paul, > > From what I can tell from playing around with the PlotSelectionOverTime > filter, it doesn't create any extra arrays so I think it may work by using > the PassArrays filter right before the PlotSelectionOverTime filter. If that > doesn't get your desired behavior then maybe you want to try the > Programmable Filter. Information on that is available at > http://www.paraview.org/Wiki/Python_Programmable_Filter. > > Regards, > Andy > > On Fri, Mar 27, 2015 at 6:24 PM, Paul DesJardin wrote: >> >> Hi, >> >> I'm trying to save a subset of data generated from the >> PlotSelectionOverTime filter. I tried using the PassArrays filter to >> narrow my selection but the data doesn't appear under Point, Cell or >> Field data options for that filter. The data in the >> PlotSelectionOverTime is labeled as "Cell Statistics" and was created >> using the following lines from a Python script... >> >> selection = SelectCells(query="id==0") >> PSOT = PlotSelectionOverTime(Selection=selection) >> PSOT.UpdatePipeline() >> >> Any help would be much appreciated.... >> >> Thanks, >> >> Paul >> >> -- >> ========================================= >> Paul DesJardin, Ph.D. >> Professor >> University at Buffalo, State University of New York >> Buffalo, NY 14260-4400 >> Tel: 716-645-1467 >> email: ped3 at buffalo.edu >> web: cet.eng.buffalo.edu >> ========================================= > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- ========================================= Paul DesJardin, Ph.D. Professor University at Buffalo, State University of New York Buffalo, NY 14260-4400 Tel: 716-645-1467 email: ped3 at buffalo.edu web: cet.eng.buffalo.edu ========================================= From livia.barazzetti at istb.unibe.ch Sun Mar 29 10:49:24 2015 From: livia.barazzetti at istb.unibe.ch (livia.barazzetti at istb.unibe.ch) Date: Sun, 29 Mar 2015 14:49:24 +0000 Subject: [Paraview] Paraview support of FieldData in a vtkTable In-Reply-To: References: Message-ID: Thanks Cory, I?ve opened the feature in http://www.paraview.org/Bug/view.php?id=15403 Regards Livia From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: gioved?, 26. marzo 2015 04:36 To: Barazzetti, Livia (ISTB) Cc: ParaView Subject: Re: [Paraview] Paraview support of FieldData in a vtkTable Livia, It seems reasonable that you should be able to save field data stored in a vtkTable. Would you mind writing up a feature request at http://www.paraview.org/Bug/view_all_bug_page.php? Thanks, Cory On Wed, Mar 25, 2015 at 9:47 AM, > wrote: Hi, I was using the writer from the gui in Paraview. I created a very simple programmable source (with output type vtkTable) with a column and a field data array, then clicked File-Save Data from the menu. In the case of a table, the writer window doesn?t allow to specify the association field, so only the row values are exported to the csv file. By the way, I see that if I apply a TableToPoints filter, the field array is copied to the polydata correctly (and can be exported from there), but I haven?t experimented with this solution further yet Thanks Livia From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: 24 March 2015 23:32 To: Barazzetti, Livia (ISTB) Cc: ParaView Subject: Re: [Paraview] Paraview support of FieldData in a vtkTable Livia, Which writer are you using that doesn't save the field data? Thanks, Cory On Sun, Mar 15, 2015 at 5:30 AM, > wrote: Hello, I am thinking to store some info as FieldData of a table (for example, the parameters used for the calculation of the data in the table - possibly they could also be changing depending on other elements of the pipeline). I tried a toy example in Python and it seems that vtkTable supports it (I am able to add an array and read it back). In Paraview 4.3.1, visualizing the field data from a python annotation works, but if I open the spreadsheet view to see the field data I get Warning: In C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\VTKExtensions\Rendering\vtkMarkSelectedRows.cxx, line 209 vtkMarkSelectedRows (0000000010381890): FieldAssociation type not supported yet. Selected elements may not be shown correctly. , also the writer doen't export the field data. Should I go forward in using the FieldData of a table (just remembering that before exporting I should use a Python annotation or a programmable filter to read the field data) or it is actually not supported by paraview and I should avoid it? (for example, the field data would not be updated as the rest of the pipeline, or something like that)? Thank you Best regards Livia Barazzetti _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- Cory Quammen R&D Engineer Kitware, Inc. -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From furutaka.kazuyoshi at jaea.go.jp Sun Mar 29 18:35:12 2015 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Mon, 30 Mar 2015 07:35:12 +0900 (JST) Subject: [Paraview] how not to scale the thickness of the Arrow Glyph? In-Reply-To: <20150327.113521.171448685.furutaka.kazuyoshi@jaea.go.jp> References: <305BB950-5456-49EA-B486-54282BB1503E@kitware.com> <20150326.143641.444834243.furutaka.kazuyoshi@jaea.go.jp> <20150327.113521.171448685.furutaka.kazuyoshi@jaea.go.jp> Message-ID: <20150330.073512.124652398.furutaka.kazuyoshi@jaea.go.jp> Dear experts... Is the ArrowGlyph plugin working on your ParaView? Kazuyoshi From: Kazuyoshi Furutaka Subject: Re: [Paraview] how not to scale the thickness of the Arrow Glyph? Date: Fri, 27 Mar 2015 11:35:21 +0900 (JST) > Dear all, > > Well... I'm still attached to the original idea, and > after some googling I found the following article and > mantis entry... > https://paraview.uservoice.com/forums/11350-general/suggestions/450560-glyphs-scale-only-the-arrow-length-instead-of-the > http://www.vtk.org/Bug/view.php?id=13660 > > So I've loaded the ArrowGlyph plugin onto my ParaView 4.3.1 > 32-bit (on linux (compiled by myself), and on windows vista > (a binary downloaded from the paraview site)) and applied it > to my data. > But even though I can see glyphs and can change e.g. radius > of shafts, I can NOT choose any "Scaling Array"; the pull-down > menus do NOT respond to clicking... > > Any clue to this? > > Thanks in advance, > Kazuyoshi > > > From: Kazuyoshi Furutaka > Subject: Re: [Paraview] how not to scale the thickness of the Arrow Glyph? > Date: Thu, 26 Mar 2015 14:36:41 +0900 (JST) > >> Dear David, >> >> Thanks for your response. I'll give it a try. >> >> Kazuyoshi >> >> From: David Thompson >> Subject: Re: [Paraview] how not to scale the thickness of the Arrow Glyph? >> Date: Wed, 25 Mar 2015 23:01:51 -0400 >> >>> Hi Kazuyoshi, >>> >>> I do not think the glyph filter will do what you want it to. You might use a Python programmable filter[1] to turn each point into a line segment (i.e., a line from (x,y,z) to (x+dx, y+dy, z+dz)). Then run "Cell Centers" on the resulting line segment data and add oriented, unscaled cone glyphs at each cell center to indicate the direction along the line segments. That would draw lines along the path plus cones pointing along the direction of the path. >>> >>> David >>> >>> [1]: http://www.paraview.org/Wiki/Python_Programmable_Filter >>> >>> >>>> On Mar 25, 2015, at 8:47 PM, Kazuyoshi Furutaka wrote: >>>> >>>> Dear ParaView experts, >>>> >>>> I'm visualizing paths of neutrons in some media. >>>> Now I prepared the data as point data with displacement >>>> vector to the next point attached to each point, and >>>> visualize them using the Glyph filter with the following >>>> setting: >>>> Glyph Type: Arrow >>>> Orientation: Orient >>>> Scale Mode "vector" >>>> Scale Factor = 1.0 >>>> Glyph Mode: All Points >>>> >>>> The problem is that some arrows are too thick... >>>> >>>> So here are my questions. >>>> >>>> (1)How can I make the thickness of the arrows not >>>> to scale (only the lengths do)? >>>> >>>> (2)It may be better to use "2D Glyph" instead of >>>> "Arrow", but the 2D Glyph is centered at a >>>> data point, instead of starting from the point... >>>> How can I make the 2D Glyphs start from the data >>>> points? >>>> >>>> (3)Do you have any recommendation on how to visualize >>>> such a particle paths? >>>> >>>> Thanks in advance, >>>> >>>> Kazuyoshi >>>> -- >>>> Kazuyoshi Furutaka >>>> furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>> >>>> 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 raphael.muenster at math.uni-dortmund.de Mon Mar 30 07:18:22 2015 From: raphael.muenster at math.uni-dortmund.de (=?UTF-8?B?UmFwaGFlbCBNw7xuc3Rlcg==?=) Date: Mon, 30 Mar 2015 13:18:22 +0200 Subject: [Paraview] How to use the Find Data function with a client/server connection? Message-ID: <551930FE.9030607@math.uni-dortmund.de> Dear ParaView mailing list members, I am trying to use the 'Find Data' function with a remote connection to a pvserver. I started the server with 'pvserver --use-offscreen-rendering' and then used my local ParaView client to connect to the server. When I try to use the 'Find Data' option no matter what kind of query I enter it does nothing. When I download the data set from the server to my local machine and then run the exact same query the 'Find Data' function works correctly and returns a selection. Is there a way to use the 'Find Data' function without having to copy the data from the server to the client, as this may not be a feasible option for all data sets. I am using Paraview 4.2.0 64bit. Best regards, Raphael From utkarsh.ayachit at kitware.com Mon Mar 30 10:03:42 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 30 Mar 2015 10:03:42 -0400 Subject: [Paraview] How to use the Find Data function with a client/server connection? In-Reply-To: <551930FE.9030607@math.uni-dortmund.de> References: <551930FE.9030607@math.uni-dortmund.de> Message-ID: Raphael, Find Data requires that Python with a working NumPy is available on the server side. Is that not the case by any chance? To test, just create a Python "Programmable Source" and in the Script, use something like: import numpy print numpy Utkarsh On Mon, Mar 30, 2015 at 7:18 AM, Raphael M?nster wrote: > Dear ParaView mailing list members, > > I am trying to use the 'Find Data' function with a remote connection to a > pvserver. I started the server with 'pvserver --use-offscreen-rendering' and > then > used my local ParaView client to connect to the server. When I try to use > the 'Find Data' option no matter what kind of query I enter it does nothing. > When > I download the data set from the server to my local machine and then run the > exact same query the 'Find Data' function works correctly and returns a > selection. > > Is there a way to use the 'Find Data' function without having to copy the > data from the server to the client, as this may not be a feasible option for > all data sets. I am using Paraview 4.2.0 64bit. > > Best regards, > Raphael > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 Patrick.Brockmann at lsce.ipsl.fr Mon Mar 30 10:36:01 2015 From: Patrick.Brockmann at lsce.ipsl.fr (Patrick Brockmann) Date: Mon, 30 Mar 2015 16:36:01 +0200 Subject: [Paraview] Double property slider with integer rather than float Message-ID: <55195F51.2080909@lsce.ipsl.fr> Hi, Is it possible to configure a"Double property slider" to display integer rather than float from Paraview XML GUI Parameters ? Patrick -- LSCE/IPSL, Laboratoire CEA-CNRS-UVSQ Data Analysis and Visualization Engineer ICMC - IPSL Climate Modelling Centre -- From anton.piccardo-selg at stfc.ac.uk Mon Mar 30 11:05:37 2015 From: anton.piccardo-selg at stfc.ac.uk (anton.piccardo-selg at stfc.ac.uk) Date: Mon, 30 Mar 2015 15:05:37 +0000 Subject: [Paraview] Setting glyph color to be independent of color scale and color map In-Reply-To: References: Message-ID: <593AFCE559F11049B8F268BE84170A0DC2E287@EXCHMBX03.fed.cclrc.ac.uk> Hi Ken, I am running into an issue with your suggestion. I update the "DiffuseColor" property to my desired value using the method that you pointed out. I then apply the UpdateVTKObjects() method, yet I don't see that the glyph color changes. When I look into the state XML files, I can see that the value was changed. What else would I need to call an update on? My code is similar to: ... pqDataRepresentation *rep = source->getRepresentation(pqActiveObjects::instance().activeView()); pqPipelineRepresentation *pipelineRepresentation = qobject_cast(rep); pipelineRepresentation->getProxy()->UpdatePropertyInformation(); vtkSMDoubleVectorProperty *prop = vtkSMDoubleVectorProperty::SafeDownCast( pipelineRepresentation->getProxy()->GetProperty( "DiffuseColor")); prop->SetElement(0, 1.0); prop->SetElement(1, 1.0); prop->SetElement(2, 0.0); pipelineRepresentation->getProxy()->UpdateVTKObjects(); pqActiveObjects::instance().activeView()->forceRender(); ... I can see that the color that I have set is set as active color in the ColorWindow of the properties panel, but the image doesn't render the color. By the way, I am developing against ParaView 3.98.1. Many thanks and best regards, Anton ________________________________________ From: Moreland, Kenneth [kmorel at sandia.gov] Sent: 12 March 2015 16:32 To: Piccardo-Selg, Anton (-,RAL,ISIS); paraview at paraview.org Subject: Re: [Paraview] Setting glyph color to be independent of color scale and color map The coloring of an object (in this case, the result of the glyph filter) is controlled by the representation object. The representation object can be set to be either a solid color or mapping a variable. It sounds like your glyph representation is already set to a solid color since the default solid color is white. There are several parameters on the representation object that control the solid color. The most relevant is the DiffuseColor parameter. Change that to be yellow (i.e. [1,1,0]) and that should do what you want. -Ken On 3/12/15, 10:10 AM, "anton.piccardo-selg at stfc.ac.uk" wrote: >Hi, > >We are building a customization of ParaView 3.98.1. Data sets are loaded >with a signal range which is then used to set the scalar range for the >color scale. Besides the data we plot some simple glyphs to indicate >special points in our rendered data set. > >Currently they are all rendered white, as the glyphs don't have a scalar >value attached to them ( I guess it is the NAN color). I was wondering >if there is a way to set the color of these glyphs to a fixed value, >independent of the color scale or the selected color map. In our case we >would always want to render an ellipsoidal glyph with a yellow color. Is >this possible? > >Many thanks and best regards, > >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 wascott at sandia.gov Mon Mar 30 15:21:33 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 30 Mar 2015 19:21:33 +0000 Subject: [Paraview] [EXTERNAL] Re: How to use the Find Data function with a client/server connection? In-Reply-To: References: <551930FE.9030607@math.uni-dortmund.de> Message-ID: <50827d304a22492798737379e2b3601d@ES05AMSNLNT.srn.sandia.gov> Another way to find out if you have python and numpy on the server side is to run ParaView, and connect to your remote server. Then, Help/ About/ Connection Information. This will show you where Numpy and Python are, whether you even have Numpy, and finally versions of both. If you don't have Numpy, as Utkarsh says, that's the problem. As a side issue, you may want to update to PV 4.3.1. There were a lot of bugs that were squashed in the new version. Alan -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Utkarsh Ayachit Sent: Monday, March 30, 2015 8:04 AM To: Raphael M?nster Cc: paraview at paraview.org Subject: [EXTERNAL] Re: [Paraview] How to use the Find Data function with a client/server connection? Raphael, Find Data requires that Python with a working NumPy is available on the server side. Is that not the case by any chance? To test, just create a Python "Programmable Source" and in the Script, use something like: import numpy print numpy Utkarsh On Mon, Mar 30, 2015 at 7:18 AM, Raphael M?nster wrote: > Dear ParaView mailing list members, > > I am trying to use the 'Find Data' function with a remote connection > to a pvserver. I started the server with 'pvserver > --use-offscreen-rendering' and then used my local ParaView client to > connect to the server. When I try to use the 'Find Data' option no > matter what kind of query I enter it does nothing. > When > I download the data set from the server to my local machine and then > run the exact same query the 'Find Data' function works correctly and > returns a selection. > > Is there a way to use the 'Find Data' function without having to copy > the data from the server to the client, as this may not be a feasible > option for all data sets. I am using Paraview 4.2.0 64bit. > > Best regards, > Raphael > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 andy.bauer at kitware.com Tue Mar 31 09:18:22 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 31 Mar 2015 09:18:22 -0400 Subject: [Paraview] saving table data In-Reply-To: References: Message-ID: Hi Paul, The Plot Selection Over Time filter has an "OnlyReportSelectionStatistics" property. You should set that to 0 to have it not compute the extra statistics. As for SelectCells, I figured that out by creating a query in the Find Data tool (under the Edit menu for Linux machines) and then creating a Plot Selection Over Time filter. In the Copied Selection widget in the Properties tab it should list the corresponding query string. There's also some information at http://www.paraview.org/Wiki/Find_Data_using_Queries but that may be a bit out of date. Regards, Andy On Sat, Mar 28, 2015 at 9:30 AM, Paul DesJardin wrote: > Hi Andy, > > Thanks for the prompt response. The generation of extra arrays arises > after the call to the PlotSelectionOverTime filter, so filtering > before that call will not have the desired reduction. For whatever > reason, there is a difference between the output of the > PlotSelectionOverTime filter using the GUI vs. calling it in the > python script using the SelectCells filter (below). When you run it > through the GUI, I get the original variables as a function of time > (as expected). When I run through the python script, I get the avg, > std, q1, q2, q3, q4, .... (bunch of other statistics) for every > variable. This is what I'm trying to eliminate - clearly there is a > difference between what GUI selection approach and using SelectCells > in the python script. > > Is there detailed documentation on valid arguments for SelectCells? > For instance, I haven't a clue exactly what query="id==0" means. Are > there other arguments to shut of statistics? I can only find very > tutorial type of information on the wiki and in the KitWare published > texts (VTk and paraview). I poked around on the doxygen site and > didn't find too much information there either. Is the source code > viewable for the SelectCells filter so I can see what exactly it is > doing? > > It looks like the programmable filter provides a mechanism to run > python code. Wouldn't this be the same thing as running python code > via pvbatch? I don't see how using the programmable filter would > provide an alternative solution approach. I must be missing > something.... > > Thanks, > > Paul > > On Sat, Mar 28, 2015 at 9:04 AM, Andy Bauer > wrote: > > Hi Paul, > > > > From what I can tell from playing around with the PlotSelectionOverTime > > filter, it doesn't create any extra arrays so I think it may work by > using > > the PassArrays filter right before the PlotSelectionOverTime filter. If > that > > doesn't get your desired behavior then maybe you want to try the > > Programmable Filter. Information on that is available at > > http://www.paraview.org/Wiki/Python_Programmable_Filter. > > > > Regards, > > Andy > > > > On Fri, Mar 27, 2015 at 6:24 PM, Paul DesJardin > wrote: > >> > >> Hi, > >> > >> I'm trying to save a subset of data generated from the > >> PlotSelectionOverTime filter. I tried using the PassArrays filter to > >> narrow my selection but the data doesn't appear under Point, Cell or > >> Field data options for that filter. The data in the > >> PlotSelectionOverTime is labeled as "Cell Statistics" and was created > >> using the following lines from a Python script... > >> > >> selection = SelectCells(query="id==0") > >> PSOT = PlotSelectionOverTime(Selection=selection) > >> PSOT.UpdatePipeline() > >> > >> Any help would be much appreciated.... > >> > >> Thanks, > >> > >> Paul > >> > >> -- > >> ========================================= > >> Paul DesJardin, Ph.D. > >> Professor > >> University at Buffalo, State University of New York > >> Buffalo, NY 14260-4400 > >> Tel: 716-645-1467 > >> email: ped3 at buffalo.edu > >> web: cet.eng.buffalo.edu > >> ========================================= > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > > -- > ========================================= > Paul DesJardin, Ph.D. > Professor > University at Buffalo, State University of New York > Buffalo, NY 14260-4400 > Tel: 716-645-1467 > email: ped3 at buffalo.edu > web: cet.eng.buffalo.edu > ========================================= > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Mar 31 10:51:11 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 31 Mar 2015 10:51:11 -0400 Subject: [Paraview] How to get point array data in paraview In-Reply-To: References: Message-ID: How about using the calculator or Python calculator? pythonCalculator1 = PythonCalculator(Input=out) pythonCalculator1.Expression = 'mag(Normals)' UpdatePipeline(pythonCalculator1) On Thu, Mar 26, 2015 at 4:17 PM, Jay Romero wrote: > I am trying to get point array data ( node and its values) of a variable in > paraview: so far I can use following (python shell): > > from paraview.simple import * > out = GetActiveSource() > > The point array data is a velocity vector on each node, and I can calculate > magnitude of a vector, next I want to treat these magnitude values as new > point array data in the pipeline browser. > How to do in python shell? > > Best Regards > > Jay From jayreno33 at gmail.com Tue Mar 31 12:08:25 2015 From: jayreno33 at gmail.com (Jay Romero) Date: Tue, 31 Mar 2015 11:08:25 -0500 Subject: [Paraview] How to get point array data in paraview In-Reply-To: References: Message-ID: Thank you so much it works. Regards jay On Tue, Mar 31, 2015 at 9:51 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > How about using the calculator or Python calculator? > > pythonCalculator1 = PythonCalculator(Input=out) > pythonCalculator1.Expression = 'mag(Normals)' > UpdatePipeline(pythonCalculator1) > > On Thu, Mar 26, 2015 at 4:17 PM, Jay Romero wrote: > > I am trying to get point array data ( node and its values) of a variable > in > > paraview: so far I can use following (python shell): > > > > from paraview.simple import * > > out = GetActiveSource() > > > > The point array data is a velocity vector on each node, and I can > calculate > > magnitude of a vector, next I want to treat these magnitude values as new > > point array data in the pipeline browser. > > How to do in python shell? > > > > Best Regards > > > > Jay > -------------- next part -------------- An HTML attachment was scrubbed... URL: From akcay.cihan at gmail.com Tue Mar 31 13:01:53 2015 From: akcay.cihan at gmail.com (Cihan A) Date: Tue, 31 Mar 2015 11:01:53 -0600 Subject: [Paraview] running a python script with new PV variables created with the calculator Message-ID: Dear Paraviewers, I have very recently begun to use PV (been a VisItor up to this point) so there are a lot of features with which I am not entirely familiar. I am trying to run a python script which does some math then stream ? ? tracing on two vectors variables "e" and "b". My code dumps out components of each vector field ?? , which I read into PV ? where they appear as point data.. I t hen combine ? this data? into vectors "e" and "b" with PV's calculator feature. After this step I run my python script from Tools->Python Shell. The script (attached it as fieldl_line.py -- looks terrible when opened with Vim) does not get very far and complains about various things. I attached the log file entitled PVlog. I cannot decipher ?some of ? these messages but I have a strong suspicion the inputs variable does not get populated correctly or the script cannot find "e" and "b". Any ideas where I have gone wrong? Is there an intermediate step after defining new variables on the calculator to make the script aware of the existence of "e" and "b". I plotted these new vector variables on PV without any issue. Thank you very much for your time and interest. -- Cihan -- Cihan -- Cihan -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PVlog Type: application/octet-stream Size: 3158 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: field_lines.py Type: text/x-python Size: 6956 bytes Desc: not available URL: From jkneppe2 at uni-koeln.de Tue Mar 31 12:25:04 2015 From: jkneppe2 at uni-koeln.de (jkneppe2 at uni-koeln.de) Date: Tue, 31 Mar 2015 18:25:04 +0200 Subject: [Paraview] Resolution bug: screenshot of 'Line Chart View' and screenshot/animation with layouts Message-ID: <20150331182504.16695gcrq9b23ejk@webmail.uni-koeln.de> Dear ParaView users and developers, I encounter two issues with ParaView while exporting my results as screenshots or animations. I execute pvserver on a Linux server and remote connect to this with an instance of ParaView running on a Windows-7-x64 system. The version I use is 4.3.1-64bit, precompiled for Linux (server) and Windows. Issue 1) Whenever I use more than one layout and save an animation, ParaView doesn't properly place the 'views' in the video. Furthermore it stores the video in a wrong resolution. E.g.: I specified 1920x1080 as the resolution to use and it saved a 2328x1220 video. Note 1: This also happens when there is only one 'view' in the layout, so it seems to be a problem with using more than one layout. Note 2: This issue does not occur if I export a screenshot. Issue 2) Whenever I export a screenshot of a layout, that contains a 'Line Chart View', I can only use the predefined resolution (or a lower one). If I specify a larger resolution, white bars (forming a cross) are placed on the 'Line Chart View'. Those white bars do not cover the axes and labels but the plotted graph and the grid. The same happens when saving an animation. Note: I have only used one method for plotting. In case this is part of the problem, I will now describe this method: For each time step I have a 'Point Array' describing displacement vectors for an object. I used the 'Calculator' to compute the magnitude of the displacements. Next I used the 'Descriptive Statistics' filter to compute the minimum, mean and maximum. I selected the appropriate row in the 'Spread Sheet View' and used the 'Plot Selection over Time' filter. (This leads to an error message, since ParaView will try to plot unplottable information. One can deselect columns which can not be plotted after the filter has been applied. Then the error message won't reappear. However I don't know how to prevent this from happening in the first place.) Best regards, Jascha Knepper From utkarsh.ayachit at kitware.com Tue Mar 31 15:52:52 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 31 Mar 2015 15:52:52 -0400 Subject: [Paraview] Blog: Axes Grid Annotation in Render View Message-ID: Folks, Just posted a blog demonstrating a new axes annotation capability set to land in ParaView soon. Any suggestions/feedback is greatly appreciated, as always! http://www.kitware.com/blog/home/post/871 Thanks, Utkarsh