When a cast is requested, the system looks up the closest depth entry for the active profiler and scales that entry's cast time proportionally to the new depth:
cast time = closest entry's cast time × (requested depth ÷ closest entry's depth)
Example: you have a 50 m entry with a cast time of 66 s and a cast is requested to 80 m:
cast time = 66 × (80 ÷ 50) = 105.6 s
What this means in practice:
- Spread entries across the depths you cast to. An entry at 50 m predicts nearby depths well, but extrapolating to 500 m from a single shallow entry will be less accurate. Aim for entries at depths that bracket your typical survey range.
- One entry set per profiler type. SWIFTSVP and RAPIDSVP entries are kept completely separate — make sure the profiler type you select here matches the one configured in the system.
- Cast time is the key value. This is what the server scales for future casts. Enter the depth and either the cast time or the drop rate — the editor will compute whichever you leave blank.
- No entries needed for basic operation. With an empty table the system falls back to the nominal drop rate. Use this editor to pre-populate calibration data before a deployment, or to carry learned timing forward from a previous survey.
- When two entries are equally close to the requested depth, the most recent one (highest cast number) wins.