Professional Documents
Culture Documents
Our class went to silverton to test the water quality of the three main tributaries of the upper
Animas watershed, Cement creek, Mineral creek, and the Upper Animas. We tested things like
Streamflow (The flow of water in a river), Temperature, Turbidity (The cloudiness of a fluid), pH
(How acidic a liquid is), and Conductivity (how conductive a material is). We then used the
results of these tests to help us predict what the levels of the Upper Animas will be by using
methods like averages (a number expressing the central or typical value in a set of data),
standard deviation (A quantity calculated to indicate the extent of deviation for a group as a
whole), mean (average), median (Middle number), maximum (Highest number), minimum
(Lowest number), and range (The difference between the lowest and highest values).
To Predict the values for streamflow below the confluence, we added up the average
streamflow for all three of the streams to get a total streamflow of 103.34 ft3/s. To Predict the
values for turbidity, conductivity, and temperature found below the convergence of these three
streams we used a weighted average. A weighted average is just like taking an average, but
each piece of the data set has a percent weight all adding up to 100%. A weighted average
allows different data points to have weight affecting the average different amounts. An example
of how we used weighted average is how we predicted temperature. If two different water
sources with different temperatures converge and have the same streamflow, you can just take
the average of the two temperatures to predict the temperature at the confluence, but this
doesn't work if the streamflows are different. When the streamflow is different a weighted
average is used. We found the weights by dividing the average streamflow of the stream we
were trying to find the weight for by the total streamflow 28% for Cement Creek 48.3% for
Mineral Creek and 23.7% for the Upper Animas. Then we multiply the average temperature of
each stream by its corresponding percent weight. After finding those values, they are added
together to find the weighted average. This process can be expressed in this formula where F is
the flow rate of a tributary, and V is the value you want to predict after the confluence.
f1 f2 f3
f +f +f ... * v 1 + f +f +f ... * v 2 + f +f +f ... * v 3 ... The weighted average for temperature was 7.1oc. We
1 2 3 1 2 3 1 2 3
used that same weighted average procedure for turbidity, and conductivity as well and predicted
the following conditions after the confluence. We predicted that turbidity would be 13.8 NTU
after the confluence, and that conductivity would be 556.3 uS/cm. To conclude we added the
water volume of all the tributaries to predict streamflow, and used weighted averages to predict
all the other values, because of the unequal contribution from the separate streams. We did not
predict pH because we didnt understand how we should predict it (because it is on a
logarithmic scale) as well as Steve telling us we didnt need to. We think that all of our
calculations are correct and any inconsistencies with the USGS data after the confluence come
from data inconsistencies.
To reiterate our prediction for temperature was 7.1oc for turbidity it was 13.8 NTU, for
conductivity it was 556.3 uS/cm, and for streamflow, it was 103.34 ft3/s. In a general sense, our
predictions were pretty spot on, but there was 1 prediction that was higher than the USGS
measurements by a significant amount. Streamflow, temperature, and turbidity were the 3
where our predictions lined up best with the USGS data. Our temperature prediction (7.1oc) was
within the 4-9o range for that day as well as being pretty close to the daily average at around
6o. Our streamflow prediction (103.34 ft3/s) was very close to the data point on that day 105
ft3/s, but not so close to the daily average around 140 ft3/s though the USGS data for this year
wasnt as well. For our predictions about turbidity and conductivity, we had to use daily
averages because the sensors froze. Our Turbidity prediction (13.8 NTU) was quite close to the
daily average of between 12-15 NTU, though the trend of this year's data was set to prove us
wrong. Now lastly conductivity, our predicted conductivity (556.3 uS/cm) was significantly higher
than the daily average about 475. Although the data from this years trend was headed to
around 530 uS/cm within a significant margin of our prediction though, this years conductivity is
in general higher than the daily average and was raising at a faster rate. Even though at some
points our predictions are askew, all of them had at least one piece of evidence from the USGS
stations to support them.
Even though this investigation was designed for us to fail, we think that it was very worthwhile.
This investigation made us not only think of how we are going to solve the problem we are
presented with, but also what assumptions do we make in our solution. A good example of this
was predicting pH. Like we said before the investigation was set up so that people would fail,
this is because people would assume that pH is on a linear scale like almost any other
measurement 5 is 1 bigger than 4. Although this is true for all of the other units of measurement
in the investigation pH is logarithmic meaning 5 is 10 times bigger than 4. Though predicting pH
couldve been hard, we had all of the tools to predict all of the other values fairly easily, but
overall it was fun.
I think we deserve an A because we worked hard to make sure the way we were making
predictions was accurate as well as fine tuning our datasets to make sure we got correct
answers.