At sea — ship-time is how most WII deployments happen.
Three streams:
This is the multi-page printable view of this section. Click here to print.
Deployment stories and project history.
Eleven-buoy deployment with the Korea Polar Research Institute starting
1 March 2024 (project id kopri). Details, ship, location, retrievals,
and photos to follow.
Two-buoy deployment in Canadian waters starting 1 December 2019 and
running through 2021 (project id twk5). Details, ship, location,
retrievals, and photos to follow.
Fourteen-buoy deployment running through Tasmanian waters from 1 July
2019 through 2022 (project id tas2019). One of the longest-running WII5
projects to date. Details, ship, location, retrievals, and photos to follow.
Single-buoy deployment with the University of Melbourne starting
1 November 2018 (project id unimelb2018). Details, ship, location,
retrievals, and photos to follow.
Three-buoy deployment in Japan starting 26 March 2018 (project id
japan2018). Details, ship, location, retrievals, and photos to follow.
Fourteen-buoy deployment with NIWA (New Zealand’s National Institute
of Water and Atmospheric Research) starting 1 April 2017 (project id
niwa2017).
This was the Intel Edison all-in-one Linux generation: the buoy ran everything — sensor capture, GPS, Iridium, scheduling — on a single Edison module running Linux. No AVR companion CPU. The Edison was chosen for its small form factor and reasonable power profile at the time; it later became the limiting factor (Intel discontinued the Edison line) and prompted the move back to AVR for WII5.
The dashboard, capture pipeline, and watchdog management for this build are documented under Software → Other → WII3_Dashboard.
Details, ship, location, and retrievals to follow.
Two-buoy deployment with NYU UAE (New York University Abu Dhabi)
starting 1 April 2017 (project id nyuuae). Details, ship, location,
retrievals, and photos to follow.
Two-buoy deployment in Japan starting 9 September 2016 (project id
japan2016). Details, ship, location, retrievals, and photos to follow.
Internal NIWA test deployment (project id niwatest2016). Zero buoys
recorded — appears to be a system test rather than a real deployment.
The dashboard records a deployment date of
13/05/2026, which looks like a placeholder default rather than a real date. Verify and correct when the deployment story is written up.
Internal test deployment (project id test2016), two buoys. Not a
real-world deployment — used for testing the server and dashboards.
The dashboard records a deployment date of
13/05/2026, which looks like a placeholder default rather than a real date.
NIWA-led field testing of the WII2 sensor board at Scott Base, Antarctica — November 2014. The trip exercised the second-generation buoy hardware end-to-end before any open-water deployment.
Hardware under test:
The WII2 firmware tree that drove this trial is documented under Software → Other → WII2_Board. The campaign sat between WII1 (the original 2012 buoy) and the WII3 generation that followed.
The seminal NIWA deployment: eight WII buoys sent into the Antarctic sea ice in 2012, collecting the first digital sea-ice wave-motion measurements ever made. The data they returned became the basis for the project’s headline publication two years later:
Kohout A. L., Williams M., Dean S., et al. (2014). Storm-induced sea-ice breakup and the implications for ice extent. Nature, 509, 604–607.
This was the work that established empirically — not just modelled — that ocean waves drive sea-ice breakup in the marginal ice zone, with direct implications for the rate and timing of Antarctic ice-edge retreat.
Every WII generation since has been an iteration on the platform first proved by these eight buoys.
Version drops and what’s in each.
Announcements and updates.
May 2026. This site goes live today, and with it the first open-source release of WII5 source material.
What’s public from launch:
The rest of the WII repository family — earlier dashboards, servers, maths tooling, test rigs, data archives — is inventoried at Software → Other and is possibly available on request. None of it has been individually assessed for release yet (licensing, customer-specific identifiers, third-party dependencies all need looking at first). If something there sounds useful, ask and we’ll review it.
The reasoning behind the release is on the Why page: continuity, auditability, due diligence, and as a way to make the work discoverable. It’s a starting point, not a finished product — feedback welcome.
— Scott Penrose (contact)