From the eagle-eyed @jonseddon 🦅 👁 :

"I just noticed that the text inside the HTML <title> tag for the Iris 2.4 documentation at https://scitools.org.uk/iris/docs/v2.4.0/gallery.html says “Thumbnail gallery — Iris 2.2.0 documentation” rather than 2.4. It’s correct in the equivalent page in the version 2.3 documentation. I’ve not done an extensive search of all pages, but it looks like the

Dear colleagues,

Since data and meta data fetchers are on track (eg: euroargodev/argopy#6, euroargodev/argopy#5), we very soon gonna need an API for visualization and plotting of fetched Argo information.

This issue is meant to design that API.
If you want to contribute or shoot some ideas or requests please reply below.
Be specific about th

The integrated summer insolation should be integrated from 152 day to 243 day (June to August), not select 'Fsw(Few<275)=0'. If I am right, please revise it.

Over in ECCO-GROUP/ECCOv4-py#6, @ifenty reported some difficulty in using open_mdsdataset to read data from ECCO. Some if this is likely due to our lousy error messages (see #126), but it's also likely related to overall deficiencies in our documentation.

This is what I wrote in that thread.

I think a big source of confusion is that the user-facing part of xmitgcm is designed not to read j

@asiddi24 @ThomasHaine
These are the test functions I'm using to check heat and salt budgets:
https://github.com/malmans2/oceanspy/blob/959a2488519008f50804325a0a69925304217fdf/oceanspy/test

The calculation layer makes the use of the scale_factor attribute in the datasetconfig.json redundant, since an equation can easily replicate the functionality:
scale_factor: 1.2 can be replaced by
equation: "my_variable * 1.2", dims: [dims...].

The only work needed is editing the config file. The calculation layer handles the rest automatically.

The other (optional but strongly

The 2D Parameter-Parameter plots are currently generated by server-side matplotlib. This is acceptable for order of a thousands data points. We now have Campaigns with many millions of points that we would like to explore with web-interactive speeds. For example, a nearly 2 million point Parameter-Parameter takes nearly 5 minutes to render: a [Share this view link](https://stoqs.shore.mbari.org/st

I read from the paper that the degree of advection constrain can be varied using a parameter but I couldn't find how to specifiy/tune this parameter in the documentation/examples. DIVAndrun accepts a velocity argument but not a parameter for this constrain.

@kwilcox asked me to let him know where documentation would be helpful. If it's OK, I'd like to track it here.

First up, Installation. For instance, I did:

conda create -n pyocean pip
source activate pyocean
git clone https://github.com/pyoceans/pocean-core
cd pocean-core
conda install --file requirements.txt -c conda-forge
pip install -e ~/Desktop/code/pocean-core