On Sun, 31 Aug 2014, Miguel Angel Salazar de Troya wrote: > I apologize for the big amount of questions I'm asking lately. Clearly, a > deadline is looming...
I apologize for the questions that have (and probably will) go unanswered. There's a catch-22 wherein people qualified to answer complex questions are also people who don't have time to answer complex questions. If you want to write up FAQ entries or pay it forward on libmesh-users yourself someday then we'll call it even. > I'm trying to modify each component of the solution vector of a > system in parallel, and then evaluate the qoi by calling the > function assemble_qoi. > The problem is that if I do this in parallel, I'm actually modifying more > than one component of the solution vector, therefore I'm not obtaining the > value that I would like to get in assemble_qoi. I don't think I'm understanding this, but let me try answering a few different interpretations of the question: If you're trying to modify every part of the solution vector in parallel and you can decompose things onto subdomains additively, that's easy; take a look at what typical assembly functions do. If the support for the function defining each new dof value falls within a processor's partition plus ghost elements, but it doesn't decompose additively, you'll want to use set() instead of add(), but you'll want to test each dof first to see if it's "owned" by the local processor. Take a look at the System::project_vector implementations for this case. If the support for the function defining each new dof value falls outside a single layer of ghost elements, and you're under a deadline, then you're probably best off serializing. See what we do in exact_solution.C in the _equation_systems_fine case for an example. --- Roy ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
