An important part of the design process is talking to users! We’ve had nine interviews with a large variety of people in the hydrology space: professors, graduate students, data managers, software developers, tribal scientists, and more. They spanned the spectrum of non HydroShare users, to daily users of HydroShare. We believe this diversity is important for getting a spectrum of ideas, painpoints, use cases, and workflows about the HydroShare ecosystem. It’s also valuable to understand the space and context in which our users are working.
Initial Design Tasks
Our team are not hydrology experts, and hadn’t used the software before. For some initial investigation into HydroShare, we went through a task list of the most common uses / workflows in the HydroShare environment. The landing page for HydroShare looks as follows: We investigated these six workflows: Discover →…
Data Science Final Project Architecture
We wrote a lot of code for this project, in many iterations and versions. We tried to compile the most relevant and important work into these three notebooks, available at our GitHub Repository Exploration Notebook Web Scraping Notebook Shot Predictor Notebook
Data Science Documentation
The game of basketball has gotten increasingly data-driven in the last couple of years, with companies like SportsVU tracking player movements with cameras above all games and companies like Second Spectrum using that information for data analytics and machine learning. We wanted to take on a project that was unique…