Skip to content

checking if historical pairing file was de-synced #996

@anoronh4

Description

@anoronh4

I am noticing that the historical pairing file that we instated in 2020 /juno/work/tempo/voyager/historical_pairing_file.tsv differs from the sample_pairing.txt file for 66 pairs. Maybe for a few we ran beaglecli tempo-mpgen override but this option was seldom used by me and probably doesn't account for 66 pairs.

here is the reference to a different historical pairing file used in the pairing operation:
https://github.com/mskcc/beagle/blob/master/runner/operator/tempo_mpgen_operator/tempo_mpgen_operator.py#L27
how are changes to this file tracked? and how come the previous pairing was "forgotten" ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions