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

Different coverage report uploaded in scout #778

Closed
keyvanelhami opened this issue Mar 26, 2018 · 5 comments
Closed

Different coverage report uploaded in scout #778

keyvanelhami opened this issue Mar 26, 2018 · 5 comments
Assignees

Comments

@keyvanelhami
Copy link

When uploading a family in Scout, one can get two different values in the coverage reports on the different level of coverage.

For example if clicking on the "View report" in Scout, the values for the different coverage depth will be shown. If the URL link is copied and pasted in a new tab, all values will change and totally new coverage values will been shown. The same appear for the covered transcripts. See attached files

Twist50M_lower_cov.pdf
Twist50M.pdf

@northwestwitch
Copy link
Member

northwestwitch commented Mar 26, 2018

I've found the reason why the report seems to act weird. Whenever you click on the coverage report button from scout you pass a gene list to chanjo_report and this list is used to calculate the coverage I guess. See the first figure: there's a lot of genes passed to the page for panel 1.

screenshot_0

When you refresh the page the list is not passed and in fact there are no genes for panel 1. See what it is passed on this other screenshot:

screenshot_1

The coverage numbers are different because in the first case the coverage is calculated on the passed genes, but after the refreshing the statistics are on something else.

It's quite easy to fix I think but the problem is that we don't have chanjo_report among our repositories so we have to fork it, modify it and re-install it on the server. A bit of a hassle but I'll work on it!

@northwestwitch
Copy link
Member

I have fixed the issue, now I just have to know where I should I do the pull request: on our forked chanjo-report repository on clinical genomics (see the new branch), or the original. See here: robinandeer/chanjo-report#29 .

@northwestwitch
Copy link
Member

There is a problem with the release version of chanjo-report running on clinical-db. The installed version is in fact version 3.0.something while the updated one is 4. The fix I wrote does not apply to the old version at all so this bug is not fixable until we do a major upgrade of chanjo-report (and scout?). We'll fix it but for the time being keep in mind that if you are interested on the coverage on the specific genes of the panel(s) then you should only trust the report produced by the button in scout. Do not refresh the page (from the browser) or copy the URL to another browser tab and most importantly don't share the link in emails and so on. If you need to send or save coverage reports download the PDF from the scout side panel.

@moonso
Copy link
Contributor

moonso commented Apr 18, 2018

@northwestwitch can we close this since it is chanjo-related and not scout-related?

@northwestwitch
Copy link
Member

Yes, I'm closing it!

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

No branches or pull requests

3 participants