Skip to content
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

Improve xml code to check for valid changes before starting #7

Closed
1 of 4 tasks
durack1 opened this issue Sep 4, 2014 · 2 comments
Closed
1 of 4 tasks

Improve xml code to check for valid changes before starting #7

durack1 opened this issue Sep 4, 2014 · 2 comments
Assignees

Comments

@durack1
Copy link
Owner

durack1 commented Sep 4, 2014

Compare list_outfiles and list_outfiles_paths to previous version of xml database prior to initiating xml creation - this way if no changes are to be made, the job will complete rather than loading up machines and the network over a weekend.

  • Check for existing instance of make_cmip5_xml.py
  • Consider situation where partial files were downloaded last run, and now complete - in such a case a new xml will be created
  • Consider querying Jeff P on ways to interrogate his database to query new downloads, and also query new data publication (migration across filesystems)
  • Will require that previous xml creation completed successfully, otherwise failed runs will continue to compare xml output file favourably

May need to interrogate Jeff Painter's database of files - which provides an update as to whether any new files (or partial files) have changed since the last run

@durack1 durack1 self-assigned this Sep 4, 2014
@durack1
Copy link
Owner Author

durack1 commented Jul 23, 2018

@pochedls should this be reincarnated in cmiplib? If yes, I'll copy it across

@durack1 durack1 closed this as completed Jul 23, 2018
@pochedls
Copy link
Collaborator

This is essentially what cmiplib does, so we can leave this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants