Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ReproNim timing sync round 3 #3

Draft
wants to merge 19 commits into
base: master
Choose a base branch
from
Draft

ReproNim timing sync round 3 #3

wants to merge 19 commits into from

Conversation

vmdocua
Copy link
Collaborator

@vmdocua vmdocua commented Sep 2, 2024

Main purpose is to provide additional data and tools to achieve goals described in ReproNim/reprostim#13

  • Create extended table with corresponding timings per each 3d volume in each 4d DICOM and corresponding birch and qrcodes in videos. From this table we will get “mean” and variances.
  • Provide statistics info for different clocks we have based on information in timing-dumps data.
  • Review/rework series generation algorithm, to support different intervals on the fly. Provide more information in dump_marks.log regarding detected series in each swimlane.
  • Tests for generated marks in series we have (ses-20240528, ses-20240604, ses-20240809), to match series datetime start between each other.
  • Merge tmap data from series we have into default global tmap table (repronim_tmap.jsonl).
  • Create "linear" function in tmap service to calculate clock with interpolation/prognose.
  • Investigate new session ses-20240830.

vmdocua and others added 19 commits September 2, 2024 12:56
…ithm to be more strict and use pre-matched birch series if found for more accurate results.
…h DICOMs one, use match with the best scored).
… processing in case records are after the expected study range.
…e DICOMs offset for ses-20240830 with new functionality and regenerated all data.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants