On Tue, 22 Aug 2017, James Strother wrote:
Thanks a lot for your help. "solution," so initially every function returned zero. But once I changed "solution->set()" to "current_local_solution->set()" everything seems to work fine. I'm not really sure what the difference is, so I'm hoping that is a reasonable thing to do.
No, but the reasonable thing to do in parallel is confusing. What you want to do is solution->set() (which sets the master copy of the solution, from processors which own the "local" indices they're setting), and then (after all the set() calls are done) System::update() (which synchronizes that master copy of the solution with the "ghosted" copy in current_local_solution, which stores both local and "ghosted" coefficients).
I was wondering how I should deal with vector-valued variables? Should I just allocate a new variable for every component of the vector, or would it be better to handle this in another way?
Depends on your system. If a tensor product of scalar finite element spaces gives you a vector finite element space you're happy with, then adding separate variables for each component will give you that. You could also add a single variable of type LAGRANGE_VEC, but there are a number of libMesh features which don't support vector-valued variables currently, so LAGRANGE_VEC is really only useful for testing. If you need a more clever vector-valued space, we do have the NEDELEC_ONE variables (which were needed by a clever developer for the electromagnetics in a multiphysics problem), but we haven't implemented any of the other standard vector elements.
The warning that I receive is: *** Warning, This code is deprecated, and likely to be removed in future library versions! ./include/libmesh/mesh_tools.h, line 70, compiled Aug 19 2017 at 14:03:27 *** From what I can tell point_value() isn't marked deprecated, but it invokes a deprecated form of the BoundaryBox constructor. I suppose I'll just ignore it.
Just ignore it, but thanks for reporting it! I'll look at it now. --- Roy ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
