jmaerz

@TomasTorsvik , I suspect this is partially linked to https://github.com/NorESMhub/BLOM/pull/567 - see my comment there on the BLOM isopycnic coordinates and their settings.

Dear @gold2718 and @TomasTorsvik , just in case: I can tag the 99db47ff... M4AGO commit, so that it becomes easier to handle this, if needed (and/or update the commit in...

Hi @TomasTorsvik , I just pushed tag [dev-1.0.1](https://github.com/jmaerz/M4AGO-sinking-scheme/releases/tag/dev-1.0.1) which is equivalent to sha `99db47ff632`, so you can change the `BLOM_externals.cfg` file for the new tag - which hopefully resolves the...

I wasn't part of the discussion, but maybe an approach for the meantime could be to set up a common git repo elsewhere (e.g. internal gitlab or just nird/betzy, controlled...

To add on @JorgSchwinger : if I am not mistaken (I can ask Reinhard Budich, if that helps), MPIOM/HAMOCC has been recently put under BSD-3C license - which is even...

Hi @YanchunHe , I lately ran a couple of times into issues (with `master`) - for reasons of units, wrong parameter values (for the units and coordinate system used) -...

@TomasTorsvik , can we rule out via the regression testing that DMS fluxes have been deteriorated (as in: are the fluxes tested by default in the regression testing)? (I am...

Maybe worth to mention that the DMS flux issue that Dirk mentioned seem not to appear when using the current `master` of BLOM (I recently was using Dirks setup and...

@YanchunHe , yes, 2.3 should be isopycnical. You can try: ``` /xmlquery BLOM_VCOORD ``` in your case setup, which should result in: ``` BLOM_VCOORD: isopyc_bulkml ``` (otherwise you can set...

Just as a brief comment: since the BLOM code development has moved/is moving fast, it would be at least good to refer to a certain git-sha (and/or tag) in the...