Skip to main content

Boston Commute

I commute between the Malden area and the Longwood area. There are several ways to solve this problem:
  1. Orange Line to Ruggles (30min) + walk (10-15min) ~ 45min
  2. Orange line to Ruggles + Free Longwood area shuttle (No ID required) - 35min to 45min
  3. Orange line to Ruggles + Bike (Haven't tried this, wouldn't work during peak)
  4. Orange line to North Sta (15min) + Green (Heath) to Longwood (20min to 1hr)
  5. Orange line to Ruggles (30min) + walk one block (5min) + Green (Heath) to Longwood (10min to 20min)
The Green line is a bit of a crapshoot. Some days its just fine, some days it crawls. The commute is faster/more reliable if you can put it out of the equation. The Orange line is fast, reliable, and during peak hours, very frequent. I would say near Malden, about 1 every 5min. In the evening, at North Station, perhaps one every 10min

The great thing about trains is that you can read on 'em. I get a paper a trip (about), which is decent.
Labels:

Comments

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...
Post a Comment
Read more

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty...
Post a Comment
Read more