On Thu, Feb 11, 2016 at 2:57 PM, Salazar De Troya, Miguel <
salazardet...@llnl.gov> wrote:
> Hello
>
> Does Exodus_IO::write_timestep() support writing on the same file after a
> refinement half through the simulation? For instance, doing this:
>
> ExodusII_IO exio(mesh);
> for (unsigned int i_step = 0; i_step<100; i_step)
> {
> exio.write_timestep("transient_data.exo", eq_sys, i_step, i_step*.01);
> exio.append(true);
> If (i_step == 50)
> Refinement();
> }
>
> Ideally I would like to have the entire simulation show the refinement in
> one file. I can imagine that this must be hard given the topology change.
IIRC, according to the Exodus format, you can't have any topology changes
and write to the same file. You can write to the same file up until you do
a refinement, then you'll need to write to a new file. Note that ParaView
will do the right thing if you have a sequence of files corresponding to
time steps even if there's mesh refinement (you just need to name it
properly: file.e-s.<timestep #>).
> Doing what I did above does not show the refined mesh and if I also try to
> call Exodus_IO::write_element _data() gives me an error. I am thinking of
> recording one file per refinement and then glue them together on Paraview
> if it cannot be done in one file. Is there any way to do so?
>
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
