> Yes, so do many of us, but what kind of data? Data like initial > conditions and forcing functions in L2/H1/H2 is easy to store with an > ExplicitSystem::solution. Data like material properties maps well to > subdomain ids. > > It's the gradient of the output of some other simulation, to be used in the RHS of my Poisson's equation. My mesh is the dual mesh of my collaborator who gave me the outputs, and so these numbers are not a smooth function but just whatever comes out.
I also just wanted to check how to properly put in the RHS which I read into MeshData. (I have checked that it read in the correct things by outputting it to a file, but not getting the info entry by entry.) Is there a function analogous like get_xyz that I can use rather than doing the following (modified from example 3, and which may not even be correct)? const Real x = q_point[qp](0); const Real y = q_point[qp](1); const Real z = q_point[qp](2); Node node(x,y,z,qp); const Real fxy = mesh_data.operator() (node, 0); Thanks so much, Karen ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
