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

IGV screenshot review feedback integration #6

Open
stevekm opened this issue Dec 10, 2016 · 3 comments
Open

IGV screenshot review feedback integration #6

stevekm opened this issue Dec 10, 2016 · 3 comments
Assignees

Comments

@stevekm
Copy link
Owner

stevekm commented Dec 10, 2016

A method needs to be developed to allow for manual review of IGV screenshot results by licensed clinician, followed by integration of the clinician's feedback on variants to keep or remove.

@stevekm stevekm self-assigned this Dec 10, 2016
@stevekm
Copy link
Owner Author

stevekm commented Dec 10, 2016

Current proposed implementations for this include:

  • printing a 'variant ID' in the full report next to each IGV snapshot. The ID can be copy/pasted by the clinician into an emailed reply, which can then be submitted to a script for removal of the given variant from the sample's report.

  • placing IGV snapshot PNG files in a directory mounted by both the clinician's computer & the report generator's system, allowing the clinician to drag&drop the images into 'PASS' and 'FAIL' directories, which can then be parsed by a script for removal from the sample report

  • developing an HTML IGV snapshot report with client-side JavaScript that allows the clinician to review all snapshots, then select which to keep/reject, and then output a summary of the selections which can be parsed by the report generator scripts to remove the selected variants.

@stevekm
Copy link
Owner Author

stevekm commented Dec 22, 2016

'variant ID' + removal script will likely be the best solution for this. Need to consider how this will affect database of all variants (to be implemented)

@stevekm
Copy link
Owner Author

stevekm commented Jan 1, 2017

Consider using 'excluded variants' file in report dir, refactor reporting scripts to check for presence, include 'Excluded Variants' section in report output.

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

1 participant