Closed ScottWales closed 3 years ago
you mean that because we're getting the facets directly from the ESGF this fails on compute nodes that cannot connect. I guess we'll have to create a json file with them as for CMIP data. A good reminder I was thinking of re-organise all of them as cordex.
It appears we also have another issue with getting the facets from ESGF, and that they might be generated on the fly depending on the nodes that are available, a user pointed out an issue with AUS-22 being sometimes a valid value and at times not. I suspect that AUS22 data is only available from ENES and hence if that node is offline the valid value disappear!
I've done this, now we have CORDEX_validation.json file and use the same functions for cordex validation as we do for CMIP, so it is independent of ESGF nodes availability and can run on compute nodes Updated in cordexupdate
Solved in release 1.3.1 commit https://github.com/coecms/clef/commit/aeacb08d597c23b0d6d313b85e19f391898fd257
Trying to run on a compute node hangs, as clef tries to get the cordex facets from esgf. I think local searches are supposed to work on the compute nodes