-
Notifications
You must be signed in to change notification settings - Fork 13
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
Post plots of NEON tower input data in S3 bucket #36
Comments
Here's a link to a bucket listing: https://neon-ncar.s3.data.neonscience.org/listing.txt |
@wwieder , I'll work to add the diagnostic plots to the S3 bucket tomorrow. They should be picked up in the next run of the bucket listing workflow. |
bucket listing changed to csv https://neon-ncar.s3.data.neonscience.org/listing.csv |
<style>
</style>
Diagnostic plots now being written to S3, example listing from BART in the table above. |
Moving the email thread here, but hopefully this can help us identify issues like #34 & #38
@ddurden said: Data from 1/1/2018-12/31/2020 should be processed for NIWO, HARV, SCBI, OSBS, and KONZ. I’m producing some diagnostic plots if you feel they would be helpful. I’ve attached examples from HARV attached.
@wwieder responded: These diagnostics are really useful on our end for quickly diagnosing errors that may be causing issues in the model. How / where should we share these data?
@ddurden: I guess we could store them in S3 bucket, but should we create a new folder or put it somewhere in the existing folder structure (eval_files folder)?
@wwieder: That would work. I like the idea of having another (input_data_eval) folder. The challenge on our end is knowing what data are available. I wonder if there is an easier way that we can see what data are available in the S3 bucket? Gordon will likely bring this up in our CICOE meeting next week.
@ddlenz Dave, we could do something similar to what we set up for access to your SAE data updates, e.g. a link to a bucket listing.
HARV_forcing.pdf
The text was updated successfully, but these errors were encountered: