search

MuffinSpawn / FMS

My personal FMS task management and field-testing repository.
0 stars 0 forks source link

Selectable motion compensation #47

Closed MuffinSpawn closed 7 years ago

MuffinSpawn commented 7 years ago

At least initially we do not want any motion compensation, so we need to be able to turn it on/off (new property).

Additionally, we may want to manually apply a pre-compensation. Thus we need a way to configure motion compensation and modify the requested coordinates accordingly.

Finally, in order to study whether compensation is necessary and what values may be needed, the errors should be exposed in the client.

MuffinSpawn commented 7 years ago

Evwrything except the manual compensation piece is done. I'm punting on that since it's unclear a) whether that will ever be needed, and b) what form that would take. There are several variables that could contribute to a compensation on the request position such as absolute distance, relative distance, and acceleration. Furthermore, would the compensation model be strictly linear or will it involve higher-order terms that may or may not be linear? I think it's safer to study the situation and create something after we know what we need (if anything).