---
title: "1D river simulations - files tab | Technical Reference"
slug: "files-tab"
description: "Learn about the files tab for 1D river simulations."
tags: ["1D river modelling", "viewing results"]
updated: 2022-08-05T07:56:47Z
published: 2022-08-05T07:56:47Z
canonical: "help.floodmodeller.com/files-tab"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.floodmodeller.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 1D river simulations - files tab

This tab contains the names of the main input and output files which are being used for the simulation. When a new 1D simulation file is created, the Data File field will be automatically populated with the name of the 1D model data file (.DAT) currently loaded in the Project Structure panel. A description of the fields available in the 1D Simulation File window are described below. An (O) indicates that the field is optional; an (M) indicates a mandatory field:

![RiverSimulationsimagesfilesimage44.gif](https://cdn.document360.io/5074bc26-a9ef-4bf4-b1de-a5c6ce628aca/Images/Documentation/RiverSimulationsimagesfilesimage44.gif)

<table>    <tbody>      <tr class="Head">        <th>          <p>Field</p>        </th>        <th>          <p>Description</p>      </th>      </tr>      <tr class="Odd">        <td>          <p>Event title (O)</p>        </td>        <td>          <p>A single line title used to describe the event/scenario. If used, this overrides the data file title in the results plots, etc</p>        </td>      </tr>      <tr>        <td>          <p>Description (O)</p>        </td>        <td>          <p>Additional lines of descriptive text. Purely for illustrative purposes, has no effect on the output files or postprocessors</p>        </td>      </tr>      <tr class="Odd">        <td>          <p>Data File (M)</p>        </td>        <td>          <p>Name of the main data file which is being used for the simulation</p>        </td>      </tr>      <tr>        <td>          <p>Default File Path (O)</p>        </td>        <td>          <p>Folder path for input/output files if not specified in the appropriate field</p>        </td>      </tr>      <tr class="Odd">        <td>          <p>Use Initial Conditions from...</p>        </td>        <td>          <p>Allows you to choose the source of your Initial Conditions, either from the <span style="font-weight: bold;  font-style: italic;">Network file</span> - this uses the initial conditions data embedded in your 1D network file (.dat file), or the<span style="font-weight: bold;  font-style: italic;"> Initial Conditions file</span> - this uses a separate, external text file, which defines the initial conditions for your network. This must be either a steady state output file (zzs) or a snapshot initial conditions file from a separate steady simulation (iic file - same format as a zzs file). &nbsp;</p>        </td>      </tr>      <tr>        <td>          <p>Initial Conditions File (O)</p>        </td>        <td>          <p>If <span style="font-weight: bold; font-style: italic;">Initial Conditions file</span><span class="menuitem">...</span> is selected above, the name and location of the Initial Conditions file (.zzs or .iic) must be specified.</p>          <p><span style="mso-add-space: auto; mso-list: l0 level2 lfo1;">This must be a either a steady state output file (zzs) or a snapshot initial conditions file from a separate steady simulation (iic file – same format as a zzs file). If this option is selected you must specify the external file you wish to utilise; either by dragging a file from the Initial Conditions section of your Project panel or by using the browse button provided.</span></p>        </td>      </tr>      <tr class="Odd">        <td>          <p>Results File (O)</p>        </td>        <td>          <p>This field must be populated with the desired results file name if this is to be different from that of the data file. Although the file extension specified here by default is .zzl, all other results files (*.zzd, *.zzn, *.zzs, etc.) will take the same name as the *.zzl file</p>        </td>      </tr>      <tr>        <td>          <p>Event Data (O)</p>        </td>        <td>          <p>This table allows event specific data to be entered separately from the main data file in up to ten event data files (*.ied) (see notes below). To add a new item, use the <span class="menuitem">Add</span> button on the right of the grid. To remove the currently selected item from the grid, or to move it up or down, use the Remove, arrow up or arrow down buttons respectively. A title may be added to each event data file in the grid for purely descriptive purposes</p>        </td>      </tr>    </tbody>  </table>


**Event Data**	  

You can use the same base data file for multiple simulations by using Event Data files (*.ied). The main features of Event Data files are that the results files may be given names independently of the data file, and that time-varying units (e.g. Flow-Time and Head-Time boundaries, Hydrological boundaries, Sluices, Gated Weirs, Abstractions, Pumps) may be replaced by 'Event Data Files', which contain data specific only to this unit and scenario.
Event Data Notes


 1. Event data files (*.ied) must be in the same format as Data files, although they do not require the General Systems Parameters or Initial Conditions data and only need to contain the event-specific units.

 2. Event data files only support units that are inherently time-dependent: QTBDY, HTBDY, QHBDY, All Hydrological Boundaries (FEHBDY, SCSBSY, FSSR16BDY), Vertical and Radial Sluices, Gated Weir, Pump, Abstraction, Breach.

 3. Event data files may contain just one unit per file, or multiple units can be lumped together within the same file, as long as they are one of the unit types listed above. Note that a maximum of 10 Event Data files may be used per simulation.

 4. Event data units must REPLACE a unit in the original data file, i.e. a unit of similar type with identical node label(s) must already exist in the data file. A QTBDY in the event data may replace a QTBDY or Hydrological boundary in the data file, for instance, but a Gated Weir may NOT replace an unsupported unit, such as a Sharp-Crested Weir.

 5. The easiest and safest way to create an Event Data file is to create or amend the required units in the main Flood Modeller interface, then highlight your desired units and use the File | Export | Partial function from the right mouse click menu.

 6. An information message is written near the top of the diagnostic file (*.zzd) when an event data file is being used.

 7. In the event of a read error in the event data file, the data from the data file will be used.