ADP-adjusted Dynamic Value Based Drafting

August 22, 2009

I’ve created an OpenOffice spreadsheet to assist in fantasy football drafting, and am releasing it at the bottom of this post for everyone to use. If you’re not familiar with “value based drafting” or its “dynamic” variant, here are a few good links explaining the basics. Essentially, the method uses players’ projected stats to determine how much value is available at any given pick, compared to baseline projections of bench-level players and what other owners in the draft are expected to do.

It took several steps to complete this ADP-adjusted Dynamic Value Based Drafting (or, ADP-dVBD) spreadsheet. First, projections on players were collected from preferred sources such as Yahoo, FFToolbox, and FFToday. Second, average draft positions (ADPs) for a site I was drafting on were recorded for each player. In this case, I’m using recent point-per-reception (PPR) ADPs for 12-man drafts from Players are listed by position on different sheets and ordered by ADP. Then, the actual ADP-adapted dVBD calculations had to be created inside the spreadsheet. Since the order of players by ADP does not coincide with the order of players by projected fantasy points, this required a multi-step process. The dVBD offsets (or, “opportunity costs”) are calculated for players, and then the highest (and hence, relevant) opportunity cost at each position among players expected to be taken is found. There is a set of input cells for the drafter to estimate how many of each position (RB, WR, etc) will be taken before his next pick, so that the opportunity costs may be calculated. Lastly, there’s a set of cells to record the positions already taken on your roster, so that opportunity costs are reduced for bench players.

