Open nicolasaunai opened 2 months ago
Can you do the same with disable_cache=True, disable_proxy=True
to check ensure that the bug not on our proxy.
Hello,
I am an Intern working with Nicolas. I tried with disable_cache=True, disable_proxy=True
.
But I am getting the following error message :
MaxRetryError: HTTPSConnectionPool(host='cdaweb.gsfc.nasa.gov', port=443): Max retries exceeded with url: /WS/cdasr/1/dataviews/sp_phys/datasets/MMS1_FPI_BRST_L2_DIS-MOMS/data/20151114T025653Z,20151114T030200Z/mms1_dis_bulkv_gse_brst?format=cdf (Caused by ResponseError('too many 503 error responses))
However when importing the speasy library I also get this warning (it could be linked) :
Can't get data from proxy server `http://sciqlop.lpp.polytechnique.fr/cache`
Description
Last date of MMS1 FPI FAST data seems erroneous on Sept. 23 2018, but only when getting the data from CDA provider, with AMDA it's fine.
What I Did
this gives:
so, on CDA, the last date of Sept. 23 is '2018-09-23T22:04:57.103826000' which is clearly wrong. On AMDA it's '2018-09-23T23:59:51.143000000', as the date before the last in CDA.
We think it's somehow related to sprays because we have read the CDF files directly from CDA and could not find the erroneous time.
We have downloaded three CDF files:
The idea was to test whether the spurious date is the last date of the first file, the first of the second or only in the merged version.... but the spurious date is in none of the files...
here is the test:
Bonus question, (maybe more for @brenard-irap ?) any reason why the dates are rounded differently from AMDA than from CDA?