Glue on Paper

Last summer I assigned my son, then six years old, to do an “inquiry.” Inquiries are guided studies of something, and empirical inquiries are like mini science fair projects. At the time I asked him to pick a topic he selected “how does glue work?” Exploring this at the chemistry level seemed like too big a reach for a 6 year old, so we morphed the question into “how well do different kinds of glue work?”

It turned out to be a really fun experiment. We gathered all the not-too-toxic glues from around the house. The oxiclean container has methyl cellulose inside.

image

He glued several trials of each paper together as crosses. Then, he brought the ends of the paper together and clamped, one piece of paper to a board hanging over the edge of the desk, and the other piece to bucket. In the picture below you can see the test setup. The paper is like two U-shapes that are glued where the come together. They don’t loop inside one another, they are held together only with glue. The glue joint area was approximately 1 inch square.

20120708-03

He added weight to the bucket until the paper failed, and then weighed the bucket.

The glues and results are in the table below. The “r” indicates that the paper ripped, otherwise the glue joint failed across the surface. The best and worst are boldface.

# Glue Name

Average Weight Held (lbs.)

Trial 1 Trial 2 Trial 3
1 Elmer’s Glue Stick 1.52 1.096 1.234 1.222
2 PVA:Methyl Cellulose 1:1 vol. 2.37 3.064 2.888 2.062
3 Elmer’s Glue-All 3.39 3.270 3.944 (r) 2.928
4 Gorilla Glue 2.27 5.438 3.180 0.746
5 Methyl Cellulose 4.20 4.468 4.392 3.752
7 PVA 3.65 3.966 2.768 3.824
8 Titebond III 4.25 3.824 5.180 3.576
9 DAP Strongstick 1.54 1.460 1.562 1.576
10 Cyanoacrylate (Super Glue) 4.15 5.180 3.966 (r) 3.284 (r)

Most of these results fit my expectations. There were a few surprises though.

  • Gorilla glue (polyurethane) was typically quite strong, but once was very poor.
  • Methyl cellulose is usually considered a weak glue, but it performed almost as well as the best of them. Maybe it is strong in our dry climate and weaker in more humid climates?
  • Glues that soak in well (super glue and methyl cellulose) seem to have an advantage.

The test was essentially performing a sort of peel-off strength test. In many ways I think the setup was quite good. The stresses on the glue joint are fairly typical for what materials are stressed with.

I Don’t Tell You How to Do Your Job

This article begins with a story from my life, my fatherhood, about the time I was most afraid. The story ends happily with the birth of a healthy baby girl. The article, on the other hand, ends with an analysis showing how medical habit increased the threat to my daughter’s life by a factor of 20.

I learned the principals of acoustic imaging in my first professional job on an air-based passive sound imaging system, and on undersea sonar systems. These systems deal with inhomogeneous media, that is materials that aren’t the same throughout. The human body is an example of the inhomogeneous media, and ultrasound technicians are well aware of the challenges. The science of sonar has much in common with the science of ultrasound imaging.

At the end of June 2008 my wife was 27 weeks pregnant with our daughter. Her first pregnancy had been difficult because she had preeclampsia that deteriorated into HELLP syndrome around the time she was induced. Since the first pregnancy was medically complicated, the second pregnancy came with extra monitoring. She had more ultrasounds and more checkups than a typical pregnancy for a woman of her age.

She was given an ultrasound examination; I was there watching the screen. Part of the test included a cranial artery peak velocity measurement. This test was never prescribed, or at least we were later told there was no reason it should have been prescribed.  Systolic flow is the fastest; it occurs when the heart contracts to push blood throughout the body. To measure the peak systolic velocity of blood flow in the middle cerebral artery, the technician puts the ultrasound in Doppler mode, and then carefully tries to hit a tiny moving target inside another person. That is, to hit a tiny moving target inside the person who is inside the person. The technician must align the ultrasound transducer’s boresight with the artery, to measure the Doppler flow accurately. This is a difficult ultrasound procedure. It took, if I recall correctly, about 15 minutes to generate the single peak velocity number.

Unfortunately, at 54 cm/s the flow rate was considered a strong indicator for for fetal anemia or hydrops. The prescribed treatment for fetal anemia is a transfusion. To give the transfusion a long needle is inserted through the mother’s abdomen, the uterus wall, and into the umbilical cord, where specially treated (irradiated) blood elements can be injected. Ultrasound is used to guide the needle in.

The procedure is risky. About 50% of the time the injection causes the umbilical cord to spasm, cutting off oxygen to the fetus. If this happens treatment is an emergency Caesarian and the delivery of a 27 week old premature baby. The prognosis for life at 27 weeks is about 90% according to babycenter. The same site indicates that 25% of those who live will have serious lasting medical problems—like cerebral palsy. An additional 50% will have some kind of lasting problem.

In my entire life I have never been as afraid, or worried, as I was through the day that followed that diagnosis. My initial reaction was skepticism. I demanded that the doctor defend the diagnosis, that she provide evidence to me that diagnosis was real and accurate.

It is well that I did.

I don’t remember every word I exchanged with the doctor. I can remember sitting in her office, across her desk. I can remember meeting each of her assertions with questions. I cannot remember being uncivil or rude, but I was terrified and may have been. I remember when she answered one of my questions with “I don’t tell you how to do your job!”

The hospital mobilized irradiated blood, and prepared an operating facility, and a prepped a sunny young doctor who had seen fetal transfusion performed (but not recently).

My daughter did not have hydrops.

I believe my skepticism saved the life of my daughter. I do not forgive that doctor. Mistakes happen, and even when bad, frightening things happen to me, I can forgive that. But I will never forgive her arrogance, the casual way she reached a conclusion and decided that nobody, especially the client, had the right to challenge her. May she find justice.

To her credit, she did eventually share some data with me. We walked together to one room, and she unpinned a photocopied graph from the wall. She took it to the photocopier and gave me a copy. This graph.

20080623_CranialBloodFlowChart2

My questioning led them to delay the infusion by a day and to take an additional measurement. I watched the screen during the rest of the measurements. One ultrasound technician rotated the cart to block my view. I got up and walked around to see the screen. I challenged each of the technicians, and each of the doctors on the measurements. I pointed out that the measurement (54 cm/s) was on the threshold, not clearly over the threshold.

After the team of doctors and technicians finally decided that they could not repeat the high flow measurement, they continued looking. One doctor seized control of the transducer from the ultrasound technician and tried to examine my daughter’s thorax. She thought she could see a dark pocket (which could indicate hydrops). What she could see is a dark pocket, which in sonar is called a “shadow zone”. In this case the shadow zone appeared because the ultrasound had to pass obliquely through the fetus’s rib cage. The sound was refracted away from her abdomen leaving a dark region. The technician was appreciably better with the instrument than the physician.

The bull-dog tenacity was unbelievable. Given one incorrect diagnosis, the propensity to look, and look, and look for more problems is insane.

Analysis of Risk

Risk is a code word meaning that bad things might happen. It is calculated, usually, by counting the number of people to which bad things actually happened. Here I’ve annotated the graph with some numbers, I’ve marked my experience, and I’ve highlighted some samples. This is a very, very, small sample.

20080623_CranialBloodFlowChart2-annotated

By my count there are 8 “well fetuses” whose peak velocity exceeds 1.5 times the median. There are 34 anemic fetuses, all of whose peak measurements exceeded the threshold. By those counts, if you get a high measurement then the odds you are actually sick are about 80% (34/42).

Prevalence of hydrops among the western first world population is quite low. In a study at a single hospital in Belfast, of 25,443 live babies 35 had fetal hydrops, or a prevalence of 1.34/1000. Presumably this excludes stillbirths, which in the U.S. account for 1 in 115 (much, much more prevalent than fetal hydrops live births).  The best data I could find for the rate hydrops among stillbirths is from the Arizona Department of Health Services, which reported 6 of 158 still births to be due to, or coincident with, hydrops.

For purposes of this discussion, assume that:

  • Hydrops affects 1.34/1000 live births
  • 8.7/1000 are stillborn
  • Of that 8.7/1000, Hydrops affects 3.8% of still births, or 0.33/1000 births
  • Thus, hydrops has a prevalence among all pregnancies of about 1.67/1000

Prognosis if the fetus has hydrops is poor, with about a 90% morbidity rate according to  Yong, a crude approximation that is still reasonable if accounting for non-immune and immune hydrops. The data I have is not very strong, rates vary wildly.

First, let us assume Eve has taken a break from her cryptanalysis work and is now pregnant. There is a small chance that Eve’s fetus has hydrops, 1.67/1000.  Her physician sends her for an ultrasound. Due to poor handwriting her fetus is given a cerebral artery peak systolic Doppler ultrasound.

Suppose that Eve’s fetus has hydrops (she was part of the 1.67 of 1000). The ultrasound shows this correctly since there are no false negatives in the chart above. The doctors order a transfusion, which has all kinds of possible complications. We’ll ignore those complications, and just assume that Eve’s fetus has a 10% chance of survival—hydrops isn’t really very curable. She will spend a lot of money, and a lot of fear on procedures. It is not clear if these treatments change the outcomes at all (see, for example, Gynekol 1996 abstract).

Suppose that Eve’s fetus does not have hydrops, which is the much more likely case of 998.33/1000. The ultrasound correctly reports “no hydrops” 81% of the time (34 of 42 dots on the graph). Unfortunately, Eve is part of the other 19%, and the test says her fetus is hydropic. She follows her doctor’s stern council, and has an intrauterine transfusion. This is a gamble, and here are her odds (again from babycenter).

Likelihood Outcome
4% Caesarian, child dies
10% Caesarian, very bad health (e.g. cerebral palsy)
21% Caesarian, poor health
11% Caesarian, good health
51% Transfusion succeeds

The main downside of a successful transfusion is cost, though there are probably rare cases of immune responses or transfusion induced illness. Eve’s cryptography work has grossed her lots of off-book income, so ignore the dollar cost of the operation. Furthermore, assume she does not contract MRSA in the hospital.

Eve had a test. If she had hydrops she changed the prognosis of her child almost none. If she did not have hydrops, she subjected herself and her fetus to really bad risks with no possible benefit.

Consider the population of Eves. Suppose that the doctors test every woman for hydrops. Disregarding the dollar cost, we have increased the risk of pregnancy so that 19% of pregnancies will result in hydrops treatments, of which 49% will result in very early preemies, of which 35% will have severe complications. In other words, testing has replaced the risk of hydrops (1.67/1000) with the risk of misdiagnosis and severe complications 32.6/1000. Testing every woman would increase the US infant mortality rate from 6.81/1000 to about 10.5/1000.

Doctors don’t have much negative risk in treatment. It isn’t their baby, it isn’t their money. Action is to their advantage, it may further their career if the action is relatively experimental. It may further their wealth if they are paid for procedures.

I believe all doctors I have ever met, and probably almost all doctors believe they are doing good. The pressure of this incentive system pushes slowly and gently toward more medical actions. It pushes common practice, the habit of treatment toward more procedures and more tests, regardless of their benefit to the patients.

I am not the first to suggest there is an issue. One indication of overtreatment is the rate at which doctors will cure themselves. Some studies indicate that doctors will undergo some procedures 1/2 to 1/5th as often as the general population. Why does the entire equation change when they have skin in the game? Would you bet the incentive structure is that different?

Would you bet your baby’s life?

Does the Bathroom Fan Do Anything?

Other than make noise, that is. I built the most recent version of my Arduino-based data logger (the RIMU), and was looking for something to log. I’ve had this question for many, many years—does the bathroom fan actually do anything? It makes noise, deafening Niagara falls thundering noise. The mirror still gets foggy, though, and condensation still forms on the fixtures. Is there something good about all that noise?

Investigating this with the RIMU is more difficult than you might think. First, it is hard to control the variables. I recorded about seven days’ worth of data before I got two records that had similar enough baselines to separate the effects of the fan. Second, the analysis had so many measurements to work with.

Our bathroom is modest in size, with a counter and sink on one side and the shower on the opposite. The RIMU was sitting on the counter.

Humidity

The plot below shows the relative humidity over time. At approximately time zero I turned on the light. Shortly thereafter I turned on the shower, and the humidity began to rise. Weirdly, the humidity rose in a very similar fashion for the first few minutes. Probably the separation is when I climbed into the shower. I speculate that the dip at six minutes in the green “fan off” curve is climbing into the shower too. Opening the shower door, it seems, sets up different air currents.

humidity

One conclusion, clearly, is that the fan actually keeps the humidity under about 90%, instead of letting it rise to 100%. Another conclusion is that, compared to leaving the bathroom door open, the fan is really ineffective. A third conclusion is that the sound and light data are actually more interesting than the humidity data.

Light

The TSL chip that I use to sense light is quite a wonderful little device. It has controllable integration time. The idea is that if it there is a low light level the sensor can record longer to provide a better estimate of the actual level. In the RIMU I try to auto-tune the integration time. If the reading is very low, I increase the integration time, if it is very high, I decrease it. Unfortunately, when I programmed the RIMU I did not realize that the TSL library was providing measurements that had to be corrected for the integration time (counts, not Lux).

That brings us to the first interesting observation. In the blue “fan on” trace, there is a really whopping spike in the light level. What is actually happening is that there is a recorded measurement before the TSL integration time is reduced.

The second cool observation is that you can see the fluorescent lights increase their output as they warm up. I knew, intellectually, that this was happening—my scanner won’t scan until its fluorescent tube has warmed up. I always thought that was a 20 second process, not a three minute process.

The third cool observation is the visible background in the green “fan off” line. I took that recording on a Saturday morning, and the natural daylight trend is visible in the background.

light

Sound

The RIMU code runs in a constant loop, as fast as it can. The downside is that the sample rate on a polled sensor is whatever it can provide—not a specific value that you wish. RIMU records a sample to the SD card about every 10 seconds. In between it takes a reading of the sound pressure level as often as possible, and then averages them. The average is a moving average implemented with a single pole infinite impulse response filter. This is the simplest filter of all, something like

SPLaverage = SPLaverage*0.99 + measurement*0.01

sound_level

The first observation is that the moving average is not very cleverly implemented. The response time is nearly 3 minutes—something like 10 seconds would have been better.

The second interesting thing to observe is how unimaginably loud the fan is. The fan more than doubles the sound level compared to the water flow. The noise during shaving is due to turning on the faucet, which was very close to the RIMU.

Temperature

The temperature in both trials increased an average of about 2 degrees Fahrenheit. The fan may provide some mixing of the air, that keeps the temperature more even—the blue “fan on” line rises much less than the green line.

temp

Conclusion

Yep. The fan does something. If controlling humidity is really important (is it?) then you should just leave the door open. If you can’t leave the door open, turn on the fan.

Revised Raspberry Pi TrueCrypt Benchmark

Revised March 31, 2013 with updated benchmarking approach that uses actual access to the mounted volume. New results show no appreciable sensitivity to hash, which is as expected. The numbers are for encryption only (write). I have not pursued read.

Hash
Algorithm
Encryption
Algorithm
Rate
(MB/s)
SHA-512 Twofish 2.8
Whirlpool Twofish 2.8
RIPEMD-160 Twofish 2.8
SHA-512 Serpent 2.6
Whirlpool Serpent 2.6
RIPEMD-160 Serpent 2.6
Whirlpool AES 2.1
RIPEMD-160 AES 2.1
SHA-512 AES 2.1
SHA-512 Twofish-Serpent 2.0
Whirlpool Twofish-Serpent 2.0
RIPEMD-160 Twofish-Serpent 1.9
SHA-512 AES-Twofish 1.6
RIPEMD-160 AES-Twofish 1.6
Whirlpool AES-Twofish 1.6
Whirlpool Serpent-AES 1.6
SHA-512 Serpent-AES 1.6
RIPEMD-160 Serpent-AES 1.6
Whirlpool AES-Twofish-Serpent 1.3
Whirlpool Serpent-Twofish-AES 1.3
SHA-512 Serpent-Twofish-AES 1.3
SHA-512 AES-Twofish-Serpent 1.3
RIPEMD-160 Serpent-Twofish-AES 1.3
RIPEMD-160 AES-Twofish-Serpent 1.3

Shell Script for Timing


#!/bin/bash

# Create a file of random elements, needs to be at least 300 bytes
 dd if=/dev/random of=random bs=512 count=1

# Iterate over the hash hash funnctions
 for HASH in RIPEMD-160 SHA-512 Whirlpool
 do
 # Iterate over the available encryption algorithms
 for ENCALG in AES Serpent Twofish AES-Twofish AES-Twofish-Serpent Serpent-AES Serpent-Twofish-AES Twofish-Serpent
 do
 # Write the algorithms to the log
 echo "Algorithms: $HASH $ENCALG" >> log
 # TrueCrypt will report the performance in the output
 truecrypt -c /home/pi/test.tc --filesystem=fat --size=10485760\
 --encryption=$ENCALG -p ppp --random-source=random \
 --hash=$HASH --volume-type=normal --non-interactive
 # Mount the partition
 truecrypt --non-interactive -p ppp -m nokernelcrypto test.tc /home/pi/tcvol
 (time  ./timeit) 2>> log
 truecrypt -d /home/pi/tcvol
 # Erase the created file
 rm test.tc
 done
 done

Timed Routine


dd if=/dev/zero of=tcvol/test bs=5242880 count=1 &> /dev/null

sync

Python Reprocessor


import sys
 fid = open( sys.argv[1], 'r')
 lines = fid.readlines()
 fid.close()

tsecs = None
 while len( lines) > 0:
 line = lines.pop(0)
 lls = line.strip()

if lls.startswith( 'Algo'):
 # If we already have a tsecs, then print
 # the last elements
 toks = lls.split()
 if tsecs == None: # first record
 algo = ",".join( toks[1:3])
 else:
 print algo,",",tsecs
 algo = ",".join( toks[1:3])
 elif lls.startswith( 'real'):
 toks = lls.split()
 toks = toks[-1].split('m')
 tsecs = float( toks[0])*60 + float( toks[1].replace('s', ''))

print algo,",",tsecs

Raspberry Pi TrueCrypt Benchmark

Note: The results in this post have been improved with more accurate values at Revised Raspberry Pi TrueCrypt Benchmark.

I recently acquired a Raspberry Pi model B 512 MB from the excellent people at Adafruit. I am interested in it as a small computer for basic text processing, and am curious about its performance in consumer crypto. One part of the security of the Pi, or any modern computer, is disk encryption.

My disk encryption of choice is TrueCrypt, mainly because it is cross-platform. That it is also free and open source is a nice benefit, though the TrueCrypt3 license may not rise to Stallman’s standard. I found several posts from persons who compiled TrueCrypt on the RasPi, and it is relatively trouble free. At the bottom of the post are my notes on how I did the install and a script that performs the benchmarking.

While I don’t understand the relationship between the hashing function and the encryption function, I expected that speed would be unrelated to the hash algorithm. This was not what I experienced, as shown in the data below.

Performance, in MB seconds, as TrueCrypt reports for initializing a 10,000,000 byte file.

Hash Encryption Speed
(MB/s)
RIPEMD-160 Twofish 3.4
RIPEMD-160 Serpent 3
RIPEMD-160 AES 2.5
SHA-512 Twofish 2.5
RIPEMD-160 Twofish-Serpent 2.3
SHA-512 Serpent 2.2
SHA-512 AES 2
RIPEMD-160 AES-Twofish 2
RIPEMD-160 Serpent-AES 1.9
SHA-512 Twofish-Serpent 1.8
SHA-512 AES-Twofish 1.6
Whirlpool Twofish 1.6
RIPEMD-160 AES-Twofish-Serpent 1.5
Whirlpool Serpent 1.5
SHA-512 Serpent-AES 1.5
RIPEMD-160 Serpent-Twofish-AES 1.5
Whirlpool AES 1.4
SHA-512 AES-Twofish-Serpent 1.3
SHA-512 Serpent-Twofish-AES 1.3
Whirlpool Twofish-Serpent 1.3
Whirlpool AES-Twofish 1.2
Whirlpool Serpent-AES 1.2
Whirlpool Serpent-Twofish-AES 1
Whirlpool AES-Twofish-Serpent 0.934

The upshot is that all of these are pretty slow, and all of them would be essentially unnoticeable for basic text file (or RTF) work. I wouldn’t want to do image or audio processing with this encryption, but then I wouldn’t want to do that on a Pi anyway.

Method of Speed Assessment

I wanted a non-interactive way to perform the test, so I wrote this script. I am relying on the data reported by the TrueCrypt volume creation process. Because TrueCrypt writes a status to the terminal it produces output that is dreadful to process, so I wrote the little python script to produce a CSV from the log.

The test was performed with an ARMv6 compatible processor rev 7 (v61) at 464.48 BogoMIPS. The OS is Debian GNU/Linux 7.0 (Wheezy), which was installed as the 2013-02-09-wheezy-raspbian image. I built TrueCrypt from source for 7.1a along with wxWidgets 2.8.12 (also built from source) and pkcs version 11.2.

Shell Script

#!/bin/bash

# Create a file of random elements, needs to be at least 300 bytes
dd if=/dev/random of=random bs=512 count=1

# Iterate over the hash hash funnctions
for HASH in RIPEMD-160 SHA-512 Whirlpool
do
# Iterate over the available encryption algorithms
for ENCALG in AES Serpent Twofish AES-Twofish AES-Twofish-Serpent Serpent-AES Serpent-Twofish-AES Twofish-Serpent
do
# Write the algorithms to the log
echo “Algorithms: $HASH $ENCALG” >> log
# TrueCrypt will report the performance in the output
truecrypt -c /home/pi/test.tc –filesystem=fat –size=10485760\
–encryption=$ENCALG -p ppp –random-source=random \
–hash=$HASH –volume-type=normal –non-interactive >> log
# Erase the created file
rm test.tc
done
done

