Hello Bruno, Thank you for your answer! Also thank you for the URL, those tests are really a good place to learn deal.II.
Best, Yiyang On Thursday, October 19, 2017 at 1:46:55 PM UTC-5, Bruno Turcksin wrote: > > Yiang, > > 2017-10-19 13:53 GMT-04:00 Yiyang Zhang <zyyce...@gmail.com <javascript:>> > : > >> >> i) I checked this page. I am a little confused. As soon as >> signal.post_refinement.connect() is called, I assume set_boundary_ids() is >> always attached to the Triangulation object, and it will always refresh the >> boundary IDs when a refinement is done. Right? >> > Sorry I misread what you wrote. You are correct you only set it once but > it is called many times. > > >> >> iii) I think it's ok. But should it be more efficient if we identify >> which cells are moved, and send a modified locally_owned_vertices vector? I >> don't know the implementation, so I don't know if that will change the >> efficiency. >> >> This is something I wouldn't bother with. Most of the time of your > program is going to be spent in your solver. Doing the optimization that > your are talking about will probably not make a big difference unless your > mesh is very fine. Anyway if you want to look how to do it right, you can > take a look at the tests (in particular this one > <https://github.com/dealii/dealii/blob/103056a1fc61609d68faa8bb454150a25641058a/tests/mpi/communicate_moved_vertices_02.cc> > > show a way to fill the vector). > > Best, > > Bruno > > > <https://github.com/dealii/dealii/blob/103056a1fc61609d68faa8bb454150a25641058a/tests/mpi/communicate_moved_vertices_02.cc> > -- The deal.II project is located at http://www.dealii.org/ For mailing list/forum options, see https://groups.google.com/d/forum/dealii?hl=en --- You received this message because you are subscribed to the Google Groups "deal.II User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to dealii+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
