-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid ESGF query for CERES-EBAF datasets #2142
Comments
many thanks for raising this @rbeucher - am gonna move this to ESMValCore since the bug needs a fix plopped in there 👍 |
Hi again @rbeucher - the faceted search is populated correctly when I run a test of
|
Hi @valeriupredoi , Here are the details.
|
I am not using any specific credentials. |
I am rather baffled - I have reproduced the install process you have (just in case there may be an issue with our deployed version - was dreading it haha) and all still works for me though - could you please understand why you have a dev version for esmvaltool? It shouldn't matter since all the esgf stuff is happening inside esmvaltool, but that's no bueno for a conda install to have any other version than stable 2.9.0. Can you maybe try and install esmvaltool yourself, w/o relying on a central install via a container, and rerun exactly this - I am using the |
installing the tool by yourself ensures that no code tampering happened (by whoever installed it on the system), and may expose what @remi-kazeroni mentions here ESMValGroup/ESMValTool#3293 (comment) |
Yes. I haven't been able to figure out why it is showing a Dev version. I'm using a conda environment inside a container. All installed by me... I'll keep investigating.
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Valeriu Predoi ***@***.***>
Sent: Thursday, July 20, 2023 1:35:42 AM
To: ESMValGroup/ESMValCore ***@***.***>
Cc: Romain Beucher ***@***.***>; Mention ***@***.***>
Subject: Re: [ESMValGroup/ESMValCore] Invalid ESGF query for CERES-EBAF datasets (Issue #2142)
installing the tool by yourself ensures that no code tampering happened (by whoever installed it on the system), and may expose what @remi-kazeroni<https://github.com/remi-kazeroni> mentions here ESMValGroup/ESMValTool#3293 (comment)<ESMValGroup/ESMValTool#3293 (comment)>
—
Reply to this email directly, view it on GitHub<#2142 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA4CVFSNZ7COWN6D6XOAKP3XQ75E5ANCNFSM6AAAAAA2M5J2IQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
So I can confirm that I am using 2.9.0 not a Dev version. The version command was picking up a remnant of a Dev installation in my '.local' folder. |
that's not good ie having old installs/other dependencies still in path - makes me wonder what else is there in the path that may lead to a bit of a strange behaviour. Do you have access to an HPC perhaps? It'd be good to test there - or even a different machine where you plop a fresh installation from scratch, if you have such access - am afraid that, without being able to replicate the issue, I can't do much more, since this could be caused by things that I can't even think of - maybe @schlunma @remi-kazeroni or @bouweandela (when he's back from holidays) can help a bit more? 🍺 |
Yes I have reinstalled. It is a fresh conda installation and it's on HPC. We need to install a development version for debugging and development anyway so I'll get back to you when I find the root of the issue. This is part of our effort to have a data pool and automated runs or the ESMValTool recipes at NCI / ACCESS-NRI. Hopefully we will have something similar to what you have at DKRZ soon and will be able to contribute. |
@valeriupredoi It was indeed an issue with the DRS in the config-developer file. Thanks for pointing me toward this. I am closing this now. |
oh man, big PHEW - was fast running out of ideas 😁 Great you figured it out and cheers muchly @remi-kazeroni for thinking of the possible hiccup! Welcome to ESMValTool (through brimstone and fire) 😁 Cheers for closing this! |
Hi All,
So I cam across an issue affection quite a few recipes. When CERES-EBAF data are missing, the code sends an ESGF query with an empty
time_frequency
argument:Starting new HTTPS connection (1): esgf.ceda.ac.uk:443 2023-06-08 07:19:48,809 UTC [176196] DEBUG https://esgf.ceda.ac.uk:443 "GET /esg-search/search?format=application%2Fsolr%2Bjson&limit=500&distrib=true&offset=0&type=File&project=obs4MIPs&source_id=CERES-EBAF&time_frequency=&variable=swcre HTTP/1.1" 400 832
This results in an invalid query.
files = esgf_search_files(esgf_facets) File "/g/data/xp65/public/apps/med_conda/envs/access-med-0.1/lib/python3.10/site-packages/esmvalcore/esgf/_search.py", line 150, in esgf_search_files results = _search_index_nodes(facets) File "/g/data/xp65/public/apps/med_conda/envs/access-med-0.1/lib/python3.10/site-packages/esmvalcore/esgf/_search.py", line 119, in _search_index_nodes results = context.search( File "/g/data/xp65/public/apps/med_conda/envs/access-med-0.1/lib/python3.10/site-packages/pyesgf/search/context.py", line 141, in search return ResultSet(sc, batch_size=batch_size) File "/g/data/xp65/public/apps/med_conda/envs/access-med-0.1/lib/python3.10/site-packages/pyesgf/search/results.py", line 42, in __init__ self.__get_batch(0) File "/g/data/xp65/public/apps/med_conda/envs/access-med-0.1/lib/python3.10/site-packages/pyesgf/search/results.py", line 82, in __get_batch response = (self.context.connection File "/g/data/xp65/public/apps/med_conda/envs/access-med-0.1/lib/python3.10/site-packages/pyesgf/search/connection.py", line 159, in send_search response = self._send_query('search', full_query) File "/g/data/xp65/public/apps/med_conda/envs/access-med-0.1/lib/python3.10/site-packages/pyesgf/search/connection.py", line 210, in _send_query raise Exception("Invalid query parameter(s): %s" % content) Exception: Invalid query parameter(s): 2023-06-08 07:19:49,563 UTC [176196] INFO
I know the CERES-EBAF observation dataset is affected by issue ESMValGroup/ESMValTool#2974 but this seems unrelated.
Recipes affected are:
recipe_autoassess_landsurface_surfrad
recipe_clouds_ipcc
recipe_cmug_h2o
recipe_deangelis15nat
recipe_flato13ipcc_figures_92_95
recipe_lauer13jclim
recipe_perfmetrics_CMIP5
recipe_validation
recipe_wenzel16jclim
The text was updated successfully, but these errors were encountered: