From: Ondrej C. <on...@ce...> - 2006-11-14 10:38:30
|
It seems to me, that the clean solution is to generally separate the mesh creation and assembly and solvers. It seems to me, that libmesh should have just one (say xda, or whatever) format for the input mesh. Then we can have other scripts to convert everything to xda (including tetgen->xda). And you can always run tetgen like this ./tetgen options > tetgen.log. Ondrej On 11/14/06, Tim Kr=F6ger <ti...@ce...> wrote: > Dear all, > > In my application, I use the TetGen wrapper classes. TetGen performs > a lot of console output, which is okay for testing but will be > annoying in real application. (One point is that when diffing the > logfiles of two runs, I get differences in the TetGen time measurement > output. Since this output is performed for all processors, I get an > enormous number of differences, making it difficult to focus on the > important things). > > What would be an appropriate way to avoid this output? > > * Patching the TetGen sources locally in my installtion? Not a good > idea, because I don't like to be inconsistent to the cvs head. > > * Patching the TetGen sources in the libMesh cvs? > > * Talk to the TetGen developer and suggest him to include a "quiet" > option? > > Any ideas? > > Best Regards, > > Tim > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job ea= sier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronim= o > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > _______________________________________________ > Libmesh-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-users > |