more flexible file designation for sailfish about tximport

[mikelove]

Yeah ill have to rework this

I just commented it out for now

[rob-p]

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 quant.sf file. Also, I think it might be useful to remove the comment character # in front of the line that names the columns so that they can be read in more easily with the typical tools (e.g. read.table and pandas.read_table). The default could then be to read the effective lengths directly from the quant.sf file and fallback to this strategy if e.g. the input is from an older version of Sailfish or Salmon. Thoughts?

[roryk]

+1 for both of those suggestions.

[mikelove]

+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

[stephenturner]

I was also going to suggest readr. Faster, no stringsAsFactors, tbl_df goodness, etc.

[mikelove]

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.