Open Maarten-vd-Sande opened 3 months ago
that is interesting. there is one thing that the frozen_tracks4 branch does that main does not, which is that it will actually put the entire track configuration into the session, instead of just a reference to the track by the track id.
this normally is ok but could, potentially, haven't traced exactly how, but lead to some weird behaviors that are hard to track down (for example mismatches between the config stored in the session and the config stored in config.json). technically, this is a bug that should be fixed on the frozen_tracks4 branch
example of a session in frozen_tracks4 (via Export session after opening a cram track)
example session from main after opening a cram track
But the strange part is that the original view is wrong. But the view from the exported session was correct.
yep i can't explain the behavior exactly. if you get any more clues feel free to update. i can tag the issue as 'hard to reproduce' :)
Describe the bug
I have a cram file with amplicon sequencing reads, and a cram file with its corresponding "haplotypes". I work with a diploid, so that means I have at most two haplotypes per amplicon. I noticed a discrepancy between my reads and haplotypes, which concerned me. When coloring at the base I noticed the sequence is way off with the reference, and since it is a CRAM file it is extra strange (has no md tag, it is determined on the spot if I understand correctly). When I asked my colleagues to take a look, they couldn't reproduce it. Turns out, if I now re-load the session, this discrepancy doesn't occur. I am not sure what caused this difference, how frequently it occurs (first time for me), and whether other users have the same issue. The files that were loaded have not been changed in between. The problem is also that I can not reproduce it, so I also cannot make a minimal reproducable example :(
I think this issue can be ignored for now. Especially since it's a wild goose chase without MRE, but it might serve as a place to collect more unexpected behaviour like this if they occur more frequently.
To Reproduce
I can't reproduce it..
Screenshots
https://github.com/user-attachments/assets/f320dedf-4ff4-4569-998a-370d8328069d
I loaded some tracks from local files, those it cannot load from the session of course (hence the failed tracks)
Version:
firefox, with the web version. The unreleased frozen tracks 4 branch.
Additional context