Python Reprocessor

import sys
fid = open( sys.argv[1], ‘r’)
lines = fid.readlines()
fid.close()

speed = None
while len( lines) > 0:
line = lines.pop(0)
lls = line.strip()

if lls.startswith( ‘Algo’):
# If we already have a speed, then print
# the last elements
toks = lls.split()
if speed == None: # first record
algo = “,”.join( toks[1:3])
else:
print algo,”,”,speed
algo = “,”.join( toks[1:3])
elif lls.startswith( ‘Done’):
toks = lls.split()
speed = “,”.join(toks[-5:-3])
print algo,”,”,speed

Bespoke Monitor Stand

I’m using two reams of paper to hold my monitor at the right height. These reams are totally functional. However, I’m trying to learn to make passable hand-cut dovetail joints and I had material from an old keyboard tray that does not fit with my office’s new furniture.

As a tangent, before starting this project I rebuilt the woodworking bench my grandfather gave me before he died. I think he would agree it was an expedient bench, and not an excellent bench. I’m glad to improve it. He made the bench top from unsanded 2×12 inch pine planks, with only moderate knots but with pretty awful warping.

I made my new bench top from his old one. I reground, honed, and lapped the blades, and squared the soles of the two jack planes I inherited. Then I planed out the cup, twist, and bow from the top surface. I planed the bottom surface to a lesser degree, but enough for the bench top to sit true.

I epoxied the handle back together on my inherited Bailey No. 7 jointer plane, reground the blade, honed the blade, and reground the chip breaker. Then I clamped the boards face-to-face, and squared the edges. I glued and clamped the top together, making it effectively a single solid piece of wood that was flatter and stiffer than it even had been.

It was connecting to use the hand planes I inherited, sharpened, lapped, and repaired the handles. More connection to square a benchtop I also inherited. I feel good that somewhere in the roughly 40 gallons of wood shavings (no exaggeration), are dents and oil stains my father made as a boy. And now my daughter and son are leaving dings in the new surface, and I feel good about that too.

20130303-123-2

I made bench dogs using oak dowel and springy stainless I repurposed from an old windshield wiper blade. The work great and cost about 25 cents a piece. Funny that I seriously considered buying brass ones at over $10 each until I learned how easy these are to make.

20130310-25-2-2

This post, though, is not really about the bench. The working bench was a nice foundation on which to build…a bespoke dovetail monitor stand.

Hand cut dovetails are not intellectually challenging. You can learn the concepts of how to do it with a few hours browsing tutorials. You need a good saw, but I made do with a mediocre one. You need to have a set of chisels and they need to be sharp. So, in a few hours you know how to make handcut dovetails. Trouble is, you can lean how to play piano the same way.

The guys who cut these in four seconds flat while whistling are like Rachmaninoff, only they’re dustier than he was when he did his work. I’m working up to Peanuts’ Schroeder.

20130310-05

It is made from an oak veneer birch plywood, but not multiply. The dovetails are cut at 14 degrees, as clearly indicated by Veritas’s sales literature for dovetail marking guides. The effect of the dovetails with sheet goods is rather cool. It makes the wood look hinged on the ends. It is pretty strong too, though I wouldn’t want a child to stand on the top.

20130310-25-zoom

The better fitting parts, like the example above, are really pretty good. Over the length of the joint there are places that gap a little. The thin oak veneer flaked off at the joints in some cases, and so the structural gaps are actually smaller than the surface gaps.

20130310-06

Big Centipede

Last August my son’s school started the year with a school-wide focus on insects. When we’d drop him off or pick him up we would see experiments laid out to determine various properties of ant behavior. We collected arthropods to bring in too, butterflies, bees, spiders, whatever we could find.

One evening my wife was sitting on the couch, and I was wandering about the kitchen. We were talking. She noticed something crawling across the floor.

20120819-14-edited

This centipede is about 11 cm long, or about 4.5 inches. This is not that big in an absolute sense. You aren’t going to be carried off. But as crawly critters go, this is really, really big. I think this is desert tiger centipede, but I really don’t have a key or guide that I trust.

The centipede is really a neat animal. Primitive, segmented all over, even the antennae. Alien, though, is the word I think when I see it. Their eyesight isn’t good, their shell isn’t robust and they’ll dry out if left in the sun. I suppose this is why we haven’t seen any of these again.

20120819-25-edited

We brought it in to share with the class. I think it was unwelcome since ti came home the same day.