npsource-wooomm — List for general topics regarding the use of WOOOMM system.

Re: [Npsource-wooomm] Touching Bases

[Connor B. <con...@vt...>]

I've enjoyed working together over the last few years, Elaina. Sorry your
car broke down, but hopefully most of your bad car and computer luck will
stay behind in Blacksburg! Good luck with everything at CSU!

Connor

On Mon, Jul 23, 2018 at 8:46 AM Joseph Kleiner <jkl...@vt...> wrote:

> Thanks for the update Elaina, I hope you were able to get the car troubles
> sorted!
>
> It’s been great having you on the team the past couple years, and I wish
> you well as you make the move to CSU.
>
>
>
> Cheers,
>
> -Joey
>
>
> On Fri, Jul 20, 2018 at 2:28 PM, Elaina Passero <pas...@vt...> wrote:
>
>> Hey everyone,
>>
>> Sorry for the super delayed response. Naturally my car broke down while I
>> was moving out of Blacksburg, so I have been in a bit of a tizzy. I wanted
>> to thank you all again for a great working environment and experience. I've
>> learned so much during my time with HARP. I will be checking my VT email,
>> but the next two weeks I will not be online much.
>>
>> My CSU email is ela...@co.... Please feel free to pass
>> my email on to anyone that is interested in CSU or who wants to learn more
>> about HARP. If you all are ever in Fort Collins, Boulder, Denver, or the
>> surrounding area please let me know.
>>
>> I'll stay in touch and let you all know where I move along in my career.
>>
>> Best,
>> Elaina
>>
>> --
>> Elaina Passero
>> Biological Systems Engineering
>> Virginia Tech Class of 2018
>> (336) 940-7328
>> pas...@vt...
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Npsource-wooomm mailing list
>> Nps...@li...
>> https://lists.sourceforge.net/lists/listinfo/npsource-wooomm
>>
>>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Npsource-wooomm mailing list
> Nps...@li...
> https://lists.sourceforge.net/lists/listinfo/npsource-wooomm
>

Re: [Npsource-wooomm] Touching Bases

[Joseph K. <jkl...@vt...>]

Thanks for the update Elaina, I hope you were able to get the car troubles
sorted!

It’s been great having you on the team the past couple years, and I wish
you well as you make the move to CSU.



Cheers,

-Joey


On Fri, Jul 20, 2018 at 2:28 PM, Elaina Passero <pas...@vt...> wrote:

> Hey everyone,
>
> Sorry for the super delayed response. Naturally my car broke down while I
> was moving out of Blacksburg, so I have been in a bit of a tizzy. I wanted
> to thank you all again for a great working environment and experience. I've
> learned so much during my time with HARP. I will be checking my VT email,
> but the next two weeks I will not be online much.
>
> My CSU email is ela...@co.... Please feel free to pass my
> email on to anyone that is interested in CSU or who wants to learn more
> about HARP. If you all are ever in Fort Collins, Boulder, Denver, or the
> surrounding area please let me know.
>
> I'll stay in touch and let you all know where I move along in my career.
>
> Best,
> Elaina
>
> --
> Elaina Passero
> Biological Systems Engineering
> Virginia Tech Class of 2018
> (336) 940-7328
> pas...@vt...
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Npsource-wooomm mailing list
> Nps...@li...
> https://lists.sourceforge.net/lists/listinfo/npsource-wooomm
>
>

[Npsource-wooomm] Touching Bases

[Elaina P. <pas...@vt...>]

Hey everyone,

Sorry for the super delayed response. Naturally my car broke down while I
was moving out of Blacksburg, so I have been in a bit of a tizzy. I wanted
to thank you all again for a great working environment and experience. I've
learned so much during my time with HARP. I will be checking my VT email,
but the next two weeks I will not be online much.

My CSU email is ela...@co.... Please feel free to pass my
email on to anyone that is interested in CSU or who wants to learn more
about HARP. If you all are ever in Fort Collins, Boulder, Denver, or the
surrounding area please let me know.

I'll stay in touch and let you all know where I move along in my career.

Best,
Elaina

-- 
Elaina Passero
Biological Systems Engineering
Virginia Tech Class of 2018
(336) 940-7328
pas...@vt...

Re: [Npsource-wooomm] HARPers rocking the white board!

[Robert B. <rbu...@vt...>]

Yeah - now this is big science!

Re: [Npsource-wooomm] HARPers rocking the white board!

[Joseph K. <jkl...@vt...>]

Whoo! Awesome. This pic is "Joey approved"

On Wed, Jun 27, 2018 at 10:30 AM, Durelle Scott <ds...@vt...> wrote:

> [image: IMG_2658.JPG]
> ​
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Npsource-wooomm mailing list
> Nps...@li...
> https://lists.sourceforge.net/lists/listinfo/npsource-wooomm
>
>

[Npsource-wooomm] HARPers rocking the white board!

[Durelle S. <ds...@vt...>]

[image: IMG_2658.JPG]
​

Re: [Npsource-wooomm] reproducible science

[Robert B. <rbu...@vt...>]

 Very cool, very relevant! Getting good at this seems like a next level for
us — lets follow up on this.

/r/b

On Fri, Jun 22, 2018 at 12:44 PM Durelle Scott <ds...@vt...> wrote:

> Hi all,
>
> Yesterday I went to a great workshop on code reproducibility. The
> presentation (goo.gl/ncBnr2) lays out the "ideal" concepts for best
> practices. There are also a bunch of links for guidance/templates that
> may/may not be helpful. The data service Code Ocean is not required...but
> is free for anyone with an academic email address. The data service
> basically builds a docker container that is transportable for folks to use
> containing the key elements of reproducing a computational analysis (e.g.
> readme, scripts, data, etc.).
>
> Cheers,
>
> Scotty
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Npsource-wooomm mailing list
> Nps...@li...
> https://lists.sourceforge.net/lists/listinfo/npsource-wooomm
>
-- 
--
Robert W. Burgholzer
 'Making the simple complicated is commonplace; making the complicated
simple, awesomely simple, that's creativity.'  - Charles Mingus

[Npsource-wooomm] reproducible science

[Durelle S. <ds...@vt...>]

Hi all,

Yesterday I went to a great workshop on code reproducibility. The
presentation (goo.gl/ncBnr2) lays out the "ideal" concepts for best
practices. There are also a bunch of links for guidance/templates that
may/may not be helpful. The data service Code Ocean is not required...but
is free for anyone with an academic email address. The data service
basically builds a docker container that is transportable for folks to use
containing the key elements of reproducing a computational analysis (e.g.
readme, scripts, data, etc.).

Cheers,

Scotty

Re: [Npsource-wooomm] Back in the office

[Robert B. <rbu...@vt...>]

First -- did you graduate!?!?!?  :) 2nd - welcome back!  I m working
(semi-)diligently on monthly variation and methods and would love to check
in when you get yourself re-grounded.

/r/b

On Mon, May 21, 2018 at 9:41 AM, Elaina Passero <pas...@vt...> wrote:

> Good morning everyone,
>
> Just wanted to let you all know that I am back in the office now. I'm not
> sure when the new analysts are beginning, but I am available to help them
> with R and onboarding when they need it. Today I'm catching myself up on
> where I left off before graduation. I plan on just picking up where I left
> off.
>
> Is it too late for me to get a key to the 4th floor? I managed to make it
> this far without one, but it would make it easier for me to arrive early in
> the morning.
>
> Best,
> Elaina
>
>
> --
> Elaina Passero
> Biological Systems Engineering
> Virginia Tech Class of 2018
> (336) 940-7328
> pas...@vt...
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Npsource-wooomm mailing list
> Nps...@li...
> https://lists.sourceforge.net/lists/listinfo/npsource-wooomm
>
>


-- 
--
Robert W. Burgholzer
 'Making the simple complicated is commonplace; making the complicated
simple, awesomely simple, that's creativity.'  - Charles Mingus

[Npsource-wooomm] Back in the office

[Elaina P. <pas...@vt...>]

Good morning everyone,

Just wanted to let you all know that I am back in the office now. I'm not
sure when the new analysts are beginning, but I am available to help them
with R and onboarding when they need it. Today I'm catching myself up on
where I left off before graduation. I plan on just picking up where I left
off.

Is it too late for me to get a key to the 4th floor? I managed to make it
this far without one, but it would make it easier for me to arrive early in
the morning.

Best,
Elaina


-- 
Elaina Passero
Biological Systems Engineering
Virginia Tech Class of 2018
(336) 940-7328
pas...@vt...

[Npsource-wooomm] HARP Meeting

[Alyssa F. <aly...@vt...>]

Here’s the link for our meeting today:

https://virginiatech.webex.com/join/Alyssaf4

Sent from Mail for Windows 10

[Npsource-wooomm] Meeting Today

[Alyssa F. <aly...@vt...>]

Here’s the link for our meeting today at noon:

https://virginiatech.webex.com/join/Alyssaf4

Sent from Mail for Windows 10

[Npsource-wooomm] HARP Meeting

[Alyssa F. <aly...@vt...>]

Here’s the link for our meeting at noon 

https://virginiatech.webex.com/join/Alyssaf4

Sent from Mail for Windows 10

[Npsource-wooomm] HARP Meeting

[Alyssa F. <aly...@vt...>]

Here’s the link for our meeting today:

https://virginiatech.webex.com/join/Alyssaf4

Sent from Mail for Windows 10

Re: [Npsource-wooomm] weekly update & ELF documentation questions

[Elaina P. <pas...@vt...>]

Alright, thanks for the feedback!

- E

On Fri, Mar 16, 2018 at 11:04 AM, Joseph Kleiner <jkl...@vt...> wrote:

> Elaina,
>
>
>
> EDAS-what to include:
>
> ·         Try to list any known *limitations* present in the dataset and
> how we used code to overcome those limitations. The primary limitation that
> comes to mind is mixed sample resolution for benthics, an issue we solved
> by using groupings of date range and agency – definitely worth including in
> this documentation
>
> ·         Beyond limitations, we want to discuss any processing we do to
> the raw dataset i.e. how we *subset* the data and why
>
> o   Subset using the benthic groupings
>
> o   Spatial containment used to subset data by individual hydrologic (and
> eco) regions
>
> o   Subset on date range (though most of our analyses have focused on the
> full date range of samples, we should still mention the ability to subset
> on date)
>
> o   Filtering for only the “max” values at stations with multiple samples
>
>
>
> Gaps in data at modeled low flows:
>
> ·         Jen has contacted the NHDPlus Developers who were going to look
> into the monthly streamflow issues that we identified -> let’s check with
> her to see if she’s heard anything back
>
>
>
> Boxplot DA units
>
> ·         Just looking at the y-axis labels it appears we used sqkm
> units. Which is a good bet since at the time of that analysis we only had
> the drainage areas from EROM imported in sqkm units
>
>
>
> RCC Breakpoints
>
> ·         This should be included in the piecewise function section
> (rather than a stand-alone section). Remembering that the piecewise method
> serves two separate independent objectives
>
> o   1) RCC breakpoint identification
>
> o   2) Can be used for automating the restriction of data below a certain
> DA or Flow for producing best fit ELFs
>
> ·         I think you're on the ball but I'll just plug this general
> note- be sure to focus on how the piecewise and the other functions do what
> they do mathematically/algorithmically (this is really the crux of the
> whole methods paper, we need to be able to show what/how/why the equations
> are doing what they're doing - this is especially important when it comes
> to the piecewise method, and also the concept of performing a quantile
> regression to subset the data prior to performing a linear regression of
> the upper x% of data)
>
>
> -J
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Npsource-wooomm mailing list
> Nps...@li...
> https://lists.sourceforge.net/lists/listinfo/npsource-wooomm
>
>


-- 
Elaina Passero
Biological Systems Engineering
Virginia Tech Class of 2018
(336) 940-7328
pas...@vt...

Re: [Npsource-wooomm] weekly update & ELF documentation questions

[Joseph K. <jkl...@vt...>]

Elaina,



EDAS-what to include:

·         Try to list any known *limitations* present in the dataset and
how we used code to overcome those limitations. The primary limitation that
comes to mind is mixed sample resolution for benthics, an issue we solved
by using groupings of date range and agency – definitely worth including in
this documentation

·         Beyond limitations, we want to discuss any processing we do to
the raw dataset i.e. how we *subset* the data and why

o   Subset using the benthic groupings

o   Spatial containment used to subset data by individual hydrologic (and
eco) regions

o   Subset on date range (though most of our analyses have focused on the
full date range of samples, we should still mention the ability to subset
on date)

o   Filtering for only the “max” values at stations with multiple samples



Gaps in data at modeled low flows:

·         Jen has contacted the NHDPlus Developers who were going to look
into the monthly streamflow issues that we identified -> let’s check with
her to see if she’s heard anything back



Boxplot DA units

·         Just looking at the y-axis labels it appears we used sqkm units.
Which is a good bet since at the time of that analysis we only had the
drainage areas from EROM imported in sqkm units



RCC Breakpoints

·         This should be included in the piecewise function section (rather
than a stand-alone section). Remembering that the piecewise method serves
two separate independent objectives

o   1) RCC breakpoint identification

o   2) Can be used for automating the restriction of data below a certain
DA or Flow for producing best fit ELFs

·         I think you're on the ball but I'll just plug this general note-
be sure to focus on how the piecewise and the other functions do what they
do mathematically/algorithmically (this is really the crux of the whole
methods paper, we need to be able to show what/how/why the equations are
doing what they're doing - this is especially important when it comes to
the piecewise method, and also the concept of performing a quantile
regression to subset the data prior to performing a linear regression of
the upper x% of data)


-J

[Npsource-wooomm] weekly update & ELF documentation questions

[Elaina P. <pas...@vt...>]

Hello all,

This week and the week before break I focused on documentation of EDAS and
EROM methods.

EDAS processing and QA are ready for you all to look over. I am not sure I
understand the limitations of the EDAS stuff though. Would those include
the variability of benthic sample resolution? What all should be included
there?

I also worked on the EROM processing, QA, and limitations. In the QA
section I discussed the USGS vs EROM winter flow issue inquiry and the
exclusion of stations with DA:Q > 1000. I pulled limitations from our
previous documentation. Tomorrow I plan on investigating/discussing those
more, but I had a couple of questions I wanted to ask first.
1) Did we ever find out more info about the "gaps" in data at modeled low
flows?
2) Did we confirm what drainage area units we used when we compared USGS vs
Gage normalized flow in those boxplots?

Also, should I be working on the RCC breakpoints section? If so, what
should go in this section?

Thanks,

Elaina


-- 
Elaina Passero
Biological Systems Engineering
Virginia Tech Class of 2018
(336) 940-7328
pas...@vt...

Re: [Npsource-wooomm] FW: Update

[Robert B. <rbu...@vt...>]

Thanks Alyssa - I agree w2ith Joey and have 2 things:
1) LEt's move this into a github issue since the listserv seems to be less
and less reliable
2) The large differences in DA we must ascertain if we are looking at
multiple segments. We will want to see maps that clearly outline the entire
contributing area of the basin in question and the USGS gage location and
then we can sort it out.  Regardless of the difference (whether 5% or 50%),
we will want to area weight the data to try our best to compare apples to
apples.

/r/b

On Wed, Mar 14, 2018 at 3:38 PM, Joseph Kleiner <jkl...@vt...> wrote:

> Thanks Alyssa,
>
> I would say YES for  "*each of the flow metrics we have been calculating,
> we should have a map of all the river segments with their flow metric data
> and error and have each color correspond to a range of model error
> percentages"*
>
> As for the differences in drainage area I believe we're talking about the
> DA of the gages and the DA of the model segments, which we might not expect
> to be identical if the gages do not exactly coincide with the model segment
> outlets. So this should be 'okay' just understanding for these cases we'll
> need to think about area-weighting the flows to have a better comparison of
> gage flow to model flow.
>
> -J
>
>
>
>
> On Wed, Mar 14, 2018 at 2:43 PM, Alyssa Ford <aly...@vt...> wrote:
>
>> Hi everyone,
>>
>>
>>
>> I tried to send this email the Friday before spring break but I got some
>> messages back saying that there was a fatal error, so I am trying again.
>> Hopefully it goes through this time.
>>
>>
>>
>> Thanks,
>>
>> Alyssa Ford
>>
>>
>>
>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
>> Windows 10
>>
>>
>>
>> *From: *Alyssa Ford <aly...@vt...>
>> *Sent: *Friday, March 2, 2018 2:27 PM
>> *To: *WOOOMM <nps...@li...>
>> *Subject: *Update
>>
>>
>>
>> Hi everyone,
>>
>>
>>
>> This past week I have mostly been working on running the model for all of
>> the river segments. Like Rob pointed out last meeting, if I run a river
>> segment, it will also run all of the river segments upstream of the one
>> being run, so I there are only a few I need to run, but they each take a
>> very long time since they contain so much information. I have also used the
>> readNWISsite tool in R to get the drainage area of each river segment. Here
>> is a link to the sheet with all the river segments:
>>
>>
>>
>> https://docs.google.com/spreadsheets/d/1py-TXac7-iuTlanYc25x
>> rFCdfrw8HYQFDfMdWCEdYJw/edit#gid=0
>>
>>
>>
>> After break, I plan to run the last of the river segments and work on
>> maps for each of the flow metrics. Rob, you said you wanted a map of the
>> model error in each gage watershed indicated in color. Does this mean that
>> for each of the flow metrics we have been calculating, we should have a map
>> of all the river segments with their flow metric data and error and have
>> each color correspond to a range of model error percentages? Here is a link
>> to the sheet containing all the flow metrics we have been calculating:
>>
>>
>>
>> https://docs.google.com/spreadsheets/d/1FmdlOGhmLWTOo6TQoe74
>> kVdGTvi8TdchqOGjLn6BJeE/edit#gid=0
>>
>>
>>
>> Hopefully, Alex and I will finish up calculating all of these after
>> break.
>>
>>
>>
>> I have also noticed that there is a slight difference between the
>> drainage area according the the USGS data and the river segments in GIS. I
>> have only calculated the drainage area in GIS for 3 river segments, and the
>> percent difference is around 10% for two of them, but for the third it is
>> 46%. I do not know if this is an issue or not, but I just thought I would
>> mention it in case anyone has thoughts.
>>
>>
>>
>> Thanks,
>>
>> Alyssa Ford
>>
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Npsource-wooomm mailing list
>> Nps...@li...
>> https://lists.sourceforge.net/lists/listinfo/npsource-wooomm
>>
>>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Npsource-wooomm mailing list
> Nps...@li...
> https://lists.sourceforge.net/lists/listinfo/npsource-wooomm
>
>


-- 
--
Robert W. Burgholzer
 'Making the simple complicated is commonplace; making the complicated
simple, awesomely simple, that's creativity.'  - Charles Mingus
Athletics: http://athleticalgorithm.wordpress.com/
Science: http://robertwb.wordpress.com/
Wine: http://reesvineyard.wordpress.com/

Re: [Npsource-wooomm] FW: Update

[Joseph K. <jkl...@vt...>]

Thanks Alyssa,

I would say YES for  "*each of the flow metrics we have been calculating,
we should have a map of all the river segments with their flow metric data
and error and have each color correspond to a range of model error
percentages"*

As for the differences in drainage area I believe we're talking about the
DA of the gages and the DA of the model segments, which we might not expect
to be identical if the gages do not exactly coincide with the model segment
outlets. So this should be 'okay' just understanding for these cases we'll
need to think about area-weighting the flows to have a better comparison of
gage flow to model flow.

-J




On Wed, Mar 14, 2018 at 2:43 PM, Alyssa Ford <aly...@vt...> wrote:

> Hi everyone,
>
>
>
> I tried to send this email the Friday before spring break but I got some
> messages back saying that there was a fatal error, so I am trying again.
> Hopefully it goes through this time.
>
>
>
> Thanks,
>
> Alyssa Ford
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
>
>
> *From: *Alyssa Ford <aly...@vt...>
> *Sent: *Friday, March 2, 2018 2:27 PM
> *To: *WOOOMM <nps...@li...>
> *Subject: *Update
>
>
>
> Hi everyone,
>
>
>
> This past week I have mostly been working on running the model for all of
> the river segments. Like Rob pointed out last meeting, if I run a river
> segment, it will also run all of the river segments upstream of the one
> being run, so I there are only a few I need to run, but they each take a
> very long time since they contain so much information. I have also used the
> readNWISsite tool in R to get the drainage area of each river segment. Here
> is a link to the sheet with all the river segments:
>
>
>
> https://docs.google.com/spreadsheets/d/1py-TXac7-
> iuTlanYc25xrFCdfrw8HYQFDfMdWCEdYJw/edit#gid=0
>
>
>
> After break, I plan to run the last of the river segments and work on maps
> for each of the flow metrics. Rob, you said you wanted a map of the model
> error in each gage watershed indicated in color. Does this mean that for
> each of the flow metrics we have been calculating, we should have a map of
> all the river segments with their flow metric data and error and have each
> color correspond to a range of model error percentages? Here is a link to
> the sheet containing all the flow metrics we have been calculating:
>
>
>
> https://docs.google.com/spreadsheets/d/1FmdlOGhmLWTOo6TQoe74kVdGTvi8T
> dchqOGjLn6BJeE/edit#gid=0
>
>
>
> Hopefully, Alex and I will finish up calculating all of these after break.
>
>
>
> I have also noticed that there is a slight difference between the drainage
> area according the the USGS data and the river segments in GIS. I have only
> calculated the drainage area in GIS for 3 river segments, and the percent
> difference is around 10% for two of them, but for the third it is 46%. I do
> not know if this is an issue or not, but I just thought I would mention it
> in case anyone has thoughts.
>
>
>
> Thanks,
>
> Alyssa Ford
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Npsource-wooomm mailing list
> Nps...@li...
> https://lists.sourceforge.net/lists/listinfo/npsource-wooomm
>
>

[Npsource-wooomm] FW: Update

[Alyssa F. <aly...@vt...>]

Hi everyone, 

I tried to send this email the Friday before spring break but I got some messages back saying that there was a fatal error, so I am trying again. Hopefully it goes through this time. 

Thanks, 
Alyssa Ford 

Sent from Mail for Windows 10

From: Alyssa Ford
Sent: Friday, March 2, 2018 2:27 PM
To: WOOOMM
Subject: Update

Hi everyone, 

This past week I have mostly been working on running the model for all of the river segments. Like Rob pointed out last meeting, if I run a river segment, it will also run all of the river segments upstream of the one being run, so I there are only a few I need to run, but they each take a very long time since they contain so much information. I have also used the readNWISsite tool in R to get the drainage area of each river segment. Here is a link to the sheet with all the river segments:

https://docs.google.com/spreadsheets/d/1py-TXac7-iuTlanYc25xrFCdfrw8HYQFDfMdWCEdYJw/edit#gid=0 


After break, I plan to run the last of the river segments and work on maps for each of the flow metrics. Rob, you said you wanted a map of the model error in each gage watershed indicated in color. Does this mean that for each of the flow metrics we have been calculating, we should have a map of all the river segments with their flow metric data and error and have each color correspond to a range of model error percentages? Here is a link to the sheet containing all the flow metrics we have been calculating:

https://docs.google.com/spreadsheets/d/1FmdlOGhmLWTOo6TQoe74kVdGTvi8TdchqOGjLn6BJeE/edit#gid=0

Hopefully, Alex and I will finish up calculating all of these after break. 

I have also noticed that there is a slight difference between the drainage area according the the USGS data and the river segments in GIS. I have only calculated the drainage area in GIS for 3 river segments, and the percent difference is around 10% for two of them, but for the third it is 46%. I do not know if this is an issue or not, but I just thought I would mention it in case anyone has thoughts. 

Thanks, 
Alyssa Ford 

[Npsource-wooomm] Tomorrow's meeting

[<al...@vt...>]

Hey everyone,

I won’t be able to make it to the meeting tomorrow due to a traveling issue.  My friends car broke down, so I need to catch a train early in the morning.  I hope everyone has a good break!

Alex Domiano


Alex Domiano
Virginia Tech Class of 2019
Biological Systems Engineering
Green Engineering Minor

Re: [Npsource-wooomm] Sick this week

[Burgholzer, R. (DEQ) <Rob...@de...>]

Quarantine!

From: Elaina Passero [mailto:pas...@vt...]
Sent: Thursday, February 15, 2018 2:37 PM
To: WOOOMM
Subject: [Npsource-wooomm] Sick this week

Hi everyone,

I've been pretty sick this week and I'm trying to avoid spreading germs as much as possible. I'll most likely be calling in from home tomorrow. I'm sorry I haven't contributed much this week, I been a little out of it. I feel that I am on the mend though! I will talk to you all tomorrow.

Best,
Elaina

Re: [Npsource-wooomm] Sick this week

[Joseph K. <jkl...@vt...>]

No worries Elaina, thanks for the heads up.
Hope you're feeling better soon!


-Joey


On Thu, Feb 15, 2018 at 2:36 PM, Elaina Passero <pas...@vt...> wrote:

> Hi everyone,
>
> I've been pretty sick this week and I'm trying to avoid spreading germs as
> much as possible. I'll most likely be calling in from home tomorrow. I'm
> sorry I haven't contributed much this week, I been a little out of it. I
> feel that I am on the mend though! I will talk to you all tomorrow.
>
> Best,
> Elaina
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Npsource-wooomm mailing list
> Nps...@li...
> https://lists.sourceforge.net/lists/listinfo/npsource-wooomm
>
>

[Npsource-wooomm] Sick this week

[Elaina P. <pas...@vt...>]

Hi everyone,

I've been pretty sick this week and I'm trying to avoid spreading germs as
much as possible. I'll most likely be calling in from home tomorrow. I'm
sorry I haven't contributed much this week, I been a little out of it. I
feel that I am on the mend though! I will talk to you all tomorrow.

Best,
Elaina

Re: [Npsource-wooomm] Flow Metrics

[Alex D. <al...@vt...>]

Great thanks!  We will work on that next week. Have a great weekend.

Alex

On Feb 9, 2018 4:24 PM, "Robert Burgholzer" <rbu...@vt...> wrote:

> Hey guys - I just copied the relevant stuff from this thread onto Github -
> let's continue there: https://github.com/HARPgroup/cbp_wsm/issues/11
>
> On Fri, Feb 9, 2018 at 4:19 PM, Robert Burgholzer <rbu...@vt...> wrote:
>
>> Sweet!  BTW - I have a great opportunity for you guys: writing monthly
>> %ile code in R :).  Turns out that I HAVE that code (it is pasted below),
>> so you will need to adapt it a bit, but it is straightforward (and a
>> fantastic skill to have).  As for the DROUGHT OF RECORD flow, that code is
>> all ready for you to copy nad paste (it is also below).
>>
>>
>> *Algorithm: MONTHLY NON-EXCEEDENCE % (i.e. the September 10% flow)*
>> 1. Load your data into a frame -- // all_flows is the complete flow
>> record in a dataset  -- T
>> 2. Make sure your data has a month column --  THIS IS THE PART YOU ALL
>> NEED TO CHANGE (set a month or some other clever method that you all can
>> figure)
>> 3. You may need a different method for USGS and CBP Model output?
>> 4. Extract flows for the month of intertest -- i.e.
>>      sep_flows = subset(all_flows, "month == 9");
>> 5. Run the quantile function once you have a vector of september flows,
>> i.e.:
>>      x10 <- quantile(sep_flows,0.10);
>>
>> *Working Code: DROUGHT OF RECORD FLOW*
>>     loflows <- group2(flows);
>>     l90 <- loflows["90 Day Min"];
>>     ndx = which.min(as.numeric(l90[,"90 Day Min"]));
>>     dor_flow = round(loflows[ndx,]$"90 Day Min",1);
>>     dor_year = loflows[ndx,]$"year";
>>
>>
>>
>> On Fri, Feb 9, 2018 at 2:56 PM, Alex Domiano <al...@vt...> wrote:
>>
>>> Sounds good, also the crop cover code worked.  Thanks.
>>>
>>> Alex
>>>
>>> On Fri, Feb 9, 2018 at 2:48 PM, Robert Burgholzer <rbu...@vt...>
>>> wrote:
>>>
>>>> Yup — good thinking.
>>>>
>>>> On Fri, Feb 9, 2018 at 2:43 PM Alex Domiano <al...@vt...> wrote:
>>>>
>>>>> Hey everyone,
>>>>>
>>>>> During the meeting today we talked about including the September
>>>>> drought warning flow along with our 7Q10 and ALF analysis.  Do we also want
>>>>> to try and include the drought of record metric and try to knock out all of
>>>>> the metrics listed in the step-3 document?  If so, it says on there that
>>>>> Rob and IHA have written code to find that data, would you be able to
>>>>> provide that along with the September 10% code?
>>>>>
>>>>> Alex
>>>>> ------------------------------------------------------------
>>>>> ------------------
>>>>> Check out the vibrant tech community on one of the world's most
>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot______
>>>>> _________________________________________
>>>>> Npsource-wooomm mailing list
>>>>> Nps...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/npsource-wooomm
>>>>>
>>>> --
>>>> --
>>>> Robert W. Burgholzer
>>>>  'Making the simple complicated is commonplace; making the complicated
>>>> simple, awesomely simple, that's creativity.'  - Charles Mingus
>>>> Athletics: http://athleticalgorithm.wordpress.com/
>>>> Science: http://robertwb.wordpress.com/
>>>> Wine: http://reesvineyard.wordpress.com/
>>>>
>>>> ------------------------------------------------------------
>>>> ------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>> _______________________________________________
>>>> Npsource-wooomm mailing list
>>>> Nps...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/npsource-wooomm
>>>>
>>>>
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Npsource-wooomm mailing list
>>> Nps...@li...
>>> https://lists.sourceforge.net/lists/listinfo/npsource-wooomm
>>>
>>>
>>
>>
>> --
>> --
>> Robert W. Burgholzer
>>  'Making the simple complicated is commonplace; making the complicated
>> simple, awesomely simple, that's creativity.'  - Charles Mingus
>> Athletics: http://athleticalgorithm.wordpress.com/
>> Science: http://robertwb.wordpress.com/
>> Wine: http://reesvineyard.wordpress.com/
>>
>
>
>
> --
> --
> Robert W. Burgholzer
>  'Making the simple complicated is commonplace; making the complicated
> simple, awesomely simple, that's creativity.'  - Charles Mingus
> Athletics: http://athleticalgorithm.wordpress.com/
> Science: http://robertwb.wordpress.com/
> Wine: http://reesvineyard.wordpress.com/
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Npsource-wooomm mailing list
> Nps...@li...
> https://lists.sourceforge.net/lists/listinfo/npsource-wooomm
>
>