Skip to content

Fix hg38 -> hg19 liftover#5

Merged
GFJHogue merged 1 commit intomainfrom
fix-liftover
Aug 29, 2025
Merged

Fix hg38 -> hg19 liftover#5
GFJHogue merged 1 commit intomainfrom
fix-liftover

Conversation

@GFJHogue
Copy link
Copy Markdown
Collaborator

It looks like the liftover logic was actually changed and broken at some point after Wei's original/website code - and unfortunately that made its way into the working copy used to start this repo.

Anyhow, the liftover process wasn't properly handling reverse-stranded lifts, thereby causing a systemic -2 coordinate error, and more concerningly yielding incorrect bases in these cases.

I've fixed this to the best of my knowledge and added more informative Liftover warning stderr logs to help diagnose any related issues going forward.
These warnings are expected in cases where a base may have been changed between hg19 and hg38 - in these situations the ALT most often matches the hg19 reference.

@GFJHogue GFJHogue self-assigned this Aug 29, 2025
@GFJHogue GFJHogue requested a review from xindizhang August 29, 2025 21:46
@GFJHogue GFJHogue added the bug Something isn't working label Aug 29, 2025
@GFJHogue GFJHogue merged commit c4ea25c into main Aug 29, 2025
1 check passed
@GFJHogue GFJHogue deleted the fix-liftover branch August 29, 2025 21:49
@lstein
Copy link
Copy Markdown

lstein commented Aug 29, 2025 via email

@GFJHogue
Copy link
Copy Markdown
Collaborator Author

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

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants