I started reading some literature on migraines, and learned that for some people, the headaches are “triggered” by some stimulus to which the person is sensitive. I was at a loss however, as I could not correlate the onset of my headaches with any particular stimulus. I saw a doctor, who seemed convinced that the headaches were stress-induced (first-year of law school, growing family, etc.). I disagreed, however, and continued to investigate.

One day, I suddenly came to the realization that the headaches began around the time I purchased a new laptop computer for school. I had never had any problems using any computer before, so it never occurred to me that the purchase of the computer might be related to the headaches. After some googling, I found this thread on forum.tabletpcreview.com, and a related thread on Lenovo’s forums, where others were reporting migraine headaches related to the LED-backlighting on the Lenovo X200 Tablet. Like most laptops sold today, my laptop, a Lenovo X200 Tablet, had an LED-backlit display. It seemed that I had found a good candidate for the cause of my headaches.

After some further investigation, this is what I have found:

• LED-backlights in most laptops do not generate constant light, rather, they flicker (flash on and off, like a strobe light) at a high frequency for most brightness levels.
• The flickering of the LED-backlight seems to serve two functions: (1) it saves power, and (2) it is used to control the brightness of the display.
• There are a couple of relevant characteristics to the flickering: (1) the speed at which the LEDs are turned on and off (frequency), and (2)  the amount of time that the LEDs are off, versus the amount of time that they are on, during each cycle (pulse-width).
• The brightness of the display is adjusted by changing (or modulating) the pulse-width, i.e., the LEDs are turned off for more of the time than they are turned on. This makes the display look dimmer.
• It would be possible to drive the LED-backlight with circuitry that does not flicker the light, but rather make the LEDs always on. This is not typically used, however, because the circuitry is either more expensive, or less precise.
• The flicker of the screen can be verified by viewing the laptop display through the LCD viewfinder of a digital camera. Because the frequency of the camera is not in sync with the frequency of the LED-backlight of the display, the display will appear to flicker through the camera.
• The Lenovo X200 Tablet uses an Intel integrated video chip, and by default the drivers for the display flickers the backlight at any brightness level lower than the maximum, and even if the brightness is at the maximum, if the laptop is operating on battery power, then the display is flickered (as a power-saving measure). However, if the laptop is plugged in to AC power, and the brightness is set to the maximum, then the LEDs are not flickered, but on constantly. Also, there is a setting in the Intel driver software to disable the flickering for the maximum brightness setting when on battery power (though it is obscure: in older driver versions, you had to turn off “Intel(R) Display Power Saving Technology”, in newer version you have to change the battery power plan settings to “Maximum Performance”).
• Different manufacturers use different frequencies for their LED-backlighting. Someone reported on the tabletpcreview.com thread that the X200 frequency is 90Hz (which is very low), while Fujitsu uses 500Hz.

It is not clear what aspect of the flickering induces migraines. It is, no doubt, different for each person that experiences this phenomenon. It’s not really surprising either, since it is well documented that some people have migraine sensitivity to flickering lights, such as florescent lights. (Note that previous display technology used florescent backlighting, at frequencies around 100Hz, however, a florescent light does not turn off almost instantly like an LED, and so the flickering is a little less significant.) Some people have had sensitivity to older florescent-backlit displays too, especially if they operated at lower frequencies. These people are in for a world of hurt as incandescent bulbs are outlawed in many parts of the world, and CFLs or LED lights are the only thing available.

At any rate, upon learning all of this, I set the display brightness of my laptop to the highest level (and I keep it there always!), and adjusted the driver settings so that even if I am using the laptop on battery power, the display is not flickered. Since that time (almost a year and a half ago), I have not experienced any more migraine headaches. My migraines were clearly linked to the flickering of the LED-backlight in my laptop, and I was not even aware of the flickering. The flickering did not act as a traditional “trigger” (in other words, it did not immediately induce a migraine), but over the course of a couple of weeks of use would give me a migraine. Everyone is unique; some people who are sensitive to the flickering get migraines within less than an hour of using the display.

