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

parseSNP #2

Closed
katholt opened this issue Jan 29, 2014 · 4 comments
Closed

parseSNP #2

katholt opened this issue Jan 29, 2014 · 4 comments
Assignees

Comments

@katholt
Copy link
Owner

katholt commented Jan 29, 2014

No description provided.

@katholt
Copy link
Owner Author

katholt commented Jan 29, 2014

coding consequences
tree post filtering

@d-j-e d-j-e self-assigned this Feb 4, 2014
@d-j-e
Copy link
Collaborator

d-j-e commented Apr 23, 2014

both coding consequences and tree post filtering (variation and conservation) restored/added to pipeline

@d-j-e d-j-e closed this as completed Apr 23, 2014
@d-j-e
Copy link
Collaborator

d-j-e commented May 21, 2014

parseSNPtable currently uses too much memory for larger files (e.g. 1.1 Gb allele table needs 80 Mb to be filtered!) - changing from dictionary to simpler 'string' structure for handling will reduce memory use to about 2X size of allele table (i.e about 2.2 Gb for the example above).

The full conversion is under way - will be included in next update of RedDog

Note: there is also a small error in the calculation of conservation filtering when outgroups are included - this will also be fixed in the updated version of parseSNPtable.

@d-j-e d-j-e reopened this May 21, 2014
@d-j-e
Copy link
Collaborator

d-j-e commented Jun 13, 2014

Full conversion of parseSNPTable.py now complete - now uses much less memory

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

No branches or pull requests

2 participants