This horrible violation of Cesium coding standards is a workaround for:

https://code.google.com/p/chromium/issues/detail?id=167394

It can be deleted once Chrome 29 (or maybe 28?) becomes stable.
Clean up descriptions on build targets.
Merge remote-tracking branch 'origin/master' into explained-NaNs
Merge remote-tracking branch 'origin/master' into explained-NaNs
Merge branch 'master' into buildFileCleanup
Merge pull request #920 from AnalyticalGraphicsInc/buildFileCleanup

Clean up descriptions on build targets.
Added @fstoner to CONTRIBUTORS.md
Using implicit surface function for ellipsoid.

Also some minor refactoring of boundary test.:
Simplification of ellipsoid surface function.
Removed ellipsoid ray intersection test.

The test in unnecessary.  It does elliminate a portion of the artifact
that appears when looking at a sensor facet edge on (the portion that
extends past the ellipsoid), but the real fix should be to the boundary
test.
Improvements to boundary test.
Fixed typo
Merge pull request #928 from cmorse/master

Fixed typo in specs
Fix for derivatives use in sensor shader.

Earlier code cleanup and refactoring made the artifact problem worse.  But
this change addresses the fundamental problem that use of the derivatives
was causing.
Adding comments to boundary tests for clarity.
Merge branch 'master' into sensorImprovements
Update dojo to 1.9.1

Fixed #883
Merge pull request #930 from AnalyticalGraphicsInc/dojo191

Update dojo to 1.9.1
Material uniforms tweak.

While the way Material deals with uniforms needs to be completely
refactored (for a variety of reasons which I won't go into here but will
write up an issue for later), a small tweak to the current architecture
can provide a huge performance boost.  The tweak here is that
getUniformType goes through an incredibly slow process to determine what
type of variable a uniform value is and it does this for every uniform
every frame.  This change simply caches the result.  As far as I know this
change has no ill affects and everything looks good to me.

Here's how I profiled.
1. Download http://bl.ocks.org/mbostock/raw/4090846/us.json and load it into Cesium Viewer.
2. Profile in master, on my machine getUniformType takes up ~33.0% of the time and frame rate is about 4.5 fps.
3. Profile in this branch, on my machine getUniformType takes up ~0.01% of the time and frame rate is about 7.0 fps.
Adding sensor boundary line width variation.