Closed seb-mueller closed 5 years ago
Yeah that's probably the problem. I thought of adding other combination of test/refs to the repo. The idea would be to run all possibilities to test the pipeline properly for all cases.
Agreed. I suspect it is easy to modify the reference genome to account for 2 species. Either append chr19 from mouse (plus renaming), or just split it in half with the second half being "mouse" genome to save space (but loose scientific accuracy which is fine for technical testing)
I think it's a bit more complicated because of the gtf file.
Maybe we should start with a dual reference and use only this for all cases.
Working on automating the download and metada generation completely with the new version. Will deal with double species cases
With the new version it works as expected. Although I'm not testing this on Travis but only locally. The test data is now actually a sample of a mixed human mouse.
We can implement multiple tests if we want but I'm not sure it makes sense since the mixed experiments are mostly used to test the doublet rates of a platform. I'm not sure people will make PRs for the mixed and that it needs to be tested online.
What do you think?
Not sure if this is due to my setup, but I'm getting regularly an error on the split_species rule.
To make it reproducible, I've tried it on the shipped data in
.test
:Running the following in the .test folder of a freshly cloned (including submodules) repository:
Gives the following
Does this work for you? Note, the map and filter rules etc. work just fine.
I suspect this is due to the absence of the second species in the reference files (only chr19). However the data-set seems a mixed_species.
I guess the reference has to be adapted to make the split_species rule testable. Thoughts?