As a numpy user myself I am looking forwards to Thursday's meeting.  I am 
trying to recruit 1-3 matlab and java coworkers to come as well.  

That traffic shouldn't affect me (maybe us).

Regards,
Ben Racine

________________________________________
From: [email protected] 
[[email protected]] On Behalf Of Matt Stumbaugh 
[[email protected]]
Sent: Tuesday, November 16, 2010 12:22 AM
To: SEAPY
Subject: [SEAPY] Fwd:  November meeting confirmed

Hey all,

Chris and I will be talking about numpy on Thursday.  That said, I
can't tell if I'm getting nervous b/c we're on the hook for that or if
it's that combined with the potential traffic mayhem some of us may
encounter trying to get from NE Seattle to Office Nomads and back.  I
definitely look forward to discussing numpy but I'm pretty
apprehensive about the traffic (Metro is going to be rerouting the
68/372/31 lines starting at 2:30 pm).  I hate to potentially mess up
the meeting planning nor do I want to say let's re-schedule (though my
gut tells me it would be wise)... so I'm looking for some objective
metric by which to make the decision (not that it's really mine to
make) or gain some peace that it's going to be alright.  To that end,
I'm wondering
1) how many are planning on attending?
2) how many will be departing from/returning to north of 520 or the east side?
3) how many will just decide to skip it b/c traffic is going to be too painful?
4) your thoughts?

Here are some links that discuss the associated traffic:

http://metrocommute.wordpress.com/2010/11/15/thursday-night-husky-game-expect-uw-area-transit-service-delays-campus-reroutes/?utm_source=twitterfeed&utm_medium=twitter

http://metro.kingcounty.gov/up/rr/reroutes.html

http://blog.seattlepi.com/huskies/archives/227886.asp

Not directly relevant but interesting,
http://www.wsdot.wa.gov/Northwest/King/ExpressLanes/I-5HuskyGames.htm

Go Dawgs!  (Don't hate b/c they're screwing up our traffic :-)

Matt

---------- Forwarded message ----------
From: Matt Stumbaugh <[email protected]>
Date: Sat, Nov 13, 2010 at 1:35 AM
Subject: Re: [SEAPY] November meeting confirmed
To: Mike Orr <[email protected]>


> So it's at Office Nomads, not the UW.

Yeah, I realized that but was thinking it's going to be a nasty p.m.
for car or transit.  Especially problematic if one is coming from
north of 520.  And getting back north or east on 520 will be bad too.
I can man up and get there but think there may be some major headaches
for anyone planning on getting to/from the meeting between 3:30 to
10:30 pm.

On Fri, Nov 12, 2010 at 3:31 PM, Mike Orr <[email protected]> wrote:

>
> On Fri, Nov 12, 2010 at 11:06 AM, Matt Stumbaugh
> <[email protected]> wrote:
>> Hey Mike,
>>
>> I'm a bit concerned that next Thursday is going to present some
>> serious transportation problems with a Husky game on Montlake from
>> 5:30-9 (not to mention rush hour).  Do you have an opinion on this or
>> do you want to query the seapy folks (or me to do so)?
>>
>> Thanks,
>> Matt
>>
>> On Thu, Oct 28, 2010 at 11:37 AM, Christopher Barker
>> <[email protected]> wrote:
>>> On 10/28/10 10:35 AM, Mike Orr wrote:
>>>>
>>>> The November meeting will be on November 18th, a week later than usual
>>>> due to Veteran's Day. That's the week before Thanksgiving. The meeting
>>>> will be at Office Nomads, 7-9pm.
>>>>
>>>> Chris Barker will give his long-awaited talk about NumPy.
>>>
>>> Make that Chris Barker and Matt Stumbaugh.
>>>
>>>> Chris, can
>>>> you remind us what specifically you'll be covering?
>>>
>>> We haven't nailed down the outline yet, but we'll introduce numpy, discuss
>>> why you'd want to us it (even if you aren't crunching numbers), and show
>>> some nifty examples.
>>>
>>> We'll put a more detailed outline in the Wiki at some point.
>>>
>>> -Chris
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Christopher Barker, Ph.D.
>>> Oceanographer
>>>
>>> Emergency Response Division
>>> NOAA/NOS/OR&R            (206) 526-6959   voice
>>> 7600 Sand Point Way NE   (206) 526-6329   fax
>>> Seattle, WA  98115       (206) 526-6317   main reception
>>>
>>> [email protected]
>>>
>>
>
>
>
> --
> Mike Orr <[email protected]>
>

Reply via email to