The minimal procedure to use the spreadsheet during a draft as picks are made is:

  • Delete the row (not “hide the row”, not “delete the content”) of a player when he is drafted.
  • When it’s your pick, enter the estimated number of players at each position that will be taken before your next pick comes around.
  • The recommended ADP-dVBD position to pick is the one with highest opportunity cost. Player names are given for the best remaining player at each position.
  • Make your pick, and update your roster listing with the new number of players at each position.
  • Continue!
  • Note, you’ll need to enter what draft slot you’re drafting out of in the appropriate cell, before the draft starts. It’s also easier to make predictions about how many players at each position will be taken before your next pick if you also update the positional rosters of other teams as they pick, but that’s not required.

    It sounds complicated, but is surprisingly easy to use once you open it up and have a look. If you want to use it for your league, you’ll need to update the ADPs, projected fantasy points, and “need multipliers” to match your league’s site and scoring/roster settings. It can also be extended to use additional roster slots, such as IDPs or flex positions. However, those things are left as an exercise for the user. I also left a blank column for player notes, since the spreadsheet is really great for that. I have all sorts of color coded notes in my personal version.

    I learned quite a bit about OpenOffice spreadsheets while creating all this. The OFFSET and INDIRECT functions were of particular value. If you notice any errors or have a particularly slick improvement or optimization to show off, please let me know.

    Good luck, and remember this is just a tool. Projections will inevitably be wrong. ADP-dVBD will be wrong. There is no perfect fantasy football drafting strategy, and it’s more art than science. So if the spreadsheet tells you to pick player A, but player B is also right there and you really want to take him instead — go for it and have fun!

    DOWNLOAD the spreadsheet. OpenOffice 3.0 or higher required to use. OpenOffice is free, and available for Windows, Mac OS X, and Linux. Filetype is .ODT, although obviously this was initially created as an .ODS (spreadsheet). OpenOffice should automatically open it with the proper application. File updated to version 1.2 (bugfix: one-off on dVBD offset player recommendations) on Saturday, September 5, 2009. It is recommended that everyone upgrades to 1.2.

    Also, some shout outs to fantasy football or football sites I enjoy. I already linked Advanced NFL Stats, Football Guys, FFToolbox, FFToday, and Yahoo. But, other good sites include FFLibrarian, Pro Football Reference, Football Outsiders, Pro Football Talk’s Rumor Mill, Rotoworld, Rototimes, FFCalc, and ESPN. Lastly, a special mention for Fantasy Sharks and their Main Tank forum which I often visit.


    TACC Thoughts

    August 14, 2008

    This summer I visited the Texas Advanced Computing Center for a week-long Supercomputing Institute. The material presented during the institute was slanted towards the introductory, but it was a good trip. The MPI and optimization sessions were quite interesting, and Austin is a wonderful city. TACC’s marquee system is a NSF Cyberinfrastructure “Track 2” system named Ranger. Much like our group’s fastest cluster, it’s a quad-socket, quad-core AMD Opteron machine running CentOS (specifically, Rocks 4.2.1. Unlike our system, they have 62,976 CPU cores instead of 256. You’d think this would be a cabling nightmare. Nope! Check it out:

    Sun Constellation Infiniband Interconnect

    Sun Constellation Infiniband Interconnect

    Rear View of Ranger Rack

    Rear View of Ranger Rack

    Pretty impressive. In the first picture, you see the two Sun Constellation Infiniband switches, back-to-back, with the longhorns on top. If not for each of those switches having over 3,000 ports, the system would require many, many more individual switches to link all the nodes together. In the background you can see the front side of invididual racks, each of which contain 4 rows of 12 nodes each (with cooling stacks inbetween compute racks).

    More interestingly, in the second picture you can see what the cabling looks like behind the racks. On the right in that photo is a typical 48-node compute rack. Only 4 Infiniband cables are required per 12 nodes, because each cable contains 3 connects! Nice. They dont have any extra gig-E cables getting in the way, nor KVM cables sitting around. The power cables route nicely into the sides. The rack on the left is a bit more crowded: it’s a disk storage rack. Still, the cables aren’t a mess. Check out all the hot-swappable power supplies in both racks!

    Adding up the money spent on building construction, initial hardware, operations and support, Ranger’s expense is roughly $50,000 per day over an expected 4 year lifespan. The air conditioning alone eats over a megawatt of power. You know, an Alaskan supercomputing center with an innovative building design for natural A/C could be a Really Good Idea.

    What would you do with tens of thousands of cores? The most popular applications are computational fluid dynamics (physics, engineering) and molecular dynamics (chemistry, computational biology). In a few years, writers of desktop applications are going to be facing this problem on a much smaller scale, as new machines are sold with 8-16 cores standard.

    I think the most promising future applications are in optimization and artificial intelligence. They may have unusually productive weak scaling properties. In the meantime, the best way to get a grant for these machines is to have a problem (or rather, a solution!) which involves a strong scaling calculation. Fortunately, our simulation codes fit the bill.

    I have to wonder what they will do with Ranger in ten years…or less. Decommissioning a machine of that size is a large undertaking. Would it be sold to recyclers?

    The TACC staff are quite nice and energetic. It’s clear they’re seeking out people with good ideas for scientific problems that need ten-thousand-core solutions. If they ever host a conference or workshop you’re interested in, it’s worth the trip. Rent a car to see Austin, and avoid my folly of visiting the week it’s over 100 degrees outside every day! Hah.

    Completing the Cycle: Fresh Boot Camp with Windows XP SP3

    May 24, 2008

    I haven’t had a post about Windows yet, so here you go. My MacBook Pro has been dual-booting into Windows XP SP2 since I had OS X 10.4, “Tiger” installed. This is an older version of Boot Camp, with drivers that are now outdated. I also tinkered with them a bit by installing some newer NVidia drivers from

    I wanted a fresh Windows install with SP3 and the latest Boot Camp 2.1 drivers. Apple recommends that you install Boot Camp 2.1 before installing SP3. But what if you have a Windows disc with SP3 already slipstreamed? It should work, but I couldn’t find a good answer on the web, and decided to try it myself.

    I created a slipstreamed SP3 disc from our University’s volume licensed SP2 disc using nLite. No problem. I then repartitioned my MacBook Pro’s drive using the Boot Camp Assistant and followed Apple’s instructions to the letter. The Windows install, using my SP3 disc, went fine. I did get a black screen after the initial reboot, but manually power cycling the machine gave a clean boot.

    I proceeded to install the Boot Camp 2.0 drivers from the Leopard disc. This went mostly smoothly, but the “SM Bus Contoller” was not found in Windows Device Manager. To fix that problem, I re-inserted the Leopard DVD and told it to “repair” the Boot Camp installation. Maddeningly, this robotically proceeded to reinstall every Boot Camp driver. But hey, it fixed the problem! I then used Apple Software Update (which itself had to be updated) to install the Boot Camp 2.1 drivers. You know, the package Apple says should be installed before SP3 — that is true if you’re upgrading from SP2 to SP3. The Boot Camp upgrade took a while, but succeeded. For those who are curious, the NVidia drivers in Boot Camp 2.1 are version 167.73. I still had to run Windows Update to get IE7, WMP11, and a couple of hotfixes on top of SP3, but that’s nothing new under the Sun.

    In summary, a Windows XP SP3 slipstreamed disc may successfully be used for a fresh install with Boot Camp.

    Lab Install of Fedora 9

    May 22, 2008

    Fedora 9 was released last week. Our lab’s servers and workstations all run varying versions of Fedora or CentOS, the RHEL-clone server distribution. In preparation for the release of F9, we had decided to replace some aging 32-bit workstations. The new workstations all have Intel Q9300 CPUs, four gigs of RAM, NVidia 9600GT video cards, and a pair of 250GB SATA drives. The 250GB drives are kind of overkill — we do most of the heavy work on our servers and clusters these days — but hard drives are cheap.

    When configuring new computers, we usually keep a log in a notebook. This time, I decided to add the log here. Hopefully others performing a clean installation of F9 in a science/programming environment may find it useful.

    Clean Install Procedure

    The install procedure, guided by Fedora’s Anaconda, is as trouble-free as it was in recent Fedoras. On one older machine, we had trouble booting from the Fedora DVD (in particular, a crc error when loading the kernel and initrd). This was remedied by using another DVD burn of the install disc, but burned at a slower speed. The first burn just wasn’t entirely reliable.

    Our dual SATA drivers were partitioned using a custom layout. In our case, we created identical software RAID partitions on each disc: 4 gig for swap, 1 gig for /boot, with / getting the remainder. /boot needs to be partitioned as RAID-1, but swap and / were partitioned as RAID-0 for maximum speed. If a disk fails, it’s not a big deal for us: all of our important data and home directories are on a RAID-5 fileserver. After the RAID, the only time consuming thing in the initial setup is specifying the network info, which includes our static IP addresses.

    Our packages to install are in the default “Office and Productivity” section and the “Software Development” section. The most important part of this log is the following list of packages added for our customized install, the first batch of which are on the DVD:

    • emacs – it’s surprising that vi is installed by default, but emacs is not
    • openbabel – a chemistry utility in the science and engineering subsection
    • all optional packages in the graphics subsection – imagemagick is particularly important
    • k3b – the best CD/DVD burner to be found for linux
    • lynx – the classic text-only web browser
    • the fedora packager subsection
    • gnuchess – how can other games be installed, but not chess?!
    • memtest86+ – useful for hardware troubleshooting
    • the system tools subsection
    • the legacy software compatibility subsection
    • tcsh – most of our lab uses this shell! this should be installed by default
    • gnome-netstatus – a useful widget
    • thunderbird – a couple members of our lab use this for reading mail
    • the authoring and publishing subsection – mostly for the TexLive packages

    Things to do at Firstboot

    After the 1300+ packages finish installing, a couple things (such as NIS logins) are configured on firstboot. Logging in as root, we need to configure two additional repositories: livna and adobe-linux. Then, we install additional packages from the Fedora repository via yum:

    • xpdf – lightweight, fast, and useful pdf viewer
    • xdvik – amazingly, xdvi is not distributed with F9’s TexLive packages
    • autofs – this is needed to mount our /home directories, and is surprisngly omitted from the F9 DVD
    • openmpi and openmpi-devel – parallel (MPI) compilers
    • scipy – a suite of modules for doing science with Python
    • PyX – a nifty module for drawing graphics with Python and LaTeX
    • grace – the best 2D graphing program for GNU/linux
    • readahead – a small package which helps cache files to speed the boot process

    Lastly, the media packages, (mostly) from livna and adobe-linux:

    • nspluginwrapper.i386 and alsa-lib.i386 – needed for getting i386 (32-bit) Flash to work with x86_64 (64-bit) Firefox. alsa-lib is needed for sound.
    • flash-plugin – flash itself, via the adobe-linux repository
    • mplayer – for playing movies and mp3s, via livna
    • lame – a mp3 encoder/decoder
    • libdvdcss – a DVD decoder
    • amarok-extras-nonfree – more plugins for Amarok, an alternative to mplayer (will install h.264 support as a dependency)

    While using yum to install all these packages, many dependencies will also be installed. This is normal.


    Now that autofs and other packages have been installed, the default services need to be configured at System>Administration>Services.
    The following are switched to disabled:

    NetworkManager – a new service being pushed by Fedora, but it overrode our static IPs with DHCP IPs
    bluetooth – not needed on workstations
    ip6tables – we don’t use IPv6
    isdn – we don’t use ISDN

    The following are switched to enabled (all these are needed for our lab’s local network):

    autofs – automounting remote nfs shares
    netfs – needed for autofs and other remote mounting
    network – replaces NetworkManager
    ypbind – NIS client

    Additionally, smartd and lm_sensors may be enabled if you plan on carefully monitoring your hardware.

    NVidia 3D Drivers and Fedora 9’s

    One thing I haven’t mentioned yet is the NVidia 3D video driver. Fedora 9 includes a pre-release version of, and NVidia’s proprietary, closed-source drivers have not yet been updated to support it. Even the supposed -ignoreABI and Disable “glx” workarounds completely fail. The solution is to downgrade some key packages to the Fedora 8 versions. A minimal downgrade can be successful by only changing five packages. However, depending on your own particular hardware and software configuration, more packages may have to be downgraded. Here’s the procedure:

    1. Get the following files:


      Other packages some people may need include xorg-x11-drv-void, xorg-x11-drv-vesa, xorg-x11-drv-evdev, xorg-x11-drv-fbdev, xorg-x11-drv-vmmouse, and xorg-x11-xkb-utils.

    2. Install, with
      rpm -Uvh --oldpackage --replacefiles --replacepkgs --nodeps xorg*
    3. Get the nvidia driver from Livna:
      yum install xorg-x11-drv-nvidia-173.08-1.lvn9.x86_64

      NOTE: that exact version is important. The 173.08-2-lv9.x86_64 package (note the -2 instead of the -1) was found to fail on our workstations. If you do not see the -1 version as an option and do not want to download and install it by hand, try installing the “yum-allowdowngrade” package and then seeing if the older version shows up.
      xorg-x11-drv-nvidia will also want to install the following, as dependencies:

      kmod-nvidia, xorg-x11-drv-nvidia-libs, akmod-nvidia, livna-config-display, kmodtool, kernel-devel, akmods

      Make sure the kmod-nvidia, xorg-x11-drv-nvidia-libs, and akmod-nvidia versions match the xorg-x11-drv-nvidia version (-1 instead of -2). The kernel-devel rpm that is installed will typically be the newest one, which will not match a non-updated Fedora 9 kernel. Now would be a good time to do a

      yum update kernel*

      as well.

    4. Finally, add the line:

      to the end of /etc/yum.conf so that the next time you upgrade anything it doesn’t replace all the F8 files with F9 ones.

    5. Reboot; the nvidia driver should get built during the boot sequence. Might require two reboots for this, or manually restarting
      service nvidia restart

    emacs and Firefox 3 tweaks

    There are a few other tweaks a fresh install of F9 needs. In particular, emacs defaults to courer 12, which is a bit larger than needed. To have it default to courier 10, add the following to your .emacs file:

      ;; custom-set-faces was added by Custom.
      ;; If you edit it by hand, you could mess it up, so be careful.
      ;; Your init file should contain only one such instance.
      ;; If there is more than one, they won't work right.
     '(default ((t (:stipple nil :background "#ffffff" :foreground "#000000" :inverse-video nil :box nil :strike-through nil :overline nil :underline nil :slant normal :weight normal :height 122 :width normal :family "adobe-courier")))))

    Also, the Firefox 3 beta 5 address bar may be particularly ugly to people accusomted to the cleaner Firefox 2 interface. Much of the previous style can be restored by modifying some settings in “about:config”:

    1. In the address bar, type “about:config” and hit enter.
    2. Accept the “void your warranty” warning
    3. Filter for “urlbar”
    4. Double click on browser.urlbar.autoFill
    5. Double click on browser.urlbar.matchOnlyTyped
    6. Double click on browser.urlbar.maxRichResults and changed the number from 12 to something more tolerable, like 2 or 3.

    Now the address bar should behave a little more like Firefox 2.

    It’s the little things.

    April 1, 2008

    The Usenet, once the dominant form of internet communication, has been rendered largely irrelevant by the World Wide Web. Yet, it can still be a great source of information: some technical groups (such as comp.lang.fortran) have an impressively high signal to noise ratio.

    It was a search for esoteric Emacs knowledge that sent me to Emacs has a nice syntax highlighting ability which makes source code more readable, by associating color with functionality. I wanted intrinsic procedures such as “mod” or “exp” to highlight in a different color than executable constructs such as “if … then” statements. Fortran mode in Emacs does this by default, but F90 mode does not. Here’s an example:

    Fortran mode

    if (mod(k,10).eq.0) then
    things to do

    F90 mode

    if (mod(k,10).eq.0) then
    things to do

    It’s a small difference, but in complicated code with many different procedures or constructs, it makes life much easier on my eyes. It wasn’t clear from the Emacs source how to make F90 mode match Fortran mode.

    Luckily, Glenn Morris, the maintainer of the fortran.el and f90.el filters, reads and was able to give me a fix:

    I don’t really know why it is like it is, but it is. Anyway, add to~/.emacs:

    (eval-after-load "f90"
         (setq f90-font-lock-keywords-3
          (append f90-font-lock-keywords-2
               (list f90-procedures-re '(1 font-lock-builtin-face keep))
          f90-font-lock-keywords-4 (append f90-font-lock-keywords-3
              (list f90-hpf-keywords-re)))))

    It works — my Fortran 90 looks good again. So many parentheses! The recently deceased Arthur C. Clarke may have imagined that most people would categorize Emacs Lisp scripting as magic.

    Personal Installation of OS X 10.5.2

    February 27, 2008

    Adventures with OS X. I decided to keep a detailed record of my fresh, custom install of OS X 10.5 (Leopard), after being an Apple “switcher” and Tiger user for about six months.  I’m also a computational chemist, and my install will feature many scientific or programming related applications.  My Mac is a Santa Rosa MacBook Pro (65nm Merom, 2.4 GHz, 2007), and it’s great.


    • Before performing the erase and install, I backed up everything to my Seagate Freeagent Desktop 500GB external USB drive. It was partitioned into three sections: one for a Disk Utility backup, one for a SuperDuper 2.5 backup, and one for a Winclone 1.6.6 archive of the Boot Camp partition.

    Special Items

    The Fresh Install Procedure

    • After backing everything up, I performed an “erase and install”.  I like my OS nice and clean, with no settings or software left from a previous version.  I customized the install to exclude foreign languages and most printer drivers.  I retained X11.  There are a lot of lists on the web touting themselves as “50 essential Mac apps” are other nonsense. My list of installed apps really are essential for my day-to-day workflow and entertainment.  I strive to keep my system as minimalist as possible.  The following items were installed in order.
    • 10.5.2 combo update downloaded from Apple’s website.  Note, my Freeagent was not detected from inside 10.5.0, and I did not want to use software update for this step.  Reboot.
    • Xcode 3.0, Dashcode, and the ADC Reference Library. Xcode and Dashcode were optional installs from the Leopard DVD, and the ADC Library was copied to /Developer from the March ADC Monthly mailing disk image, which I had stored on my Freeagent.  The ADC Library contains over five gigabytes of documentation which is not installed by default with Xcode.
    • Xquartz 2.1.4, a significant upgrade over Leopard’s X11.  This will be needed later by Macports applications which use X11.  Jeremy Huddleston and Ben Byer maintain this package, and both work for Apple.
    • iLife ’08 and iWork ’08.  They’re nice collections of apps.  I find Keynote, iPhoto and iMovie to be of particular value.
    • After all the Apple software was installed, I performed the online Software Update.  14 updates were found.  By design, none of the applications had been opened yet.  After a reboot, I completed the keyboard firmware update and ran Software Update again.  Two updates were found; I did not keep track if they were part of the original batch of 14.  The last updates installed smoothly.
    • Now was a good time to open an iWork application and complete the mandatory registration, and enter in my Quicktime Pro upgrade code.
    • Flip4Mac and Perian 1.1 began the parade of third-party applications.  These are nice codec collections for Quicktime, although I think VLC is pretty good too.
    • Caffeine 1.01 and iStat Nano 2.2 are two widget applications.  Caffeine loads in the menu bar, and is a simple way to toggle power-saving features of laptops.  I prefer the minimalist approach of iStat Nano over the more popular iStat Pro.
    • Skype, their first official Leopard release.  Not everyone can be reached via iChat.
    • VMD 1.8.6, a wonderful visualization tool for chemists and biologists.
    • Aquamacs 1.3a, a port of the popular *nix editor, emacs, to an OS X native Aqua interface.  Awesome.  I want to use the Xcode IDE environment more, but Aquamacs has better syntax highlighting for Fortran, and I use emacs on Linux systems.
    • I also installed a fortran plugin for Xcode 3.0.  I learned about this at the nifty site  The only drawback to using Xcode is that its syntax highlighting for fortran isn’t quite as good as aquamacs / emacs. Anyway, don’t forget to defaults write DBGFortranBasePath /opt/local/bin/gfortran-mp-4.2
    • Macports 1.6.0 base installer.

    Macports Configuration and Package Installations

    • There is a bug in the Macports 1.6.0 base installer which doesn’t set a couple paths (and perhaps other things) on Leopard. So, I ran the Macports svn repository postflight script.
    • Next, I edited a setting in sources.conf to install my macports local portfile: py25-pyx, and copied the Portfile to the appropriate local directory.
    • As I have two cores for compiling, I set the macports.conf buildmakejobs to 2.
    • Now it’s time to “port install” the packages I need.  Macports will automatically install the ports for any dependencies.  I started with gcc42 (4.2.3).  Leopard/Xcode 3.0 comes with gcc 4.0.1 and does not provide gfortran.
    • Next, the parallel compiler package, openmpi +fortran (1.2.5).  Again needed to handle the 4.2.x compilers and parallel fortran.
    • grace (5.1.21), a wonderful 2D plotting program which is also popular on Linux systems.  Grace uses X11, and one of its major dependencies is openmotif (more on that later).
    • PyX, a Python package for creating 2D/3D graphics with a TeX interface.  In Macports, this is py25-pyx (0.10).  I need PyX for some 2D vector graphics creation from simulation output.  A notable dependency of py25-pyx in my Portfile is TeX Live 2007 (by default it depends on teTeX).  Several users have had problems installing texlive on Leopard, possibly due to missing openmotif or a strange X11R6 path problem.  There is a syntax bug in a TeX Live fonts map file which PyX warns about, but it is easily corrected.  Finally, py25-zlib (a dependency for py25-pyx) failed to build, but I came up with a workaround.
    • ImageMagick (6.3.8).  This suite of command-line graphics tools is great to have on any *nix system.  It’s useful in scripting when dealing with large numbers of graphics files.
    • I recently installed Tkinter and the Python Imaging Library.  py25-tkinter needed the same workaround as py25-zlib, but py25-pil installed easily.  At least one person has found my note about the zlib and tkinter workaround to be useful.

    Leopard System Preferences

    • The first thing to go was the desktop background, which was changed to the Black & White “Sea Mist” provided by OS X.
    • I set all four hot corners, to Screen Saver, Expose, Dashboard and Spaces.
    • Next were two of my favorite settings which I probably should have changed earlier, Trackpad clicking and two finger secondary click.
    • To Dashboard!  I added iTunes (I like that little control) and Stickies, while deleting that ridiculous calculator.
    • On to more serious work.  Gmail IMAP setup isn’t that bad (see the gmail link in my Special Items section), but the best options aren’t documented on  Do not store drafts or notes on server, do store junk on server.  I use “plain text composing” because many good people still use Pine.   I deleted the Apple Hot News RSS feed.  Set the IMAP Path Prefix to [Gmail].  Now the initial IMAP mail import can be done.  When that’s finished, right-click on the Gmail folders to use the Gmail ones for Sent, Trash, and Junk.  Note, the IMAP sync to Gmail’s “All Mail” folder was rather slow, as has been noticed elsewhere. Also, my Spam folder is filtered on the Gmail side so that items in it do not appear as unread.
    • Security settings! Amazingly, even after installing 10.5.2, the Leopard firewall was still disabled by default. So, after allowing ssh remote access in “Sharing”, I enabled the firewall (allowing ssh) and enabled the screen saver + login password prompts.
    • Speaking of ssh, next I copied the names and addresses of the machines in our lab’s local network from our main fileserver’s /etc/hosts file, and added them to my Mac’s /etc/hosts file.
    • Open PDF files in Preview instead of Safari, by default.
    • Lastly, banish the 3D dock.  How I hate it so.  This not only makes things look better, it visibly increases performance of minimizing/maximizing windows, dock scrolling and dashboard.  I had already applied the Leopard Graphics Update 1.0, and this performance difference is still present.  Hopefully it’s fixed in a future OS X update, but I do like the 2D look better anyway.
    • One thing which did not have to be changed was disabling Bluetooth wake from sleep, which Leopard does by default (Tiger did not).

    Put the External Drive Back to Work

    • It was about time to restore my personal data.  My movies, music, pictures, data and anything else that was backed up but not yet reinstalled.  This was the easy part; I just had to be sure to restore the iTunes database by copying over all its folders.
    • I configured Time Machine to use one of the three 160 GB partitions on my Freeagent.  This allows me to keep a complete backup of my old, bootable Tiger and Windows partitions for the time being. Unfortunately, the first attempt at using Time Machine failed!   I had erased the partition and set it up to do the initial TM backup, then I went to sleep.  Although it was running on external power, my MBP apparently went to sleep as well, after about 10GB of the backup.  TM did not recover gracefully, and I had to cancel it, and reboot in order to successfully reformat the Freeagent partition.  I tried Time Machine again the next day, this time using the Caffeine applet to disable system sleep.  It worked.


    • Acquire/install Adobe Web Premium CS3.

    Hello world.

    February 19, 2008

    Blog inception. wins my account by allowing uploads of PDF files, while provides no such luxury.