Closed ArtPoon closed 1 year ago
Well, it looks like the options being passed to 3Seq
were wrong. -f
is used to specify the starting (from) coordinate of sequences to analyze. We should be using -full
to specify the entire input alignment for analysis.
Ok I take that back. After reading the 3Seq documentation, it seems like -f
is an overloaded option (I didn't think that was possible!) to specify both a full run and starting coordinate. There were other issues though - primarily that the file extension of the output file was missing (.csv
) and the parser function was looking for tab delimited, not comma.
Was this a Windows thing?
Fixed in dev
branch.
Gah. Did some more testing on my Linux machine:
<prefix>.3s.rec
, not <prefix>.3s.rec.csv
like macOS binaryOk updated code so it works for both macOS and Linux 3Seq binaries.
This exception is currently being thrown on master branch (commit
3a59bc1ae09c7fed4af4dd077c02d5abe9e097ad
):