Strange error using xp65

Technical
,
1

Hi,

I’ve decided today to be adventurous and use the latest conda environ (25.04) in xp65 instead of hh5, and my notebooks that ran with no problems are now giving weird errors (multiple of them). Here is a minimal example:

import cmocean as cm
import dask.distributed as dsk
import gcm_filters
import glob
import gsw
import intake
import matplotlib.gridspec as gridspec
import matplotlib.pyplot as plt
import numpy as np
import xarray as xr
from xgcm import Grid
import scipy.stats as st

import warnings # ignore these warnings
warnings.filterwarnings("ignore", category = FutureWarning)
warnings.filterwarnings("ignore", category = UserWarning)
warnings.filterwarnings("ignore", category = RuntimeWarning)

import logging
logging.getLogger("flox").setLevel(logging.WARNING)

import os
os.chdir('/home/561/jn8053/g_x77/Ross_gyre_colab')

catalog = intake.cat.access_nri
exp = "01deg_jra55v140_iaf_cycle3"

data = catalog[exp].search(variable = 'tx_trans_int_z', frequency = "1mon").to_dask().sel(xu_ocean = slice(-230, -80))
psi = data['tx_trans_int_z'].sel(yt_ocean = slice(None,-50)).cumsum('yt_ocean')/(1035*1e6)
g_str = (-psi.where(psi<-12).sel(xu_ocean = slice(-180, -140))).chunk({'xu_ocean':-1, 'yt_ocean':-1}).quantile(.95, ['xu_ocean', 'yt_ocean']).load()

g_str = g_str.rolling(time=12, center=True).mean('time')

And these are the errors. I’ve never seen them before:

image
image1891×424 143 KB

image
image1891×424 77 KB

I have switched back to hh5 which works fine and don’t really have the time to troubleshoot this, but thought I’d flag.

1 Like
2

Thanks Julia

If you still have the errors, can you copy and paste the text here rather than screenshot

The screenshot of the first is just some warnings, but my memory when you showed me was some esoteric BDB error ??

The second error looked like something odd with the access telemetry - @CharlesTurner @tmcadam

3

Yeah, this is a telemetry issue. @JuliaN is this being triggered by the

g_str = g_str.rolling(time=12, center=True).mean('time')

line?

If so I’ll get a fix in right away, should be relatively simple.

A word of caution re. analysis3-25.04 - Intake ESM mysteriously started triggering segmentation faults in the 25.04 environment, apparently due to a dependency change. We’ve got a bugfix in, but still haven’t released the new fixed version. Hopefully this should be out in the next couple days.

For now, I’d recommend dropping to analysis3-25.02 environment, which:
a. Intake-ESM appears to be stable in.
b. Telemetry isn’t enabled in - so no AST parsing errors.

4

It happened throughout the code, not just the g_str line, and I had tried to switch back to 24.07 kernel but the error still came up. But maybe it was one of those times you just have to close the ARE sesh and start again

5

That’s weird, I wouldn’t expect to see the error in previous versions. I’ll do some more digging.

I’ve worked out the source of the bug, so I’ll have the fix released later today - I’ll update once it’s applied to the environment.

6

Hi @JuliaN,

the issue is now fixed & I’ve modified the relevant packages such that there should be no more issues of this type.