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

internalize Gonzalo's parser/model #16

Open
dmarulli opened this issue Apr 17, 2018 · 1 comment
Open

internalize Gonzalo's parser/model #16

dmarulli opened this issue Apr 17, 2018 · 1 comment

Comments

@dmarulli
Copy link
Collaborator

No description provided.

@dmarulli
Copy link
Collaborator Author

dmarulli commented Apr 23, 2018 •
edited
Loading

"Do you think we should continue to only have a single file that is overwritten every time? This would be the simplest approach, and I don't foresee us running into file size issue if it is only a few dozen sensors reading daily. Just want to be explicit about this choice vs. a choice that needs more logical overhead like having each daily snowpack file written to S3 as a different CSV or something" - @christophertull (comment ported from argus pull request)

context note: updates to how the ucla parser/model writes data to s3 may have to be accounted for by means of some additional argus dev

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
@dmarulli