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.