A question on how abyss-pe manages to find the library files

[leonardo alves]

Hi there,
Sorry if that's a dumb question, but I would like to understand how Abyss look for the files whose paths I've included after "in=".
For example:
$ls temp/
test_r1.fq.gz test_r2.fq.gz
Then running:
$abyss-pe -C out j=12 name=nana k=46 in='temp/test_r1.fq.gz temp/test_r2.fq.gz'
Returns the error:
Reading `temp/test_r1.fq.gz'...
error: `temp/test_r1.fq.gz': No such file or directory
However, typing the full path returns no error and the assembly runs smootly.
$abyss-pe -C out j=12 name=nana k=46 in='/home/some_path_to/temp/test_r1.fq.gz /home/some_path_to/temp/test_r2.fq.gz'

I am running Abyss 2.0.3 in a bash shell.

Many thanks!

[Ben Vandervalk]

Hi Leonardo,

When using relative paths, the paths must be relative to the `out` directory (because you used `-C out` in your command).  GNU make switches to the target directory first, then runs the assembly commands.

- Ben

--
You received this message because you are subscribed to the Google Groups "ABySS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to abyss-users...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[leonardo alves]

Hi Ben,
Think I got it. But does that mean I have to store the input files in the "out" directory when running?

Thanks

[Ben Vandervalk]

Leonardo,

Not at all! It just means that your relative paths have to be written as if you were in the "out" directory.  Probably that just means adding an extra "../" in front of your paths.

IMO, it is simpler and better practice just to use absolute paths.

- Ben

[leonardo alves]

That is alright. Thank you Ben!