Sylvain, Oh, I think I know what those values appears and it is my bad ... > It is probably not 22116 but 22 and 116 and it is probably not 89130 but > rather 89 and 130. I used something like *std::cout << dof_index[0] << > std::endl* to get those values and sometimes they just get attached to > each other like if the *std::endl* was skipped (not sure why, maybe > because I have several threads ?). I did not realise it before reading your > message but it actually makes sense because I was not getting an error for > those values and my Assert was not triggered. I should have seen it, sorry. >
I ran into this exact issue a few weeks ago. For printing statements while debugging in assembly loops, check the signatures of functions like MeshWorker::run and MeshWorker::mesh_loop. You should be able to pass parameters that force non-multithreaded execution, and your print statements will make sense. I found this helpful for debugging. Best, Corbin -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/dealii/7ec902ce-e1fa-4baa-a669-4b2b288479dfn%40googlegroups.com.
