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

Must manually include each year in the copyAllToOwfAmazonS3.bat #15

Open
egiles16 opened this issue Jan 2, 2018 · 0 comments
Open

Must manually include each year in the copyAllToOwfAmazonS3.bat #15

egiles16 opened this issue Jan 2, 2018 · 0 comments
Labels

Comments

@egiles16
Copy link
Contributor

egiles16 commented Jan 2, 2018

The SNODASDaily_Automated.py Python script runs everyday and processes data files for each day that it is run. Within the SNODASDaily_Automated.py Python script, the copyAllToOwfAmazonS3.bat script is called. The copyAllToOwfAmazonS3.bat script pushes all of the changed data files created by the SNODASDaily_Automated.py Python script to the Amazon S3 account.

In order to push the files up, the copyAllToOwfAmazonS3.bat script uses a sync functionality rather than a copy functionality (Line 47). This is an insurance policy so that all of the already-uploaded data files on Amazon S3 do not accidentally get erased. The downside to the sync functionality is that you have to manually include the years of data files to push up to the S3 account.

On 2018/01/01, the map on the SNODAS application did not display any of the basin data layers. This is because in the copyAllToOwfAmazonS3.bat script, --include *2018* was not in the Line 47 command. As a security net, the new version of the copyAllToOwfAmazonS3.bat script has the years pre-loaded up until 2023. However, in 2024, the same issue will occur within the SNODAS application.

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

No branches or pull requests

1 participant