[dune-pdelab] Very large .vtu files

[Marian Piatkowski]

Hi,

concerning the size of the vtu-files:
Maybe you could try to reduce the amount of sub-sampling. This is the 
number '3' in the VTK-writer.
Because sub-sampling stands for the number of virtual refinements of 
your grid to draw the VTK-output and at the moment you do it three times.
A common choice for the sub-sampling would be 'degree-1' where 'degree' 
is the polynomial degree of your function space.

Best regards,

Marian

On 21.08.2015 23:52, conf86 at web.de wrote:
> Sorry for my late response.
> Thank you, I did it just like that.
> If someone is interested, this is how I solved it:
>
>   // <<<9>>> time loop
>    U unew(gfs,0.0);                                            // solution to be computed
>    while (time<tend-1e-8) {
>        // do time step
>        bctype.setTime(time+dt);                                // compute constraints
>        cc.clear();                                             // for this time step
>        Dune::PDELab::constraints(bctype,gfs,cc);
>        osm.apply(time,dt,uold,g,unew);                         // do one time step
>        
>        if (fmod(time,10*dt)<=1e-3*dt){                         // write every 10th step into a graphic file
>        // graphics
>        Dune::SubsamplingVTKWriter<GV> vtkwriter(gv,3);
>        Dune::PDELab::addSolutionToVTKWriter(vtkwriter,gfs,unew);
>        vtkwriter.write(fn.getName(),Dune::VTK::appendedraw);
>        fn.increment();
>        }
>
>        uold = unew;                                            // advance time step
>        time += dt;
>      }
>
> _______________________________________________
> dune-pdelab mailing list
> dune-pdelab at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune-pdelab