-
Notifications
You must be signed in to change notification settings - Fork 33
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
more flexible file designation for sailfish #5
Comments
Yeah ill have to rework this I just commented it out for now |
Moving forward I may be able to help simplify this. The reason for the (somewhat tortured) structure of the output (e.g. effective lengths being in a separate file) was to maintain backward compatibility with prior versions of Sailfish & Salmon. However, if it would be helpful here (and / or in other contexts), starting in the next release I'd be willing to break backward compatibility of the output format and put the effective length (and any other useful information) directly into the |
+1 for both of those suggestions. |
+1 for both as well. Simplifying here will help me with something else i want to do, which is make it easy for users to swap in readr::read_table which is 50x faster |
I was also going to suggest readr. Faster, no stringsAsFactors, tbl_df goodness, etc. |
I think we're set here. Rather than go looking for stats.tsv, the effective length will be in the quant.sf file for future versions of Sailfish/Salmon, and tximport will now autodetect if its a old or new version. |
Trying to import sailfish results that aren't in the typical
dir/quant.sf
anddir/stats.tsv
convention, because I've moved/renamed some things:Coming from this bit of code:
tximport is strictly looking in the same path as the results file for
stats.tsv
. Suggest allowing explicitly specifying this file as an argument, but default back to this?The text was updated successfully, but these errors were encountered: