Development of ACCESS-ARGO

[navidcy]

Developing ACCESS-ARGO, the diagnostic tool that deploys synthetic ARGO floats into the ACCESS-OM2 model.

Or, the lesser version of it, that deploys synthetic ARGO floats into the existing model output that is currently available.

from @kialstewart

cc @ Annie Foppert, @ Helen Phillips, @ChrisC28 to whom it may be of interest?

(@ChrisC28 do you know the GitHub handles of Annie and Helen, if they have?)

[navidcy]

This project sounds a bit more technical as it probably involves creating a python library or adding functionality in the cosima-cookbook. But we can start with a jupyter notebook that will demonstrating the basic functionality of the synthetic ARGO floats.

[ChrisC28]

This would be extremely useful, but is not a trival task (particularly implementing the module within the model itself). Working with model output is probably a more do-able task - it would require modifying some Lagrangian particle tracking code to correctly take into account dive/resurface cycles, surface drift, etc...

[kialstewart]

Thanks Chris. The idea for this was rather than having a network of “active” passive Lagrangian floats being advected around in the model online (although this would be awesome by the way), we would just use the locations and times of the actual ARGO profile network to develop a database of synthetic hydrographic profiles. Comparing the known 4D “truth” model output with the fields that we can develop from the synthetic ARGO model output will help inform us how we can interpret the actual ARGO data. And deep ARGO. Using existing (daily?) model output could be ok, as a first go, by taking profiles at the closest grid point and time stamp. Running it online would be great though. Does this make sense? Kial

…

On Tue, 24 Jan 2023 at 09:53, Chris Chapman ***@***.***> wrote: This would be extremely useful, but is not a trival task (particularly implementing the module within the model itself). Working with model output is probably a more do-able task - it would require modifying some Lagrangian particle tracking code to correctly take into account dive/resurface cycles, surface drift, etc... — Reply to this email directly, view it on GitHub <#205 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSWJ3XKDAMZUP5BIRYYM4DWT4DX5ANCNFSM6AAAAAAUDTOYAQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ChrisC28]

OK, understood. I'm developing this with @Thomas-Moore-Creative as part of an internal CSIRO project. We are using the profiling float data from the World Ocean Database (which includes, but is not limited to, Argo).