peterdsharpe
Joined 4 years ago
Joined 4 years ago
I train a new model. I publish my training data and my training code/workflow.
I then secretly do additional post-training to poison it. I do not release the data or workflow for this.
Now, I publish the poisoned weights and an md5 hash of the poisoned weights.
To you, the user - you have no way of knowing this happened.
You might ask "why not publish intermediate training checkpoints" but those are nondeterministic (in the sense of being not bitwise-reproducible). Anything with shuffling, random initialization, distributed races, driver versions changing roundoff, compiled vs. eager, and a million other factors introduce slight differences that yield totally different training trajectories. So publishing checkpoints does not yield verifiability.
Napkin math:
(27 minute flight) * (25000 lbm TOGW) * (Earth gravity) / (~10 average L/D) * (160 KTAS average) / (70% propulsive efficiency) / (97% coulombic efficiency) * ($50/MWh) = $30
(Add residual kinetic energy upon landing too)
Side note: Heart also has a weight issue here they'll need to overcome if they want to certify under FAR Part 23 (as their 19-pax spec implies); TOGW limit for that is 19,000 lbm.
"Largest" is just straight-up a false claim. [Solar Impulse](https://en.wikipedia.org/wiki/Solar_Impulse) and [Helios](https://en.wikipedia.org/wiki/AeroVironment_Helios_Prototype...) were electric and had over double the wingspan, just to name a few of the ~dozen examples.
Heart's engineers should be proud of this genuinely impressive accomplishment, but they need to rein in whoever is writing their PR pieces.