`nocache` parameter disabled for ADS requests?

Software and Tools API
,
1

As of last night previously functioning requests to the ADS which included the nocache parameter began to fail. Requests to CDS implementing this parameter seem to be going through however.

Can someone from ECMWF confirm that nocache is no longer a valid ADS parameter? If so, was it superseded by a different parameter or has caching as a concept been removed altogether from the ADS?

2

Hi Arbol. Can you tell me what dataset you’re referring to and what error message you got?

Thanks,

Luke.

3

Hi Luke,

I’m trying to request ozone data from the EAC4 dataset. Exact request formatted like so:

{
'time': ['00:00', '03:00', '06:00', '09:00', '12:00', '15:00', '18:00', '21:00'], 
'data_format': 'grib', 
'download_format': 'unarchived',
'variable': 'ozone', 
'date': '2024-01-01/2024-01-31', 
'nocache': '5463547217391356', 
'model_level': 60
}

This (and similarly formatted requests), which previously worked without issue, trigger an error

Exception occurred during CDS API call: HTTPError - 400 Client Error: Bad Request for url: https://ads.atmosphere.copernicus.eu/api/retrieve/v1/processes/cams-global-reanalysis-eac4/execution
invalid request
request: Invalid key name: 'nocache'
4

Hi Arbol. From what I can see “nocache” has never worked (or should never have worked) for that dataset. It will allow “no_cache” though.

What’s your reason for wanting to avoid cached results? That’s generally only useful for datasets that update on a daily basis, and many of those have caching disabled anyway.

Luke.

5

Hi Luke,

Thanks for taking the time to reply. To be honest, we copied this parameter over from requests to CDS pulling daily ERA5 updates when setting up ETLs for the ADS. It’s no sweat taking the parameter out, I just wanted to confirm it wasn’t a separate issue.

Robert