You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
The
SNODASDaily_Automated.py
Python script runs everyday and processes data files for each day that it is run. Within theSNODASDaily_Automated.py
Python script, thecopyAllToOwfAmazonS3.bat
script is called. ThecopyAllToOwfAmazonS3.bat
script pushes all of the changed data files created by theSNODASDaily_Automated.py
Python script to the Amazon S3 account.In order to push the files up, the
copyAllToOwfAmazonS3.bat
script uses async
functionality rather than acopy
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 thesync
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 thecopyAllToOwfAmazonS3.bat
script has the years pre-loaded up until 2023. However, in 2024, the same issue will occur within the SNODAS application.The text was updated successfully, but these errors were encountered: