Skip to main content

Lead

Lead paint is a scary topic, especially in Massachusetts where a lot of the housing is old. Lead paint is also a complex topic. Because the effects of lead paint on children and adults are dire and since many children have suffered permanent disability because of exposure to lead paint, state and federal governments take a very proactive and cautious stance regarding lead paint. The authoritative sources are your state and federal websites dedicated to lead paint issues (some links are below).
Apparently lead was added to paint because it enhanced its longevity and was government sanctioned. This same website states that the dangers of lead paint began to be realized in the 30s and 40s and in 1955 paints that were to be used in home interiors were restricted to less than 1% by weight of lead. Lead paint was also expensive and used mostly for living rooms and window sills and other locations where durability and quality were important.
From the EPA and state materials (which, again, are the materials you should refer to) it seems that the biggest risk is from chipping and peeling paint which can be eaten by children (they like the sweet taste) and dust from lead paint released from windows and door jambs. If paint is in good condition it is of lower risk and can be painted over and encapsulated as far as I could understand. Again, this is a complex, thorny topic with the health of children at stake, so even though it takes time, please go through the official documentation.
A common question is trying to judge the risk of lead paint based on the age of the house. The most common cut-off is 1978. Houses built before 1978 are assumed to have lead paint and there are some rules that govern the purchase and sale of such houses. Before 1955 paints contained as much as 50% by weight of lead. This was reduced to 1% by weight in 1971 (by the Feds) and then, since 1977, the limit is 0.06% by weight. Massachusetts uses 1950 as a criterion for 'old' houses as far as lead goes. This EPA page has a rough graph showing the percentage of homes having lead paint by year of construction.
Resources:
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

Remove field code from Word document

e.g. before submitting a MS, or hand manipulating some formatting because Word does things (like cross-references) so half-assed [from here ] Select all the text (CTRL-A) Press Ctrl+Shift+F9 Editing to remove anonymous comments that only contain thanks. I really appreciate the thanks, but it makes it harder to find comments that carry pertinent information. I'm also going to try and paste informative comments in the body of the post to make them easier to find.
24 comments
Read more

h5py and multiprocessing

The HDF5 format has been working awesome for me, but I ran into danger when I started to mix it with multiprocessing. It was the worst kind of danger: the intermittent error. Here are the dangers/issues in order of escalation (TL;DR is use a generator to feed data from your file into the child processes as they spawn. It's the easiest way. Read on for harder ways.) An h5py file handle can't be pickled and therefore can't be passed as an argument using pool.map() If you set the handle as a global and access it from the child processes you run the risk of racing which leads to corrupted reads. My personal runin was that my code sometimes ran fine but sometimes would complain that there are NaNs or Infinity in the data. This wasted some time tracking down. Other people have had this kind of problem [ 1 ]. Same problem if you pass the filename and have the different processes open individual instances of the file separately. The hard way to solve this problem is to sw...
Post a Comment
Read more