Closed lcoombe closed 5 years ago
Hi Lauren,
Hmm, that's unexpected behaviour. Only complete, single-copy cDNAs are supposed to be reported in the GM results table. It is possible for a cDNA to have lower-quality alignments in addition to a complete one (though these aren't reported, or really checked-for since it says 'good enough' after finding one or more complete alignments), but your example suggests that there is no complete alignment for WS03215_F02 at all.
Is it possible that Gnavigator is reading from a different alignment file than intended? Its autodetect function is pretty simplistic.
I'll send you a link to a spot where you can share the outputs :)
Thanks! Austin
Thanks for sharing your files! Gnavigator was erroneously checking the LG and order of all uniquely-aligned cDNAs found in the genetic map instead of just the complete ones. The latest commit (2c5b6c0) should enact the intended behaviour. Please let me know if it works for you, or if the new results don't look right.
Thanks, Austin
Thank you so much for this fix, Austin! I did a test run and did a couple of spot checks, and everything looks good now.
Hi Austin,
Hope you're well! I was working on slightly changing how we report the GM summary from the cDNA perspective, so I was taking a look at some examples. I thought that only 'Complete' cDNAs were used for the genetic map assessment, but it doesn't look like that's the case?
Example -
This cDNA is in the GM, but it is 'poorly mapped'. But, we do still use that cDNA for the GM assessment.
I'm just wondering if that was what was intended, and what the rationale for that is? I was wondering if including these non-complete cDNAs could prove to be an issue?
Thank you! Lauren