docs: run-log encoding options for course logs (turning + forward)#141
Open
mbreiser wants to merge 2 commits into
Open
docs: run-log encoding options for course logs (turning + forward)#141mbreiser wants to merge 2 commits into
mbreiser wants to merge 2 commits into
Conversation
…zes @ 15-min) Proposal doc (for Frank / #140): the 4 curated FicTrac fields for turning + forward locomotion (delta-rot lab side/fwd/yaw cols 6-8 + integrated heading col 17), and an encoding-options table from full-25-JSON down to compact CSV, with file sizes modeled on a 15-minute run @ 50 Hz (45k frames). Recommends the hybrid CSV-frames + JSON-events scheme (relative-ms, rounded floats) at ~1.8 MB. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…ted fields Add an explicit 'identity + timing' table (ms/seq/index) and put seq back into the recommended CSV schema; a full frame row is ms,seq,index,side,fwd,yaw,hd. Note seq is the only droppable field (~8 B). Reconcile the size note (~2.2 MB with seq / ~1.8 MB without over 15 min). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
Author
|
@floesche Please take a look at the proposal and let me know if you agree with the recommendation for updating the data logging, or if you prefer storing different fields in a different format. |
Member
|
I made some suggestions in #143. I think the minimal recording is sufficient: FicTrac is pretty efficient in recording the data, but that would require a post-hoc step to combine the data. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
A proposal doc to review with Frank on how to log FicTrac data for the course run-logs — balancing behavioural coverage vs. file size.
docs/development/run-log-encoding-options.mdcovers:side/fwd/yaw= cols 6–8, plus integratedheading= col 17), with the FicTrac axis convention + a bench sanity-check.frame_schemaline) with a concrete example.seq).Implementation is tracked in #140 — this PR is the shareable discussion doc; not required to merge as-is.