Matt Thompson
Matt Thompson
I am thinking that #6394 by @YuKitsune is probably the PR to focus on. I think it's a successor to #5833 by @jochenhz?
I just learned about `diff-so-fancy` myself. Bump and :+1:
@rokuingh Well, the only mention of "mpi" in the xESMF repo is the on the [installation page](https://github.com/JiaweiZhuang/xESMF/blob/master/doc/installation.rst), so maybe there is a chance. Now, my reading of ESMPy is that...
Slight update. I was able to install xesmf 8 following #47 and `pytest` does succeed (with warnings). I can even then *delete* the `mpi*` from `bin/` and it still seems...
Also interesting: it looks like when xESMF does do a regridder, it only uses one core/process. ETA: though maybe that's because I removed `mpirun` et al?
> Thanks for this! I can confirm that the addition of the `mpi*` executables in my env confused our scheduler, but the simple deletion of them from `bin/` after installing...
> My first guess was going to be something to do with it being an M1 CPU, but this is actually on an x86, so probably not that... I updated...
@cmacmackin Do you know if this is now in FORD? (It is a ~3 year old issue and sometimes they fall through the cracks in closing) As @ZedThree knows (thanks...
> I'm afraid there's currently no mechanism for dealing with this. When the files are preprocessed, the text of the `#include` files is literally included, so ford has no way...
I'll try and see. I've been holding off on moving to HDF5 1.14 (as we have some code that assumes 1.10). But maybe this is the time to move forward...