Writers#
tecio.open() returns a TecplotSzlWriter,
TecplotPltWriter, or TecplotDatWriter for
modes 'w'/'x', based on the output file extension, or an
AppendWrite/AppendReadWrite for modes
'a'/'a+'. All three concrete writers share the same five-method
lifecycle:
with tecio.open("out.szplt", "w", variables=["x", "y", "p"]) as w: # 1. open
w.add_auxdataset_dict({"Solver": "SU2"}) # 2. stage dataset level aux data
w.write_ordered_zone(data=[x, y, p], title="Zone 1") # 3. write structured zones
w.write_fe_zone(data=[...], zone_type=ZoneType.FETRIANGLE, ...) # 4. write unstructured zones
w.write_femixed_zone(data=[...], cell_shapes=[...], node_maps=[...]) # SZL only
w.write_poly_zone(data=[...], zone_type=ZoneType.FEPOLYGON, ...) # PLT and DAT only
# 5. close happens automatically on context-manager exit
Opening with an explicit variables list opens the file immediately
(eager open); omitting it defers file creation until the first zone write,
which must then supply variables itself (lazy open). Either way, closing
(directly, or via the context manager, recommended) is required to produce a
valid, readable file.
Order of operations#
The SZL format allows for flexible order of operations, but PLT and DAT
require a sequential order of operations. However, the implementation of
writing via tecio.open() requires all three formats to write zones
sequentially. If a SZL file is desired to be written with arrays out of
sequence, tecio.libtecio wrapper functions must be called directly.
Zone-level aux data must be specified with the zone write methods, but dataset aux data may be staged at any time. Upon file close, all buffered aux data is written to the file before finalizing output.
TecplotWriter#
Set once at construction. These are plain attributes, not properties,
readable at any point, but reassigning one after the file header has
already been written (e.g. title under eager-open, once the first zone
exists) changes the Python object without changing the file, the header was
already committed.
Attribute |
Type |
Description |
|---|---|---|
|
|
Output file path |
|
|
Dataset title |
|
|
Variable name list, |
|
|
|
|
|
0-based index of the most recently written zone, |
meta (below) is a running, read-only summary of everything committed to
the file so far (title, variables, aux-item counts, and a per-zone record
in write order), useful for a quick sanity check without re-opening the
file for reading.
|
Shared interface and lifecycle for all Tecplot file writers. |
write_ordered_zone#
Writes one complete IJK-ordered zone. Dimensions are inferred from the shape
of the first array (1-D → (N, 1, 1), 2-D → (I, J, 1), missing trailing
dimensions default to 1).
Parameter |
Type |
Default |
SZL |
PLT |
DAT |
|---|---|---|---|---|---|
|
|
required |
✓ |
✓ |
✓ |
|
|
|
✓ |
✓ |
✓ |
|
|
|
✓ |
✓ |
✓ |
|
|
|
✓ |
✓ |
✓ |
|
|
|
✓ |
✓ |
✓ |
|
|
|
✓ |
✓ |
✓ |
|
|
|
✓ |
✓ |
✓ |
|
|
|
✓ |
✓ |
✓ |
|
|
|
✓ |
✓ |
✓ |
|
|
|
✓ |
✓ |
✓ |
|
|
|
✓ |
— |
— |
flush (SZL only) writes this zone’s data to a temporary file and releases
it from memory immediately, rather than holding everything until close();
useful for very large datasets. Every other parameter behaves identically
across all three formats.
var_sharing maps a variable (by name or 0-based index) to the 0-based
index of the zone to share it from, e.g. {"x": 0, "y": 0} shares x and
y from zone 0. passive_vars takes variable names or 0-based indices,
e.g. {"x"} or [3].
write_fe_zone#
Writes one complete finite-element zone. All the write_ordered_zone parameters
apply here too (except datapacking, which only means something for
ordered zones), plus:
Parameter |
Type |
Default |
SZL |
PLT |
DAT |
|---|---|---|---|---|---|
|
|
required |
✓ |
✓ |
✓ |
|
|
|
✓ |
✓ |
✓ |
|
|
|
✓ |
✓ |
✓ |
|
|
|
✓ |
✓ |
accepted, not yet written¹ |
|
|
|
✓ |
✓ |
accepted, not yet written¹ |
|
|
|
✓ |
— |
— |
Node and cell counts are inferred from node_map, or, if node_map is
omitted, from the zone referenced by con_sharing. node_map holds
0-based node indices into this zone’s coordinate arrays. con_sharing is
the 0-based index of the zone to share connectivity from, or None to
write node_map directly. face_neighbors cell references, remote-zone
references, and the face ordinal (0..faces-per-cell - 1) are all 0-based.
Tecplot 360 itself and the data format guide’s face-numbering diagrams
number faces starting at 1; tecio follows Python container-index
convention here instead, same as everywhere else in the Python API.
¹ Known limitation: DAT’s face_neighbors/face_nbr_mode parameters are
accepted without error but currently do nothing, the ASCII face-neighbor
representation isn’t implemented yet. Passing them silently produces a file
with no face-neighbor data, planned work, not yet scheduled.
write_femixed_zone#
Writes one complete FEMIXED zone (SZPLT only). A FEMIXED zone holds multiple
“sections” sections, where each section contains homogeneous element shape and
grid order. write_femixed_zone is not currently suported for PLT and DAT file
formats (Tecplot contstraint) and will raise a NotImplementedError Variable,
sharing, time, strand ID and aux parameters of write_fe_zone also apply to
write_femixed_zone, plus new keyword arguments:
Parameter |
Type |
Default |
SZL |
PLT |
DAT |
|---|---|---|---|---|---|
|
|
|
✓ |
✗ |
✗ |
|
|
|
✓ |
✗ |
✗ |
|
|
|
✓ |
✗ |
✗ |
|
|
|
✓ |
— |
— |
cell_shapes and node_maps have one entry per section. Each node map is a
(num_cells, nodes_per_cell) integer array of 0-based node indices, a section
may hold no cells, and all sections must have the same spatial dimension (all
line, all surface or all volume cells). Node and cell counts are inferred from
the node maps, or from the FEMIXED zone referenced by con_sharing, in which
case both arguments should be omitted. A cell-centered array lists the cells
of the first section first. While higher order elements are supported by
Tecplot for FEMIXED, only linear cells are implemented in this library. Face
neighbors are not written.
Note
SZPLT may store cells and nodes in a different order than the order supplied to TecIO. When read back every variable and node map will be reordered consistently.
Face neighbors for FEMIXED is broadly disabled for SZPLT due to a bug in the version of TecIO released with the Tecplot360 2025R2.
with tecio.open("mesh.szplt", "w") as w:
w.write_femixed_zone(
data=[x, y, z, p],
cell_shapes=[FeCellShape.TETRAHEDRON, FeCellShape.HEXAHEDRON],
node_maps=[tets, hexes], # (n_tets, 4) and (n_hexes, 8)
variables=["x", "y", "z", "p"],
)
write_poly_zone#
Writes one complete FEPOLYGON or FEPOLYHEDRON zone. PLT and DAT only; SZPLT
raises NotImplementedError (Tecplot plans SZPLT polyhedra support in a future
TecIO release). write_fe_zone raises ValueError for these zone types. The
write_fe_zone variable, sharing, time, strand and aux parameters apply here
too, plus:
Parameter |
Type |
Default |
SZL |
PLT |
DAT |
|---|---|---|---|---|---|
|
|
required |
✗ |
✓ |
✓ |
|
|
|
✗ |
✓ |
✓ |
|
|
|
✗ |
✓ |
✓ |
|
|
|
✗ |
✓ |
✓ |
|
|
|
✗ |
✓ |
✓ |
|
|
|
✗ |
✓ |
✓ |
|
|
|
✗ |
✓ |
✓ |
|
|
|
✗ |
✓ |
✓ |
|
|
|
✗ |
BLOCK |
BLOCK |
Note that all face connectivity arrays use 0-baesd node and element indices,
consistently with the node connectivity and face neighbors for classical
finite-element zones. 1D arrays for face_left_elements/face_right_elements are required to
indicate the element on each side of a face. An edge cell face with no
neighbor should use -1, and -(b + 2) to point at boundary face b, which
is described by the three boundary arrays. face_node_counts is required for
polyhedra, but Polygon faces always have two nodes and is optional (must be
all 2 if given). Node and element counts are inferred as the highest index
plus one. If boundary faces are defined for a zone, connectivity is sharing is
disabled as the zone boundary must be uniquely defined. Tecplot requires BLOCK
packing for poly zones (even with only nodal variables) so this package will
raise ValueError for datapacking="POINT".
Format-specific classes#
Constructor and a handful of format quirks; everything else is the shared interface above.
|
Write Tecplot SZL ( |
|
Write Tecplot PLT ( |
|
Write Tecplot ASCII ( |
Precision#
Each writer’s precision constructor argument means something different,
this is the one constructor parameter worth understanding up front rather
than discovering by trial and error.
SZL |
PLT |
DAT |
|
|---|---|---|---|
Default |
|
|
|
Scope |
Optional whole-file override; without it, each variable’s on-disk type is inferred from its own array’s dtype |
Whole file, unconditionally; the classic API has no per-variable type at all, even integers are stored as the chosen float type |
Whole file for the float-vs-double choice and the printed significant-digit count; integer-inferred variables always keep their own declared type ( |
DAT is the one format where an integer variable’s memory footprint on read
genuinely depends on what was written, not on precision, e.g. a count
array written alongside float64 coordinates under precision=DataType.DOUBLE
still declares (and reads back) as LONGINT, only the printed digit count
for the floating-point variables changes.