From 26ecb12c84204cd08bf37b18686e0d756838033c Mon Sep 17 00:00:00 2001 From: wolf Date: Tue, 5 Apr 2005 21:20:05 +0000 Subject: [PATCH] Reference step-18. git-svn-id: https://svn.dealii.org/trunk@10368 0785d39b-7218-0410-832d-ea1e28bc413d --- deal.II/examples/step-17/step-17.cc | 46 ++++++++++++++++------------- 1 file changed, 26 insertions(+), 20 deletions(-) diff --git a/deal.II/examples/step-17/step-17.cc b/deal.II/examples/step-17/step-17.cc index da3431b476..e6adf7d48c 100644 --- a/deal.II/examples/step-17/step-17.cc +++ b/deal.II/examples/step-17/step-17.cc @@ -961,26 +961,32 @@ unsigned int ElasticProblem::solve () // times they generate output through this // function. // - // The solution to this is to have each - // process generate output data only for it's - // own local cells, and write them to - // separate files, one file per process. This - // would distribute the work of generating - // the output to all processes equally. In a - // second step, separate from running this - // program, we would then take all the output - // files for a given cycle and merge these - // parts into one single output file. This - // has to be done sequentially, but can be - // done on a different machine, and should be - // relatively cheap. However, the necessary - // functionality for this is not yet - // implemented in the library, and since we - // are too close to the next release, we do - // not want to do such major destabilizing - // changes any more. It will be fixed in - // later releases of the library and this - // example program, though. + // The solution to this is to have + // each process generate output data + // only for it's own local cells, and + // write them to separate files, one + // file per process. This would + // distribute the work of generating + // the output to all processes + // equally. In a second step, + // separate from running this + // program, we would then take all + // the output files for a given cycle + // and merge these parts into one + // single output file. This has to be + // done sequentially, but can be done + // on a different machine, and should + // be relatively cheap. However, the + // necessary functionality for this + // is not yet implemented in the + // library, and since we are too + // close to the next release, we do + // not want to do such major + // destabilizing changes any + // more. This has been fixed in the + // meantime, though, and a better way + // to do things is explained in the + // step-18 example program. template void ElasticProblem::output_results (const unsigned int cycle) const { -- 2.39.5