<commit_before>\chapter{Data Structure of the Data Files} \label{Header}

A common data structure for the programs MAD-X and SixTrack is agreed on.
Besides some minor differences this allows a straightforward post-processing of data from either program.
Each binary data file has a header which holds a description of the run with comments, tracking parameters and 50 additional parameters for future purposes, six of which are already specified in SixTrack.

\begin{table}[h]
    \caption{Header of the Binary Data Files}
    \label{T-HDF}
    \centering
    \begin{tabular}{|c|c|>{\raggedright\arraybackslash}p{8cm}|}
        \hline
        \rowcolor{blue!30}
        \textbf{Data Type} & \textbf{Bytes} & \textbf{Description} \\
        \hline
        Character & 80 & General title of the run \\
        \hline
        Character & 80 & Additional title \\
        \hline
        Character & 8 & Date \\
        \hline
        Character & 8 & Time \\
        \hline
        Character & 8 & Program name \\
        \hline
        Integer & 4 & First particle in the file \\<commit_msg>Mention the change and the tool in the manual.<commit_after>\chapter{Data Structure of the Data Files} \label{Header}

A common data structure for the programs MAD-X and SixTrack is agreed on\footnote{
Historically, SixTrack wrote one such file per particle pair (files \texttt{fort.90}, \texttt{fort.89}, \ldots), however recent versions of SixTrack always produce a single \texttt{singletrackfile.dat} containing all the data, by interleaving the contents of the old files in one large file as discussed below.
Files of the old (MAD-X and Sussix compatible) format can be generated from this new format by running the tool \texttt{splitSingletrack} in the folder containing the \texttt{singletrackfile.dat}.
This splits the combined \texttt{singletrackfile.dat} into one file for each pair.

This chapter describes the old format used for single particle pairs, followed by a description of the built-in postprocessing tool output.}.
Besides some minor differences this allows a straightforward post-processing of data from either program.
Each binary data file has a header which holds a description of the run with comments, tracking parameters and 50 additional parameters for future purposes, six of which are already specified in SixTrack.

\begin{table}[h]
    \caption{Header of the Binary Data Files}
    \label{T-HDF}
    \centering
    \begin{tabular}{|c|c|>{\raggedright\arraybackslash}p{8cm}|}
        \hline
        \rowcolor{blue!30}
        \textbf{Data Type} & \textbf{Bytes} & \textbf{Description} \\
        \hline
        Character & 80 & General title of the run \\
        \hline
        Character & 80 & Additional title \\
        \hline
        Character & 8 & Date \\
        \hline
        Character & 8 & Time \\
        \hline
        Character & 8 & Program name \\
        \hline
        Integer & 4 & First particle in the file \\
{'fraction_non_alphanumeric': 0.07796610169491526, 'fraction_numerical': 0.010169491525423728, 'mean_word_length': 2.8777923784494086, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5199342', 'n_tokens_mistral': 777, 'n_tokens_neox': 742, 'n_words': 343}