Oops, I should have re-titled this email.What I meant to say, is the images in the previous email are showing one of the issues I have been seeing with the data set. I recently pulled and rebuilt ParaView from source and things are better:
a) It is not crashing with this data set; yay!b) Not displaying those crazy bounds - though sometimes it loads and does not show anything; c) And I think I saw on the git log that Utkarsh fixed a crashing bug when a xdmf temporal collection had no time step specified (so thanks Utkarsh! and whoever else fixed bugs :-)
Jon On 2/8/2011 6:43 PM, Jon Goldman wrote:
To followup a bit, attached are two images of the issue I am seeing. The two-lobe rendering (from another package) is correct. The single lobe that is rendered with ParaView is incorrect.And if somebody would be kind enough to download the sample data and verify what I am seeing:http://pages.swcp.com/~goldman/data/farfield/farfield.xmf.zip <http://pages.swcp.com/%7Egoldman/data/farfield/farfield.xmf.zip>And/or if anybody knowledgeable on the xdmf or paraview source code can suggest an area of the code to look at, I can dig in to figure out what's going on.thanks, Jon
smime.p7s
Description: S/MIME Cryptographic 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
