For an impulse that uses high res accelerometer data, the Float32 version of the model has a lot better performance. When I go to run “Analyze Optimizations” under to Deployments so I can download the Float32 version of the model, I get the following error:
Creating job... OK (ID: 226421)
Cannot read property 'interval_ms' of undefined
Job failed (see above)
It turns out this is because I do not have any Testing Data. Adding some solved this problem. A better error message would be nice, and/or a way to download the Float32 deployment without having to run the Analyze Optimizations.