Overview
This app helps the crew track streamer cleaning work by project. You can set up a project,
define streamer parameters, record cleaning events, and review results in the statistics and planning pages.
Main page
Use it to select a cleaning method, mark cleaned sections on the heatmap, add manual events, and review the log.
Config page
Use it to create projects, set the active project, define streamer parameters, and save deployment details.
Statistics page
Use it to review coverage, cleaned distance, event counts, and project trends.
Planning page
Use it to see which sections have gone the longest without cleaning and plan the next work.
Create a Project
Go to Config, then use Create New Project. New projects inherit the current configuration,
so it is a good idea to review the parameters first.
Project Number
Main identifier for the job, for example a survey or campaign reference.
Project Name
Optional plain-language label that makes the project easier to recognize.
Vessel Tag
Vessel code the project belongs to, such as `TTN`.
After creating the project, select it and click Set as Active so the app loads that project's settings.
Define Streamer Parameters
These settings describe how the streamer spread is arranged for the active project.
Number of Streamers
Total streamers in the spread for this project.
Active Sections per Streamer
Default number of active sections for every streamer in the spread. Use this when all streamers have the same length.
Section Length (m)
Physical length of one section. This is used when the app calculates cleaned distance.
eBird Frequency
How often equipment box positions repeat along the streamer.
Channels per Section
Number of channels contained in each section.
Tail Configuration
Choose whether the tail uses rope only or includes 5 extra tail sections.
Save the configuration after changes. The active project uses its own saved parameters.
If one or more streamers are shorter or longer than the rest, set Active Sections per Streamer to the value used by most streamers, then override individual lengths in Per-Streamer Deployment Configuration (see below).
Configure Streamers
In the active project, use Per-Streamer Deployment Configuration to define deployment details for each streamer.
Deployment date
Records when a streamer was deployed for the project.
Coating status
Mark each streamer as coated, uncoated, or unknown.
Sections override
Optional active section count for this streamer only. Leave empty to use the project default from Active Sections per Streamer, or enter a value when this streamer differs from the others (if you have a configuration where any streamer has more sections than others).
The heatmap, planning view, and statistics use each streamer's effective section count. Streamers with fewer sections show inactive (grey) cells beyond their length; longer streamers can have more active cells than shorter ones in the same spread.
You can use the bulk actions to set the same date or coating status for all streamers. Set Sections override per streamer as needed, then click Save Streamer Configurations.
Use the Main Page
Choose the method
Select Rope, Scraper, Scraper&Rope, SCUE, or Knife before recording work. Your last selected method is remembered on this device and pre-selected on the next visit.
Mark cleaned sections
Click and drag across active cells in the heatmap to record a cleaned range.
Add manual events
Use the manual entry form when you need to enter a cleaning event directly.
Review the log
Check the history table to confirm the event was saved and sorted correctly.
If the wrong project is active, change it in Config before recording new work.
Use Stats and Planning
Statistics
Best for checking coverage, total cleaned distance, number of events, and filtered project results.
Planning
Best for deciding what to clean next by looking at days since last scraping and suggested ranges.
Upload RMS noise CSV files here to overlay noise levels on the heatmap and rank suggestions by noise.
RMS Noise File Upload
RMS noise files are CSV exports of per-section noise measurements from the current acquisition sequence.
Uploading them lets the app show where noise is highest, compare noise before and after cleaning work,
and include a noise heatmap in PDF reports. RMS data is stored per project — each upload becomes a dated
snapshot you can switch between later.
Upload a file
- Open the Planning page and select the project the noise file belongs to.
- Click Upload noise CSV (Administrators and above).
- Choose the RMS CSV file from your survey system. The app validates the file before saving it.
- Optionally enter water speed at the start and end of the line, then confirm the upload.
The upload label defaults to the file name. Administrators can later edit the label and water speed
values, or delete an upload, using the controls next to the upload selector.
Expected CSV format
First column
Active section number, starting at 1 (one row per section). Tail sections are not included in RMS files.
Remaining columns
One column per streamer, typically labelled like Active, Cable 01,
Cable 02, and so on — matching the project's streamer count.
Cell values
RMS noise in µBar for that section on that streamer. Zero or blank means there is no data for this section and is ignored.
Must match project config
The number of streamer columns and section rows must match the active project's
Number of Streamers and Active Sections per Streamer settings
(including any per-streamer section overrides). Fix the project configuration first if validation fails.
How RMS data is used across the app
Planning — noise overlay
Turn on Noise overlay on the planning heatmap to replace days-since-cleaning colours
with an RMS gradient (low noise in blue, high noise in red). Each cell shows the RMS value.
Use the upload dropdown to compare different acquisition snapshots. Legend thresholds can be adjusted
on the page.
Planning — cleaning suggestions
When an RMS upload is loaded, the suggestions table adds an Avg Noise (RMS) column
for each suggested range. Sort by this column to prioritise high-noise sections that also need cleaning.
Planning — section tooltips
Hover over a section on the planning heatmap to see its RMS value alongside days since last scraping
and other deployment details.
Statistics — cleaning noise efficiency
On the Statistics page, the Cleaning Noise Efficiency section compares two RMS uploads
(an earlier Before snapshot and a later After snapshot) against
cleaning events in a chosen time window. It shows how much noise changed on sections that were cleaned
between those acquisitions — useful for judging whether recent scraping work reduced noise.
PDF reports
When generating a PDF from the main page or Statistics page, check Include noise heatmap
to add a dedicated RMS heatmap page. You can pick a specific upload or use the latest one for the project.
ℹ️
Upload at least two RMS snapshots over time to use the cleaning noise efficiency KPI meaningfully.
A single upload is enough for the planning overlay, suggestions column, and PDF noise heatmap.
Tips
ℹ️
Always activate the correct project before entering events. Project-specific configuration, deployments,
and planning data depend on the active project.
If you create a new project, save its configuration first, then start logging cleaning events.