Yes Julianna Presley Recruiter Oak Ridge National Lab Computational Sciences
865.574-4429 office 865.591.4774 cell 865-241-6157 fax [email protected] Building 5600 C317 -----Original Message----- From: ParaView [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, May 07, 2014 9:35 AM To: [email protected] Subject: ParaView Digest, Vol 121, Issue 24 Send ParaView mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://www.paraview.org/mailman/listinfo/paraview or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of ParaView digest..." Today's Topics: 1. Re: Changes to color bar placement and visibility (M P) 2. Re: Changes to color bar placement and visibility (Utkarsh Ayachit) 3. Save Interpolated Results (Eggleston, Richard (2011)) 4. PV 4.1.0 binary download ; unstructured mesh. reading pieces fails (Stephen Wornom) 5. Re: PV 4.1.0 binary download ; unstructured mesh. reading pieces fails (Utkarsh Ayachit) 6. Re: PV 4.1.0 binary download ; unstructured mesh. reading pieces fails (Stephen Wornom) ---------------------------------------------------------------------- Message: 1 Date: Wed, 7 May 2014 07:46:38 +0200 From: M P <[email protected]> To: Utkarsh Ayachit <[email protected]> Cc: ParaView <[email protected]> Subject: Re: [Paraview] Changes to color bar placement and visibility Message-ID: <cakkv2wuphxg478eoy-xswwtwy6ve1kmja4n7qd5g8_a49vz...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi Utkarsh, regarding colormaps I would certainly love if for colormaps that include transparency there could be a checker texture displayed behind the transparent colormap. That would certainly improve the readability of the the colormap for volumerendering. Now the behavior is a little bit strange, the colormap turns transparent (but witout the opaque checker texture) when the "Enable Opacity Mapping for Surfaces" is turned on. But these two different things and should not be connected, what if need transparent colormap for volumerendering but still want opaque surfaces with this colormap? Thank you, Martin On Tue, May 6, 2014 at 2:54 PM, Utkarsh Ayachit <[email protected] > wrote: > Folks, > > Several new changes are hitting ParaView development repository soon, > slated to be included in the next ParaView release. We're writing a > series of blog posts that introduces several of these new features and > changes. > > Here's another post discussing changes to the color bar (or scalar > bar) visibility and placement. > http://www.kitware.com/blog/home/post/653 > > Let us know if you have any feedback. The code hasn't landed in > git/master yet and won't for a couple more weeks. > > Utkarsh > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects 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://www.paraview.org/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.paraview.org/pipermail/paraview/attachments/20140507/96f8fb37/attachment-0001.html> ------------------------------ Message: 2 Date: Wed, 7 May 2014 07:00:30 -0400 From: Utkarsh Ayachit <[email protected]> To: M P <[email protected]> Cc: ParaView <[email protected]> Subject: Re: [Paraview] Changes to color bar placement and visibility Message-ID: <cadhsjjcvqot0ruqh_foabonvyjodnbcqgwqu7mvpg1ucyts...@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 That sounds reasonable. Mind adding a feature request to http://paraview.org/Bug? Thanks On Wed, May 7, 2014 at 1:46 AM, M P <[email protected]> wrote: > Hi Utkarsh, > regarding colormaps I would certainly love if for colormaps that include > transparency there could be a checker texture displayed behind the > transparent colormap. That would certainly improve the readability of the > the colormap for volumerendering. > Now the behavior is a little bit strange, the colormap turns transparent > (but witout the opaque checker texture) when the "Enable Opacity Mapping for > Surfaces" is turned on. But these two different things and should not be > connected, what if need transparent colormap for volumerendering but still > want opaque surfaces with this colormap? > > Thank you, > > Martin > > > On Tue, May 6, 2014 at 2:54 PM, Utkarsh Ayachit > <[email protected]> wrote: >> >> Folks, >> >> Several new changes are hitting ParaView development repository soon, >> slated to be included in the next ParaView release. We're writing a >> series of blog posts that introduces several of these new features and >> changes. >> >> Here's another post discussing changes to the color bar (or scalar >> bar) visibility and placement. >> http://www.kitware.com/blog/home/post/653 >> >> Let us know if you have any feedback. The code hasn't landed in >> git/master yet and won't for a couple more weeks. >> >> Utkarsh >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects 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://www.paraview.org/mailman/listinfo/paraview > > ------------------------------ Message: 3 Date: Wed, 7 May 2014 11:30:48 +0000 From: "Eggleston, Richard (2011)" <[email protected]> To: "[email protected]" <[email protected]> Subject: [Paraview] Save Interpolated Results Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" ?Hi, I would like to export the results of a calculation made on a vtk import. I have made the calculation and exported it but it only saves the value at the points (nodes). I would like to export a map of the interpolated results, as seen in the display window, is this at all possible? Thanks Richard -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.paraview.org/pipermail/paraview/attachments/20140507/7275f3e2/attachment-0001.html> ------------------------------ Message: 4 Date: Wed, 07 May 2014 14:03:13 +0200 From: Stephen Wornom <[email protected]> To: ParaView list <[email protected]> Subject: [Paraview] PV 4.1.0 binary download ; unstructured mesh. reading pieces fails Message-ID: <[email protected]> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" I have 64 vtu pieces listed in my data.pvtu file. I do not wish to visualize pieces 36, 48, and 49. I remove them from the data.pvtu file (61 vtu pices remain). When I open the data.pvtu file I get this error. ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/IO/XML/vtkXMLPDataReader.cxx, line 364 vtkXMLPUnstructuredGridReader (0x18427600): File for piece 35 cannot be read. How can I correct the error? Thanks, Stephen -- [email protected] 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: 160 bytes Desc: not available URL: <http://www.paraview.org/pipermail/paraview/attachments/20140507/e44be8cb/attachment-0001.vcf> ------------------------------ Message: 5 Date: Wed, 7 May 2014 08:38:36 -0400 From: Utkarsh Ayachit <[email protected]> To: Stephen Wornom <[email protected]> Cc: ParaView list <[email protected]> Subject: Re: [Paraview] PV 4.1.0 binary download ; unstructured mesh. reading pieces fails Message-ID: <cadhsjjam9x3r3cs_m36snp06dcaapun35vu+vgavyv4anuh...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Can you attach the original and modified pvtu file? That'll make it easier :). On Wed, May 7, 2014 at 8:03 AM, Stephen Wornom <[email protected]>wrote: > I have 64 vtu pieces listed in my data.pvtu file. > I do not wish to visualize pieces 36, 48, and 49. I remove them from the > data.pvtu file (61 vtu pices remain). > > > When I open the data.pvtu file I get this error. > ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ > ParaViewSuperbuild-Release/paraview/src/paraview/VTK/IO/XML/vtkXMLPDataReader.cxx, > line 364 > > vtkXMLPUnstructuredGridReader (0x18427600): File for piece 35 cannot be > read. > > > How can I correct the error? > Thanks, > Stephen > > -- > [email protected] > 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 > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.paraview.org/pipermail/paraview/attachments/20140507/a789f16b/attachment-0001.html> ------------------------------ Message: 6 Date: Wed, 07 May 2014 15:34:27 +0200 From: Stephen Wornom <[email protected]> To: Utkarsh Ayachit <[email protected]> Cc: ParaView list <[email protected]> Subject: Re: [Paraview] PV 4.1.0 binary download ; unstructured mesh. reading pieces fails Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8"; Format="flowed" Utkarsh Ayachit wrote: > Can you attach the original and modified pvtu file? That'll make it > easier :). The solf_2D.004000.before.pvtu contains the 1st 40 the vtu files. When I open it in PV, I get an error that PV cannot read piece 36. solf_2D.004000.after.pvtu does not contain piece 35. I get this error > > ERROR: In > > /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/IO/XML/vtkXMLPDataReader.cxx, > line 364 > > vtkXMLPUnstructuredGridReader (0x18427600): File for piece 35 > cannot be read. > Many thanks for your help. Stephen > > > How can I correct the error? > Thanks, > Stephen > > -- > [email protected] <mailto:[email protected]> > 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 <http://www.kitware.com> > > Visit other Kitware open-source projects 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://www.paraview.org/mailman/listinfo/paraview > > -- [email protected] 2004 route des lucioles - BP93 Sophia Antipolis 06902 CEDEX Tel: 04 92 38 50 54 Fax: 04 97 15 53 51 -------------- next part -------------- <VTKFile type="PUnstructuredGrid" byte_order="LittleEndian"> <PUnstructuredGrid GhostLevel="0"> <PPointData> <PDataArray type="Float64" Name="Density" /> <PDataArray type="Float64" Name="Pressure" /> <PDataArray type="Float64" Name="Mach" /> <PDataArray type="Float64" Name="K" /> <PDataArray type="Float64" Name="Epsilon" /> <PDataArray type="Float64" Name="Blend" /> <PDataArray type="Float64" Name="LogFR" /> <PDataArray type="Float64" Name="Temperature" /> <PDataArray type="Float64" Name="gamma" /> <PDataArray type="Float64" Name="SGS" /> <PDataArray type="Float64" NumberOfComponents="3" Name="Velocity" /> <PDataArray type="Float64" NumberOfComponents="3" Name="Vorticity" /> </PPointData> <PCellData> </PCellData> <PPoints> <PDataArray type="Float64" NumberOfComponents="3" /> </PPoints> <Piece Source="solf_2D.004000_1.vtu" /> <Piece Source="solf_2D.004000_2.vtu" /> <Piece Source="solf_2D.004000_3.vtu" /> <Piece Source="solf_2D.004000_4.vtu" /> <Piece Source="solf_2D.004000_5.vtu" /> <Piece Source="solf_2D.004000_6.vtu" /> <Piece Source="solf_2D.004000_7.vtu" /> <Piece Source="solf_2D.004000_8.vtu" /> <Piece Source="solf_2D.004000_9.vtu" /> <Piece Source="solf_2D.004000_10.vtu" /> <Piece Source="solf_2D.004000_11.vtu" /> <Piece Source="solf_2D.004000_12.vtu" /> <Piece Source="solf_2D.004000_13.vtu" /> <Piece Source="solf_2D.004000_14.vtu" /> <Piece Source="solf_2D.004000_15.vtu" /> <Piece Source="solf_2D.004000_16.vtu" /> <Piece Source="solf_2D.004000_17.vtu" /> <Piece Source="solf_2D.004000_18.vtu" /> <Piece Source="solf_2D.004000_19.vtu" /> <Piece Source="solf_2D.004000_20.vtu" /> <Piece Source="solf_2D.004000_21.vtu" /> <Piece Source="solf_2D.004000_22.vtu" /> <Piece Source="solf_2D.004000_23.vtu" /> <Piece Source="solf_2D.004000_24.vtu" /> <Piece Source="solf_2D.004000_25.vtu" /> <Piece Source="solf_2D.004000_26.vtu" /> <Piece Source="solf_2D.004000_27.vtu" /> <Piece Source="solf_2D.004000_28.vtu" /> <Piece Source="solf_2D.004000_29.vtu" /> <Piece Source="solf_2D.004000_30.vtu" /> <Piece Source="solf_2D.004000_31.vtu" /> <Piece Source="solf_2D.004000_32.vtu" /> <Piece Source="solf_2D.004000_33.vtu" /> <Piece Source="solf_2D.004000_34.vtu" /> <Piece Source="solf_2D.004000_35.vtu" /> <Piece Source="solf_2D.004000_37.vtu" /> <Piece Source="solf_2D.004000_38.vtu" /> <Piece Source="solf_2D.004000_39.vtu" /> <Piece Source="solf_2D.004000_40.vtu" /> </PUnstructuredGrid> </VTKFile> -------------- next part -------------- <VTKFile type="PUnstructuredGrid" byte_order="LittleEndian"> <PUnstructuredGrid GhostLevel="0"> <PPointData> <PDataArray type="Float64" Name="Density" /> <PDataArray type="Float64" Name="Pressure" /> <PDataArray type="Float64" Name="Mach" /> <PDataArray type="Float64" Name="K" /> <PDataArray type="Float64" Name="Epsilon" /> <PDataArray type="Float64" Name="Blend" /> <PDataArray type="Float64" Name="LogFR" /> <PDataArray type="Float64" Name="Temperature" /> <PDataArray type="Float64" Name="gamma" /> <PDataArray type="Float64" Name="SGS" /> <PDataArray type="Float64" NumberOfComponents="3" Name="Velocity" /> <PDataArray type="Float64" NumberOfComponents="3" Name="Vorticity" /> </PPointData> <PCellData> </PCellData> <PPoints> <PDataArray type="Float64" NumberOfComponents="3" /> </PPoints> <Piece Source="solf_2D.004000_1.vtu" /> <Piece Source="solf_2D.004000_2.vtu" /> <Piece Source="solf_2D.004000_3.vtu" /> <Piece Source="solf_2D.004000_4.vtu" /> <Piece Source="solf_2D.004000_5.vtu" /> <Piece Source="solf_2D.004000_6.vtu" /> <Piece Source="solf_2D.004000_7.vtu" /> <Piece Source="solf_2D.004000_8.vtu" /> <Piece Source="solf_2D.004000_9.vtu" /> <Piece Source="solf_2D.004000_10.vtu" /> <Piece Source="solf_2D.004000_11.vtu" /> <Piece Source="solf_2D.004000_12.vtu" /> <Piece Source="solf_2D.004000_13.vtu" /> <Piece Source="solf_2D.004000_14.vtu" /> <Piece Source="solf_2D.004000_15.vtu" /> <Piece Source="solf_2D.004000_16.vtu" /> <Piece Source="solf_2D.004000_17.vtu" /> <Piece Source="solf_2D.004000_18.vtu" /> <Piece Source="solf_2D.004000_19.vtu" /> <Piece Source="solf_2D.004000_20.vtu" /> <Piece Source="solf_2D.004000_21.vtu" /> <Piece Source="solf_2D.004000_22.vtu" /> <Piece Source="solf_2D.004000_23.vtu" /> <Piece Source="solf_2D.004000_24.vtu" /> <Piece Source="solf_2D.004000_25.vtu" /> <Piece Source="solf_2D.004000_26.vtu" /> <Piece Source="solf_2D.004000_27.vtu" /> <Piece Source="solf_2D.004000_28.vtu" /> <Piece Source="solf_2D.004000_29.vtu" /> <Piece Source="solf_2D.004000_30.vtu" /> <Piece Source="solf_2D.004000_31.vtu" /> <Piece Source="solf_2D.004000_32.vtu" /> <Piece Source="solf_2D.004000_33.vtu" /> <Piece Source="solf_2D.004000_34.vtu" /> <Piece Source="solf_2D.004000_35.vtu" /> <Piece Source="solf_2D.004000_36.vtu" /> <Piece Source="solf_2D.004000_37.vtu" /> <Piece Source="solf_2D.004000_38.vtu" /> <Piece Source="solf_2D.004000_39.vtu" /> <Piece Source="solf_2D.004000_40.vtu" /> </PUnstructuredGrid> </VTKFile> -------------- next part -------------- A non-text attachment was scrubbed... Name: stephen_wornom.vcf Type: text/x-vcard Size: 169 bytes Desc: not available URL: <http://www.paraview.org/pipermail/paraview/attachments/20140507/90060de5/attachment.vcf> ------------------------------ Subject: Digest Footer _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects 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://www.paraview.org/mailman/listinfo/paraview ------------------------------ End of ParaView Digest, Vol 121, Issue 24 ***************************************** _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects 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://www.paraview.org/mailman/listinfo/paraview
