Hi, Please respond to the entire mailing list so that anyone that wants to participate or follow along can.
I think the issue here is that you have the same cell specified in multiple vtu files and ParaView is getting confused when trying to render them. These are the overlapping cells at the subdomain boundary. My recommendation would be to either mark these repeated cells as ghost cells (see https://blog.kitware.com/ghost-and-blanking-visibility-changes/ for information on that). Other than that, you could use the Clean to Grid filter to get rid of coincident points and then use the Clean Cells to Grid filter to get rid of extra copies of the cell. Cheers, Andy On Tue, Sep 5, 2017 at 6:24 PM, Rilin Shen <shenri...@gmail.com> wrote: > > Bone.7z > <https://drive.google.com/file/d/0B1JLvkeOK5PQVXR3cTBHa2lfQjQ/view?usp=drive_web> > Dear Andy, > > Thanks a lot for your help. > > As you said, It looks like a ghost cell issue. I attached my dataset. > Please check it. > > If you need any additional information, please let me know. > > Best regards, > > Rilin Shen > Division of Solid Mechanics, School of Astronautics > *Harbin Institute of Technology*, Harbin 150001, China > Civil Engineering & Engineering Mechanics > *Columbia University*, New York 10027, U.S. > Tel: (+1) 646-200-2122 <(646)%20200-2122> > Email: shenri...@gmail.com / rs3...@columbia.edu <shenri...@126.com> > > 2017-09-05 16:54 GMT-04:00 Andy Bauer <andy.ba...@kitware.com>: > >> Hi, >> >> This typically happens when ghost cells are marked improperly or the data >> set has a node/point partitioning and no cells to bridge between the >> subdomains (though the point partitioning issue usually happens with finite >> difference simulations instead of FEM simulations). If you could share your >> dataset it would be easier to diagnose. >> >> Best, >> Andy >> >> On Tue, Sep 5, 2017 at 4:23 PM, Rilin Shen <shenri...@gmail.com> wrote: >> >>> Dear all, >>> >>> I'm very happy to meet all of you in this society. >>> >>> I use a finite element software with multiprocessors(40) to solve >>> problems. >>> >>> All the .vtu files. associated with each processor are output and then a >>> file .pvtu is generated. >>> >>> The original file is displayed perfectly as shown in bone.png. However, >>> when I try to cut it with a plane, it occurs the following issue as >>> clip.png, It seems not be displayed correctly. >>> >>> Would you please tell me what happened to my data? >>> >>> Best regards, >>> >>> Rilin Shen >>> Division of Solid Mechanics, School of Astronautics >>> *Harbin Institute of Technology*, Harbin 150001, China >>> Civil Engineering & Engineering Mechanics >>> *Columbia University*, New York 10027, U.S. >>> Tel: (+1) 646-200-2122 <(646)%20200-2122> >>> Email: shenri...@gmail.com / rs3...@columbia.edu <shenri...@126.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
