Skip to content

Sessions Reported Inaccurately #4

Closed

Description

@miloswrath

Problem

There are sessions that are being reported inaccurately and causing some files to be lost due to early session assignment.

Replication

Add a session to rdss that should technically be 2, then add 1 after having ran pipeline.

Solution

Working through adding a file fingerprint to make sure that sessions are correctly reported and to rename when needed.

Activity

  1. self-assigned this
    on Feb 3, 2026
  2. miloswrath commented on Feb 4, 2026

    @miloswrath
    ContributorAuthor

    Using tsv and line hashing to solve this, introduces a LOT of complexity and may take longer than expected.

  3. miloswrath commented on Feb 5, 2026

    @miloswrath
    ContributorAuthor

    Next Steps - run new changes on vosslnx in temp dir for confirmation. IN PROGRESS

  4. miloswrath commented on Feb 5, 2026

    @miloswrath
    ContributorAuthor

    Summary of Changes

    • Reworked session determination to use lightweight signatures + TSV history,
      handle conflicts with renames, and gap‑fill runs per subject.
    • Integrated session renames before copy, updated duplicate handling, and
      normalized session path helpers.
    • Added/updated tests covering signature reuse, TSV conflict reassignment,
      gap‑fill, logging coverage, and end‑to‑end dry‑slice behavior.
  5. miloswrath commented on Mar 5, 2026

    @miloswrath
    ContributorAuthor

    view #13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions