Closed tomvothecoder closed 2 weeks ago
This issue seemed to only affect that single user. I will close for now.
I have also hit this issue, but I figured out some way around it (I don't remember the details).
I have also hit this issue, but I figured out some way around it (I don't remember the details).
This might have occurred in older versions of xCDAT. I don't think it should be happening in the more recent versions with esmpy/esmf/xesmf constraints.
What happened?
An attendee at the E3SM tutorial workshop ran into a
VersionMismatch
error withesmf=8.4.2
andesmpy=8.6.0
after running theimport
cell containingxcdat
(source notebook).This notebook requires the user to setup and activate the E3SM Unified v1.10.0 kernel. I was unable to reproduce this issue on my end.
What did you expect to happen? Are there are possible answers you came across?
The user should have been able to use the E3SM Unified 1.10.0 kernel. Other attendees running the xCDAT notebook did not run into this issue.
I'm not sure exactly the root cause of this issue because the environment is pre-built with all of the required dependencies.
Minimal Complete Verifiable Example (MVCE)
No response
Relevant log output
No response
Anything else we need to know?
Environment
E3SM Unified v1.10.0 xCDAT=0.7.0