Skip to main content

Central Vacuum Systems

We have a Nutone range hood and need to replace/repair some parts. I was looking over the Nutone website and I came across a reference to "central vacuum systems". A quick web search (with images) caused jaw drop. 

 In case you haven't caught on already (or have caught on but are thinking, "No Way! They got people to install this in their home?") , this involves installing a powerful vacuum motor in the house and then running a system of vacuum ducts into different rooms terminating at vacuum outlets. You then attach a hose to the outlet and vacuum the rooms.

 Of course, you could do this. Is it genius? I think it's genius that you can get people to install yet another set of ducts in the walls of their home. Another set of ducts that can clog up, needs maintenance and, when things go wrong, as they will, dry wall cutting and replacement and repainting.

 What are the benefits of doing this? Well, you could install an amazingly powerful vacuum motor that you couldn't otherwise use on a portable vacuum (but would you want to?). You don't have to lug that heavy vacuum around anymore. And potentially, you are insulated from the motor noise.

 The downsides? Well, you got yet ANOTHER set of outlets in your walls now. And you need some kind of switch at every outlet (I'm sure the vacuum motor is not on all the time) so you need to run more wiring from your rooms to a central location - yet more stuff to go wrong. And everytime you vacuum a room this POWERFUL motor ramps up - even more electricity being eaten. And what happens when everyone decides to vacuum at the same time.

 I know, I know, 20 years later I'll be put on the same pile as those guys who laughed at electricity being piped around in homes, or who laughed at modern plumbing  ...
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