notroot

Ask anyone if their vote was counted. The only honest answer is, "I'm not sure." That is concerning.

Seems like a good kind of work to spread, thanks for sharing.

And then, Figure 4, 15 deployments are counted before instillation while no additional mileage is counted for the before instillation group. [pg.16] Could the NHTSA group really have done that? It give us an incredible rate of 15/0 deployments/mi without autosteer which violates some very important law of arithmetic, statistics and common sense.

I'm going to hold my breath until we see the data these claims are based on.

The plot thickens there in Figure 3 where they suggest mistreatment of deployments/miles that occur between `Prev Mileage before Autosteer Install Reported` and `Next Mileage after Autosteer Install Reported` "result in estimates of the true exposure that are statistically biased downward – resulting in crash rates that are somewhat too large." [pg.13]

This bit about before autosteer install airbag deployment counts coming from vehicles with 0 miles of before autosteer install distance is certainly odd, if true. "That is, simply because the data are missing for the Previous Mileage before Autosteer Install and the “Next Mileage after Autosteer Install,” NHTSA’s method of calculation assumes that all of the exposure mileage must belong to the “after Autosteer” category. The three airbag deployments without any exposure mileage in the “before Autosteer” category show this is not the case. " [pg.11-12]

Remind me what the ROC curve looks like for `can` again.

Yes, no, maybe, I don't know

Can you repeat the question?

alright, can we get the next study to show pigs are more intelligent than humans? shouldn't be too hard.

Why hexagons?

* Neighbor traversal

simplicity of neighbors; triangles 3 classes of neighbors, squares 2 classes of neighbors, hexagons only one class of neighbor!

* Subdivisions

Squares obviously do this pretty well but by alternating cw, cww rotations and allowing not quite perfect coverage they get to shard with different resolutions/hex sizes.

* Distortion

"most important" Basically the use case here is visualizations that maintain basic unit appearance. They even pick the location of their vertices to be over water minimizing land distortions.

source: https://youtu.be/ay2uwtRO3QE?t=11m53s

p.s. as `contravariant` said you can't tessellate a sphere with hexagons so they project onto a icosohedron with pentagons at each of the twelve vertices (positioned over water) https://youtu.be/ay2uwtRO3QE?t=23m00s

@ariwilson you work at google. since we're on the topic of truth and the actions of your corporate sponsor.

but again i get it, you got some stock and you gotta protect that bottom line.

"We might as well change Hacker News from an article based format to a [corporate sponsor] based format if everyone is just going to . . . [support their company in] every discussion."

'codelord:working on ml @google' haha. using accrued inertia/loyalty to bully/force `mit ocw` and `blender` to adopt more convenient terms for the company is, at minimum, a dick move.

but i get it, you got some stock and you gotta protect that bottom line.

There are a lot of good reasons why monopolies should be regulated.

Probably a super unpopular opinion here on hn but your boss `aint completely wrong. It's not a bad strategy when considering starting a business relationship with someone or something you don't know much about.

Agreed. I expressed some concerns about the now dead "trusted by" section as well https://twitter.com/stephenrigsby/status/973640170648956929 .

Also why is your comment kinda-greyed out?

oh man you can't delete comments? another reason why i shouldn't be on hackernews. nice work making something sorry for bein' a jerkk

maybe it's just me but i feel like using of any of these "tools" would slow me down when compared to using the equivalent shell-foo or a language built-in/library.

also seems like a terribly brittle externality to add to my life

Location: SoCal, Remote: OpenToIt, Relocatable: Yes

Technologies: python, Mathematica, JS, go, ruby, julia, C, bash.zsh

Resume/CV: https://docs.google.com/document/d/1osRS1Z5kPLSqm5jdiU3gHja5...

Email: rigsby at alum.mit.edu

I have been setting up custom software for small clients: automated systems both numerical and NLP based for a small hedge fund and for another client I worked with their software and hardware team to expedite development of their cloud data sharing service as well as their pressure sensor algorithms.

Quick overview of some research positions I've held; simulating offshore wind turbine designs, creating HMM/disease clusters for GE Healthcare, testing new gravitational communication model with data from AT&T as well as Telecom Italia.

rigsby_blurb: Software Developer with a BS from MIT; designed, wrote, maintained software deployed on Win, Mac, Linux and Android

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Location: Los Angeles, San Diego, Santa Barbara (moving to CA mid summer) Remote: OpenToIt Willing to relocate: Yes Technologies: python, Mathematica, JavaScript, go, ruby, julia, C, google, bash (zsh) Resume/CV: https://www.dropbox.com/s/n91fu9wialf1qud/rigsby_resume.pdf

Email: stephenrigsby at gmail dot com

Have of late been setting up custom server solutions for small clients; automated systems both numerical and NLP based. For a recent client I worked with their software and hardware team to expedite development of their "cloud" data sharing service as well as their pressure sensor algorithms for back country skiers interested in avalanche risk. Prior to this I worked on a DoD funded embedded system used in combat theaters, i.e. built and coded systems that ran in countries I've never been to. Please feel free to contact me if I may be of help to your team.

...and just in case some nefarious Dropbox/NSA/ISP/coffee shop hackers/hckrnews are trying to alter my words or document.

sha256sum rigsby_resume.pdf -> output 4f175764d5c646f52cf74dfb7edf4bb250262041acf1abf8e001faebb1bd9515 rigsby_resume.pdf -----BEGIN PGP SIGNATURE----- Version: GnuPG v1

iQEbBAEBAgAGBQJXLFqlAAoJEIj+T/k1V/OoKNgH9A2nPpQOiR8ckMHV8TyxK564 tt2AXAN8hqyXTjS6R+vxqKx21pKd3VxNqdjv9KCgrkm+n9UHmwGDlogrIWW2cUUu wNjhHVT8PyD4SaINdKfwFC7wbqAwKrnwPxd86qbzFXAC8ZPHrihJjvZbFdz49tSV yrlhPokCGd5AgbtMoPkqx+OS+2BC8qOLFUYxDLND4emVJpvveFksNk7e6Deu47i5 gNZeRicuUE06ZhVKrTuI1bIoCt6xL/fCbm5sWT2BexBZvpOPBkdiNirFsN8LeYTf e+PgK7WF9sFxXWEArNCcHRbPJx7W2esW6kOr0kYm0/7Fp/UpGwTj/yV5i9ntCQ== =gCNw -----END PGP SIGNATURE----- and if you don't use pgp.mit.edu https://gist.github.com/srigsby/ebbe9651fb5b946171e3e3942d5e...

http://blog.thedataincubator.com/2016/03/calculus-is-so-last... /source

gawd I'm tired of paywalls. If only I had a couple hundred friends with scanners we could... actually I guess I should just stop reading garbage like this and stick to worthwhile stuff like analysis/calc texts

Anybody wanna verify that the fnr in this sentence on the bottom of page 5 (1151) is an error and should be fpr?

"ROC curves that plot 'hit' rate (1-fpr) as a function of 'false alarm' rate fnr are instrumental..."

Was gonna email them but considering published in '03 figured we were more interested in this than they are at this point.

Boo. No mention of the [lightning network](lightning.network).