Yeah, of course I know that the RHS is my source... At least which equation I wanna solve after all.... I'm just asking how I would write it in the code explicitly, since we no longer have just the vector with indices of the nodes but the points are quadrature points for each element when we construct Fe and Ke...
To recap, I guess I wasn't very clear (regarding what Roy mentioned) how to store the data on a degree 1 LAGRANGE basis in the code... I've used the original Poisson example with a constant term for fxy to test the program, but I ought to be feeding that from my data (which I have successfully read into MeshData, just not sure how to access the correct points...) I know that the quadrature points are not the node values... How do I assign the correct values and not have MeshData think I'm giving it a node it doens't know about? Also, should I be using mesh_data.operator()? Would I be better off storing data to be used in the RHS for elements instead of for the nodes instead? Thanks, Karen On Thu, Mar 11, 2010 at 12:22 AM, liang cheng <[email protected]> wrote: > >> >> >> I'm a newbie to finite element, and I guess I wasn't very clear how to >> store >> the data on a degree 1 LAGRANGE basis in the code... I just tried to give >> fxy the correct RHS value and do the same thing as example 3. I know that >> the quadrature points are not the node values... How do I assign the >> correct >> values and not have MeshData think I'm giving it a node it doens't know >> about? (Also, am I using mesh_data,operator() correctly? And is this the >> function to use?) >> >> Would I be better off storing data to be used in the RHS for elements >> instead of for the nodes instead? >> >> I guess I don't know this too well for now, so might need you to spell it >> out more... Sorry about that. >> >> Thanks! >> Karen >> >> ------------------------------------------------------------------------------ >> >> I am newbie also, as far as I know the RHS(right hand side) means the > source term in your PDE or weak form of PDE. just my 2cents. > > Liang > ------------------------------------------------------------------------------ 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