Hopefully this dump of information will be useful to someone else who has experienced similar issues. It is bound to become a bigger issue as all manufacturers are moving over to LED-backlighting for all displays. Pretty soon all computer displays, all TVs, and all light bulbs, are going to be using this technology. It is possible that I am only sensitive to my current display because it operates at a relatively low frequency. This is hard to investigate though, because the data about the frequencies at which these backlights operate is very hard to come by. It is never disclosed by the laptop manufacturers. I hope that this will change in the future, for the sake of all the potential migraine sufferers out there.

Today is the first Friday in June, which means that it is time again to celebrate one of the most magical events of the year, National Doughnut Day. On this day we give thanks for all the joy and happiness that doughnuts have brought into our lives. It is a time to recollect on all the events that have been enhanced by the presence of those wonderful fried rings of dough.

This year National Doughnut Day is particularly poignant for me because I am back in the land of a million doughnut stores: Southern California. Here it seems that there are doughnut stores on every corner, and happily almost none of them are Dunkin’ Donuts. In Illinois there are quite a few doughnut stores, but 90 percent or more of them are Dunkin’. Upon our arrival in California, we stopped at one of the first doughnut stores that we saw, and were amazed to find that the doughnuts here are even better than we remembered. Hooray for good doughnuts!

Celebrate the day by getting yourself a free doughnut from Krispy Kreme, or one of the many other stores that are giving away free doughnuts today.

Recently, I made the jump to an electronic format for my scripture study and other church related reading. Currently, the best format for reading and marking up text on the computer is when it is in the form of a PDF. The LDS church makes most of its materials available as PDFs, but unfortunately that doesn’t include the scriptures, which are only available in various text formats or HTML.

In my quest to find all the standard works — the four books of scripture of the church: The Bible, The Book of Mormon, The Doctrine & Covenants, and The Pearl of Great Price — in PDF, I found that you can get a KJV of the Bible from a number of places (but not the LDS version with the footnotes), and you can get the Book of Mormon (but again, without the footnotes).

That’s when I came across this post on MormonTechie.com. A comment there explained how to download the Church’s HTML version of the scriptures and convert it to a PDF:

This is what I did to get the scriptures into a pdf:

Use HTTrack to copy the online scriptures to your computer. You can find it at http://www.httrack.com/.

You’ll want to scan http://scriptures.lds.org/en/ and under “set options” use the following scan rules:

+*.png +*.gif +*.jpg -*.css -*.js -mime:application/foobar
-*/*listen*
-*/*server*
-*/*jst*
-*/*helps*
-*/*/gs/*
-*/*biblemaps*
-*/*chmaps*
-*/*biblephotos*
-*/*chphotos*
-*/*search*
-*/*options*
-*/*help*
-*/*-*
-*/*/dc/*/**
-*/*/bd/*
-*/*/tg/*
-*/*/in/*

That will leave only the scriptures (no index, dictionary, photos, guides, etc.) in order to make the final pdf a manageable size. Also under limits, set max mirroring depth to 4. That will prevent all the footnotes from being copied. The footnote links in the verses still work, they’ll just send you to the online footnotes in your browser. The other links will move you around the pdf.

That should take an hour or so to download. Then you can use adobe acrobat (or the trial version of acrobat if you don’t have it) to make a pdf of the site that is now located on your hard disk. After opening acrobat hit ctrl shift O and enter the location of the index web page. Select “get entire site.” You can change the font size, and formatting of the pdf you’ll make under settings. It will take 45 min or so for acrobat to make your pdf.

The pdf I made is just under 45 MB. Now I can use my tablet to read my scriptures and save all the ink highlighting and annotating I make (I use PDF Annotator from GRAHL software). Navigating through the scriptures is very quick within the pdf. If you click on a link that is outside of the pdf (like a footnote) it will open your web browser so you can still access that info.

I did this and it worked out pretty well. My PDF is actually more like 17 MB, which is nice. Like the commenter explains, it doesn’t include the footnotes in the PDF, but if you have internet access, then it will link you to the church website. But it is still pretty hefty for most computers and PDF annotators to handle. So I made some adjustments to the layout, and broke each of the books up into separate PDFs that link to each other. Pretty cool. Now I can read the scriptures in the PDF, and mark it up with PDF Annotator or PDF Revu (as I have been doing with the other church materials) to my heart’s content.

Here it is for anyone that doesn’t want to go through the whole process to make it themselves: scriptures.zip (18 Mb)