From: Steffen P. <ste...@tu...> - 2004-04-04 21:32:59
|
Martin L=FCthi wrote: >Hi all > >Either I am again missing something obvious (in that case: sorry for >the noise), or I feel something is missing: > >Upon mesh refinement, the mesh.data is not projected on the new mesh. >To my understanding this could be accomplished in a similar way as the >projection of solution vectors. Indeed the only workaround I could >come up with was to add a trivial system, solve it for the nodal data >on the RHS, and subsequently use the solution of this system to >obtain the data values on a refined mesh. > =20 > Try the MeshData::translate function. Than you do not have to solve a sys= tem to get the data in a vector, and let the system do the projection. I am=20 not quite sure if a function similar to project_vector is really necessary in MeshData=20 (code duplication!?). Steffen >I think that such a routine would be either explicitly called as >mesh.data.reinit(), or would automatically be called by =20 >mesh_refinement.refine_and_coarsen_elements(); > =20 > >Does this make sense? > >Best, Martin > > > >------------------------------------------------------- >This SF.Net email is sponsored by: IBM Linux Tutorials >Free Linux tutorial presented by Daniel Robbins, President and CEO of >GenToo technologies. Learn everything from fundamentals to system >administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcl= ick >_______________________________________________ >Libmesh-users mailing list >Lib...@li... >https://lists.sourceforge.net/lists/listinfo/libmesh-users > > =20 > |