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.

Sign up for GitHub

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

Jump to bottom

Better checking for corrupt data #58

Open
kendonB opened this issue Apr 4, 2016 · 1 comment
Open

Better checking for corrupt data #58

kendonB opened this issue Apr 4, 2016 · 1 comment

Comments

@kendonB
Copy link
Contributor

kendonB commented Apr 4, 2016

I had a single day download that contained tmax data with values around 6e+36. Everything read in fine and the errors went away after I redownloaded the day.

Could implement some sort of check on the data to make sure these get redownloaded. I can't think of any way to do it without literally reading everything in though. Might just have to leave this to the user.
@kendonB
Copy link
Contributor Author

kendonB commented Apr 4, 2016

There's a chance this was simply an error on the PRISM end (since fixed) and the file downloaded correctly. Any users who encounter this, please leave a comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kendonB