Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remapped overturning into depth space, masked the mediteranean in mom5 #284

Merged
merged 8 commits into from
Oct 25, 2023

Conversation

willaguiar
Copy link
Collaborator

@willaguiar willaguiar commented Sep 4, 2023

Closes #274

@review-notebook-app
Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@navidcy
Copy link
Collaborator

navidcy commented Sep 4, 2023

oftentimes people say "dask gives problems" and the respond is "give us an example that does not work".

Well, here's an example that we get a lot of struggles. When I try to run this notebook to review the PR I get a bunch of

2023-09-04 20:11:46,126 - distributed.utils_perf - WARNING - full garbage collections took 13% CPU time recently (threshold: 10%)
2023-09-04 20:14:38,890 - distributed.utils_perf - WARNING - full garbage collections took 10% CPU time recently (threshold: 10%)
2023-09-04 20:14:53,643 - distributed.utils_perf - WARNING - full garbage collections took 11% CPU time recently (threshold: 10%)
2023-09-04 20:15:10,090 - distributed.utils_perf - WARNING - full garbage collections took 12% CPU time recently (threshold: 10%)
2023-09-04 20:15:10,243 - distributed.utils_perf - WARNING - full garbage collections took 11% CPU time recently (threshold: 10%)
2023-09-04 20:15:16,134 - distributed.utils_perf - WARNING - full garbage collections took 10% CPU time recently (threshold: 10%)
2023-09-04 20:15:17,872 - distributed.utils_perf - WARNING - full garbage collections took 10% CPU time recently (threshold: 10%)
2023-09-04 20:15:28,173 - distributed.utils_perf - WARNING - full garbage collections took 14% CPU time recently (threshold: 10%)
2023-09-04 20:15:29,787 - distributed.utils_perf - WARNING - full garbage collections took 12% CPU time recently (threshold: 10%)
2023-09-04 20:15:30,983 - distributed.utils_perf - WARNING - full garbage collections took 10% CPU time recently (threshold: 10%)
2023-09-04 20:15:33,889 - distributed.utils_perf - WARNING - full garbage collections took 10% CPU time recently (threshold: 10%)
2023-09-04 20:15:45,577 - distributed.utils_perf - WARNING - full garbage collections took 10% CPU time recently (threshold: 10%)
2023-09-04 20:15:45,903 - distributed.utils_perf - WARNING - full garbage collections took 15% CPU time recently (threshold: 10%)
2023-09-04 20:15:48,333 - distributed.utils_perf - WARNING - full garbage collections took 13% CPU time recently (threshold: 10%)
2023-09-04 20:15:48,916 - distributed.utils_perf - WARNING - full garbage collections took 11% CPU time recently (threshold: 10%)
2023-09-04 20:15:50,338 - distributed.utils_perf - WARNING - full garbage collections took 11% CPU time recently (threshold: 10%)
2023-09-04 20:15:53,357 - distributed.utils_perf - WARNING - full garbage collections took 10% CPU time recently (threshold: 10%)
2023-09-04 20:16:01,402 - distributed.utils_perf - WARNING - full garbage collections took 11% CPU time recently (threshold: 10%)
2023-09-04 20:16:03,721 - distributed.utils_perf - WARNING - full garbage collections took 16% CPU time recently (threshold: 10%)
2023-09-04 20:16:05,052 - distributed.utils_perf - WARNING - full garbage collections took 12% CPU time recently (threshold: 10%)
2023-09-04 20:16:05,388 - distributed.utils_perf - WARNING - full garbage collections took 12% CPU time recently (threshold: 10%)
2023-09-04 20:16:08,567 - distributed.utils_perf - WARNING - full garbage collections took 14% CPU time recently (threshold: 10%)
2023-09-04 20:16:10,557 - distributed.utils_perf - WARNING - full garbage collections took 11% CPU time recently (threshold: 10%)
2023-09-04 20:16:10,627 - distributed.utils_perf - WARNING - full garbage collections took 10% CPU time recently (threshold: 10%)
2023-09-04 20:16:20,151 - distributed.utils_perf - WARNING - full garbage collections took 11% CPU time recently (threshold: 10%)
2023-09-04 20:16:24,950 - distributed.utils_perf - WARNING - full garbage collections took 12% CPU time recently (threshold: 10%)
2023-09-04 20:16:25,058 - distributed.utils_perf - WARNING - full garbage collections took 17% CPU time recently (threshold: 10%)
2023-09-04 20:16:27,788 - distributed.utils_perf - WARNING - full garbage collections took 12% CPU time recently (threshold: 10%)
2023-09-04 20:16:29,696 - distributed.utils_perf - WARNING - full garbage collections took 10% CPU time recently (threshold: 10%)
2023-09-04 20:16:30,694 - distributed.utils_perf - WARNING - full garbage collections took 12% CPU time recently (threshold: 10%)
2023-09-04 20:16:34,041 - distributed.utils_perf - WARNING - full garbage collections took 14% CPU time recently (threshold: 10%)
2023-09-04 20:16:44,566 - distributed.utils_perf - WARNING - full garbage collections took 14% CPU time recently (threshold: 10%)
2023-09-04 20:16:45,109 - distributed.utils_perf - WARNING - full garbage collections took 11% CPU time recently (threshold: 10%)
2023-09-04 20:16:45,226 - distributed.utils_perf - WARNING - full garbage collections took 19% CPU time recently (threshold: 10%)
2023-09-04 20:16:48,488 - distributed.utils_perf - WARNING - full garbage collections took 10% CPU time recently (threshold: 10%)
2023-09-04 20:16:48,931 - distributed.utils_perf - WARNING - full garbage collections took 13% CPU time recently (threshold: 10%)
2023-09-04 20:16:50,947 - distributed.utils_perf - WARNING - full garbage collections took 13% CPU time recently (threshold: 10%)
2023-09-04 20:17:05,183 - distributed.utils_perf - WARNING - full garbage collections took 11% CPU time recently (threshold: 10%)
2023-09-04 20:17:05,185 - distributed.utils_perf - WARNING - full garbage collections took 14% CPU time recently (threshold: 10%)
2023-09-04 20:17:05,886 - distributed.utils_perf - WARNING - full garbage collections took 14% CPU time recently (threshold: 10%)
2023-09-04 20:17:06,270 - distributed.utils_perf - WARNING - full garbage collections took 11% CPU time recently (threshold: 10%)
2023-09-04 20:17:07,718 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.20 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:08,282 - distributed.utils_perf - WARNING - full garbage collections took 19% CPU time recently (threshold: 10%)
2023-09-04 20:17:10,451 - distributed.utils_perf - WARNING - full garbage collections took 14% CPU time recently (threshold: 10%)
2023-09-04 20:17:11,270 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.12 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:11,879 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.10 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:12,674 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.17 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:12,988 - distributed.utils_perf - WARNING - full garbage collections took 14% CPU time recently (threshold: 10%)
2023-09-04 20:17:13,809 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.19 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:17,828 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.72 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:21,280 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.49 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:22,728 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.71 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:27,420 - distributed.utils_perf - WARNING - full garbage collections took 14% CPU time recently (threshold: 10%)
2023-09-04 20:17:27,561 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.38 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:27,688 - distributed.utils_perf - WARNING - full garbage collections took 11% CPU time recently (threshold: 10%)
2023-09-04 20:17:27,824 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.50 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:29,233 - distributed.utils_perf - WARNING - full garbage collections took 11% CPU time recently (threshold: 10%)
2023-09-04 20:17:29,367 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.79 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:30,134 - distributed.utils_perf - WARNING - full garbage collections took 19% CPU time recently (threshold: 10%)
2023-09-04 20:17:34,268 - distributed.utils_perf - WARNING - full garbage collections took 15% CPU time recently (threshold: 10%)
2023-09-04 20:17:35,474 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.20 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:36,760 - distributed.utils_perf - WARNING - full garbage collections took 14% CPU time recently (threshold: 10%)
2023-09-04 20:17:36,847 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.58 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:37,580 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.81 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:37,996 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.96 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:38,414 - distributed.utils_perf - WARNING - full garbage collections took 16% CPU time recently (threshold: 10%)
2023-09-04 20:17:38,481 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.84 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:38,611 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.11 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:39,384 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 12.24 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:46,917 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 12.02 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:48,666 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 12.40 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:54,452 - distributed.utils_perf - WARNING - full garbage collections took 19% CPU time recently (threshold: 10%)
2023-09-04 20:17:54,602 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.63 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:54,942 - distributed.utils_perf - WARNING - full garbage collections took 16% CPU time recently (threshold: 10%)
2023-09-04 20:17:55,110 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 12.26 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:55,307 - distributed.utils_perf - WARNING - full garbage collections took 12% CPU time recently (threshold: 10%)
2023-09-04 20:17:55,338 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 12.33 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:57,089 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 12.31 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:58,739 - distributed.utils_perf - WARNING - full garbage collections took 17% CPU time recently (threshold: 10%)
2023-09-04 20:17:58,868 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.58 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:17:58,980 - distributed.utils_perf - WARNING - full garbage collections took 13% CPU time recently (threshold: 10%)
2023-09-04 20:17:59,063 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 12.59 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:18:04,795 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 12.08 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:18:05,403 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 12.66 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:18:05,434 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 12.67 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:18:08,951 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 11.89 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:18:10,830 - distributed.utils_perf - WARNING - full garbage collections took 17% CPU time recently (threshold: 10%)
2023-09-04 20:18:10,831 - distributed.worker.memory - WARNING - gc.collect() took 13.085s. This is usually a sign that some tasks handle too many Python objects at the same time. Rechunking the work into smaller tasks might help.
2023-09-04 20:18:10,831 - distributed.worker.memory - WARNING - Worker is at 80% memory usage. Pausing worker.  Process memory: 12.82 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:18:10,990 - distributed.utils_perf - WARNING - full garbage collections took 14% CPU time recently (threshold: 10%)
2023-09-04 20:18:11,133 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 12.40 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:18:13,757 - distributed.utils_perf - WARNING - full garbage collections took 14% CPU time recently (threshold: 10%)
2023-09-04 20:18:13,758 - distributed.worker.memory - WARNING - gc.collect() took 9.106s. This is usually a sign that some tasks handle too many Python objects at the same time. Rechunking the work into smaller tasks might help.
2023-09-04 20:18:13,758 - distributed.worker.memory - WARNING - Worker is at 80% memory usage. Pausing worker.  Process memory: 12.80 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:18:13,791 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 12.80 GiB -- Worker memory limit: 16.00 GiB
2023-09-04 20:18:15,382 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 12.26 GiB -- Worker memory limit: 16.00 GiB

and more.

Do we have any suggestions for how can we this example run smoother?

Perhaps an overambitious is to be able to run the same with 0.1 degree model output... (but that's beyond imagination atm)

cc @aidanheerdegen, @angus-g, @dougiesquire, @micaeljtoliveira

@dougiesquire
Copy link
Collaborator

One issue here is that more attention needs to be paid to the chunking of some of the data being used. E.g., adding the following to the "mom5" key in psi_args means the first few cells complete more efficiently and without warnings:

"chunks": {
    "time": 1,
    "potrho": -1,
    "grid_yu_ocean": 270,
    "grid_xt_ocean": -1,
 }

This may still not be the best chunking for the subsequent calculations, but before getting to that I'm curious why the density remapping doesn't use xgcm?

@navidcy
Copy link
Collaborator

navidcy commented Sep 6, 2023

This may still not be the best chunking for the subsequent calculations, but before getting to that I'm curious why the density remapping doesn't use xgcm?

I don't think there is a particular reason we didn't use xgcm but @AndyHoggANU or @adele-morrison may have a more definite opinion?

@navidcy
Copy link
Collaborator

navidcy commented Sep 29, 2023

@willaguiar could you try @dougiesquire's suggestion here and rerun all cells?

@willaguiar
Copy link
Collaborator Author

One issue here is that more attention needs to be paid to the chunking of some of the data being used. E.g., adding the following to the "mom5" key in psi_args means the first few cells complete more efficiently and without warnings:

"chunks": {
    "time": 1,
    "potrho": -1,
    "grid_yu_ocean": 270,
    "grid_xt_ocean": -1,
 }

This seems to have corrected the Dask warnings ( thanks @dougiesquire ). Could you explain in a little more detail why? ( so I keep in mind for future codes).

PS:I added a new edit to the code on the mom6 remapping function. Before, I was manually setting the southernmost cutout latitude for the remapping (78S index nmin), but the index I set before would only work on panan-01. Now I changed so the cutout (78S) latitude is automatically identified in each model.

@review-notebook-app
Copy link

review-notebook-app bot commented Oct 4, 2023

View / edit / reply to this conversation on ReviewNB

navidcy commented on 2023-10-04T12:30:31Z
----------------------------------------------------------------

Will could you add spaces after commas here?

Also, isn't there an xarray-way to do this?

    for ii in range(nmin,nmax):
        if model=='mom5':
            rho1 = rho2_zonal_mean.isel(yt_ocean=ii).values
            f = interp1d(rho1,z1,bounds_error=False,fill_value = (0,'NaN'))
            psi_depth[:,ii] = np.nan_to_num(f(psi_avg.potrho.values),nan=6000)
        elif model=='mom6':
            rho1 = rho2_zonal_mean.isel(yh=ii).values
            f = interp1d(rho1,z1,bounds_error=False,fill_value = (0,'NaN'))
            psi_depth[:,ii] = np.nan_to_num(f(psi_avg.rho2_l.values),nan=6000)

willaguiar commented on 2023-10-13T01:39:30Z
----------------------------------------------------------------

I altered the code to use xarray.interp. Might be a little prolix, so any suggestions are welcome

@review-notebook-app
Copy link

review-notebook-app bot commented Oct 4, 2023

View / edit / reply to this conversation on ReviewNB

navidcy commented on 2023-10-04T12:30:34Z
----------------------------------------------------------------

Will is it on purpose that only the south-most bit of the overturning shows up here?


navidcy commented on 2023-10-04T12:35:31Z
----------------------------------------------------------------

Oh I see, it's because you used panant-01-zstar-ACCESSyr2 .

Was there any thinking behind this choice?

willaguiar commented on 2023-10-13T01:40:41Z
----------------------------------------------------------------

Thanks for noticing! Yes - just wanted to make sure the code would work for the regional configuration. I submitted a new code where I use the global-01-v3 mom6 experiment

@review-notebook-app
Copy link

review-notebook-app bot commented Oct 4, 2023

View / edit / reply to this conversation on ReviewNB

navidcy commented on 2023-10-04T12:30:35Z
----------------------------------------------------------------

how come only the southern part of the MOC is shown?


willaguiar commented on 2023-10-13T01:40:47Z
----------------------------------------------------------------

Same as above

Copy link
Collaborator

navidcy commented Oct 4, 2023

Oh I see, it's because you used panant-01-zstar-ACCESSyr2 .

Was there any thinking behind this choice?


View entire conversation on ReviewNB

@review-notebook-app
Copy link

review-notebook-app bot commented Oct 4, 2023

View / edit / reply to this conversation on ReviewNB

navidcy commented on 2023-10-04T12:35:38Z
----------------------------------------------------------------

Let's rephrase "I recommend" to "We recommend". It reads better. We want to avoid the notion that examples are somebody's but rather that the community is talking to the users!


willaguiar commented on 2023-10-13T01:40:53Z
----------------------------------------------------------------

done

@review-notebook-app
Copy link

review-notebook-app bot commented Oct 4, 2023

View / edit / reply to this conversation on ReviewNB

navidcy commented on 2023-10-04T12:35:39Z
----------------------------------------------------------------

Line #1.    %matplotlib inline

we can delete this line as is not the default


willaguiar commented on 2023-10-13T01:41:01Z
----------------------------------------------------------------

done in the new commit

Copy link
Collaborator Author

Added in the new commit


View entire conversation on ReviewNB

Copy link
Collaborator Author

Thanks for noticing! Yes - just wanted to make sure the code would work for the regional configuration. I submitted a new code where I use the global-01-v3 mom6 experiment


View entire conversation on ReviewNB

Copy link
Collaborator Author

Same as above


View entire conversation on ReviewNB

Copy link
Collaborator Author

done


View entire conversation on ReviewNB

Copy link
Collaborator Author

done in the new commit


View entire conversation on ReviewNB

@review-notebook-app
Copy link

review-notebook-app bot commented Oct 13, 2023

View / edit / reply to this conversation on ReviewNB

willaguiar commented on 2023-10-13T03:19:25Z
----------------------------------------------------------------

Also, last time I ran the notebook was on hugemem queue, so these warnings didn't appear before. They are back on the normalbw queue. Not quite sure how to solve it


@review-notebook-app
Copy link

review-notebook-app bot commented Oct 13, 2023

View / edit / reply to this conversation on ReviewNB

willaguiar commented on 2023-10-13T03:19:26Z
----------------------------------------------------------------

One thing that could be improved is the spikes on the bottom cell, below 4000m. I think at these depths small rho changes happens in large depth ranges, so the conversion of rho to z gets noisy. it would be cool if we could improve that someway?


@navidcy
Copy link
Collaborator

navidcy commented Oct 14, 2023

@dougiesquire I get a lot of similar-type warnings as in #285 here using unstable.

@navidcy
Copy link
Collaborator

navidcy commented Oct 14, 2023

@willaguiar, can you use pint to deal with the unit conversion, e.g., from m^3/s -> Sv? At the moment is done ad-hoc by dividing with the conversion factor.

Have a look at https://cosima-recipes.readthedocs.io/en/latest/DocumentedExamples/Transport_Through_Straits.html

@navidcy
Copy link
Collaborator

navidcy commented Oct 14, 2023

@willaguiar another remark: the ticks on the colorbar in the very last plot seems a bit weird... Am I right?

@navidcy
Copy link
Collaborator

navidcy commented Oct 25, 2023

Fixed the warnings and the colorbar ticks.

I'm happy for this to be merged as is; no need to deal with pint in this PR.

Copy link
Collaborator

@navidcy navidcy left a comment

Choose a reason for hiding this comment

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

lgtm

@navidcy navidcy merged commit d9fc8d6 into main Oct 25, 2023
3 checks passed
@navidcy navidcy deleted the Will_branch branch October 25, 2023 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

Update meridional overturning circulation example
3 participants