may be easiest to write out an exodus file and use paraview to extract whatever points you are interested in?
df > > Message: 7 > Date: Mon, 12 Jan 2009 17:26:05 +0100 (CET) > From: Tim Kroeger <[email protected]> > Subject: [Libmesh-users] MeshFunction > To: [email protected] > Message-ID: <[email protected]> > Content-Type: TEXT/PLAIN; format=flowed; charset=UTF-8 > > Dear all, > > At the end of my application, I want to evaluate the computed solution > at a number of points (which cannot be assumed to be grid nodes). > Since I only want to write the values to a file, it suffices to do > this on one processor. > > My idea was: > > 1. Localize. > 2. On all processors except #0, let everything go out of scope. > 3. On processor #0, make a MeshFunction and evaluate as required. > > However, this fails to work because there is a call to parallel_only() > in the initialization of MeshFunction (that is, in tree.C, line 45, > MeshTools::bounding_box() is called, which itself calls > parallel_only()). > > Is there any chance to work around this problem? > > An idea would be to allow the user to manually specify the bounding > box of the mesh. > > Any suggestions welcome. > > Best Regards, > > Tim > > -- > Dr. Tim Kroeger > [email protected] Phone +49-421-218-7710 > [email protected] Fax +49-421-218-4236 > > Fraunhofer MEVIS, Institute for Medical Image Computing > Universitaetsallee 29, 28359 Bremen, Germany > > > > ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
