Sign in to Drift Modelling

Orange Force Marine Ltd. · IAMSARSolutions

Version —

Use your assigned operational credentials to access the training suite. Standard session duration is 8 hours and can be adjusted by an administrator.

Please sign in to continue.
Message Console
Ready.

Drift Modelling Simulation Experience Suite v0.5.9DEVELOPMENT

Drift Parameters

Incident Details

Input field Calculated

All incident changes saved.

Required to save: Case Title and Scenario Name.

Quick details menu: Wizard opens the guided flow, Save stores updates, Load opens a saved incident, and Audit Log shows parameter change history.

Getting started:
  1. Enter a Case Title and Scenario Name in the fields below, then click Save.
  2. Click Wizard for guided step-by-step setup — it walks you through search object, last known position and time, environment (wind & current), leeway, and model generation.
  3. Or expand the Review Information section below and enter data directly using the Quick Entry, Worksheet Entry, SARMap Entry, or TSI Entry tabs — then click Validate / Generate Model when ready.
Incident: n/a
No objects selected
Scenario Notes

Review Information

Use one of the entry methods below to review and validate your drift parameters. Each tab provides a different view of the same underlying data — choose whichever approach best matches your workflow.

Generate Models to Calculate Datum

Select one or more drift models, verify your source data, then submit the run. Results will appear in Computed Results below. Use IAMSAR for manual planning or OpenDrift for probabilistic simulation.

Computed Results

View run history, model outputs, and computed datum positions. Compare results across runs, review diagnostics, and export data for search planning.

No timeline Object: n/a Distance: n/a
Style key: Center track = solid faded, Left divergence = dotted, Right divergence = dashed.

Trainer Class Management

Create and manage your classes, then add students to each class.

Classes

    Class

    Class Members

      Parameter Abbreviations

      Core SAR Terms

      • PIW — Person in Water
      • LKP — Last Known Position
      • EIP — Estimated Initial Position
      • PD — Probable Datum
      • DATUM — Most probable search position
      • TC — Tidal Current
      • SC — Sea Current
      • WC — Wind Current
      • OWC — Other Water Current
      • TWC — Total Water Current
      • LEEWAY — Wind-driven drift component
      • ZTA — Total Available Search Effort
      • Fs — Optimal Search Factor
      • SRU — Search and Rescue Unit
      • A/O — Area of uncertainty

      Error / Worksheet Terms

      • ASWe — ASW probable error
      • ASWDVe — ASW drift velocity error
      • TCe — Tidal current error
      • SCe — Sea current error
      • WCe — Wind current error
      • OWCe — Other water current error
      • TWCe — Total water current error
      • LWe / LWE — Leeway error
      • DVe — Drift velocity error
      • De — Drift error distance
      • E — Total probable error
      • — Squared total probable error
      • fW / fV / ff — Search effort correction factors
      • Wu — Corrected sweep width
      • Z — Search effort total
      • Zta — Total available effort over time

      OpenDrift / Particle Type Codes

      Official OpenDrift Leeway keys from OBJECTPROP.DAT are loaded into the Particle Type picker.

      • PIW-1 — Person in water (mean values)
      • LIFE-RAFT-NB-1 — Life-raft, no ballast (mean values)
      • LIFE-RAFT-DB-10 — Life-raft, deep ballast (mean values)
      • SKIFF-1 — Skiff / runabout powerboat
      • SAILBOAT-1 — Sailboat mono-hull (average)
      • FISHING-VESSEL-1 — Fishing vessel (mean values)

      About

      User
      CompanyOrange Force Marine Ltd. / IAMSARSolutions
      App Version
      Build Date/Time
      Environment
      LAN Address
      VPN Address
      External Address

      Total Available Search Effort (Zta) Data

      Sub-area SRU V (kts) On-scene Endurance (hrs) Daylight Remaining (hrs) T (hrs) Altitude Wu (NM) fw/ft fv ff W (NM) Z (NM²)

      Load Training Incident

      Run Log

      Select a run log to view details.
      No run log selected.

      Scenario Change Audit

      Select and load a training incident to view change history.
      No scenario audit entries recorded.

      Save Template

      Template ID: n/a
      Confirm template save details.

      User Usage Report

      No user usage data available.
      User Role Active Cumulative Hours Last Login

      Workflow Wizard

      Wizard toolbar: Previous/Next moves between steps, Go to Section scrolls the worksheet to the relevant fields, and Done closes while keeping progress.

      Follow the steps in order. Use Go to Section to jump to each relevant data area quickly. Press ← → arrow keys to navigate steps.

      Quick Start wizard tabs

        Step

        Select a step to continue.

        Leeway Search Objects

        Use sliders to set each object line opacity. Five levels are available: 0, 25, 50, 75, 100.

        Reference Image

        Reference image preview

        Drift Execution Routing Guide

        Each drift run is automatically routed to the fastest available backend based on the workload size. The table below shows the current thresholds. All conditions for a tier must be met; if any threshold is exceeded the next tier is used.

        🖥 Local API In-process, fastest cold-start
        ⚙️ Docker On-demand Linux container, interactive runs
        ☁️ AWS Batch Elastic cloud, very long runs

        Auto-routing thresholds

        Threshold Local API Docker AWS Batch
        Max concurrent runs
        Max particles
        Max duration
        Min time step
        Max particle-steps (particles × duration / timestep)

        Particle-steps is the single workload metric: particles × (duration_hours × 3600 ÷ time_step_seconds). A 500-particle, 6-hour run at 600 s timestep = 18 000 particle-steps — well within the local limit.

        Active backends

        Local API Always enabled
        Docker
        AWS Batch

        Fast-profile mode

        Tips

        Drift Deployment Guide

        Deploy with one public API container and choose where Docker worker containers run. This supports same-host operation now, optional remote worker host later, and AWS Batch as the third path.

        Recommended Topology

        1 Same Host API + Docker worker containers on one machine
        2 2nd EC2 Worker Host API points Docker runs to larger remote engine
        3 AWS Batch Elastic backend for large or queued runs

        Topology A: Same Host (local Windows Docker Desktop or single EC2)

        Topology B: Move Docker Worker to 2nd EC2 Later

        Topology C: AWS Batch as Third Option

        Live Deployment Status

        Docker Worker
        Docker Engine Target
        AWS Batch