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

checking if historical pairing file was de-synced #996

Open
anoronh4 opened this issue Feb 4, 2022 · 0 comments
Open

checking if historical pairing file was de-synced #996

anoronh4 opened this issue Feb 4, 2022 · 0 comments

Comments

@anoronh4
Copy link

anoronh4 commented Feb 4, 2022

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" ?

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

No branches or pull requests

1 participant