Home

Welcome to the Yellowstone-Application wiki!

Currently the large job is to get all the data updated and into the program, any data still needed can be found in the project section

A software manual is being created in order to stay organized and allow other users to add river sites as well as constituents.

Tantalus creek needs to be completely added to the program, and this is going to be used as a test to see if the software manual works well.

Tantalus creek will eventually be pulling data from a satellite mid-July, and the program will need to be updated to pull data from the feed.

Log

5/31/2018

Started to upload and format the software manual.
Tantalus Creek in the works
Cloned project to USGS OpenSource on GitLab (need to submit proposal for public access)

6/1/2018

Snake Data Updated
Falls R. Site Data added (note no water year or average data, not enough history)
Server & Ui updates pushed, Falls implemented, Snake data range changed.
Software Manual On Github in Readme.md
Hyperlinks bug fixed
Water year info put into bar graph in server.R (not pushed to master)
Tantalus Creek implemented in server (not pushed to master)
To-Do, find if we want water year data for more than just chloride.

6/4/2018

Bar Graph used to solve bug and data clarity issues for water year (Not Pushed)
Work began on on creating water years for all constituents.
- In order to do this we need to streamline the water years feature so that during future updates (new correlations), we do not need to re-calculate the water years. We are changing the SiteWater-Years input file to raw data separated into years, and calculating total loads based on the constituent selected. The concern of this is the effect it may have on benchmarks and run time but this has yet to be tested.

Update: Total bench marked time added with new feature, 1.75s, proceeding with overhaul.

Madison, Yellowstone, Fire-hole (WY), and Gibbon R. all have updated Water Year Input Files, work successfully with all constituents. Nothing has been uploaded to the update branch, still a lot to push to master.

6/5/2018

Work continues on getting the rest of the river sites updated Water Year Files to be compatible with new water year constituent code.
All River sites excluding Firehole Old Faithful (No Data) and Falls R. (Not enough Data), have been updated to include new water year constituent compatible input files. (not yet pushed)
Ethan- Tantalus Updates became too outdated for pull request, being used for understanding of program, will be delted in several days. Ethan-6/5 Updates will be pushed later in day.
License Added, USGS code.

6/6/2018

Work continues with data updates, Madison, Firehole, and Tantalus
Updates being put in Ethan 6/5 update branch
Server.R updates (to be pulled in near future)
- More robust overlap function, relies on offline data function for user input errors
- All constituent water years implemented (bar graph & new input files)
- Tantalus Creek implemented
- Notification to user upon requesting dates out of range, start of robust error handling.
Ui.R updates (TBP)
- Only compatibility with new Tantalus site.
File Updates (TBP)
- License as deemed necessary by USGS in own branch
- Tantalus data (Offline, Avg, Year)
- Constituent water year compatible input files, raw data separated into water years instead of previously calculated.
- Firehole Data Updated, more offline data.
Software Manual (TBP)
- Information on new water year functions added, function and input file changes
- Clarifying improvements to overlap function

6/7/2018

Deployed code today to shiny app servers, some performance issues and bugs, will be addressed tmro.

6/8/2018

Yellowstone Deploy Crashing Bug fixed, see Issue 14
Ethan 6/5 Updates Pulled, see Updates 6/8 for details
Software Manual Polishing
For the future, we would like a more robust input file system (automatic updating, less formatting)

6/11/2018

6/12/2018

6/18/2018

6/19/2018

Pre-release v1.0.0-beta
Waiting on meta-data publication and director approval before v1.0.0
Researching machine-learning in R to possibly implement predictions into the program.

6/20/2018

6/21/2018

6/22/2018