Interface and Navigation
This page walks you through the Event Builder Table in three phases: loading a database source, adding and editing event rows, and saving the finished event file. Each phase below is one tab of the walkthrough.
- Phase 1: Load your database and pick a source
- Phase 2: Add and edit event rows
- Phase 3: Save your event file
Confirm the catalog is loaded, then optionally seed rows from an event file that already lives in the working environment.
Database Status
Confirm your database is loaded before doing anything else. The
Database: label at the top of the Event Builder shows the basename
of the catalog currently loaded; if it reads No database loaded,
no dropdowns will populate. While the catalog is being read the label
reads Loading catalog….
Use ↻ Reload to re-read the catalog from disk after switching working environments or after another tool updates it. Reload is disabled while the catalog is loading and while no database is configured. If the reload surfaces problems — a missing file, a parse error, or a warning about unknown regions — a brief banner appears beneath the row.
Seed rows from an existing event file
To pre-populate rows from a file that already lives in DirEvt, pick it from Load from existing: and press + Add.
- Picker placeholder
— pick a source to add —; dropdown. Ev*.csvfiles in DirEvt are shown as options.- Dedup rule: byte-identical incoming rows REPLACE the existing copy (keep-last); rows that differ in any field are all kept.
- ↻ Refresh list re-scans DirEvt without leaving the tab.
- Each added source appears below the picker, showing its name, a loading indicator while reading, a warning icon if there are problems, and a × button to remove it.
- The chip's
×retracts the rows that source contributed unless another added source contributes the same row or you have edited the row since it was loaded.
With the table primed you can move on to Phase 2 to edit rows.
Write the finished event file into the working environment's event directory.
Save the event file
Type a base name into the Output file input (placeholder name)
and press Save Event File. The editor writes Ev_<name>.csv into
the working environment's event directory (DirEvt).
- When one or more rows fail validation, a blocking-summary strip
appears between the toolbar and the table. It reads
{N} row(s) need attentionand carries a Show details disclosure that lists per-row reasons inRow {N}: {reason}; {reason}form. Save Event File stays disabled until every row is valid. - If a file with the composed name already exists in DirEvt, an
overwrite-confirmation banner appears asking
**{filename}** already exists in DirEvt. Overwrite this event file?, with a red Overwrite button and a Cancel button.
Parse warnings raised while loading a source and other cross-cutting messages surface through the Suite's shared notification pop-up rather than a dedicated Event Builder panel.