The ASCII format follows the general block structure of the OSCAR format, but offers more flexibility with the particle line quantities written in the file. It is available for the Particles and Collisions output contents (see Output), creating files with the extension .dat. This format is useful to decrease storage usage.

Key(s)	C++ type	Description
`t`, `x`, `y`, `z`	`double`	Space-time coordinates
`mass`	`double`	Particle's rest-mass
`p0`, `px`, `py`, `pz`	`double`	Energy and 3-momentum
`pdg`	`int32_t`	PDG code of the particle (see http://pdg.lbl.gov/). It contains all quantum numbers and uniquely identifies its type
`ID`, `id`	`int32_t`	Particle identifier in terms of an integer. It is unique for every particle in the event. `ID` is used in the OSCAR 2013 standard, while `id` is used in OSCAR 1999
`charge`	`int32_t`	Electric charge of the particle in units of the elementary charge \(e\)
`ncoll`	`int32_t`	Number of collisions the particle has undergone
`form_time`	`double`	Formation time of the particle
`xsecfac`	`double`	Cross section scaling factor (if the particles are not yet fully formed at the time of interaction, the cross section for the underlying process is scaled down by the cross section scaling factor)
`proc_id_origin`	`int32_t`	ID of the process of the particle's last interaction
`proc_type_origin`	`int32_t`	Type of the last process the particle has undergone. The possible process types are listed in Process types
`time_last_coll`	`double`	Time of the particle's last interaction (except wall crossings)
`pdg_mother1`	`int32_t`	PDG code of the 1st mother particle (0 in case the particle is sampled in a thermal bubble. It is not updated by elastic scatterings)
`pdg_mother2`	`int32_t`	PDG code of the 2nd mother particle (0 in case the particle results from the decay of a resonance or the appearance of a thermal bubble. In the former case, `pdg_mother1` is the PDG code of this resonance. It is not updated by elastic scatterings)
`baryon_number`	`int32_t`	Baryon number of the particle: 1 for baryons, -1 for anti-baryons and 0 for mesons
`strangeness`	`int32_t`	Net-strangeness of the particles
`0`	-	Prints a column of 0 (for compatibility with OSCAR 1999)

Attention

Not all combinations of quantities are allowed and, in particular:

id and ID cannot be given together;
the same quantity cannot be repeated.

Example

If one is interested, for example, in the rate of production/annihilation of resonances, for events divided into centrality classes based on the charged particle yield at midrapidity, the config file would contain the following:

Output:
    Particles:
        Format:     ["ASCII"]
        Quantities: ["p0","pz","pdg","charge"]
        Only_Final: IfNotEmpty
    Collisions:
        Format:     ["ASCII"]
        Quantities: ["t","pdg","ID","pdg_mother1","pdg_mother2"]

Then, the output files would have the following headers:

particle_lists.dat

#!ASCII particle_lists p0 pz pdg charge
# Units: GeV GeV none e
# SMASH_version

full_event_history.dat

#!ASCII full_event_history t pdg ID pdg_mother1 pdg_mother2
# Units: fm none none none none
# SMASH_version