Feature/remove recording sample frequency choice #149
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Boolean "events" such as gear down happen at the very time they have
been recorded ("p1")
- So no need to interpolate them between "p1" and "p2"
- Add unit tests
- Reason: position data is now sampled at a fixed 1 Hz only anyway (to smoothen position data, specifically in case of "stutters") - Attitude data is sampled "as fast as possible" (every simulated frame) - All other simulation data is sampled "as available" (infrequently) - Simplifies recording code - Few users probably actually knew about this "Recording Frequency" option, let alone were using it actively
- Calculate both position- and attitude sample rates
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.