#1793: activating 3d output at restart results in unexpected behavior ---------------------------------+------------------------------------------ Reporter: physik@… | Owner: eschnett Type: defect | Status: new Priority: unset | Milestone: Component: Carpet | Version: ET_2014_05 Resolution: | Keywords: ---------------------------------+------------------------------------------
Comment (by rhaas):
Yes, the code paths for 'out_vars' and 'out3d_vars' are completely different. Basically 'out_vars' is the older implementation and the one required for checkpointing/recovery so will always write the full amount of data in a grid function/grid array. 'out3d_vars' uses the same code as the other 'outXD_vars' options and can only write 3d data.
Both should be functional and both are supported right now, however -- at least personally -- I would recommend using 'out3d_vars' for output and also tend to add more complex new features (such as being able to remove buffer points for output, and use less than one file per process) only to 'out3d_vars'.
Yes, according to your parfile you are not setting 'out3d_vars' so will use the default value for that parameter which is empty and for 'out3d_every' you'd use its default which means 'no output'.