deal.II version GIT relicensing-1936-ge55124254b 2024-10-04 21:10:00+00:00
\(\newcommand{\dealvcentcolon}{\mathrel{\mathop{:}}}\) \(\newcommand{\dealcoloneq}{\dealvcentcolon\mathrel{\mkern-1.2mu}=}\) \(\newcommand{\jump}[1]{\left[\!\left[ #1 \right]\!\right]}\) \(\newcommand{\average}[1]{\left\{\!\left\{ #1 \right\}\!\right\}}\)
Loading...
Searching...
No Matches
Public Member Functions | Static Public Member Functions | Public Attributes | List of all members
GridOutFlags::Vtu Struct Reference

#include <deal.II/grid/grid_out.h>

Inheritance diagram for GridOutFlags::Vtu:
Inheritance graph
[legend]

Public Member Functions

 Vtu (const bool serialize_triangulation=false)
 
void parse_parameters (const ParameterHandler &prm)
 
std::size_t memory_consumption () const
 

Static Public Member Functions

static void declare_parameters (ParameterHandler &prm)
 

Public Attributes

bool serialize_triangulation
 
double time
 
unsigned int cycle
 
bool print_date_and_time
 
DataOutBase::CompressionLevel compression_level
 
bool write_higher_order_cells
 
std::map< std::string, std::string > physical_units
 

Detailed Description

Flags for grid output in Vtu format. These flags are the same as those declared in DataOutBase::VtkFlags, with the addition of a flag that determines if you want to add a entry in the vtu file (which is really a xml file) containing the entire serialization of the triangulation.

Definition at line 905 of file grid_out.h.

Constructor & Destructor Documentation

◆ Vtu()

GridOutFlags::Vtu::Vtu ( const bool  serialize_triangulation = false)
inline

Definition at line 907 of file grid_out.h.

Member Function Documentation

◆ declare_parameters()

void DataOutBase::OutputFlagsBase< VtkFlags >::declare_parameters ( ParameterHandler prm)
staticinherited

Declare all flags with name and type as offered by this class, for use in input files.

This method does nothing, but child classes may override this method to add fields to prm.

Definition at line 574 of file data_out_base.h.

◆ parse_parameters()

void DataOutBase::OutputFlagsBase< VtkFlags >::parse_parameters ( const ParameterHandler prm)
inherited

Read the parameters declared in declare_parameters() and set the flags for this output format accordingly.

This method does nothing, but child classes may override this method to add fields to prm.

Definition at line 584 of file data_out_base.h.

◆ memory_consumption()

std::size_t DataOutBase::OutputFlagsBase< VtkFlags >::memory_consumption ( ) const
inherited

Return an estimate for the memory consumption, in bytes, of this object. This is not exact (but will usually be close) because calculating the memory usage of trees (e.g., std::map) is difficult.

Definition at line 593 of file data_out_base.h.

Member Data Documentation

◆ serialize_triangulation

bool GridOutFlags::Vtu::serialize_triangulation

Add to the vtu file also the serialized triangulation.

Definition at line 914 of file grid_out.h.

◆ time

double DataOutBase::VtkFlags::time
inherited

The time of the time step if this file is part of a time dependent simulation.

The value of this variable is written into the output file according to the instructions provided in http://www.visitusers.org/index.php?title=Time_and_Cycle_in_VTK_files unless it is at its default value of

std::numeric_limits<unsigned int>::min() 

.

Definition at line 1138 of file data_out_base.h.

◆ cycle

unsigned int DataOutBase::VtkFlags::cycle
inherited

The number of the time step if this file is part of a time dependent simulation, or the cycle within a nonlinear or other iteration.

The value of this variable is written into the output file according to the instructions provided in http://www.visitusers.org/index.php?title=Time_and_Cycle_in_VTK_files unless it is at its default value of

std::numeric_limits<unsigned int>::min() 

.

Definition at line 1150 of file data_out_base.h.

◆ print_date_and_time

bool DataOutBase::VtkFlags::print_date_and_time
inherited

Flag to determine whether the current date and time shall be printed as a comment in the file's second line.

Default is true.

Definition at line 1158 of file data_out_base.h.

◆ compression_level

DataOutBase::CompressionLevel DataOutBase::VtkFlags::compression_level
inherited

Flag determining the compression level at which zlib, if available, is run. The default is best_speed.

Definition at line 1164 of file data_out_base.h.

◆ write_higher_order_cells

bool DataOutBase::VtkFlags::write_higher_order_cells
inherited

Flag determining whether to write patches as linear cells or as a high-order Lagrange cell.

Default is false.

Note
The ability to write data that corresponds to higher order polynomials rather than simply linear or bilinear is a feature that was only introduced in VTK 8.1.0 in December 2017. You will need at least Paraview version 5.5.0 released in April 2018 or a similarly recent version of VisIt for this feature to work (for example, VisIt 3.1.1, released in February 2020, does not yet support this feature). Older versions of these programs are likely going to result in errors when trying to read files generated with this flag set to true. Experience with these programs shows that these error messages are likely going to be rather less descriptive and more obscure.

Definition at line 1183 of file data_out_base.h.

◆ physical_units

std::map<std::string, std::string> DataOutBase::VtkFlags::physical_units
inherited

A map that describes for (some or all) of the output quantities what the physical units are. This field is ignored for VTK file format, but used for VTU format where it is attached to the individual scalar, vector, or tensor fields for use by visualization or other postprocessing tools. The default is to not attach any physical units to fields at all, i.e., an empty map.

If the map does not contain an entry for a specific output variable, then no unit will be written into the output file. In other words, it is not an error to provide units for only some variables.

step-19, step-44 and step-69 all demonstrate how to use this variable.

Note
While the functions that make use of this information do not care about how physical units are specified, downstream postprocessing tools should and do. As a consequence, these units should be specified in a format that is understandable to these postprocessing tools. As an example, the unyt project describes a standard for describing and converting units.

Definition at line 1206 of file data_out_base.h.


The documentation for this struct was generated from the following file: