Scheduling Process Started

Everyone who has helped out in the Herring Counting Program in prior years was asked if they could help count again this year. This email went out late yesterday and we've have received 15 replies so far, which is good!

We'll be using the same Google Docs spreadsheets for scheduling/counting as we did in 2010, with things being a little easier this year as the counter will not have to have a Google account or sign-in to access their spreadsheet.

As we did last year, we'll use the early responders and schedule just the first couple of weeks. Then as more people respond we'll schedule the rest of the run.

What Happened In 2010?
I'll gather and chart some statistics sometime over the next few weeks, but my posts at the time [April 2010] highlighted my concern about the volume and velocity of the water traveling through the pipe under Route 28 from Mill Pond. This was due to the very heavy rains we had in late March and early April, which I feel was too much for the herring to overcome.

The flaw in the design of the herring run at Mill Pond is that while there is a ladder to allow the herring to climb the change in elevation, there's no way to control the volume [and therefore the velocity] of water that travels through the pipe used by the fish. And the pipe is 175+ long and there's no pool for the herring to rest/regroup.

Over the winter I did a bit of research about the velocity that herring can overcome and what they do when confronted with this [or by some other obstruction]. That will be the topic of a later post.

We're going to watch this element of the run this year very closely. If you want to help out in this velocity testing, please let me know [we need someone at both ends of the pipe]. We'll do this only if we get heavy rains, but I'll be keeping a daily log of the height of the water traveling through the pipe.

If there's an engineer out there who could tell me how to figure this out [with the diameter of pipe, inches of water, change in elevation, and whatever other input might be needed] I'd appreciate it - as that would be much easier then the current method of timing ping-pong balls...