-
Notifications
You must be signed in to change notification settings - Fork 5
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
esgpull not recognizing updated datasets #60
Comments
I notice you are using I tried reproducing your issue, and got updates with new files on my end, with
That amounts to 48 files, which is also what I get after an |
Using
After running From the LOG output:
So it appears that
results in
|
At times, esgpull will have a difficult time recognizing retractions to datasets/files that fall under a particular query, thus leading to the scenario that I presented in #58.
The example I present here is for the input4MIPs project, and the following query:
From this particular institution, there have been several iterations of data, the latest of which as of this writing is "1-3-1".
Example: input4MIPs.CMIP6Plus.CMIP.uoexeter.UOEXETER-CMIP-1-3-1.atmos.day.utsvolcemis.gn
Previous "versions" of '1-1-3', '1-2-0', and '1-3-0', have been retracted. When I go to update the esgpull query (i.e.
esgpull update cd5e6e
, I will receive the following message:<cd5e6e> is already up-to-date.
For some reason, esgpull is not recognizing these different dataset ID's. Any help would be appreciated.
Thanks
The text was updated successfully, but these errors were encountered: