Closed taltman closed 6 years ago
Hey Tomer, I think the way I have been naming my converted 23andMe files (converted23andme.txt) is causing some issues when your code tries to convert one of my files because of the name. Is there a standard naming practice I should follow?
Edit: I think I found a generic filename that works in the parser.
In the makefile, the file you try to get with: "wget ftp://ftp-trace.ncbi.nih.gov/1000genomes/ftp/technical/reference/human_g1k_v37.fasta.gzi" Does not show up anymore and it is preventing the tests from running correctly. wget gives a no such file error. Is there a replacement that I could substitute in?
Hi Max, I've committed a series of changes to dev. You should pull those changes from the dev branch to your feature branch, so that you'll work past that build issue in the Makefile. Thanks!
Hi @mxscott, regarding the filename issue, probably best to create a separate issue and assign it to me if you are hitting a problem working with the code. Please include an example of where a file name leads to breakage. Thanks!
Create a test function in MAMBA that uses your code to generate a 23 & Me text file, and then puts that file as input for the 23 & Me -> VCF function that I've written.
This will require you to use the Docker framework to auto-install the dependencies that are external to Python.
Thank you!