Skip to content

Add BGC sensors to Argo Floats - #414

Merged
j-atkins merged 9 commits into
mainfrom
bgc-argos
Oct 21, 2026
Merged

j-atkins merged 9 commits into
mainfrom
bgc-argos

Conversation

@j-atkins

Copy link
Copy Markdown
Collaborator

This PR adds biogeochemical variables to the Argo Float instrument, by adding them as available sensors to the instrument.

The only BGC variables which are added to Argo floats are those that are both used on real-life BGC-Argo floats and are available from Copernicus. That means oxygen, chlorophyll, nitrate and pH. A BGC CTD for example has a wider range of sensors but restricting it on the Argo floats is more realistic.

Note also that the BGC sensors are off by default in an expedition. Adding additional fields adds more expense to the Argo float simulations, which are already quite intensive, so I see it as a trade off between having them available to users should they want them but not encouraging everyone use them if they don't need them.

On a related note, there are changes to the virtualship plan tool which means the BGC sensors appear as options in the instrument config sections but are default off. Previously all instruments sensors were on by default so it wasn't a concern that they wouldn't show as options in the plan tool. The docs now also have updates to explain that the BGC sensors are available for Argo floats but off by default.


  • Docs updated
  • Tests updated/added

Closes #234

@erikvansebille erikvansebille left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good - one very small comment (and a reflection) below

| **XBT** | TEMPERATURE | Sea Water Potential Temperature | °C | Physical |

```{note}
The `ARGO_FLOAT` BGC sensors (oxygen, chlorophyll, nitrate, ph) are off by default. Each extra sensor adds another variable for the simulation to load and sample, which can make the already-expensive Argo float simulations more intensive. When needed though, they can be turned on in the `virtualship plan` tool or by adding them to the `sensors` list of `argo_float_config` in `expedition.yaml`.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mixing the words "expensive" and "intensive" may be confusing. Reword?

# =====================================================


def _sample_on_ascent(particles, field, var):

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice improvement to make this its own function! Shows the flexibility of Parcels v4 ;-)

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes this is a really nice feature of v4!

@j-atkins
j-atkins merged commit d62130c into main Oct 21, 2026
12 checks passed
@j-atkins
j-atkins deleted the bgc-argos branch October 21, 2026 10:04
@j-atkins j-atkins mentioned this pull request Oct 21, 2026
2 tasks done
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

New ARGO_BGC instrument

2 participants