@adlangmead no i think it's in trouble, something where the underscore.js is pointing to the wrong place—I'll ping 'em